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
<valpackett>
looks like the excess power consumption was mostly due to lack of ASPM
<valpackett>
i rebooted without pd_ignore_unused but with pcie_aspm=force, pretty much no change, force did nothing.. used the pciset script and there it is
<valpackett>
now i get 3.8W on low brightness idle again. and 2.6W on screen-off
<valpackett>
let's see if any issues appear with ASPM L1 on everything :)
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
<anthony25>
oh cool!
<anthony25>
I think I tested once, and got random freezes, but it was ages ago
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<valpackett>
huhhh so the random freezes *are* caused by aspm?? makes sense considering they stopped at the same time aspm got disabled
<valpackett>
well that narrows things down
<valpackett>
also sort of makes the "it was happening more for ppl who swapped the ssd" phenomenon make more sense
<mani_s>
valpackett, pd_ignore_unused has nothing to do with aspm
<mani_s>
IIRC, x1e doesn't support L1ss due to phy driver limitation
<mani_s>
but l0s should work
<mani_s>
Ah, sry. it is the other way around. No L0s, but L1ss are supported
chrisl has joined #aarch64-laptops
jhovold has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<mani_s>
abelvesa, lumag Sometimes external DP is failing to detect the monitor and falling back to 'Unknown display'. Here is the dmesg log when it happens: https://pastebin.com/9yD4BrVf
<mani_s>
this is on x1e thinkpad running johan's 6.16.0-rc4+ branch
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
hl` has quit [Remote host closed the connection]
hl` has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<alexVinarskis[m]>
does anyone else experience issues with built in screen on latest linux-next? On next-20250708,next-20250710 on Dell XPS internal screen (OLED version) stays black after boot, external still works. Gnome detects internal screen, no other errors. Suspend/resume, brightness adjustements do not fix it. Got one more person confirming same issue on XPS.
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<anthony25>
was there any change in the dts?
<deathmist>
valpackett: interesting, I assume you also just have SSD and WLAN as PCIe devices? for me SSD (with its root complex) at least seems to already be using L1 as expected on X1E Vivobook but WLAN has ASPM disabled but could use L1 and L0s L1 for its root complex and card itself respectively
chrisl has joined #aarch64-laptops
<valpackett>
alexVinarskis: hm, but brightness is definitely the one thing that broke on linux-next
<valpackett>
(my patch got an R-b but not merged yet)
<valpackett>
deathmist: yeah. ath12k has a disable in the driver somewhere
<valpackett>
The weird thing is that after BIOS updates, the SSD stopped having ASPM, even with pcie_aspm=force
<valpackett>
only setpci gets it back
<alexVinarskis[m]>
let me try to pick your patch maybe it fixes it here
chrisl has quit [Ping timeout: 480 seconds]
<alexVinarskis[m]>
valpackett: thanks, that fixes black screen as well here! didn't think to try it. Will drop a T-by later today, don't have the correct laptop with me.
chrisl has joined #aarch64-laptops
<valpackett>
s
<valpackett>
cool, makes sense that on oled it would be a different (worse) impact i guess
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
Lucanis_ has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
lczyk has joined #aarch64-laptops
<lczyk>
just discovered that my toaster, being slightly broken, trips fuses in my house. the router turning off proceeds to also bsod my laptop, so, effectively, i can bsod my laptop with my toaster. xD ( dell xps 9345, running 6.16.0-7-qcom-x1e )
<lczyk>
( already reported to @tobhe )
chrisl has quit [Ping timeout: 480 seconds]
<lynxy>
don't fix it or you'll break somebody's workflow
<tobhe[m]>
That's how I exit vi!
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
minecrell has quit [Quit: Ping timeout (120 seconds)]
sgerhold has quit [Quit: Ping timeout (120 seconds)]
sgerhold has joined #aarch64-laptops
minecrell 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]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
lczyk has quit [Remote host closed the connection]
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
lczyk has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
indy has joined #aarch64-laptops
<bryanodonoghue>
jhovold thanks for the ping - squeaky wheel gets the oil !
chrisl has joined #aarch64-laptops
lczyk has quit [Remote host closed the connection]
sudeepholla has joined #aarch64-laptops
<mani_s>
valpackett, reg. high power consumption. I noticed that aspm L1 is not getting enabled for the WLAN device and I know why. By default we enable L1ss for all devices on Qcom compute platforms
<mani_s>
and I'm going to send a patch to fix that
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
eluks has joined #aarch64-laptops
<anthony25>
mani_s: I'm super interested to test it, can you link the patch here if you send it?
jglathe_angrybox has quit [Ping timeout: 480 seconds]
FANTOM has quit [Ping timeout: 480 seconds]
<deathmist>
anyone with released X1E/X1P hw: would you mind checking https://github.com/TravMurav/dtbloader/issues/8 to see if your device isn't yet supported? collected a list of currently unsupported devices with devicetrees in various known locations there and I hope this helps somehow :)