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
<steev> Between which chip and heat sink clover[m] ?
hightower3 has joined #aarch64-laptops
hightower2 has quit [Ping timeout: 480 seconds]
<steev> 6.6 rc1 has been tagged :)
<steev> (i've not tested or anything, just saw)
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
<steev> https://salsa.debian.org/kernel-team/linux/-/merge_requests/842/diffs?commit_id=efc68ea51d807a242a549411e64d56de3840312c looks like someone opened a merge request with debian to get x13s (all? haven't read through a kernel config to see if anything is missing yet) needed options enabled in the debian kernel builds
<steev> oh it's ema that did :)
<steev> [ 3.423383] genirq: Flags mismatch irq 218. 00082008 (hid-over-i2c) vs. 00082008 (hid-over-i2c)
<steev> [ 3.423411] i2c_hid_of 21-0015: Could not register for hid-over-i2c interrupt, irq = 218, ret = -16
jhovold has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
alfredo1 has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
alfredo1 is now known as alfredo
<ema> steev: yes! I hope to get that merged soon, then we'll need to add all the relevant modules to the installer and that should be it! :)
<ema> the official vanilla images should work for most things (except for what is known not to work, notably kvm and a few other things)
hightower3 has quit [Ping timeout: 480 seconds]
alfredo has quit [Ping timeout: 480 seconds]
alfredo has joined #aarch64-laptops
hightower2 has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
altacus__ has joined #aarch64-laptops
altacus_ has quit [Ping timeout: 480 seconds]
altacus__ has left #aarch64-laptops [Leaving]
altacus has joined #aarch64-laptops
hightower2 has quit [Ping timeout: 480 seconds]
<erebion[m]> What exactly is known not to work?
<ema> erebion[m]: kvm, audio, webcam
<erebion[m]> Is that a complete list?
<erebion[m]> Or just the most noticeable?
<ema> the complete list of what I'm aware of, which may not be the actual complete list :)
<erebion[m]> And... has anyone looked at the webcam yet? Does it look like this could at some point work as well?
<erebion[m]> I know audio seems to get closer as some told me either here or in #_oftc_#debian-arm:matrix.org
<erebion[m]> Wait, 5G. Does that work?
<erebion[m]> It seems like this whole thing is pretty close to what I would need for a main machine. Just audio is missing, 5G apparently works for some Arch users, so should work on Debian as well, I guess.
<erebion[m]> As soon as audio works I might actually consider buying my own more seriously to replace my X270 (keyboard backlight and trackpoint stopped working, looking at what I could find online the voltage pin for the flat cable might not have voltage, as the seperate click buttons for the trackpoint work and they seem to have seperate pins)
<erebion[m]> Oh and voltage would fit with backlight and trackpoint not working, as both need power.
<erebion[m]> Oh and I can toggle the state and read it from /sys so I know I can toggle the light, it just never actually lights up.
<erebion[m]> Anyway, I could live without webcam, temporarily without audio as well by using Bluetooth, but when audio works it is good enough for me. :)
<erebion[m]> Currently only playing with the X13s from work as they are as curious about Linux on that as I am
<erebion[m]> And I finally found a replacement for Signal-Desktop which seems to be available for ARM: https://gitlab.com/schmiddi-on-mobile/flare
<erebion[m]> Sure, I could compile it myself, but it is a buggy Electron app I'd prefer to not use.
<steev> audio works fine, you just need some things that are still out of tree
<steev> and yes, people are working on the webcam
<erebion[m]> Audio input as well? Last time I asked that still had some issues.
<konradybcio> as for camera, it's another thing that we need to build half the infrastructure for.. so it understandably takes some time!
hightower2 has joined #aarch64-laptops
<exeat> Speaking of things that don't work yet: some more of the F-key functions would be nice to have, and it would be great if the function leds were controllable like capslock is.
<steev> i'm not sure about audio input, i keep meaning to try to test that again
<steev> i don't think we'll ever be able to poke into the ec for the led functions like can be done on x86 thinkpads, but who knows
<clover[m]> steev ^ that shows where thermal material should go
<clover[m]> when i lifted the heatsinks my coverage was spotty so im going to cover it with that phase change material to see if i can get better thermals
<steev> oh
<clover[m]> yeah, it might be the same material that covers the wwan card
<clover[m]> lenovo has been known to use PCM7950 before
<steev> good to know
<_[m]1> <steev> "6.6 rc1 has been tagged :)" <- our future stable huh 😜
<steev> possibly!
<_[m]1> it's promising huh, I really like the look and feel of this laptop and I'm guessing this appeal makes people that can do the work are like motivated? because they want to use it themselves?
<steev> that's because this feels like a thinkpad and not an arm laptop
<steev> it very much reminds me of my x1 carbon
<_[m]1> I never got that one because I was sure it couldn't get cooled properly! the arm boards seem so small in comparison dunno
<_[m]1> and less energy usage, less heat generated
<_[m]1> * less energy usage, less heat generated - at least I guess
<clover[m]> jhovold: got your message, not sure why emails are going to the mailing list encrypted. In any case, no worries since I have worked around my issue by dropping my 21BX board into my 21BY chassis! I will leave a warning message on my wiki about 21BY models possibly having WLAN issues under Linux
<jhovold> clover[m]: it seems like the message went unencrypted to the list, but encrypted to me personally
<jhovold> does this mean you will no longer be able to reproduce the issue you just reported?
<jhovold> also I have a BY here with no such issues
<clover[m]> i can probably reproduce it on the other x13s since windows seems to be working, but i havent tried linux since doing laptop surgery last saturday
<clover[m]> ok good to know some BY boards work
hightower2 has quit [Remote host closed the connection]
hightower2 has joined #aarch64-laptops
xroumegue has quit [Ping timeout: 480 seconds]
xroumegue has joined #aarch64-laptops
alpernebbi has quit [Ping timeout: 480 seconds]
alpernebbi has joined #aarch64-laptops
<_[m]1> after 6.6.0 I am never rebooting again ugh stupid boot loop
<steev> dang
<steev> i've only ever had that happen with the windows update that was causing it to blue screen, but even that let me in after redoing the bitlocker key
<_[m]1> you had to switch on and off tpm ?
<steev> no
<steev> windows update reboot would bluescreen, looped about 3 times and then kick me into bitlocker recovery
<_[m]1> now it crashed after entering my user password twice (and had to give decryption pw 4-5 times)
<steev> maybe enter the correct password :P
<_[m]1> to put back a backup or some shit?
<steev> i think that's what it did yeah
<_[m]1> I'm seeing in the grub luks prompt missing efivars but I have verified and the folder is populated
<_[m]1> it's like /sys/firmware/efivars
alpernebbi has quit [Ping timeout: 480 seconds]
<steev> do you have efivars as a module?
<_[m]1> * I'm seeing in the grub luks prompt unknown filesystem type efivars but I have verified and the folder is populated
<_[m]1> ah you need that?
<_[m]1> no
<steev> the default for EFIVARS_FS is m i think
alpernebbi has joined #aarch64-laptops
<steev> not sure why that would affect encrypted boot though?
<_[m]1> oh ok nice now it consistently crashes on 3 pw entry attempt when trying to login to the system
<_[m]1> steev: nah it's unrelated I think
<_[m]1> but the message is there (then again I wouldn't be certain)
<steev> you could try setting EFIVARS_FS=y, if you haven't already, just so its built in
<_[m]1> don't know either what was meant with "use clang to debug", my knowledge is limited
<_[m]1> k txx
<_[m]1> * k tx
<steev> would at least get rid of that message, i think
<_[m]1> @clover I'm trying to boot the new kernel but now I can't seem to find the old kernel in the grub menu
<clover[m]> new kernel overwrites old kernel
<_[m]1> oh my
<_[m]1> ok so when I take the fallback image, it takes the pw immedialy of FDE but now it keeps crashing on login 😲
<_[m]1> and seems first time after rebooting the fallback it also takes it immediately on the normal entry
<_[m]1> or not
<_[m]1> * the fallback initramfs image, it
<_[m]1> not always either -_-
<_[m]1> seems to be a gnome thing -_-
<clover[m]> time to learn sway
<_[m]1> ctrl alt f2 not working again mm
<_[m]1> shouldn't this work ? https://oftc.irclog.whitequark.org/aarch64-laptops/2023-09-11#;ctrl%20alt%20f2
<Jasper[m]> <steev> "not sure why that would affect..." <- It might not be loaded during initfs when using fde
<clover[m]> (⊙_◎): do you find the fallback image helpful? it's quite noisy so i was thinking about disabling it since i never use it
<_[m]1> how so noisy?
<clover[m]> try running mkinitcpio -P and you will see what i am talking about. lots of "WARNING: Possibly missing firmware for module:" lines when generating the fallback image
<_[m]1> ah yeah I saw that indeed, is that just for the fallback? why only there?
<_[m]1> could it be that the kernel update broke the gnome login
<_[m]1> plasma can login but it still has black screen
<clover[m]> i did a pacman update and had to install llvm libraries or else sway wouldn't start
<clover[m]> (⊙_◎): maybe try pacman -S llvm15
<clover[m]> robclark: does current mesa (23.1.7) need llvm15 to work? would that explain why sway failed to launch after updating to llvm16?
<clover[m]> oh maybe because when i built it yesterday it was using the older llvm. will try to rebuild
<_[m]1> I can't login to the DE and I can't switch to cli -__-
<clover[m]> you might need to use archiso as a rescure disk and then chroot in
<_[m]1> eh why not once more 🙂
<_[m]1> how you figured llvm15?
<clover[m]> just a hunch
<clover[m]> it was looking for llvm15 libs when i ran sway from command line
<robclark> clover[m]: depends on which drivers it is built with, looks like radeonsi/amdgpu need llvm15 but otherwise you don't need something that new
<clover[m]> (⊙_◎): try doing a pacman update to pull in the mesa update and see if that fixes it
<_[m]1> I did pacman -Syu
<robclark> clover[m]: I guess you could build mesa without amd drivers?
<robclark> although probably you need to make sure what you have installed matches what mesa was built with
<clover[m]> robclark: so i rebuilt mesa with llvm16, and now sway launches correctly without needing the older llvm libs. but now chromium / electron is broken hmm
<HdkR> Does Arch not let you have both llvm 15 and 16 installed at the same time?
<clover[m]> it does, just trying to get to the bottom of how stuff broke
<_[m]1> the fun never ends 🙂
<steev> Jasper[m]: right, but what does efivars have to do with unlocking fde
jhovold has quit [Ping timeout: 480 seconds]