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
nashpa has joined #aarch64-laptops
dliviu has quit [Ping timeout: 480 seconds]
pabs has quit [Ping timeout: 480 seconds]
pabs has joined #aarch64-laptops
ezbin has joined #aarch64-laptops
ezbin has quit [Quit: WeeChat 4.1.1]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
tobhe_ has joined #aarch64-laptops
hexdump02 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
tobhe has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
hexdump01 has joined #aarch64-laptops
<freekurt[m]>
I have 100% load on some CPU cores too on my x13s.
hexdump0815 has quit [Ping timeout: 480 seconds]
<bamse>
freekurt[m]: which kernel version?
<freekurt[m]>
One of the latest kernels that has come out. I use [@jglathe:matrix.org](https://matrix.to/#/@jglathe:matrix.org)'s and update regularly. The issue has been happening for a while though.
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<valpackett>
bamse: steev: freekurt[m]: yes finally i'm not alone with that ath12k 100%cpu issue!
<valpackett>
it's bouncing because every 6 seconds networkmanager tries to read wifi status
<valpackett>
and ath12k somehow manages to spin on a spinlock for like a whole second
<steev>
i use my kernel, as well as the debian kernel on the x13s and have not seen it, but i did not really test 6.15 yet, i saw some stuck clocks and haven't gone back just yet to figure out where the issue is
<alexVinarskis[m]>
Glad someone else got the zenbook. Have you tried booting Ubuntu Concept as live USB stick? Latest ISO should support both x1p/x1e, that would be the simplest way to get started.
<alexVinarskis[m]>
Aah okay. So its not the dtb/patches issue.
<krzk>
Can you stop using matrix chat on IRC? Half of these messages are totally unreadable.
<krzk>
Basically there is just "Hey" and some weird link
<krzk>
s/matrix chat/matrix style/
pbrobinson has joined #aarch64-laptops
<osmoz[m]>
I will install a client later, I think it’s because I replied to the message
<krzk>
I know. You can use Matrix, just without Matrix features.
<osmoz[m]>
But my first message does include matrix features, maybe it’s the size or the newline with my client
chrisl has joined #aarch64-laptops
<osmoz[m]>
I don’t think it’s the dtb, but I only used the first one (0012) because there were compile errors when all of them were included and I don’t need sound and media right now
<osmoz[m]>
The kernel seems to start but my issue is when mounting the root partition I will have to research how does the initramfs work and what does it needs
<jhovold>
alexVinarskis[m]: I can confirm that reverting the genirq cpu hotplug commit fixes the hosed nvme after suspend here too
chrisl has quit [Ping timeout: 480 seconds]
<jhovold>
can you please report this today (to avoid waiting until rc1 is released with this regression on sunday)?
pbrobinson has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
<alexVinarskis[m]>
Thanks for testing! Absolutely, will be on it in maybe an hour.
<deathmist>
I'd submit my stuff to chimera officially but imo kernel side stuff is still way too much in flux for me to bother while limine (which the aarch64 and most other isos uses as bootloader) is missing stuff to make the live boot experience proper, for some reason it also takes forever to show the menu which I'd have to debug somehow too
<deathmist>
maybe the solution for the iso problem would be to make a separate x1e ones integrating sysd-boot + dtbloader or even just swap the main aarch64 ones to use those instead, will see ig once most stuff on kernel side starts to settle down a bit and the various patches wouldn't need to be dealt with as much on each pkgver bump
chrisl has joined #aarch64-laptops
pbrobinson has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
tudorl has joined #aarch64-laptops
pbrobinson has joined #aarch64-laptops
pbrobinson has quit [Ping timeout: 480 seconds]
<jhovold>
alexVinarskis[m]: thanks for reporting and spotting the autosel selection, just asked stable to drop it for now
<alexVinarskis[m]>
Great, thanks for the followup. Hope they can have it resolved on such short notice...
whiskey9 has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<osmoz[m]>
deathmist: thanks I will look into it weekend. I will also try to send upstream my changes to void if I can make something clean
chrisl has joined #aarch64-laptops
<abby>
yeah it'd be cool to support x1e, but i don't have any of the devices
chrisl has quit [Ping timeout: 480 seconds]
hexdump01 has quit [Read error: Connection reset by peer]
chrisl has joined #aarch64-laptops
<freekurt[m]>
valpackett: is there a way to fix the ath12k 100% cpu issue? revert firmware version maybe?
chrisl has quit [Ping timeout: 480 seconds]
tudorl has quit [Remote host closed the connection]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<JosDehaes[m]>
Jens Glathe: again same USB issue with yoga 7x with your kernel `jg/ubuntu-qcom-x1e-6.15.0`. No USB works (but DP alt does), lsusb gives an error
<JensGlathe[m]>
Can you check in the dtb if the smb2360 repeaters are explicitly enabled? On the phone, can’t look
<JosDehaes[m]>
it says status=okay
<JensGlathe[m]>
In smb2360_0 , _1, _2 ? Not in the phy node?
<JensGlathe[m]>
no they look okay
<JensGlathe[m]>
lsusb gives permission errors? That's broken since somewhere in 25.04
<JosDehaes[m]>
no it returns 1
<JosDehaes[m]>
this was the same the last time
<JosDehaes[m]>
also, this is arch not ubuntu
<JosDehaes[m]>
hmm, same issue with jhovold's tree
chrisl has joined #aarch64-laptops
<JosDehaes[m]>
got to go now, will check later
<alexVinarskis[m]>
there was a change of eusb driver ~2 weeks ago, from iirc next-20250515 or next-20250514 CONFIG_PHY_QCOM_SNPS_EUSB2 would become CONFIG_PHY_SNPS_EUSB2, do you have the correct one enabled?
<JensGlathe[m]>
I backed the new synopsys driver out bc of issues, not in my tree/config
<JosDehaes[m]>
no I did not have that one, rebuilding
<alexVinarskis[m]>
since Jens reverted the change, you need the old/CONFIG_PHY_QCOM_SNPS_EUSB2 one
chrisl has quit [Ping timeout: 480 seconds]
<JosDehaes[m]>
Works, thx 🙏
jhovold has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
tudorl has joined #aarch64-laptops
jglathe_volterra has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
<valpackett>
freekurt[m]: no, it's not a firmware issue. evidently it's a regression so we need to bisect the kernel to find out when it started happening
<freekurt[m]>
Oh dang. Ok!
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
tudorl has quit [Remote host closed the connection]
todi1 has quit [Read error: Connection reset by peer]