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
hightower3 has joined #aarch64-laptops
shoragan has quit [Quit: quit]
shoragan has joined #aarch64-laptops
hightower2 has quit [Ping timeout: 480 seconds]
shoragan has quit [Read error: Network is unreachable]
shoragan has joined #aarch64-laptops
matalama has quit [Quit: Connection closed for inactivity]
matalama has joined #aarch64-laptops
alpernebbi has quit []
alpernebbi has joined #aarch64-laptops
<_[m]1>
<Jasper[m]> "It still crashes after filling..." <- luks1?
<Jasper[m]>
To play it, install by clicking subscribe and wait for it to download, use "offline with bots" and select workshop maps. It should do the benchmarking automatically including some metrics.
<clover[m]>
Does anyone else with a modem x13s have issues with their wlan device coming up on boot? I've had these issues.
<clover[m]>
rebooting usually fixes it.
<Jasper[m]>
I only have wlan issues when it's in low power mode for a while
<Jasper[m]>
Like locked, screen off but power button lit
<konradybcio>
the led will not go off until we reach actual RPMh sleep
<konradybcio>
which means "the power lines that keep the logic on the soc up are shut down"
<konradybcio>
"or at least put to sleep mode"
<clover[m]>
playing with fex-emu today. i always feel like im doing something wrong lol. able to emulate glxgears. now trying to run the steam flatpak
<HdkR>
Container software is likely to have issues
<clover[m]>
got a segfault
<Jasper[m]>
<konradybcio> ""or at least put to sleep mode"" <- Oh yeah, I'm mostly describing it like that because I still have to wake it using the keyboard
<Jasper[m]>
But the led is on
<Jasper[m]>
Normally it flashes if it's in one of the sleep kodes
<Jasper[m]>
s/kodes/modes/
<konradybcio>
It = the soc
<konradybcio>
The led will only go off when we get soc power collapse
<clover[m]>
i wonder if i can add a user to this x86 chroot
<clover[m]>
makepkg doesn't really like to be run as root
<exeat>
BTW, is the x13s power key missing some kind of debouncing setting? It seems to emit multiple press/release events for each actual press.
<HdkR>
clover[m]: You can once it is unpacked yes
<bluerise>
exeat: I don't see them on OpenBSD
<bluerise>
the power key is hooked up through 2 layers, and those are built in a way that it should trigger twice
<bluerise>
it's edge-triggered
<exeat>
Interesting... on Linux, with systemd's handling for that key disabled, I get this with a single press and release:
<exeat>
2.453892 KeyPress event, serial 25, synthetic NO, window 0x3400001,