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
chrisl has quit [Ping timeout: 480 seconds]
weirdtreething_ has joined #aarch64-laptops
weirdtreething has quit [Ping timeout: 480 seconds]
weirdtreething_ is now known as weirdtreething
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
weirdtreething_ has joined #aarch64-laptops
weirdtreething has quit [Ping timeout: 480 seconds]
weirdtreething_ is now known as weirdtreething
shdhs[m] has joined #aarch64-laptops
shdhs[m] has quit [autokilled: This host has violated network policy. Mail support@oftc.net if you feel this is in error. (2025-03-07 02:02:11)]
ungeskriptet_ has quit [Ping timeout: 480 seconds]
unsaidMoonshine has quit [Remote host closed the connection]
unsaidMoonshine has joined #aarch64-laptops
unsaidMoonshine has quit [Remote host closed the connection]
unsaidMoonshine has joined #aarch64-laptops
pabs has quit [Remote host closed the connection]
pabs has joined #aarch64-laptops
<steev>
my problem is i don't know what triggers it so, i'll be running it here, but since applying it, at least in the last 2 hours, nothing
<JensGlathe[m]>
With iwd on 6.14 I haven't seen it yet
<jhovold>
we need craftyguy to test it, since he's the only one who has a decent reproducer it seems
<jhovold>
that said, that patch looks like a bit of a hack... even if it may paper over the bug
<JensGlathe[m]>
currently rebuilding as 6.14.0-17-jg-3, based on jhovold's 6.14-rc5 and merged into Ubuntu-Concept 6.14.0-17, so its essentially Ubuntu-Concept on 6.14-rc5
<JensGlathe[m]>
I can fire up my EL2 wdk, was a reliable reproducer of this the last year
<jhovold>
just make sure you still hit this (and determine how often since I believe you said it was "only" a couple of times a day), before applying and testing the patch
<jhovold>
to make sure nothing else is currently masking it, I mean
<JensGlathe[m]>
will try first.
<steev>
at my sister's place, i was able to hit it every time i came out of suspend
<steev>
unfortunately, i won't be there til ~monday
Dantheman825[m] has joined #aarch64-laptops
<Dantheman825[m]>
is it possible to boot into an SSD through USB on the X13s? I hear it required some boot parameters to make it work
<steev>
like an ssd attached via usb? or using a usb as boot and ssd as root?
<Dantheman825[m]>
the former
<jhovold>
steev: wasn't that with her previous AP?
<steev>
no, it's with her new one :)
<Dantheman825[m]>
the cursed idea I had was to move the laptop SSD into an external USB enclosure so I could poke around with the exposed M.2 PCIe slot
<steev>
i specifically could not hit it with the old one
<jhovold>
ah, ok, good
<Dantheman825[m]>
I would sacrifice the wireless card, but I believe Lenovo vendor-locked it, so you can post without it
<Dantheman825[m]>
* you can't post
<steev>
you could always pop it off, see if it still boots, and then pop it back in if it doesn't. i don't think they'd make it so you can't post if the wifi card is broken/missing
<wizzard>
> currently rebuilding as 6.14.0-17-jg-3, based on jhovold's 6.14-rc5 and merged into Ubuntu-Concept 6.14.0-17, so its essentially Ubuntu-Concept on 6.14-rc5
<wizzard>
Which kernel patches does Ubuntu-Concept 6.14.0-17 have which jhovolds 6.14-rc5 does not have?
<wizzard>
I am asking since I am trying to find out why alt-dp does not work on my 6.14-rc5 postmarketos install.
<JensGlathe[m]>
X13s is quite tolerant re loading of adsp and VBUS on type-c as it seems. I can't remember having the issues with it I have seen on other devices. Since the available other options are limited (internal nvme only), that's good. You could probably make it more reliable by having a self-powered hub for the USB SSD.
green has quit [Quit: Konversation terminated!]
green has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
ungeskriptet has quit [Remote host closed the connection]
green has quit [Quit: Konversation terminated!]
ungeskriptet has joined #aarch64-laptops
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #aarch64-laptops
green has joined #aarch64-laptops
green has quit [Quit: Konversation terminated!]
<Dantheman825[m]>
Having a more stationary hub for it would probably be nice
<Dantheman825[m]>
The goal is to jerryrig a graphics card into the open M.2 slot now. But time will tell what troubles await me there
srinik has quit [Remote host closed the connection]
todi1 has joined #aarch64-laptops
todi has quit [Ping timeout: 480 seconds]
srinik has joined #aarch64-laptops
ektor52 has joined #aarch64-laptops
ektor5 has quit [Ping timeout: 480 seconds]
<bryanodonoghue>
anybody willing to do some highly experimental debug on t14s hardware ?
<bryanodonoghue>
No schematics for slim7x but my guess is its the same sensor setup
<bryanodonoghue>
There's a pretty good chance TBH
chrisl has joined #aarch64-laptops
<anthony25>
so if I rebase your patches on top of jhovold's kernel, enable "CONFIG_VIDEO_OV02C10=m", the camera should show up in v4l?
<anthony25>
(and change the dts for the slim 7x)
chrisl has quit [Ping timeout: 480 seconds]
<bryanodonoghue>
with the dts that would be the hope
<bryanodonoghue>
anthon25 yep
<bryanodonoghue>
Lenovo pretty much followed the qcom example for the t14s per schematics
<bryanodonoghue>
different sensor
<bryanodonoghue>
so...
<bryanodonoghue>
its possible they changed things up significantly on slim7x
<bryanodonoghue>
but unlikely
<bryanodonoghue>
caveat/warning this won't all just work on the first go
<bryanodonoghue>
new sensor driver, first time dts
<bryanodonoghue>
if we can find the sensor at the expected address that's a huge win
SpieringsAE has quit [Quit: SpieringsAE]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
ektor52 has quit []
<steev>
there is a new efi firmware for the thinkpad t14s, but i only see it on the website, not the vantage software, and oddly, despite the website saying 2.16, it installs 2.17
<robclark>
macc24: I don't have windows so I'm not getting any automatic updates.. should I skip this one or any useful fixes?
green has quit [Quit: Konversation terminated!]
<anthony25>
the webcam doesn't seem to work, this is what Cheese is giving me: https://bpa.st/CLHQ
<macc24>
robclark: i don't know
<robclark>
ok.. I guess I skip it for now
<anthony25>
bryanodonoghue: this is my patch for the slim 7x dts: https://bpa.st/E4AA
weirdtreething has joined #aarch64-laptops
<robclark>
Hmm, this is weird, I rebooted after to install f41 updates and now some keys on my kb don't work (including ones I need to login)
<robclark>
and now it starts working properly again.. confused
<robclark>
Seems related to "Need keyval or commitString" msgs in journal from gnome-shell
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
green has joined #aarch64-laptops
green has quit [Quit: Konversation terminated!]
f_ is now known as funderscore
funderscore is now known as f_
f_ is now known as funderscore
<steev>
definitely hit whatever it is, since the patch added this - `[ 632.187036] ath11k_pci 0006:01:00.0: rxed invalid length (nbytes 0, max 2048)` but unlike the other thing, it doesn't seem to be spamming the logs
<bryanodonoghue>
anthony25
<bryanodonoghue>
dmesg | grep -e camss -e cci -e ov02c
<bryanodonoghue>
and either
<bryanodonoghue>
apt install libcamera-tools
<bryanodonoghue>
yay/pacman same thing
<bryanodonoghue>
then cam -l
<bryanodonoghue>
if you can
<bryanodonoghue>
v appreciated
<bryanodonoghue>
btw your dts patch looks spot on
<anthony25>
I do that in 30min or so
<anthony25>
maybe I forgot a patch to apply, there was quite a lot :p