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
krei-se- has joined #aarch64-laptops
krei-se has quit [Ping timeout: 480 seconds]
tobhe has joined #aarch64-laptops
hexdump02 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
tobhe_ has quit [Ping timeout: 480 seconds]
hexdump0815 has joined #aarch64-laptops
hexdump02 has quit [Ping timeout: 480 seconds]
mbuhl has quit [Remote host closed the connection]
mbuhl has joined #aarch64-laptops
hexdump02 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
krei-se has joined #aarch64-laptops
krei-se| has joined #aarch64-laptops
krei-se- has quit [Ping timeout: 480 seconds]
krei-se has quit [Ping timeout: 480 seconds]
<pengyu[m]>
bryanodonoghub: I think you don't need guess, Those AeoB file from windows drivers can tell these regulators. When I was working on sc8280xp based device, CAMD.bin and CAMR.bin contain lots of information.
<pengyu[m]>
I noticed since sc8280xp, those *_ext drivers are introduced, qualcomm provided the common drivers, vendors repack the ext drivers. Devices configurations are contained in it, it's quiet similar to dsdt.
<pengyu[m]>
* I noticed since sc8280xp, those *_ext drivers are introduced, qualcomm provided the common drivers, vendors repack the ext drivers. Devices configurations are contained in it, i.e. AeoB files, which are quiet similar to dsdt.
patrickm has quit [Read error: Network is unreachable]
patrickm has joined #aarch64-laptops
jhovold has joined #aarch64-laptops
<krzk>
Anyone knows which packages/files on Ubuntu or Debian copntrol installation of dtbs in /boot from DEB? It's nicely installing DTB for rcX, but when I rebased on v6.14, the DTB is not put into /boot (it is only in /usr/lib/linux-image....)
<alexVinarskis[m]>
it has kernel installation hooks that will copy it when running `make install`. However it needs to 'magically' match dtb to your machine, and only copy that one dtb to /boot - defined in `all.db`
<krzk>
alexVinarskis[m]: flash kernel is only for embedded which do not use /boot partition
<krzk>
At least that is what I read when checking it... but maybe they just forgot to update description/help/everything :/
<JensGlathe[m]>
using flash-kernel here, and it looks like Ubuntu 25.04 installed from ISO does, too
svarbanov__ has quit [Remote host closed the connection]
svarbanov__ has joined #aarch64-laptops
<bryanodonoghue>
Pengyu[m] yeah something to extract the windows data is needed -> dts, regulators and sensor init sequences - its all there and not even encrypted or compressed afaik
<bryanodonoghue>
anthony25 kuruczgy[m] we have the ov02c10 detected on the t14s now
<bryanodonoghue>
you might give the update a try on slim7x
<anthony25>
hmm so this is what I tried yesterday, no?
<pengyu[m]>
bryanodonoghue: It is not hard to guess, the structure basically likes package size, 0x0100(start sign?), name_size, name,0x0300(end sign?), another package size, {0x0000, data_size(0x0800, 8B), data,}, ..., If I remembered correctly, someguy wrote a program to extract.
<anthony25>
with this list of regulators, I had this error: https://bpa.st/OCJQ
<bryanodonoghue>
I believe we had a -6 error which went away with the update to t14s
<bryanodonoghue>
so I was asking to double check on slim7x
<bryanodonoghue>
so that is very interesting really
<anthony25>
what does the -110 error mean?
<bryanodonoghue>
-ETIMEDOUT
<bryanodonoghue>
-6 is -EIO
<bryanodonoghue>
so no response on -ETIMEDOUT
<bryanodonoghue>
and not quite sure when -EIO gets set
<bryanodonoghue>
but different results with different regulators
<bryanodonoghue>
I should write a sensor bus probe driver
<bryanodonoghue>
if there isn't already one
<bryanodonoghue>
switch power and reset line
<bryanodonoghue>
probe every address at every reg
<pengyu[m]>
alexVinarskis: I follow your guide to try again. It still doesn't work. It seems that ath12k does not support calibration-variants. grep -r 'qcom,calibration-variants' shows ath10k and ath11k only.
enyalios has quit [Ping timeout: 480 seconds]
uwealtmann[m] has left #aarch64-laptops [User left]
<jhovold>
kuruczgy[m]: good to hear the pmos yoga retimer issue is fixed, it should have been the regulator pinconfig function that was the problem
<kuruczgy[m]>
(It's NixOS not pmos, not sure what level of support exists for the yoga with pmos)
<jhovold>
ah, sorry, nixos
Caterpillar has quit [Quit: Konversation terminated!]
enyalios has joined #aarch64-laptops
erebion3421EPVPN[m] has joined #aarch64-laptops
<erebion3421EPVPN[m]>
Hey there! Current kernel in Debian Testing broke battery readings from /sys/class/power_supply/qcom-battmgr-bat/uevent on the X13s, can I get it from somewhere else?
underpantsgnome[m] has joined #aarch64-laptops
<erebion3421EPVPN[m]>
Version is 6.12.20-arm64, worked fine on 6.12.17-arm64
underpantsgnome[m] has left #aarch64-laptops [User left]
<pengyu[m]>
My android tablet will become a laptop soon :P, with downstream code, it is easy mode now for me to port.
ungeskriptet_ has quit [Remote host closed the connection]
ungeskriptet has joined #aarch64-laptops
<alexVinarskis[m]>
<JensGlathe[m]> "using flash-kernel here, and..." <- Did you need to do anything extra to make 25.04 work? Just did `sudo do-release-upgrade -d` to go from 24.10 concept to 25.04 Beta, for some reason Wayland session is not available, compared to 24.10 lots of wayland related packages are missing... it does not move on X11 with software rendering (on purwa here), its unusable basically :(
<tobhe_>
alexVinarskis[m]: that is unexpected. last time I tested on my T14s everything worked fine. might be worth looking at the logs to see if anything important was removed by accident
<JensGlathe[m]>
alexVinarskis: I would say my Purwa device is still 24.10
<tobhe_>
in particular you should have an ubuntu-desktop meta package that pulls in all the important stuff
<JensGlathe[m]>
and also it is software rendering
<tobhe_>
krzk: yeah, flash kernel is the correct answer. I would guess that the problem could be the dtb search path. ubuntu installs them to /lib/firmware/$kernel_release/device-tree/, I think the mainline .deb and Debian use a different path
<alexVinarskis[m]>
JensGlathe[m]: it would take me now ~5-6mins to take a screenshot, open client to share it, thats how slow it is haha
<alexVinarskis[m]>
could you share list of packages installed, if its ok? I could compare it to mine and install diff
<JensGlathe[m]>
sent
<JensGlathe[m]>
would be cool to have x1-45 support
<tobhe_>
I guess you could try something like sudo apt-get -o APT::Install-Recommends="true" -o APT::Install-Suggests="true" install ubuntu-minimal ubuntu-desktop-minimal to make sure all the suggested and recommended dependencies are installed
<tobhe_>
if the x1e-settings package is still installed it is unlikely to be the problem. there shouldn't be any major changes
<steev>
erebion3421EPVPN[m]: i can't reproduce here? what do you mean it broke reading from it?
<alexVinarskis[m]>
tobhe_: unfortunately did not help, seems everything is installed
<alexVinarskis[m]>
But upstream x1e-settings doesn't support Asus Zenbook yet, my local build does (MR that I shared with you). Couldn't that be an issue?
<tobhe_>
I guess without your change you might be missing firmware in the initrd
<tobhe_>
that's the only difference I can see. the other part is only to have it install automatically and doesn't matter if it is already installed
jhovold has quit [Ping timeout: 480 seconds]
<JensGlathe[m]>
Data point: I did do-release-upgrade to plucky on the ThinkBook, and it worked reasonably well. It moved to X11 / software rendering, but is as usable as before. Needed to enable the x1e concept ppa, edit it to plucky. Worked. Had to re-install sublime and element-nightly since the apt sources were gone. That worked well, too.
<tobhe_>
yeah do-release-upgrade does disable all PPAs by default
<JensGlathe[m]>
Since the ThinkBook is not in Ubuntu-Concept at all, there was no info re modalias
<tobhe_>
did it use wayland + software rendering before? afaiu the x1p don't have working gpu support yet right?
<JensGlathe[m]>
yes and yes
<tobhe_>
i am not 100% sure how gnome determines if wayland is supported. I think it might be /usr/lib/udev/rules.d/61-gdm.rules
<tobhe_>
could be that you can force wayland by setting WaylandEnable=true in /etc/gdm3/custom.conf