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
svarbanov has quit [Ping timeout: 480 seconds]
KREYREN_oftc has quit [Remote host closed the connection]
possiblemeatball has quit [Ping timeout: 480 seconds]
possiblemeatball has joined #aarch64-laptops
possiblemeatball has quit [Quit: Leaving]
ungeskriptet is now known as Guest2096
ungeskriptet has joined #aarch64-laptops
Guest2096 has quit [Ping timeout: 480 seconds]
jglathe_x13s has joined #aarch64-laptops
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
bumble[m] has joined #aarch64-laptops
<craftyguy>
is onboard audio still choppy/popping a lot for folks with 6.9-rc5 and alsa-ucm-conf 1.2.11 ?
<craftyguy>
on the x13s
<craftyguy>
I'm using pipewire/pipewire-pulse, maybe that's the "problem" ?
<craftyguy>
tried setting max-quantum per jhovold's wiki page too :(
jhovold has joined #aarch64-laptops
mcbridematt has quit [Remote host closed the connection]
mcbridematt has joined #aarch64-laptops
jglathe__ has joined #aarch64-laptops
<Jasper[m]>
<craftyguy> "I'm using pipewire/pipewire-..." <- yes
<Jasper[m]>
Switching to regular pulse fixed some issues for me up to a certain point
jglathe_ has quit [Ping timeout: 480 seconds]
<jhovold>
steev: you can use lore to download an mbox of the thread
<krzk>
or b4 mbox...
<jhovold>
it just pulls it from lore
<jhovold>
but yeah, I use b4 for that
<jhovold>
craftyguy: haven't tried pipewire since late last year but I expect it to still be broken
<krzk>
interfaces on user side are different. b4 is command line tool, "use lore" means go to https://lore .... and clicking link there. So obviously both will fetch the same backend, so lore...
<jhovold>
the quantum workaround did work for me back then, but capture was still completly broken
<jhovold>
yeah, i meant use lore using whatever interface you prefer, a user just wanting to reply with a tested by tag does not need to install b4
<steev>
i've just never had any success importing the mbox into thunderbird (which is what i use for work)
<steev>
i'm fine with typing it up in a file and using git send-email
<\[m]>
just had some weird shit again
<\[m]>
I disconnect my docking before I put the laptop to sleep now, so I woke the laptop up plugged the dock, logged in, went away 10min, woke it up again - the external screen doesn't come up
<\[m]>
I then 180´d the usb c, the external screen came up but my internal one got frozen, I've had this before, then I go to displays (have to guess correct name + 3 time down) since the start menu is on the frozen screen
<\[m]>
but this time around, I tried to replug a couple of times and then the system crashed
f_ has joined #aarch64-laptops
f_ has quit [Remote host closed the connection]
f_ has joined #aarch64-laptops
<jglathe__>
last time I tried some combinations on the X13s it was a frustrating day. I try to avoid external display on X13s, only for tests
<jglathe__>
on 6.9rc4 was the last test series, now 6.9rc5
<jglathe__>
can sb shed some light on the orientation-switch witchery? qmpphy has orientation-switch, and usb-sbu-mux has it as well. sbu is only orientation for the sideband channel? and DP?
svarbanov has joined #aarch64-laptops
f_ has quit [Ping timeout: 480 seconds]
craftyguy has quit [Remote host closed the connection]
craftyguy has joined #aarch64-laptops
craftyguy has quit [Remote host closed the connection]
craftyguy has joined #aarch64-laptops
<adamcstephens>
craftguy, jhovold: pipewire is working well for me on my x13s on 6.9rc5
<Jasper[m]>
adamcstephens: I've personally had issues with volumes on the headphone jack above 10%. I'm assuming you don't have this?
<adamcstephens>
i've never tried the headphone jack
<Jasper[m]>
Speakers are generally soft, but that's intended as long as hw speaker protection isn't implemented
<adamcstephens>
yeah the speakers could be a bit louder but it's not bad
<adamcstephens>
there's almost zero bass, but i assume that's the speaker design :)
<Jasper[m]>
adamcstephens: @craftyguy 's issue seems to line up with what I had with the 3.5mm jack so I'm assuming it's about that and not the speakers
<adamcstephens>
i had choppy sound from the speakers in the past
possiblemeatball has joined #aarch64-laptops
echanude has joined #aarch64-laptops
Lucanis has quit [Ping timeout: 480 seconds]
hightower2 has joined #aarch64-laptops
<craftyguy>
Jasper: no, both internal speaker and headphones are choppy for me
<craftyguy>
adamcstephens: I'm curious about your setup.. did you make any additional config to pipewire? Which alsa ucm version:
<steev>
jglathe__: afaik, orientation switching is a patchset but it was only fairly recently submitted (and neither johan nor myself have added the patches afaik)
<HdkR>
Yea, but even on Steam it launches the EA Play stuff
<albsen[m]>
now :)
<albsen[m]>
not for me
<HdkR>
Huh, wonder if this one was special
<albsen[m]>
I bought the ultimate collection they released recently to steam
<albsen[m]>
but also, I have the CD's from back in the day ... steam is just easier
<HdkR>
Well if it doesn't have EA Play launcher it might work. As for Starcraft, I haven't tried any Blizzard games since I didn't want to faff with it :D
<HdkR>
If it is not on Steam then care level plummets
<albsen[m]>
u recon the GPU is strong enough?
<HdkR>
Starcraft 1? Probably
<albsen[m]>
generals or starcraft 2 :)
<HdkR>
Starcraft 2, might be fine on low settings. I remember the game being hard on the my NVIDIA GPU at launch
<HdkR>
I don't know Generals GPU load
f_ has joined #aarch64-laptops
f_ has quit [Remote host closed the connection]
<jhovold>
adamcstephens: interesting, srini also says pipewire is working for him
<jhovold>
at least makes it sounds like there may be some configuration settings that could make it work
<jhovold>
was totally broken here
f_ has joined #aarch64-laptops
<jhovold>
Jasper[m]: the choppy pipewire issue has nothing to do with the volume and any distortion may hear when overdriven whatever it is you are connecting
<jhovold>
you may hear*
<jhovold>
steev, jglathe__: orientation switching supposedly works, the only issue I'm aware of is related to coldplugging
<jhovold>
this is due to the fact that we currently rely on the adsp to report the orientation and it is not up and running when we start usb
<steev>
jhovold: oh, that makes sense
<jhovold>
that may lead to a disconnect and reenumeration in the correct orientation
<steev>
and that would break usb booting
<jhovold>
exactly, was just gonna say that it is related to the problem the distro folks have with getting a usb installer to run
<jhovold>
we have gpio that can be used the orientation in theory we should not need the adsp for this on the x13s
<jhovold>
the patches that were posted only add them to the dt, there is no driver support yet for it
<jhovold>
we have gpios that can be used to determine the orientation*
f_ has quit [Remote host closed the connection]
f_ has joined #aarch64-laptops
f_ has quit [Remote host closed the connection]
f_ has joined #aarch64-laptops
<Jasper[m]>
<jhovold> "Jasper: the choppy pipewire..." <- Yes, but all is fixed up to some point by switching to regular pulse
<Jasper[m]>
I did think the crackling he mentioned had to do with the gain being weird, but apparently not
<Jasper[m]>
(though I guess it's the other issue indeed)
<steev>
6.9 wifi is very unstable, i keep hitting that vdev issue as well
<craftyguy>
ya "just use pulse" isn't a fix though, so I would like to compare notes with someone who has working audio w/ pipewire :)
<Jasper[m]>
craftyguy: I agree hahaha, I'm afraid I lack the knowledge to debug the issue. I don't think anyone here has a fully working setup though sadly.
<jglathe__>
I actually tried them, tlmm 166 and 49. Only good for determining the initial state, however i'm at odds with the qmpphy orientation switch
<bumble[m]>
is it true x13s drains battery significantly while turned off? (reviewers on the internet say it does)
iivanov has joined #aarch64-laptops
<steev>
craftyguy: have you tried the quantum size thing?
<craftyguy>
steev: thanks for the tip, this is MUCH better now. I'm going to add this config to postmarketOS (for the x13s) so hopefully it's usable OOTB :P
<exeat>
craftyguy: Setting quantum=1024 doesn't cure the problem but certainly made a (positive) difference in my testing, when I suggested that workaround at the time. I'm curious if 512 works any better for your applications.
<exeat>
BTW, I think 2048 is the default max quantum so you don't need a setting for that value
<craftyguy>
yeah I can still hear some distortion :(
<craftyguy>
512 is worse
<craftyguy>
seems like the default (for me at least) min/max quantum are 32/1024
<bumble[m]>
<rfs613> "bumble深く傷を: on linux or windows?" <- I've seen reviewers using both linux and windows make this claim, but I also saw somewhere someone using inux changed a bios coniguration and then the x13s could be shutdown without draining battery (supposedly)
<rfs613>
bumble[m]: so i can give you my experience ;-)
<rfs613>
bumble[m]: on windows, out of the box, there was pretty bad battery drain. I got mine well over a year ago so I don't know if this has been fixed in newer units.
<rfs613>
second commant, in admin cmd prompt, POWERCFG /HIBERNATE OFF
<rfs613>
after this, it behaves just like any other windows laptop... close lid, it goes to sleep, only drains a few percent each day. It can sleep for week or two, if not more.
<rfs613>
I tried all possible combinations of settings in the usual windows GUI, but none of them worked.
<rfs613>
It seems that that windows "hybrid sleep" does not work well on X13s (or at least, it was bad when i got mine)
<rfs613>
sorry the correct term may be "Modern Standby" rather than "hybrid sleep"
<rfs613>
i'm not a windows guy ;-)
ungeskriptet is now known as Guest2164
ungeskriptet has joined #aarch64-laptops
Guest2164 has quit [Ping timeout: 480 seconds]
<steev>
woo, v7 of pd mapper seems to be working here, at least the immediate "it's not working" of the battery not showing up isn't manifesting :D
<bumble[m]>
<rfs613> "second commant, in admin cmd..." <- how is battery life when using linux?
jhovold has quit [Ping timeout: 480 seconds]
<craftyguy>
Fine I guess. I regularly get 8hr+
<bumble[m]>
do you know if x13s may one day have suspend working in linux or do you think it is basically unlikely?
<bumble[m]>
all things considered suspend doesn't seem hugely important but it would be nice if somehow it worked in the future
<craftyguy>
s2idle works (kinda). I think power usage is still a bit high though?