ChanServ 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
chrisl has quit [Ping timeout: 480 seconds]
shoragan has quit [Read error: Connection reset by peer]
shoragan has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
shoragan has quit []
shoragan has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
<clover[m]>
13 inches is such a great form factor
<clover[m]>
I think the x13s is a bit more than 13 maybe like 13.3 inches?
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
<angeloverlain[m]>
<JensGlathe[m]> "anthony25: This one I guess..." <- I thought you also had a tree ?
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
<JensGlathe[m]>
Yes, mine was based on Johan's. Currently (*) on sgerhold's which was based on Johan's. When I start doing 6.17rc, it will be the mentioned one plus.
<SpieringsAE>
same, now I just have the regular kernel plus whatever I find interesting for the asus vivobook in particular. Though I hope that when I get these latest display things merged I can just start running mainline
<SpieringsAE>
ayy video clock controller just got fully applied
<SpieringsAE>
Hmm, x plus or elite? I've not really had any usb issues with the kernels that I've built, I've not had it overheat yet, but given the fans barely spin it is not entirely unlikely to happen
<SpieringsAE>
yeah the function keys are weird, somebody here made a bpf program to get more of them working, didn't try that out yet
<SpieringsAE>
keyboard rgb is very likely part of the embedded controller so yeah...
<SpieringsAE>
Can't really say I notice anything weird about low brightness, but I am very bad at judging that sort of stuff
SpieringsAE has quit []
SpieringsAE has joined #aarch64-laptops
<angeryboi[m]>
X elite
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
Ariadne has quit [Remote host closed the connection]
chrisl has joined #aarch64-laptops
<jdb[m]>
I've had this issue of adb working on one USB port but not on the other one, on the X13s
icecream95 has joined #aarch64-laptops
<jdb[m]>
With the 6.16 kernel from Debian Experimental, I've also discovered that I need to unplug and replug my dock to get the external screen detected on cold boot (X13s too)
<icecream95>
angeryboi[m]: Yep, I've noticed the display weirdness, and so mostly keep it at maximum brightness, using a shader to adjust apparent brightness (this also reduces 240Hz flicker)
<jdb[m]>
And if I unplug the external screen when the device is in sleep mode, opening the lid wakes the device but it still believes that the external screen is here -> it's tricky to fix when you've set the primary as the external one :-) Hopefully I'm running Xorg so I could type a randr command
<icecream95>
The display also seems a bit weird in Windows, so in some games it is really hard to see anything...
Ariadne has joined #aarch64-laptops
Ariadne has quit [Remote host closed the connection]
<jdb[m]>
So there are still a few wonky issues with the USB ports
Ariadne has joined #aarch64-laptops
<angeryboi[m]>
My biggest issue from the list is inability to charge the laptop, other issues are more or less manageable
<angeryboi[m]>
(Maybe a dedicated charge port is not so bad, huh)
<icecream95>
For charging issues, do you have adsp firmware copied over from Windows?
chrisl has quit [Ping timeout: 480 seconds]
<icecream95>
For the display, it also seems that the red channel has a different response time to green and blue at low brightness, and very dark but not true black backgrounds are not uniform across the display, which are both a bit distracting, but I assumed that it might just be inherent to OLED
<angeryboi[m]>
icecream95: I ran the firmware utility for firmware, so I assume so.
harrisonvanderbyl has joined #aarch64-laptops
ravikant_ has joined #aarch64-laptops
<harrisonvanderbyl>
Yay, got the UFS working on the sp12, can now actually ditch the USB drive now ahhah, now I think the only thing left is the audio, ubc-hdmi, and fixing a couple odd gpios
<icecream95>
angeryboi[m]: huh. dmesg output might be useful
chrisl has joined #aarch64-laptops
<angeryboi[m]>
If dmesg still has logs for firmware tool at this point
<JensGlathe[m]>
harrisonvanderbyl nice
<JensGlathe[m]>
The 2 weeks are almost over now
<JensGlathe[m]>
And UFS, although not used often, is good to have working example
<harrisonvanderbyl>
Yeah, luckily found some working snippets from the magicbook dts, there's at least 3 devices that would benefit from the UFS node
<jdb[m]>
harrisonvanderbyl: very nice indeed! Did you have to include non-mainstream patches or was it a matter of enabling UFS in your devicetree?
<harrisonvanderbyl>
No extra upstream, just a matter of porting some devicetree stuff and wasting time not understanding how things work
<harrisonvanderbyl>
Actually hmm
<harrisonvanderbyl>
I am based of JensGlathe kernel
<harrisonvanderbyl>
And I did end up enabling qcomufs in the config
<jdb[m]>
angeryboi: no need for the firmware tool log, just the regular log will tell if the adsp firmware Is properly loaded on boot or missing from its expected location on the filesystem
chrisl has quit [Ping timeout: 480 seconds]
<jdb[m]>
I remember I had to add a script on boot to enable its proper activation btw
<harrisonvanderbyl>
Asap and cdsp and purwa need a patch to work on some devices that's not on mainstream
<harrisonvanderbyl>
I think
<harrisonvanderbyl>
It's in Jen's repo tho
chrisl has joined #aarch64-laptops
<jdb[m]>
You can try one of these 2 manual commands:
<angeryboi[m]>
I couldn't execute either of these commands as I need to setup root account, but idk what changed as charging works now, I checked dmesg and adsp seems to start properly, maybe it's a different issue. Could be something to do with sleep and/or overheating.
chrisl has quit [Ping timeout: 480 seconds]
<JensGlathe[m]>
Re weird brightness issues: There is a [regression](https://github.com/jglathe/linux_ms_dev_kit/issues/46) due to a T14s hack for OLED that needs to be removed. 6.16-el2-jg-2 is the first of my kernels that has it removed.
longptr has quit [Ping timeout: 480 seconds]
longptr has joined #aarch64-laptops
<jdb[m]>
Great if charging works!
chrisl has joined #aarch64-laptops
<angeryboi[m]>
Also, I know why the laptop might overheat
<angeryboi[m]>
If OS goes to sleep while charging, fans will stop spinning
<angeryboi[m]>
And considering keyboard rgb doesn't turn off either, it could be some weird state the laptop ends up in
harrisonvanderbyl has quit [Quit: Connection closed for inactivity]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
KREYREN_oftc has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
ravikant_ has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
ravikant_ has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
<erebion_muc>
Anyone else having issues with the X13s with key presses occasionally not being recognised for a a couple seconds and the mouse (touchpad/trackpoint) sometimes not being able to click anythng for maybe a minute and then just working again..?
chrisl has quit [Ping timeout: 480 seconds]
<erebion_muc>
I often have to press enter around 20 times before it reacts
<erebion_muc>
And the 3rd keyboard layer with Alt Gr has stopped working
<erebion_muc>
6.12.38+deb13-arm64
<erebion_muc>
Debian Issue or Kernel Issue?
chrisl has joined #aarch64-laptops
<jdb[m]>
Not so far for me. However I've moved on to more recent kernel versions from Experimental, 6.15 for a while and now 6.16 for a few days
<krzk>
erebion_muc: that's quite old kernel, so first advice is try to reproduce it on something recent
chrisl has quit [Ping timeout: 480 seconds]
<glu>
speaking of x13s, did suspend/resume support improve recently?
<JensGlathe[m]>
Working fine for me for a long time now. Only thing out of line is WWAN having issues after suspend
Kelsar has joined #aarch64-laptops
<erebion_muc>
Update: I had a stuck backspace key -.-
chrisl has joined #aarch64-laptops
<erebion_muc>
So if anyone else has issues with keys, try removing and re-attaching them...
<glu>
but what about it not entering lower power states? last time i tried it worked (with flaws) but it would drain battery overnight still
craftyguy has quit [Read error: No route to host]
craftyguy has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
xeliteCJF has joined #aarch64-laptops
<tobhe[m]>
This is more likely not related to power states but individual power consumers not being turned off before "sleeping"
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
harrisonvanderbyl has joined #aarch64-laptops
<harrisonvanderbyl>
I found it doesn't detect charging if the glink USBs are set to "host", but if you set to "dual" then it can switch to allow charging (at least on sp12)
<JensGlathe[m]>
what
<harrisonvanderbyl>
In the device tree, in the section where the glink defines the USB section, where it has "role=X" if role is set to host, then it doesn't detect USBC charging, and just runs out of charge when plugged in, but if I change that to "dual" it detects that it is plugged in and charges
<JensGlathe[m]>
yeah I know, but there's a power-role and data-role
<harrisonvanderbyl>
i wonder how power-on-demand chargers get the voltage data from the device
<harrisonvanderbyl>
I moved all my stuff to the UFS, no more USB sticking out the side anymore :)
<harrisonvanderbyl>
I'll put through a pr for the UFS node
xeliteCJF has quit [Read error: Connection reset by peer]
paulk has quit [Remote host closed the connection]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<bamse>
harrisonvanderbyl: in usb type-c you have a couple of wires where power-delivery (PD) messages are exchanged between the involved parties...
<bamse>
harrisonvanderbyl: they are used to establish who's sink and who's source, for data and for power independently
<bamse>
harrisonvanderbyl: in that process the source discloses what power levels are supported and the sink request a particular level - and can change that later if needed
<harrisonvanderbyl>
Would setting the data mode for the charger port as "host" in the DTS prevent that from taking place?
SpieringsAE has quit [Quit: SpieringsAE]
<harrisonvanderbyl>
Or is it just more that having the incorrect setting prevents a driver or two from booting correctly
<bamse>
setting the data mode shouldn't affect that, as you can have power and data go in different direction...
<bamse>
so i wonder if role=host tells the software that both data and power should be host/source?
<bamse>
without looking at the code, that would be my expectation
<clover[m]>
Got my archiso to boot today on the wdk2023!
<Jasper[m]>
Awesome stuff!
<Jasper[m]>
I still need to try and get some stuff running on mine
chrisl has quit [Ping timeout: 480 seconds]
<anthony25>
JensGlathe[m]: thanks for recommending the Linaro's branch, it works great!
<clover[m]>
Still a few things to iron out but should have a archiso release with including a new iso for volterra in the next day or so
chrisl has joined #aarch64-laptops
ravikant_ has quit []
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
<bamse>
anthony25: is there anything in that branch that you actually need compared to v6.17-rc1 (well, there's a bug in the firmware loader there...but -rc2 should be good)
<anthony25>
Actually all the firmware bins are loading fine
<bamse>
anthony25: pacman -S linux-aarch64 or linux-aarch64-rc should work fine btw, that's what i run on my sc8280xp and x1 devices
<anthony25>
Oh wow ok, I'll try 6.16 when it'll ship on Tumbleweed
chrisl has quit [Ping timeout: 480 seconds]
harrisonvanderbyl has quit [Quit: Connection closed for inactivity]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<anthony25>
bamse: and to answer your question, there is the iris hw decoding that I'm applying on this branch
<anthony25>
and the EC driver for the slim 7x
<anthony25>
even if, about the hw video decoding, iirc someone here was saying that ffmpeg needs a patch to actually use it?