05:57 <gwolf> steev: Thanks for the tip about tqftpserv! I updated my system, including pushing the kernel to 6.11, and was going crazy about it...

05:57 <gwolf> At least, I am happy to report that _mostly_ everything worked from a stock 6.11 tree!

05:58 <gwolf> The only thing I'm missing: Could not find anything about the battery :-(

06:00 <gwolf> I found /sys/bus/12c/drivers/bq27xxx-battery,but cannot read from its uevent (permission denied)

13:42 <steev> it should be lenovo-c630-ec-battery or something like that

15:18 <gwolf> I guess I didn't build that module or something... Will check the config tonight. Thanks for the pointer.

15:20 <gwolf> Did you find anything about the reason for tqftpserv? I can report a bug on the package, as it's a clear regression...

15:55 <MrCatfood[m]> on the vivobook i created a partition, and wrote the ubuntu image to it, is there a way to boot into that?

15:59 <maud> MrCatfood[m]: if you have a valid boot entry for it in the bootloader that is the first boot option

15:59 <maud> I had to boot into a usb, then efibootmgr from a live usb to set the correct boot order

16:00 <maud> you can probably do this from windows but I have no idea how

16:06 <tobhe> JensGlathe[m]: turns out my T14s usb boot bluescreen problem was just a module missing from the initrd

16:20 <JensGlathe[m]> let me guess - tcsr_80100?

16:21 <tobhe> not sure yet, I added a bunch based on lsmod from a working system

17:04 <JensGlathe[m]> do you have type-A ports running?

17:09 <MrCatfood[m]> ah man its a pain, i tried to add ubuntu to windows boot manager but cannot boot, im not sure why, im not even sure about the proper entry file

17:12 <SpieringsAE> i managed to get mine working with the arch wiki pages of systemd-boot and efibootmgr

17:12 <SpieringsAE> only need to add an extra devicetree parameter to the systemd-boot entry

17:12 <SpieringsAE> which is not on the wiki I believe

17:13 <SpieringsAE> have you tried booting your image from usb?

17:19 <macc24> SpieringsAE: you can also use https://github.com/TravMurav/dtbloader/ for something more portable

17:21 <MrCatfood[m]> yeah it boots fine but painfully slow, maybe i will buy a faster device or something, i just want to try to install Unity3d and try it on linux but that will be another challange

17:22 <macc24> what do you mean by painfully slow?

17:25 <SpieringsAE> guess slow usb, so bad rootfs r/w

17:25 <SpieringsAE> you can see the configuration of the bootloader of the usb

17:25 <SpieringsAE> you will still need efibootmgr

17:26 <SpieringsAE> maybe bootctl or grub-install or something

17:26 <SpieringsAE> macc24: I have heard about dtbloader, but Im confortable setting up embedded linux systems so ill just chill with making my own systemd-boot entries

17:34 <steev> gwolf: i have not had a chance to look into it; work has been packed and my free time was not wanting to. lumag helped me track it down a few nights ago in #linux-msm , and he poked konradybcio about it but last week/this week(?) was/is LPC (i think it is) so no idea if konrad has had time or if i should bother looking into it (we probably should open a debian bug and more probably an upstream issue)

17:35 <MrCatfood[m]> <macc24> "what do you mean by painfully..." <- i have an usb2.0 pendrive

17:37 <gwolf> OK. I'll _try to_ do so tonight (I've also been overwhelmed by work)

17:37 <steev> SpieringsAE: it is likely missing from arch as their wiki is fairly x86_64 heavy and they don't use dts there :(

17:40 <SpieringsAE> yep, I ran archlinuxarm which isn't even officially arch but eh

17:40 <SpieringsAE> mostly the same

17:43 <SpieringsAE> in general the "devicetree" parameter seems to be very poorly documented among bootloaders

17:43 <SpieringsAE> cant even really find it in documentation of grub or systemd-boot, when I get a snapdragon machine again im going to try out refind

17:56 <JensGlathe[m]> for booting from USB I recommend a m.2 nvme SSD enclosure. Usually dependent on orientation for typ-c, but its quite fast. And they are more durable

18:00 <steev> SpieringsAE: https://www.gnu.org/software/grub/manual/grub/html_node/devicetree.html

18:01 <steev> and probably because the docs are (usually) x86_64 centric as well, unfortunately. ubuntu has a patch in their grub that makes it easier to use, but grub upstream (from what i remember) nacked it

18:04 <travmurav[m]> Speaking of grub, for anyone interested I've posted a patch to add "efidriver" command to grub efi chainloader module. https://lore.kernel.org/grub-devel/20240922-cmd-efidriver-v1-1-750b77bfca0a@trvn.ru/T/#u

