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
GurneyBuchanan[m] has joined #aarch64-laptops
Tammieyem[m] has joined #aarch64-laptops
Eighth_Doctor has joined #aarch64-laptops
macc24 has joined #aarch64-laptops
ahoneybun[m] has joined #aarch64-laptops
KieranBingham[m] has joined #aarch64-laptops
dcavalca has joined #aarch64-laptops
alexVinarskis[m] has joined #aarch64-laptops
apple-corps[m] has joined #aarch64-laptops
mehdidjait[m] has joined #aarch64-laptops
smoorgborg[m] has joined #aarch64-laptops
steveej[m] has joined #aarch64-laptops
TangTang[m] has joined #aarch64-laptops
anonymix007[m] has joined #aarch64-laptops
chapstikk[m] has joined #aarch64-laptops
sadan[m] has joined #aarch64-laptops
jdb[m] has joined #aarch64-laptops
Treibholz[m] has joined #aarch64-laptops
noisycoil[m] has joined #aarch64-laptops
WeetHet[m] has joined #aarch64-laptops
n0nfl3x[m] has joined #aarch64-laptops
Timmy[m] has joined #aarch64-laptops
logan2611 has joined #aarch64-laptops
Jasper[m] has joined #aarch64-laptops
clover[m] has joined #aarch64-laptops
JosDehaes[m] has joined #aarch64-laptops
kuruczgy[m] has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
tobhe[m] has joined #aarch64-laptops
travmurav[m] has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
konradybcio has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
xroumegue has quit [Ping timeout: 480 seconds]
xroumegue has joined #aarch64-laptops
<valpackett>
hogliux: oh, shit, i did swap the ssd. not a 7x btw.
<HdkR>
Gotta watch out, those WD Black drives run hot AF.
<valpackett>
swapped the stock wd for the only other 2230 i had which was an SK Hynix 256gb gen3 OEM drive
tobhe has joined #aarch64-laptops
hexdump0815 has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
hexdump02 has quit [Ping timeout: 480 seconds]
<valpackett>
i'm a bit anti-WD with ssds right now since the whole "drives can't handle the load and just crap out" fiasco
tobhe_ has quit [Ping timeout: 480 seconds]
<valpackett>
oh and the freezes being ssd does make sense, i think at least sometimes they were the kind where the cursor moves but the rest doesn't react, which is exactly how it looks when nvme doesn't come back from deep suspend
chrisl has quit [Ping timeout: 480 seconds]
hexdump02 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<JensGlathe[m]>
Could it be that aspm is not supported by the drive, but signaled that it does? I remember something similar vaguely with SN770 and X13s. And I also disabled aspm for the I226V (NIC) in the DevKit for this reason.
martiert_work has joined #aarch64-laptops
martiert_ has quit [Ping timeout: 480 seconds]
<valpackett>
JensGlathe[m]: hmmm. maybe? apparently NVME_QUIRK_SIMPLE_SUSPEND (which helps with the on-resume thing) is the same as not having ASPM in terms of nvme_suspend
<SpieringsAE>
I have seemingly random crashes on my vivobook as well, also swapped the nvme to a 2TB one. Is this the pinebook pro with nvme all over again? lol
<SpieringsAE>
the original ssd looked very minimal as well, barely any chips on there
<SpieringsAE>
but yeah random moments, especially noticed it while playing morrowind, normally my laptop isn't on for very long periods of time so I don't really notice it I guess
<valpackett>
we're not actually sure *what* the freezes are :(
<valpackett>
they're seeeemingly correlated to audio playback of various kinds (mostly bluetooth?) but also apparently mostly among users who did swap ssds??
<valpackett>
in other audio news, after fully resetting the saved alsa knob state, seeeems like the wild momentary one-channel boost on the headphone jack is no more
<valpackett>
actually it still feels like there are some specific like, volume/frequency ranges that go more into the left channel, but the sort of normal average song volume no longer falls into that range
ksco has joined #aarch64-laptops
<valpackett>
it's so weird, literally when the sound is super quiet it gets panned to the left headphone
<icecream95>
With stock vivobook SSD and USB audio I haven't had any problems with OpenMW, maybe I should try with Bluetooth audio to see if that can cause it
dliviu has joined #aarch64-laptops
<icecream95>
I do play limited to 40fps and with the CPU downclocked though (both to save power and because it looks too smooth at 120fps), so maybe the lower load makes a difference
<SpieringsAE>
ayy fellow openmw enjoyer, I run it on 1440p at 100 fps cap, drops a little sometimes, but its pretty good. I was indeed using bluetooth audio while playing as well.
<SpieringsAE>
external 1440p monitor
reng has joined #aarch64-laptops
reng_ has quit [Ping timeout: 480 seconds]
<jdb[m]>
@ksco: I have an issue with EDID, but it's on a different laptop, I can't get the screen to power up on a Surface Pro 9 5G
dliviu has quit [Ping timeout: 480 seconds]
<jdb[m]>
On a ThinkPad X13s, I don't have this issue, the built-in screen works fine when loading the devicetree, I'm running Debian by the way
dliviu has joined #aarch64-laptops
hogliux has joined #aarch64-laptops
<hogliux>
valpackett: I don't think it's the SSD directly. Due to the issue, I swapped in the original SSD again but the freezes still happen. There is absolutely no correlation between IO load and the freezes so I don't think it's the temp of the SSD.
<hogliux>
valpackett: If I would have to guess, I think it may be something ESD or EMI issue: just because of the randomness where the issue might not show up for months but then sometimes happens a few times a day. Maybe replacing the SSD breaks some kind of ESD protection in the case?
<hogliux>
valpackett: But the SSD might also be a red herring: I'd assume that people who swap their SSD probably have the intention to use their laptops more for serious work. Maybe this groups just tends to use their laptops more and because the issue is so rare
<hogliux>
valpackett: only these people see it happening.
<JensGlathe[m]>
A load issue?
<hogliux>
valpackett: Another pointer on why I think it's not directly the SSD (but maybe indirectly): to debug the issue, I route all my kernel logs to my home server in realtime. There is nothing in the kernel logs when the issue occurs. So definitely not directly a SSD I/O error.
<hogliux>
JensGlathe[m]: I really don't think so either. Most of the day I'm just editing code/writing e-mails etc. Up until now it's always occured during one of these light weight tasks. Occasionally I recompile the entire ubuntu kernel and I've never had it happen then.
hogliux_ has joined #aarch64-laptops
<hogliux_>
Would would be really good to know, if x elite users on this channel have this issue and have *NOT* swapped their SSD. As a reminder: the symptoms of this issue is that your laptop completely freezes and then automatically reboots after 30-40 seconds
<JensGlathe[m]>
Hmm I had instability (but not really noticeable hangs) for a long time on the DevKit. Disappeared after removing the RTL8125 card, and the WCN7850 card because ath12k is sort of in a bugfixing storm. Adter some tweaks for the replacement Intel 2,5G card (in the A slot) its actually really stable.
<JensGlathe[m]>
I have 2 laptops where I have not swapped the SSDs, HP Omnibook X14 and ThinkBook 16. No hangs with reboot on both.
<hogliux_>
It also happens with Wifi disabled for me. It used to happen in Windows for me too - for others on this channel as well. Exactly the same symptoms. Even after swapping in back the old SSD. But I haven't been able to reproduce the issue anymore in Windows for a while now.
<JensGlathe[m]>
So its the UEFI firmware... 😈 Something in TZ
<hogliux_>
Maybe a software update fixed it in Windows, but maybe I'm just unlucky and if I would use Windows more (I hardly use it) it would happen there as well again. As it is so rare it's really hard to diagnose. I thought I had fixed it a few times in the past already.
hogliux has quit [Ping timeout: 480 seconds]
<SpieringsAE>
speaking of firmware, been seeing some patches over at coreboot for the x plus from google. Guess there might be a chromebook coming at some point based on it
<Jasper[m]>
Huh, interesting
chrisl has joined #aarch64-laptops
hogliux_ has quit [Quit: Leaving]
chrisl has quit [Ping timeout: 480 seconds]
<deathmist>
on X1E Vivobook with external display plugged in I've once had the laptop instantly reboot while just chilling on desktop iirc, think I tried to look into /sys/fs/pstore or whatever at the time but ofc that's not hooked up and I found no other logs I could look at. I don't remember it freezing for ~30s or so before rebooting but I'll be on the lookout, haven't replaced SSD
<deathmist>
myself
<deathmist>
btw still seeing weird burst charging behavior with the v2 qcom-battmgr-bat patches adding charge control way past set /sys/class/power_supply/qcom-battmgr-bat/charge_control_end_threshold which slowly seems to adds up to probably even 100%. when reached isn't charging supposed to fully stop until it drops under charge_control_start_threshold?
<ksco>
this tool can print that info, if you still have windows
pbrobinson has joined #aarch64-laptops
bionade24 has joined #aarch64-laptops
bionade24 has quit []
ksco has quit [Quit: Page closed]
ravikant_ has quit [Remote host closed the connection]
bionade24 has joined #aarch64-laptops
ravikant_ has joined #aarch64-laptops
craftyguy has quit [Remote host closed the connection]
craftyguy has joined #aarch64-laptops
craftyguy has quit [Remote host closed the connection]
chrisl has joined #aarch64-laptops
craftyguy has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
ksco has joined #aarch64-laptops
ksco has quit [Remote host closed the connection]
Stardust has quit [Read error: Connection reset by peer]
Stardust has joined #aarch64-laptops
<deathmist>
should e.g. /sys/devices/system/cpu/cpu*/cache/index3/size be expected to exist later? afaik there should be 6MB of L3 cache on X1E, no idea if that's expected to be exposed at all or perhaps through a different interface
chrisl has joined #aarch64-laptops
Caterpillar has quit [Read error: Connection reset by peer]
chrisl has quit [Ping timeout: 480 seconds]
<kettenis>
deathmist: I see the battery chargings slowly under windows as well on the vivobook
<deathmist>
I suspect something is up with ADSP firmware since it also appears to happen with the machine powered off, dunno if that's a known issue in general on X1
<anthony25>
you're talking about the max charge limit?
<deathmist>
yeah
<anthony25>
I can test on the slim 7x and tell you if there's also the problem, if no one did already
<anthony25>
how can you replicate it? you set the limit to something like 80%, and it still goes over after some time?
<deathmist>
I have the start value set at 50 with end at 55 but it never really starts going back but just keeps slowly going up over time thanks to larger burst charges
chrisl has joined #aarch64-laptops
SpieringsAE has quit [Quit: SpieringsAE]
chrisl has quit [Ping timeout: 480 seconds]
pbrobinson has quit [Ping timeout: 480 seconds]
rmsilva- has joined #aarch64-laptops
rmsilva has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
ravikant_ has quit []
loki_val is now known as crabbedhaloablut
<deathmist>
just measured it with the computer on over 3 hours and it seems to be charging at a rate of ~0.11 W/h
<deathmist>
so in my case I should have the battery at 100% again despite the set limit at 55% after 10 days
icecream95 has quit [Ping timeout: 480 seconds]
Grabunhold_ has joined #aarch64-laptops
Grabunhold has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
pbrobinson has joined #aarch64-laptops
<craftyguy>
is bluetooth working for others on the x13s with 6.15?
chrisl has joined #aarch64-laptops
<JensGlathe[m]>
Yes ofc
<craftyguy>
ok just checking, it's not for me, so I must have broken it somehow
<craftyguy>
is the kernel able to get the MAC for bluetooth now?
<travmurav[m]>
dtbloader can :^)
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
jannau has quit [Quit: WeeChat 4.5.1]
jannau has joined #aarch64-laptops
<JensGlathe[m]>
no
<JensGlathe[m]>
I have a hack in the dtb , and bootmac
<steev>
i still use my service
<steev>
not mine, but the one recommended on johan's wiki
jannau has quit [Quit: WeeChat 4.6.2]
<steev>
robclark: oh dang, congrats on the move?
<robclark>
surprise! :-)
<HdkR>
party party 🎉
jannau has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
jannau has quit [Quit: WeeChat 4.6.3]
chrisl has quit [Ping timeout: 480 seconds]
agl has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
agl has joined #aarch64-laptops
jhovold has quit [Ping timeout: 480 seconds]
jannau has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
jglathe_volterra has quit [Remote host closed the connection]
<jdb[m]>
Congratulations, Rob!
osmoz[m] has joined #aarch64-laptops
pbrobinson has quit [Ping timeout: 480 seconds]
<jdb[m]>
@ksco: I have a different display on my X13s here:
<jdb[m]>
panel-simple-dp-aux aux-aea0000.displayport-controller: Detected IVO R133NW4K-R0 (0x854b)
<steev>
jdb[m]: yours is touch i think
<jdb[m]>
indeed it is
<steev>
that's the one i have :( (the frown is because i purchased a non-touch but they shipped me touch)
<jdb[m]>
@ksco: I've tried the .dtb file you've linked, it works on my model but I'm using a different kernel version
<jdb[m]>
I'm using the regular Debian kernel images, linux-image-6.12.27-arm64 (6.12.27-1) for instance
<jdb[m]>
and I've tried 6.14 from Experimental: linux-image-6.14-arm64 (6.14.3-1~exp1)
<jdb[m]>
and now linux-image-6.15-arm64 (6.15-1~exp1) too
<osmoz[m]>
Hello, do you know where I can find resources to learn how the boot process on arm works ? I think I’m struggling because I don’t understand all of it (the step between grub et the first process launch by the kernel)
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
wizzard has joined #aarch64-laptops
<konradybcio>
every single chip will boot a little differently.. but between grub and the kernel, there's the efi stub
<konradybcio>
which is a simple efi "program" that starts up the kernel
<robclark>
from PoV of someone that isn't working on the fw itself, it is "just efi" (with some differences in boot flow depending on secure boot or not, but not so much x86 vs arm)
<robclark>
^^^ specifically about windows arm laptops, other random arm or $whatever_arch dev boards, android devices, etc can differ significantly
<konradybcio>
yeah efi onwards it's pretty similar, just assume there's no CSM (because there's nothing to be compatible with)