From 84de74b2e66179ea2c8199908f91b2d7e134f4ed Mon Sep 17 00:00:00 2001 From: askiiart Date: Fri, 23 May 2025 11:37:48 -0500 Subject: [PATCH] okay minor correction/improvement (arm saga 0) --- blog/elitebook-g1q/the-arm-saga-part-0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/elitebook-g1q/the-arm-saga-part-0.md b/blog/elitebook-g1q/the-arm-saga-part-0.md index 3eac097..cad99d4 100644 --- a/blog/elitebook-g1q/the-arm-saga-part-0.md +++ b/blog/elitebook-g1q/the-arm-saga-part-0.md @@ -8,7 +8,7 @@ ARM laptops are different from x86 ones (duh), rather than the core system being ## Ubuntu Concept -Ubuntu has a concept image available [here](https://discourse.ubuntu.com/t/ubuntu-24-10-concept-snapdragon-x-elite/48800) that supports the Elitebook G1q's sister laptop, the Omnibook X 14. When I tried it on my laptop, I had to force it to use the Omnibook X 14's device tree, which matches up with what was reported [here](https://discourse.ubuntu.com/t/ubuntu-24-10-concept-snapdragon-x-elite/48800/573). Changing the grub argument from `$dtb` to `devicetree /casper/dtbs/x1e80100-hp-omnibook-x14.dtb`[^1] (which I found by just mounting the iso) worked to get it booted. However, it would throws a bunch of weird errors and try to netboot, then after going through all that, and waiting several minutes for the DHCP fail enough times (it has no networking at all), would drop me into a busybox session? So that's definitely some improvement over nothing, and an alternate way to do stuff if needed, but not ideal. +Ubuntu has a concept image available [here](https://discourse.ubuntu.com/t/ubuntu-24-10-concept-snapdragon-x-elite/48800) that supports the Elitebook G1q's sister laptop, the Omnibook X 14. When I tried it on my laptop, I had to force it to use the Omnibook X 14's device tree, which matches up with what was reported [here](https://discourse.ubuntu.com/t/ubuntu-24-10-concept-snapdragon-x-elite/48800/573). Changing the grub argument from `$dtb` to `devicetree /casper/dtbs/x1e80100-hp-omnibook-x14.dtb`[^1] (which I found by just mounting the iso) worked to get it booted. However, it would throws a bunch of weird errors and try to netboot, then after going through all that, and waiting several minutes for the DHCP fail enough times (it has no networking at all), would drop me into an initramfs busybox session? So that's definitely some improvement over nothing, and an alternate way to do stuff if needed, but not ideal. And I couldn't find a decent way to work this in, but: it also behaved a bit strangely, both the keyboard and a USB keyboard wouldn't be recognized in Grub ~50% of the time, not sure why. I *think* they would have worked once Ubuntu was actually started, but given Grub wouldn't auto-boot, I couldn't test this.