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
<erebion[m]> Trying it out right now, doed not seems to be. X and Wayland both do not want to start, but maybe I'm missing something.
<erebion[m]> Desktop works during install, so theee should be a way to fix it.
<erebion[m]> `qcom/a690_gmu.bin` is missing, so I'm limited to the shell and no GUI.
<erebion[m]> Not sure where Id get that.
<erebion[m]> Also no audio. Wifi has speed issues.
<erebion[m]> But so far I have not noticed anything else.
<erebion[m]> If graphics and audio can be fixed I'd be able to daily drive it. I can work around the slow wifi, cable with dongle, USB tethering, digital detox... So many ways!
<erebion[m]> I could even live without audio as long as Bluetooth works, as I barely use the built in sound card. But have not tested yet.
<konradybcio> check /lib/firmware/qcom, there's a660_gmu.bin
<konradybcio> symlink it
<erebion[m]> From where to where?
<erebion[m]> From there to what path?
<clover[m]> Sounds like you need some firmware. Check out github.com/ironrobin the x13s alarm repo and check out the x13s-firmware package
<bamse> erebion[m]: in /lib/firmware/qcom make a690_gmu.bin a symlink to a660_gmu.bin
<bamse> erebion[m]: the rest of the firmware should be in the linux-firmware-qcom package
strongtz[m] has joined #aarch64-laptops
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
mcbridematt has joined #aarch64-laptops
echanude_ has joined #aarch64-laptops
echanude has quit [Ping timeout: 480 seconds]
Lucanis has joined #aarch64-laptops
Lucanis0 has quit [Ping timeout: 480 seconds]
iivanov has joined #aarch64-laptops
iivanov has left #aarch64-laptops [#aarch64-laptops]
sally_ has quit [Remote host closed the connection]
<erebion[m]> @bamse Thanks. I cannot find linux-firmware-qcom anywhere, though.
<juergh> erebion[m], Yes that Ubuntu image is official, sort of ;-) I'm the kernel maintainer for it. In the process of updating it all to Mantic which should support the machine officially. I need to upgrade linux-firmware for Lunar.
<ema> erebion[m]: as far as I understand, for the x13s you need a 6.4 kernel (which is currently in Debian Sid and Testing). However the kernels currently shipped by Debian miss a few Kconfigs, I'll let you know if/when I find out which ones
<erebion[m]> <juergh> "erebion 🏳️‍🌈♾, Yes that Ubuntu..." <- Just tried upgrading to Mantis, that wasn't yet a good idea it seems. :)
<konradybcio> ive been running the ubu concept but some recent update messed with things (e.g. the gmu firmware went missing)..
<konradybcio> nothing that can't be worked around though
<erebion[m]> Now with Mantis I only get a blank screen booting, huh
<erebion[m]> yup this
<konradybcio> i think i was still on lunar
<erebion[m]> @ema Yes, please do let me know, that'd be very helpful :)
juergh1 has joined #aarch64-laptops
<juergh1> The fw package from that special PPA got replaced by upgrades from the archive.
<juergh1> Which don't have the x13s blobs
<erebion[m]> Some people at work claim that the X13s is completely unusuble, so I want to show them that it works, lol
<erebion[m]> I can still boot to graphics on 6.2.0-1002, so at least that works for now
<erebion[m]> What's the state of audio?
<erebion[m]> If all the changes land in the next release and audio works, I can tell work I want to try out working with that one to see how far I get. :D
<juergh1> used to work on lunar. but alsa-ucm-conf got borked. working on it as well...
<erebion[m]> Also, is Ubuntu doing the changes and Debian taking them? Or what is the reason I cannot find anything on the state of Debian on the Debian wiki?
<erebion[m]> I'd expect Debian to be first
<juergh1> no. this is all Ubuntu only.
<erebion[m]> But.. It will all eventually get picked up by Debian, right?
<ema> generally speaking Debian waits for upstream (eg: the linux kernel) to include the changes
<juergh1> and firmware as well
<erebion[m]> I'd report an error, but the error reporting daemon does not start, lol
iivanov has joined #aarch64-laptops
iivanov has left #aarch64-laptops [#aarch64-laptops]
<erebion[m]> Can I somehow get the graphics binaries back on Mantis?
<erebion[m]> I suppose activating the Lunar PPA and installing linux-firmware again from there is a dumb idea?
<juergh1> what version of linux-firmware do you have installed?
<erebion[m]> 20230731.git07f05b0c-0ubuntu1+x13s+202308091026~ubuntu23.10.1 from the Concept PPA
<erebion[m]> Or could I just switch to the Lunar PPA, install Linux Firmware,
<erebion[m]> copy the files
<erebion[m]> And upgrade again
<juergh1> That package does have the GPU fw. I'm running it right now.
<erebion[m]> And then place them im /lib/firmware/qcom again?
<erebion[m]> huh
<erebion[m]> [ 2111.792] (EE) unw_get_proc_info failed: no unwind info found [-10]
<erebion[m]> X.org segfaults:
<erebion[m]> For a moment I assumed it's missing firmware again as it looked the same
<erebion[m]> Wayland also crashes immediately
<agl7> erebion[m]: Have you restarted the x13s new. Only then the fw is loaded!
<erebion[m]> I rebooted after the upgrade, yes
<juergh1> Can you pastebin the kernel log?
<erebion[m]> Error plus some messages before and after
laine has quit [Ping timeout: 480 seconds]
<erebion[m]> Added a 2nd error that I get when running startx and which is different to what I get when bootin
<erebion[m]> g
<juergh1> What kernel are you running?
svarbanov has quit [Remote host closed the connection]
<erebion[m]> 6.2.0-1002-laptop on Mantis
<erebion[m]> The newer ones get stuck on a blank screen
svarbanov has joined #aarch64-laptops
laine has joined #aarch64-laptops
laine_ has joined #aarch64-laptops
laine has quit [Ping timeout: 480 seconds]
laine__ has joined #aarch64-laptops
agl7 has quit [Remote host closed the connection]
agl7 has joined #aarch64-laptops
laine_ has quit [Ping timeout: 480 seconds]
laine__ has quit [Ping timeout: 480 seconds]
<juergh> erebion[m], Can you upgrade again (apt update && apt upgrade)? That should pull in the 6.5 kernel. Make sure the initrd is updated or run 'update-initramfs -u -k 6.5.0-1001-laptop' explicitly to be sure.
<erebion[m]> It is installed, but does not boot. I just get a blank screen, few seconds after pressing enter in grub.
<agl7> erebion[m]: Boot the install system and make a fsck on the root partition!
<agl7> I have also this error. There was errors in the filesystem.
<erebion[m]> I could just do `touch /forcefsck && reboot`, right?
<erebion[m]> Wow, I seem to be using very outdated info
<erebion[m]> I'll just use fsck.mode=force
<juergh> erebion[m], update the initrd. does it boot just no display? i.e. can you ssh to it after a bit?
<erebion[m]> No, I cannot unlock the disk so it does not continue to boot
<erebion[m]> Actually, let me just check whether I can unlock without seeing anything
<agl7> erebion[m]: I had booted the install system from an USB stick and then I made an fsck. When you want to make this at boot time from the booted kernel, that does not work.
<erebion[m]> Does not seem to be the case, cannot unlock the disk
<juergh> oh. disk encryption?
<erebion[m]> yup
<Jasper[m]> juergh: Yeah you need some modules in your initramfs for that
<juergh> yeah. I thought we shove them all in.
<erebion[m]> The 6.2.0 Kernel works, so should be included automatically
<Jasper[m]> juergh: I think they're trying to boot a newer kernel, don't know where from though
<erebion[m]> 6.50 from the repo
<erebion[m]> 6.5.0 actually
<Jasper[m]> erebion[m]: Ah, yeah then it shouldn't be different
<erebion[m]> Regenerated initrd, no noticeable effect
<erebion[m]> What I like if that the X13s knows its own layout, so I can always type in every character and not suddenly have US Layout and have to consciously think about it.
agl7 has quit [Quit: ZNC 1.8.2 - https://znc.in]
agl7 has joined #aarch64-laptops
<robclark> bamse: btw any conclusion on whether we should just change kernel to look for a660_gmu.bin?
<konradybcio> just having a "gmu.bin" should be enough..
heapify has joined #aarch64-laptops
heapify has quit [Quit: heapify]
<bamse> robclark: no conclusion there, unfortunately...i need to chase the team again...
<robclark> I've been using the a660_gmu.bin for a while.. I'm tempted just to send a patch to switch to that in the mean time, since it seems to work fine and it is better than no gmu fw
<bamse> robclark: if you say it seem to work, how about us just doing that...and then switch back if/when the team wakes up here?
<robclark> yeah, that's what I'm thinking.. I kinda suspect that even if a newer gmu fw is needed, it is just a newer a660_gmu.fw
laine has joined #aarch64-laptops
<gwolf> steev: /me is fiddling with github in order to start building from your tree -- but something quite odd is failing
<gwolf> While from the Web interface I do see quite up-to-date branches, if I clone it I see only ~6 year old work! :-\
<gwolf> (tried it from two different machines already, just to make sure)
<steev> that's odd - c630-linux-6.3.y should be the newest c630 branch i've pushed
<steev> i really do need to clean up my kernel tree there... i accidentally pushed all once and... yeah
<travmurav[m]> it probably fails to get the (mis?)named branch and only gets the default one, at least looks like that
<travmurav[m]> also is it steeve or steev?
<gwolf> Also c630-v6.3.y is reported not to ...
<gwolf> travmurav[m]: OH!
<steev> travmurav[m]: steev
<gwolf> Stupid fat fingers of mine
<steev> though, tbh, most people throw that last e at the end
<gwolf> But still -- "git clone https://github.com/steev/linux -b c630-v6.3.y throws me a "Remote branch not found" :-\
<gwolf> steev: Well, yes, but I happen to know who you are
<steev> well
<steev> it's c630-v6.3 or c630-linux-6.3.y not a mix of the two :)
<travmurav[m]> gwolf: neiter does such named branch actually exist in the repo
<steev> but yes, that's my fault for not following naming schemes :(
<steev> typically v6.x means it was an rc, and linux-X.X.y means it's based on the stable branch of that name
<gwolf> grah :-)
matalama has joined #aarch64-laptops
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
<Jasper[m]> It took me 4 tries to boot my x13s now
<Jasper[m]> It still crashes after filling in the luks password
<Jasper[m]> I am once again asking for your support in debugging this issue.
<Jasper[m]> Is there something like UEFI backed pstore or something similar?
<konradybcio> technically
<Jasper[m]> Any idea if the needed config option is already in steev's kernel or not? /sys/fs/pstore is empty currently
<konradybcio> sorry, keine idee
<Jasper[m]> Scheiße
<agl7> Hello German boys. I'am also a German boy ;-)
<konradybcio> i have a german/ic name and speak a few words but i'm very much not one :p
<clover[m]> polish, right?
<konradybcio> yep
<Jasper[m]> konradybcio: Yeah me neither
<steev> the config option likely isn't enabled, if such a thing exists in the kernel, you can always grep the installed config to see though?
<clover[m]> config option for what, LUKS?
<clover[m]> "Before using cryptsetup, always make sure the dm_crypt kernel module is loaded." arch wiki
<clover[m]> its set to "m" in arch kernels
<Jasper[m]> <clover[m]> "config option for what, LUKS?" <- Nah, pstore
<Jasper[m]> So I can fetch kernel logs from last boot attempt (since it keeps crashing)
<konradybcio> realistically you can just set up pstore like we have on phones
<konradybcio> and then boot back to a working kernel+initrd that also has pstore enabled at the same addr
<erebion[m]> <konradybcio> "i have a german/ic name and..." <- Cześć!
<Jasper[m]> <konradybcio> "and then boot back to a working..." <- The kernel does boot, but only sometimes
<Jasper[m]> Which makes it weird
<Jasper[m]> So in theory (assuming the filesystem doesn't corrupt itself) I could just keep retrying and read the logs afterwards
<Jasper[m]> <konradybcio> "realistically you can just set..." <- I thought efi_pstore could work aswell.