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
abc123bac2[m] has joined #aarch64-laptops
<abc123bac2[m]>
recently got a ideapad 5 2 in 1 (x1p42100) with a broken screen, intending to use it has a headless desktop. this doesn't seem to be a linux specific issue (happens on windows too) but it looks like this laptop doesn't output on USB-C/DP when the internal display's edp cable is unplugged from the motherboard.
<abc123bac2[m]>
not sure if it extends to all snapdragon x laptops, or just mine. wondering if anyone here knows anything
chrisl has quit [Ping timeout: 480 seconds]
<robclark>
you might approximately be the first one to test this scenario, but I assume it is similar to the devkit/nuc thing which has no eDP?
<robclark>
got dmesg.. and `cat /sys/kernel/debug/devices_deferred`? Could be something about panel probe is blocking the drm driver (but lumag had an interesting idea that might solve that)
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<abc123bac2[m]>
will post in a bit, need to open up the device to unplug the edp cable
<abc123bac2[m]>
In both cases, this is the same cat /sys/kernel/debug/devices_deferred -> c42d000.spmi:pmic@0:rtc@6100
<abc123bac2[m]>
I'm actually able to see grub and a small duration of the kernel boot logs in the 2nd case. It all goes black after that.
<abc123bac2[m]>
In the first case, it goes black for a moment, and then GDM appears (sadly with the main parts of the UI on the connected but non functioning eDP display). I can login to gnome, open settings and disable the internal display in that case.
hexdump0815 has quit [Ping timeout: 480 seconds]
tobhe has quit [Ping timeout: 480 seconds]
<abc123bac2[m]>
the system as it is (without edp plugged in), stays online for 5 min and reboots on it's own. Been doing that for the last 5-10 min in a loop. On one of the reboots, the external display came up at a super low resolution and before I could check anything, it rebooted again
<abc123bac2[m]>
These are the last lines in journalctl -b -1 before the reboot
<abc123bac2[m]>
kernel: [drm:dpu_kms_wait_for_commit_done:524] [dpu error]wait for commit done returned -110
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
mbuhl has quit [Remote host closed the connection]
mbuhl has joined #aarch64-laptops
vanveldt has quit [Ping timeout: 480 seconds]
<JensGlathe[m]>
abc123bac2: which dt do you use
<abc123bac2[m]>
I used the image you put on google drive for ideapad 5 and that dtb (which is a slightly different device, yes)
<abc123bac2[m]>
I dumped the DSDT on mine, but haven't looked at the diff between the two yet
<JensGlathe[m]>
Would be enough to remove the mdss_dp3 node to not have internal display, not enabling it (and the phy) should be sufficient
<JensGlathe[m]>
The type-c dp altmode works in only one orientation
chrisl has joined #aarch64-laptops
<JensGlathe[m]>
(From my current status on the tb16)
<abc123bac2[m]>
I'll try that. I also wanna try using a newer kernel with the patches for the GPU on the X1P42, I saw you have a branch with that
<abc123bac2[m]>
Is there a reason why the DP out works for GRUB but not after booting?
chrisl has quit [Ping timeout: 480 seconds]
<JensGlathe[m]>
6.15.0-jg-6 should work nice enough, but orientation issue.
<JensGlathe[m]>
Don‘t have the x1p gpu firmware files yet
<JensGlathe[m]>
Bios sets up dp (probably) but driver init very likely kills it. On the dev kit you get grub, after selecting no screen, eventually output again with windows or linux
<abc123bac2[m]>
Thanks for the suggestion. I deleted the mdss_dp3 node and am able to boot. The behavior is the same as what you described (grub, no screen, output with linux)
<abc123bac2[m]>
Hope someone can figure out what the error is though, and fix upstream
<steev>
the rockchip portion didn't apply (to .14 or .15) but since i only care about the qcom portion, i'm okay with dropping that one
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<JensGlathe[m]>
Nice
<JensGlathe[m]>
abc123bac2: can you proved some more data on the device for distinguishing them (if required)
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<valpackett>
oh huh, went to check for bios updates, learned that it's common between Dell Inspiron_5441_7441_Latitude_5455_7455 and the codename is Thena
<jdb[m]>
abc123bac2: robclark: I can confirm a similar experience
<jdb[m]>
Whenever I was trying to bring up the built-in display for the Surface Pro 9, each time I tried a non-working config, it was blocking the external output via USB-C
<jdb[m]>
Whereas I had a known working config for external display...
<jdb[m]>
It was annoying as I had to connect remotely via ssh from another computer to see the dmesg output
<jdb[m]>
If the probe could be non-blocking, that would be a great improvement
<jdb[m]>
And it would make the Linux config via devicetree more robust to hardware failures
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<valpackett>
just had another random hang after 1.5 days of uptime, during light load, not doing anything, just moving the cursor. it gets so frozen it doesn't respond to magic sysrq. could it be something power management related?
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
HarrisonV has quit [Remote host closed the connection]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
Mary has quit [Quit: .]
Mary has joined #aarch64-laptops
Mary has quit []
Mary has joined #aarch64-laptops
Mary has quit [Quit: .]
Mary has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
jglathe_volterra has quit [Remote host closed the connection]
Mary has quit []
Mary has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<deathmist>
I also had a random full system hang on X1E Vivobook yesterday, running a 6.15.0-jg-5 tree based kernel myself
_trat has joined #aarch64-laptops
<abc123bac2[m]>
Jens Glatheyeah sure let me know what you need
chrisl has joined #aarch64-laptops
zetam has joined #aarch64-laptops
_trat has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
zetam has quit [Ping timeout: 480 seconds]
pbrobinson has quit [Ping timeout: 480 seconds]
indeo has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
zetam has joined #aarch64-laptops
pbrobinson has joined #aarch64-laptops
ektor52 has quit []
ektor5 has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
indeo has quit [Ping timeout: 480 seconds]
indeo has joined #aarch64-laptops
fantom has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
todi has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
indeo has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
<steev>
ah, nope, still get the aer
<JensGlathe[m]>
SN770M, right?
todi has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
<konradybcio>
valpackett: "computer goes bad" is unfortunately not enough to take any meaningful conclusions..
<konradybcio>
any chance systemd saved the dmesg?
todi has joined #aarch64-laptops
<steev>
yeah jens
<steev>
WD BLACK SN770M 2TB
<JensGlathe[m]>
I was about to put in my SN770 for test, too.
<steev>
they're correctable errors so...
fantom has joined #aarch64-laptops
<steev>
i did just update the firmware to latest though (i think)
indeo__ has joined #aarch64-laptops
<steev>
yeah, 731130WD is now the latest firmware for mine
<zetam>
About <valpackett>'s “[PATCH 0/4] Add support for Dell Latitude 7455 (X1E-80-100)”: I have a Latitude 7455 that still won’t boot, and I’d like to try these patches, could you suggest which kernel version or tree is best suited for them? linux-next, or another?
chrisl has quit [Ping timeout: 480 seconds]
<JensGlathe[m]>
I have it on my tree as well
<JensGlathe[m]>
Question for the Yoga Slim7 torturers: Is the wcn7850 a m-2 card on it or soldered-on?
<HdkR>
Oh, hah. I partially read the sentence. Yes, soldered :D
<JensGlathe[m]>
Was about to compose a spicy answer already 😎
<HdkR>
Brain rats getting to me today.
<JensGlathe[m]>
2 fans, wow
<JensGlathe[m]>
and they don't behave?
<HdkR>
Yea, I haven't been able to get the thing to thermally throttle even throwing 60W+ of load at it.
<JensGlathe[m]>
good
<JensGlathe[m]>
but ig they don't throttle on Linux, they switch off (seen on HP Omnibook X14)
<HdkR>
Not sure there.
<JensGlathe[m]>
The X14 makes a lot of noise, and if the airflow is sufficient it will power through - sucking the battery dry since the 65 PSU is not enough
<JensGlathe[m]>
The tb16 will also make a lot of noise, but no high pitched whine - haven't been able to throttle / switch it off yet
monkeybusiness has joined #aarch64-laptops
zetam has quit [Ping timeout: 480 seconds]
etehtsea has quit [Ping timeout: 480 seconds]
jglathe_volterra has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<steev>
theres still something funky with soundwire
<anthony25>
JensGlathe[m]: it throttles, just the frequency as shown by the governor is lying
<anthony25>
someone here explained it to me, I don't remember whom, when I was complaining that the laptop shutdowns when too hot, and that I didn't see it throttling
<anthony25>
the shutdown part I think has been fixed, it hasn't happened to me for a while
<valpackett>
zetam: linux-next is what i use, but the 7455 dt patch is already in jglathe's tree for example
<valpackett>
we really need to unify latitude/inspiron tbh because they're such close variants of the same thing that they share the bios update file
<valpackett>
konradybcio: nothing interesting in journalctl -b-1, the last message is a systemd-run scope for a terminal starting. it's an entirely sudden hard freeze, so hard that magic sysrq doesn't respond, seemingly not correlated to anything in particular (though we thought it was slightly more correlated to audio playback but eeehhh) and it happens for many people on different laptops
<valpackett>
if someone with internal debug equipment could reproduce and investigate it, that would really save the day ;)