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
sgerhold has quit [Remote host closed the connection]
sgerhold9 is now known as sgerhold
tobhe_ has joined #aarch64-laptops
tobhe has quit [Ping timeout: 480 seconds]
hexdump0815 has joined #aarch64-laptops
hexdump02 has quit [Ping timeout: 480 seconds]
hexdump02 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
eluks has quit [Remote host closed the connection]
eluks has joined #aarch64-laptops
<valpackett>
right, someone already saw the effect of that on oled and it did feel completely dead
SpieringsAE has joined #aarch64-laptops
<JensGlathe[m]>
My main experience trying to get the ATNA40CT01 panel in the Ideapad 5 to behave. panel-edp works, with brightness control. After suspend/resume brightness is stuck at max. atna33xc20 as driver: brightness always stuck at max. Own driver: not even a display most of the time.
<JensGlathe[m]>
Unfortunately no datasheet
matthias_bgg has joined #aarch64-laptops
pbrobinson has joined #aarch64-laptops
fantom has quit [Ping timeout: 480 seconds]
jhovold has joined #aarch64-laptops
laine_ has joined #aarch64-laptops
laine has quit [Read error: Connection reset by peer]
<lynxy>
bamse: i hadd issues with the oled display on the xps13 not coming up at all (totally black) on rc1, and i believe the fix was included in linaro's rc2- but in all honesty i've been running 6.16-rc7 because it has been the most stable for me so far
ttttrfg has joined #aarch64-laptops
ttttrfg has quit []
neobrain[m] has joined #aarch64-laptops
<neobrain[m]>
Reading the backlog about those "Couldn't power up the GPU" errors on X13s when booting at EL1 that might be fixed when booting to EL2... how does one actually do that?
<neobrain[m]>
oh seems to require a custom kernel, probably not "I have no idea what I'm doing"-land then
<Jasper[m]>
Sort of, you need some DTB changes and slbounce.
<Jasper[m]>
Or I think just dtbloader can do that aswell
<Jasper[m]>
but you lose some stuff
<neobrain[m]>
I think I'll try and see if updating to kernel rc5 helps first
martiert_ has joined #aarch64-laptops
martiert_work has quit [Ping timeout: 480 seconds]
<bamse>
lynxy: same here, and i broke firmware loading in -rc1...and the fix didn't land until -rc5... so i didn't notice until now
<neobrain[m]>
ended up downgrading to 6.15, which now fixed the GPU error and an issue with external display output I had. Previously was on 6.16.5 (not sure if that's known to have regressions or if opensuse just backported bad 6.17 patches to it)
<sgerhold>
neobrain[m]: you need 6.16.6 (or 6.16.3) to avoid the gpu error. 6.16.4 and 6.16.5 are broken
exeat has joined #aarch64-laptops
bionade24 has quit []
bionade24 has joined #aarch64-laptops
krzk has quit [Remote host closed the connection]
<neobrain[m]>
<sgerhold> "neobrain: you need 6.16.6 (or 6...." <- Ah, perfect, so a fixed kernel should be in my distro's repos soon then. Thanks!
krzk has joined #aarch64-laptops
SpieringsAE has quit [Quit: SpieringsAE]
laine has joined #aarch64-laptops
laine_ has quit [Ping timeout: 480 seconds]
matthias_bgg has quit [Ping timeout: 480 seconds]
sally has quit []
sally has joined #aarch64-laptops
sally has quit []
sally has joined #aarch64-laptops
<bamse>
neobrain[m]: yeah, i broke v6.17-rc1 and the breakage was backported to v6.16.4 before the fix made it in
<bamse>
neobrain[m]: fixed in -rc5 and making its way into stable as well...