01:44 <louist103> Hi all. I was redirected here form the gentoo-arm chat. I was wondering about the support of the Yoga C630. Going by the top with it being named I would assume its good. I noticed that when I booted into the live CD I couldn't use the builtin keyboard but the trackpad worked and an external keyboard also worked. I could aos navigate the grub menu just fine. For the install to work with my keyboard will I need the patches from aarm64-l

01:47 <louist103> Or is there an option in the kernel config I could set when building to make the keyboard work?

04:47 <dgilmore> fwiw audio with the latest 6.3-rc3 and alsa 1.2.11 seems fine here with pipewire. the speakers could maybe be a smidge louder, butare clear and without any crackling. at leastplaying some youtube videos

04:47 <dgilmore> steev: ^^ louist103's questions seem up your alley

05:58 <steev> ah dang, it was superbowl sunday and i missed it, but it should be the i2c_hid_of driver on the c630 iirc

05:58 <steev> maybe it's hid_multitouch (or maybe hid_multitouch is loaded and thats' why their touchpad worked and hid_of wasn't and that's why the keyboard wasn't)

07:34 <jhovold> dgilmore: interesting, is that with or without the limited quantum size workaround?

07:48 <jhovold> dgilmore: and I assume you only refer to playback?

13:01 <dgilmore> jhovold: yes to playback, not sure what the limited quantum size workaround is, so I would say without

13:03 <jhovold> dgilmore: exeat and others, including myself, had multiple issue when using pipewire for playback, including too fast playback and choppy playback

13:04 <jhovold> exeat noticed that limiting the quantum size made these issues go away, but the underlying cause is yet to be identified

13:05 <jhovold> the quantum size can be limited using: pw-metadata -n settings 0 clock.max-quantum 1024

13:59 <danielt> This patch should fix the C630 keyboard-not-working-if-hid-sensor-hub-is-enabled issue: https://lore.kernel.org/all/20230528092427.42332-1-daniel.thompson@linaro.org/ (and if backporting... don't forget that there was a follow up fix to avoid regressions: https://lore.kernel.org/lkml/170326966337.2018208.16515231674277786077.b4-ty@kernel.org/T/ )

14:17 <steev> ah, i wonder if that's why louist103's wasn't working

14:34 <louist103> Thanks for the information. Is i2c_hid_of, hid_multitouch and the two linked patches in the kernel it builds during the build process? And is it enabled by default or will I need to enable it my self in the menu config?

14:41 <Jasper[m]> <louist103> "Thanks for the information. Is i..." <- There are config options for both yes

14:42 <danielt> I'm not familiar with the i2c_hid_of vs hid_multitouch stuff but my patch should "just work" if you have v6.6 or later (so if you are runing v6.6 or later you can ignore my comment).

14:50 <louist103> Ok. So the patches aren't in upstream linux yet I assume? Or are you saying they are in 6.6 already?

14:54 <danielt> v6.6.0 has just the first patch but the other was backported at some point IIRC (and probably isn't needed on C630).

15:10 <louist103> Ok great. Lets hope after enabiling those two options it "just works". I guess I can just follow the x86_64 handbook and use the ARM tar balls.

15:24 <steev> for the most part, probably; i thought there was an arm64 handbook too, but i haven't done a gentoo install in a few years

15:24 <louist103> If there was its not there any more. It says there are too many different types of machines to make one book.

15:25 <steev> there's a lot of steps that are the same regardless of hardware

15:25 <louist103> That is what I was thinking

15:26 <steev> fwiw, since i was used to gentoo (i was a dev at one point in the past) i always just followed the quickinstall guide rather than the handbook

15:26 <Jasper[m]> steev: They note in the wiki that the differences per SoC are too big to be consistent

15:26 <steev> well they are right, but also wrong

15:27 <Jasper[m]> "Embedded Handbook" is apparently community maintained and covers some arm things

15:27 <Jasper[m]> Might be worth looking at

15:28 <louist103> I did see that but it looks like its more focused on dev boards and not really laptops

15:31 <steev> the c630 should be fairly cut and dry; you might want to look at some of nerdboy's packages for the x13s, i believe he has grub with the devicetree patches

15:32 <danielt> context74Fork

15:41 <ardb> anyone try the slbounce thing on c630?

15:42 <travmurav[m]> the approach was tested, not sure if anyone tried to boot linux on it

15:42 <travmurav[m]> well

15:43 <travmurav[m]> someone did try but there was some problem and this was using very WIP and VERY unfriendly version

15:44 <travmurav[m]> so I think in the end we only confirmed that cpu runs at EL2, and they put linux aside

16:00 <ardb> ack

16:00 <ardb> will have a go at this later this week

17:05 <jhovold> Here's an updated wip branch for the X13s:

17:05 <jhovold> - https://github.com/jhovold/linux/tree/wip/sc8280xp-v6.8-rc4

17:05 <jhovold> Changes include

17:05 <jhovold> - fix PCIe link errors when starting Wi-Fi link

17:05 <jhovold> - switch to using GIC ITS for PCIe MSIs

17:05 <jhovold> - disable ASPM L0s for X13s Wi-Fi

17:05 <jhovold> - disable ASPM L0s for CRD NVMe

17:05 <jhovold> - add missing PCIe minimum OPP

17:07 <jhovold> Segfault[m]: Could you see if the intermittent issue you had with the Wi-Fi not starting goes away with the above?

17:07 <jhovold> I think should be related to the link errors seen when bringing up the Wi-Fi link

17:08 <jhovold> Also I'd appreciate if someone with a modem on the X13s could give it a spin and look for any AER errors in the logs

17:08 <jhovold> We may need to disable ASPM L0s also for the modem if that's the case

17:34 <Jasper[m]> <jhovold> "Also I'd appreciate if someone..." <- Up to what point? Usage with SIM and such or just power on and fcc unlock and such?

17:36 <jhovold> yes, transfers in both directions should trigger it if there are any issues

18:03 <jhovold> oh, and watch out for any errors from the the NVMe controller as well (mine does not support L0s, so no errors here)

18:07 <jhovold> these are correctable errors and would be there today as well, they're just not reported by AER driver currently as the corresponding interrupts are not received

18:52 <enyalios> louist103: i just followed the amd64 handbook for my x13s and it worked for the most part

19:38 <louist103> Perfect. I'll do that then