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
hwpplayer1 has quit [Remote host closed the connection]
Kelsar has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
<valpackett>
caught the "random early after boot" panic on console, turns out it's ath12k "Unable to handle kernel paging request at virtual address .." ath12k_pci_ext_grp_napi_poll -> ath12k_dp_service_srng -> ath12k_dp_tx_completion_handler → ieee80211.. -> skb_complete_wifi_ack -> queued_spin_lock_slowpath
chrisl has quit [Ping timeout: 480 seconds]
<janrinze>
fwiw; I did do a firmware upgrade before I started tinkering with Linux. And I kept Win11 on a partition just to be able to do future firmware upates.
<janrinze>
On the side of Xorg vs Wayland, I like to use x2x a lot (part of my workflow) and Wayland does not have an alternative for that.
<valpackett>
i wonder if some "panic after resume" issues were also ath12k..
<valpackett>
funnily enough searching the web for '"Unable to handle kernel paging request at virtual address" ath12k' returns a lot of cve.mitre.org
<Treibholz[m]>
janrinze: I wanted to try deskflow (synergy/barrier-fork), but didn't have the time yet, to fiddle around with the permission-stuff under sway.
pabs has quit [Read error: No route to host]
pabs has joined #aarch64-laptops
GAODA has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
GAODA has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
pbrobinson has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
<janrinze>
Treibholz[m]: deskflow looks promising however I don't know what its requirements are nor if it is secure over network. With x2x we use a secure ssh tunnel with X protocol enabled.
pbrobinson has joined #aarch64-laptops
<Treibholz[m]>
janrinze: by default, every host (client and server) has a self-signed ssl-certificate, what you need do accept. (similiar to SSH...), and it also works with windows and macos.
chrisl has joined #aarch64-laptops
<Treibholz[m]>
I don't know how much development was done in x2x since I last used it (~10years ago?) - but synergy/barrier and thus deskflow nave much fewer issues with different screen resolutions.
<Treibholz[m]>
s/nave/have/
<Treibholz[m]>
in the meantime I tested deskflow with gnome: works. With sway I can't give it the permissions to my local screen/keyboard/mouse... Problems you never have with X, because X has no modern permission system (just yes/no) - wayland is more sophisticated (and complicated...)
chrisl has quit [Ping timeout: 480 seconds]
<jhovold>
valpackett: can you post a complete oops somewhere for the ath12k issue you hit somewhere?
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
SpieringsAE has quit [Quit: SpieringsAE]
hwpplayer1 has joined #aarch64-laptops
vfdkjted2 has joined #aarch64-laptops
vfdkjted has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
ungeskriptet_ has joined #aarch64-laptops
ungeskriptet has quit [Ping timeout: 480 seconds]
<nirik>
so whats the current status of sound and webcam on the 7x? I know I saw patches floating around, but I guess still rough? also oddly I note now that plugging/unplugging power doesn't seem to register, it always seems to think it's plugged in. ;( Otherwise looking pretty good for daily driving tho. ;)
<robclark>
sound works, but no speaker protection so distros are perhaps not enabling it
<robclark>
AFAIU there are patches for camera but I haven't tried that yet on my 7x
<anthony25>
the plugging/unplugging power is strange, do you have the firmwares for the slim7x?
<anthony25>
like, are you able to see the battery %?
ungeskriptet_ has quit [Remote host closed the connection]
ungeskriptet has joined #aarch64-laptops
<nirik>
yep. it just says that it's plugged in, but discharging.
<nirik>
oof... and now I test again and it's working. bah
<nirik>
will dig more.
<anthony25>
I never saw that bug
<anthony25>
what does say it's always plugged in? gnome, upower or in sysfs?
<nirik>
all of the above, but now I can't get it to happen.
* nirik
tries a reboot
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<Treibholz[m]>
uhh, two external 4k monitors are (kind of) working (just 30hz) with the X13s...
<Treibholz[m]>
one via my Lenovo ThinkPad Thunderbolt 4 Dock, and the other via USB-C
<Treibholz[m]>
ahh, the dock is also just in USB-mode...
<nirik>
ok, still working, no idea. ;( sorry for the noise there... I now see bluetooth isn't working. I know it was before my last re-install here... must be missing some firmware or something...
<JosDehaes[m]>
nirik: sound works (speakers + mic), but output is distorted. It's passable if I turn the volume in sound playing app very low (like 25%). There seems to be too much gain somewhere, even if I put the digital volume to only 5). Camera and video accel are working with some patches
<nirik>
cool. thanks.
<nirik>
this bluetooth thing is much more dealbreaking. I'll dig around to see what I missed on it...
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #aarch64-laptops
<JosDehaes[m]>
bluetooth has been working for a long time?
<nirik>
yeah, thats what I thought too... but I just did a wipe/reinstall and it's not working for me now. ;(
<JosDehaes[m]>
what kernel are you using?
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<bumble[m]>
craftyguy: want to share my experience that, for the past two or three weeks, firefox and qutebrowser are prone to crash easily on postmarketos-edge-x13s. firefox has been so crashy as to be almost unusable
<bumble[m]>
no expectations from me and only appreciation; just wanting to let you know as a sort of data point
<bumble[m]>
$ firefox-esr --version
<bumble[m]>
Mozilla Firefox 128.10.1esr
<nirik>
Jos Dehaes: It's fedora rawhide ( 6.15.0-0.rc7.57 ) + jhovold's rc7 patch on top.
<JensGlathe[m]>
is bluetooth defined in yout dtb? How did you reinstall
<nirik>
can check the dtb... but upstream + jhovold's tree used to define it I thought?
<nirik>
I bodged up a fedora rawhide live media with this kernel and installed via usb. I reinstalled to get a encrypted install (my old one wasn't)
<nirik>
yeah, no bluetooth in the dtb. hum
<nirik>
I see you have a patch in your tree adding it. I can add that, just don't get why it used to work? I guess I could have had a hacked up dtb or something (that was another reason to re-install... too many months of manually poking things)
<JensGlathe[m]>
I have a patch open for it on the list, since this little part is not upstream.
<hogliux>
nirik: On the slim 7x I have the following working: GPU acceleration, suspend (albeit only s2idle), Bluetooth, wifi, USB, DP Alt mode, hw assisted video deciding (h264 only),
<nirik>
cool. I have not tried dp alt mode or video decode, but I think the rest barring bluetooth is working.
<hogliux>
Webcam (with pronounced green tint), battery monitoring and kvm virtualization
<hogliux>
When kvm virtualization is enabled then hw assisted video deciding and some USB features stop working as you are forced to use the same adsp firmware that bios is using during boot
<hogliux>
Not working for me is speaker protection and USB4 PCIe tunneling
hogliux has quit [Remote host closed the connection]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
macc24 has joined #aarch64-laptops
<macc24>
hogliux_: technically it wasn't bricked, it still booted fine, it just was draining battery 24/7
<kuruczgy[m]>
SpieringsAE: I just looked at it, IIUC this is only for sm8550, not x1e or sc8280xp :/
<jhovold>
valpackett: thanks, is that 6.15-rc7? how often do you hit it?
chrisl has joined #aarch64-laptops
<valpackett>
jhovold: that's next-20250516, i hit it very soon after booting very often, only sometimes it "gets off the right foot" and doesn't do this and remains stable
<valpackett>
let me also retest with new fw (i've been using older fw)
jhovold has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<valpackett>
nope, firmware 1.1 doesn't help, but i've noticed that on a "good" boot unbinding and rebinding ath12k multiple times is fine (well.. not that i let that much time pass after those attempts but)
hwpplayer1 has quit [Remote host closed the connection]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<valpackett>
hm is the "qmi dma allocation failed" in ath12k any important? (when it works but has these panics)
<valpackett>
well probably not
<valpackett>
it seems to be something early boot dependent like power or link training or whatever..? because on a "lucky" boot right now i can definitely rmmod && modprobe ath12k just fine and keep working, multiple times