ChanServ changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630)
echanude has quit [Quit: WeeChat 3.6]
falk689 has quit [Remote host closed the connection]
falk689 has joined #aarch64-laptops
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
alfredo has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
alfredo1 has joined #aarch64-laptops
alfredo has quit [Ping timeout: 482 seconds]
alfredo1 is now known as alfredo
srinik has quit [Killed (NickServ (Too many failed password attempts.))]
srinik has joined #aarch64-laptops
alfredo has quit [Remote host closed the connection]
alfredo has joined #aarch64-laptops
alfredo has quit [Quit: alfredo]
<danielt> Can anyone offer some clues on the getting the GPU running on Thinkpad X13s. I've seen the success photos but can't replicate them. Initially I got the black screen discussed yesterday... but I switched to a less modular kernel (based on johan_defconfig). That does at least boot but I get messages saying it couldn't power up the GPU.
<danielt> If anyone can compare my logs to known working (or just share some known working info about kernel config or firmware) that would be awesome!
alfredo has joined #aarch64-laptops
<juergh[m]> danielt: maybe this?
<juergh[m]> [ 16.956974] panel-simple-dp-aux aux-aea0000.displayport-controller: Couldn't identify panel via EDID
<juergh[m]> [ 17.219386] panel-simple-dp-aux aux-aea0000.displayport-controller: Unknown panel BOE 0x0a84, using conservative timings
<juergh[m]> jhovold: still puzzled. I can't seem to replicate the black screen anymore. different question: how can I prevent the early console switch so that the initramfs console is actually usable?
alfredo has quit [Quit: alfredo]
<jhovold> juergh[m]: you need to include the display deps in the initramfs, see the commit adding johan_defconfig for details
<jhovold> this is specifically needed to prevent regulator core from disabling seemingly unused regulators after 30 s
<jhovold> juergh[m]: that "Unknown panel" warning should be benign, but you can add the panel timings to the driver to suppress the warning
<jhovold> danielt: bamse found another bug related to the msm drm driver late component bind failure ("probe deferral") which you may need when enabling the GPU unless you make sure to load (and bind) the panel driver before the drm driver
<danielt> juergh: Could be (although I think that's probably just the USB-C dock failing to come up on the boot I captured... and it also fails for me without the dock plugged in). Overall I don't know what "good" boot with GPU looks like so I'm not sure what to compare against. If you have one you are willing to share that would be useful.
<danielt> jhovold: Thanks. I'll take a look at that.
<juergh[m]> jhovold: I'm aware of the initrd modules requirement. but my question is is it not possible to prevent the console switch and stay on the fb console? not sure if that make sense, don't know much about graphics.
<jhovold> juergh[m]: you'd currently need to mark the corresponding regulators as always-on in the DT if you want them to stay on when no driver has claimed them
<jhovold> there's been some talk about addressing this similar to how we handle interconnects, that is, to keep the regulators on until all drivers are bound
<jhovold> but there's no such support in mainline currently
<juergh[m]> ok. thanks for the elaboration.
echanude has joined #aarch64-laptops
tomeu has quit [Quit: The Lounge -]
alfredo has joined #aarch64-laptops
neggles has joined #aarch64-laptops
svarbanov_ has joined #aarch64-laptops
svarbanov has quit [Ping timeout: 480 seconds]
alfredo has quit [Quit: alfredo]
<HdkR> danielt: I used this branch for the GPU working pictures
<danielt> HdkR: Thanks. I'll take a look over the weekend. After help from jhovold the GPU looks OK in the logs but hasn't come to life to that should help me figure out what I overlooked!
<danielt> s/life to/life so/
<steev> if you don't have the mesa stuff, that's likely it
<bamse> ndec: fwiw, changing bt address dynamically works fine...
<steev> i suppose we could set one in the dt, or maybe we could do something like the rtc and store it in nvmem?
<bamse> steev: the default one works fine...until you have more than one device with the default one...
<steev> i'd rather have one that starts with winstrom's oui at least
<bamse> steev: it's stored somewhere...
<steev> i was thinking lenovofprdata but that's probably the fingerprint data... maybe in one of the lenovo* variables, like maybe lenovowolinfo
<clover[m]> steev: is wayland/mutter still borked even with gpu for external display?
<steev> yes
<clover[m]> rip
<steev> bamse: possibly lBoot0014
<clover[m]> have you noticed better battery life with gpu?
<steev> i haven't used it closely enough yet to see
<steev> i wanna say yes because i went to sleep with it suspended, and woke up with it not dead
<steev> and it wasn't at 100% when i suspended it
alfredo has joined #aarch64-laptops
hexdump0815 has quit [Quit: WeeChat 1.9.1]
hexdump0815 has joined #aarch64-laptops
alfredo has quit [Quit: alfredo]
<steev> huh
<steev> didn't get the frame reassembly timeout on 20230210 next
<rfs613> steev: maybe some elves came in overnight and tightened all the screws to manufacturer spec? :P
<steev> it's probably a fluke of the boot :)
iivanov has quit [Ping timeout: 480 seconds]