02:20 <steev> there's definitely x1 google support going into the kernel

03:50 <Segfault[m]> hey it's semi-offtopic but does anyone know how reliable kexec is on mainline linux qualcomm devices?

08:51 <abby> hi, I've gotten void booting 6.8.1 on my x13s by merging the defconfig from the 6.8 wip branch (https://github.com/jhovold/linux/tree/wip/sc8280xp-v6.8) with void's generic aarch64 .config, but i did not include any of the patches in that branch. the primary thing I see not working is usb and the built-in keyboard. are any of the patches on that branch related to known issues with usb/keyboard?

08:52 <abby> the config i'm using is arm64-dot-configcustom.full in this commit, with the diff on arm64-dotconfig-custom showing the changes relative to the defconfig (https://github.com/classabbyamp/void-packages/commit/3d073756c701b0644fcea764dba6ede8d6ad4a5a)

08:55 <jhovold> abby: no, you can run mainline 6.8 on the x13s (i.e. you don't strictly need anything from my wip branches)

08:55 <abby> mainline assuming the correct config options are enabled, correct?

08:56 <jhovold> yeah, obviously (you can run using the mainline arm64 defconfig without modification too)

08:57 <jhovold> and you need to make sure your initramfs has what is needed to boot, which depends on your config

08:57 <jhovold> there are some details in the commit message for johan_defconfig if you haven't seen that already:

08:57 <abby> i added the modules specified in the commit message to the initrd, but i may need to go back over things and see if i'm missing anything

08:57 <jhovold> https://github.com/jhovold/linux/commit/935f2e13e13d2dcfb923d3b0881c905861a7a9ce

08:58 <jhovold> ah, good

08:58 <jhovold> for the built in keyboard you need i2c_hid_of and i2c_qcom_geni

08:59 <abby> i have i2c_hid_of and i2c_qcom_geni as =m and force_modules in dracut

08:59 <abby> force_drivers*

08:59 <jhovold> and you don't strictly need that in your initramfs either, only if you need to enter a FDE password or similar

09:00 <abby> via ssh i can confirm those two modules are loaded, so hmm

09:04 <jhovold> sounds like you may still be missing some dependency then (e.g. a regulator driver)

09:05 <jhovold> you should be able to tell from dmesg | grep hid if the driver probes at all

09:05 <jhovold> otherwise you can check for missing suppliers in sysfs (/sys/bus/i2c/devices/21-0068)

09:06 <abby> there's a bunch of hid-generic 0018:06CB:CE5C.0002: unknown main item tag 0x0

09:07 <jhovold> that'd be the touchpad, never seen any errors like that here

09:08 <abby> half of those messages have 0018:04F3:000D.0001

09:08 <abby> might that be the keyboard?

09:08 <jhovold> yes, that's the keyboard

09:10 <abby> i'm going to try flipping some of the regulator configs from m to y

09:10 <jhovold> the keyboard should not even probe if those were missing, so something else appears to have gone wrong here

09:12 <abby> CONFIG_REGULATOR_QCOM_PM8008=m was missing from my config, relevant?

09:12 <jhovold> just to rule that out, are you booting with "clk_ignore_unused pd_ignore_unused"

09:12 <jhovold> not relevant

09:12 <abby> yes

09:15 <jhovold> perhaps you can start by making sure you can build and boot my wip branch, or mainline, using a johan_defconfig only

09:17 <abby> sure

09:43 <abby> that appears to be worse, display goes off after ~30s and network is not up for me to ssh in

09:43 <abby> does appear to be on though

09:49 <jhovold> sounds like you fail to boot so that the display subsystem is not probed

09:50 <jhovold> check the console log before the display turns off

09:50 <abby> last thing i could see was some messages about either pmic or pcie waiting to sync

09:51 <jhovold> with my wip branch and config you need to make sure pcie_qcom is in the initramfs (or make sure to compile it in)

09:51 <jhovold> sounds like you're missing the pcie controller driver

09:51 <jhovold> with mainline it is always compiled in

09:53 <abby> not set, it seems

09:53 <jhovold> CONFIG_PCIE_QCOM=y

09:54 <jhovold> would be =m in johan_defconfig

11:28 <abby> wasn't able to have any luck with the defconfig. the kconfig diff between the defconfig and the best-working kconfig is https://p.qrm.cat/Fph4iS.diff. i noticed that rmmmod/modprobe i2c-qcom-geni causes the spam of unknown main item tag 0x0 messages again

11:28 <abby> have to do other things for a bit but thanks for the help troubleshooting

11:32 <abby> as another datapoint, debian (6.6.15) works well on the same machine

16:29 <zdykstra> I hit the same issue(s) as abby in my own process of trying to bring up Void on the x13s, with kernel 6.7.something.

21:18 <abby> jhovold: not sure what I was doing wrong last night, but i was able to boot your defconfig (with PCIE_QCOM m -> y) today and keyboard works in there