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 has quit [Remote host closed the connection]
martiert has quit [Remote host closed the connection]
martiert has joined #aarch64-laptops
<Dantheman825[m]> I might've made a lapse in judgement
<steev> i like to call them spontaneous science experiments
<Dantheman825[m]> so I ran `unbreak_chroot.sh` in fex's RootFS to install a newer version of Mesa.
<Dantheman825[m]> I was able to build mesa, but my system would not exit the chroot gracefully
<Dantheman825[m]> I think /tmp /dev, and I think /usr/lib/* directories refused to unmount due to being "busy"
<Dantheman825[m]> so I rebooted, and now my Wifi's gone
<Dantheman825[m]> literally everything else is fine, audio, touchscreen, whatnot, so I don't think it's a firmware issue
<steev> a) what device b) what does dmesg say
<Dantheman825[m]> X13s
<Dantheman825[m]> gimme a moment to get the log
<Dantheman825[m]> here you go
<Dantheman825[m]> also `iwconfig` lists this... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/FUvZUMPyPfHIISueqFKVADkk>)
<Dantheman825[m]> the network care isn't usually named like this, is it?
<Dantheman825[m]> s/care/card/
<steev> it is actually default named to that
<Dantheman825[m]> ah, okay so that's not concerning then
<steev> nope, everything on the kernel side seems like it's working
<steev> i'd check networkmanager logs, assuming it's still networkmanager
<Dantheman825[m]> here's what journalctl says
<steev> those wrong perms make me think.... did you do anything in the chroot to change permissions?
<Dantheman825[m]> I think the unbreak_chroot and break_chrootprobably did something fucky
<Dantheman825[m]> * I think the unbreak_chroot and break_chrootscripts probably did something fucky
<steev> sounds like the perms are messed up, yeah
<steev> Dec 26 20:06:10 daniel-X13s NetworkManager[884]: <warn> [1703649970.2496] plugin: skip invalid file /usr/lib/aarch64-linux-gnu/NetworkManager/1.44.2/libnm-device-plugin-wifi.so: file has invalid owner (should be root)
<steev> i'd check all the files in there
<Dantheman825[m]> these perms will be a mess to fix :(
<travmurav[m]> can you ask the package manager to reinstall everything?
<steev> yeah, that might be the best bet
<Dantheman825[m]> what would the apt equivalent be of that? sudo apt reinstall *?
<steev> i'd probably just reinstall network-manager which has those files ; sudo apt install --reinstall network-manager
<steev> the problem with trying to do something like what you suggest is that everything will then be marked as manually installed and un-needed dependencies won't go away
<Dantheman825[m]> ah, yikes
<Dantheman825[m]> steev: okay, that worked for me, thank you
<steev> that fixed the wifi too?
<Dantheman825[m]> yes
<steev> nice
<Dantheman825[m]> I imagine I'll run into additional permission issues down the line, but right now I don't know what they may be since I haven't encountered them yet
<steev> probably
<steev> i'd probably check for stuff that isn't owned by root in there
<steev> you can then check what package it is, by running `dpkg -S /path/to/file` and then reinstall it
<Dantheman825[m]> in the FEX Rootfs?
<Dantheman825[m]> or in /?
<steev> probably in yours, since that's where the issue is
Lucanis has quit [Read error: Connection reset by peer]
Lucanis has joined #aarch64-laptops
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
jhovold has joined #aarch64-laptops
Caterpillar has joined #aarch64-laptops
Kelsar has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
Kelsar has joined #aarch64-laptops
enyalios_ has joined #aarch64-laptops
enyalios has quit [Ping timeout: 480 seconds]
systwi has quit [Ping timeout: 480 seconds]
systwi has joined #aarch64-laptops
<jenneron[m]> bamse: i got headphones to work and maybe fixed touchpad on lenovo flex/yoga 5g. it also seems that UFS problem is solved by upgrading from 6.6.0 to 6.6.8
<jenneron[m]> however, what i want to ask is why TCPD and TSC2 have the same interrupt in ACPI and has anyone tried to get touchscreen and pen working?
<bamse> jenneron[m]: nice
<bamse> jenneron[m]: i don't think i've looked at either touch or pen...
<jenneron[m]> touchscreen has some reset gpio, it may deserve a separated driver based on i2c-hid-of
<travmurav[m]> jenneron: I think hid-over-i2c defines reset gpio
<travmurav[m]> at least the driver does afaict
<jenneron[m]> interesting, it is undocumented
<jenneron[m]> there are also some delays in ACPI
<jenneron[m]> between resetting and toggling regulators
<travmurav[m]> jenneron: and they are also defined in the driver afaict...
<travmurav[m]> post-power-on-delay-ms post-reset-deassert-delay-ms sounds like what you are describing at least xD
<travmurav[m]> there is some fun comment about it being internal, not sure what's that about
<jenneron[m]> hmm okay let's try it
<travmurav[m]> might want to add it like wacom one - a dedicated compatible with a fallback and maybe define the binding to always set those when that compatible is used with an if directive, at least I'd guess this is what the comment means
<travmurav[m]> but well, just making it work would be a first step anyway xD
<steev> oh that's awesome jenneron[m] do you have a kernel branch? i haven't touched my flex5g in a while, it just sits on my coffee table sad
<jenneron[m]> use sc8180x_defconfig
<steev> do you still see an issue with heavy internet traffic that the touchpad gets... sluggish?
<jenneron[m]> steev: do you mean the issue when touchpad gets stuck on some clicks and it results in scrolling instead of moving cursor?
<steev> no
<jenneron[m]> ohh
<steev> i mean when you're downloading a large file, moving the cursor around causes it to stutter
<jenneron[m]> i know what are you talking about
<jenneron[m]> steev: use iommu.strict=0 in cmdline
<steev> makes sense
<jenneron[m]> i think bamse has been working on a patch to fix it without using non-strict iommu
<jenneron[m]> steev: are you going to try it? can you send me the output of `strace alsaucm reload 2>&1 | grep ucm2`?
<jenneron[m]> my device is lenovo yoga 5g, not flex 5g, so my path for ucm may not work for you
<steev> jenneron[m]: when i head back to my place later (watching my sister's place while they're home for christmas), i'll grab it and bring it back over and definitely try it out
<jenneron[m]> yeah, the path is /usr/share/alsa/ucm2/conf.d/sm8150/LENOVO-81XE-Yoga5G14Q8CX05-LNVNB161216.conf which contains Yoga5G
<jenneron[m]> definitely not going to work on flex 5g, needs a symlink
<steev> probably yeah
<jenneron[m]> ucm config
<jenneron[m]> travmurav: touchscreen works
<jenneron[m]> TSC2 is probably unused.. at least on my variant
systwi has quit [Ping timeout: 480 seconds]
<jenneron[m]> yeah, pen works as well
<jenneron[m]> no idea what is TSC2
<jenneron[m]> there are still not working features on this device: speakers and mics, sensors, fingerprint, qcom-venus, keyboard backlight, suspend, maybe DP
systwi has joined #aarch64-laptops
<jbowen> What are folks using to tune power/battery usage?
<bamse> jenneron[m]: didn't i post the sc8180x patch (in mdss/dpu) as well?
<bamse> jenneron[m]: for the non-strict iommu thing
<jhovold> jlinton, travmurav[m]: i had reason to look closer at the bluetooth driver today, and indeed the device address needs to be reversed on the X13s
<jhovold> presumably that's the same on all non-ROME devices, unless the fw developers screwed up badly
<jhovold> let's see what qcom says
systwi has quit [Ping timeout: 480 seconds]
<steev> i still have no idea what the frame timeout is :(
<jenneron[m]> bamse: i don't remember about sc8180x
<jenneron[m]> if yes please send the link, i will include it in my fork
Ablu is now known as Guest11999
Ablu has joined #aarch64-laptops
systwi has joined #aarch64-laptops
Guest11999 has quit [Ping timeout: 480 seconds]
<steev> jhovold: not sure why but with your patch, i had to actually power off, not just restart to get the bluetooth addr to apply in lsb
<steev> er, no... i have to boot into windows?
<jhovold> steev: you can't set the bd-addr using udev directly, unless perhaps if you've disabled some systemd settings
<jhovold> command line works fine though
<jhovold> and you specifify it in MSB order on the command line (MSB is used in all UIs, LSB internally and in DT)
<steev> erk. where the hell am i setting it then lol
<jhovold> probably using a version of hans's systemd service: https://github.com/bluez/bluez/issues/107
<steev> oh right,t he override, yeah
<steev> i wonder why it was correct the first time after i powered off out of windows
<jhovold> windows had set the address correctly, presumably
<jhovold> but i guess, we'd still mark it invalid, so scratch that
jhovold has quit [Quit: WeeChat 4.0.4]
<steev> yeah, windows shows it correctly, it was just me being silly
<steev> moving that udev rule file out of there so i don't spend 20 minutes editing it and re-editing it thinking i screwed up :D
jhovold has joined #aarch64-laptops
jhovold has quit [Ping timeout: 480 seconds]
jhovold has joined #aarch64-laptops
jhovold has quit [Ping timeout: 480 seconds]
txnintn has joined #aarch64-laptops
<txnintn> Would this be the right place to hang out? I have a Dell Venue 8pro 5830 with a Atom Z3740D. I would like to convert to linux and run a Home Assistant clien on it.
txnintn has quit [Quit: Got to go, my Pi is on FIRE!!!]
txnintn has joined #aarch64-laptops
<jbowen> txnintn: the Atom Z3740D is still an x86_64 processor, so you should be able to run a distro with x86_64/amd64 support (i.e. pretty much anything these days)
<jenneron[m]> bamse: i was mistaken, UFS problem still happens
<jenneron[m]> i should probably try the latest release candidate
<txnintn> jbowen -. I'm a bowen, decendent of Moses Bowen arrive 1690's
<txnintn> I run most of my rpi4s on alpine linus with a vanilla aarch64 setup.
<jbowen> I don't know my family history back more than 4 generations, but perhaps we share a common Bowen ancestor :)
<txnintn> I have the bowen back past Rodrick the Great in 740 ad in Wales.
<jbowen> Back to ARM stuff, I don't expect anyone will ask you to leave, but the Atom Z3740D being an x86 processor would be offtopic for this channel
<txnintn> ok, I understand. Only pain it on the convertion is has a 32bit uefi with a 64bit os yippie
<jenneron[m]> txnintn: there is some work in pmOS on x86_64 generic port that will be bootable with 32 bit efi https://gitlab.com/postmarketOS/pmaports/-/merge_requests/4554
<txnintn> thanks I'll look in two it. I'm goin to get a virt going so I work on it there first thanks for the link.
txnintn has left #aarch64-laptops [Leaving]