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
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
nothorseface has quit [Ping timeout: 480 seconds]
<bamse>
robclark: we've had this show up in a number of discussions, i'd prefer that we encode the actual fact we're affected by...rather than defining some generic state which currently implies our fact
<bamse>
robclark: specifically, it would/might give false positives if people where to run an alternative hypervisor, and could give false negatives if one where to run a version of gunyah without the restrictions solved by the zap shader
<robclark>
bamse: just tell me what you want the dtb to look like in the various scenarios, and then we can figure out how to make the sw fit that ;-) But the entire range of (possibly implausible scenarios) points me to continuing with how the driver works and express the difference via dtb
chrisl has quit [Read error: Connection reset by peer]
chrisl has joined #aarch64-laptops
<bamse>
robclark: zap-shader node present or not seems to cover the presented scenarios, am i missing some case there?
<robclark>
not really.. that is the status-quo solution that I pointed out of the email thread ;-)
<robclark>
drawback is maybe bootloader needs to do dtb patching/overlay
<robclark>
which seems to me just a matter of someone banging on a keyboard a bit
<robclark>
given that this isn't something that is all that hard to do
<bamse>
yeah, that is indeed a drawback, but there are several other cases where that would be necessary
<robclark>
at least in the laptops (sc8280xp and x1*) we do indeed need some unrelated dt patching.. idk about devices that idk about
<bamse>
well, if you change the world presented to the OS, then you need to update the description of that world as necessary
<robclark>
that was my opinion too
<robclark>
I just wanted others to weigh in on the thread to make sure it isn't only just my singular opinion ;-)
chrisl has quit [Ping timeout: 480 seconds]
<bamse>
robclark: +1, and done
<robclark>
thx
nothorseface has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
<_merk>
you lot certainly seem to be all about the srs business (;
<_merk>
getting shit done
<robclark>
umm, it's a dirty job but someone has got to do it?
<_merk>
robclark: why does your name look/sound so familiar?
<_merk>
anyway it's lunch time
<robclark>
I do some things to make gpu work on these things ;-)
nothorseface has quit [Read error: Connection reset by peer]
norwoodites has joined #aarch64-laptops
pinskia has quit [Ping timeout: 480 seconds]
<_merk>
robclark: i'll need a tree to try building with the gpu working on this snapdragon sometime soon
<_merk>
i'm about to enter another tribunal in 30 mins then i'm free to go home
<robclark>
specific path for firmware-name
<robclark>
so base support for x1e is already in place.. ofc you need to get the fw files, it should only be the zap fw that is device specific due to how fw signing works.. beyond that you need zap fw node with the correct fw path for your device.. and then it should all work.. so like something equiv to https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/qcom/x1e80100-lenovo-yoga-slim7x.dts#L509 but with a device
<robclark>
and ofc mesa 24.2.x or newer
<_merk>
hmm
<robclark>
`dmesg | grep drm` should give you some hints if fw is not found
echanude has quit [Ping timeout: 480 seconds]
<_merk>
[ 3.860347] msm_dpu ae01000.display-controller: [drm:adreno_request_fw] loaded qcom/gen70500_gmu.bin from new location
<_merk>
i got messages like that
norwoodites is now known as pinskia
<_merk>
i did just update mesa through pacman yesterday i think
<_merk>
i'll take another look at glxgears -info
xroumegue has quit [Ping timeout: 480 seconds]
<_merk>
Running synchronized to the vertical refresh. The framerate should be
<_merk>
approximately the same as the monitor refresh rate.
<_merk>
GL_VENDOR = freedreno
<_merk>
yes!\
<_merk>
it's working!
<_merk>
yay
<robclark>
\o/
<_merk>
i gotta try GL in enlightenment now
<_merk>
but i'm having bluetooth audio problems that dont happen in gnome but do in e
<_merk>
i can't switch to the a2dp acc sink on my headphones
<_merk>
and it thinks im on a phone call and sounds crap
<_merk>
oh i have to charge my headphones now anyawy so perfect timing
<_merk>
brb
dlg has quit [Remote host closed the connection]
dlg_ has joined #aarch64-laptops
<_merk>
raster isn't around to tell
<_merk>
yay it works
<robclark>
bt is probably something others know about more than me.. gpu things I know about
<_merk>
the bluetooth thing is a bug with pipewire/bt, thats ok i'll handle it
<_merk>
but sound on the speakers would be fantastic!
<robclark>
sound on yoga 7x seems ok, but I've mostly kept it at "don't disturb others around me" levels
<robclark>
and defn not a thing I'm expert on.. since it isn't a gpu
<_merk>
any chance of sound on the asus vivobook?
xroumegue has joined #aarch64-laptops
<_merk>
oh robclark what about touchscreen?
<robclark>
re: sound and touchscreen.. they aren't gpu.. I know (but don't follow too closely) that there is sound stuff in flight.. but in general these are things that others around here know better
<_merk>
ok
<_merk>
thats ok i can wait
<_merk>
(; thx for all your hard work
<robclark>
as far as gpu, since you have fw sorted, ToT mesa has conformant vk 1.4 as of ~1week ago... but I'll leave others to help with non-gpu things
<robclark>
np :-)
<_merk>
hmm cool
chrisl has joined #aarch64-laptops
<_merk>
i'll have to hack up a chroot to run steam i guess on arch
<_merk>
as it's not multilib/arch
<_merk>
okk i gtg bbl thx
<robclark>
wip for vkd3d dx12 support.. kernel part might be ready for v6.14 or v6.15 and userspace in same timeframe but pre dx12 should already work
<robclark>
so early next year should be fun for windows games on arm linux
chrisl has quit [Ping timeout: 480 seconds]
<kuruczgy[m]>
re steam: I got some games running using fex-emu, linux games seem to run fine (I tried Portal 1+2, HL1, and Factorio), haven't tried any windows games yet.
<kuruczgy[m]>
Though Portal 2 did once crash the whole machine... from inside the VM.
<kuruczgy[m]>
Also interestingly my Steam only properly works inside QEMU, natively it tends to crash. (Environments should basically be the same inside and outside the VM, so really not sure what could be the issue.)
<robclark>
gpu hang on cpu crash? And if latter can you catch it under gdb? (although in general a better topic for #freedreno and/or mesa gitlab issues)
<robclark>
s/on/or/
<kuruczgy[m]>
I have no idea yet. The Steam-not-working-natively issue is bugging me much more right now. But once I have solved that and I can still repro the Portal 2 crash with a reasonable frequency I could look a bit more into it, sure.
<kuruczgy[m]>
So after hours of bisecting (I think I need to improve my bisection setup) I think I found the culprit for the systemd-boot-messages-not-appearing issue: 4c3d9c134892c4158867075c840b81a5ed28af1f ("x1e80100: Add debug uart to Lenovo Yoga Slim 7x")
<kuruczgy[m]>
macc24: are you using systemd? I guess this patch causes systemd to write logs to uart, but not to the screen for some weird reason. Is it working fine for you, could this be some NixOS specific issue?
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
ungeskriptet_ has joined #aarch64-laptops
ungeskriptet has quit [Ping timeout: 480 seconds]
ungeskriptet_ is now known as ungeskriptet
echanude has joined #aarch64-laptops
tobhe has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
tobhe_ has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
krzk has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
<macc24>
i am using systemd
<macc24>
do you have console=tty1 in your cmdline?
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
enyalios_ has joined #aarch64-laptops
enyalios has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
alfredo has joined #aarch64-laptops
krzk has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
SpieringsAE has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
iivanov_ has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
jhovold has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
alfredo1 has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
alfredo has quit [Ping timeout: 480 seconds]
alfredo1 is now known as alfredo
iivanov_ has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
iivanov_ has joined #aarch64-laptops
iivanov has quit [Read error: Connection reset by peer]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
srinik has joined #aarch64-laptops
hogliux has joined #aarch64-laptops
<hogliux>
A question for the yoga slim 7x folks out there: every since using linux on the device (6.11 rc days) up until now (6.12), I'm getting random laptop hangs about once a week.
<hogliux>
The laptop will just freeze and then reboot after a few seconds. This also happens when I boot into EL2. I've not been able to figure out what is causing this.
<hogliux>
The rare times I've booted into Windows, I also get BSODs (much more frequently in Windows). So I'm starting to think this may be an issue with my motherboard.
<hogliux>
kuruczgy: As I'm running a very similar kernel/setup as you: do you ever have your machine freeze and then reboot?
srinik has quit [Read error: Connection reset by peer]
<kuruczgy>
macc24: nope, but that sounds like something that might help. Will try it later in the afternoon, thanks.
<kuruczgy>
hogliux: nope, for me it's very stable. The only crashes I have gotten was overheating (but that's on orderly shutdown by the kernel and not a crash), qemu without `id_aa64mmfr0.ecv=1`, and Portal 2.
alfredo1 has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
alfredo has joined #aarch64-laptops
alfredo1 has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
norwoodites has joined #aarch64-laptops
pinskia has quit [Ping timeout: 480 seconds]
alfredo1 has joined #aarch64-laptops
<TheBITLINK[m]>
hogliux: I'm experiencing the same kind of hangs (I have an asus though), for me they usually happen within the first 5 minutes of booting into Windows, and it's annoying since I have to reboot multiple times until it randomly stops happening, the whole system freezes, after a while the fans ramp up to 100% then after a few seconds more it turns off by itself
alfredo has quit [Ping timeout: 480 seconds]
alfredo1 is now known as alfredo
<macc24>
hogliux: try running mprime to see if it's cpu cores weirding out
<macc24>
small setting for cpu cores, large for ram and cache
Caterpillar has joined #aarch64-laptops
hogliux has quit [Remote host closed the connection]
alfredo has quit [Quit: alfredo]
craftyguy has quit [Remote host closed the connection]
craftyguy has joined #aarch64-laptops
<kuruczgy[m]>
macc24: yep that works, thanks.
craftyguy has quit [Remote host closed the connection]
craftyguy has joined #aarch64-laptops
<steveej[m]>
kuruczgy: i'm also on nixos. the journal seems to be working properly here. does it just stop altogether for you? or how would i acknowledge or deny the symptom here?
craftyguy has quit [Remote host closed the connection]
craftyguy has joined #aarch64-laptops
<kuruczgy[m]>
steveej: I think 6.13-rc2 + no `console=tty1` on the command line should be enough to reproduce the issue, I don't believe it's NixOS specific.
agl has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
<steveej[m]>
my cmdline: initrd=\EFI\nixos\f4nh3n2v4xmjyfvifmqb16y3cbrgcih7-initrd-linux-6.13.0-rc2-initrd.efi init=/nix/store/i74iyhkzh5vinp60891gaaw7d778zbsv-nixos-system-steveej-x13s-25.05pre-git/init dtb=dtbs/x13s.dtb clk_ignore_unused pd_ignore_unused arm64.nopauth psi=1 root=fstab loglevel=4 so i don't have the console instruction in there
agl has joined #aarch64-laptops
<kuruczgy[m]>
ah but this is a yoga slim 7x specific issue, you have the x13s, oops...
<steveej[m]>
ah yeah, sorry
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<macc24>
steveej: i guess it's because x13s doesn't have console-capable uart enabled
<macc24>
and it just falls back to tty1 instead
todi has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
alfredo1 has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
alfredo1 is now known as alfredo
chrisl has quit [Ping timeout: 480 seconds]
davidinux has joined #aarch64-laptops
davidinux has quit [Quit: WeeChat 4.3.1]
davidinux has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
alfredo has quit [Ping timeout: 480 seconds]
<_merk>
does anyone have suspend and resume working with the x1e?
<_merk>
im using enlightenment/acpid
<_merk>
dunno if it works with gnome etc
todi has quit []
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
todi has joined #aarch64-laptops
SpieringsAE has quit [Quit: Leaving]
<kuruczgy[m]>
_merk: Yep it works for me, though suspend power consumption is still not optimal. Use `systemctl suspend` or even `echo mem > /sys/power/state` to bypass stuff from the DE for testing.
<macc24>
i recall it working fine-ish on my slim7x, tho no suspend-on-lid-close :(
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
todi has quit []
norwoodites is now known as pinskia
srinik has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
davidinux has quit [Quit: WeeChat 4.3.1]
srinik has quit [Ping timeout: 480 seconds]
<JensGlathe[m]>
Good news. Testing around with a [D-Link DUB-M520 USB-C hub](https://www.amazon.de/dp/B07XQJKMS7?ref=ppx_yo2ov_dt_b_fed_asin_title) with Ethernet and HDMI and keyboard connected on on the X13s, works. HDMI gets 2 lanes, 4k@30Hz, the hub gets also 2 lanes for USB3.0
<JensGlathe[m]>
and it works in both orientations
<JensGlathe[m]>
on both type-c connectors. That's an improvement
laine has joined #aarch64-laptops
<JensGlathe[m]>
Hama type-c to HDMI adapter only works in swapped orientation 🤔
<JensGlathe[m]>
6.12 and external monitor seem to get along better.
<JensGlathe[m]>
The adapter shipped with the Snapdragon Dev Kit works only in swapped direction, unswapped will give you 640x480 output and an error message
<JensGlathe[m]>
`[40803.998782] [drm:dp_bridge_get_modes [msm]] *ERROR* failed to get DP sink modes, rc=0`
<_merk>
kuruczgy[m]: and a simple power on will resme?
chrisl has joined #aarch64-laptops
<kuruczgy[m]>
_merk: lots of things can wake it up. Pressing the power button, pressing a key on the keyboard, plugging in the charger. (This is the Yoga Slim 7x, importantly, the lid switch is not working.)
<_merk>
kuruczgy[m]: ok
<_merk>
i think the pid switch no wirkies on the asus vivo too then
<_merk>
is that a dt so driver issue?
<_merk>
lid*
<_merk>
its hard for me on this qwerty
<_merk>
or*
<macc24>
i've spent far too much time working on the lid switch and even i have no idea why it's doing that
<macc24>
probably some magic setting in the EC
<_merk>
hm ok
<_merk>
good moaning everyone
<_merk>
vyvanse is the breakfast of kings
<Jasper[m]>
I don't use vyvanse, but agreed
<JensGlathe[m]>
Hmm on the HP X14 only type-c port 0 works with the HDMI adapter, but yay
<macc24>
i should probably be put on it but no one diagnosed adhd in me so i'm going to make it everyone else's problem :D
<JensGlathe[m]>
first ever on x1e with retimer
chrisl has quit [Ping timeout: 480 seconds]
<_merk>
macc24: not in a marcacistic way i hope lol
<macc24>
_merk: well i'd rather spin around on my chair waiting for something to compile instead of boiling silently
<macc24>
tho it gets bad when i zone out when talking to people and i asked them to repeat themselves all the time :(
<_merk>
yeah and hyperfocus on scripting
<_merk>
sounds about right
<_merk>
i dont want to put stickers on my keyboard so my subconscious doesn't get confused when im typing
<_merk>
cos the backlight is so prtty
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
hogliux has joined #aarch64-laptops
<hogliux>
macc24: thanks for suggesting mprime. can't get it to repro with mprime. Tried all possible command line option combinations. As I said, it's quite rare for me - maybe once a week. And it never happend when the system is under load. Usually when I'm in vs code editing some code.
<hogliux>
TheBITLINK: that aligns with what I'm experiencing in Windows. Usually shortly after boot when I start opening apps.
<hogliux>
TheBITLINK: Like I said, in Linux it's a lot less common.
<hogliux>
kuruczgy: TheBITLINK: did you swap out your ssd? I bought a 2 TB ssd and replaced the internal one. Maybe the slim 7x really doesn't like that and it uses too much power or something.
hogliux has quit []
<kuruczgy>
hogliux: Nope, I use the stock SSD
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
sally has quit [Remote host closed the connection]
sally has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
svarbanov has joined #aarch64-laptops
svarbanov_ has quit [Read error: Connection reset by peer]