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
<anonymix007[m]>
bamse: it's UKI. But yeah, I'm sure. Same UKI boots from USB GRUB just fine, it's just systemd-boot from NVMe having this problem
<steev>
heh
enyalios has joined #aarch64-laptops
enyalios_ has quit [Ping timeout: 480 seconds]
echanude has quit [Ping timeout: 480 seconds]
hipboi has joined #aarch64-laptops
hipboi has quit []
hipboi has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
hipboi has quit [Quit: hipboi]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
tobhe_ has joined #aarch64-laptops
tobhe has quit [Ping timeout: 480 seconds]
echanude has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
bluerise has quit [Quit: brb]
checkfoc_us9 has quit []
checkfoc_us9 has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
alfredo has joined #aarch64-laptops
hipboi has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
eac5 has joined #aarch64-laptops
eac has quit [Read error: Connection reset by peer]
eac5 is now known as eac
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
iivanov has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
erebion[m] has joined #aarch64-laptops
<erebion[m]>
Should wifi on the X13s be this extremely and excrutiatingly slow?
<erebion[m]>
speedtest-cli says:
<erebion[m]>
Download: 0.58 Mbit/s
<erebion[m]>
Upload: 2.46 Mbit/s
<erebion[m]>
On another laptop on the same network, I get:
<erebion[m]>
Download: 81.09 Mbit/s
<erebion[m]>
Upload: 30.33 Mbit/s
<erebion[m]>
So I know it's not my ISP having issues
srinik has joined #aarch64-laptops
<erebion[m]>
I've reconnected and now I get:
<erebion[m]>
Download: 22.21 Mbit/s
<erebion[m]>
Upload: 40.57 Mbit/s
<erebion[m]>
Do others here get better results or is that just what we currently can get?
<craftyguy>
I've noticed that sometimes it slows waaaaay down
<steev>
Download: 221.78 Mbit/s
<steev>
Upload: 279.18 Mbit/s
<steev>
then 283.99Mbit/s down, 417.12Mbit/s up
<craftyguy>
I just measured 13.51 Mbit/s down on a 200 Mbit connection 🤷
<konradybcio>
for me it's been infinitely faster on windows on the same network lately
chrisl has joined #aarch64-laptops
iivanov has quit [Quit: Leaving...]
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<macc24>
<erebion[m]> "So I know it's not my ISP having..." <- you can always try iperf to rule out isp
nothorseface has quit [Ping timeout: 480 seconds]
anarsoul|2 has quit [Remote host closed the connection]
anarsoul has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
aradhya7 has joined #aarch64-laptops
hipboi has quit [Quit: hipboi]
nothorseface has joined #aarch64-laptops
hipboi has joined #aarch64-laptops
<deathmist>
got my HP OmniBook, any ideas about doing a backup of /dev/nvme0n1 by booting via network/USB? the Ubuntu X1E ISO has no working Wi-Fi or USB ootb so I can't even do ethernet. ig I'll have to already setup the firmware somehow?
<macc24>
disassemble the laptop and run the whole drive through xz?
<deathmist>
lol thanks but no thanks
<macc24>
after plugging in the drive into nvme -> usb adapter
chrisl has joined #aarch64-laptops
<macc24>
you can also try cadmium as it's got wifi working out of the box, tho idk if your laptop will work on it
<deathmist>
even just USB would be fine so I could at least store it on an external drive, I assume even that needs aDSP firmware up these days like other modern qcom phones I've started to see...
jhovold has joined #aarch64-laptops
<tobhe_>
deathmist: first time I'm hearing that usb doesn't work
<deathmist>
keep in mind I didn't install yet, I just booted via a USB-A 2.0 stick to the live env
chrisl has quit [Ping timeout: 480 seconds]
<deathmist>
just wanting to do a full disk backup before touching anything
<tobhe>
so usb-a does work
<deathmist>
for booting to the live env anyway yes, not sure if booting from USB-C and then plugging in something to USB-A will be different, maybe worth a shot too
<tobhe>
setting up firmware in the live environment is tricky because everything is ro. I could try building a pre-installed image you can put on a usb drive
<JensGlathe[m]>
@deathmist you don't need the firmwares for a backup. what you need is an usb to ethernet adapter
<JensGlathe[m]>
booting from type-a should work, although I haven't verified it.
hipboi has quit [Quit: hipboi]
<JensGlathe[m]>
so... sounds like some hub on usb-A for boot and ethernet
<deathmist>
I don't have any fancy USB-A hub or even ethernet adapter, and nothing on USB-C seems to be getting powered including a standalone USB-C ethernet adapter
<JensGlathe[m]>
okay try changing the orientation ofthe type-c ethenet adapter
<deathmist>
uh now the USB-C hub got power apparently? I just accidentally booted into windows but just shut it back down immediately and previously disabled the "USB Charging" in UEFI setup, let's see
<deathmist>
I just also enabled "USB Charging" back I mean
<deathmist>
got ethernet via the USB-C hub now, great
<JensGlathe[m]>
unswapped orientation for HP X14 is logo down btw
<jhovold>
erebion[m], craftyguy: I'm still maxing out my ISP at 476/533 Mbit/s with 6.12-rc7 on the x13s here
<jhovold>
and this is with the latest ath11k from linux-firmware (.41)
<jhovold>
latest ath11k fw*
<jhovold>
erebion[m]: if you have a mesh network, perhaps it's stuck connected to the wrong AP or something? haven't noticed that here either, but I think someone mentioned seeing that at some point
craftyguy has quit [Remote host closed the connection]
craftyguy has joined #aarch64-laptops
craftyguy has quit [Remote host closed the connection]
craftyguy has joined #aarch64-laptops
<macc24>
<tobhe> "setting up firmware in the..." <- tmpfs mount in /lib/firmware/qcom/$vendor/$product for device specific firmware + systemd service to automatically copy it from windows installation?
chrisl has joined #aarch64-laptops
<tobhe>
would be worth a try. more likely initramfs script than systemd service though. that's what we do on apple silicon
<tobhe>
except there we take the firmware from the esp, here we'd need to actually mount ntfs/bitlocker
<tobhe>
so far I haven't trusted dislocker enough to automate it
<jenneron[m]>
i was definitely against relying on windows installation, at least because i didn't have one, and it's silly to have windows just for linux to work
<jenneron[m]>
i also had an idea that we could extract some firmware from uefi capsule on devices without NHLOS partition, but i haven't researched it properly
<jenneron[m]>
(i mean 'in runtime' for all of that)
<travmurav[m]>
+1 for not relying on windows install, I think it's not toooooo hard to even download needed packages from windows update but worst case we could provide some extract_firmware.ps1 that would copy stuff into efs
<travmurav[m]>
then os can do something similar to msm-fw-loader and apply the override firmware dir
<travmurav[m]>
will need some small changes in pd-mapper and other userspace things to consider extra path but it shouldn't be hard
<jhovold>
anonymix007[m]: hmm, was gonna suggest someone trying uki and see if that helps at all with the t14s fw bugs, but apparently not then
<travmurav[m]>
(...) and also while some people can spare some 25GiB on their 4TB ssds, it will sadden me with my 64GiB emmc device
<jenneron[m]>
travmurav: have you checked uefi capsule?
<jenneron[m]>
there is no one that we need on this screenshot, but it might be there
<jenneron[m]>
haven't really looked into it
<travmurav[m]>
jenneron: I think uefi has some special "adsp lite" firmware and other fun stuff
<travmurav[m]>
i.e. it doesn't have sound stuff afaiu
<travmurav[m]>
not sure how far back this practice goes but afaiu this isthe case on x1e
<jenneron[m]>
does windows just store it as persistent file or does it load it from somewhere to the directory?
<travmurav[m]>
uefi loads _lite firmware on boot and windows kills and restarts with full firmware from the driver package
<travmurav[m]>
afaiu
<travmurav[m]>
and windows drivers just include the blobs via windows update
<travmurav[m]>
one interesting question is how many of those are actually oem signed or if the platofrm has per-remoteproc key slots that could be assigned to qcom only signing keys
<travmurav[m]>
but iirc at least samsung on older things had custom signed
<jenneron[m]>
travmurav[m]: so windows can't be booted from usb..?
<jenneron[m]>
or they solved the problem
<travmurav[m]>
jenneron: I'd assume windows has some hacks for usb reload but I won't be surprised
<travmurav[m]>
i.e. they could load those drivers in the early boot before c: is mounted
<travmurav[m]>
afaiu windows boot chain is quite involved
<jenneron[m]>
maybe we could do something similar with packaging firmware from windows update files?
<jenneron[m]>
and then maybe use lite versions in initramfs and reload them in runtime (except adsp when booted from USB), but that would be more complicated
<travmurav[m]>
well actual usb fix is including firmware in initramfs (or otherwise having a hook that would mount the storage, load stuff, survive usb reset)
<travmurav[m]>
s/actual/possible that is simple
<jenneron[m]>
yeah it's easier to just package it from windows update files and include in initramfs
<travmurav[m]>
not sure how pain it is to kill remoteproc and then load with different firmware
<jenneron[m]>
we do it in pmOS, but not directly from windows update
ellyq has quit [Remote host closed the connection]
<jenneron[m]>
(i mean loading adsp in initramfs, so usb booting works)
<travmurav[m]>
I guess
ellyq has joined #aarch64-laptops
<jenneron[m]>
i would be glad if this APKBUILD referenced windows update file instead of my gitlab repo
<travmurav[m]>
I feel like letting the user put it into esp may be a simple short term solution
<travmurav[m]>
I think it's possible to download stuff but the (only?) existing tool for that is quite fun
<jenneron[m]>
we should also somehow handle firmware versions
<jenneron[m]>
i think my samsung 8cx laptop refuses to load firmware i packaged in pmOS after updating windows
<travmurav[m]>
(note the funny branch)
<travmurav[m]>
no idea if ^^ even runs on linux xD
<travmurav[m]>
ugh if they do some rollback protection shit it will be so sad
<travmurav[m]>
as in, imagine the insanity of considering if your linux has newer version, it burns rollback and now windows doesn't boot
<jenneron[m]>
yeah we basically need either to handle multiple firmware versions in the same rootfs or provide a way to update UEFI (not sure how possible it is)
<travmurav[m]>
but oh well
<jenneron[m]>
i'm also glad that i don't work on this stuff anymore
<travmurav[m]>
I can really imagine xD
* travmurav[m]
is so glad his device is pre adsp-usb-mess
<jenneron[m]>
i actually still use lenovo flex/yoga 5g laptop
<jenneron[m]>
haven't found a replacement for it
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
einar has joined #aarch64-laptops
phire has quit [Quit: No Ping reply in 180 seconds.]
phire has joined #aarch64-laptops
<jhovold>
alexlanzano: regarding the in-kernel pd-mapper regressions, there's been at least four of them
<jhovold>
bamse fixed up a NULL-deref in one of the glink drivers early in the 6.12 dev cycle
<jhovold>
and he and chris lew from qcom fixed up the most severe one, a race in the glink code, in rc7
<jhovold>
that race could break things like battery and altmode notifications in almost every other boot
<jhovold>
there are some more details in my original report and the revert I posted before we had a fix:
<SpieringsAE>
its also nice that they offer a thingy that will give you 50% off of the next mainboard they will make
<SpieringsAE>
still really wish theyd put that spacemit 8 core chip in it
<macc24>
they sell an entire laptop with the spacemit 8
<SpieringsAE>
yeah, but it isnt the framework laptop
<SpieringsAE>
that is a pretty big value add to me
<SpieringsAE>
that one is also almost 600 euro damn
<macc24>
yeah :(
<SpieringsAE>
the whole idea of some other company being able to make a board for a framework laptops is just great to me
<SpieringsAE>
it gets close to what we do at my work and I really like that
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
jhovold has quit [Ping timeout: 480 seconds]
<deathmist>
JensGlathe[m]: got my own stuff running already, tho now I should package it all instead of copying random things from ubuntu rootfs to here lol, was a successful first test for sure though https://i.imgur.com/i9oHW9o.jpeg
<JensGlathe[m]>
Nice
<JensGlathe[m]>
Still fighting the Ubuntu packaging fight, getting better at it
SpieringsAE has quit [Quit: SpieringsAE]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
srinik has joined #aarch64-laptops
<tobhe>
the fight is eternal
<dlg>
tobhe: ha
DanaG has joined #aarch64-laptops
srinik has quit [Ping timeout: 480 seconds]
<DanaG>
I've tried a newer version of the ubuntu concept for Snapdragon on my Surface Pro 11 (Snapdragon X Plus with 5G), and it still tends to fail to initialize. The most I've gotten is an initramfs prompt with nonworking keyboard. I'm hoping Linux will eventually support the device; I'd be bummed if we get to full support of most other Snapdragon X machines but leave this one behind.
<DanaG>
I'm alsu curious why I can't get 4k 120hz output on Windows... is it a hardware limitation, a firmware issue, or a driver issue in Windows? There's no way to tell until we get some degree of display output support for the machine on Linux.
DanaG has quit [Remote host closed the connection]
erebion[m] has quit [Ping timeout: 480 seconds]
jenneron[m] has quit [Ping timeout: 480 seconds]
JensGlathe[m] has quit [Ping timeout: 480 seconds]
psydroid[m] has quit [Ping timeout: 480 seconds]
konradybcio has quit [Ping timeout: 480 seconds]
Jasper[m] has quit [Ping timeout: 480 seconds]
travmurav[m] has quit [Ping timeout: 480 seconds]
z3ntu has quit [Ping timeout: 480 seconds]
KieranBingham[m] has quit [Ping timeout: 480 seconds]
macc24 has quit [Ping timeout: 480 seconds]
DenysVitali[m] has quit [Ping timeout: 480 seconds]
anonymix007[m] has quit [Ping timeout: 480 seconds]