ChanServ changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630)
leezu has joined #aarch64-laptops
derzahl has quit [Ping timeout: 480 seconds]
<leezu> It seems there is a regression on 6.0 with lazor? I'm seeing the following error when booting up with external screen + usb hub connected over usb-c. External keyboard didn't work at first until I replugged the usb-c connector, at which point the error was printed a second time. "rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { P2483 } 21 jiffies s: 389 root:
<leezu> 0x0/T"
<steev> i see those on the c630 too, have for a while
<steev> never could figure out what it is
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
psydroid[m] has quit []
derzahl has joined #aarch64-laptops
hexdump01 has quit [Quit: WeeChat 1.9.1]
hexdump0815 has joined #aarch64-laptops
xroumegue has quit [Ping timeout: 480 seconds]
SSJ_GZ has joined #aarch64-laptops
jhovold has joined #aarch64-laptops
xroumegue has joined #aarch64-laptops
<ardb> so external display works now on c630? anything in particular i need to enable in my kernel config?
matthias_bgg has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
iivanov has joined #aarch64-laptops
iivanov has quit [Quit: Leaving...]
iivanov has joined #aarch64-laptops
<steev> the patches aren't in the kernel yet, it needs bamse's patches for the EC, and if it throws an error, you need to flip the usb-c connector and plug it back in
<ardb> got a link to those patches?
<ardb> and it's only the port on the right, right?
<steev> si
<steev> only the right port (not sure if that's a limitation of the patches or if it's the limitation of the ec )
<steev> gotta find his older stuff
<ardb> same on windows
Guest2372 is now known as qzed
<steev> ah, didn't know that
<steev> i believe both of those are required for it to work, and if you use gnome, you should run it on xorg not wayland
<steev> mutter has issues
<ardb> does that replace the some-battery stuff?
<steev> yes
<steev> oh wait
<steev> that too
<ardb> and the drivers for that?
<steev> ^
<steev> they are still WIP, and changes have been requested, but for the most part, it works
<ardb> good stuff - i'll have a go with those tomorrow
<gwolf> steev: FWIW, I never tried too much, but for the C630 I have very good performance under Wayland, while it was close to unusable under Xorg
<gwolf> Maybe I didn't load the right modules for the GPU... But anyway -- I don't run Gnome, but I'd prefer Gnome on Wayland
<gwolf> (unless there's something very severe I missed)
<steev> gwolf: there's an open issue about mutter >=42 crashing with wayland - https://gitlab.gnome.org/GNOME/mutter/-/issues/2398 - that's the main reason
<steev> i also prefer wayland :) and the issue doesn't show up at all on 3.38 (but they added atomic stuff in 40+ (not sure when exactly)) so debian stable is fine
<gwolf> oh, bummer :-\
<gwolf> I guess the crash is only on Adreno or ARM or something like that...?
<gwolf> As it sounds like _way_ of a release blocker otherwise
<steev> i unfortunately don't run gnome on any systems but adreno, and i know it happens there
<steev> i do believe it's specific to adreno, i just don't know enough to fix it
<gwolf> right, and it's not popular enough I guess
<gwolf> unless you count Gnome for Tablets
<travmurav[m]> isn't this that issue that is only hit with the external display?
<travmurav[m]> yeah, seems to be
matthias_bgg has quit [Remote host closed the connection]
<ardb> does it only happen when using both displays at the same time?
<gwolf> Say, re:external displays...
<gwolf> ...Do you know if Anderson's kernel patches for having the C630 recognize the HDMI output have been sent or accepted upstream?
<gwolf> (read: Should I attempt to use 6.0?)
Penguinpee has quit [Remote host closed the connection]
Penguinpee has joined #aarch64-laptops
jhovold has quit [Ping timeout: 480 seconds]
<steev> they aren't yet
<steev> iirc, they kinda want him to do it as mfd driver, but, i haven't kept up
<steev> sorry - sent yes, accepted, no
<steev> at least, not all of them
<gwolf> OK. Well, that's the right path at least :-)
<gwolf> I can at least stay with 5.19 and be happy
<gwolf> the only pain point I've had (but it's so minor I have learnt not to even care is that... audio really still sucks :-(
<gwolf> And I have *two* external USB audio controllers -- but this 5.19 errors when trying to use any of them
derzahl has quit [Remote host closed the connection]
derzahl has joined #aarch64-laptops
derzahl has quit [Ping timeout: 480 seconds]
derzahl has joined #aarch64-laptops
iivanov has quit [Quit: Leaving...]
derzahl has quit [Ping timeout: 480 seconds]
gwolf has quit [Ping timeout: 480 seconds]
derzahl has joined #aarch64-laptops
gwolf has joined #aarch64-laptops
<NomadNaomie[m]> will 6.0 fix the X13S' Audio and BT?
SSJ_GZ has quit [Ping timeout: 480 seconds]
<mani_s> NomadNaomie[m], unfortunately, no
<clover[m]> Nomad Naomie: I use a usb BT adapter for now, it works well as a workaround!
<NomadNaomie[m]> Yeah I have one too but I was hoping to use it for audio :
<NomadNaomie[m]> s/:/:|/
<clover[m]> X13s support seems to have slowed down :(
<HdkR> It's a shame, I just had three X13s laptops land on my door this morning
<NomadNaomie[m]> I might have to dig deeper into getting recovery media for W11 then and dual boot
<mani_s> BT and audio are still wip for x13s
<clover[m]> >The (expensive) Lenovo ThinkPad X13s laptop, which runs on the Qualcomm Snapdragon 8cx Gen3, starts to pick up support. The ThinkPad X13s is pre-loaded with Windows 11 for ARM but, with Linux support now in the formative stages, this could be a great reference device for Linux ARM enthusiasts.