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
ellyq has joined #aarch64-laptops
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
Mathew has joined #aarch64-laptops
mcbridematt has quit [Ping timeout: 480 seconds]
jglathe_volterra has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
iivanov has quit [Quit: Leaving...]
iivanov has joined #aarch64-laptops
svarbanov_ has quit [Ping timeout: 480 seconds]
jglathe_volterra has quit [Remote host closed the connection]
svarbanov has joined #aarch64-laptops
hightower3 has quit [Ping timeout: 480 seconds]
hightower2 has joined #aarch64-laptops
jglathe_volterra has joined #aarch64-laptops
<vadikas[m]> Every time I move from one room to another, wifi breaks as described by @jhovold
<vadikas[m]> Only reboot helps
jglathe_volterra has quit [Remote host closed the connection]
jglathe_volterra has joined #aarch64-laptops
<jglathe_volterra> vadikas[m] tried ```sudo rmmod ath11k_pci && sudo modprobe ath11k_pci``` ?
jglathe_volterra has quit [Remote host closed the connection]
jglathe_x13s has joined #aarch64-laptops
hightower2 has quit []
jglathe_volterra has joined #aarch64-laptops
echanude has quit [Ping timeout: 480 seconds]
ungeskriptet is now known as Guest4578
ungeskriptet has joined #aarch64-laptops
Guest4578 has quit [Ping timeout: 480 seconds]
echanude has joined #aarch64-laptops
<vadikas[m]> <jglathe_volterra> "vadikas tried ```sudo rmmod ath1..." <- tried -- system dies in kernel deadloop
<jglathe_volterra> oof sorry. That's my go-to rescue if ath11k acts up and I don't want to reboot. Might take a few seconds, but works here reliably on X13s and Volterra.
iivanov__ has joined #aarch64-laptops
iivanov___ has joined #aarch64-laptops
<vadikas[m]> I even tried to echo 1 > /sys/bus/pci/devices/0006\:01\:00.0/reset , but resetting device doesnt work also
<jglathe_volterra> do you have some dmesg fragment? What are you running on? Mine is Ubuntu 23.10, kernels from 6.6..6.8.1
iivanov___ has quit [Quit: Leaving]
iivanov___ has joined #aarch64-laptops
iivanov___ has quit []
iivanov___ has joined #aarch64-laptops
flokli has quit [Quit: WeeChat 4.2.1]
flokli has joined #aarch64-laptops
iivanov___ has quit [Quit: Leaving]
iivanov___ has joined #aarch64-laptops
iivanov___ has quit []
iivanov___ has joined #aarch64-laptops
iivanov___ has quit []
iivanov__ has quit [Remote host closed the connection]
iivanov__ has joined #aarch64-laptops
<vadikas[m]> looks like now they gone in reboot, I'll save it next time. But its the same 'wrong buffer size'
iivanov__ has quit []
iivanov__ has joined #aarch64-laptops
iivanov__ has quit [Quit: Leaving]
<jglathe_x13s> hmm you could try journalctl -b -1 -g ath11k
<jglathe_x13s> and see where it died (or stopped writing to the journal), too
<vadikas[m]> no entries
todi1 has joined #aarch64-laptops
todi has quit [Ping timeout: 480 seconds]
Caterpillar has joined #aarch64-laptops
<steev> which firmware version are you running?
<vadikas[m]> x13s-firmware 20240312-0
iivanov has quit [Quit: Leaving...]
<steev> the actual firmware version that reports when it's loaded, i don't know what that version number means
<vadikas[m]> [ 6.350301] ath11k_pci 0006:01:00.0: fw_version 0x1106196e fw_build_timestamp 2024-01-12 11:30 fw_build_id WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.37
ema has quit [Quit: .]
<steev> .37 is the newest firmware though
ema has joined #aarch64-laptops
<clover[m]> i think i can stop carrying mutter now that v46 is released. seems to have the fixes that address usbc display out
<jglathe_volterra> yaaay
<steev> nice!
<agl> Have you heard about the xz-backdoor debacle?
<steev> kali was affected by it, so yes :)
<steev> to be clear, we had the packages, not that it was exploited
jglathe_volterra has quit [Remote host closed the connection]
Caterpillar has quit [Quit: Konversation terminated!]
<clover[m]> if you are on arch,
<clover[m]> sudo downgrade xz and choose 5.4.6
<abby> arch probably doesn't even have the malicious code compiled in
Mathew has quit [Quit: Leaving]
mcbridematt has joined #aarch64-laptops
<clover[m]> i just learned it only affected x64 packages too. aarch64 ftw!
<abby> the malicious code was included precompiled, so it would only be injected on x86_64 && glibc && gcc && gnu ld
<abby> with additional checks for if you're in a debian or rpm build environment (checks existence of debian/rules or RPM_ARCH=x86_64)
<clover[m]> does that mean debian-based distros like ubuntu were also affected?
<abby> yes
<abby> well, i think ubuntu didn't pull in xz 5.6.*, but they would have been affected