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
<zdykstra>
s/with/with abby
<steev>
suspend is fine?
<zdykstra>
I can close the lid and open it back up with out an issue, but the red LED never blinks
<zdykstra>
but I haven't looked that close to see how deep of a sleep state it hits
<steev>
does it actually suspend when you close it or no
<zdykstra>
it does not, my SSH connection to my IRC host was still active
<wiley[m]>
oh, does the WWAN on the x13s work?
<steev>
it should, check jhovold's wiki for the commands you need to run
<abby>
pretty sure mine does a very shallow suspend on 6.8.2 because the wlan disconnects
<steev>
and it does wake up?
<abby>
yes
<steev>
okay, thank you :)
<steev>
you're just using void's 6.8.2 which is vanilla upstream?
<abby>
vanilla upstream but I've switched the necessary few config options
<steev>
okay, so wip patches may be breaking things
sz3m3k[m] has quit [Quit: Client limit exceeded: 20000]
<zdykstra>
does the x13s support charge limiting like x86 thinkpads?
<zdykstra>
I seem to remember that it doesn't, but my memory is fuzzy
<steev>
i don't think we have anything in place for it, not sure about on windows
<jglathe_>
steev: I'm using 6.8.2.
<jglathe_>
Suspend seems to work well
<dgilmore_>
anyone updated their bios to 1.60 yet on the x13s?
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
<jglathe_>
WLAN and BT disconnect on suspend here
jglathe_ has quit [Ping timeout: 480 seconds]
jglathe_sdbox2 has joined #aarch64-laptops
<zdykstra>
ahh, I changed KDE to suspend on display close - and it does seem to do so now, since wifi disconnects
<zdykstra>
I'm going to suspend over night and see how much battery drain there is
<jglathe_sdbox2>
I had an odd situation here, box (Volterra) stuck in link training, no network, no reaction on sudo systemctl reboot
<jglathe_sdbox2>
it was only visible in dmesg
<jglathe_sdbox2>
... and not preserved. I had a working display through it, though.
<jglathe_sdbox2>
on 6.8.2-EL2
<steev>
dgilmore_: what's new with it?
jglathe_ has joined #aarch64-laptops
<dgilmore_>
Some CVE fixes
<dgilmore_>
steev: I didn't look to see what the CVE's actually are
<steev>
in b4 the cves deal with travmurav[m]'s work
* travmurav[m]
was confused for a moment "what cve" since he doesn't consider his work cve-able
<travmurav[m]>
just that I didn't even connect the dots at first :D
<steev>
they're both secureboot bypasses
<dgilmore_>
I just installed it
jglathe_ has quit [Remote host closed the connection]
<dgilmore_>
https://paste.centos.org/view/86b729e4 is a bit ugly but will make an iso image to update the firmware. hit f12 on boot after putting it on a usb stick
<lollaritits[m]>
just build it like any AUR package
<lollaritits[m]>
sadly arm64 packages (without x86_64) arent allowed on AUR
<lollaritits[m]>
and the maintainer doesnt want to merge multi arch
<robclark>
travmurav[m]: btw, has anyone managed to get slbounce working on x13s yet?
<travmurav[m]>
robclark: yes, multiple people afaik
<robclark>
hmm, ok.. It didn't look like there were any changes in slbounce repo since I last tried.. but maybe the fixes where on kernel side?
<travmurav[m]>
robclark: initially there was a small change, otherwise yes, need 6.8+ and there are dt overlays to fixup pcie in the repo
<travmurav[m]>
as in, to have both iommus
<robclark>
I think I was on jhovold v6.8-rc<something>.. and I did have the dt overlay.. but I guess I should update kernel and try again this weekend
<travmurav[m]>
do you remember what issue you had?
<robclark>
I assume it was pcie/nvme
<travmurav[m]>
yeah, that needed extra recent figuring out
<travmurav[m]>
wrt iommus that is
<travmurav[m]>
but I think it should "just work" now with 6.8+ and smmuv3 overlays
<robclark>
I didn't spend too long on it because it seemd to still be WIP at the time.. but I hadn't followed where all the fixes went (ie. what was in kernel vs dt overlay / slbounce)
<robclark>
ok
<travmurav[m]>
I don't think we've made any fixes that explicitly target EL2 in the kernel actually, only the reserved node for smmuv3 maybe
<travmurav[m]>
but more like figuring out how to set up pcie iommu was the fun part
<travmurav[m]>
afaik jglathe__ runs a volterra in EL2 constantly nowdays so I assume it works pretty well on sc8280xp
<robclark>
yeah, the EL2 part itself was ok.. I think it was just the broken pcie
<travmurav[m]>
(^^ running from nvme that is)
svarbanov has quit [Ping timeout: 480 seconds]
janrinze has quit [Quit: Leaving.]
adamcstephens has quit [Remote host closed the connection]
adamcstephens has joined #aarch64-laptops
janrinze has joined #aarch64-laptops
jglathe_volterra has joined #aarch64-laptops
jhovold has quit [Quit: WeeChat 4.2.1]
<jglathe_volterra>
robclark, travmurav[m] yep, running 24/7 except for other tests. I have a dedicated EL2 branch, but the only thing different to the normal one is a dt with enabled arm-smmuv3, and no zap shader. So, as of 6.8, no dedicated code in the kernel itself. And the box boots from internal nvme now.
<travmurav[m]>
steev: partially, I should probably split it into two: one that applies node as-is with status reserved and another one that applies status=okay and pcie mappings
<travmurav[m]>
... split into two so those who have the patch with status=reserved applied can drop one of the overlays and get it to work
<travmurav[m]>
I'm still not completely sure if it's safe to define iommu-map that references a disabled iommu but I guess it works for jglathe_volterra ...
<jglathe_volterra>
No error messages <shrug>
<jglathe_volterra>
and MSI interrupts
<_[m]123>
nice steam is working and dota2 starts butit crashes when I start a demo mode game
svarbanov has joined #aarch64-laptops
<steveej[m]>
my wifi issues on the x13s aren't mentioned on jhovold's wiki known issues page. where else can i see whether someone has already reported? it's quite gnarly and it'd be great to at least get the devs aware
svarbanov has quit [Ping timeout: 480 seconds]
<_[m]123>
I had the weirdest bug today though, when I opened the laptop, the main screen was frozen but still showing a still image and my external screen was responsive
<steev>
steveej[m]: i'd check the kernel bugzilla
altacus has joined #aarch64-laptops
<altacus>
Has anyone gotten proton to run on the x13s? I was able to get steam to work, but not proton. I'm assuming it has to do with having to set up wine properly, but not sure. Error logs are not very helpful.
<HdkR>
Yes
<HdkR>
Do you have namespacing enabled in your kernel?
<altacus>
HdkR: not sure, I will check. Is there a resource with the requirements specified?
<HdkR>
Not that I'm aware of
<HdkR>
What is your x86 emulator of choice?
<altacus>
Box86/Box64
<HdkR>
Ah. I've never used it, I don't know what their proton support is like
<altacus>
I'm running Debian Testing, Unstable has broken packages
<altacus>
do you know the namespacing config name? Is it CONFIG_NAMESPACES?
<HdkR>
I think that's the main one and then there are a few sub-config options
<altacus>
Well, box is working i.e. steam is running.
<altacus>
I think proton relies on Wine so I'm thinking the issue is there.
<HdkR>
Proton is a whole another layer of tomfoolery though. It uses SteamLinuxRuntime which does some chroot shenanigans and wine on top of that as well
<HdkR>
I guess latest version of steam puts steamwebhelper inside the SteamLinuxRuntime, so if the GUI is running in steam that implies it is working
<HdkR>
So Proton+Box specific quirk
<altacus>
I could have sworn I got it working at one point, I think with Ubuntu. Unfortunately, I only get like 1-2 hours a week to play around with my x13s
<altacus>
HdkR: agreed
jhovold has quit [Ping timeout: 480 seconds]
<HdkR>
Sadly I've never used Box so I don't know its behaviour. Only used FEX-Emu
<steev>
the unstable thing is because of the t64 transition... it SHOULD be over soon, hopefully
<HdkR>
That affects arm64?
<HdkR>
Or are all of their packages being rebuilt?
<steev>
all of them are being rebuilt, apparently it's a temporary thing too, until upstreams accept the patches, but it's kinda annoying because they're changing the sonames
<HdkR>
huh, interesting
<steev>
annoying because SOME OF THE PACKAGES HAVE SLIPPED THROUGH INTO TESTING
<steev>
main one being libaio, which affected both the debian installer, as well as some binary packages we have from oracle, in kali
<HdkR>
Spicy
<altacus>
HdkR: Are you able to run Proton with FEX-Emu?
<HdkR>
altacus: Yes
<altacus>
HdkR: Cool. Was anything else need in order to run steam? I.e. wine, etc?
<HdkR>
Nah, steam doesn't need wine at all. Proton ships its own copy