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
ellyq_ has quit []
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
tobhe has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
tobhe_ has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
paddymahoney has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
alfredo has quit []
alfredo has joined #aarch64-laptops
alfredo has quit [Quit: alfredo]
matthias_bgg has quit [Ping timeout: 480 seconds]
alfredo has joined #aarch64-laptops
matthias_bgg has joined #aarch64-laptops
<JensGlathe[m]> Bluetooth on HP X14 is up
<JensGlathe[m]> same chip ids as Volterra
<JensGlathe[m]> makes you wonder
<JensGlathe[m]> and the BT host MAC is set correctly from (wherever it was stored)
srinik has joined #aarch64-laptops
jhovold has joined #aarch64-laptops
alfredo has quit [Quit: alfredo]
srinik has quit [Ping timeout: 480 seconds]
<jhovold> abelvesa: by "usb-c dp altmode" I'm just referring to external display
<jhovold> and the monitor that works fine with the x13s, doesn't work at all with the x1e crd so support is definitely broken
<jhovold> those link training errors you also on the monitor that you get it to work with, may just suggest that things are working mostly by chance
<jhovold> works sometimes, with some monitors, does not mean dp support is working, quite the contrary
chrisl has quit [Remote host closed the connection]
chrisl has joined #aarch64-laptops
<jhovold> as I mentioned before, I've only tested on port (the third, on the right side), but iirc anonymix007[m] mentioned seeing the same symptoms as me also on his t14s
<jhovold> one port*
<abelvesa> jhovold: ok, got it.
<JosDehaes[m]> jhovold: when I cherry-pick the bluetooth patches for yoga on top of your 6.11 final branch, it does not work, while on rc7 it does
<JosDehaes[m]> logs ☝️
<jhovold> JosDehaes[m]: yes, steev reported that yesterday as well, one of the serial fixes are exposing another bug in the serial driver
<jhovold> I'm working on a fix as we speak
<JosDehaes[m]> ah great! thx
<steev> slacking on testing smh
<jhovold> steev: i've tracked it down the the third patch in the series exposing an existing bug in the dma support
<steev> oh fun
iivanov has joined #aarch64-laptops
srinik has joined #aarch64-laptops
<jhovold> JosDehaes[m], steev: I don't have time to fix this properly today, but I've added a workaround that should unbreak bluetooth to both the sc8280xp and x1e80100 branches
<jhovold> please give it a test as well
<JosDehaes[m]> jhovold: thx, I will test. Appreciate the fix!
<JosDehaes[m]> jhovold: can confirm working!
<jhovold> thanks for testing
rsalveti has joined #aarch64-laptops
srinik has quit [Remote host closed the connection]
iivanov_ has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
Lucanis has quit [Ping timeout: 480 seconds]
Lucanis has joined #aarch64-laptops
sgerhold has joined #aarch64-laptops
svarbanov has joined #aarch64-laptops
srinik has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
iivanov_ has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
<konradybcio> abelvesa: could you check kde+wayland?
iivanov has quit [Quit: Leaving...]
iivanov has joined #aarch64-laptops
iivanov has quit []
iivanov has joined #aarch64-laptops
iivanov has quit [Remote host closed the connection]
jhovold has quit [Quit: WeeChat 4.3.4]
iivanov has joined #aarch64-laptops
iivanov has quit [Quit: Leaving...]
iivanov has joined #aarch64-laptops
<anonymix007[m]> abelvesa: just checked the video output with USB-C to HDMI dongle and it still doesn't work on T14s
<abelvesa> anonymix007[m]: that's DP+USB scenario, that is currently not working. If you could try DP-only, that is type-c to DP or type-c to type-c. That is currently working on my T14s.
<abelvesa> anonymix007[m]: with the HDMI dongle, it will most definitely try to assign 2 lanes for DP and 2 lanes for USB. The USB does work fine, but DP lanes are messed up in this specific scenario.
alfredo has quit [Ping timeout: 480 seconds]
<anonymix007[m]> abelvesa: I don't really understand why it would assign any lanes to USB. Can you please elaborate?
<tobhe> i think that latest jhovold kernel might actually work better with the 120hz screen
<tobhe> I can break in the initrd and do things, it dies with a blue screen when I mount the root fs
SteveCossette[Farchord][m] is now known as farchord
farchord has quit [Quit: Reconnecting]
farchord has joined #aarch64-laptops
<JensGlathe[m]> blue screen? Like this one?
alfredo has joined #aarch64-laptops
<tobhe> yep
<JensGlathe[m]> In my case it was clock controller related, wakeup from DPMS - screen is 4k@60Hz. Tracked it down to camcc_8280xp, which must (!) be enabled on sc8280xp. And venus, and this resolution. Maybe there are other non-working combinations. Workaround on Volterra is to black-list camcc_sc8280xp.
<tobhe> interesting, thx!
<JensGlathe[m]> so if you're trying to load venus on T14s, this might be enough?
alfredo has quit [Ping timeout: 480 seconds]
iivanov has quit [Remote host closed the connection]
hexdump01 has quit []
hexdump0815 has joined #aarch64-laptops
<agl> steev: In your kernel 6.10.6 the battery guard no longer works. I have heard that there is now a kernel battery monitor, probably as a kernel module. How do I disable the previous battery guard, which is probably running as a process (I think it's the pd-mapper)? And how do I switch on the kernel battery monitor?
<agl> Have i to install one or more packages.
<agl> All on the x13s
iivanov has joined #aarch64-laptops
<steev> i'm not sure what you mean; even with the in kernel modules (which my 6.10 has had since they were available), the userland should work
<steev> sounds like maybe you're missing files if it stopped working, did you have firmware updates or something?
iivanov has quit [Remote host closed the connection]
chrisl has quit [Remote host closed the connection]
chrisl has joined #aarch64-laptops
srinik has quit [Ping timeout: 480 seconds]
<agl> steev: I only did "apt upgrade". I have not done any firmware updates except the ones that are done during Debian/testing upgrades. In your kernel 6.10.4 (Debian/testing) the userland pd-mapper works. It also works in your kernel 6.10.5 (under EndeavourOS from clover[m]). But as of kernel 6.10.6 the battery symbol is no longer displayed, instead only the symbol for brightness is displayed. It no longer finds a battery. Since nothing has been changed on
<agl> the Debian, a missing or old firmware file seems to be the reason. Do you know which one it is and where I can get it?
<steev> it would be the jsn files
chrisl has quit [Remote host closed the connection]
<agl> steev: I found under /usr/lib/firmware/qcom/sc8280xp/LENOVO/21BX the files: adspr.jsn, adspua.jsn, battmgr.jsn and cdspr.jsn. It seems this are the files. From where can I update this firmware files. Gives there a new one for QCOM?
<agl> steev: Ther are alsoo mbn files.
<JensGlathe[m]> agl: the unpopular way (assuming you have a Windows partition on the device) is to just use [fetch_sc8280xp_fw.sh](https://github.com/jglathe/wdk2023_fw_fetch/tree/jg/x13s). It copies all of them.
<steev> is it unpopular... or unknown? because that's the first i'm hearing of the script :P
<JensGlathe[m]> it is there for a year or so now
<JensGlathe[m]> there is also an x1e template branch
<agl> ok I will look ...
<steev> i guess i'd also check if pd-mapper is throwing some errors or something
<steev> but, if you have qcom_pd_mapper, you **shouldn't** need the userland service
chrisl has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
hexdump0815 has quit [Quit: WeeChat 3.8]
iivanov has quit [Ping timeout: 480 seconds]
hexdump0815 has joined #aarch64-laptops
matthias_bgg has quit [Ping timeout: 480 seconds]
iivanov has joined #aarch64-laptops
matthias_bgg has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
tobhe_ has joined #aarch64-laptops
Lucanis has quit [Ping timeout: 480 seconds]
tobhe has quit [Ping timeout: 480 seconds]
iivanov has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
iivanov has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
<spawacz> Hi, I got similar issue, upgraded Debian testing kernel from 6.10.4 to 6.10.9 and the battery status and pulseaudio are not working
<spawacz> pd-mapper is not throwing errors
agl7-x13s has joined #aarch64-laptops
agl7-x13s has quit []
<steev> if you're using the *debian* kernel, 6.10 does not have the pd mapper driver
<steev> but that sounds like the remoteprocs aren't up
<steev> can you check if there is anything in /sys/kernel/debug/devices_deferred
<konradybcio> Jens Glathe: any chance you get some dmesg spam about sync_state and camcc after you get rid of that module?
<steev> spawacz: can you make sure you've updated the dtb file as well?
<steev> i'm on the kali kernel which is based on the debian testing 6.10.9 and do not have issues with audio or charging/battery here using pd-mapper service
<steev> (the kali kernel does not do hardware enablement, not even for myself)
wizzard has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
<anonymix007[m]> sibis: have you had any chance to check secure boot on the devkit?
iivanov has quit [Ping timeout: 480 seconds]
Lucanis has joined #aarch64-laptops