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
checkfoc_us has quit []
checkfoc_us has joined #aarch64-laptops
kuruczgy[m] has quit [Ping timeout: 480 seconds]
Molyuu[m] has quit [Ping timeout: 480 seconds]
JensGlathe[m] has quit [Ping timeout: 480 seconds]
JosDehaes[m] has quit [Ping timeout: 480 seconds]
colemickens has quit [Ping timeout: 480 seconds]
FarchordSteveCossette[m] has quit [Ping timeout: 480 seconds]
Segfault[m] has quit [Ping timeout: 480 seconds]
thenightman97[m] has quit [Ping timeout: 480 seconds]
konradybcio has quit [Ping timeout: 480 seconds]
Jasper[m] has quit [Ping timeout: 480 seconds]
clover[m] has quit [Ping timeout: 480 seconds]
LoganLeland[m] has quit [Ping timeout: 480 seconds]
z3ntu has quit [Ping timeout: 480 seconds]
jenneron[m] has quit [Ping timeout: 480 seconds]
nirik has quit [Ping timeout: 480 seconds]
exeat has quit [Remote host closed the connection]
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
kuruczgy[m] has joined #aarch64-laptops
kuruczgy has quit [Read error: No route to host]
kuruczgy has joined #aarch64-laptops
dubiousness has quit [Read error: No route to host]
dubiousness has joined #aarch64-laptops
JensGlathe[m] has joined #aarch64-laptops
Mary has quit [Quit: Ping timeout (120 seconds)]
Mary has joined #aarch64-laptops
Molyuu[m] has joined #aarch64-laptops
xnox has quit [Remote host closed the connection]
xnox has joined #aarch64-laptops
hexa- has quit [Ping timeout: 480 seconds]
FarchordSteveCossette[m] has joined #aarch64-laptops
JosDehaes[m] has joined #aarch64-laptops
hexa- has joined #aarch64-laptops
maz_ has joined #aarch64-laptops
xnox1 has joined #aarch64-laptops
ektor52 has joined #aarch64-laptops
xnox has quit [reticulum.oftc.net liquid.oftc.net]
Molyuu[m] has quit [reticulum.oftc.net liquid.oftc.net]
JensGlathe[m] has quit [reticulum.oftc.net liquid.oftc.net]
cyrinux has quit [reticulum.oftc.net liquid.oftc.net]
Erisa has quit [reticulum.oftc.net liquid.oftc.net]
todi has quit [reticulum.oftc.net liquid.oftc.net]
tobhe has quit [reticulum.oftc.net liquid.oftc.net]
hightower2 has quit [reticulum.oftc.net liquid.oftc.net]
ektor5 has quit [reticulum.oftc.net liquid.oftc.net]
pbsds has quit [reticulum.oftc.net liquid.oftc.net]
flokli has quit [reticulum.oftc.net liquid.oftc.net]
krei-se has quit [reticulum.oftc.net liquid.oftc.net]
maz has quit [reticulum.oftc.net liquid.oftc.net]
f_ has quit [reticulum.oftc.net liquid.oftc.net]
Segfault[m] has joined #aarch64-laptops
colemickens has joined #aarch64-laptops
Molyuu[m] has joined #aarch64-laptops
f_ has joined #aarch64-laptops
JensGlathe[m] has joined #aarch64-laptops
hightower2 has joined #aarch64-laptops
flokli has joined #aarch64-laptops
tobhe has joined #aarch64-laptops
pbsds has joined #aarch64-laptops
krei-se has joined #aarch64-laptops
todi has joined #aarch64-laptops
Erisa has joined #aarch64-laptops
flokli has quit [Ping timeout: 480 seconds]
thenightman97[m] has joined #aarch64-laptops
eac has quit [Read error: No route to host]
flokli has joined #aarch64-laptops
konradybcio has joined #aarch64-laptops
z3ntu has joined #aarch64-laptops
Jasper[m] has joined #aarch64-laptops
clover[m] has joined #aarch64-laptops
LoganLeland[m] has joined #aarch64-laptops
cyrinux has joined #aarch64-laptops
jenneron[m] has joined #aarch64-laptops
nirik has joined #aarch64-laptops
LoganLeland[m] has quit [Ping timeout: 480 seconds]
nirik has quit [Ping timeout: 480 seconds]
thenightman97[m] has quit [Ping timeout: 480 seconds]
konradybcio has quit [Ping timeout: 480 seconds]
clover[m] has quit [Ping timeout: 480 seconds]
colemickens has quit [Ping timeout: 480 seconds]
Molyuu[m] has quit [Ping timeout: 480 seconds]
JensGlathe[m] has quit [Ping timeout: 480 seconds]
JensGlathe[m] has joined #aarch64-laptops
colemickens has joined #aarch64-laptops
Molyuu[m] has joined #aarch64-laptops
clover[m] has joined #aarch64-laptops
cyrinux has quit []
Erisa has quit [Quit: Ping timeout (120 seconds)]
Erisa has joined #aarch64-laptops
cyrinux has joined #aarch64-laptops
nirik has joined #aarch64-laptops
LoganLeland[m] has joined #aarch64-laptops
thenightman97[m] has joined #aarch64-laptops
konradybcio has joined #aarch64-laptops
kalebris_ has joined #aarch64-laptops
kalebris has quit [Ping timeout: 480 seconds]
kalebris_ is now known as kalebris
alfredo has joined #aarch64-laptops
flokli has quit [Ping timeout: 480 seconds]
flokli has joined #aarch64-laptops
ektor52 has quit []
ektor5 has joined #aarch64-laptops
<anonymix007[m]> I still have no idea which gpio to use, but there must be something else that prevents Bluetooth from working. Necessary modules (btqca and hci_uart) don't load automatically. But even with them, I don't see attempts to load firmware in dmesg. There are references to wcn7850 and BT enable pin in
<anonymix007[m]> `/sys/firmware/devicetree/` though, so the correct dtb (with Bluetooth changes) seems to be loaded.
<steev> rebooting my x13s into windows to see if i can jog my memory
<steev> let me looksie
<steev> i can't match it up now :( the dsdt for the x13s only has Pin list of 0x0085 but i don't remember what that relates to, and in the bt driver we have 2 different gpios for it, the bt-en and the sw-ctrl; maybe you need sw-ctrl too?
alfredo1 has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
alfredo1 is now known as alfredo
<anonymix007[m]> Well, I have no idea. It doesn't seem to be enabled for CRD. For me the pin in dsdt is 0x0074 which is the same 116 that is already set in dts: https://github.com/anonymix007/linux-t14s/blob/wip/x1e80100-6.11-rc4/arch/arm64/boot/dts/qcom/x1e78100-lenovo-thinkpad-t14s.dts#L643
<travmurav[m]> pretty sure those dsdt pin numbers have funny random offsets
<JensGlathe[m]> there's several gpio chips, maybe the offset is "just" the base of this chip when loaded in Linux?
<JensGlathe[m]> so like absolute addresses in dsdt assuming a table with the order of gpio chips?
<travmurav[m]> I don't think I was able to map the offsets to tiles on 7c when I quickly tried
<travmurav[m]> presumably there is some lookup table in the gpio driver
<anonymix007[m]> So the only option is to try all the gpios to find which one works? I'll leave the driver reverse-engineering for another day
<travmurav[m]> does crd use same gpio?
<steev> crd on sc8280xp doesn't seem to have bluetooth enabled in it, unfortunately?
<travmurav[m]> I meant x1e but seems like same story
<steev> it looks like abelvesa added the x1e crd bt
<travmurav[m]> ah so it's 116 there too, interesting
<steev> anonymix007[m]: can you post your dmesg up somewhere? dmesg | grep -v wlan0 should put everything except your wlan network infos
<steev> i think anon only took what was in crd and dropped it in place :)
<steev> can't compare to crd's dsdt because that's not submitted ;)
<steev> i wonder if the x1e crd is that sexy red color
<travmurav[m]> I think the one they shown in the demos was indeed a red laptop
<travmurav[m]> travmurav[m]: but i wonder if there the gpio is also wrong but firmware just sets it on by default
<travmurav[m]> alternatively there could be some extra power line for it
<travmurav[m]> but I'd guess it's in the wifi module so probably should share power...
<steev> yeah, it should
<steev> maybe we'll get lucky and ....bartosz (i don't recall his name) will do the powerseq work for it too
<anonymix007[m]> steev: https://katb.in/ulogaqepuvi
<anonymix007[m]> If I run `modprobe hci_uart` dmesg will also show... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/gxtOvAvHrQETzEOZeQELanVz>)
<steev> same for the btqca
<travmurav[m]> anonymix007: can you try adding aliases with those uarts?
<steev> i'm assuming
<travmurav[m]> in the dt
<travmurav[m]> I think some uart drivers don't want to probe without those
<travmurav[m]> (adding both serial0 and 1)
<steev> oh, yeah
<steev> assuming those are the same uart numberson the thinkpad
<anonymix007[m]> uart14 and uart21 are from dtsi, so should be the same, shouldn't they?
<travmurav[m]> but are aliases in dtsi? :)
<travmurav[m]> but well, serial0 is always the same debug serial, serial1 is whatever you have uart under
<travmurav[m]> ugh
<travmurav[m]> bluetooth
<travmurav[m]> but
<travmurav[m]> [ 0.101026] qcom_geni_serial a98000.serial: Invalid line -19
<travmurav[m]> this is because there is no alias
<travmurav[m]> and this is exactly your bluetooth uart
alfredo has quit [Quit: alfredo]
<anonymix007[m]> Thanks, it helped! Now the firmware loading failed, but it was an easy fix.
<steev> progress :)
alfredo has joined #aarch64-laptops
hexa- has quit [Quit: WeeChat 4.2.2]
exeat has joined #aarch64-laptops
hexa- has joined #aarch64-laptops
<Jasper[m]> @hdkr quick question, how was I supposed to update my rootfs again? Do I need to reinstall steam and the games I installed if I download a new rootfs?
jhovold has joined #aarch64-laptops
<HdkR> Jasper[m]: Just run FEXRootFSFetcher, steam installs things in to ~/.steam which is outside the rootfs
<Jasper[m]> Ah, cool
<Jasper[m]> I think I messed something up with it either way since it's complaining about the x64 ld.so.2 file missing
<Jasper[m]> But thst might have to do with me not running unbreak_chroot beforehand
<HdkR> Yea, the rootfs needs to be "broken" appropriately otherwise applications break
<Jasper[m]> HdkR: So the way to go is, fetch rootfs -> unbreak -> install steam -> exit -> fexbash
<Jasper[m]> If I understand correctly
<Jasper[m]> Hmm, no that gives me the missing ld-linux lib again
<Jasper[m]> I think I'm missing something
<HdkR> ah yea, if you installed steam in the rootfs yea, you'll need to reinstall after getting the new image. Once Steam runs it'll retain your config from $HOME
<Jasper[m]> Yes, but qemu is missing a library I think
<HdkR> FEXBash complaining about ld.so missing, or when you're unbreaking/chrooting?
<Jasper[m]> HdkR: If I use the regular host to execute FEXbash, it'll say `qemu-x86_64-static: Could not open '/lib64/ld-linux-x86-64.so.2` with nearly every command I try
<HdkR> Looks like you have qemu-user-static conflicting with FEX's binfmt_misc install
<Jasper[m]> If I execute unbreak chroot I get neatly put into a rootshell on the rootfs, executing commands works
<Jasper[m]> exiting from that shell kills it again
<Jasper[m]> HdkR: I git pull'd, cleaned the build folder, recompiled and reinstalled fex
<Jasper[m]> and also did sudo ninja binfmt_misc (since the 32-bit and 64-bit build target didn't exist anymore)
<HdkR> Check `/proc/sys/fs/binfmt_misc/` to see which binfmt_misc handlers are installed. If qemu is in there then it's a mess
<Jasper[m]> HdkR: It is, yes
<Jasper[m]> dang it
<Jasper[m]> Do I just uninstall qemu-static?
<HdkR> Probably
<Jasper[m]> HdkR: Yep, that fixed it
<HdkR> One of the benefits of package managers, they can more easily label conflicts like that
<Jasper[m]> Jasper[m]: Well, I specifically uninstalled the x86-64 version
<Jasper[m]> Worked well enough, I do think dnf pulled qemu-static with t, but left the other archs
<HdkR> You'd probably want to uninstall the i686/i386 or whatever one as well
<Jasper[m]> Hmm, fexinterpreter crashes and steam has no internet
<Jasper[m]> Maybe I should revert back to a release and not use main
<Jasper[m]> hahahha
<Jasper[m]> HdkR: Ah yeah, I'll check
<HdkR> The binfmt_misc installation changed just recently to support the systemd approach. I still need to wire up conflict resolution since I'm not sure what the qemu binaries for that are called
<Jasper[m]> Jasper[m]: Ah wait, that may be missing updates instead. mb
<HdkR> Also still not quite sure if restarting the systemd-binfmt service actually reinstalls the handlers...
<Jasper[m]> HdkR: Anything in particular you want me to check?
<HdkR> Would be hard to tell, I mostly just need to spend more time fussing with it
<HdkR> cmake option `-DUSE_LEGACY_BINFMTMISC=True` would go back to the old path
kinotable has joined #aarch64-laptops
<Jasper[m]> Also, Warframe seems to work quite well on x13s
<Jasper[m]> A bit slow, sure
<Jasper[m]> But everything off, 1200p gives you a solid 40fps in the beginning ship. Gonna check if I can get to somewhere busy
<HdkR> Whoa, fancy
jhovold has quit [Ping timeout: 480 seconds]
<HdkR> I haven't even tried Helldivers 2 on the X1E, since I'm assuming the lack of Sparse in the video driver wouldn't allow it to run
jhovold has joined #aarch64-laptops
kinotable has quit [Read error: Connection reset by peer]
kinotable has joined #aarch64-laptops
<Jasper[m]> <HdkR> "Whoa, fancy" <- Hung around 40 in a busier stage. Choppy but not unplayable
<Jasper[m]> FSR2.2 works aswell
<Jasper[m]> Surprisingly to me anyway
<HdkR> CPU limited or GPU limited? I presume CPU
<Jasper[m]> Will check
<Jasper[m]> HdkR: KDE System Monitor does not get over 400%
<Jasper[m]> So average is 400/8
<HdkR> Most cases it'll be a single CPU core maxing out
<Jasper[m]> Does spike to over 600% from time to time, but that may be a scheduler thing
<HdkR> Easiest to look at the threads of the process in htop and see if one is pegged at 100%
<HdkR> or nvtop and see the GPU at 100%
<Jasper[m]> HdkR: In this case it's 3 or 4 of the hovering inbetween 50 and 70%
<Jasper[m]> *them
<HdkR> Neat, seems like all of our optimizations are doing things
<Jasper[m]> HdkR: inbetween 65 and 75
<Jasper[m]> But that may be fsr compensating
<HdkR> Very fancy
Darsh has joined #aarch64-laptops
<Jasper[m]> Yep, it kinda just sits at 60 for both if I have scaling stuff turned on
kinotable has quit [Ping timeout: 480 seconds]
<HdkR> Definitely some weirdness if one side isn't capping out before hitting vsync, but eh, there's been weirder
<Jasper[m]> Person that asked me to test said that Warframe is notoriously badly optimized
<Jasper[m]> Because it's been revised a lot
<Jasper[m]> and only some parts of it
<Jasper[m]> My account is 11 years old, they still bring out new content
<Jasper[m]> Ultrakill now also runs as you said
<Jasper[m]> Not very well, but it does
alfredo has quit [Ping timeout: 480 seconds]
<Jasper[m]> Depends on a shitton of particles though
alfredo has joined #aarch64-laptops
alfredo has quit [Read error: Connection reset by peer]
<Jasper[m]> HdkR: btw, source2 will never work on sc8280xp right? I still wonder why it does on Windows
<TSIN[m]> Jens Glathe: Is v5 image out?
<JensGlathe[m]> sorry not yet, got distracted by some bsod (now apparently solved)
<JensGlathe[m]> will assemble it now, but since it's not a script, will take until tomorrow with testing - and unfortunately no testing on x1e hardware, thanks Arrow
ellyq has quit [Ping timeout: 480 seconds]
Darsh has quit [Ping timeout: 480 seconds]
<JensGlathe[m]> bsod news: it only took a few weeks, but I guess its isolated now. The presence of other clock drivers not compatible to sc8280xp is kind of enought to provoke the bsod behaviour. Additionally, it is not enough to load the compatible drivers as modules. DISPCC, GPUCC and VIDEOCC need to be builtin. With that it appears to not happen. I will test a little further, but looks like the hw detection for the qcom drivers should be a
<JensGlathe[m]> little more precise.
hexdump0815 has quit [Quit: WeeChat 3.8]
hexdump0815 has joined #aarch64-laptops
<steev> anonymix007[m]: so did you end up getting the bluetooth working?
<anonymix007[m]> steev: Yes. Needed to add aliases to dts and copy firmware.
<steev> nice!
<steev> you should submit it upstream
<anonymix007[m]> It depends on dtsi patches which aren't upstream yet. T14s dts patches weren't merged either
<steev> the dts patches don't need to be merged; you can simply say that your patchset depends on it. as for the dtsi patch, i'm not 100% sure how it works submitting someone else's work, but abelvesa is in here, so maybe you could ask him to submit it so you can submit the T14s?
<anonymix007[m]> Maybe. I actually tagged him here a while back with this a similar question.
<anonymix007[m]> Not sure if I actually want to send the patch (since it's basically a direct copy of the CRD patch) though.
ellyq has joined #aarch64-laptops
<steev> you can say that :) "i don't have access to the schematics so i just copied what was done in the CRD and it seems to work"
<anonymix007[m]> How easy would it be to run code on ADSP? I tried Bluetooth audio in Windows and it supports aptX Adaptive R3 using QDSP6 libraries like in Android.
<anonymix007[m]> Would be great to have this in Linux as well.
<steev> i could not answer that
todi_away has joined #aarch64-laptops