03:03 <steev> shawnguo: what version of the lmh patches are in the laptops tree? v2 or v3?

03:08 <steev> bamse: yeah, it's looking like it's v2; let me pull in v3 and test that.... i guess

03:09 <shawnguo> steev: it's v2, and I will pick up the latest when I create 5.14 branch

03:09 <steev> shawnguo: yeah i just ran into something but i don't wanna waste thara's time if it's fixed in v3

03:09 <steev> https://bpa.st/3LTA

03:09 <bamse> steev: check if the request_irq is done in the same way?

03:10 <steev> oh good call

03:10 <bamse> steev: i.e. if it has been replaced with request_threaded_irq

03:11 <shawnguo> steev: let me know if v3 fixes it or not :)

03:12 <steev> bamse: it has not, as far as i can tell

03:13 <bamse> steev: then please let her know

03:13 <bamse> steev: thanks for testing :)

03:14 <steev> sent

03:16 <steev> i wish this xz would finish compressing, so i could reboot it

03:17 <steev> bamse: the interesting thing to me is the null pointer for slimctrl - on 5.12 that's fatal, and that c630 won't boot, but on 5.13, it hums along happily (just no audio, wifi works though)

20:10 <derzahl> so what am i missing here guys? since reinstalling with the latest debian cdimage, i am unable to boot any kernel without using the dtb loader(just specifying devicetree in grub). the boot pocess hangs right after the 3 "EFI stub" lines about loading the dtb etc.

20:11 <derzahl> ive been going for months without dtbloader and even modified grub scripts to automatically add the devicetree line

20:11 <derzahl> really strange it just stopped working

20:19 <steev> not sure. it definitely works here just specifying the dtb (on my second c630)

20:19 <steev> maybe add verbose to the kernel bootline? also something like earlycon=efifb ?

23:03 <derzahl> hm, ill try that

23:04 <derzahl> or should i just try to turn off all video modes until there system is fully booted and loads the msm module? not sure what the best way to do that would be

23:10 <derzahl> earlycon=efifb doesnt give me any more output:(

23:11 <derzahl> doesnt the boot process ususally stop there or go black because its trying to switch into a new video mode?

23:12 <derzahl> wonder if i can prevent that from happening.

23:14 <robclark> if earlycon=efifb doesn't show you anything more, then things are rather borked (corrupt or no dtb table?)

23:21 <derzahl> i dunno. i think there is something more to it.

23:22 <derzahl> so if i boot with dtbloader and try to boot steevs 5.12 kernel, without specifiying a devicetree in grub, it fails with that i2c_hid_of reset message over and over

23:23 <derzahl> if i specify a devicetree in grub, it seems to override the dtbloaders one

23:24 <derzahl> but if i boot without dtbloader at all, with my efi config just set to EFI\debian\grubaa64.efi, then it hangs even if i have the correct devicetree specified

23:24 <robclark> I suppose it is possible to have efifb support disabled in kernel config

23:25 <derzahl> so im thinking that grubaa64.efi isnt what it is supposed to be set to

23:25 <derzahl> i forgot what "Windows Boot Manager" was originally pointing to before i changed it to EFI\debian\dtbloader.efi

23:27 <derzahl> to clarify. if i specify the *correct 5.12 devicetree in grub, it seems to override the dtbloaders one, and the 5.12 kernel boots. but only if i boot the dtbloader entry, not when i boot grabaa64.efi

23:28 <derzahl> robclark: are you pointing to EFI\debian\dtbloader.efi when you boot

23:30 <robclark> well, EFI\fedora\dtbloader.efi but close enough

23:31 <derzahl> ah. yeh. im wondering what the default setting was now

23:32 <robclark> are you not getting into grub, it sounded like you were getting far enough to start kernel?

23:33 <derzahl> no, im getting in to grub

23:33 <derzahl> im just not sure why i cant boot a kernel without booting dtbloader.efi first anymore

23:36 <robclark> iirc, dtbloader removes the ACPI tables and adds the dtb table.. grub, assuming it is managing to correctly load the dtb is, I suppose, only doing the latter

23:37 <derzahl> so what should i be booting if im not booting dtbloader.efi?

23:37 <derzahl> is there something else that needs to come before grubaa64.efi?

23:38 <robclark> normally the boot flow would involve shim too, but with secure boot disabled that shouldn't really matter

23:56 <derzahl> very strange. i think it mustve been set to something else. because it doesnt make sense that "Windows Boot Manager" would be set to grubaa64.efi by default

23:58 <derzahl> shawnguo: do you know what Windows Boot Manager is set to by default? before you change it to dtbloader.efi per the instructions here https://github.com/aarch64-laptops/debian-cdimage?