robclark changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Chrome OS Trogdor Devices - Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630 - Lenovo ThinkPad X13s - and various other snapdragon laptops) - https://oftc.irclog.whitequark.org/aarch64-laptops
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
<steev> jenneron[m]: have you tried 6.9 on the c630? just using the defconfig, i'm getting a null pointer deref with the soundwire device - http://sprunge.us/dYBW50
ajhalaney[m] has quit []
alfredo has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
<jenneron[m]> steev: hm?
<jenneron[m]> i don't have c630
<jenneron[m]> and isn't this a problem we have already discussed?
<jenneron[m]> i think if you take 6.7 drivers/soundwire/qcom.c and place it in recent kernel it works
<jenneron[m]> just need to find the commit breaking it
<travmurav[m]> can probably bisect over that file? (or even just check the log of it and maybe see if the change that broke it is obvious?)
<jenneron[m]> yes, but i'm not the one doing it
<jenneron[m]> last time i did send a patch to fix it, and someone else posted another version of patch (more correct one) even without Repored-by from me
f_ has joined #aarch64-laptops
<jenneron[m]> if they treat people spending time for bisect like this they should bisect it themselves
<jenneron[m]> i can just take a file from 6.7 on ayn odin and it should work for me
<jenneron[m]> and it's probably not difficult here as you work with only one file
<jenneron[m]> (not difficult to bisect, i mean)
jhovold has joined #aarch64-laptops
svarbanov has quit [Ping timeout: 480 seconds]
alfredo has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
NewWheat has joined #aarch64-laptops
<NewWheat> I'm trying to make the audio work on huawei matebook e 2019 (sdm850). How can I configure the &sound node in dts and the ucm2 files?
NewWheat has quit [Remote host closed the connection]
<jenneron[m]> NewWheat: it pretty much depends on hardware
<jenneron[m]> you may have a chance o get headphones working by copying c630 bindings removing speakers from there
NewWheat has joined #aarch64-laptops
<NewWheat> jenneron[m]: The speaker and headphone works fine with c630's settings, but the microphone doesn't. Is it possible to get the hardware information from Windows or dsdt.dsl?
<jenneron[m]> NewWheat: i actually really doubt microphones work on c630
<jenneron[m]> i have a device with the same setup and mics don't work for me
<jenneron[m]> so it is likely that c630 configuration is wrong
<jenneron[m]> i haven't managed to fix mics unfortunately, i don't know that much about audio routing on qcom, maybe others can help
<NewWheat> jenneron[m]: I see...
<NewWheat> Thanks a lot
NewWheat has quit [Quit: Page closed]
z3ntu has quit [reticulum.oftc.net helix.oftc.net]
Jasper[m] has quit [reticulum.oftc.net helix.oftc.net]
KieranBingham[m] has quit [reticulum.oftc.net helix.oftc.net]
martiert has quit [reticulum.oftc.net helix.oftc.net]
flokli has quit [reticulum.oftc.net helix.oftc.net]
martiert has joined #aarch64-laptops
flokli has joined #aarch64-laptops
possiblemeatball has joined #aarch64-laptops
KieranBingham[m] has joined #aarch64-laptops
jglathe_x13s has quit [Remote host closed the connection]
jglathe_x13s has joined #aarch64-laptops
jglathe_volterra has joined #aarch64-laptops
<abby> interesting, using the in-kernel pd-mapper on 6.8.9 removes the deferred probes for soundwire stuff, but it still takes 120 seconds to boot to getty
<abby> previously it was hanging at messages about deferred probes for ~120 seconds then continuing
<jglathe_volterra> hm? I have a login screen before the 30 seconds, usually
<abby> yeah i dunno
<abby> but iirc same thing happened on johan's defconfig?
<jglathe_volterra> sounds like a module is missing
<abby> probably, but there's no output even at loglevel=7
<bumble[m]> x13s is an incredible machine and is much better than reviews on the internet would lead one to believe
<jglathe_volterra> the touchscreen rule shouldn't be necessary btw
<jglathe_volterra> @bumble[m] it def is
<abby> jglathe_volterra: since when?
<abby> jhovold's wiki page says it's only in the wip branc
cyrinux3 has quit []
cyrinux3 has joined #aarch64-laptops
jglathe_volterra has quit [Remote host closed the connection]
jglathe_volterra has joined #aarch64-laptops
f_ has quit [Ping timeout: 480 seconds]
<steev> bumble[m]: most people judge it based on windows arm performance. then again, people used to judge our single core 800mhz board against the latest i7 when i was at the device manufacturer
<steev> reviews are.... fickle
Erisa has quit [Read error: No route to host]
Erisa has joined #aarch64-laptops
<steev> jenneron[m]: it wasn't a null pointer before, that's why i'd asked if you'd seen it, i forgot you have odin not c630
<jenneron[m]> steev: i thought it was
<pstef_> speaking of Odin, I saw someone running Armbian on the Odin 2. But I don't know how barebones it is
<jenneron[m]> the latest stuff is in my kernel branch
<jenneron[m]> but yeah people did run linux on it before
<jenneron[m]> i'm probably okay with pmOS on it
<jenneron[m]> odin 2 would be much better, might be able to run some PC games with FEX
<pstef_> how would the driver support be for Odin 2?
<HdkR> Neat, Snapdragon 8 Gen 2 in the Odin 2, but Android.
<jenneron[m]> there is someone working on odin 2, but i doubt it is documented anywhere
<jenneron[m]> Jasper[m]: it has been done already
<jenneron[m]> i would like to see odin 2 supported in pmOS as well
<jenneron[m]> the only problem is 350$ for it, heh
<lollaritits[m]> anyone has a collection of X55 firmwares here?
<pstef_> what I saw was PRs like this one https://github.com/armbian/build/pull/6305 and another one I can find if anyone wants
todi has quit [Ping timeout: 480 seconds]
<jenneron[m]> you can use it on any distribution
<pstef_> thanks, I wasn't aware of that one
hightower2 has joined #aarch64-laptops
todi has joined #aarch64-laptops
z3ntu has joined #aarch64-laptops
<abby> huh, the delay seems to have resolved itself now
<jglathe_volterra> @abby the famous magic healing
<abby> i added pinctrl_sc8280xp to the initrd and it didn't solve it immediately, but after a few boots
<jglathe_volterra> oddd
Jasper[m] has joined #aarch64-laptops
<jglathe_volterra> tried to add the other ones too?
<abby> most of them i already had, adding q6v5_pas or whatever it is fails to boot
<jglathe_volterra> oh thats odd. Didn't come around to document what I've seen with this and @jenneron[m]'s hint https://gitlab.com/postmarketOS/pmaports/-/blob/master/device/testing/firmware-lenovo-yoga-5g/APKBUILD?ref_type=heads#L44-46
<jglathe_volterra> If it's not there I only got "late" adsp fw loads, leading to the VBUS issue when booting from type-c. To make sure it loads from initramfs I had to store the adsp blob only in .disabled form on the root fs.
<abby> hm well i'm booting from nvme :)
<abby> dunno
<jglathe_volterra> so all *8280.mbn files should be in the initramfs to make this work. However if there is none of these available it still boots as long as there are the a660 firmware files.
<jglathe_volterra> from nvme all this is sort of a non-issue
<jglathe_volterra> which makes it all the more interesting... kernel config missing?
<jglathe_volterra> I built debs today and installed on Volterra (after fixing flash-kernel with a local config) and on x13s, works without change on both as intended. My devkit_defconfig is derived from @steev's laptop_defconfig.
<lollaritits[m]> anyone has an up to date recovery image for the x13s?
jhovold has quit [Ping timeout: 480 seconds]
jglathe_volterra has quit [Remote host closed the connection]
<abby> anyone here on ALARM with the x13s? is it using mkinitcpio? i was not able to get mkinitcpio to load the firmware and/or modules properly, so the rootfs couldn't be mounted
<steev> i do believe clover does but seems his matrix hasn't reconnected
clover[m] has joined #aarch64-laptops
<clover[m]> Yeah I'm on alarm
<abby> using mkinitcpio?
<abby> i have the default mkinitcpio conf + https://p.qrm.cat/rYjOd1.conf on void, and it doesn't appear to be loading the modules and/or firmware properly and thus can't find the rootfs and boot
<abby> was wondering what kind of conf alarm has
<clover[m]> Yes I can send you my config after dinner
<abby> thanks