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
<SpieringsAE>
fun, that ps185hdm chip has GPIO that can be configured for the manufacturer in the firmware
<SpieringsAE>
"Hot plug events are normally routed through the DP_HPD pin but, as noted above, itβs possible that the motherboard manufacturer asked for this to be replicated on the GPIO pin."
<SpieringsAE>
This makes it sound to me like the chip is alive when I read the hotplug event
<anthony25>
I thought it was working in Chromium, if I remember correctly it was listing hw decoding for x264 (when applying the iris patch in the kernel)
srinik has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
srinik has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
<robclark>
maybe some distros are already enabling the build flag?
<anthony25>
I'll double check, it was in tumbleweed
<anthony25>
maybe it was enabled to get hw decoding in raspberry pi
laine has joined #aarch64-laptops
<kuruczgy[m]>
Does anyone have working dp altmode on the slim 7x with Johan's new -rc4 branch? I get the "failed to write conn_status_0: -6" error, so apparently that's some polarity issue?
<jhovold>
kuruczgy[m]: just change reset gpios so be GPIO_ACTIVE_LOW
<jhovold>
same issue JensGlathe[m] had with the devkit
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<Jasper[m]>
Mediamarkt is selling a book4 edge with purwa for 499β¬
<tobhe_>
that seems pretty cheap
<Jasper[m]>
I agree
<Jasper[m]>
But it's purwa
<Jasper[m]>
And UFS
<tobhe_>
cheapest I see on the website is 819
<Jasper[m]>
The Dutch one, apologies
chrisl has joined #aarch64-laptops
<tobhe_>
found it. ufs is a bummer but the price is still pretty decent
<steev>
wait is purwa good or bad?
<tobhe_>
less powerful
<steev>
oh good
<steev>
i thought it was the other way around
<tobhe_>
X Plus X1P-42-100
<tobhe_>
Hamoa is the big one
<steev>
i got the x1e not x1p thinkpad
<JensGlathe[m]>
Purwa workd fine, only no GPU driver yet. GPU is X1-45. And its pretty new-ish re dtb
<steev>
2 more weeks, give or take, and i can focus on my t14s
<JensGlathe[m]>
But performance is good, 8 core
<tobhe_>
Toetsenbordindeling says qwert, I wonder if it is actually ansi like the stock photo...
<tobhe_>
*qwerty
<Jasper[m]>
tobhe_: If they did properly localize then yes
<Jasper[m]>
We switched from ISO to ANSI some time ago, but because we're outliers in that regard, most companies don't bother shipping ANSI keyboards in NL
<Jasper[m]>
@tobhe_ I looked p the actual typenumber, it's ISO
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
enyalios_ has joined #aarch64-laptops
teadaniel[m] has joined #aarch64-laptops
enyalios has quit [Ping timeout: 480 seconds]
<teadaniel[m]>
I just got a Vivobook 15 S X1P and am interested in installing any flavor of Linux.
<JensGlathe[m]>
Actually, the image will boot, and you get a usable box (as far as x1p42100 is supported yet). Installing locally on nvme is a PITA, yes.
chrisl has quit [Ping timeout: 480 seconds]
<JensGlathe[m]>
Support will merge eventually into the normal Concept X1E image.
<KieranBingham[m]>
(I am/was running fedora rawhide)
<KieranBingham[m]>
Other than it rebooted to do the update (and hasn't come up again) I don't know what the update was supposed to include :-(
<anthony25>
Can you use the previous kernel, and most importantly I think, the previous dtb?
<KieranBingham[m]>
No none of the kernel entries are working. I'll see if I can override the dtb from command line.
<KieranBingham[m]>
Can't get the latest fedora image to boot from usb either, neither f41 or rawhide but Ubuntu's image is booting ... Which makes it tempting to just reinstall with Ubuntu... But I'll see if I can dig into what happened here first
<steev>
commandline flags?
<robclark>
KieranBingham[m]: double check the cmdline didn't loose the dtb= bit? A week or two back a f41 broke booting for me, and I realized that all the boot loader entries were regenerated (and lost dtb= clk_ignore_unused, etc)
<KieranBingham[m]>
Still have clk_ignore_unused etc, but I wasn't previously booting with a dtb option on command line, just relying on it losing from the efi partition
<robclark>
next step would be earlycon=efi
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
nairda has quit [Quit: Connection closed for inactivity]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<kuruczgy[m]>
jhovold: Thanks, that definitely helps.
<kuruczgy[m]>
Unfortunately dp altmote still seems to have regressed in jhovold/wip/x1e80100-6.14-rc4 (compared to jhovold/wip/x1e80100-6.14-rc2), now only 1 out of the 3 ports work, instead of the 2 previously (they fail with link training errors).
<kuruczgy[m]>
jhovold: do you have any guess for which commit could be the culprit? I saw that there are now patches to add LTTPR transparent mode support, I was hoping that that would improve the link training issues. Is fixing those still in the "we need someone with an oscilloscope to look at it" territory?