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
feespay[m] has quit [autokilled: Spambot. Mail support@oftc.net if you think this is in error. (2025-06-26 03:26:57)]
zetam has joined #aarch64-laptops
jglathe_ has quit [Remote host closed the connection]
kalebris has quit [Ping timeout: 480 seconds]
kalebris has joined #aarch64-laptops
jhovold has joined #aarch64-laptops
zetam has quit [Ping timeout: 480 seconds]
SpieringsAE has joined #aarch64-laptops
ravikant_ has joined #aarch64-laptops
ravikant_ has quit [Ping timeout: 480 seconds]
ravikant_ has joined #aarch64-laptops
enyalios_ has joined #aarch64-laptops
enyalios has quit [Ping timeout: 480 seconds]
<Jasper[m]>
Do you KNOW? How good the Qualcomm Snapdragon X Elite is????
icecream95 has joined #aarch64-laptops
icecream95 has quit [Ping timeout: 480 seconds]
<lynxy>
i gave up on trying to get booting off of usb-c working- just pulled the nvme out of the laptop and flashed that and it worked first time :pensive:
<JensGlathe[m]>
But it worked
<lynxy>
yup! :]
<JensGlathe[m]>
I added some mitigation code (like only having adsp.mbn in the initramfs), with these newer SoC's that's not always enough
ravikant_ has quit [Ping timeout: 480 seconds]
ravikant_ has joined #aarch64-laptops
mani_s has joined #aarch64-laptops
<GurneyBuchanan[m]>
Cross posting here from the Fedora-ARM channel (sorry for the dup to anyone in both places):
<GurneyBuchanan[m]>
Hitting issues running Steam under box64 (with 32 mode enabled) on SDXE1 on Fedora Rawhid - opened up https://github.com/ptitSeb/box64/issues/2776 for a missing symbol error!
<GurneyBuchanan[m]>
Does anyone have this currently working? Any experience in this group on FEX? Considering giving it a shot as well but the setup is more intensive!
<kuruczgy_>
GurneyBuchanan[m]: I use FEX for gaming on my slim7x, for me it works well. (I am on NixOS, but I think it should work well on any distro.)
<kuruczgy_>
I think box32 translates to arm32, so it's not supposed to work on X1E (which only has arm64)
<tobhe[m]>
kuruczgy_: which rootfs do you use on nix?
<GurneyBuchanan[m]>
kuruczgy_: great point - I'm using box64 with the 32 mode enabled (that they recently-ish added) that enables it do do both!
<robclark>
(I have had it working in the past w/ my own build.. but now that it is packaged in fedora along w/ fedora fex rootfs, I was hoping to use that instead)
<GurneyBuchanan[m]>
robclark: thanks - that's a GREAT data point - I'll hopefully hear back from the Fedora folks and can ask about that! I heard through the grape-vine that Valve may be interested in / investing in FEX so it seems worthwile to keep that on the table!
<GurneyBuchanan[m]>
s/worthwile/worthwhile/
<tobhe[m]>
fex has worked for me in the past too on my t14s
<tobhe[m]>
haven't tried for a while though and installed it from their ppa
<JensGlathe[m]>
oof these freezes are something
<kuruczgy_>
tobhe[m]: I don't use a rootfs, I reuse the bubblewrap based FHS env that the steam package uses anyway on Nix. Here is my setup if you are curious: https://codeberg.org/kuruczgy/aarch64-gaming/
<tobhe[m]>
awesome, thanks! glad I asked, that sounds very interesting
<jhovold>
JensGlathe[m]: no freezes here still, what compositor are you using? and which kernel?
<jhovold>
and on which machine?
<JensGlathe[m]>
6.16.0-rc3-jg-1, Wayland. Was happily typing a commit message, switched windows to look sth up, moved the mouse, then it stuck. After a minute or so it rebooted. Snapdragon Dev Kit
<jhovold>
is that wlroots, or gnome or something else?
<JensGlathe[m]>
sorry, gnome 48
<jhovold>
and that devkit it x1e, right?
<jhovold>
is*
<JensGlathe[m]>
yes
<jhovold>
robclark: some people are seeing these freezes, other like me have never hit them, could it be some fence regression that triggers more easily with gnome-shell?
<jhovold>
using wlroots myself
* robclark
using standard gnome-shell
<jhovold>
and no issues?
<robclark>
(occasionally test hyprland, but day to day it is g-s)
<jhovold>
but you said you had not moved to 6.16-rc yet, right?
<robclark>
yeah, still on 6.15-rc7 plus newer msm-next plus a bunch of WIP stuff (sparse/vm_bind, etc)
<robclark>
I have seen some crashes.. but they show up in `journalctl -b -1`.. the ones unrelated to my WIP don't appear drm related
<robclark>
(well, I do get some dpu related smmu faults sometimes when I wake up to lock screen... seems to only happen when I have external dp plugged as well)
<jhovold>
yeah, hypervisor resets could have different causes, it just seems there may be some gpu/display related regression going on here
<jhovold>
i guess you also run the absolute latest mesa unlike most people here
<robclark>
hypervisor resets could be power related? Touching unclocked hw block?
<tobhe>
JensGlathe[m] mentioned this happens on the devkit so it is probably using external dp
<jhovold>
oh, yeah, any system error would be trapped by the hypervisor and trigger a reset
<robclark>
My system mesa is stock f42, but I test w/ ToT mesa (using script to set some env vars to point to non-system mesa.. but `meson devenv` should be roughly equivalent)
<jhovold>
a pain to debug
<robclark>
yeah
<robclark>
I wish we had consoleramoops
<jhovold>
but random freezes + hypervisor watchdog timeout and resets during light use, sounds like a gpu/display issue rather than power (e.g. during hotplug or suspend)
<jhovold>
think we hit something similar at one point with the x13s, and it only affected some compositors (maybe gnome shell) that were using more fancy features
<robclark>
fence issue would probably not look like a system reset.. or at least I can't think of any reason that it would.. it would look more like tearing or screen flickering. (There have been some compositor bugs in that area)
<robclark>
is it specific to having external display connected, or not?
<JensGlathe[m]>
Mouse stopped dead, no other reaction. After a while, reset.
<krzk>
robclark: in my case not. Happen without anything plugged. Also happen now on stock ubuntu installers - 24.10 and 25.04
<jhovold>
I don't think so, but I also don't see it myself and there quite a bit of noise in these reports
<robclark>
idk if you can repro it while connected via ssh from another device running `dmesg -Hw`?
<robclark>
I suppose maybe that isn't the latest bios anymore
<robclark>
hmm, nothing too interesting there.. idk what those audio errors are but presumably unrelated?
<jhovold>
I'm not on the latest either
<jhovold>
could be secondary issues
zetam has joined #aarch64-laptops
SpieringsAE has quit [Quit: SpieringsAE]
hogliux has joined #aarch64-laptops
<hogliux>
FWIW: I see the freezes + reboot about once every day or two and no journal logs. To debug, I've been streaming my journalctl via netcat to my router but there is never anything at the time when the freeze/reboot ocurred.
<hogliux>
I'm on 6.15, with mesa from kiask ppa and run stock gnome with wayland on Ubuntu 24.10. Slim 7x DMI: LENOVO 83ED/LNVNB161216, BIOS NHCN57WW 01/03/2025
<hogliux>
I don't have an external display connected but a USB etehernet adapter and sometimes USB headphones. But I also see it regularly happen with nothing connected. But never when the system is under load.
ravikant_ has quit []
<jhovold>
hogliux: which 6.15 kernel is that exactly? mainline, my wip branch or something else?
<hogliux>
It's your branch (wip/x1e80100-6.15) but then with a bunch of patches on top - mainly camera, bluetooth. I basically manually apply the same patches that kuruczgy applies on his slim 7x nix recipes.
<hogliux>
I've always run your branch (for a year now) and I've had the issues also happen without any extra patches
<hogliux>
... well not quite a year. Since August/Sept 2024
<jhovold>
hogliux: ok, always a bit worried about extra patches, there's a lot around of varying quality, so best to make sure it's reproducable with mainline or my wip branch
<jhovold>
floating around*
<jhovold>
but perhaps some interaction with user space explains why only some people hit this if it's been there since 6.15 or further back
mani_s has quit [Remote host closed the connection]
hogliux has quit [Remote host closed the connection]
jglathe_angrybox has joined #aarch64-laptops
<robclark>
is there any correlation to bios fw version? or device? or DE?
<hogliux>
I have mostly everything identical to kuruczgy except I have a newer BIOS version (but the issue also occurred for me on the same version that kuruczgy is on) and desktop environment/WM
<hogliux>
@kuruczgy which desktop environment/WM do you use? I could try using the same as you for a few months and see if I can reproduce the problem
<kuruczgy[m]>
run it with WLR_RENDER_NO_EXPLICIT_SYNC=1
<Meti[m]>
Hi, I wanted to ask; what's the state of Linux support with the X1P42100? Last I checked the fan, sound, and gpu (nor opengl) worked
<JensGlathe[m]>
which model I need to ask
<JensGlathe[m]>
ThinkBook 16 is fully supported except hdmi
<JensGlathe[m]>
Zenbook A14 I guess, too
<JensGlathe[m]>
Omnibook x14 fe1 too
<JensGlathe[m]>
GPU since a week or so
<JensGlathe[m]>
Vivobook has its fan issue
<JensGlathe[m]>
but otherwise good, also GPU support
<JensGlathe[m]>
acer Swift Go also supported
<JensGlathe[m]>
no dtbs yet: Yoga Slim 7x, T14s
<JensGlathe[m]>
currently working on: Ideapad Slim 5x, Ideapad 5 2-in-1
zetam has quit [Ping timeout: 480 seconds]
<robclark>
oh, didn't realize there were x1p42 7x/t14s
<alexVinarskis[m]>
yup now with GPU on Zenbook A14 everything but HDMI can be working. Sound is upstreamed but did not land yet, camera is out of tree still, everything else just works.
<Douloureux[m]>
does anyone know the status for the x1e80100 surface laptop 7?
<alexVinarskis[m]>
valpackett: is the v1 series for Dell Latitude that you mailed upstream the latest state, or do you keep somewhere a more upto date branch?
<bamse>
Douloureux[m]: i believe there are still some core things missing to talk to the surface hub (if that's the name of it)... konradybcio knows better
<konradybcio>
there's a suspend issue, possibly related to the hub, and I'm yet to crack the code on the trackpad communications..
jglathe_volterra has joined #aarch64-laptops
<Meti[m]>
<JensGlathe[m]> "acer Swift Go also supported" <- Swift go 14 ai
<Meti[m]>
We talked before, I had the BIOS issue
<JensGlathe[m]>
yeah I remember
<JensGlathe[m]>
no change re fan
<JensGlathe[m]>
As I said I'm afraid nobody is working on it
<Meti[m]>
mm, I'll see myself if it's really messed up
<Meti[m]>
GPU and sound work now though?
<JensGlathe[m]>
let's say "should"
<Meti[m]>
mm
<JensGlathe[m]>
There are so many models its hard to keep track. The nodes for gpu should work, the nodes for audio are maybe a bit more variable.
<Meti[m]>
Audio is not that important anyways
<Meti[m]>
Where can I download this image from?
zetam has joined #aarch64-laptops
<JensGlathe[m]>
wait a day or two then its an updated image
<JensGlathe[m]>
for GPU you need patched Mesa, I have that on the image already.
<Meti[m]>
Will let you know ab the fan when I install it
<genius1237[m]>
does anyone know if there is a way to edit/disable a node in the device tree to make it look like the device doesn't have a battery at all?
<genius1237[m]>
Would disabling one of the pmics do this?
pabs has quit [Remote host closed the connection]
pabs has joined #aarch64-laptops
<steev>
whatever loads adsp, though you'd lose the rest of the remote procs i'd suppose
<genius1237[m]>
well I'd need remoteprocs for external video out
<JensGlathe[m]>
Then the question is what do you want to do. Charge limiting?
<genius1237[m]>
I have no battery, the system thinks a battery with 0% charge is plugged in and systemd triggers a critical shutdown. I can disable the systemd thing, but wondering if there is a way to have the device tree reflect that there is no battery
<JensGlathe[m]>
Never made one for the Dell IMO. You could go from the newest (Ideapad Slim 5x) and work from there. Inner workings doc is lacking, though. Need to go to sleep now 🙂
<lynxy>
which of the *many* different power management tools would one recommend for the snapdragon devices?