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)
<bamse>
shawnguo: "gave up" and installed networkmanager...damn it was convenient to get the wwan stuff up :)
<steev>
for shame. you're supposed to be a greybeard sir
<bamse>
steev: i got plenty of other things causing that effect ;P
<steev>
same
<steev>
my boss submitted an absolutely massive merge request right before heading to vacation and.... i missed a bunch of breaking changes
<bamse>
hehe
<steev>
qemu is also being a piece of shit and crashing on arm now that arm64 is fixed
<bamse>
and fyi, i did a whole bunch of testing on the 8cx yesterday, and i don't think cpufreq works...
<bamse>
previously i just tested at powersave vs performance governor and saw some change
<bamse>
but yesterday i ran dhrystone on each frequency and was expecting to see some correlation, but after the first 3-4 frequencies, it's mostly random
<steev>
oh that's weird
<steev>
i haven't looked at the new stuff recently
<bamse>
we did see something similar on 845 with the thermal thing, which lmh fixed...but i don't know what's going on
<steev>
lenovo just reused the 845 stuff on the 5g :P
<steev>
when in doubt, i'll always blame the vendor
<bamse>
nah, because i tested this on the primus device...
<bamse>
and it doesn't get past ~37-38C...the yoga was capping somewhere around 60-65C
<bamse>
which is more reasonable for an overly concervative configuration
<bamse>
so, one more thing to put back on the todo list
<steev>
maybe you just need to push it harder/
<bamse>
write the register twice? ;)
<steev>
i'm currently trying to find a missing '
<steev>
and it's hiding itself *very* well
<steev>
found it. it was in a friggin comment
<bamse>
steev: on my second c630, sometimes when it's idling it does so by providing a constant stream of SYSRQ from the keyboard...is this something you have seen or heard anyone else have problems with?
<steev>
i have not seen that, no, haven't heard either
<bamse>
wonder if there's electrical variations...or if the EC is acting up
<shawnguo>
bamse: yeah, and modem-manager-gui makes it even more convenient!
iivanov has joined #aarch64-laptops
iivanov_ has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
iivanov_ has quit []
iivanov has joined #aarch64-laptops
maz has quit [Read error: Connection reset by peer]
maz has joined #aarch64-laptops
iivanov has quit [Remote host closed the connection]
<steev>
hey bamse, next time you come back from suspend and the cursor stops work, try hitting the touchpad button (f6/fn+f6)
<steev>
i did it on a whim and it started working
<robclark>
what does f6 do?
<steev>
mostly because i hit it the other day while trying to do something... and rebooted, and noticed the touchpad wasn't working after reboot either
<robclark>
presumably it isn't the "fix your cursor" key :-P
<steev>
it's the disable/enable touchpad button on the c630
<robclark>
hmm, ok.. so maybe hiding/reshowing cursor "fixes" it?
<steev>
not sure, was just something i noticed as i never actually hit it before
<steev>
i was trying to change something in htop i think it was, which uses f6 for the settings
<robclark>
next time you have it in the no-cursor state, take a look at /sys/kernel/debug/dri/0/state and see if it thinks there is a cursor plane or not.. cursor is probably 64x64
<steev>
i cna
<steev>
doesn't happen often because there's a bug with upower and it won't suspend if i unplug it unless i restart upower
<steev>
at least, when i have it set to never suspend when on mains, and suspend when on battery
<steev>
i swear i had patched that at some point
<gwolf>
Yes, I have used the Fn-F6 thingy several times
<gwolf>
Only once it didn't work -- once I used the C630 fully folded (tablet-mode), and switched the display to vertical, and back, several times
<gwolf>
and... it seems the cursor plane did get completely lost. I was able to navigate the PDF reader using touchscreen events, though
<gwolf>
anyway... killing sway and restarting it fixed the issue. And I did too many changes to be able to pinpoint what I did odd.
<gwolf>
(FWIW, do you know how to read the gyroscope events? I am _almost_ sure they worked under Gnome, but I don't want that thing installed in my system)
<robclark>
I'm not aware of any reports of missing cursor on CrOS (and it's the sort of thing I would hear about if it was happening).. but it could be that CrOS compositor follows a different sequence.. the $debugfs/state file should make it reasonably clear if it is a driver or userspace bug
<gwolf>
(re: gyroscope: I'll check via iio-sensor-proxy)