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
tobhe_ has joined #aarch64-laptops
hexdump0815 has joined #aarch64-laptops
hexdump02 has quit [Ping timeout: 480 seconds]
tobhe has quit [Ping timeout: 480 seconds]
zetam has joined #aarch64-laptops
zetam has quit []
zetam has joined #aarch64-laptops
zetam has quit []
mani_s has joined #aarch64-laptops
hexdump02 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
enyalios has joined #aarch64-laptops
enyalios_ has quit [Ping timeout: 480 seconds]
mani_s has quit [Quit: Connection closed for inactivity]
ungeskriptet has joined #aarch64-laptops
SpieringsAE has joined #aarch64-laptops
ravikant_ has joined #aarch64-laptops
kalebris has quit [Ping timeout: 480 seconds]
kalebris has joined #aarch64-laptops
vanner- has joined #aarch64-laptops
vanner has quit [Ping timeout: 480 seconds]
ravikant_ has quit [Remote host closed the connection]
ravikant_ has joined #aarch64-laptops
pbrobinson has quit [Ping timeout: 480 seconds]
pbrobinson has joined #aarch64-laptops
mani_s has joined #aarch64-laptops
ravikant_ has quit [Ping timeout: 480 seconds]
ravikant_ has joined #aarch64-laptops
<HdkR> `The chipmaking giant is reportedly working with MediaTek to develop an accelerated processing unit (APU)`
<HdkR> They're a bit slow on the uptake aren't they? They probably don't even know N1X/Spark exists.
pbrobinson has quit [Ping timeout: 480 seconds]
<HdkR> Also "Make its debut" is funny wording when Tegra was already in Windows laptops in the past :P
<\[m]> yeah the verge isn't necessarily the best source - I agree
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #aarch64-laptops
<\[m]> wait you're saying that the cpu in that alienware will be the n1x?
<HdkR> as far as I can tell, Alienware/Dell is pure speculation.
<HdkR> Not yet anyway :D
<HdkR> Pretty cute even if both Spark and Thor are late to market.
machoskraito has joined #aarch64-laptops
<Jasper[m]> <HdkR> "Also "Make its debut" is funny..." <- Mine's withering away in a closet
<HdkR> I have a pile of Shield Portables doing the same.
<Jasper[m]> arm32-laptops never got the launch down :^)
<HdkR> The Exynos 5250 Chromebook did pretty well :D
<HdkR> Bit of a nightmare as a power user on it, but mostly worked.
<Jasper[m]> HdkR: Ohhh, well slightly off topic, but if you feel like trying to get it working upstream (possibly with U-Boot), I'd suggest joining #postmarketOS-on-tegra:matrix.org. I also have a telegram link if preferred (it's not bridged to IRC iirc)
<HdkR> eeeeeeeh
<Jasper[m]> GPU is still painful obviously, worse than Kepler+
<HdkR> It's mostly just a nostalgia trophy for me
<Jasper[m]> Alright, no worries! The collection of pre-K1 Tegra devices (that are somewhat sane to unlock/get kernel sources for) is nearing completion
<Jasper[m]> And I think that specific one is missing
<machoskraito> hi all
<Jasper[m]> Hi!
<HdkR> It's a trap!
AlekseiNosachev[m] has joined #aarch64-laptops
<AlekseiNosachev[m]> Hello there!
<AlekseiNosachev[m]> Diving in SP11 ACPI parsing 😀
machoskraito has quit [autokilled: This host violated network policy and has been banned. Mail support@oftc.net if you think this is in error. (2025-07-03 11:41:28)]
machoskraito has joined #aarch64-laptops
<machoskraito> hi all back ... .
machoskraito has quit [autokilled: This host violated network policy and has been banned. Mail support@oftc.net if you think this is in error. (2025-07-03 11:54:07)]
agl has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
agl has joined #aarch64-laptops
agl has quit []
agl has joined #aarch64-laptops
todi has joined #aarch64-laptops
todi1 has quit [Ping timeout: 480 seconds]
pbrobinson has joined #aarch64-laptops
jglathe_angrybox has quit [Ping timeout: 480 seconds]
jglathe_angrybox has joined #aarch64-laptops
pbrobinson has quit [Ping timeout: 480 seconds]
SpieringsAE has quit [Quit: SpieringsAE]
<jdb[m]> Aleksei Nosachev: Hello, there is already a working SP11 devicetree
<AlekseiNosachev[m]> <jdb[m]> "Aleksei Nosachev: Hello, there..." <- Wow, any hints where I can get it? For now only seeing romulus one
<tobhe[m]> can't vouch for it though
<jdb[m]> tobhe: you were faster than me!
<jdb[m]> And I'm running it, I can confirm it's working fine
<jdb[m]> I have issues with suspend sometimes and random freeze also
<jdb[m]> I'd like to see it being upstream, I'll try to see if I can progress on it during the summer time
ravikant_ has quit []
todi1 has joined #aarch64-laptops
todi has quit [Ping timeout: 480 seconds]
todi has joined #aarch64-laptops
todi1 has quit [Ping timeout: 480 seconds]
<steev> jhovold: now that the venus firmware is in, can the driver stuff be submitted?
agl has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
agl has joined #aarch64-laptops
<Lenni> Hi, a few days ago I already asked here, but after looking further and trying different things nothing worked for me. The WWAN modem is shown as "unavailable" in programs like nmcli and nmtui. I followed the steps in the Debian wiki (and enabled the FCC unlock), but that didn't help: https://wiki.debian.org/InstallingDebianOn/Thinkpad/X13s#FCC_unlock_procedure
mani_s has quit [Quit: Connection closed for inactivity]
<steev> Lenni: can you show your /etc/ModemManager/fcc-unlock.d/ directory?
<steev> also lspci
<Lenni> The contents of the directory: 03f0:4e1d 105b 105b:e0ab 105b:e0c3 1199 1199:907914c3 14c3:4d75 1eac:1001 1eac:1004 1eac:1007 2c7c2c7c:030a 2c7c:0313 2c7c:0314 2c7c:0801 413c:81a3 413c:81a8
<Lenni> The modem in lspci, it is in the fcc-unlock.d directory: 0004:01:00.0 Wireless controller [0d40]: Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] [105b:e0c3]
<bamse> Lenni: if you look at the the journal for ModemManager (journalctl -f -u ModemManager) it will repeatedly perform the first 2-3 steps of the setup and then report restarting if the problem is caused by fcc locking
<bamse> Lenni: iirc i had to set it up once in windows, and let it perform some firmware upgrade, before i could get it working in linux...
<valpackett> robclark: lumag: yes, the enable_color_mgmt gamma is what all compositors support, it's the only way to get all the existing night lights everywhere to work
<valpackett> cdsp update: https://github.com/quic/fastrpc/issues/188#issuecomment-3031400546 (it works with signed binaries for me now! some kind of patch is coming? i also asked about qurt headers)
<Lenni> bamse: I alrady got rid of Windows a few weeks ago because my SSD was too small to keep it. Do you know if I can do it from Windows PE? :/
<bamse> Lenni: i don't think you should need windows to get it going...i think when i did it i couldn't get it working, so i booted windows to check that everything was happy, then booted back to linux and got it to work...but i might have figured out and resolved the fcc unlock in that latter phase
<Lenni> bamse: The Debian wiki mentions the firmware update on Windows, so that might indeed be necessary. I'm planning on buying a larger SSD and putting at least a small Windows partition on there, mainly for things like that.
<bamse> Lenni: i don't know how often they ship updates...the x13s isn't new anymore, so might be a onetime thing at this point
<Lenni> bamse: I'd expect one update to the current (or some relatively recent) version to be enough, but I still need Windows for that
<bamse> Lenni: but i'd suggest checking "journalctl -fu ModemManager" if it continuously is looping in the setup phase
<bamse> Lenni: yeah, people have successfully been fetching the lenovo update and applying it from linux, but the modem update/setup was some windows thing...
<Lenni> The Lenovo Support page doesn't seem to have a standalone firmware update EXE I could try to run from PE, great...
<Lenni> bamse: This is the output of `journalctl -fu ModemManager`: https://paste.debian.net/1384221/
<Lenni> Oops, accidentally deleted it, here it is again: https://paste.debian.net/1384222/
<bamse> "[modem2] modem couldn't be initialized: eSIM without profiles detected"
<bamse> do you intend to use it with esim or physical sim?
<Lenni> A phyical SIM which already is inserted
<bamse> does it still show up in mmcli --list-modems ?
<Lenni> That command's output: /org/freedesktop/ModemManager1/Modem/2 [foxconn] Qualcomm Snapdragon X55 5G
<bamse> so "mmcli -m 2" gives you some output then?
<bamse> Lenni: i think " slot 2: none (active)" says that your "none sim" is the active one
<bamse> not sure about the numbering here, but i'm guessing you want "mmcli -m 2 --set-primary-sim-slot=1"
<Lenni> bamse: That command worked, this message is now sent over mobile data. Thank you!
<Lenni> Did I understand it correctly that it was just defaulting to the eSIM?
<bamse> yeah, your modem has 2 sim slots and it defaulted to the esim one...
<bamse> so then it's quite likely that windows fixed that for me
<bamse> and now i learned how to fix that :)
<bamse> thanks
<\[m]> for those wanting to keep windows, I've recently learned about tiny win11, takes up a fraction and I found aarch64 for on my mac in parallels
<Lenni> I remember hearing that it is a bit sketchy because the repo with the builder contains a binary EXE from an unknown source
<steev> bamse: could be a good addition to jhovold's x13s wiki too
<bamse> steev: indeed
<bamse> too bad that he hasn't figured out how to stay connected to irc ;)
<bamse> now he will never know!
<steev> nah, he reads the archives :D
<steev> but you can also clone the wikis and do pull requests against them on the githubs
<steev> or so i've been told, i don't actually know how
<bamse> didn't know that, but that sounds quite useful
<steev> git clone git@github.com:myusername/foobar.wiki.git apparently
<bamse> yourusername or mine? and who's foobar project?
<steev> so git clone git@github.com:jhovold/linux.wiki.git
<steev> no idea how to make it a pull request though :D
<steev> i'm still trying to figure out how to do a custom kali installer for the x1e devices, i'd like to start with kali instead of start with debian and "upgrade"
<bamse> which part, getting kali to run, figuring out how to get the kali installer to run, or figuring out how to make it install a working kali system?
<steev> i tried the mkosi stuff and it just... doesn't go. it exits efi services and then nothing, either its locked up, or something, but it just sits there saying that
<steev> building the custom kali installer, because i need to build a custom d-i (because we use a custom d-i)
<steev> i mean, i know the repos, just gotta figure out how to get the custom kernel into the custom di
<bamse> lockups there tend to be missing dt or some magical flags missing, but do we have any magical flags needed there on x1e?
<steev> i think we just need the usual
<steev> though for mine, i gotta do the thing where i limit it to 32GB
<steev> oh
<steev> oh
<steev> i bet its that
<steev> i completely whiffed on needing to limit 32, i should add that and see if it helps
<tobhe[m]> steev: what tooling does kali use to build ISOs?
<tobhe[m]> live-build like debian?
<steev> yeah we do
<steev> but with a custom build d-i
<steev> overall its easy, i just need to do the custom build with the 6.16 kernel debs/udebs
<steev> actually, lb for the live image, and simple-cdd for the installer
<tobhe[m]> oh i didn't know simple-cdd
<tobhe[m]> but it seems to also use debian-cd internally
<steev> i'd like us to move to something more... modern
<bamse> steev: doesn't seem that unreasonable if the goal is to produce a standard installer image...
<tobhe[m]> if you use grub that might need a patch to work with 32GB too
<bamse> the reason i use mkosi is to generate the custom images, not to distribute them...
<steev> ah right, the grub patch too, did we ever figure out something that was more... generic?
<tobhe[m]> unfortunately not. last I tried I didn't get it working properly and then was distracted by release work
<bamse> what's the grub patch? just limiting grub from using upper memory?
<tobhe[m]> yeah, but that potentially breaks other machines
<tobhe[m]> we should probably try allocating low first and fall back to what it does now
<bamse> if nothing else it's a machine-specific hack...
<bamse> we (different we) should fix the "bootloader"
<tobhe[m]> or that. just check smbios for "Snapdragon.*" and activate the hack if it matches
<tobhe[m]> or get rid of grub
<tobhe[m]> systemd-boot seems to do something similar https://github.com/systemd/systemd/pull/36715
<bamse> but grub in this scenario is just a generic efi application...so it shouldn't have to do custom things
<tobhe[m]> agree it shouldn't, but this appears to be a firmware bug
<tobhe[m]> I think we now have confirmation that people using slbounce don't see it
<bamse> i was told that we had delivered a fix for this problem...
<tobhe[m]> might not have made it to OEMs builds?
<steev> well, progress-ish
<steev> now it just spits out something about unsupported with my kernel :D
<steev> probably don't have some efi thingie enabled in my config
<tobhe[m]> depending on how recent that was my info might also be outdated
<steev> definitely wasn't anything mentioned in the changelogs for the bios
<steev> but i can always check once i finally get it booting here :D
<steev> well, i get part of the way there :D
<steev> now its booting but then it blue screens :D
<tobhe_> bluescreen is the same issue but in the kernel
<steev> this is with systemd-boot and passing mem=32G on the kernel command line
<tobhe[m]> that might not be enough
<tobhe[m]> on grub i also need cutmem 0x8800000000 0x8fffffffff
<tobhe[m]> not sure what the systemd-boot people are doing
mbuhl has quit [Remote host closed the connection]
<steev> hm, i thought that's what the pull request you mentioned does to get around having to do that
<steev> okay, so, guess i gotta grab the ubuntu image and use that to start :D
mbuhl has joined #aarch64-laptops
<tobhe[m]> let me find my grub...
<tobhe[m]> plucky one from https://launchpad.net/~ubuntu-concept/+archive/ubuntu/x1e should work
<steev> bamse: you can tell whoever "we" is, that if they've fixed it, lenovo definitely hasn't shipped the fix :D
<steev> i'm on the latest t14s bios with 64gb of ram and hit it
tobhe_ is now known as tobhe