robclark changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Chrome OS Trogdor Devices - Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630 - Lenovo ThinkPad X13s - and various other snapdragon laptops) - https://oftc.irclog.whitequark.org/aarch64-laptops
baozich has joined #aarch64-laptops
KREYREN_oftc has quit [Remote host closed the connection]
KREYREN_oftc has joined #aarch64-laptops
baozich1 has joined #aarch64-laptops
baozich has quit [Ping timeout: 480 seconds]
baozich1 has quit [Ping timeout: 480 seconds]
KREYREN_oftc has quit [Remote host closed the connection]
<enyalios>
HdkR: FEXRootFSFetcher cant find unsquashfs, but its installed
<enyalios>
its in my path `% which unsquashfs` returns `/usr/bin/unsquashfs`
<enyalios>
i dont think this will actually help me though, since i run gentoo and it doesnt look like gentoo is one of distros with a provided image
baozich has joined #aarch64-laptops
KREYREN_oftc has joined #aarch64-laptops
<enyalios>
hmm i just grabbed an ubuntu rootfs to see if that would work
<enyalios>
steam sort of installed, but them an error about steamwebhelper not responding
<enyalios>
i feel like others were having this same issue so im checking the history
<enyalios>
i did remove my ~/.local/share/Steam directory and had steam redownload everything just to make sure i didnt have something old and broken in there
<enyalios>
$HOME/.steam/steam/logs/steamwebhelper.log only has: steamwebhelper.sh[26792]: Starting steamwebhelper under bootstrap sniper steam runtime at /home/enyalios/.local/share/Steam/ubuntu12_64/steam-runtime-sniper
KREYREN_oftc has quit [Remote host closed the connection]
KREYREN_oftc has joined #aarch64-laptops
KREYREN_oftc has quit [Remote host closed the connection]
KREYREN_oftc has joined #aarch64-laptops
possiblemeatball has quit [Ping timeout: 480 seconds]
Evaia631011 has joined #aarch64-laptops
altacus_ has quit [Remote host closed the connection]
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
baozich1 has joined #aarch64-laptops
baozich has quit [Remote host closed the connection]
baozich1 is now known as baozich
<travmurav[m]>
robclark: I think type-c is managed in adsp magic, near the charging, so probably can't switch the mux to alt mode without adsp either?
jglathe_ has joined #aarch64-laptops
jglathe_ has quit []
<jglathe_x13s>
no you can't without adsp, but mux is getting odd calls to switch to altmode even when there's an USB hub on it - mux switches, but hwardware doesn't care ^^
<jglathe_x13s>
fortunately, because my kb is on this hub
<HdkR>
https://wiki.fex-emu.com/index.php/Development:Setting_up_RootFS We have a small guide on it. It's basically setting up a chroot, installing everything you need, moving some files/folders, and putting it in $HOME/.fex-emu/RootFS/ then configuring $HOME/.fex-emu/Config.json to point to that folder
<enyalios>
there is a script to merge usr on gentoo
<enyalios>
and it looks like ill have to do that soon anyways because its recommended going forward
<HdkR>
hah, I guess that's a good thing :D
<enyalios>
yeah, seems cleaner that way anyways
f_ has joined #aarch64-laptops
possiblemeatball has joined #aarch64-laptops
KREYREN_oftc has joined #aarch64-laptops
mcbridematt has quit [Read error: Connection reset by peer]
mcbridematt has joined #aarch64-laptops
Caterpillar has joined #aarch64-laptops
Caterpillar has quit [Quit: Konversation terminated!]
iivanov_ has quit [Quit: Leaving...]
wiley[m] has joined #aarch64-laptops
<wiley[m]>
clover: are you the fellow behind the ironrobin x13s stuffs on Github and if so, what happened with that 6.8 upgrade/downgrade?
<wiley[m]>
I'm noticing that the current 6.7 kernel doesn't play nice with bluetooth earbuds and thinking I should probably update before any other troubleshooting
<wiley[m]>
tried building 6.9-rc4 from jhovold's WIP branch last night but the result wouldn't boot
<jhovold>
I used to have a workaround which meant that you did not have to specify 'arm64.nopauth'
<jhovold>
that would now prevent boot also with the wip branches if you leave it out
<wiley[m]>
awesome, that's probably exactly the issue
<wiley[m]>
I have anything else
<wiley[m]>
thanks!
<wiley[m]>
* I have everything else
<clover[m]>
I haven't updated the ironrobin repo to 6.8 because I am still not able to boot it with encrypted rootfs using the laptop defconfig
KREYREN_oftc has quit [Remote host closed the connection]
KREYREN_oftc has joined #aarch64-laptops
<\[m]>
I thought you figured it was f2fs related, or what's the name
cyrinux3 has quit []
<\[m]>
wtf debian caved to /usr, I missed that
cyrinux3 has joined #aarch64-laptops
<\[m]>
so redhat won hahhaha
<\[m]>
installing asahi Linux turned out to be feasy but no shortcut to maximise a window since you have no page up / down and I already lost my appetite
KREYREN_oftc has quit [Write error: connection closed]
<wiley[m]>
<jhovold> "that would now prevent boot also..." <- Bleah, now it boots, fails to mount root, drops to a recovery prompt, then the screen turns off after a few seconds 😑
<jhovold>
wiley[m]: sounds like you're missing a module in your initramfs
<jhovold>
I've listed what you need with johan_defconfig here:
<steev>
\[m]: fn+arrow keys are pageup/down in macos, maybe the same in linux?
<KieranBingham[m]>
I'm trying to boot the x13s with the latest ubuntu noble iso, - I update boot parameters in grub (clk_ingore_unused pd_ignore_unused) are already set, so I add - arm64.nopauth (then removed quiet / splash). But it looks like it goes into a cycle of usb resets maybe? The devicetree is /casper/sc8280xp-lenovo-thinkpad-x13s.dtb so I presume that's being loaded from the ISO ... Is there any thing obvious that I need to do just to
<KieranBingham[m]>
get a first boot in Linux on this ? There seems to be a lot of outdated information on various blogs/pages now ... I'm no longer sure what the correct steps are to follow. - https://openwebcraft.com/linux-on-thinkpad-x13s-gen-1/ reads like I should expect to just be able to boot the noble.iso from a USB stick directly ....
<KieranBingham[m]>
aha - To boot from USB, modprobe.blacklist=qcom_q6v5_pas must be added to the boot arguments. This keeps the USB from being reset and the storage device from being renamed mid-boot.
<KieranBingham[m]>
nope. Even with taht I hit the cyclic resets ;-(
<KieranBingham[m]>
I've just given up on ubuntu noble and switched to debian netinstall indeed. Making progress with the text install ... worried what will happen when it needs 'network' ;-)
<Jasper[m]>
Ubuntu still has a separate "x13s" iso iirc
<KieranBingham[m]>
I was using the ubuntu x13s iso ... that's where my difficulties were I think ;-)
<Jasper[m]>
Aha! Interesting that didn't work then
<Jasper[m]>
It did for me last time I tried
<KieranBingham[m]>
Perils of a daily image I guess.
<Jasper[m]>
But the current qa site doesn't list the separate ones anymore
<KieranBingham[m]>
Seemed more successful but I don't seem to be getting into a GUI yet. Grub is installed, and offers debian+windows, and debian already has the arm64.nopauth set .... but ... even removing 'quiet' - I end up with a black screen and not much in the way of a system. So much for my dreams of getting camera tested and merged tonight :-(
<Jasper[m]>
KieranBingham[m]: Are clk_ignore_unused and pd_ignore_unused also added?
<KieranBingham[m]>
Oh good call. I didn't check that.
<KieranBingham[m]>
even with those - I get screen blanked after some boot logs. I wish I had a serial console ;-)
<jenneron[m]>
tldr: you need remoteproc modules and firmware in initramfs
<jenneron[m]>
but check that comment, make sure it is the problem you're hitting
<jenneron[m]>
USB reset should happen only when loading ADSP firmware
<KieranBingham[m]>
jenneron: Aha, that's probably something for the Ubuntu builds to handle. The reset I was hitting then was while trying to boot their x13s specific iso. The resets scroll too fast for me to see what the potential cause was though ...
<jenneron[m]>
ah, maybe something else
<jenneron[m]>
i would expect just I/O filesystem errors for this issue
<jenneron[m]>
so if your rootfs has adsp firmware and you're booting from usb then you need it in initramfs
<KieranBingham[m]>
I haven't even had a booting system yet to have a rootfs. Well - the debian text installer ran, so I assume I have installed a rootfs currently, but I haven't had a successfull kernel boot into that yet. Qcom is killing me ;-) couldn't get anywhere with the HPx2 camera input as I still depend on updates to get the D-PHY handled, so switched to X13s and ... the roads are all bumpy :-)
<Jasper[m]>
KieranBingham[m]: The F40 beta image should work
<Jasper[m]>
Might need the odd kernel cmdline option, but it has everything necessary
<jenneron[m]>
KieranBingham[m]: i'm considering an x86 laptop after my journey with lenovo flex 5g, heh
<Jasper[m]>
The ISO folder will give you a liveusb like you'd expect
<KieranBingham[m]>
thanks
<Jasper[m]>
KieranBingham[m]: The "raw" images will always be bigger because it contains the entire rootfs expanded and such. Normally you'd write that to a bootdisk directly like a pi's sdcard
<Jasper[m]>
Rawhide itself is like debian testing. It used to be necessary to get a working install at all, but the changes needed are in f40
<bamse>
jenneron[m]: booted my flex 5g this weekend, but as i updated sway i got display artifacts, do you have those problems as well?
<jenneron[m]>
bamse: i tried 6.8.5, the major problems are UFS and GPU, but i don't have any artifacts
<jenneron[m]>
bamse: i also remember some major artifacts in gnome long time ago, it was either old mesa + new kernel or new mesa + old kernel, but it got resolved after upgrading everything
KREYREN_oftc has joined #aarch64-laptops
<KieranBingham[m]>
... third OS attempt of the evening and I saw a gui .... but gone. It rebooted/crashed.
jglathe_sdbox2 has quit [Ping timeout: 480 seconds]
<KieranBingham[m]>
Yes, I went through the secure boot/linux setting already and did the bitlocker reset in windows.
<bamse>
jenneron[m]: i seem to have tested next-20240412 and that worked fine...except that when i start wayland my screen is scrambled within small 16x16(?) blocks...quite likely an ubwc configuration issue
<KieranBingham[m]>
It's also an updated firmware
<jenneron[m]>
bamse: have you tried benchmarking UFS?
<Jasper[m]>
KieranBingham[m]: As in it just turned off immediately?
<bamse>
jenneron[m]: no
<KieranBingham[m]>
uefi-bios-date 2024-03-14
<bamse>
jenneron[m]: i used to use the flex 5g as my desktop, and it was fast enough for that...but i have no idea if things have regressed
<KieranBingham[m]>
Jasper[m]: rebooted during what looked like the fedora loading spinner or such yes.
<Jasper[m]>
Did you put the DTB on the esp itself?
<Jasper[m]>
of the flash drive I mean
<bamse>
jenneron[m]: i should make sure to setup some regular benchmarking on these...
<KieranBingham[m]>
I did - following the instructions to download then copy ... d:\ ... I don't know how that dtb gets used/identified yet though.
<jenneron[m]>
bamse: UFS issue doesn't happen on 6.1.x which i'm sitting on.. it regressed around 6.4-6.5
<KieranBingham[m]>
Oh wait. No - I didn't put a dtb on the flash drive after writing the iso.
<jenneron[m]>
bamse: these parameters for gnome-disks benchmark make UFS fail for me
<KieranBingham[m]>
It's on the ESP partition on the nvme
<KieranBingham[m]>
Ok - well I'll add that to the grub, as the dtb should be in the root of the ESP partition on nvme already.
KREYREN_oftc has quit [Remote host closed the connection]
<KieranBingham[m]>
"As a workaround, add a devicetree line in grub to load the DTB until it can be put in place on the ESP" ... I think this line could be a bit more explicit. I'm guessing it means add the line "devicetree /boot/efi/sc8280xp-lenovo-thinkpad-x13s.dtb" when modifying the grub boot cmnd
<Jasper[m]>
KieranBingham[m]: correct
<Jasper[m]>
or wherever it's situated from grub's perspective
KREYREN_oftc has joined #aarch64-laptops
<KieranBingham[m]>
I have no idea where it is from grubs perspective :S
<Jasper[m]>
tab completion works iirc
<KieranBingham[m]>
Give me uboot and tftpboot and an nfsroot and I'm back in my comfort zone ;-)
<Jasper[m]>
if all else fails, check where the kernel image is, place it next to it
<jglathe_x13s>
devicetree /boot/dtb-6.8.5+
<Jasper[m]>
then copy the path that's listed for the kernel image
<jglathe_x13s>
Best is to do this with a symlink. With the same name as the kernel, in my case vmlinuz-6.8.5+
<jglathe_x13s>
then even update-grub works fine
<Jasper[m]>
symlink doesn't work on fat32 partitions afaik
<Jasper[m]>
Or at least that's the issue I ran into
<jglathe_x13s>
then you know the name of the dtb file :)
<KieranBingham[m]>
Of course the iso is readonly even on the usb stick ;-) I hope I can remount that.
<KieranBingham[m]>
but it's ISO9660 .... I'm not sure that's live writable?
<Jasper[m]>
You mean already on the stick?
<jglathe_x13s>
it isnt, pretty sure its not
<KieranBingham[m]>
Ok - so ... backtracking. I have a bootable Fedora ISO written to a USB stick which is ISO9660 format. And I need to get the dtb on to that ... so I can manaully specifiy it ...
<KieranBingham[m]>
unless ... I can mount the nvme ESP from grub ?
<Jasper[m]>
KieranBingham[m]: How did you get the iso on the stick?
<Jasper[m]>
dd?
<KieranBingham[m]>
dd yes
<KieranBingham[m]>
dd if=....iso of=/dev/sda
<KieranBingham[m]>
(from this laptop)
<Jasper[m]>
Are you sure that iso thing is the only partition?
<KieranBingham[m]>
Yes. I wrote it to /dev/sda
<KieranBingham[m]>
Isn't that normal for iso images ? I assume there is space unused after the iso - but there's no partition table
<Jasper[m]>
KieranBingham[m]: I mean the ISO9660 partition itself
<jglathe_x13s>
Te Ubuntu noble daily build (just downloading should be bootable with x13s ootb
<Jasper[m]>
KieranBingham[m]: Yes, but I'm pretty sure making an image bootable requires an esp
<Jasper[m]>
Anyways, can you check what ls /dev/sda* returns
<Jasper[m]>
Assuming that's still the letter
<KieranBingham[m]>
There's only /dev/sda
<KieranBingham[m]>
That's the full iso written to the entire block device of the usb stick.
<KieranBingham[m]>
(CD's don't have partition tables)
KREYREN_oftc has quit [Remote host closed the connection]
<KieranBingham[m]>
Just as per the debian install instructions : "$ sudo dd if=debian-testing-arm64-netinst.iso of=/dev/sdX"
KREYREN_oftc has joined #aarch64-laptops
<Jasper[m]>
KieranBingham[m]: Issue is that I have gotten valid partitions out of these images, it might just be dd doing its job too well :D
<KieranBingham[m]>
I think dd did exactly as I told it to ;-)
<Jasper[m]>
Alternative would be using gnome-disk-utility
<Jasper[m]>
Nice and small, shouldn't pull in too many dependencies
<Jasper[m]>
Otherwise Fedora Media Writer exists
<Jasper[m]>
Could also just create a single fat32 partition marked as esp and extract the iso
<Jasper[m]>
That's probably best
<bamse>
jenneron[m]: okay, well i've been unable to reliably boot a clean upstream build...so i guess it's time to try to fix up these last few things now if it works
<jenneron[m]>
bamse: what exactly do you mean by "if it works"?
<KieranBingham[m]>
Jasper: How do I mark a FAT32 partition as an ESP ?
<KieranBingham[m]>
Oh well, the ISO is now simply extracted into the USB stick as a FAT32, which means it's now writable and I can add the dtb. I'll see if it boots.
<KieranBingham[m]>
I see. So it's a specific flag that needs to be set.
<Jasper[m]>
Yes, can do that with fdisk
<bamse>
jenneron[m]: "...now that it works"
jglathe_x13s has quit [Remote host closed the connection]
jglathe_x13s has joined #aarch64-laptops
<KieranBingham[m]>
Ok - new partitions. esp flags set... Re-extracted, dtb added. Boots to grub \o/ ... time to change kernel flags ... add device tree ... and ....
<jglathe_x13s>
Hmm Ubuntu 24.04 boots ootb, but doesnt come up. Not yet
<KieranBingham[m]>
fedora logo + spinner .... screen is still on ....
<KieranBingham[m]>
screen is black ....
<Jasper[m]>
KieranBingham[m]: No cursor? No activity LED on the drive?
<KieranBingham[m]>
nothing.
<KieranBingham[m]>
Though I don't see an activity light on this drive so I don't think that helps much.
KREYREN_oftc has quit [Remote host closed the connection]
<KieranBingham[m]>
Hrm. That cycle I omitted the "modprobe.blacklist=qcom_q6v5_pas" option. Retrying with that.
KREYREN_oftc has joined #aarch64-laptops
<Jasper[m]>
KieranBingham[m]: also add rd.driver.blacklist=msm
<KieranBingham[m]>
I had that one. It's mentioned clearly in the top of https://fedoraproject.org/wiki/Thinkpad_X13s ... but the qcom_q6v5 is lower and I missed it that iteration.
<Jasper[m]>
Ah alright
<KieranBingham[m]>
back to spinner ....
<KieranBingham[m]>
screen goes black ...
<KieranBingham[m]>
This is killing me :-D
<Jasper[m]>
Hahaha I understand
<Jasper[m]>
I am planning to go to bed at the moment so I won't be able to help you in a bit
<KieranBingham[m]>
don't worry - thank you for your support.
<Jasper[m]>
But it should work okay, there might be something I'm missing
<Jasper[m]>
@dgilmore any notes? (if you're here)
* dgilmore
reads back
<Jasper[m]>
Lots of stuff hahahaha
<Jasper[m]>
Short of it is F40 iso, DTB on the ESP (or at the very least put into grub config), linux boot option is on, all the cmdline options on the wiki are filled in
<Jasper[m]>
@[Kieran Bingham] Is that dtb you're using from the iso itself or is it the one you put on the nvme drove before?
<KieranBingham[m]>
It's the one I obtained from the debian instructions. Honestly - I've pulled instructions from debian, fedora, arch, and (well, not ubuntu) in this process... there's not a single clear source of truth :-(
<Jasper[m]>
Otherwise I'd recommend getting one from the iso or Fedora's packages (lemme check which one it is)
<KieranBingham[m]>
I ... don't see a dtb in the iso ?
<KieranBingham[m]>
What did I miss.
<Jasper[m]>
KieranBingham[m]: It's in either some subfolder on in an rpm somewhere, one sec
<KieranBingham[m]>
The extracted ISO has very few files. None of them are a dtb.
<dgilmore>
I have an issue currently with my x13s where while grub, the kernel, and initrd are loaded from the NVMe drive, it's not showing up in the running system
<dgilmore>
I wonder if that's the same here
<KieranBingham[m]>
dgilmore: How do you mean "its not showing up in the running system"?
<dgilmore>
I do have a bug opened to install the dtb files in the livecds so they can be loaded from there manually
<KieranBingham[m]>
That would help at least in part I guess.
<dgilmore>
KieranBingham[m]: it does not show up on the PCIe bus. So I have no storage
<KieranBingham[m]>
when you've booted something ?
<dgilmore>
Yes
<KieranBingham[m]>
I'm booting from USB-C currently.
<KieranBingham[m]>
Lets see if I get more info by removing rhgb
<Jasper[m]>
Jasper[m]: Okay yeah I can't find it for some reason, don't have a running system infront of me to find out either :/
<Jasper[m]>
Sorry for that
<KieranBingham[m]>
(such a pain having to retype /add all the kernel args each boot)
<Jasper[m]>
KieranBingham[m]: You can change the config on a different pc
<Jasper[m]>
It's a file on the drive that's less hidden
<KieranBingham[m]>
aha yes - I think I can see that file. /EFI/BOOT/grub.cfg
<KieranBingham[m]>
Alright - now that might be progress. Removing rhgb before the screen goes black I see messages about remoteproc. Perhaps that does indicate I need an updated initramfs /initrd on there.
<KieranBingham[m]>
I think I've gone full circle ;-)
<dgilmore>
Booting from USB works okay. You could boot a disk image. Last I tested the live is booted fine. So long as the dtb file is on the NVMe drive and you have Linux boot selected
<KieranBingham[m]>
dgilmore: That's what I'm doing isn't it? Or are you distinguishing the disk image from the iso image ?
<KieranBingham[m]>
Last output before the screen goes black
<dgilmore>
KieranBingham[m]: you don't. The bios loads it and passes it on
<KieranBingham[m]>
Ok - so all the iteration I did to get the dtb on the usb stick was in vain anyway as the same dtb should already have been loaded and provided ;-)
<KieranBingham[m]>
well, midnight calls time. Maybe tomorrow will bring some new light ;-)
<KieranBingham[m]>
Thanks for your support tonight