robclark 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
<enyalios>
steev: so ive still been messing around with this x13s a lot to try to get it to work
<enyalios>
i installed ubuntu in another partition alongside the gentoo install
<enyalios>
and the sound works fine there
<enyalios>
so its not a hardware issue, and i didnt blow out my speaker
<enyalios>
s
<enyalios>
i just really dont understand all the parts required to get also working
<enyalios>
s/also/alsa/
<enyalios>
ubuntu is using pipewire on top of alsa, so i tried installing that in gentoo but that didnt help because the underlying alsa stuff wasnt working
<enyalios>
i also tried installing 6.6-rc2 kernel with the same .config that laptop_defconfig generates on yours
<enyalios>
but the system wouldnt boot
<enyalios>
it just hangs after grub, i forget the exact error message, ill have to try it again to see
<steev>
good that sound works fine on ubuntu and means the speakers aren't blown
<enyalios>
yeah, that was reassuring
<enyalios>
the message is:
<enyalios>
EFI stub: Booting Linux Kernel... / EFI Stub: Using DTB from configuration table / EFI Stub: Exiting boot services...
<enyalios>
and it just hangs there forever
<enyalios>
that shows up right after grub does its thing
<steev>
that makes it sound like maybe the wrong dtb being used but idk
<enyalios>
huh, im using the one that comes with that kernel
<enyalios>
i seem to recall getting that same message on a lot of different distros live usb drives too
<enyalios>
when trying to find something that could boot this so i could install a distro
<steev>
EFI Stub: Using DTB from configuration table says different?
<enyalios>
i have "devicetree /dtbs/6.6.0-rc2/qcom/sc8280xp-lenovo-thinkpad-x13s.dtb" in my grub config for that kernel
<enyalios>
and that file exists on /boot
<steev>
maybe add verbose
<steev>
unless you're using **vanilla** 6.6.0-rc2 and not from my tree
<steev>
in which case, you'd be missing some patches still
<enyalios>
oh yeah thats vanilla
<enyalios>
i thought you said everything necessary to boot was in 6.4 or so?
<enyalios>
err, 6.5 i believe you said
<steev>
6.5, but 6.6 had some regressions afaik
<steev>
but i thought the 6.6 regression was just breaking touchpad
<steev>
you could compare with yours, some things won't be strictly necessary (lru_gen)
<enyalios>
thanks
<steev>
fwiw, i've not touched **anything** related to alsa to get it set up with 6.5+, just installing the alsa-ucm-conf and applying the 335 pull request. pipewire runs in my user's session
<enyalios>
its like 17 lines different, but im not sure if thats the issue or missing patches that vanilla doesnt have that are causing it
<steev>
disabled pointer authentication and you need that if you're not using mine or johan's kernels
<steev>
disables*
<steev>
you need that for the 6.6.0-rc2, not for the 6.5 based on my tree
<enyalios>
oh cool, ill add that in and give it a whirl
<steev>
unless you're also doing vanilla 6.5, in which case, you're missing patches
<steev>
that would be why audio doesn't work (and they don't look like they're gonna be in 6.6 either, unless they make it in further rc)
<steev>
oh wait maybe they are, i'm looking over what i have here in 6.6
<steev>
yeah, they're still out of tree it seems, although i'm not sure how much they are strictly needed
<enyalios>
so the one that boots gentoo is 6.5.3+ from your tree, branch lenovo-x13s-linux-6.5.y
<enyalios>
are you saying audio wont work is that one
<enyalios>
or in one of the vanilla ones
<steev>
it will work with mine, i am currently using it, vanilla won't
<enyalios>
because i cant get a vanilla one to even boot
<steev>
right, because of the pointer authentication
<enyalios>
ah, then i wont even bother trying to get a vanilla kernel to work
<enyalios>
ill stick with yours and try to figure out why alsa is unhappy
<enyalios>
any alsa experts around?
<enyalios>
wow, i just ran `efibootmgr -v` and it just suddenly reset my computer
<steev>
do you have the qseecom stuff and efivars enabled?
<steev>
i can't reproduce that here
<enyalios>
normally efibootmgr works just fine
<enyalios>
not sure why it crashed this time
hightower3 has joined #aarch64-laptops
agl7 has quit [Remote host closed the connection]
agl7 has joined #aarch64-laptops
hightower2 has quit [Ping timeout: 480 seconds]
derzahl has joined #aarch64-laptops
pbsds has quit [Ping timeout: 480 seconds]
pbsds has joined #aarch64-laptops
agl7 has quit [Remote host closed the connection]
agl7 has joined #aarch64-laptops
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
alfredo has joined #aarch64-laptops
derzahl has quit [Ping timeout: 480 seconds]
alfredo has quit [Quit: alfredo]
derzahl has joined #aarch64-laptops
<ema>
ukleinek: yup, copying the dtb in a efi shell would work too. But given that for the BIOS update you must be in Windows anyways, I thought I'd document how to copy the DTB from Windows itself
<ema>
and GRUB has to be forced to the EFI removable media path because there's a problem mounting efivarfs
<ema>
ukleinek: .dts is the source file, .dtb the compiled version
<steev>
ema: qseecom has been accepted in next, so you could take the patches from my 6.5 and submit them to debian
<steev>
that's required for uefivars
<ema>
steev: nice, is your work going to be into 6.6?
<steev>
not my work, qzed and no, 6.7
<steev>
i think
<ema>
ack, thanks!
<steev>
i'm not sure if that's enough but efivar reading definitely requires it
derzahl has quit [Remote host closed the connection]
alfredo has joined #aarch64-laptops
<ukleinek>
ema: The wiki reads: sc8280-lenovo-thinkpad-x13s.dtb must be copied, but given the .dts is called sc8280xp-lenovo-thinkpad-x13s.dts I wonder if there is a "xp" missing in the dtb cp cmdline
<jhovold>
push: ok, thanks for testing, which kernel are you using?
<jhovold>
enyalios: mainline 6.5 works just fine, including audio modulo some pops and clicks
<jhovold>
you only need to run with the patches from my wip branches (or steev's branches which are based on those) if you want efivars, video acceleration or fingerprint reader
<jhovold>
the rest just comes down to configuration (defconfig, kernel parameters) and user space (e.g. alsa-ucm files, fw symlinks)
ungeskriptet75 has joined #aarch64-laptops
ungeskriptet73 has joined #aarch64-laptops
ungeskriptet71 has joined #aarch64-laptops
ungeskriptet76 has joined #aarch64-laptops
ungeskriptet70 has joined #aarch64-laptops
ungeskriptet736 has joined #aarch64-laptops
ungeskriptet77 has joined #aarch64-laptops
ungeskriptet78 has joined #aarch64-laptops
ungeskriptet768 has joined #aarch64-laptops
ungeskriptet79 has joined #aarch64-laptops
ungeskriptet7 has quit [Ping timeout: 480 seconds]
ungeskriptet799 has joined #aarch64-laptops
ungeskriptet75 has quit [Ping timeout: 480 seconds]
ungeskriptet73 has quit [Ping timeout: 480 seconds]
ungeskriptet71 has quit [Ping timeout: 480 seconds]
ungeskriptet76 has quit [Ping timeout: 480 seconds]
ungeskriptet70 has quit [Ping timeout: 480 seconds]
ungeskriptet796 has joined #aarch64-laptops
ungeskriptet736 has quit [Ping timeout: 480 seconds]
ungeskriptet77 has quit [Ping timeout: 480 seconds]
ungeskriptet78 has quit [Ping timeout: 480 seconds]
ungeskriptet768 has quit [Ping timeout: 480 seconds]
ungeskriptet797 has joined #aarch64-laptops
ungeskriptet798 has joined #aarch64-laptops
ungeskriptet79 has quit [Ping timeout: 480 seconds]
ungeskriptet7986 has joined #aarch64-laptops
ungeskriptet7983 has joined #aarch64-laptops
ungeskriptet799 has quit [Ping timeout: 480 seconds]
ungeskriptet7984 has joined #aarch64-laptops
ungeskriptet79860 has joined #aarch64-laptops
ungeskriptet7989 has joined #aarch64-laptops
ungeskriptet798606 has joined #aarch64-laptops
ungeskriptet79840 has joined #aarch64-laptops
ungeskriptet796 has quit [Ping timeout: 480 seconds]
ungeskriptet7988 has joined #aarch64-laptops
ungeskriptet7985 has joined #aarch64-laptops
ungeskriptet797 has quit [Ping timeout: 480 seconds]
ungeskriptet7981 has joined #aarch64-laptops
ungeskriptet798 has quit [Ping timeout: 480 seconds]
ungeskriptet7986 has quit [Ping timeout: 480 seconds]
ungeskriptet7983 has quit [Ping timeout: 480 seconds]
ungeskriptet7984 has quit [Ping timeout: 480 seconds]
ungeskriptet79860 has quit [Ping timeout: 480 seconds]
ungeskriptet7989 has quit [Ping timeout: 480 seconds]
ungeskriptet798606 has quit [Ping timeout: 480 seconds]
ungeskriptet79840 has quit [Ping timeout: 480 seconds]
ungeskriptet7988 has quit [Ping timeout: 480 seconds]
ungeskriptet7985 has quit [Ping timeout: 480 seconds]
ungeskriptet7981 has quit [Ping timeout: 480 seconds]
hightower3 has quit [Ping timeout: 480 seconds]
alfredo has quit [Quit: alfredo]
hightower2 has joined #aarch64-laptops
todi1 has joined #aarch64-laptops
todi has quit [Read error: Connection reset by peer]
<ema>
ukleinek: ah yes! Thanks for spotting the mistake, fixed
todi1 has quit [Read error: Connection reset by peer]
todi has joined #aarch64-laptops
<push>
jhovold: 6.5.0-1002-laptop the kernel from ubuntu concept, it still resets, but now the uptime is a few hours instead of a few minutes
ungeskriptet has joined #aarch64-laptops
<jhovold>
push: ok, guess you need to bring this up with ubuntu (e.g. juergh)
<jhovold>
haven't seen anything similar with my wip branches or mainline
<push>
does anyone have a dtb for the galaxy book go with the 8cx chip? is there any expectation that it would be the same as the galaxy book with the 7c?
<push>
I want to plug that into one of these x13s build and see what happens
matalama has joined #aarch64-laptops
matalama_ has joined #aarch64-laptops
alfredo1 has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
alfredo1 is now known as alfredo
alfredo has quit [Ping timeout: 480 seconds]
<enyalios>
jhovold: ah, thanks for the clarification
todi has quit []
alfredo has joined #aarch64-laptops
matalama_ has quit [Quit: Connection closed for inactivity]
<steev>
ema: why does the installer need the wifi firmware to be separate though? it should be in the firmware-atheros package already, and i'd have thought the debian-installer would do that during network detection?
<steev>
or is that package in non-free-firmware?
<ukleinek>
nowadays that's not a stopper for it to be included in the installer