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
<bamse>
steev: yeah, i'll check with "we" next week
<steev>
enjoy the 3 day weekend :D
<steev>
offsec is doing a mental health day on monday, so we're getting a 4 day weekend, which is nice
<bamse>
steev: wife decided that 5 was a better number...
<steev>
oh nice
<bumble[m]>
I'm a fan/user of x13s and am curious to know: will recently-merged venus firmware will lead to any user-visible improvements? or is it maybe mostly something that will simplify some maintenance details?
<bamse>
bumble[m]: "no", because the driver isn't enabled in the kernel...but that answer depends on which kernel you're running
<bamse>
bumble[m]: once you have the kernel pieces in place the answer is a different variation of "no"...because few applications will actually use the video accelerator without further tinkering
<bumble[m]>
thank you for answering, good to know
<bamse>
bumble[m]: there's some activity in the area of improving that though...so at some point you hopefully would get lower cpu load and better battery life in some use cases
<steev>
tobhe[m]: do i need to do anything specific for the 64G with oled? i've tried adding mem=32G but it's just doing nothing, and if i try to pass devicetree but apparently y'all don't install them to linux-image-X.X...
<steev>
this is with 25.04
<tobhe[m]>
25.04 concept image?
<steev>
yeah, i installed it
<steev>
booting it from usb works
<tobhe[m]>
ah and that is trying to boot the installation?
<steev>
no, it doesn't boot at all :)
<steev>
screen goes black and then it reboots
<tobhe[m]>
so this is booting from live media and you see grub and then it fails?
<tobhe[m]>
that shouldn't happen
<steev>
no, the live media works fine
<steev>
once installed, and the live media is removed, grub comes up, but it doesn't boot, the screen just goes black after choosing ubuntu
<steev>
i tried adding mem=32G to the kernel command line, still just a black screen, when i tried to pass the dtb manually, it said the file doesn't exist, which, seems correct there is no /usr/lib/linux-image... like on debian or kali
<tobhe[m]>
sounds like a bug that i hadn't heard about yet
<tobhe[m]>
oh
<tobhe[m]>
you need to tick the additional drivers flag in the installer
<steev>
oh
<tobhe[m]>
but you can still save it. let me think
<steev>
do you not apply the separate one for oled yet?
<steev>
separate dts*
<tobhe[m]>
no, because I need to find a proper upgrade path
<steev>
there we go, so by default it doesn't seem to be passing the t14s dtb apparently
<steev>
unless i skipped a step somewhere and was supposed to copy it to efi
<tobhe[m]>
try installing hwe-qcom-x1e-meta and flash-kernel by hand
<tobhe[m]>
that should fix it
<steev>
rebooting to test
<tobhe[m]>
flash-kernel is what copies the dtb to /boot, hwe-qcom-x1e-meta includes a few extra hacks like clk_ignore_unused and pd_ignore_unused
<steev>
i still seem to have to pass the dtb manually, but at least its faster to type now :D
<steev>
gonna head over to my sister's place, will play with it more (and maybe even do a reinstall and see if choosing the proprietary stuff fixes it)
<steev>
its not like i've installed anything on it :D
<tobhe[m]>
let me know if it doesn't, not sure why flash kernel doesn't automatically install it
<tobhe[m]>
but time for bed for me. Will have a look tomorrow
<tobhe[m]>
you probably just need to run flash-kernel manually to fix it because it is normally triggered by a kernel hook
tobhe_ has joined #aarch64-laptops
hexdump01 has joined #aarch64-laptops
tobhe has quit [Ping timeout: 480 seconds]
hexdump0815 has quit [Ping timeout: 480 seconds]
todi has quit [Ping timeout: 480 seconds]
todi has joined #aarch64-laptops
tobhe has joined #aarch64-laptops
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
tobhe_ has quit [Ping timeout: 480 seconds]
hexdump01 has joined #aarch64-laptops
hexdump02 has quit [Ping timeout: 480 seconds]
eluks has quit [Remote host closed the connection]
eluks has joined #aarch64-laptops
SpieringsAE has joined #aarch64-laptops
<steev>
tobhe[m]: so, i closed it (assuming suspend? idk), and later when i opened it, it was off, and after powering it back on, i'm getting a... i'm not sure if its a crash, but i get this from grub (sorry for the crappy cell phone pic)
<steev>
then it goes back to the grub menu but seems locked up
alpernebbi has quit []
<steev>
i ended up re-installing, and got a frozen screen after pushing it, setting mem=32G on the kernel, and that seemed better, but i went to power it off, and it froze when i clicked power off, and now i'm back to getting the above; one thing i noticed when doing the re-install was that the system complained that the efi partition needed to be fscked
<steev>
and after booting to the live image again, sure enough the efi partition needed to be fscked
todi1 has joined #aarch64-laptops
todi has quit [Ping timeout: 480 seconds]
<albsen[m]>
steev: this is normal on the t14s version you and I have. it's everytime the system crashes the reboot will crash initramfs or something in the critical boot path. I've been replicating that consistently for months. if you simply ctrl-alt-del reboot right before it locks you should be fine.
<albsen[m]>
also, the blank screen something I get every boot as well, it's due to the something is being initalized late and hence the screen only shows when the kernel starts booting. in my case I have to type the disk encryption password blind with the screen off once i hit enter (with the correct password) it continues to boot
<\[m]>
yeah that seems very proper for the pricepoint !
<\[m]>
if anyone wants to buy a macbook air m1 🙂 though I still love the form factor, I don't think a laptop case has had such epic design - to bad they make them square for m2+
<\[m]>
oh my so glossy it hurts 😲
<JensGlathe[m]>
there are non-oled options (~850) that are non-glossy
<\[m]>
(on the ideapad)
<\[m]>
how do you like the oled? it's some sort of cheaper variant or what I read here - I don't care for oled really myself, I like my screen matte but 400 nits minimum
<JensGlathe[m]>
Lenovo has a sale currently, its same with IPS
<JensGlathe[m]>
I don't have an OLED device here yet
<JensGlathe[m]>
Others that have the ideapads test my tree
<\[m]>
"sale"
<JensGlathe[m]>
Yeah
<JensGlathe[m]>
Whatevs
<JensGlathe[m]>
I guess they still earn something on them
<\[m]>
oh my it's true it's so weird, 800 euro 512gb 32gb ram 😲
<\[m]>
lol but you can't get a qwerty for that
<\[m]>
maybe I'll get that oled for this money, and come rant about it here afterwards 🙂
<JensGlathe[m]>
That’s a plan
<\[m]>
does someone live in the netherlands? it's 50 euro cheaper and qwerty
<Jasper[m]>
Yes
<Jasper[m]>
Wait what are we talking about?
<SpieringsAE>
\: ✋
_whitelogger has joined #aarch64-laptops
<albsen[m]>
tobhe: thats great news, I'll upgrade and let you know how it goes.
<\[m]>
it's to deliver the laptop from lenovo NL webshop and I'd come to pick it up after - can't select BE
<SpieringsAE>
rip, you can have it delivered to my work, its kinda far from belgium though, its in Ulft
<Hugo[m]1>
I'm now trying to add SPI for "hid-over-spi" support to the device tree, but I'm not sure where to find the GPIO pins from the dumped and decompiled DSDT.
<Hugo[m]1>
I've identified a QSPI device (the only one) in the DSDT with the name 'SP11', '_HID = QCOM0C0E', '_SUB = MSHW0489
<Hugo[m]1>
Digitizer and Pen Input is SPI over HID
<JensGlathe[m]>
There should be AeoB files with some additional (and maybe deviating) description in the windows driver repository, *.bin, I vaguely remember qspi named .bin files
<Hugo[m]1>
I
<Hugo[m]1>
I'll check. Still need to find the pinctrl gpios for hid
<JensGlathe[m]>
Look for SP11 packages in the DSDT if there is TLMMGPIO in there
<Hugo[m]1>
Cannot find a TLMMGPIO entry in SP11 packages.
<jdb[m]>
Hugo: everything working otherwise on your SP11? Suspend? Random freezes?
<Hugo[m]1>
Lid sensor not working, and sometimes unresponsive USB after wake up (but that happened rarely so I need to investigate that further). But it is stable, I've not experienced any kernel panics or freezes
<jdb[m]>
Ok, I need to understand why I get freezes after a long suspend period then
<jdb[m]>
And in the issue tracker, you mentioned : "fixing the suspend button."
<jdb[m]>
It doesn't work for you?
<Hugo[m]1>
jdb[m]: yea surface just freezes, sorry forgot to mention that
<Hugo[m]1>
But I remapped that key for now
<Hugo[m]1>
Putting it into suspend via software works
<jdb[m]>
In my case, sometimes the suspend button does work, but it's not deterministic
<jdb[m]>
But I've had issues as well with the power button too, it's weird
<Hugo[m]1>
<JensGlathe[m]> "There should be AeoB files..." <- Found `BSRC_QSPI.bin` and `BSRC_QSPI_DEN.bin` in the store
<\[m]>
ordered - 800 euro 😲 I think it's rather cheap for what you get but maybe I'm just very done with mac os
<Hugo[m]1>
40, 41, 42 are used in `qup_spi10_data_clk`, and 43 is `qup_spi10_cs`.
<Hugo[m]1>
So should I just gamble with 49, and 50?
<JensGlathe[m]>
those are yours as it seems
<Hugo[m]1>
fun
<JensGlathe[m]>
It was in the AeoB files, right
<Hugo[m]1>
yes
<Hugo[m]1>
had a fight with .NET building the AeoBUtil so that's why it took me so long
<alexVinarskis[m]>
there is prebuilt for amr64 Windows attached in 'Github Releases'
<alexVinarskis[m]>
*arm64
<Hugo[m]1>
too late, built it on macOS
<Hugo[m]1>
The `surface-pro-x.dts` has `vdd-supply = <&vreg_ts_5p0>;` defined in `hid@0`, do you have an idea on where to find the vreg responsible for powering the spi hid peripherals?
<JensGlathe[m]>
Also in the AeoB file. At least a name hint
<Hugo[m]1>
Lots of BUSARB with clock references , the TLMMGPIO, but don't see any ref to vregs
<tobhe[m]>
i also have them in my dmesg on a working t14s
<anonymix007[m]>
pdmapper seems to be up and running
<tobhe[m]>
then my last guess would be firmware vs modules in the initrd
<tobhe[m]>
i think the firmware might have to be there when the modules are first loaded
<anonymix007[m]>
I don't have neither adsp firmware nor pas module in the initrd. It worked previously (and still works in Windows) though and just suddenly broke this time
<steev>
dang, i was hoping memmap would help with systemd-boot since it doens't have an equivalent of badram or cutmem, but no luck
<tobhe[m]>
anonymix007: how do you generate your initrd? maybe some package update changed the included modules
<anonymix007[m]>
Well, it also needs /phy_qcom_snps_eusb2/phy_snps_eusb2/ since 6.16(?)
<steev>
yes, they renamed a config option in 6.16
mani_s has quit [Quit: Connection closed for inactivity]
<tobhe[m]>
if it isn't the kernel it could also be a change in dracut itself
<anonymix007[m]>
I'm using mkinitcpio though... It looks like a hardware issue. The laptop doesn't work without a charger even in Windows (despite 100% being reported) and unplugging the charger immediately shuts it off as well. Nice, it isn't even a year old
<JensGlathe[m]>
ouch
<steev>
oh hell yeah, they did fix monitor mode for ath12k... now if only they'd backport the work to ath11k
<steev>
oh hell yeah, they did fix monitor mode for ath12k... now if only they'd backport the work to ath11k
<valpackett>
wow so it's possible to have even worse luck with lenovo than i do, oof (my L14gen2 AMD at one point got "insomnia" (random wakeups in both s3 and s0ix) and also sometimes keyboard keys get logically stuck)
<tobhe>
anonymix007[m]: oh no :(
<tobhe>
I hope it is one of those things that just go away after waiting or discharging the battery