05:06 <travmurav[m]> jenneron: steev : I didn't really follow but if it's "bt works ootb on 6.1 but needs mac on 6.7", I think the kernel was changed at some point to refuse bluetooth if the mac was not set

06:15 <steev> travmurav[m]: that could be it

12:01 <bryanodonoghue> steev yep and annoying and stupid message

12:03 <bryanodonoghue> present for a long time which I haven't gottten around to getting rid of

15:36 <albsen[m]> (no question, just an update) I been checking to setup linux on my x13s, so far, debian didn't boot at all. ubuntu booted and I installed it on a new drive I got before. well, it's still ubuntu and I just can't get over how much I don't like snap. so now, I'm trying to get archlinux working. so far that actually worked. I managed to boot it using the archlinux iso from here also following this tutorial.

15:36 <albsen[m]> https://github.com/ironrobin/archiso-x13s/wiki/EndeavourOS-Tutorial (simply didn't go forward with the endeavourOS install at the end which is in the end a pretty stable archlinux. now I'm trying to reinstall with encrypted boot using GRUB and LUKS; not yet done.

16:36 <steev> did you follow the debian wiki for the debian install? https://wiki.debian.org/InstallingDebianOn/Thinkpad/X13s i mean

17:55 <jglathe> (update) the ath11k wakeup fail happened today on both x13s and volterra, the ones where irc was running. Both still have pcie.aspm.policy=powersupersave as kernel parameter, hmm

17:58 <steev> i still haven't seen that :(

17:59 <steev> otoh, i do get spammed with "ath11k_pci 0006:01:00.0: msdu_done bit in attention is not set" and i dunno why

17:59 <steev> i'm sure someone familiar understands that, but while the words make sense to me individually, in that order, they are nonsensical

18:30 <jglathe> Let's see if it changes without the aspm setting

18:30 <jglathe> both run 6.7

18:57 <steev> 6.7 on the c630 also gets angry when the firmware crashes

18:57 <albsen[m]> <steev> "did you follow the debian wiki..." <- yes, I noticed that booting from ventoy was the issue. I've now placed debian on a usbstick and I'm trying to install it

19:00 <albsen[m]> I'm actually quite happy that debian looks like its working, that was my preferred os for this machine

19:01 <steev> i use kali, which is a derivative, but ema does use debian (and does most of the merge requests for x13s stuff in debian)

19:01 <steev> we've still got a little ways to go for kernel support, but we're getting there

19:02 <albsen[m]> it's amazing how well everything works considering that it's arm and a single unit (x13s) I'm super grateful for all the work that went into this.

19:02 <steev> arm stuff has worked fine for long time

19:02 <steev> most of the "arm performance is trash" is the fact that companies use slow ass io

19:02 <albsen[m]> what I mean is that arm stuff in general isn't as standardized as intel

19:03 <albsen[m]> and that many things are custom for individual devices

19:03 <steev> that... is kinda true, yeah

19:03 <steev> as long as the device has u-boot new enough to do distrobootcmd it should be fine

19:05 <konradybcio> intel isn't standardized either.. it's just a duopoly that play together

19:06 <konradybcio> if there were 2 arm soc makers (excl apple), there would probably be compatible too

19:07 <albsen[m]> well in anycase, I'm super happy that the nice people in this chat and around the world have put so much time into making this random laptop that I have in front of me work with my favorite OS :)

19:10 <steev> jglathe: were you using something like https://bugzilla.kernel.org/show_bug.cgi?id=217239 the systemd service they suggest (you can also i guess, try the other wifi firmware in kvallo's github to test)

19:16 <jglathe> @steev oh interesting, I have linux-firmare 20230919.git3672ccab-0ubuntu2.5 could be. Thank you for the link.

19:16 <steev> according to that bug, some versions work for some people and some don't for others (e.g. i have 23 here, and it seems to work fine suspending and resuming)

19:22 <nerdboy> apparently x13s bios does not like booting EFI/vendor/grubaa64.efi without a boot menu entry?

19:24 <nerdboy> adding a shell bin seems like it should be helpful, is anyone using the edk one?

19:24 <nerdboy> eg, https://github.com/tianocore/edk2/releases/download/edk2-stable201911/ShellBinPkg.zip

19:32 <steev> not sure if that's the one i have, but there was one on the (long ago) debian installer iso i used, and i just dropped it in there to always have one

19:36 <ema> albsen[m]: if you install debian sid most things should work fairly way at this point with two important exceptions: (1) audio due to a missing firmware file - https://bugs.debian.org/1057040 and (2) efi variable support which is in linux 6.7 and pending a config change currently under review

19:36 <ema> *fairly well

19:37 <ema> (1) you can fix manually by fetching the firmware from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/qcom/sc8280xp/LENOVO/21BX and creating the symlink yourself

19:39 <ema> (2) requires still a bit of patience :)

19:57 <albsen[m]> <ema> "(1) you can fix manually by..." <- amazing, thank you. I actually just now finished the installation. encrypted drive and all. really nice. will check how the link you shared and how to do this

20:35 <hexdump0815> leezu: what is your latest state with your asurada spherion? i'm currently trying to see what works and what not

20:36 <hexdump0815> it seems to basically run with v6.7.0 but for me (and it seems other too) the touchpad does not seem to work - do you have yours working?

20:37 <hexdump0815> did you get audio and scp working? from your last notes it seemed you had problems with both around v6.4/v6.5

20:46 <hexdump0815> leezu: my plan is to build a newer and hopefully more useful debian image for it and i'm now at the point to figure out what works and where i'll have to hunt for patches/info

21:54 <jglathe> oops

21:55 <jglathe> volterra starting up, the WLAN MAC address is quite random... 00:03:7f for Atheros, the rest is random

21:59 <steev> probably need to do the same thing as x13s (for now)

21:59 <steev> some day we'll learn where they store it

22:01 <jglathe> with windows they have Microsoft OUI a0:4a:5e and WLAN and BT the same address differing by 1 in the last octet