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
<steev>
if i download to /tmp, i get 7.5MB/s - still get that whine though
<logan2611>
hmm
<logan2611>
also yeah that's definitely some kind of coil whine
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
alfredo has quit [Ping timeout: 480 seconds]
alfredo has joined #aarch64-laptops
alfredo1 has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
alfredo1 is now known as alfredo
chrisl has joined #aarch64-laptops
enyalios_ has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
enyalios has quit [Ping timeout: 480 seconds]
<macc24>
considering that linux almost always runs under gunyah is there a 1:1 correspondence between physical cores and vcpus that linux sees?
<macc24>
so if i shut down big cores do they actually get shut down or is gunyah still using them?
<JensGlathe[m]>
There is so much we don't seem to know. Can't imagine that Windows is a client of Gunyah with all these difficulties.
<travmurav[m]>
I'd assume/hope gunyah would generally be transparent for "host" os
<travmurav[m]>
I guess that part could actually check in the sources
<travmurav[m]>
but also iirc quic claim that pinning certain specific cores helps performance so I guess core ids match?
<HdkR>
You usually want core ids to match with hypervisors, otherwise when you query the information registers things will wiggle around like VMs in MacOS
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
svarbanov__ has joined #aarch64-laptops
svarbanov__ has quit []
svarbanov_ has quit [Ping timeout: 480 seconds]
alfredo has quit [Remote host closed the connection]
SpieringsAE has joined #aarch64-laptops
<SpieringsAE>
Okay, I was expecting my asus to use the available sdhc2 for the sd card reader, but nope, after some digging on windows it seems to be a usb2 card reader
<SpieringsAE>
also it doesn't work for shit in windows
<SpieringsAE>
if only that dwc3-mp port would properly probe
<JensGlathe[m]>
there is anoter usb2 controller you can try. It is defined in the T14s dt. It is only usb2, uses one smb2360 eUSB2 repeater (?) and I had it enabled successfully on the HP, but ofc nothing on it since no sdhc slot there.
<JensGlathe[m]>
Counter q: my T14s doesn't like the RTC
<SpieringsAE>
the two I see there I already have
<SpieringsAE>
jeah, I've not tried the rtc yet
<SpieringsAE>
though it would be nice to have sooner rather than later
<SpieringsAE>
there is the extra smb2360 in the crd dts
<SpieringsAE>
I'll give that one a try
<JensGlathe[m]>
you also need usb_5(?) controller
kalebris_ has joined #aarch64-laptops
kalebris has quit [Ping timeout: 480 seconds]
kalebris_ is now known as kalebris
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
SpieringsAE has quit [Quit: SpieringsAE]
hightower4 has quit [Remote host closed the connection]
janrinze has quit [Ping timeout: 480 seconds]
janrinze has joined #aarch64-laptops
sri has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
sri has left #aarch64-laptops [Leaving]
alfredo has joined #aarch64-laptops
mynery[m] has joined #aarch64-laptops
<mynery[m]>
so, given that google announced plans to get rid of chromeos, does that mean we might lose access to widevine for arm?
<TheBITLINK[m]>
huh, so it's not only me, I thought I broke something when I tried to use the SD card reader and it didn't work under Windows
SpieringsAE has joined #aarch64-laptops
<SpieringsAE>
yeah I have no idea how that is a thing, does it just completely lock up for you too if you try to do anything with it?
<SpieringsAE>
and then only gets going again when you phyically remove the card
hightower2 has quit [Remote host closed the connection]
<TheBITLINK[m]>
nah it literally does not do anything, I do have an entry for it in device manager, but when I put any card in, nothing happens
<TheBITLINK[m]>
doesn't appear in the file explorer either
<SpieringsAE>
for me it appears, but if I click on it, whatever application I used to access it just completely locks up
<SpieringsAE>
its weird to me, this seems like a very common driver usb -> sd, how is it so messed up
<TheBITLINK[m]>
I tried installing the driver from the asus support webpage, but it's still broken lmao
chrisl has joined #aarch64-laptops
janrinze has quit [Ping timeout: 480 seconds]
<TheBITLINK[m]>
I wouldn't be surprised if they didn't test the SD card reader during QA
chrisl has quit [Ping timeout: 480 seconds]
alfredo1 has joined #aarch64-laptops
exeat has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
alfredo1 is now known as alfredo
janrinze has joined #aarch64-laptops
SpieringsAE has quit [Remote host closed the connection]
alfredo has quit [Quit: alfredo]
exeat has quit [Ping timeout: 480 seconds]
<ppd[m]>
Ok so I got QACT on my windows install. Turns out, the speaker protection "module(?)" is licensed, and I wouldn't be able to access it anyways, probably without paying.
chrisl has joined #aarch64-laptops
NecoArc has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<ppd[m]>
macc24:
<ppd[m]>
see above
<ppd[m]>
Thank you for trying though.
<steev>
x13s has a new bios update, bunch of cve fixes
<steev>
something about wifi 6e support
<spawacz>
steev: is it installable from Linux?
<JensGlathe[m]>
Operating on it already I guess
<JensGlathe[m]>
Had an update yesterday
<steev>
spawacz: not sure that you can do it with fwupd, but it's possible to make a usb drive with it, i think dgilmore wrote something up for it? could be misremembering who wrote it up
<steev>
i can't actually update at the moment, the battery is < 50% and it keeps canceling (in windows)
janrinze has quit [Remote host closed the connection]
<ppd[m]>
oh shizz I might have just figured out something funky about qact
<ppd[m]>
maybe I might be able to extract the protection params
<ppd[m]>
can't do so right now tho, need to do other things irl :)
<ppd[m]>
still, this is a huge step in the right direction
<ppd[m]>
a* direction. this probably will lead to something better...
<steev>
nice!
<steev>
don't forget to take notes :D
<spawacz>
i downloaded the manual setup, prepared usb stick basing on the .bat file but laptop reboots when i select "Y" to install it
<spawacz>
anyways, I'm not in a rush
<ppd[m]>
steev: will do. The only issue is that qact will still be required and that creates an interesting question regarding if such stuff can be used at all
<ppd[m]>
Stuff -> extracted data
<dunc4n>
<jhovold> "dunc4nn: just use my wip branch,..." <- thanks, managed to boot UKI from efi shell. direct boot didn't work
<JensGlathe[m]>
Newest X13s bios is N3HET91W (1.63 ) from 10/15/2024
hogliux has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
<dunc4n>
what do you guys think, will x1e get in working state faster than 8cxg3? the chip gets more attention at least, but I'm not familiar with ARM stuff at all so can't imagine how much work is needed to get everything in working state. was surprised to see people still have so much problems with x13s, it's been out for so long. don't want to sound too skeptical, I appreciate all the work you put into this
<dunc4n>
also; what are the downs/ups of running Linux from EL2 vs. ontop of gunyah? I assume the former requires qcom and oems to figure stuff out first before it's even theoretically possible
chrisl has quit [Ping timeout: 480 seconds]
<steev>
JensGlathe[m]: ah, i didn't check the date, it just listed today not the released date
<dunc4n>
HP allows to toggle EL2 boot? so it's more of an OEM issue then? (not available on T14s yet)
<JensGlathe[m]>
No. But you could try slbounce. This is how I run a Windows Dev Kit 2023 on EL2, where this is more feasible. Hven't tried yet on x1e, but others have.
hightower2 has joined #aarch64-laptops
<hogliux>
I for one am very happy with my slim 7x. I got the 32 GB variant from lenovo.com for 1500 Euros and upgraded it myself to a 2TB ssd. I love the keyboard and the screen is just gorgeous.
<hogliux>
Since the day I bought it in mid-August, I've been using it exclusively on Linux and using it as my daily driver.
<hogliux>
A few things don't work: I'm using the same kernel as kuruczgy (Thank you kuruczgy!!), so basically have the same things working as him:
<hogliux>
I also have hibernation working and regularly use the built-in speakers on very very low gain.
<hogliux>
I also sometimes boot into EL2 (via slbounce - thank you TravMurav!) to fire up the odd VM
<hogliux>
(but in EL2 many things don't work: bluetooth, battery-indicator,charging etc.).
<hogliux>
Whenever i have time I'd like to work on speaker protection. Here, I'm wondering why asahi linux use a daemon (sepakerprotectiond) for this. In my day job
<hogliux>
I've written a few ALSA linux userspace devices (pulseaudio/pipewire use linux userspace devices to bridge ALSA apps to pulseaudio/pipewire).
<hogliux>
I feel like that would be a better fit.
<hogliux>
Regarding better EL2 suppoer, I was wondering if it would be possible to somehow leverage gunyah to intercept how DSPs are booted in EL1. Does this even make sense?
<dgilmore>
spawacz: https://pagure.io/arm-image-installer/blob/main/f/update-x13s-bios is a script to make a usb disk for updating the bios. the efi program will only load the firmware update from USB. I am not aware of a cap file available that can update with fwupd. It would be nice if lenovo would push updates in lvfs
<dgilmore>
I need to update my bios
<kuruczgy[m]>
One downside of the slim 7x is that the lid switch still isn't working. Otherwise I also quite like it and have been using it as a daily driver for months.
<hogliux>
kuruczgy[m]: My laptop before the 7x was ten years old and the battery so bad that I had the habit of always hibernating it instead of sleeping. So I don't really miss sleeping not working correctly yet on the slim 7x.
hogliux has quit [Quit: Page closed]
<dgilmore>
my next install, planned on the t14s I need to add a swap partition to hibernate. I have not hibernated in years
<kuruczgy[m]>
I upgraded from an X230 ๐ (Though I was mostly using my desktop and my work laptop in the past few years. But even compared to the x86 work laptop this feels like a big upgrade. Sleep reliability and power consumption wasn't great on that one either. The yoga is faster, lighter, has significantly more battery life, and a gorgeous screen.)
hogliux has joined #aarch64-laptops
janrinze has joined #aarch64-laptops
<hogliux>
Yeah my previous laptop was a 7th gen Intel Dell XPS 13. So anything would feel fast for me.
hogliux has quit [Remote host closed the connection]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
clee_ has quit [Read error: Connection reset by peer]
clee has joined #aarch64-laptops
<spawacz>
dgilmore: I did something similar by hand, the latop reboots when pressing Y to confirm the update
<JensGlathe[m]>
look into the qcom-x1e tree. Also,you need to load the iris firmware blob which is on the device. Ihave only seen it in the log, asked tobhe about it, not tried anything yet.
nothorseface_ has quit []
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<macc24>
Jens Glathe: what's the name for the firmware blob?
<JensGlathe[m]>
qcav1e8380.mbn
<macc24>
thanks
Caterpillar has quit [Quit: Konversation terminated!]