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
<steev>
clover[m]: you can try grabbing my hack and applying it again
Erisa has quit [Remote host closed the connection]
Erisa has joined #aarch64-laptops
Erisa has quit [Remote host closed the connection]
Erisa has joined #aarch64-laptops
Erisa has quit [Remote host closed the connection]
Erisa has joined #aarch64-laptops
Erisa has quit [Read error: Connection reset by peer]
Erisa has joined #aarch64-laptops
Erisa has quit []
agl7-x13s-eos has joined #aarch64-laptops
Erisa has joined #aarch64-laptops
Lucanis has quit [Read error: Connection reset by peer]
Lucanis has joined #aarch64-laptops
hightower3 has joined #aarch64-laptops
hightower2 has quit [Ping timeout: 480 seconds]
agl7-x13s-eos has quit [Quit: Leaving]
sally has joined #aarch64-laptops
<leezu>
I've noticed recent chromebooks (eg. asurada series) no longer support closed case debugging (CCD). Does someone know the reason? I tried connect SuzyQ to a asurada-spherion and just got a few usb errors (usb 1-1.3: device descriptor read/64, error -32, usb 1-1.3: Device not responding to setup address., usb 1-1.3: device not accepting address 30, error -71), so it does seem
<leezu>
something is responding (though indeed clearly CCD does not work)
djakov has quit [Remote host closed the connection]
<robclark>
leezu: ccd is only supported on one of the two usb-c connectors and one of two possible plug orientations.. but as far as I'm aware it should still be supported
djakov has joined #aarch64-laptops
xypron has quit [Quit: xypron]
xypron has joined #aarch64-laptops
matalama has joined #aarch64-laptops
sally has quit [Remote host closed the connection]
sally has joined #aarch64-laptops
sally has quit [Remote host closed the connection]
hexdump01 has joined #aarch64-laptops
sally has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
sally has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
matalama has quit [Quit: Connection closed for inactivity]
<travmurav[m]>
(yes, internet archive, the aser thing seems to have flopped hard...)
<Jasper[m]1>
@clover in its current setup the speakers work perfectly, headphones are currently amplified too much, that was better before when the volume still had issues
<clover[m]>
<Jasper[m]1> "@clover in its current setup the..." <- cool. i don't use the headphoens much but if you do, steev has a patch available to reduce the amplification
<Jasper[m]1>
clover[m]: Guessing I can build that with your pkgbuild then?
<clover[m]>
Sure
<agl7-x13s-eos>
clover[m]: I have running Steevs Kernel 6.4.3 under EndeavourOS. Must I use the rc-kernel to have and setup sound?
<agl7-x13s-eos>
clover[m]: Under EndeavourOS I have only a dummy-device for the sound.
<clover[m]>
Yes because the also configuration I shipped yesterday has changes
<clover[m]>
Sorry you need to switch h to rc
<clover[m]>
s/also/alsa/
<agl7-x13s-eos>
clover[m]: CanI use the PKGBUILD in x13s-alarm/linux-x13s-rc to get/compile the Kernel?
<steev>
the good news is, we only have about another month or so of rc
baozich has quit [Remote host closed the connection]
baozich has joined #aarch64-laptops
agl7-x13s-eos has quit [Quit: Leaving]
agl7-x13s-eos has joined #aarch64-laptops
<agl7-x13s-eos>
clover[m]: I have now "Linux EOS-x13s 6.5.0-rc3-0-x13s-rc+ #1" running. What have I to do to get sound? I have always the "Dummy Output" device.
<agl7-x13s-eos>
Or is it in the wiki?
<agl7-x13s-eos>
There is Audio, but when I click on "also...." i get the Error 404
<agl7-x13s-eos>
s/also/alsa/
<agl7-x13s-eos>
clover[m]: I see the alsa... in x13s-alarm ....
agl7-x13s-eos has quit [Quit: Leaving]
agl7-x13s-eos has joined #aarch64-laptops
xypron has quit [Ping timeout: 480 seconds]
<agl7-x13s-eos>
clover[m]: I have it installed (alsa-ucm....) but it seems there is more to do. I get always the "Dummy Output" device.
<agl7-x13s-eos>
I have never to do something with sound.
agl7-x13s-eos has quit [Quit: Leaving]
agl7-x13s-eos has joined #aarch64-laptops
<clover[m]>
it's a doozy of an update for sure. you will also need the latest x13s-firmware package because they changed the name and path of the topology firmware file
<clover[m]>
yeah will need alsa-ucm-conf-git-x13s as well
<clover[m]>
you have the right kernel yes
<clover[m]>
me and jasper did it today so it should work on your device if you have all of the latest and greatest packages from my repo
<steev>
clover[m]: fwiw, a pull request went out to create a symlink to the old position
<steev>
but it does need to have the latest version of it
<clover[m]>
lol
laine has joined #aarch64-laptops
matalama has joined #aarch64-laptops
agl7-x13s-eos has quit [Quit: Leaving]
laine has quit [Ping timeout: 480 seconds]
agl7-x13s-eos has joined #aarch64-laptops
xypron has joined #aarch64-laptops
agl7-x13s-eos has quit [Quit: Leaving]
matalama has quit [Quit: Connection closed for inactivity]