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
<craftyguy>
nice, thanks for trying it. I was about to but was in the process of saving work elsewhere juuuuust in case 😅
chrisl has quit [Ping timeout: 480 seconds]
* craftyguy
tries....
bionade24 has quit [Read error: Connection reset by peer]
bionade24 has joined #aarch64-laptops
<steev>
luckily, all our stuff is open source, so i can just re-clone after rebuilding :D
<craftyguy>
neato, the update worked for me too
<craftyguy>
ya "saving work elsewhere" is adding commits and pushing heh
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<steev>
definitely handy! thanks for pointing that out!
phire_ has joined #aarch64-laptops
phire is now known as Guest15835
phire_ is now known as phire
Guest15835 has quit [Ping timeout: 480 seconds]
<freekurt[m]>
Wait, how do I upgrade the firmware on my x13s without windows? Run that 2 year old script?
tobhe_ has joined #aarch64-laptops
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
tobhe has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
<robclark>
fwupd apparently
<robclark>
I hope that also works on newer things
<steev>
freekurt[m]: i downloaded the exe from lenovo's website, ran `innoextract n3huj22w.exe`, then ran the 2 commands in the link that craftyguy asked about - `fwupdmgr get-devices 2>/dev/null| grep -A 1 "System Firmware"` and then `sudo fwupdtool install-blob 'code$GetExtractPath$/Rfs/Fw/N3HET92W/\$0AN3H00.FL1' b3f2723a04671a24bdf2d087cf9da60dcf5cb886` (where b3f2723.... was the device id that is spit out by the get-devices command
<steev>
could probably pretty it up and awk to only print the device id
<dgilmore>
b3f2723a04671a24bdf2d087cf9da60dcf5cb886 is probably the device id on all x13s's
<craftyguy>
Maybe, but this doesn't seem like a good time to make assumptions if it could mean bricking something 😅
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<steev>
true
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
GAODA has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<JensGlathe[m]>
rc6 seems better at suspend/resume
<JeromedeBretagne[m]>
alexVinarskis: Thanks a lot for the feedback! Jens Glathe: also told me that the display seems to be using GPIO 3 (instead of 25), now I understand why from the ACPI dumps. I quickly tested it late yesterday, now I don't have the following error message anymore:
<JeromedeBretagne[m]>
```panel-simple-dp-aux aux-aea0000.displayport-controller: Couldn't power on panel to ID it; using conservative timings: -110 ```
<JeromedeBretagne[m]>
What do you mean by "no gpios node listed" ?
<alexVinarskis[m]>
Pmics with gpios have pmicName_gpios node in dtsi definition. 0th pmic for your platform doesn't. I checked, on Zenbook with x1p there are also x2 pmicgpios defined for display, one seems to not exist (or is something else?) as well, 2nd is enable gpio for the panel.
<JeromedeBretagne[m]>
I'm planning to switch into drm.debug mode to see what's going on, as some other Surface displays need a quirk or 2, or some explicit parameters like link-frequencies
<alexVinarskis[m]>
So no error, but still no image i assume? Did you try adding enable gpio for the panel as per my example? Or you could try to set it with gpioset for the test
<JensGlathe[m]>
The dsdt provided displays have 2 lanes defined (eDP1.2), for 2880x1920 I would either expect HBR (810MHz link speed) or more lanes
<alexVinarskis[m]>
jdb: you may also try reading panel's EDID from linux, eg. via cat /sys/class/drm/card1-eDP-1/edid | edid-decode to confirm that it is indeed powered on.
<JeromedeBretagne[m]>
I don't see the edid file nor the eDP-1 directory yet in /sys/ . I can only see the `card1-DP-[12]` and the edid for my external monitor on the bottom UBS-C port (the only one working for video out so far)
<JeromedeBretagne[m]>
Not having `card1-eDP-1` necessarily means that it is not powered on?
<JensGlathe[m]>
I had the same effect with the newer panel-edp. Maybe it is anothe enable gpio required
<alexVinarskis[m]>
Could be. Jdb: is that with pmicgpio as panel enable gpio as well or just with vreg enable gpio3?
<JeromedeBretagne[m]>
Now, I'm on the go for work so my next tests will be later today
<JeromedeBretagne[m]>
alexVinarskis: About your suggestion "Did you try adding enable gpio for the panel as per my example?", do you know if some other devicetrees have it as a reference example? I would need to add it into the `display` node? It doesn't seem very common
ravikant_ has joined #aarch64-laptops
<JensGlathe[m]>
The x1e ones have these, for example T14s (oled)
ravikant__ has joined #aarch64-laptops
<JensGlathe[m]>
But probably the PMICGPIO needs to be decoded first
<JeromedeBretagne[m]>
Ok, I will have a look at this one, thanks for the pointer Jens!
martiert_ has joined #aarch64-laptops
martiert_work has quit [Ping timeout: 480 seconds]