00:56 <adrian_> woot, ok, i got freebsd booting (and then panicing) with the fdt

00:56 <adrian_> and found a whole lot of hilarious stuff that needs fixing

00:57 <adrian_> (but god i wish I had a UART)

08:29 <smoorgborg[m]> I've been trying to get Arch booting on my T14s for two days now. Both with x1e kernel from anonymix007 and compiling the version from jhovold myself. I'm not getting anywhere with this - looks like modules aren't loading properly on either kernels. Any hints?

08:50 <SpieringsAE> smoorgborg: start job stuff makes me think that rootfs uuid or something may be wrong

08:50 <SpieringsAE> that is systemd already I believe, you have display out, so the modules are loading

08:50 <smoorgborg[m]> screen blanks after 30 seconds, keyboard is not responding

08:50 <SpieringsAE> maybe that usb issue that needs the special module blacklist

08:51 <smoorgborg[m]> also I don't think nvme ever gets loaded, fairly sure about the uuid, it should trigger the sd-encrypt unlock

08:51 <SpieringsAE> that also looks like a uuid

08:51 <SpieringsAE> so yeah it definetly seems like an issue mounting the partition(s)

08:52 <smoorgborg[m]> what about the ton of i2c errors?

08:52 <SpieringsAE> there are still a lot of errors in dmesg, even in a working system. Don't quite know if these are some of those

08:55 <jhovold> smoorgborg[m]: looks like missing modules in your initramfs

08:55 <jhovold> you can work around the display going black after 30 s by passing "regulator_ignore_unused" until this has been resolved

08:56 <jhovold> you the i2c and hid driver for keyboard in whatever rescue environment you end up in

08:56 <jhovold> a missing nvme driver could prevent the root fs from being mounted, etc

08:56 <smoorgborg[m]> These are the modules I've built the initrd with https://github.com/anonymix007/x1e-alarm/blob/master/linux-x1e/mkinitcpio.conf.d-x1e.conf

08:57 <smoorgborg[m]> the modules are in there, I've checked with lsinitcpio

08:59 <SpieringsAE> yeah I use that list as well

09:00 <jhovold> for some reason the i2c driver has not yet probed (successfully), hence the sync state messages

09:00 <SpieringsAE> what are your boot args smoorgborg

09:01 <SpieringsAE> fstab

09:01 <SpieringsAE> boot config

13:26 <calebccff> hey everyone, we just merged a "distro integration guide" to the aarch64-laptops website: https://aarch64-laptops.github.io/distro_integration.html -- this is mostly aimed at folks trying to bring up a new distro on their Snapdragon laptop, but might have some useful info if you're messing with the kernel too

13:54 <tobhe_> Looks great, thx calebccff!

13:57 <Jasper[m]> Extremely useful @calebccff thank you!

14:00 <tobhe_> I wonder if it should mention the 64GB RAM workarounds somewhere because they cost a few people a lot of time to debug in the past

14:23 <robclark> calebccff: thx, one typo: `or even derives itself from the defconfig` s/derives/drives/

15:11 <bumble[m]> <calebccff> "hey everyone, we just merged a..." <- "For those unitiated" should probably read "For those uninitiated"

17:22 <robclark> Hmm, I noticed arm64 defconfig does not set CONFIG_HZ_* so we end up defaulting to CONFIG_HZ_250 .. which is a bit suboptimal.. are others explicitly overriding the defconfig here? Anyone know why arm64 defconfig isn't setting CONFIG_HZ_1000 (x86 defconfig is)

17:34 <tobhe_> the ubuntu default config is setting CONFIG_HZ_1000

17:37 <tobhe_> that was apparently added some time last year with a bunch of low latency stuff

17:41 <robclark> yeah, I'm hoping distro's are mostly setting it explicitly rather than relying on defconfig

17:42 <robclark> jhovold: btw you might want to add CONFIG_HZ_1000=y to your defconfig

17:54 <tobhe_> looks like debian actually explicitly configures 250 https://salsa.debian.org/kernel-team/linux/-/blob/debian/latest/debian/config/config#L6394

18:04 <pengyu[m]> have anyone encountered atk12k failed to fetch board file? weird, I added mine to regenate it and set a variant name, it still fails.

18:12 <alexVinarskis[m]> <Pengyu[m]> "have anyone encountered atk12k..." <- Had the same the first time with atk11k. Iirc it was because firmware was compressed, but boards file wasn't, or the other way around, but maybe I messed something else too. Re-did from scratch placing both firmware and pacthed boards under `/firmware/updates`, and it worked.

18:12 <alexVinarskis[m]> Made a small guide with step-by-step like it worked for me, should be the same for atk12k:

18:12 <alexVinarskis[m]> https://github.com/alexVinarskis/linux-x1e80100-zenbook-a14?tab=readme-ov-file#wcn688x-wifi

18:44 <pengyu[m]> alexVinarskis: Thank you, I just wanted to try to use the firmwares from stock one.

18:46 <alexVinarskis[m]> Pengyu[m]: maybe that still works though, did you compress your boards file?

18:46 <alexVinarskis[m]> At some point I was in the state where board was read, old firmware used, and firmware crashed - perhaps it won't crash in your case though

18:48 <pengyu[m]> I have two copies, zstd and normal bin, it doesn't work for me.

18:49 <pengyu[m]> And there was another issue, the board file is too large to merge(I guess the limit is 2M?), So I removed some board files in it.

20:46 <kuruczgy[m]> jhovold: It appears you were right, changing the retimer regulator pinconfig from "func1" to "normal" (plus adding power-source and bias-disable, not sure if they matter) appears to fix the retimer probing issue for at least one user. I also added some pinctrls for the retimer reset gpios, as I found them in the CRD dts, again not sure if those matter: https://github.com/kuruczgy/x1e-nixos-config/pull/105/files

21:29 <bryanodonoghue> hey anthony25 are you feeling like a guinea pi... like a hero ?

21:29 <bryanodonoghue> https://git.codelinaro.org/bryan.odonoghue/kernel/-/commits/x1e80100-6.14-rc6-dell-xps-inspirion14-lenovo-slim7x-t14s-camss-sound-wip?ref_type=heads

21:29 <bryanodonoghue> I certainly had the regulators for t14s RGB sensor wrong

21:29 <bryanodonoghue> per commit log its either one set of regulators or the other

21:30 <bryanodonoghue> could you try the slim7x commit ?

21:31 <bryanodonoghue> that branch should have working dell inspiron 14, xps RGB camera and I hope now lenovo t14s and slim7x

21:51 <kuruczgy[m]> bryanodonoghue: Do you have a branch based on Johan's 6.14? I could also try it on the slim7x if I have time over the weekend.

22:16 <bryanodonoghue> yes that branch is johan's branch + clock fixes from the list and camera driver/dts and sensor enabling

22:16 <bryanodonoghue> you can literally just cherry pick

22:29 <anthony25> haha, ok that much flattering has convinced me