dc7800_ has quit [Remote host closed the connection]
FANTOM has joined #aarch64-laptops
martiert_ has joined #aarch64-laptops
martiert has quit [Ping timeout: 480 seconds]
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Ping timeout: 480 seconds]
tobhe has joined #aarch64-laptops
tobhe_ has quit [Ping timeout: 480 seconds]
dc7800 has joined #aarch64-laptops
dc7800_ has quit [Read error: Connection reset by peer]
<notHorseface_>
I will use arch linux arm, although there is two files, Image and also Image.gz ...
<notHorseface_>
does Image is a usual kernel and then Image.gz is a boot stubbed one or whatever, what does this mean?
<notHorseface_>
does the compressed one (gz) contain the initrd and also the device trees?
alpernebbi has quit [Ping timeout: 480 seconds]
<abby>
they're both just the kernel
alpernebbi has joined #aarch64-laptops
hexdump0815 has joined #aarch64-laptops
dc7800 has quit [Read error: Connection reset by peer]
dc7800 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Remote host closed the connection]
dc7800 has joined #aarch64-laptops
dc7800_ has quit [Read error: Connection reset by peer]
dc7800 has quit [Read error: Connection reset by peer]
dc7800 has joined #aarch64-laptops
FANTOM has quit [Ping timeout: 480 seconds]
<notHorseface_>
I see...
<notHorseface_>
which one should I enter into the systemd boot arch.conf file?
<notHorseface_>
the Image or the Image.gz ..?
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Read error: Connection reset by peer]
FANTOM has joined #aarch64-laptops
dc7800 has joined #aarch64-laptops
dc7800_ has quit [Read error: Connection reset by peer]
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Read error: Connection reset by peer]
<notHorseface_>
I tried the Image.gz and it then says unsupported.
<notHorseface_>
so I am going to use the Image file, however when I boot it, it just flashes on the screen with a bunch of penguins along the top and some text below it, and then the screen turns off and that is it.
<notHorseface_>
this is what I have got in my arch.conf ...
<notHorseface_>
but now it is stuck on start job running for /dev/by-uuid/<and the uuid I put into it>...
<notHorseface_>
so it cannot find the root.
<notHorseface_>
root volume
<notHorseface_>
what should I do?
<notHorseface_>
start job is running for /dev/disk/byuuid/<uuid> ...
<notHorseface_>
it just hangs on this.
<JensGlathe[m]>
Well its getting somewhere. I have looked, my additional start options (aside from clk_ignore_unused which is not needed on my newer kernels) are these: pd_ignore_unused cma=192M efi=noruntime id_aa64mmfr0.ecv=1
<notHorseface_>
okay thank you...
<JensGlathe[m]>
I don't do arch, btw, what kernel are you boting
<JensGlathe[m]>
Only announcing that there is no efi service to be used (or something). It prevents some hiccup on shutdown iirc
<notHorseface_>
but it is with finding the root which is the issue as it is stuck on that 'start job running for /dev/disk/by-uuid/xxxxx-xxx-xxx-xxxxx' etc...
<notHorseface_>
oh I see.
<JensGlathe[m]>
If it can't find the root device you should see other error messages. Like: unable to mount root device and a list of devices it has tried
<JensGlathe[m]>
That would be the Hamoa variant. Should boot with the "Try or install Ubuntu" default boot entry. If it doesn't, well... how did you write the ISO?
<notHorseface_>
maybe I will redownloadit...
<notHorseface_>
but I want to use arch on it, :-
<notHorseface_>
:-(
<notHorseface_>
I wrote it using dd...
<notHorseface_>
btw
<notHorseface_>
dd if=the iso of=the disk status=progress ...
<JensGlathe[m]>
Let's verify if it works first. Okay, dd should do. I'm out with arch, though
<notHorseface_>
it works using openbsd, I have installed that onto it.
<notHorseface_>
that works fine...
<notHorseface_>
I will redownload the ubuntu image.
<notHorseface_>
I am writing it now.
<notHorseface_>
that one doesn't even boot...
<notHorseface_>
:-/
jhovold has joined #aarch64-laptops
pbrobinson has joined #aarch64-laptops
<notHorseface_>
itdoesn't come up with the bootloader or any thing, JensGlathe[m]...
<notHorseface_>
:-/
enyalios_ has joined #aarch64-laptops
enyalios has quit [Ping timeout: 480 seconds]
<deathmist>
notHorseface_: tried just regular Ubuntu ISO? it also integrates stubble so dtb (which is in mainline too) should just load there already. also run "sync" command afterward to be sure it's done in case that was caused by partial write when unplugged
<notHorseface_>
Isee...
<notHorseface_>
so after I dd it, i run sync?
<deathmist>
yes, there's other ways too like safe removal option in DEs but the command should account for everything. when it finishes all data should actually be written on the USB
<notHorseface_>
okay cool.
<notHorseface_>
thanks
dc7800 has joined #aarch64-laptops
dc7800_ has quit [Ping timeout: 480 seconds]
<notHorseface_>
I can only find the ubuntu lts version's iso on their website, is this it?
<notHorseface_>
deathmist
<deathmist>
26.04 arm64 one is plenty fresh still, should be good enough to at least test it boots and bootstrap something else too ig as you wihs
<deathmist>
s/wihs/wish/
<notHorseface_>
yes it booted using that!
<notHorseface_>
haha
<notHorseface_>
but the battery isn't detected...
<deathmist>
welcome to the fun world of qualcomm firmware, this is why you should have windows partition to pull them from :)
<notHorseface_>
lol I see...
<deathmist>
or worst case there's other options too. would be rather nice if ADSP lite attach stuff was mainlined though so you could at least get battery stats...
dc7800_ has quit [Read error: Connection reset by peer]
dc7800 has joined #aarch64-laptops
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Remote host closed the connection]
<tobhe[m]>
deathmist: that one is still missing in stubble/dtbloader I think. I'd appreciate if you could share the hwids once you have a booting Linux 🙂
<deathmist>
yea ofc
<deathmist>
hopefully they resolved only one USB4 port being properly functional, may return it just based on that if not. haven't heard back from people on A16 even if that has the same problem
dc7800_ has quit [Remote host closed the connection]
<notHorseface_>
this is more important right now, although I will try that later.
<clover[m]>
You might have blown away windows too soon. You need some of the firmware from the windows partition for some things, depending on your device
<notHorseface_>
hmm...
<deathmist>
notHorseface_: for GPU you'd deal with the firmware I already linked before. if it doesn't force-rebuild new initramfs you may have to do that yourself too to include some bits there too (and confirm e.g. gen70500_sqe.fw is present afterward)
<notHorseface_>
those files, what do I do with them..?
<deathmist>
check the other link for packaging, or releases for prebuilt without involving makepkg etc
<notHorseface_>
okay
<deathmist>
hm ig for mkinitcpio you'd also want something like https://github.com/anonymix007/x1e-alarm/blob/master/linux-x1e/mkinitcpio.conf.d-x1e.conf which was part of that custom kernel package (now outdated v6.16), can just put it in /etc/mkinitcpio.conf.d/x1e.conf or whatever. you should have fw under /usr/lib/firmware/qcom/x1e80100/hp/omnibook-x14/
<notHorseface_>
oh I see...
<clover[m]>
What's the license on that windows firmware anyway
<notHorseface_>
and amend my mkinitcpio.conf or whatever however and it should work?
<notHorseface_>
alright so I have downloaded those files, I will place them into that path and see what happens...
<notHorseface_>
lol
<anthony25>
you might now want to have the firmware in initramfs
<anthony25>
*not
<anthony25>
it depends on your setup, but if you have dmcrypt, it can introduce some timeouts with wifi or the battery status, because it starts to init things in initramfs that are only fully loaded after you decrypt your disk (if I oversimplify things)
<notHorseface_>
I do not have encryption..
<anthony25>
so no need to have your firmware in initramfs, just have them in /lib/firmware
<notHorseface_>
so then I just place them ALL into that path, and then reboot?
<anthony25>
yes
<notHorseface_>
yay okay one moment...
<notHorseface_>
thanks!
<anthony25>
you don't need all of them, but at least you have it, that's what you normally extract from windows using the scripts shipped in ubuntu and maybe other distro
<notHorseface_>
oh I see.
<notHorseface_>
rebooting now.
<notHorseface_>
:-D
<deathmist>
ig gpu fw in initramfs is pretty useless too after some dtb changes in maybe 7.0 broke even internal display output for fde unlock
<anthony25>
hmm that was a bit different, iirc, but I think this is fixed in 7.2?
<anthony25>
I can't find the patch, but there was something incorrectly set before you load the firmware, resulting in a black screen
<notHorseface_>
yay my gpu works!
<notHorseface_>
hah
<anthony25>
nice!
<notHorseface_>
haah thanks!
<notHorseface_>
:-D
<notHorseface_>
although the sound doesn't..
<notHorseface_>
but this didn't work before either..
<notHorseface_>
lol
<deathmist>
that's another beast, not sure it's still fully safe to enable either as things stand
<anthony25>
nope :D
<notHorseface_>
LOL
<deathmist>
was anything done about that on X2 either or will we get more blown speakers while we wait some more years before qcom has speaker protection fully upstream?
<anthony25>
I mean, if you know why it doesn't work, it's better to dig into it so that you don't happen rebooting one day and full blast your speakers
<anthony25>
as they might go boom
<anthony25>
did you delete the -tplg.bin file in /lib/firmware/qcom/x1e80100/hp/omnibook-x14?
<deathmist>
audio topology is one of the files you'll need for working audio. the other stuff is in devicetree (appears to be setup) and https://github.com/alsa-project/alsa-ucm-conf
<deathmist>
notHorseface_: soooo surely your userspace is setup correctly with pipewire et all? you'd need to figure out what exactly is missing since everything from an outside view says it should work
<deathmist>
could be some random kernel config toggle too
dc7800_ has quit [Ping timeout: 480 seconds]
<deathmist>
also probably keep volume low even if kernel side driver has some kinda limit since v7.1
<anthony25>
notHorseface_: no, you shouldn't delete it, if you did delete it then it could have explained why the audio didn't work