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)
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
<cenunix[m]>
are you having issues with the GPU martiert, the gpu still works for me although I do get some errors like you mentioned, on NixOS
<jhovold>
martiert: i believe juergh posted a patch adding the missing module macros for the gpu fw
<jhovold>
Here's an updated wip branch for the X13s based on 6.4.1:
<clover[m]>
Oh was gdb broken on X13s? I don't use lower level languages so I didn't notice
<jhovold>
juergh: ok, maybe time to drop the hack soon then. I knew they were testing something, but have not heard that they had given up on it.
<jhovold>
i'll double check with lenovo as well before dropping it
<konradybcio>
the main point of using the cores ending in C was to have pauth, so it would be nice indeed :P
Kelsar has joined #aarch64-laptops
<konradybcio>
jhovold: could you test a quick venus patch for me if I emailed it to you?
laine has joined #aarch64-laptops
<clover[m]>
jhovold: how do you test your kernels? Since there is no vm do you have to build, install and reboot?
apalos_ has joined #aarch64-laptops
<jhovold>
konradybcio: sure, but i may not have time to test it tomorrow
<konradybcio>
jhovold ah okay I'll test it earlier myself then, thanks anyway
<jhovold>
clover[m]: yes, but i use different machine for development
mani_s- has joined #aarch64-laptops
<jhovold>
and for some things i can just update and reload a module or two
<steev>
clover[m]: i tend to tag them ( LOCALVERSION="-testing-thing" ) and then manually point at the dtb
<steev>
jhovold: srinik: any idea why headphones are so friggin loud, and speakers are so friggin quiet?
<jhovold>
steev: mixer settings? ;)
<steev>
possibly... or maybe some devices are swapped somewhere?
<steev>
but my mixer settings are defaults, and with the headphones at ~10% they're pretty much louder than the speakers
<steev>
with the speakers at 100%
<jhovold>
i think we had to set some defaults and if you crank the speakers up to loud we have a distortion issue
<steev>
yeah, headphones too... above ~25%
<jhovold>
i haven't really been using headphones except when fixing the headphone output race, but i did not notice that you could turn up the default headphone volume to what appeared to be non-healthy levels (for ear and headphones)
<broonie>
steev: Headphone drivers are typically also usable as line outputs, but the volume levels you want for the two applications are wildly different (headphones typically have -20dB or more, line output should usually be around 0dB so you don't loose resolution).
<steev>
broonie: hm, let me look at that in pavucontrol or whatever, gnome doesn't really let you dig into that, it seems
<broonie>
It's likely that the hardware defaults are just wrong and need tuning. You can also get some effects due to different headphones, and someone might test by using the headphone out to drive speaker.
<broonie>
s
<steev>
hm
<steev>
so, according to pavucontrol, 100% volume is 0.00dB, and yeah, it's quite loud and there's resolution loss. 45% is -20.87 dB, and it's still quite loud and still quite a bit of audio loss. 22% is -40.00 dB and that's where i'd say that the headphones are "comfortable"
<steev>
so i guess i just need to dig through alsamixer and figure out where that correlates?
<broonie>
Yes, probably there's some volume control directly on the headphone output. -40dB sounds like a typical value for headphone output ain.
<broonie>
gain
<konradybcio>
i think my x13's battery is dying after 3 months
<konradybcio>
the % jumps around in linux a bit and the closer-to-me right corner of the bottom plate is mushy..
<konradybcio>
also I think linux underdischarges the thing..
<konradybcio>
or I guess overdischarges would be more english
ptitSeb has joined #aarch64-laptops
ptitSeb_ has quit [Ping timeout: 480 seconds]
systwi has quit [Ping timeout: 480 seconds]
systwi has joined #aarch64-laptops
derzahl has quit [Ping timeout: 480 seconds]
<cenunix[m]>
steev check in alsamixer, SpkrLeft PA and SpkrRight PA
<steev>
cenunix[m]: i've seen those, and tested as well, but there's definitely resolution loss when turning them up
<cenunix[m]>
ah yes, well not sure then tbh, but I also have noticed the speaker headphone discrepancy. Headphones will blow your ears out at 50% but speakers are super quiet
<cenunix[m]>
a bit off topic, but whats the best way to set the 'bluetooh address' each time the x13s boots, I would assume a systemd service? but what program/script should I use to set it? btmgmt?