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
AladdinSane has joined #aarch64-laptops
shawnguo has joined #aarch64-laptops
Lucanis has joined #aarch64-laptops
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
alfredo has joined #aarch64-laptops
fossdd has quit [Read error: Connection reset by peer]
fossdd has joined #aarch64-laptops
martiert_ has quit [Quit: WeeChat 4.3.6]
martiert_ has joined #aarch64-laptops
jhovold has joined #aarch64-laptops
alfredo has quit [Quit: alfredo]
alfredo has joined #aarch64-laptops
Mary4 has joined #aarch64-laptops
kuruczgy_ has joined #aarch64-laptops
dubiousness_ has joined #aarch64-laptops
maz_ has joined #aarch64-laptops
maz has quit [Write error: connection closed]
Mary has quit [Read error: Connection reset by peer]
kuruczgy has quit [Read error: No route to host]
dubiousness has quit [Ping timeout: 480 seconds]
alfredo1 has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
alfredo1 is now known as alfredo
alfredo has quit [Ping timeout: 480 seconds]
enyalios has quit [Ping timeout: 480 seconds]
enyalios has joined #aarch64-laptops
Mary4 has quit []
Mary4 has joined #aarch64-laptops
Mary4 has quit []
Mary4 has joined #aarch64-laptops
Mary4 has quit []
Mary has joined #aarch64-laptops
<HdkR>
Looks like the patches for aarch64 vdso_getrandom have dropped on the mailing list. Sadly it doesn't compile here for some reason :/
alfredo has joined #aarch64-laptops
<pundir>
JensGlathe[m]: thank you for pointing it out. I didn't get the grub option screen yesterday and it booted with Windows Devkit DTB
<pundir>
I tried it again and paid attention to it and I could select and boot with Yoga Slim 7x option now
<pundir>
and it booted to UI!
alfredo has quit [Quit: alfredo]
alfredo has joined #aarch64-laptops
ema has quit [Quit: leaving]
ema has joined #aarch64-laptops
<JensGlathe[m]>
There are some things you could do after you're up on GUI. Need to add some more info to the wiki. Like, fetching the firmwares from the Windows install. Setting up /etc/initramfs-tools/modules and /etc/initramfs-tools/hooks/yoga-slim-7x-firmware for your box. Checking if all firmwares are loaded. Handling grub entries to drop all non-needed ones. Installing on the local SSD.
iivanov_ has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
alfredo has quit [Quit: alfredo]
craftyguy has quit [Remote host closed the connection]
craftyguy has joined #aarch64-laptops
iivanov_ has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
craftyguy has quit [Remote host closed the connection]
craftyguy has joined #aarch64-laptops
craftyguy has quit [Remote host closed the connection]
craftyguy has joined #aarch64-laptops
abcdw has quit [Remote host closed the connection]
kuruczgy_ has quit [Remote host closed the connection]
dubiousness_ has quit [Remote host closed the connection]
Mathew has joined #aarch64-laptops
abcdw has joined #aarch64-laptops
mcbridematt has quit [Ping timeout: 480 seconds]
kuruczgy has joined #aarch64-laptops
dubiousness has joined #aarch64-laptops
maz_ is now known as maz
mrkajetanp has joined #aarch64-laptops
eliaselias[m] has joined #aarch64-laptops
jelly has quit [Remote host closed the connection]
jelly has joined #aarch64-laptops
mrkajetanp has quit [Ping timeout: 480 seconds]
jelly has quit [Read error: Connection reset by peer]
<kuruczgy[m]>
I am getting the following crash in the panel driver, is it supposed to be not crashing? Am I perhaps supposed to use a different panel in the device tree? I thought the yoga dtb already had the right one.
<kuruczgy[m]>
Tbh. I don't really care about this particular issue because the screen works just fine, but I wonder if this could be related to the suspend issues I am having?
<kuruczgy[m]>
AFAIU suspend is supposed to be working on X1E (and it isn't for me), it just draws a bit more current than necessary due to still not everything getting powered down properly.
<robclark>
kuruczgy[m]: I think you have dtb which doesn't have my dts patch to switch over to the samsung panel driver
<steev>
that's the splat for the kernel not having any information about the panel
<kuruczgy[m]>
I am using `jhovold/wip/x1e80100-6.11-rc5`, so I should have it.
<kuruczgy[m]>
Let me also dump the relevant device tree node from sysfs, just to double check that I am not mixing up the dtbs or something...
<robclark>
yup
<robclark>
double check the the up-to-date dtb is copied over to wherever it gets loaded from
<kuruczgy[m]>
Yes the wrong device tree is loaded apparently :/
<kuruczgy[m]>
Okay then this is an issue with my setup for loading the dtb, thanks.
<robclark>
no worries, I've made this mistake before ;-)
<kuruczgy[m]>
Ok, I now I actually have the correct dtb loaded, and the splat is gone, but unfortunately the sleep issue is still present :/
<kuruczgy[m]>
Jos said that he had the same issue, so at least I am not alone
<kuruczgy[m]>
robclark: Is suspend/resume working correctly for you? E.g. the machine stays suspended, and when resuming the screen comes up without the drm "Failed to resume" error?
<robclark>
sometimes it wakes up early from suspend
<steev>
blergh, something in the asoc-fix-v6.11-rc3 seems to have broken audio on the x13s
<robclark>
I'd have to check dmesg to see if I see any "Failed to resume", but at least the screen comes back
<robclark>
so I don't think it is failing to resume
<steev>
occasionally it dies, but for the most part it works
<dgilmore>
it does not work at all here
<dgilmore>
it crashes as soon as it connects. I only managed to get the backtrace because I had not been home and was on 5g. I had suspended and the connected at home