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
lucanis has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
anthony25 has quit [Quit: Quit]
anthony25 has joined #aarch64-laptops
<craftyguy>
hmm with jhovold's 6.14-rc2 on the x13s, I get this message printed in dmesg multiple times per second: [drm] Loaded GMU firmware v3.1.10
<craftyguy>
anyone else running that kernel see this?
<robclark>
craftyguy: normal.. there was a patch posted to print it only the first time instead of every time the gpu resumes (but I've not had a chance to pick it up)
sally has joined #aarch64-laptops
weirdtreething has quit [Read error: Connection reset by peer]
weirdtreething has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<craftyguy>
it's normal to print that a few times _per second_ and spam the kernel long for as long as it's booted? Haha
<craftyguy>
I don't think this happened on 6.13
<craftyguy>
Glad to hear there's a patch though to improve it 😁
tobhe has joined #aarch64-laptops
<robclark>
turns out the gpu wakes up a lot
tobhe_ has quit [Ping timeout: 480 seconds]
<craftyguy>
yeah no kidding
<craftyguy>
is it loading that fw from disk every time it wakes up?
chrisl has joined #aarch64-laptops
haver_ has joined #aarch64-laptops
hexdump0815 has joined #aarch64-laptops
<robclark>
no
hexdump01 has quit [Ping timeout: 480 seconds]
<robclark>
it is just informing dmesg each time ;-)
haver has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
mbuhl has quit [Remote host closed the connection]
mbuhl has joined #aarch64-laptops
mbuhl has quit [Remote host closed the connection]
mbuhl has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
anthony25 has quit [Quit: Quit]
anthony25 has joined #aarch64-laptops
lucanis has quit [Read error: Connection reset by peer]
icecream95 has joined #aarch64-laptops
<icecream95>
What bwmon actually supposed to do?
<icecream95>
It is meant to change the interconnect bandwidth and not just monitor what's happening, right?
<icecream95>
'cause it seems to be that the opp changes from the driver have no effect.
<icecream95>
That would certainly explain why programs using a lot of memory bandwidth run slowly compared to Windows, and perhaps also why power usage is higher than it could be?
<icecream95>
But I assume that *something* is changing the bandwidth, or else I don't know how to explain the weird behaviour with the performance governor
<icecream95>
Also what do the per-cluster bwmon instances measure? Are they meant to control bandwidth between the cores and L2, or between L2 and LLC?
<icecream95>
Time to switch back to Windows to see what happens there...
<icecream95>
Hmm, I can't see a major difference between Windows and Linux behaviour, except that bw is higher on Windows
<icecream95>
Um, why does sleep 1 in WSL not return? Why does clock_gettime jump 300 seconds between calls? Surely it couldn't be that... Windows is affected by the CNTVOFF bug as well?
<icecream95>
I can't seem to reproduce it, though :(
<icecream95>
It seems that the trigger might be: `wsl --terminate $Distro`, then start `wsl anycommand` and do `wsl --shutdown` before it finishes starting up again
<icecream95>
But perhaps that race needs to be timed precisely? I managed to cause some "catastrpohic error" where WSL wouldn't start, but nothing more since then.
chrisl has joined #aarch64-laptops
<icecream95>
I've probably written more than enough spam today... end I didn't learn much other than: Nothing makes sense!
icecream95 has quit [Quit: rcirc on GNU Emacs 29.1]
chrisl has quit [Ping timeout: 480 seconds]
SpieringsAE has joined #aarch64-laptops
<SpieringsAE>
my clonezilla backup thing seems to have worked, I didn't really expect it, but yep, even windows still works
SpieringsAE has quit [Read error: Connection reset by peer]
anthony25 has quit [Quit: Quit]
anthony25 has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
SpieringsAE has joined #aarch64-laptops
jglathe_volterra has quit [Remote host closed the connection]
<SpieringsAE>
I guess that means it is now time to ship this thing back to asus toget a fully working one
<SpieringsAE>
:(
SpieringsAE has quit [Remote host closed the connection]
jhovold has joined #aarch64-laptops
SpieringsAE has joined #aarch64-laptops
laine has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<SpieringsAE>
Has anyone with the lenovo t14s investigated the hdmi port a bit? I have this patch trying to get something working on the asus: