ChanServ 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
ceezy9 has joined #aarch64-laptops
ceezy9 has quit []
ceezy9 has joined #aarch64-laptops
ceezy9 is now known as eac
<eac> anyone having any luck with the Thinkpad T14s gen6? I've got it booting with the devicetree kernel patch that's up for review, but currently debugging why the nvme ssd (and other pcie bus devices it seems) aren't being detected
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
<steev> akaWolf: you mean 6.10.2? depending on what you were on, please do check the documentation about which files you need in the initrd
<steev> what is "other kernel" though (please give version numbers)
<Molyuu[m]> <kuruczgy[m]> "Ok, then I will try to look into..." <- I also encountered this problem, you can picking up three patches about probe timeout from linux-surface as a temporary solution.
<travmurav[m]> eac: Hi! Did you manage to get T14s to boot at least from usb? Would you be able to share output of `sudo fwupdtool hwids` with me? I'm trying to collect the hwids for all woa devices for dtbloader, so we can make generic os/installer images later
<travmurav[m]> eac: otherwise you may want to look into i.e. `/sys/kernel/debug/devices_deferred` in case you're missing some kernel modules, I'd guess with modern enough kernel the main problems would be just kernel config...
<akaWolf> steev: lenovo-x13s-linux-6.10.y branch
<akaWolf> now I'm at 6.9.11 and it works fine
DJ_Mulder has joined #aarch64-laptops
<akaWolf> https://bin.akawolf.org/f/jujQr.jpg I have that errors in the log with specified new kernel
<kuruczgy[m]> <Molyuu[m]> "I also encountered this problem,..." <- Thanks, applied. It makes the error message go away, because now `msm-mdss` never tries to probe I guess because it is waiting for a supplier, which is `clock-controller@af00000`/`x1e80100-dispcc`, so that still seems like the root cause.
<kuruczgy[m]> akaWolf: akaWolf: Ooh my errors are looking very similar to this, what kernel/machine combo is this?
<kuruczgy[m]> Does someone know how I could get the kernel logs after the screen stops working? It seems that pstore is the intended kernel mechanism for this, but I am struggling to get it working.
<Molyuu[m]> kuruczgy[m]: Userspace filesysytem must working, then you can get logs in /var/log/journals if you are using systemd. If you are using openrc, once it get into default stage, you can get log at /var/log/dmesg
<Molyuu[m]> If you can get USB controller working, use UNDIS network, make sure openssh is automatically running after system booted.
<Molyuu[m]> s/filesysytem/filesystem/
<Molyuu[m]> Or if you have a working debug serial, you can also use that.
<Molyuu[m]> s/UNDIS/RNDIS/
<kuruczgy[m]> Everything is mounted as tmpfs right now, so the logs don't survive reboot. But you are right I should just try mounting /var/log to persistent storage first, not sure why I am already thinking of more complicated solutions without having tried the most straightforward one
<Molyuu[m]> How's the support status about DSI with DSC on video mode? My device is using 1:1:1 mode dsc (Profile ID 4). After applying patchset https://lore.kernel.org/linux-arm-msm/20240530-msm-drm-dsc-dsi-video-upstream-4-v6-0-2ab1d334c657@linaro.org/ , screen keeps black and I got an error dsi_err_worker: status=5 (FIFO and TIMEOUT), and after I applied https://github.com/z3ntu/linux/commit/f249b7af2f59d95225092ff251e3287eb8d4e166 and
<Molyuu[m]> https://github.com/z3ntu/linux/commit/d300c891647e501f6a7af024a1499f29ab36cf1b, screen still keeps black, and got an error dsi_err_worker: status=4 (FIFO)
<DJ_Mulder> Molyuu[m] did you get my messages? :) I'm not sure if that works on this webchat I'm using :)
<Molyuu[m]> DJ_Mulder: Oh, I see it, wait a minute.
kuruczgy has joined #aarch64-laptops
<kuruczgy[m]> Managed to get the kernel logs when I do `modprobe dispcc-x1e80100`:... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/UQgKUOoDNeshexamGHaBUCzX>)
<kuruczgy[m]> What is arm-scmi? Is it supposed to be working?
DJ_Mulder has quit [Quit: Page closed]
<akaWolf> kuruczgy[m]: 6.10.0 and x13s
<akaWolf> I guess it's bad that it can't load mmu
<kuruczgy[m]> So I added a bunch more modules to my initrd (copy-pasted all from colemickens' repo), and now on boot the screen goes black for a second... and then comes back!!
<kuruczgy[m]> So apparently some other module is needed after dispcc-x1e80100 to bring the screen back. Not sure if this is intended behavior.
<kuruczgy[m]> And now vulkaninfo also sees my gpu 🎉
<kuruczgy[m]> And now I can also re-enable udev
<eac> travmurav[m]: yep im booting from USB. I'll be playing more around with it later today so I'll let you know what I find
<steev> akaWolf: all those pending sync states tells me you're somehow missing some modules from your initramfs.
<travmurav[m]> eac: Cool! If you can get the hwids I'd also appreciate having your name/email for co-authored-by tag if you want to be credited in dtbloader. It's a bit late for me right now so I guess I will see what you find in the morning my time though :)
Lucanis has quit [Ping timeout: 480 seconds]
Lucanis has joined #aarch64-laptops
<akaWolf> steev: https://i.imgur.com/XhWXxdO.png well looks like I have all the needed modules, at least I've compared with the modules for 6.9.1 and they are the same
<akaWolf> okay, I've realized what was the problem -- bootloader used the old initramfs
<gabertron> has anybody created an iso to boot on the yoga? trying to find some base starting point that works that I can iterate from
<JensGlathe[m]> well v5 of the ubuntu image will come this week, and yoga 7 is a boot option
<JensGlathe[m]> hopefully it will boot up to the installer on x1e too
<steev> akaWolf: so with the correct initramfs it works?
colemickens has joined #aarch64-laptops
<colemickens> kuruczgy: if you have figured out the udev stuff, please let me know or send a PR.
<colemickens> or maybe it won't matter in a few weeks
<colemickens> :)
<kuruczgy[m]> <colemickens> "kuruczgy: if you have figured..." <- Right now these are my initrd modules:... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/yvZMaqCuUOKZvsomjVRMppGa>)
<kuruczgy[m]> My extra kernel params are module_blacklist=qcom_edac,qcom_q6v5_pas pd_ignore_unused clk_ignore_unused
<akaWolf> steev: yeah, it works, thanks
<kuruczgy[m]> With these, I can leave udev enabled and the system boots up
<steev> akaWolf: glad to hear :)
<kuruczgy[m]> <gabertron> "has anybody created an iso to..." <- I do plan on putting together a NixOS install iso eventually, at this point I think I have solved all the hard problems, now it's just a matter of putting the pieces together.
<kuruczgy[m]> Right now my boot setup is nixos initrd + rootfs grafted onto the debian iso
<gabertron> ah ok -- sounds good -- I managed to get my setup going with some help from HdkR -- my kernel command line had some extra stuff best I can tell causing problems -- will confirm which thing was bad
<kuruczgy[m]> colemickens: Here is my ISO image config if you want to compare: https://github.com/kuruczgy/x1e-nixos-config/
<kuruczgy[m]> I just tested again and it boots without issues. (Modulo missing firmware so no gpu, but that should be trivial to add.)