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
rz_ has joined #aarch64-laptops
rz has quit [Ping timeout: 480 seconds]
laine_ has quit [Quit: (╯°□°)╯︵ ┻━┻]
rz has joined #aarch64-laptops
rz_ has quit [Ping timeout: 480 seconds]
rz has quit [Remote host closed the connection]
rz has joined #aarch64-laptops
<bamse>
d0pefish: on the reference design both spi0 and spi1 looks to be i2c buses...
<bamse>
d0pefish: if you read the ACPI DSDT you might have better luck figuring out which serial engines are used on your device, then adjust the index of those (0-indexed vs 1-indexed iirc) and you can try to enable the relevant node(s) in devicetree
<bamse>
d0pefish: iirc we have ~24 serial engines on the x1e, each one can be programmed (by early boot) to talk things like uart, i2c, spi, spi-hid etc...and/or be disabled/made unaccessible to linux
rz_ has joined #aarch64-laptops
rz has quit [Ping timeout: 480 seconds]
rz has joined #aarch64-laptops
rz_ has quit [Ping timeout: 480 seconds]
tobhe_ has joined #aarch64-laptops
tobhe has quit [Ping timeout: 480 seconds]
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
<dgilmore>
on my t14s I have to run "echo 0-0010 > /sys/bus/i2c/drivers/i2c_hid_of/bind" to get the touchscreen working
<dgilmore>
something similiar has been fixed on the x13s for awhile now
ungeskriptet_ has joined #aarch64-laptops
ungeskriptet has quit [Ping timeout: 480 seconds]
<steev>
dgilmore: on the x13s, it's the elan driver
<steev>
dgilmore: my t14s doesn't have touch though, i hope, i ordered the one that shouldn't be
<albsen[m]>
Got my first blue screen on the t14s 64gb (limited to 32gb) with the current Ubuntu kernel
<JensGlathe[m]>
That reminds me
<JensGlathe[m]>
Linux tb16-jg 6.14.0-5-qcom-x1e #6
<JensGlathe[m]>
built yesterday with the config/annotations from 6.14.0-5. WiFi and BT are working
<JensGlathe[m]>
I rebased jhovold 's wip/x1e80100-6.14-rc3 tree and mine on it. Probably more like 6.14-rc1(?) but with all the Ubuntu-Concept sstuff like Iris
<albsen[m]>
that actually took 2 days, my guess is that it has something to do with memory pressure. when the machine gets busy it's more likely to crash, will see if I can find more info
<JensGlathe[m]>
I had my devkit slowly stall at 6.13-8 while building new kernel. First, new ssh wasn't coming up. Then the build process slowly ground to a halt.
<tobhe_>
use with caution, don't destroy your hardware :)
almuerto has quit [Quit: Konversation terminated!]
<dgilmore>
Cheers
<dgilmore>
I have linux-firmware-20250211-1.fc42.noarch installed and the right configs. something is missing. but its not critical. will dig more later
<jhovold>
I haven't linked to either the ucm or topology file from the wiki since they are work-in-progress, and we don't have any speaker protection in place
<jhovold>
I'll add a comment about they being needed at least
<jhovold>
and this is the patch (series) that fixed the touchscreen on the x13s:
<jhovold>
first time I hear that it's not working on the the t14s, but I guess not many people use it
fossdd has quit [Ping timeout: 480 seconds]
almuerto has joined #aarch64-laptops
almuerto has quit [Quit: Konversation terminated!]
<dgilmore>
jhovold: I'll just wait on the audio. Was just poking at what was listed as working. I am probably odd in that I got pretty much all the options.
Mary has quit [Quit: .]
Mary has joined #aarch64-laptops
jhovold has quit [Ping timeout: 480 seconds]
fossdd has joined #aarch64-laptops
icecream95 has joined #aarch64-laptops
Caterpillar has quit [Quit: Konversation terminated!]
srinik has joined #aarch64-laptops
d0pefish3 has joined #aarch64-laptops
d0pefish has quit [Read error: Connection reset by peer]