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
alpernebbi has quit [Ping timeout: 480 seconds]
alpernebbi has joined #aarch64-laptops
possiblemeatball has quit [Remote host closed the connection]
hightower4 has joined #aarch64-laptops
hightower3 has quit [Ping timeout: 480 seconds]
echanude has quit [Quit: WeeChat 4.2.1]
echanude has joined #aarch64-laptops
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
alfredo has joined #aarch64-laptops
alfredo has quit [Quit: alfredo]
owlman has quit [Read error: Connection reset by peer]
owlman has joined #aarch64-laptops
<steev>
using the new .bin here, instead of the b8c file, i can almost get to my bedroom, which is definitely good. thursday i can probably get a better idea of how far i can go because my sister's place is open layout versus mine which is... not
<steev>
on the flip side... my razer headphones which are 2.4ghz have problems going to my kitchen which is maybe 5 feet from the computer (and i can literally see the dongle while standing in front of the sink...
alfredo has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
<steev>
in fact, i might just drop that patch out
alfredo1 has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
alfredo1 is now known as alfredo
iivanov has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
iivanov has quit [Remote host closed the connection]
mcbridematt has quit [Remote host closed the connection]
iivanov has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
alfredo has quit [Quit: alfredo]
Caterpillar has joined #aarch64-laptops
iivanov has quit [Remote host closed the connection]
owlman has quit [Remote host closed the connection]
hightower4 has quit [Ping timeout: 480 seconds]
iivanov has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
iivanov has joined #aarch64-laptops
alfredo has quit [Quit: alfredo]
alfredo has joined #aarch64-laptops
alfredo has quit [Remote host closed the connection]
alfredo1 has joined #aarch64-laptops
alfredo1 is now known as alfredo
alfredo has quit [Quit: alfredo]
iivanov has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
iivanov has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
hightower2 has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
hightower2 has quit [Ping timeout: 480 seconds]
possiblemeatball has joined #aarch64-laptops
possiblemeatball has quit [Remote host closed the connection]
possiblemeatball has joined #aarch64-laptops
martiert_work has quit [Remote host closed the connection]
martiert_work has joined #aarch64-laptops
iivanov has quit [Remote host closed the connection]
minecrell7 has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
minecrell has quit [Ping timeout: 480 seconds]
iivanov has quit [Ping timeout: 480 seconds]
iivanov has joined #aarch64-laptops
iivanov has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
iivanov has quit []
alfredo has quit [Quit: alfredo]
craftyguy has quit [Remote host closed the connection]
craftyguy has joined #aarch64-laptops
<dgilmore>
Jasper[m]: it does not want to register in Czech Republic. I do have a different sim I can try to see if it is Google Fi thats being problematic.
craftyguy has quit [Remote host closed the connection]
<Jasper[m]>
<dgilmore> "Jasper: it does not want to..." <- Could be a issue where no operator wants to register with that sim
<Jasper[m]>
You can try swithing those around instead of letting MM do it automagically
<dgilmore>
Jasper[m]: yeah. I see people complaining about the data only sims not registering and working well internationally
craftyguy has joined #aarch64-laptops
<dgilmore>
It is likely not an issue with the modem.
craftyguy has quit [Remote host closed the connection]
craftyguy has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
bruno_rodriguezz[m] has joined #aarch64-laptops
alfredo has quit [Quit: alfredo]
martiert has quit [Quit: WeeChat 4.2.2]
martiert has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
<steev>
abby: yep
iivanov has quit [Remote host closed the connection]
possiblemeatball has quit [Remote host closed the connection]
possiblemeatball has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
possiblemeatball has quit [Quit: Quit]
iivanov has quit [Remote host closed the connection]
Caterpillar has quit [Quit: Konversation terminated!]
<clover[m]>
steev: so the b8c file is not needed anymore?
<steev>
clover[m]: no, it is, in fact, i swore i had rewritten it to only try to load it if found, but somehow that seems to be dropped
<steev>
if you drop the generate nvm name patch, it isn't
<steev>
which i'll be doing in a little bit, just tryng to do some other stuff for work atm
possiblemeatball has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
iivanov has joined #aarch64-laptops
iivanov has quit [Read error: No route to host]
iivanov has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
possiblemeatball has quit [Remote host closed the connection]
<agl>
clover[m]: Can you help me? I have further the problem than under EndeavourOS ARM the Xorg-server died. I can connect over SSH but I have a black screen at the x13s. I have updated to the new linux-kernel and the new x13s-firmware, but Xorg died further.
<agl>
clover[m]: I don't know where I have to look.
<clover[m]>
I'm sorry I use Wayland. I wouldn't know how to debug xorg, which is not really supported anymore
<agl>
ok, how I can use wayland under your EndeavourOS arm ?
<craftyguy>
does anyone know what changed in the new qca BT fw that was pushed to linux-firmware
<craftyguy>
in other news, I've been running the version "41" ath11k fw from linaro's branch for like a week now and it seems to have completely solved the frequent dropouts I was getting with PM enabled on my 5GHz wifi \o/
bumble[m] has joined #aarch64-laptops
<bumble[m]>
craftyguy: yay! looking forward to get that in postmarketos
<steev>
craftyguy: they never tell us what they changed in the firmware, unfortunately
<craftyguy>
:(
<exeat>
Does the new firmware also fix the BT range problem?
<Jasper[m]>
steev: I haven't checked, but could the Lenovo Windows wireless driver changelog contain a hint?
<craftyguy>
I had to load some other fw thing that I got straight from lenovo, to fix the range problem. I haven't tried the new fw in linux-firmware
<steev>
Jasper[m]: i don't think so, the version of the windows firmware looks to be 0297, and the version in linux firmware is 0639
ellyq has quit []
<Jasper[m]>
steev: Ah
ellyq has joined #aarch64-laptops
<steev>
unless i just still have a really old version of the bt firmware from windows, i'll reboot later today and check i guess
<Jasper[m]>
<steev> "unless i just still have a..." <- Getting it from the lenovo website may be better if you don't wanna reboot hahaha
<steev>
oh i don't mind rebooting, just in the middle of other things :)
<agl>
steev: It gave lunch and so I was some minutes away.
<agl>
[ 12.255080] adreno 3d00000.gpu: iommu configuration for device failed with -ETIMEDOUT
<agl>
[ 12.255504] msm-mdss ae00000.display-subsystem: probe with driver msm-mdss failed with error -110
<agl>
steev: in /var/log/lightdm was plymouth which was not executable. I install plymouth.
iivanov has joined #aarch64-laptops
<steev>
plymouth is just a splash screen at boot. i'm not sure what you mean in there was plymouth
<steev>
but, msm-mdss failing with a timeout i've no idea, but that would definitely stop graphics from working
<steev>
and again, i have absolutely no experience whatsoever with endeavor
<bamse>
agl: do you have CONFIG_SC_GPUCC_8280XP=m
<agl>
bamse: I use the kernel from clover[m] ... I must look.
iivanov has quit [Ping timeout: 480 seconds]
<clover[m]>
bamse: Yes
<steev>
craftyguy: what was the firmware file named? and can you run strings on it?
* craftyguy
looks
<craftyguy>
the filename is hpnv21.bin
<steev>
the first line from strings should give the version string
<craftyguy>
BTFW.HSP.2.1.0-00297-WOS_PATCHZ-1
<steev>
that's just the windows firmware, named .bin
<craftyguy>
this file was extracted from the windows thing that lenovo distributes
<steev>
yeah, on windows it's a .b8c file (and what i had patched the kernel to use)
<steev>
which according to someone who replied back when i was working on the driver... it's android firmware?
<craftyguy>
ya I don't recall... but at the time using this version from lenovo fixed the bt range issues I was having
<steev>
that's the extent that i know :D
<JensGlathe[m]>
The b8c file is also part of the Windows driver package. Not sure if they use everything thats in the package
<steev>
doubt they do, it's basically the same files as the commit, just different names
<craftyguy>
I haven't tried removing it to see if the range issue has been fixed in newer linux-firmware versions... that's why I asked earlier if anyone knew what changed in the recent patch :)
<steev>
can always mv that file outta the way :P
<steev>
i can get to my bedroom but my apartment has horrible signal regardless
<craftyguy>
yeah that's what I'm going to do... :P
<steev>
hm, there do seem to be some new lenovo drivers in windows update
<steev>
lenovo system 2.1.17.0 and 11.1.1.11
<steev>
i appreciate that they have the exact same names
<steev>
and lenovo software had a "lenovo base utility" that from the readme talks about the special function keys that we can't access
<bamse>
clover[m]: not sure what dependency 3da0000.iommu would be missing then...
<agl>
steev: ther is no /dev/dri directory. The Xorg-Server try to open /dev/dri/card0
<steev>
agl: that makes sense because the display subsystem is timing out
<agl>
[ 12.256479] arm-smmu 3da0000.iommu: probe with driver arm-smmu failed with error -110
<agl>
[ 12.256803] qcom-rpmhpd 18200000.rsc:power-controller: sync_state() pending due to 3d90000.clock-controller
<agl>
clover[m]: I have installed the x13s-firmware
<agl>
I must go home (i'am in the clubhouse). I'am in ca. 35 minutes at home.
<clover[m]>
Do a uname -a
<agl>
[ag@EOS-x13s ~]$ uname -a
<agl>
[ag@EOS-x13s ~]$
<agl>
Linux EOS-x13s 6.9.2-2-x13s-g4ad79d624a0a #1 SMP PREEMPT Tue Jun 11 01:05:14 UTC 2024 aarch64 GNU/Linux
<steev>
could he potentially not be using the correct dtb?
<agl>
ok later I try steev
<agl>
I must go
<craftyguy>
steev: ya sounds about right. i only grabbed the .bin from it I mentioned earlier, and also have linux-firmware installed. Does loading the windows one take priority over the linux-firmware version if both are on disk?
<steev>
no, well, yes, kinda, if you have my patch, it does. i had a version of it that would load b8c if it existed, and bin if not, but i cannot seem to find that now in my patchsets
<KieranBingham[m]>
Video calls coming soon on x13s :-)
<JensGlathe[m]>
nice
iivanov has quit [Ping timeout: 480 seconds]
alfredo has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
iivanov_ has joined #aarch64-laptops
iivanov has quit [Read error: Connection reset by peer]
<agl>
clover[m] & steev: Now it works! I'am at the grafical screen of my x13s under EndeavourOS arm. What have I do: I rename /usr/lib/firmware to an other nameand make then "pacman -S x13s-firmware". Then there is a new /usr/lib/firmware created with the x13s firmware. Reboot and then it works. It seems in my old firmware-tree was something wrong. Then i delete the old firmware tree.
<JensGlathe[m]>
so it was the missing firmware
<steev>
somehow :)
<JensGlathe[m]>
for graphics (unaccelerated) you need at least a660.sqe and a660.gmu
<agl>
JensGlathe[m]: No I have twice times installed the new x13s-firmware. It seems somthing was wrong in my old firmware tree.
<JensGlathe[m]>
hmm is x13s-firmware only the *8280.mbn part?
iivanov has quit [Remote host closed the connection]
<clover[m]>
nevermind, it is broken
<steev>
does anyone happen to remember which patchset fixes the usb-c phy flippery? or is that still unsolved?
<agl>
clover[m]: Oh, I hope you still have a working gnome.
<clover[m]>
yeah i do, its just that extension that is broken
iivanov has joined #aarch64-laptops
iivanov has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
<agl>
Okay, I'am going to bed. Here it's 11 pm. Good night!
<steev>
broken or just not compatible since gnome likes to break extensions every friggin release
<clover[m]>
yeah idk. too lazy to go deep into it. still trying to fix docker atm
<clover[m]>
that moby script is going to be helpful i think
<steev>
sorry :/
alfredo has quit [Quit: alfredo]
<steev>
this performance issue is driving me insane, i could reproduce the issue with texlive by using qemu arm64 on arm64 (albiet still faster than x86_64), but i cant with python
<Dantheman825[m]>
Well now it works for some reason
<Dantheman825[m]>
I accidentally drained my laptop’s battery dry last night, so had to plug it back in and power it back up, but I’ve been doing reboots for the past few months
<Dantheman825[m]>
So I guess all it took was a cold boot
iivanov has quit [Remote host closed the connection]