18:04 <SpieringsAE> I guess its also just an effect of the eco system, there were not a lot of systems besides x86/x86_64 using these bootloaders.

18:11 <JensGlathe[m]> travmurav: does that include slbounce?

18:12 <travmurav[m]> Yes

18:12 <JensGlathe[m]> nice

18:13 <travmurav[m]> That should be able to load any efi driver normally

18:15 <macc24> SpieringsAE: i found 'devicetree' option in systemd-boot to not work on my yoga slim 7x and had to use kernel's efistub dtb= parameter

18:16 <SpieringsAE> macc24: huh thats odd, it worked fine on my asus, dont know how that would differ

18:17 <macc24> JensGlathe[m]: i NEVER wanted to use anything other for a pendrive than my usb-nvme stick, tho some efi implementations don't like it :/

18:17 <macc24> SpieringsAE: *shrugs* it put a red error on screen about a protocol being not supported

18:17 <SpieringsAE> old systemd boot?

18:17 <travmurav[m]> If you mean dt fixup protocol it can be ignored assuming device boots after

18:18 <travmurav[m]> That error will be removed in next sd boot

18:18 <travmurav[m]> As in red warning

18:18 <macc24> SpieringsAE: i used systemd-boot 256

18:19 <macc24> travmurav[m]: i don't remember, it also happened when using UKI images

18:19 <SpieringsAE> thats new, so age shouldn't be it

18:20 <Jasper[m]> <travmurav[m]> "Speaking of grub, for anyone..." <- Very cool

18:20 <macc24> i don't know i just used dtbloader as it allows to have an image that works on more than one device

18:20 <travmurav[m]> Fwiw it also implements dt fixup protocol: p

18:21 <travmurav[m]> Which is of not much use for most devices right now though

18:21 <macc24> all i know is one worked the other didn't

18:22 <SpieringsAE> I want the 32gb version off the asus to become available here, I returned my 16 gb version when I realized that was coming out, so I don't have a snapdragon machine right now

18:22 <SpieringsAE> s/off/of

18:23 <SpieringsAE> its weird, it seems a bunch of them are not available here in the netherlands, the lenove t14s for example, nowhere to be found here

18:24 <macc24> if they're abroad in a different eu country it should be fine, btw which part of netherlands? i spent 6 months living in groningen and loved the city

18:25 <SpieringsAE> nice, thats far north of me, I practically live on the german border about in the middle of the country, near arnhem

18:25 <SpieringsAE> i believe the t14s is available from germany

18:25 <LucasTreffenstdt[m]> yeah, definitely is

18:26 <macc24> it should be fine as long as the address gets onto the packaage properly

19:55 <kuruczgy> macc24: for the record I am using systemd-boot on my yoga 7x with the devicetree option, never had issues

20:12 <JensGlathe[m]> I was able to boot with sd-boot and the devicetree option, too, on the hp Omnibook X14

20:13 <JensGlathe[m]> To install sd-boot, though, I had to allow qseecom first for the device name

20:15 <JensGlathe[m]> oh and the vmlinuz image must be uncompressed

20:28 <gabertron> tobhe: was there a patch someplace for your fix to get the display working on the 64GB t14s -- and which kernel are you using?

21:31 <tobhe> am using https://github.com/jhovold/linux/commits/wip/sc8280xp-6.11/ with two commits reverted

21:32 <tobhe> 9eb660f1ece4c05ed6f4c9e20208d21120928966 and 0951491f00704c3e901ba91c73178ec61c4e02b6

21:34 <steev> the sc8280xp or the x1e?

21:35 <tobhe> urgh right :) https://github.com/jhovold/linux/commits/wip/x1e80100-6.11 of course

21:35 <tobhe> thx steev

21:35 <steev> :D

23:03 <gabertron> Oh sweet thanks!

23:07 <HdkR> Huh, so it was external DP support that was breaking T14s OLED's eDP panel?

23:16 <tobhe> possible yes, I haven't had time to research what exactly is going on and everything is still a bit unstable

23:17 <tobhe> even with my current kernel it doesn't work sometimes

23:20 <HdkR> Wacky

23:24 <tobhe> another thing I noticed was that wifi seemed to be working at some point until it didn't. I think a linux-firmware upgrade happened in-between

23:24 <tobhe> working might be an overstatement. at least it showed up

23:43 <tobhe> oh no it actually works with git linux-firmware, so probably just broken or too old in Ubuntu

23:50 <tobhe> gabertron: double checked right now, dropping those two commits might not actually be necessary