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
<steev>
looks like 6.12.19, so yeah you should have it
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<erebion>
Also, I have libcamera installed
<erebion>
Still GNOME Camera says "no camera found"
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
shoragan has quit [Quit: quit]
shoragan has joined #aarch64-laptops
thevar1able_ has quit [Remote host closed the connection]
thevar1able_ has joined #aarch64-laptops
<steev>
are you sure you're using the debian kernel's dtb?
<steev>
if you install libcamera-tools what does cam -l say?
tobhe_ has joined #aarch64-laptops
hexdump01 has joined #aarch64-laptops
tobhe has quit [Ping timeout: 480 seconds]
hexdump0815 has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
mbuhl has quit [Remote host closed the connection]
mbuhl has joined #aarch64-laptops
todi has quit [Read error: Connection reset by peer]
todi has joined #aarch64-laptops
erebion has left #aarch64-laptops [Error from remote client]
mynery[m] has joined #aarch64-laptops
<mynery[m]>
i just updated my nix on x13s and my new generation only boots to a tty instead of a gui. were there any issues regarding this with the mainline kernel? i assume not, but who knows
<mynery[m]>
also, is there a maintained fork of the nixos-x13s flake that supports mainline or should i just ditch the flake at this point?
erebion has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
svarbanov__ has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
svarbanov__ has quit [Ping timeout: 480 seconds]
hogliux has joined #aarch64-laptops
<hogliux>
Will there ever be any chance of getting USB4 PCIe tunneling working on linux for slim 7x? It definitely works on Windows.
<hogliux>
and here is a screenshot with a thunderbolt network device plugged in Windows (obviously there are no arm64 drivers for windows for this device): https://pasteboard.co/NDB0EdySTvPe.png
<hogliux>
I can see in device manager that the thunderbolt root bridge is attached to the PCI root bus at ACPI\PNP0A08\0. So I could look at the ACPI tables to figure out which PCI bus that is and enable it in the slim 7x dts
<hogliux>
But I think I'd probably also need patches to the ps883x driver to actually pass-through the PCI signals. Are there any datasheets for the ps883x anywhere (I couldn't find any). Any ideas from anybody else on how I could go about to try to add linux support for PCIe passthrough?
<HdkR>
Would be nice.
<hogliux>
(It surprised me btw that for the USB4 PCIe tunneling, Qualcomm seems to be relying on Intel chips, i.e. Alpine Ridge. See second screenshot above)
<travmurav[m]>
perhaps that's in the adapter?
<hogliux>
Hmmm maybe. Multiple thunderbolt devices list the same chip though. But possible.
<hogliux>
Is the ps883x connected via i2c or similar? If there is some kind of way to record i2c messages in Windows then I could record what happens when a thunderbolt device is plugged in and experiment with replaying that on Linux
<JensGlathe[m]>
i2c
hogliux has quit [Remote host closed the connection]
<erebion>
Could you point me to the source of your DTB so I can find the one from Debian and compare whether that might be different for anything camera related?
tstachecki has joined #aarch64-laptops
<tstachecki>
managed to get audio working on SL7 with pulse by adding load-module module-alsa-sink device=hw:X1E80100Romulus,1. not sure why it doesn't auto detect.... Will look more later
<tstachecki>
retracing steps... Seems I also had to run alsaucm -c hw:0 set verb HiFi, probably something related to auto detection also
SpieringsAE has quit [Ping timeout: 480 seconds]
Core3708 has joined #aarch64-laptops
SpieringsAE has joined #aarch64-laptops
Core4770 has joined #aarch64-laptops
tstachecki has quit [Ping timeout: 480 seconds]
SpieringsAE has quit [Remote host closed the connection]
SpieringsAE has joined #aarch64-laptops
Core3708 has quit [Ping timeout: 480 seconds]
SpieringsAE has quit [Remote host closed the connection]
SpieringsAE has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
Core4770 has quit [Read error: Connection reset by peer]
tstachecki has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
Core7635 has joined #aarch64-laptops
tstachecki has quit [Read error: No route to host]
Core7635 has quit [Read error: Connection reset by peer]
tstachecki has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
SpieringsAE has quit [Ping timeout: 480 seconds]
SpieringsAE has joined #aarch64-laptops
SpieringsAE has quit [Quit: SpieringsAE]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
hogliux has joined #aarch64-laptops
hogliux has quit [Quit: Leaving]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<steev>
erebion: unfortunately, the htc rx insufficient thing needs a patch - in kali, i had sophie (she does our kernel bumps) apply jhovold's patch https://github.com/jhovold/linux/commit/7ea7822ac5c32e8c092da43a7ae74dd809efc976 - unfortunately, i'm not sure the status of it, so i don't know if debian would accept it into their kernel sources
<steev>
they typically won't pull something in until its in at least linux-next
<steev>
erebion: is that daily built against trixie or against sid?
agl has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
agl has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<erebion>
steev: Not sure
<steev>
just grabbing the dtb from the daily-image, you should have it as part of linux-image-6.12.xx... in /usr/lib/linux-image-$(uname -r)
<steev>
that's for me, but we're on the 6.12 from unstable
Core7423 has joined #aarch64-laptops
Core2369 has joined #aarch64-laptops
tstachecki has quit [Ping timeout: 480 seconds]
jdb has joined #aarch64-laptops
Core7423 has quit [Ping timeout: 480 seconds]
jdb has quit []
jdb has joined #aarch64-laptops
jdb has quit []
agl has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
agl has joined #aarch64-laptops
Core2369 has quit [Read error: Connection reset by peer]
tstachecki has joined #aarch64-laptops
jdb has joined #aarch64-laptops
Core4020 has joined #aarch64-laptops
<erebion>
[6:53:09.794056224] [64765] INFO Camera camera_manager.cpp:327 libcamera v0.4.0
<erebion>
Available cameras:
<erebion>
steev: cam -l says this:
tstachecki has quit [Ping timeout: 480 seconds]
<steev>
is that after switching to the 6.12 dtb?
<steev>
assuming they aren't the same
chrisl has joined #aarch64-laptops
jdb has quit [Quit: jdb]
jdb has joined #aarch64-laptops
jdb has quit []
jdb has joined #aarch64-laptops
jdb has quit []
jdb has joined #aarch64-laptops
jdb has quit []
jdb has joined #aarch64-laptops
jdb has quit []
<erebion>
I didn't notice I could simply take it from that package, I downloaded the DTB from the Debian FTP archives linked to on the X13s page in the wiki, maybe my DTB did not match my kernel, now rebooting and testing again...
jdb has joined #aarch64-laptops
jdb has quit []
jdb has joined #aarch64-laptops
jdb has quit []
jdb has joined #aarch64-laptops
jdb has quit []
jdb has joined #aarch64-laptops
<erebion>
Nope, cam -l still does not list a camera
jdb has quit []
jdb has joined #aarch64-laptops
jdb has quit []
jdb has joined #aarch64-laptops
jdb has quit []
jdb has joined #aarch64-laptops
jdb has quit []
jdb has joined #aarch64-laptops
jdb has quit []
chrisl has quit [Ping timeout: 480 seconds]
jdb has joined #aarch64-laptops
jdb has quit []
<steev>
do you still have that udev rule in place because i don't have any
jdb has joined #aarch64-laptops
jdb has quit []
jdb has joined #aarch64-laptops
jdb has quit [Quit: jdb]
jdb has joined #aarch64-laptops
jdb has quit []
jdb has joined #aarch64-laptops
jdb has quit []
jdb has joined #aarch64-laptops
jdb has quit []
jdb has joined #aarch64-laptops
<KieranBingham[m]>
erebion: to get anything useful for debugging, at the debug log levels.