ChanServ changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630)
<steev> bamse: ah, i think Arch does connectivity checking by default (no idea if debian does) - kali doesn't, as we're meant to be silent on the network
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
<steev> bamse: rc5 seems to be okay, minus the rcu stalls that happen around bluetooth times - https://paste.debian.net/1246082
flowriser has quit [Remote host closed the connection]
jhovold has joined #aarch64-laptops
krzk has quit [Remote host closed the connection]
matthias_bgg has joined #aarch64-laptops
krzk has joined #aarch64-laptops
vsp has joined #aarch64-laptops
matthias_bgg has quit [Ping timeout: 480 seconds]
matthias_bgg has joined #aarch64-laptops
vsp_ has joined #aarch64-laptops
vsp has quit [Ping timeout: 480 seconds]
falk689 has quit [Remote host closed the connection]
falk689 has joined #aarch64-laptops
vsp_ has quit []
matthias_bgg has quit []
jhovold has quit [Ping timeout: 480 seconds]
<steev> and the c630 - https://paste.debian.net/1246186 - also has an rcu stall, but only 1, it looks like
<qzed> steev: so you got the dp-aux thing working now?
<steev> qzed: i have display now yeah :D
<steev> well, mostly
<qzed> nice!
<steev> sometimes it takes 3-7 boots to get it
<qzed> hmm, it's somewhat random for me too but not that bad
<steev> not sure what/where the badness is, but i have 0 visibility as there is no logs
<qzed> bamse suggested some things, like building in CONFIG_DRM_PANEL_EDP
<qzed> I think those help a bit
<qzed> also the disable deferred probe timeout commit
<qzed> I'm not really sure what specifically the magic combination is, but the things I have in my config fragment seem to work mostly well
<qzed> still, like one in five boots is still bad
<steev> maybe i'll try building in edp
<steev> i have the disable deferred commit
<qzed> I think the reasoning was that the drm code probes the panel when probing some part of the drm stack, and that works more reliably if the module is already loaded
<steev> makes sense, i just need to go up the stack to see why it wants to stay =m here
<steev> qzed: but yes, the mp usb stuff also works, as i now have the webcam available :D
<qzed> awesome!
<qzed> thanks for testing!
<steev> you pretty much wrote it, i just did the stuff
<steev> now my only issue is, if i sit at the console, it works longtime, but if i go into X or wayland, it locks up pretty quick, but nothing in the logs about why
<steev> i'm wondering if it really dislikes your a680 firmwares on it
<qzed> hmm... I wonder if there's actually any difference in firmware between the flex and spx
<steev> how did you extract that? i could provide the same file, or extract mine
<qzed> ghidra
<steev> everyone using ghidra these days
<qzed> took a bit, but you can fairly quickly find the GMU stuff
<qzed> the GMU struff is fairly well structured in some block format
<qzed> and has a bunch of 0xff in series
<qzed> I think that's how I found that