From 70494f5e93abd2d5093bde46dfc5ee2ace3fdf65 Mon Sep 17 00:00:00 2001 From: askiiart Date: Tue, 8 Jul 2025 17:53:24 -0500 Subject: [PATCH] add arm saga part 1 --- blog/elitebook-g1q/the-arm-saga-part-1.html | 60 +++++++++++++++++++++ blog/elitebook-g1q/the-arm-saga-part-1.md | 32 +++++++++++ blog/feed.xml | 6 ++- feed.xml | 6 ++- sitemap.xml | 2 + 5 files changed, 104 insertions(+), 2 deletions(-) create mode 100644 blog/elitebook-g1q/the-arm-saga-part-1.html create mode 100644 blog/elitebook-g1q/the-arm-saga-part-1.md diff --git a/blog/elitebook-g1q/the-arm-saga-part-1.html b/blog/elitebook-g1q/the-arm-saga-part-1.html new file mode 100644 index 0000000..ab049b3 --- /dev/null +++ b/blog/elitebook-g1q/the-arm-saga-part-1.html @@ -0,0 +1,60 @@ + + + + + + The ARM saga: part 1 + + + + +

The ARM saga: part 1

+

Progress update and guide

+
+

Turns out in the time I was looking away, 1) the Elitebook + got added to the mainline kernel (somewhere in the 6.16 release + candidates), and 2) Ubuntu released an updated Snapdragon + Concept image - and not just that, I managed to find new + builds. Unfortunately, the version of Ubuntu I tested + doesn't support it yet, but it's a good start.

+

To work around this though, you can just add in the Elitebook + device tree manually (I stole borrowed it from the + postmarketOS package linux-postmarketos-qcom-sm7635 + and copied it to the drive), then updated the grub config + file:

+ 
  regexp "HP EliteBook Ultra G1q 14.*" "$system_product_name"
+  if [ $? == 0 ]; then
+    cmdline="clk_ignore_unused pd_ignore_unused cma=128M"
+    dtb="devicetree /casper/dtbs/x1e80100-hp-elitebook-ultra-g1q.dtb"
+  fi
+

I'm still gonna give Ubuntu flak for making new builds + without actually changing anything meaningful, though. At this + point, the mainline kernel has had better compatibility for over + a month.

+

What's broken

+

Out of some quick testing, these things were still + broken:

+ +

Based off the Postmarket OS page for the ASUS + Vivobook S 15, I wouldn't be surprised if video hardware + encoding/decoding was broken too.

+

But for the most part, it's working as far as I've seen - at + least, not crashing. There's certainly some errors in + journalctl, ones that I might not report because + Ubuntu's bug reporting is horrible, but it works.

+ + + + + diff --git a/blog/elitebook-g1q/the-arm-saga-part-1.md b/blog/elitebook-g1q/the-arm-saga-part-1.md new file mode 100644 index 0000000..99eb993 --- /dev/null +++ b/blog/elitebook-g1q/the-arm-saga-part-1.md @@ -0,0 +1,32 @@ +# The ARM saga: part 1 + +Progress update and guide + +--- + +Turns out in the time I was looking away, 1) the Elitebook got added to the mainline kernel (somewhere in the 6.16 release candidates), and 2) Ubuntu released an updated Snapdragon Concept image - and not just that, I managed to find [new builds](https://people.canonical.com/~platform/images/ubuntu-concept/). Unfortunately, the version of Ubuntu I tested doesn't support it yet, but it's a good start. + +To work around this though, you can just add in the Elitebook device tree manually (I ~~stole~~ borrowed it from the postmarketOS package `linux-postmarketos-qcom-sm7635` and copied it to the drive), then updated the grub config file: + +```txt + regexp "HP EliteBook Ultra G1q 14.*" "$system_product_name" + if [ $? == 0 ]; then + cmdline="clk_ignore_unused pd_ignore_unused cma=128M" + dtb="devicetree /casper/dtbs/x1e80100-hp-elitebook-ultra-g1q.dtb" + fi +``` + +I'm still gonna give Ubuntu flak for making new builds without actually changing anything meaningful, though. At this point, the mainline kernel has had better compatibility for over a month. + +## What's broken + +Out of some quick testing, these things were still broken: + +- Wifi +- Battery level +- Audio +- Processor isn't listed in GNOME settings for whatever reason + +Based off the Postmarket OS page for the [ASUS Vivobook S 15](https://wiki.postmarketos.org/wiki/ASUS_Vivobook_S_15_(asus-s5507q)), I wouldn't be surprised if video hardware encoding/decoding was broken too. + +But for the most part, it's working as far as I've seen - at least, not crashing. There's certainly some errors in `journalctl`, ones that I might not report because Ubuntu's bug reporting is horrible, but it works. diff --git a/blog/feed.xml b/blog/feed.xml index 32e15f8..be8deb0 100644 --- a/blog/feed.xml +++ b/blog/feed.xml @@ -5,11 +5,15 @@ askiiart.net blog The feed for askiiart.net but just the blog, I guess https://askiiart.net/blog/ - Fri, 23 May 2025 04:28:17 +0000 + Tue, 08 Jul 2025 22:53:00 +0000 The ARM saga: part 0 https://askiiart.net/til/elitebook-g1q/the-arm-saga-part-0.html + + The ARM saga: part 1 + https://askiiart.net/til/elitebook-g1q/the-arm-saga-part-1.html + 300 https://askiiart.net/til/300.html diff --git a/feed.xml b/feed.xml index 91583b2..3e32a63 100644 --- a/feed.xml +++ b/feed.xml @@ -5,11 +5,15 @@ askiiart.net The feed for askiiart.net, I guess https://askiiart.net - Fri, 23 May 2025 04:28:17 +0000 + Tue, 08 Jul 2025 22:53:00 +0000 The ARM saga: part 0 https://askiiart.net/blog/elitebook-g1q/the-arm-saga-part-0.html + + The ARM saga: part 1 + https://askiiart.net/blog/elitebook-g1q/the-arm-saga-part-1.html + 300 https://askiiart.net/blog/300.html diff --git a/sitemap.xml b/sitemap.xml index 40904f9..cf21e4e 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -2,6 +2,8 @@ https://askiiart.net/blog/ https://askiiart.net/blog/300.html https://askiiart.net/blog/another-new-pgp-key.html +https://askiiart.net/blog/elitebook-g1q/ +https://askiiart.net/blog/elitebook-g1q/the-arm-saga-part-0.html https://askiiart.net/blog/foooooonts.html https://askiiart.net/blog/marlin-boot-animations.html https://askiiart.net/blog/new-pgp-key.html