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 joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
hipboi has joined #aarch64-laptops
hipboi has quit []
chrisl has quit [Ping timeout: 480 seconds]
hipboi has joined #aarch64-laptops
hipboi has quit []
hipboi has joined #aarch64-laptops
hipboi has quit []
chrisl has joined #aarch64-laptops
tobhe_ has joined #aarch64-laptops
tobhe has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
jhugo has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
jhovold has joined #aarch64-laptops
<juergh>
noisycoil[m], " For some reason ubuntu doesn't use that command line parameter. Have no idea why" <- which commandline is that?
<JensGlathe[m]>
based on jhovold 's hotfixed branch
<JensGlathe[m]>
with Windows Devkit 2023 dt as proposed upstream - different firmware directory `qcom/sc8280xp/MICROSOFT/blackrock/`
hipboi has quit [Quit: hipboi]
<juergh>
steev, Hm. Why would I want that? With that I get no battery info.
<JensGlathe[m]>
my (quite reliable) hack is to put all firmware files into initramfs, including the .jsn files. And disable the adsp firmware file on the rootfs, so it can only be loaded from cache. This works with booting from type-c and battery monitoring.
<noisycoil[m]>
juergh @_oftc_juergh:matrix.org: yes, they don't have juergh: probably modprobe.blacklist=qcom_q6v5_pas on the command line and are including that module explicitly in the initramfs
<noisycoil[m]>
s/juergh//, s/juergh: probably//
chrisl has joined #aarch64-laptops
<noisycoil[m]>
In the installer specifically
<juergh>
noisycoil[m], yes, that was me :-) I'm trying to remember the reasoning but given that happened longer than 2 days ago there's a very slim chance of that.
<noisycoil[m]>
Oh, sure, was not sure who had written it, if you or tobhe
<noisycoil[m]>
I talked to him too, been working with him on Debian for Apple Silicon
chrisl has quit [Ping timeout: 480 seconds]
alfredo has joined #aarch64-laptops
hipboi has joined #aarch64-laptops
<juergh>
I still don't understand the problem with that module in the initrd. The size due to the required fw?
<juergh>
initrd size on Ubuntu is ... suboptimal anyways (to put it nicely in a public channel)
<JensGlathe[m]>
no its the moment of initialization, reloads adsp firmware (I assume) and drops VBUS on the type-c for a short time. SInce the rootfs is also on this type-c its bad. workaround is to try this early before mounting the rootfs (and then loading adsp firmware from there).
<juergh>
Well yes, that's why the module and the firmware are included in the initrd so it gets loaded before root is mounted from USB.
<noisycoil[m]>
<juergh> "I still don't understand the..." <- I have no idea honestly. Also, Tails' initramfs already is as small as it can be, so I'd exclude that.
<JensGlathe[m]>
additional hack I needed was to explicitly disable the fw file in the rootfs to avoid trying to load it. I had situations where it tried to load adsp again and then the rootfs might be unusable afterwards
<macc24>
i don't think i ever had issues with firmware when using in-kernel pd mapper and booting from nvme
<JensGlathe[m]>
Snapdragon Dev Kit is here, just arrived
<noisycoil[m]>
The issue is not booting from nvme, is booting from USB. This is specific to that
<JensGlathe[m]>
It's the VBUS from the type-c connectors that is controlled via ADSP (or something).
iivanov has joined #aarch64-laptops
<noisycoil[m]>
Jens Glathe: Yes, I saw that too. Not sure if Ubuntu removes that in the installer (it surely doesn't in the initramfs hook)
<noisycoil[m]>
JensGlathe[m]: In reference to this
hipboi has quit [Quit: hipboi]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<agl>
JensGlathe[m]: Oh that's good that you have the Dev Kit :-)
<maz>
tobhe_: I see you use dislocker to dump the original FW. I'm trying to do the same, but I get a cryptic error ("[CRITICAL] Unable to compute regions. Abort."). ring any bell?
<\[m]>
<steev> "\: nope, kali (since i'm a..." <- i was trying to make a systemd joke
<JosDehaes[m]>
wait if you got a dev kit, you get your money back AND get to keep it?
<maz>
yup, that's the deal.
<maz>
to be fair, they never took my money the first place.
<\[m]>
for once early adoption gets rewarded π
alfredo has joined #aarch64-laptops
<maz>
tobhe_: upgrading to a modern dislocker, I get something clearer: it needs a key yo read the BitLocker partition, and I don't have any FVEK/VMK file.
chrisl has joined #aarch64-laptops
agl has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
agl has joined #aarch64-laptops
srinik has joined #aarch64-laptops
<maz>
tobhe_: problem solved -- ask M$ for the key...
alfredo has quit [Quit: alfredo]
<travmurav[m]>
Oh is it that mess where you need to get the key from the online Microsoft account? XD
<maz>
yeah. not a big deal, but it took me some time to find where to look.
<travmurav[m]>
maz: also ugh
<travmurav[m]>
You say you didn't pay for it, mind telling who sponsored it then? :D
<maz>
Arrow. they initially charged my credit card, but as they didn't ship "the next day", the provision on the card lapsed after a week. and then they never tried to take the money again.
<travmurav[m]>
Ah
<travmurav[m]>
I see
<maz>
I only payed the import taxes to fedex.
<travmurav[m]>
For a split second I thought someone separately sponsored it for kvm purposes, which would've been pretty funny to me
<maz>
nah, I buy my own HW. it is pretty rare that HW companies send me machines without strings attached, and I value my freedom.
<travmurav[m]>
Yeah that makes total sense
<maz>
there is *one* notable exception to that rule, where the company just dumped a server box in the back of my car, and that was it.
<maz>
I'm still thankful for it.
spoonerandrew has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
hipboi has quit [Quit: hipboi]
hipboi has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
<JensGlathe[m]>
Made a complete image of the Dev Kit SSD before even switching it on. In that state its still unencrypted.
<JosDehaes[m]>
.krzk: I've updated my PR for the yoga 7x tplg files. I'm quite confident this is correct at least for speakers. I also have UCM config, but somewhere there is too much gain (haven't found yet where), all 4 speakers are working. https://github.com/linux-msm/audioreach-topology/pull/3
<\[m]>
maz which vendor?
<krzk>
JosDehaes[m]: great, thanks! I will take a look soon
chrisl has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<maz>
JensGlathe[m]: ah, nice one.
<maz>
\[m]: that's not for me to disclose.
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
Tims has joined #aarch64-laptops
<whiskey9_>
Does anyone see problems with the xps when mounting a usbc disk? Mine blue-screens(Yeah, the screen turns dark blue) and reboots.
agl has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
chrisl has joined #aarch64-laptops
agl has joined #aarch64-laptops
<sibis>
JensGlathe[m]: at this point I have pretty much have everything up on the devkit except for the edp -> hdmi converter (audio, sdhc and the three dp's work as expected)
agl has quit []
agl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
kalebris_ has joined #aarch64-laptops
iivanov has quit [Remote host closed the connection]
kalebris has quit [Ping timeout: 480 seconds]
kalebris_ is now known as kalebris
<JensGlathe[m]>
sibis: that's great news. Those edp -> hdmi xonverters got yanked though, my package has the type-c to HDMI converter
<JensGlathe[m]>
Do you have the dts somewhere in a repo? Or is it completely in a patchset already?
<JensGlathe[m]>
And does DP alt mode work? I thought I read you mentioning to take type-c-0
<JensGlathe[m]>
I have one display that can directly connect via type-c, probably the best choice
chrisl has joined #aarch64-laptops
srinik has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
spoonerandrew has quit [Quit: Connection closed for inactivity]
<robclark>
JosDehaes[m]: btw is there a description somewhere of what all I'd need to get audio working? I guess the tplg.bin file from the audioreach tree. And some UCM thing? And??
<robclark>
Looks like the tplg should end up in /lib/firmware .. but not seeing where the path comes from (not in dts?)
<robclark>
(maybe dumb questions.. I've managed to get thru life so far blissfully ignorant about audio)
<clee>
maybe was not included in the 6.11-next kernel in this image, though? who knows. I've tried booting with `efi=runtime` and `efi=novamap` and neither gets me working efivarfs