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
<kuruczgy>
hogliux: nope, I have only tried a Linux guest so far. Nowdays games either run well enough under Proton or have some anti-cheat that makes VMs a non-starter anyway, so my interest in windows VMs has become quite low.
hightower2 has joined #aarch64-laptops
hightower4 has quit [Ping timeout: 480 seconds]
<kuruczgy>
Though one interesting thing would be running windows under a thin bare metal hypervisor (like what m1n1 can do with MacOS) for helping with reverse engineering drivers.
<icecream95>
In that case I could chvt to a VT from SSH and killed KDE, so the display driver managed to recover, but trying to start a compositor made the GPU hang again
<icecream95>
"arm-smmu 15000000.iommu: Unhandled context fault" seems bad
<icecream95>
Is there anything I can do to make the GPU reset properly rather than having to reboot?
hipboi has joined #aarch64-laptops
hightower4 has joined #aarch64-laptops
<dgilmore>
does anyone else have remoteproc crashing on the t14s?
<anthony25>
I'm trying to remove the IRQF_NO_SUSPEND flag for the moment
<anthony25>
(I can't sleep so that kept me busy :p)
hightower2 has quit [Ping timeout: 480 seconds]
tobhe_ has joined #aarch64-laptops
tobhe has quit [Ping timeout: 480 seconds]
<anthony25>
well… that didn't work as expected, but indeed the problem doesn't trigger if I remove all IRQ from there
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
hightower4 has quit [Remote host closed the connection]
hipboi has quit [Quit: hipboi]
hightower4 has joined #aarch64-laptops
hightower4 has quit [Remote host closed the connection]
hightower4 has joined #aarch64-laptops
hipboi has joined #aarch64-laptops
hipboi has quit []
<_mike>
macc24: hi are you around?
<_mike>
i updated to mainline kernel 6.13.0-rc6 with your scripts
<_mike>
but now i dont have bluetooth or gpu accel..?
<_mike>
i've tried your mainline, the jhorold or whatever it is and maud's and they are all giving me no love
<_mike>
i also tried to reinstall windows on it but it kept asking me to plug in the power lead even though it was already plugged in
hipboi has joined #aarch64-laptops
<_mike>
if i load the bluetooth module then start the bluetooth service it starts but has missing plugins
hipboi has quit [Quit: hipboi]
jhovold has joined #aarch64-laptops
hipboi has joined #aarch64-laptops
<macc24>
_mike: yes i am around, for x1e devices you need jhovold-x1e ktree set, and i don't include patches for non-slim7x laptops so you need to bring your own and set the file extension to patch_x1e for the build script to pick them u
<macc24>
up*
anthony25 has quit [Quit: Quit]
anthony25 has joined #aarch64-laptops
hogliux has joined #aarch64-laptops
<hogliux>
kuruczgy: I think gunyah may be better suited as a thin bare metal hypervisor than qemu for this sort of reverse engineering task
hogliux has quit [Quit: Page closed]
hipboi has quit [Quit: hipboi]
<macc24>
it would be so funny to make a hypervisor that would make macos run on x1e
<macc24>
with a gpu on usb4
sgerhold has joined #aarch64-laptops
icecream95 has quit [Ping timeout: 480 seconds]
hipboi has joined #aarch64-laptops
srinik has joined #aarch64-laptops
hogliux has joined #aarch64-laptops
xroumegue has quit [Ping timeout: 480 seconds]
<hogliux>
macc24: macOS requires TSO memory order mode for Rosetta. I don't think x1e supports this, right?
hogliux has quit []
<maz>
hogliux: whatever is the current linux top-of-tree.
<maz>
plus whatever is in my KVM queue, obviously.
xroumegue has joined #aarch64-laptops
svarbanov_ has quit [Quit: Leaving]
svarbanov_ has joined #aarch64-laptops
\\ has quit [Read error: Connection reset by peer]
abby has quit [Read error: Connection reset by peer]
hogliux has joined #aarch64-laptops
<hogliux>
maz: and I assume your kvm queue is not public?
<_mike>
macc24: hmm ok i'll give that a shot
hipboi has quit [Quit: hipboi]
hipboi has joined #aarch64-laptops
<maz>
hogliux: *everything* is public.
<maz>
how do you think things end up in -next?
<hogliux>
maz: makes sense. I just wasn't sure what you meant with "your kvm queue".
<_mike>
bah iono whats the deal
<_mike>
i'll wait for maud
matrix7125[m] has joined #aarch64-laptops
<_mike>
ahh i just compiled the kernel and modules without clang/llvm and used gcc instead now it's working okay
hogliux_ has joined #aarch64-laptops
hogliux_ has quit []
hogliux has quit [Quit: Page closed]
<macc24>
that's... odd
hipboi has quit [Quit: hipboi]
hogliux has joined #aarch64-laptops
hightower4 has quit [Remote host closed the connection]
<SpieringsAE>
that is indeed odd, have never noticed functional differences, only that gcc at least feels faster
<SpieringsAE>
_mike: from 6.14-rc1 I believe gpu should be in mainline linux
<SpieringsAE>
usb-a not yet though, this weekend I think I might make a new patchset with usb-a support and hopefully the sd-card reader if that works, I expect it will work though.
hogliux has quit [Quit: Leaving]
SpieringsAE has quit [Quit: Leaving]
alfredo has joined #aarch64-laptops
<jhovold>
Here's an updated wip branch for the X13s:
<JensGlathe[m]>
I tried the dev kit sd-card reader with the sdhc nodes from abelvesa , doesn’t really work yet. It gets recognized, but any i/o gives errors in dmesg.
pstef has quit [Ping timeout: 480 seconds]
pstef has joined #aarch64-laptops
pstef_ has joined #aarch64-laptops
pstef has quit [Ping timeout: 480 seconds]
pstef has joined #aarch64-laptops
pstef_ has quit [Ping timeout: 480 seconds]
pstef_ has joined #aarch64-laptops
pstef has quit [Ping timeout: 480 seconds]
<anthony25>
thanks jhovold!
<dgilmore>
jhovold: hope you had a good holiday period.
<dgilmore>
jhovold: curious if you have seen crashes in remoteproc related to qcom_q6v5_pas
<bamse>
dgilmore: do you have any more details about such crashes?
<dgilmore>
bamse: everytime I touch the keyboard or mouse on the t14s
<dgilmore>
the system gets a blue screen and resets
<bamse>
hmm, wonder if that's as a result of the remoteprocs restarting, or the issue causing [ac]dsp to crash
SpieringsAE has joined #aarch64-laptops
<SpieringsAE>
with regards to the usb_2 patches by abelvesa, it seems to work but I think I'm missing a modules or something https://pastebin.com/raw/1EvaXCrR
<SpieringsAE>
I do get a /dev/sda, but it doesn't actually get the partitions it seems
<bamse>
SpieringsAE: can you access sda? e.g. fdisk -l /dev/sda
<SpieringsAE>
nope
<SpieringsAE>
fdisk: cannot open /dev/sda: No medium found
<SpieringsAE>
looking around the scsi bits in menuconfig, I don't really see something that I feel is missing
alpernebbi has joined #aarch64-laptops
<dgilmore>
bamse: the same kernel works when I boot from USB, but to do that I have to blacklist qcom_q6v5_pas so its not loaded
<dgilmore>
I have hit this by booting from NVMe
SpieringsAE has quit [Remote host closed the connection]
<steev>
not sure how correct it is though; it shows 26c/23c when idle, but if playing audio it shows 1c for both
<steev>
guess i can reply on the list
srinik has quit [Ping timeout: 480 seconds]
<HdkR>
Every so often I've noticed the Yoga 7x's EC freaks out and stops charging. Not sure what's up with that, I only notice it a few days later when I can no longer SSH in to the thing.
<HdkR>
Then I get to do a little unplug, hold power button a couple times, plug in dance with the thing
<HdkR>
Today it was kind of funny since the backlight of the keyboard kept flashing and then it would die over and over
anthony25 has quit [Quit: Quit]
anthony25 has joined #aarch64-laptops
<macc24>
do you have the latest firmware update for ec?
<HdkR>
Probably not
<HdkR>
It's not like I have Windows on the thing to get it
jhovold has quit [Ping timeout: 480 seconds]
<anthony25>
macc24: I mean… battery life with video acceleration is pretty nice, and battery is kind of the all point of these laptops
<craftyguy>
are folks still successfully using s2idle on the x13s? I seem to always lose display when resuming from s2idle after some (tens?) of minutes, since many kernels ago