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
alpernebbi has quit [Ping timeout: 480 seconds]
thevar1able_ has quit [Remote host closed the connection]
alpernebbi has joined #aarch64-laptops
<dgilmore>
craftyguy: I have my main network on 3 aps with 2.4ghz, 5ghz, and 6ghz. I roam between the aps all on different frequencies okay. I am running 6.12.9
tobhe_ has joined #aarch64-laptops
tobhe has quit [Ping timeout: 480 seconds]
nothorseface has joined #aarch64-laptops
nothorseface has quit [Remote host closed the connection]
nothorseface has joined #aarch64-laptops
nothorseface has quit []
hexdump01 has joined #aarch64-laptops
sally has quit [Quit: sally]
sally has joined #aarch64-laptops
<JensGlathe[m]>
5 APs here, nothing special set up. 2 of them are separate networks for ... reasons, so the laptop would get a new IP. The laptops usually don't move much between AP areas, the dev kits usually don't move at all. And if it happens, I see HTC Rx errors on all of them. Except for X1e devices, regardless of ath11k or ath12k.
<JensGlathe[m]>
The X13s with 6.13-rc7, msi-map off and iwd is silent now for 30 hours. Only the occasional msdu_done bit message.
alfredo has joined #aarch64-laptops
sally is now known as Guest6061
sally has joined #aarch64-laptops
Guest6061 has quit [Ping timeout: 480 seconds]
nothorseface has joined #aarch64-laptops
nothorseface has quit [Remote host closed the connection]
nothorseface has joined #aarch64-laptops
jhovold has joined #aarch64-laptops
martiert has quit [Quit: WeeChat 4.4.4]
martiert has joined #aarch64-laptops
martiert has quit []
martiert has joined #aarch64-laptops
nothorseface has quit [Ping timeout: 480 seconds]
todi has quit [Ping timeout: 480 seconds]
mbuhl has joined #aarch64-laptops
todi has joined #aarch64-laptops
todi1 has joined #aarch64-laptops
todi has quit [Ping timeout: 480 seconds]
srinik has joined #aarch64-laptops
todi has joined #aarch64-laptops
todi1 has quit [Ping timeout: 480 seconds]
todi has quit [Ping timeout: 480 seconds]
nothorseface has joined #aarch64-laptops
todi has joined #aarch64-laptops
nothorseface has quit []
nothorseface has joined #aarch64-laptops
nothorseface has quit [Remote host closed the connection]
srinik has quit [Ping timeout: 480 seconds]
nothorseface has joined #aarch64-laptops
srinik has joined #aarch64-laptops
nothorseface has quit []
<teythoon>
I'm trying to get the webcam to work on my X13s running Debian, but I'm stuck
<teythoon>
I recompiled the Debian kernel to expose /dev/dma_heap
<teythoon>
but, libcamera's cli utility still doesn't list the camer
<teythoon>
a
<kbingham>
teythoon, can you run "LIBCAMERA_LOG_LEVELS=*:0 cam -l" and paste the results in a pastebin please ?
<kbingham>
also add in a log from 'dmesg'
<kbingham>
and 'media-ctl -p'
<kbingham>
(I should really write a script that does all that and call it 'libcamera-debug' or something)
<kbingham>
That's the main fault. Somewhere along the lines of you don't have the correct drivers registered or installed or loading
alfredo has quit [Quit: alfredo]
<teythoon>
kbingham: that's not actionable, how can i debug this further?
<kbingham>
actionable?
<teythoon>
as in, i don't know what to do next
<kbingham>
You said you recompiled the debian kernel. You need to check you compiled in all the camera drivers correctly.
<teythoon>
but I don't know which ones are required
<kbingham>
You might also need to make sure you're using a kernel that has any required support ... I don't know if all the support is in mainline yet - so "just run debian" depends on what debian do.
<teythoon>
steev: well i started from 6.12.6, lemme retry with 6.12.8...
<Jasper[m]>
spawacz: psref.lenovo.com with the full type number on the bottom of your device
<Jasper[m]>
Otherwise... touch it?
<steev>
well, touching it won't do anything if I2C_HID_OF_ELAN isn't a module or built in
srinik has quit [Ping timeout: 480 seconds]
<teythoon>
steev: I built 6.12.9 with your config, can access /dev/udmabuf, cam -l lists no camera
<steev>
that is... odd
<steev>
maybe you don't have one?
<steev>
(it's a joke)
<teythoon>
i'm also having trouble looking up the model on psref.lenovo.com
<teythoon>
sticker on the back says MTM: 21BYS0E500
<teythoon>
web site says no results found
<steev>
pretty sure there are a few people here with a 21BY
<steev>
can you pastebin the dmesg output?
<Jasper[m]>
@teythoon start with 21BY, click on the product page and them under the tab with the list of models, you should be able to look for your number.
<Jasper[m]>
steev: Won't be correct
<steev>
Jasper[m]: i just want to see his output
<Jasper[m]>
Oh for the camera? mb
<Jasper[m]>
I know dmesg plops machine type in there, I meant to say that was going to be incorrect
<steev>
yeah, no :) i don't care what efi reports it is :)
<steev>
if you didn't copy it to /boot/efi/ then likely not using it or adding it at the grub prompt via something like `devicetree /usr/lib/linux-image-6.12.9/qcom/sc8280xp-lenovo-thinkpad-x13s.dtb` in grub
<teythoon>
didn't do anything with a dtb thereafter
<steev>
i prefer the latter, especially when testing a new kernel
<steev>
i say grub prompt, but i mean hitting `e` at the grub menu
<steev>
and adding that device.... line at the bottom
<teythoon>
hmyeah that's not gonna fly with my luks drive...
<teythoon>
promising...
srinik has quit [Ping timeout: 480 seconds]
<teythoon>
cam -l lists a camera now
<steev>
ayy
<steev>
yeah, you need to put the dtb somewhere it can be loaded then :)
<teythoon>
the installation instructions suggested to put it onto the efi partition
<teythoon>
and i guess that is where it is picked up from
<teythoon>
i didn't see any explicit devicetree instructions in the grub.cfg
<steev>
yeah
<steev>
it'll be picked up if you copy the new one there
<steev>
there isn't in upstream grub, but it's available as a command
<steev>
ubuntu patches their grub to put it in automagically for their users
<teythoon>
the camera does work now, thanks for all the handholding :)
<steev>
awesome :) glad you got it sorted, the dtb thing will need to be done any time you upgrade your kernel
<teythoon>
cause the devices move around in the address space..?
<steev>
no, in case some new support comes in, or changes in the dts
<teythoon>
hmm
<steev>
e.g. if qualcomm ever submits the venus firmware and johan's patches for it can go into the tree
<steev>
you'd then need the related dts changes for the device
<teythoon>
Jasper[m]: btw, i had a closer look on the lenovo page, and while i see some models with the 21BY prefix, mine isn't listed
<teythoon>
(but touching the screen only adds fingerprints to it, it doesn't seem to affect the pointer)
<Jasper[m]>
Looks like it's not listed indeed
<Jasper[m]>
Could be BTO or CTO I guess
<Jasper[m]>
(I guess BTO since mindfactory and idalo sells them)
<teythoon>
not a 100% what bto or cto means, but i bought it as "refurbished", came in a factory sealed package, at a 50% discount
<Jasper[m]>
Business (I think) To Order or Configure To Order
<Jasper[m]>
Basically something businesses can buy a ton of per some default config at reduced rate (for selling or rollout within a company)
<Jasper[m]>
Configure To Order is basically whatever configurator you use on Lenovo.com
<Jasper[m]>
They're different configs to the point they can't list them all on psref so they just slap a generic CTO/BTO label onto them
<steev>
teythoon: it won't move the pointer
<teythoon>
will xev pick it up?
<steev>
but assuming you're using the config i sent, you should have i2c_hid_of_elan loaded
<steev>
that, i don't know, i am using gnome as my desktop and it works as an input there
<teythoon>
that module is loaded
<JensGlathe[m]>
then you should see lines in dmesg for the touchscreen
<steev>
i can tap on apps for example, and it acts as if i moved the cursor there and clicked on it
<steev>
dmesg| grep -i touchsc
<steev>
[ 3.106090] input: ekth5015m 04F3:2FE6 Touchscreen as /devices/platform/soc@0/9c0000.geniqup/990000.i2c/i2c-4/4-0010/0018:04F3:2FE6.0003/input/input6
<teythoon>
i don't see that
<teythoon>
so i guess my screen is not of the touchy variety
<teythoon>
good progress today, thanks for all the help!
<steev>
it may not be - some options don't have it (mine wasn't supposed to, but they initially shipped me the wrong machine altogether (a t14 intel))
mbuhl has quit [Remote host closed the connection]