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
sjs_ has joined #aarch64-laptops
pstef has joined #aarch64-laptops
checkfoc_us has quit []
checkfoc_us has joined #aarch64-laptops
shoragan has quit [Remote host closed the connection]
shoragan has joined #aarch64-laptops
shoragan has quit []
shoragan has joined #aarch64-laptops
sjs_ has quit [Ping timeout: 480 seconds]
sjs_ has joined #aarch64-laptops
jglathe_ has joined #aarch64-laptops
jglathe_sdbox2 has quit [Ping timeout: 480 seconds]
sjs_ has quit [Ping timeout: 480 seconds]
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
jglathe_x13s has joined #aarch64-laptops
jglathe_x13s has quit [Remote host closed the connection]
jglathe_x13s has quit [Remote host closed the connection]
jglathe_x13s has joined #aarch64-laptops
jglathe_x13s has quit [Remote host closed the connection]
jglathe_x13s has joined #aarch64-laptops
<jglathe_x13s>
up on 6.8-rc3 on X13s
todi has quit []
<jglathe_x13s>
this was the box where arm64.nopauth was missing
todi has joined #aarch64-laptops
<_[m]123>
anything different?
<jglathe_volterra>
if you don't put the parameter in the cmdline it just won't boot, for starters
<jglathe_volterra>
otherwise looks normal, still. Sound is there. Will do another test on 4 lanes on USB-C DP. On 6.7.1 it said the display is there (and behaved accordingly), link training with 4 lanes was successful, but no stream enabled - so it stayed dark.
<jglathe_x13s>
by contrast, my Volterra box has minidp (same driver, sc8280xp-dp) and runs with 4 lanes at 4k@60 for ages.
<jglathe_x13s>
same branch, same OS
<Jasper[m]>
USB-C has more bandwidth per lane I think
<Jasper[m]>
So setup and linktraining may be different
<jglathe_x13s>
same numbers I see
<travmurav[m]>
afaiu alt mode is more or less hardwired dp
<travmurav[m]>
that is, muxed to the usb diff pairs
<jglathe_volterra>
maybe usb_sbu_mux is the issue
<jglathe_volterra>
but I see link training for all 4 lanes
ema has quit [Quit: reboot]
<_[m]123>
maybe the internal display uses something?
ema has joined #aarch64-laptops
<Jasper[m]>
_[m]123: That's hooked up to the eDP port
<Jasper[m]>
s/eDP/mDP/
<_[m]123>
I don't think it's hardware that's limiting
<jglathe_volterra>
no, its some sort of negotiation that fails or an IO
<_[m]123>
so just tested a workaround, I disable the screen in settings when I go afk, seems to work if I resume and thén enable it again
<_[m]123>
#worksforme lol
<_[m]123>
does anyone else actually have that the touchpad buttons are not always engaging? maybe it's just this one?
<_[m]123>
I have to click hard
<HdkR>
Sounds like you have something stuck under it. All five buttons click with relatively light pressure here on the X13s
<HdkR>
er, four buttons even
<jglathe_volterra>
on Volterra its mdss0_dp2, I defined it to sc8280xp-dp
<_[m]123>
ok - but the behavior was from the start
<HdkR>
Could be a defect from factory
<_[m]123>
yeah I already asked for the model part, maybe I backorder
<_[m]123>
it's not clicking like 1 in 4 clicks if I'm gentle -_- good to read though
jglathe_ has quit [Remote host closed the connection]
jglathe_x13s has quit [Ping timeout: 480 seconds]
jglathe_sdbox2 has joined #aarch64-laptops
jglathe_sdbox2 has quit [Remote host closed the connection]
jglathe_x13s has joined #aarch64-laptops
jglathe_ has joined #aarch64-laptops
jglathe_x13s has quit [Read error: Connection reset by peer]
jglathe_ has quit [Remote host closed the connection]
jglathe_x13s has joined #aarch64-laptops
jglathe_x13s has quit [Remote host closed the connection]
jglathe_sdbox2 has joined #aarch64-laptops
jglathe_sdbox2 has quit [Remote host closed the connection]
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
craftyguy has quit [Remote host closed the connection]
craftyguy has joined #aarch64-laptops
<exeat>
I find that the middle button has this problem if I press on its upper right corner
jglathe_sdbox2 has joined #aarch64-laptops
<exeat>
(TBH I'm not a huge fan of the trackpoint system, I'd probably swap the X13 touchpad+buttons for the Z13 forcepad if I could)
<_[m]123>
oh that one is fine for me
<Jasper[m]>
6.8.0-rc3 is in Fedora Rawhide now
<Jasper[m]>
Audio works, but it's still soft, gonna see what clearing alsa state does
KREYREN_oftc has joined #aarch64-laptops
<Jasper[m]>
Okay seems like neither the alsa-ucm-conf changes nor the kernel changes changed anything about audio for me
<Jasper[m]>
Speaker audio is still very soft at most and 3.5mm jack audio has too high of a gain
<Jasper[m]>
I am using Pipewire however, I think most people here that had it working have Pulse
jhovold has joined #aarch64-laptops
<jhovold>
Jasper[m]: yeah, you need to remove your current audio settings to get the defaults
<jhovold>
the alsa state should be cleared in any case to clean out any effect of the codec bug which could have set the digtial speaker gain incorrectly
<Jasper[m]>
jhovold: I did do that, no change
<jhovold>
but you also need to clear out your pulseaudio/pipewire settings if you really want the default settings
<jhovold>
but you could also just lower the gain manually
<jhovold>
so if the headphone gain was too high before, it's not going to change by itself otherwise
<jhovold>
the difference is that the headphone gain was always set at a much too high level before, and then the volume was lowered in software
<jhovold>
resulting in crappy audio
<jhovold>
no, if you turn down the volume in pavucontrol, the actual hardware amplification will be reduced (i.e. not just software volume)
<jhovold>
which is what you want if you have external speakers connected
<jhovold>
specifically, you don't want any software attenuation, and a low hardware volume setting
<jhovold>
with the fixed kernel and ucm files, you can acheive that with pavucontrol, but you could do manually with alsamixer before too
<jhovold>
as for the speakers, the volume is limited at roughly the previous level in order to not risk damaging them
<Jasper[m]>
jhovold: Aha, that makes sense
<Jasper[m]>
jhovold: Okay
<Jasper[m]>
I will try to mess around with headphone gain settings then for pipewire
<jhovold>
easiest way is to just lower the volume in pavucontrol until it sounds good on the external speakers
<Jasper[m]>
I have neither external speakers nor pavucontrol hahaha
<Jasper[m]>
but I'll see about the gain first of all
<jhovold>
best way is to set the volume at 100% in pavucontrol (while not playing anything) and then lower just the hardware amplification in alsamixer until it sounds good
<Jasper[m]>
it gets out of hand after about 10% volume
<jhovold>
ah, ok, i thought you were using external speakers too
<Jasper[m]>
Nope, just regular 'ol earbuds
<jhovold>
yeah, it gets really loud quickly here too
<jhovold>
but 10 % in pavucontrol (or whatever volume control you use) should sound better than what 10% did before as it no longer relies on software attenuation
<Jasper[m]>
Oh yeah it's crystal clear
<Jasper[m]>
<jhovold> "best way is to set the volume at..." <- Which one is the hardware amplification for the headphone jack?
<Jasper[m]>
HPH Type is the only one cranked to 100 in alsamixer atm
<jhovold>
HPHL and HPHR
<jhovold>
(or HP to control both)
<Jasper[m]>
alsamixer says they're both set to 0
<Jasper[m]>
HP aswell
<jhovold>
default setting is now 2 (-27 dB), it used to be set at level 20 (0 dB)
<jhovold>
then you have them at the lowest level already
<Jasper[m]>
Then I'm not entirely sure what's going on
<Jasper[m]>
are these earbuds too sensitive? lol
<Jasper[m]>
or is the amp too good
<jhovold>
I end up using setting 1 here too, maybe 0 as well
<Jasper[m]>
That would make it louder no?
<jhovold>
1 is louder than 0, yes
<Jasper[m]>
:/
<jhovold>
but i'm using a proper pair of headphones
<Jasper[m]>
I'll grab my 3W pair of cans
<jhovold>
setting 2 sound good, loud, but not deafening
<jhovold>
i could easily use setting 0 as well, still fairly loud
<Jasper[m]>
Okay the hard to run cans have the same issue
<Jasper[m]>
It's distorted from 10% onwards
<Jasper[m]>
Like it's less loud as expected, but it starts crackling from 10% onwards
<jhovold>
this is with a pair of Bose QC45 (too much bass, but that's Bose...)
<Jasper[m]>
I'm using Fostex T40RP's
<Jasper[m]>
they have low impedence but they require a lot of amplification
<Jasper[m]>
that shows with the X13s, but the problem isn't that
<Jasper[m]>
it just gets distorted
<jhovold>
i have the setting at the default 28% (hw amplication 2)
<jhovold>
sounds good, but definitely starts breaking up I move towards level 10
<jhovold>
as I
<Jasper[m]>
I may not be explaining this properly out of ignorance
<Jasper[m]>
the whole time HP is set to 0
<jhovold>
not using pipewire here, there are playback issues with pipewire but you should here that on any volume level (so i assume you have the quantum workaround in place)
<Jasper[m]>
When I change pipewire related settings to something above 10% it starts crackling
<Jasper[m]>
I will try the quantum thing
<jhovold>
crackling is indeed what you get in pipewire without the workaround (or too fast playback)
<Jasper[m]>
did that, no difference
<jhovold>
did you clear out the old state?
<Jasper[m]>
I did before
<jhovold>
properly? it gets recreated unless you stop the alsa state service *before* deleting it, etv
<jhovold>
etc
<Jasper[m]>
I did it thrice, exactly as listed in your wiki page
<jhovold>
ok, good
<jhovold>
and what does 'amixer sget "RX_RX0 Digital"' say?
<Jasper[m]>
Not found, but that may be because it tries to find that for the pipewire card
<Jasper[m]>
alsamixer says 22
<Jasper[m]>
at least the setting for it
<jhovold>
yeah, you probably need to run it as root
<Jasper[m]>
amixer: Mixer attach default error: Host is down
<Jasper[m]>
huh
<jhovold>
hmm, should be 84 (0 dB)
<Jasper[m]>
as root that is
<Jasper[m]>
had to specify the card
<Jasper[m]>
that command says it's 84 indeed
<jhovold>
good
<jhovold>
assuming pipewire works as pulseaudio, you should be good, it's always possible to generate distorted sound with software amplification
<Jasper[m]>
I'm guessing that's where the problem resides
<Jasper[m]>
I need to figure out how that's set up, it's a bit unclear to me how that's handled with pipewire
<jhovold>
try switcing to pulse audio, perhaps? steev said it may be hard to do if you use gnome, perhaps depending on your distro
<jhovold>
failry straight forward here, just uninstall pipewire and install the corresponing pa packages
<Jasper[m]>
pactl still says pipewire is in charge hahaha
<Jasper[m]>
I rebooted, let's see if that fixes it
<Jasper[m]>
now I have no sound at all
<Jasper[m]>
interesting
<Jasper[m]>
Okay, that does make it a little bit better, but still not quite
<Jasper[m]>
loudness fluctuates a lot like it's giving up sending the fully amplified signal
<Jasper[m]>
and at some point it just gives up sending sound entirely
<Jasper[m]>
If I do pulseaudio -k it'll work for a bit afterward with the problem I mentioned (plus it being distorted from ~50% pavucontrol volume and onwards) and then it just stops working again
<Jasper[m]>
user service says:
<Jasper[m]>
`Failed to create sink input: sink is suspended.`
<Jasper[m]>
Ah that's a different issue with suspend-on-idle
<Jasper[m]>
Okay actual music sounds okay up until 50% volume now
<Jasper[m]>
that's more serviceable
<Jasper[m]>
after that you get the same issue as before where it gets distorted
<_[m]123>
super weird, dis- and reconnecting the hdmi also disconnects the usb ports on the dock 😲
<_[m]123>
pavucontrol still can't connect hmm did I somehow reinstall pipewire?
<_[m]123>
so the kernel came out in fedora ?
<_[m]123>
yesterday I noticed some other bug with kodi where audio was stuttering but playing in vlc was ok
<_[m]123>
trial and error but generally more than usable - it's just sometimes you're like ARGH linux why so much cnfig
<HdkR>
Apparently soem docks are super rude and will throw a whole USB reconfigure event with HDMI/DP replugging. Which sounds nutty but I guess it makes sense with the expected lane reconfigurations.
<Jasper[m]>
_[m]123: yes
<jglathe_volterra>
feels like you're not supposed to plug/unplug anything when DP or HDMI is involved
<_[m]123>
so rude
<_[m]123>
usb and hdmi interfere ? they share the same lanes?
<_[m]123>
how does that work anyway, are logical buses encapsulated - like multiple ones per lane?
<_[m]123>
or it's like ethernet frames with headers n shit
<HdkR>
USB 20gbit was the first to introduce dual-lane operation. So everything on these 10gbit ports share the single lane
<HdkR>
I'd guess some docks need to do some phy switcharoo magic depending on configuration, but I'm not in that embedded world :D
<jhovold>
Jasper[m]: so you're saying it's working with pulseaudio?
<jhovold>
getting distortion when turning the volume up hig
<jhovold>
high is expected
<jhovold>
perhaps we can cap it at some level if there's an argument to be made that it's not useful for anyone above that level, but we leave that to the user for now
<jhovold>
_[m]123: basically pipewire is not supported on the x13s, but there is a workaround for playback (see the wiki)
<jhovold>
hopefully someone will have time to look into this soon
<jhovold>
sorry, maybe I misread you message about kodi, if you hear stuttering also with pulseaudio then that seems to be a different issue
<steev>
playback is fine, with the workaround, mostly, it's just hte mic that isn't. and i do plan to work on it once i get my install back up to snuff
<_[m]123>
> 3 weeks of configuration later
<_[m]123>
😄
<_[m]123>
i had switched to pulseaudio
<_[m]123>
i thought
<_[m]123>
but last time I was updating and saw again some pipewire libs -_-
<Jasper[m]>
<jhovold> "Jasper: so you're saying it's..." <- It's working _better_ not very good still
<Jasper[m]>
On volume changes it still crackles a lot
<Jasper[m]>
And it distorts after 50% this time
<Jasper[m]>
<jhovold> "getting distortion when turning..." <- And with distortion I don't mean that it's loud
<_[m]123>
maybe try clearing alsastate again and reboot/
<_[m]123>
s///?/
<Jasper[m]>
The Headphones are not giving up, they're normally amplified MUCH more
<Jasper[m]>
_[m]123: Yeah could try, have done it with the pulseaudio setup before
jglathe_volterra has quit [Remote host closed the connection]