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?
<_[m]1> make journalctl persistent over boot?
agl7 has quit [Remote host closed the connection]
agl7 has joined #aarch64-laptops
pbsds has quit [Quit: The Lounge - https://thelounge.chat]
pbsds has joined #aarch64-laptops
matalama has quit [Quit: Connection closed for inactivity]
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
<HdkR> https://www.youtube.com/watch?v=gx-AwMVSrHc People love to play meme games on X13s right? :)
<Jasper[m]> <_[m]1> "make journalctl persistent..." <- Could do that, do you have a link, for archwiki for example, by any chance?
indy_ has quit [Ping timeout: 480 seconds]
indy has joined #aarch64-laptops
<konradybcio> HdkR: has anyone tried like csgo
<HdkR> konradybcio: Yes, hits some pedantic case in the menus because of CEF, but I think once in-game it's okay
exeat has joined #aarch64-laptops
<_[m]1> <Jasper[m]> "Could do that, do you have a..." <- I thought that it s just creating the folder`/var/log/journal/`
<robclark> HdkR: s/okay/better/ .. although maybe having gl thunks would improve it.. I hadn't been able to get thunking working
<HdkR> ah
<HdkR> robclark: konradybcio: Took a bit of time to get through the menus, but once in the training mode it's okay-ish perf
<HdkR> Oh, I had laptop mode on
<robclark> I guess that is with thunking
<robclark> without, IIRC, it was more like 20ish fps
<HdkR> Yea, with thunking. so about 100fps
<robclark> that is a substantial improvement
<robclark> I guess I should figure out how to get thunking working on non-multiarch distro
<HdkR> We're definitely working on it, but it is slow since I don't use Fedora/Arch
<Jasper[m]> HdkR: there's a workshop map that often gets used for benchmarking, check that out
<Jasper[m]> I think it's by crashz
<HdkR> eeeeh, that's effort
<Jasper[m]> HdkR: A search query, a click on a button and loading a map from the regular menu hahaha
<Jasper[m]> Installing mods basically means clicking a button and it gets downloaded automagically
<konradybcio> HdkR: oh very nice!
<konradybcio> hopefully that perf can be made better
<HdkR> It's a combination of CPU and GPU limited in-game
<HdkR> Which that's 1200p on lowest graphics settings
<konradybcio> if you go into the settings and enable developer console, you can then press the ~ key and type in map de_mirage for a "real" map
<HdkR> Once a light in the scene turns on, it immediately becomes GPU limited at dropped to like 50
<konradybcio> this looks like some sort of a tutorial
<HdkR> Indeed it is, some sort of training map
<HdkR> I don't play CSGO so it's hard for me to poke around much in a shooty game
<konradybcio> just run around with a knife (it's faster)
<konradybcio> press 3 to hold it
<konradybcio> also that message taken out of context would be weird lol
<HdkR> Ah yes, just play knife game instead of shooty game. I get it :P
<Jasper[m]> <HdkR> "I don't play CSGO so it's hard..." <- https://steamcommunity.com/sharedfiles/filedetails/?id=500334237 found it, it's by a different mapper than crashz
<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,
<exeat> % xev -event keyboard | grep -E --line-buffered '^Key(Press|Release)' | ts -i "%.s"
<exeat> 0.171688 KeyRelease event, serial 28, synthetic NO, window 0x3400001,
<exeat> 0.000133 KeyPress event, serial 28, synthetic NO, window 0x3400001,
<exeat> 0.014120 KeyRelease event, serial 28, synthetic NO, window 0x3400001,
<exeat> 0.000091 KeyPress event, serial 28, synthetic NO, window 0x3400001,
<exeat> 0.016354 KeyRelease event, serial 28, synthetic NO, window 0x3400001,
<exeat> 0.000021 KeyPress event, serial 28, synthetic NO, window 0x3400001,
<exeat> 0.016500 KeyRelease event, serial 28, synthetic NO, window 0x3400001,
<exeat> 0.000020 KeyPress event, serial 28, synthetic NO, window 0x3400001,
<exeat> 0.016549 KeyRelease event, serial 28, synthetic NO, window 0x3400001,
<exeat> 0.000119 KeyPress event, serial 28, synthetic NO, window 0x3400001,
<exeat> 0.016300 KeyRelease event, serial 28, synthetic NO, window 0x3400001,
<exeat> 0.000097 KeyPress event, serial 28, synthetic NO, window 0x3400001,
<exeat> 0.015944 KeyRelease event, serial 28, synthetic NO, window 0x3400001,
<exeat> 0.000117 KeyPress event, serial 28, synthetic NO, window 0x3400001,
<exeat> 0.001061 KeyRelease event, serial 28, synthetic NO, window 0x3400001,
<exeat> (first timestamp relative to the start of the command, the rest to the previous line)
<bluerise> Can't tell you about those event internals in Linux, but at least from a hardware/driver side it shouldn't be an issue
<bluerise> you can probably add prints in the pwrkey driver to find out if it's the drivers fault or some upper layers
<exeat> Yes, it seems that the problem is absent in the lower layers (I tried showkey(1))
<exeat> D'oh, it's my vicious key repeat rate setting (though the other keys aren't affected)
<clover[m]> HdkR: i know you don't get a lot of arch users, but here is the log for my steam launch: https://pastebin.com/FYQqiRiD
<HdkR> clover[m]: `MESA-LOADER: failed to retrieve device information` I have never seen that before
<HdkR> Also weird zenity crash
<clover[m]> i also get [GFX1-]: No GPUs detected via PCI when i start firefox. it comes up though, just quite slow
<HdkR> That one at least makes sense, there's no GPUs on a PCI bus
<HdkR> Steam is likely just crashing since mesa loader is freaking out
erebion[m] is now known as erebionCCCamp232142[m]
<Jasper[m]> [ 0.965865] cros-ec-i2c 1-001e: Chrome EC device registered
<Jasper[m]> [ 1.682278] cros_secure
<Jasper[m]> [ 5.464672] cros-ec-sensorhub: probe of cros-ec-sensorhub.2.auto failed with error -22
<Jasper[m]> Hmmmm
<Jasper[m]> Another mainline port for the pixel c just changed the message length to 120 as a HACK, that seemed to work for them