05:36 <alexVinarskis[m]> jdb: you don't need any magic with on off, simply change in your patch pin 3 to pin 36. It says active high, so regulator control will handle it for you such that it will go high to turn on, and will go low to turn off.

08:27 <efenex> returning to my own question from yesterday, i built custom kernel and initrd, replaced them in the snapdragon concept ubuntu iso using livefs-edit, attempted to boot it on the zenbook a14 and end up with the following output "EFI stub: Booting linux kernel... Loaded initrd from LINUX_EFI_INITRD_MEDIA_GRUB device path. Measured initrd data into PCR 9. Generating empty DTB. Exiting boot

08:27 <efenex> services..."

08:28 <efenex> i assume the "generating empty dtb" is the biggest clue here and I should be also copying some dtb files into the installer iso context to get it to boot?

12:49 <JeromedeBretagne[m]> Latest arcata update: the display is now recognized with gpio36, I can get and decode the edid from /sys/class/drm/card0-eDP-1/edid !

12:49 <JeromedeBretagne[m]> Here is the corresponding patch:

12:49 <JeromedeBretagne[m]> https://github.com/JeromeDeBretagne/linux_surface_pro_9_5G/commit/013ca6ecadd522a7f48b729653a312ff1a52d280

12:50 <JeromedeBretagne[m]> Jens Glathe: alexVinarskis: I've put you both with a `Co-developed by:` tag if that's ok with you

12:51 <JeromedeBretagne[m]> Here is the EDID read from Linux:

12:51 <JeromedeBretagne[m]> https://gist.github.com/JeromeDeBretagne/dd084beb9f8cdc3d6856fff2d231368d

12:53 <JeromedeBretagne[m]> Now, I need to get the panel-edp module working, here is the current dmesg output, I'll need to enable some debug levels:

12:53 <JeromedeBretagne[m]> https://gist.github.com/JeromeDeBretagne/a4e2e7d0b589aeef2c01f2d9d6504261

12:55 <alexVinarskis[m]> But you have the picture too, right?

12:55 <JeromedeBretagne[m]> not yet, no

12:56 <JeromedeBretagne[m]> I've used `drive-strength = <2>;` by comparing with other TLMMGPIO btw

12:56 <JeromedeBretagne[m]> no reason to be sad, I've never been so close :-)

12:58 <alexVinarskis[m]> Conservative timings warning is normal, need to add panel to driver and set timings, LGD panels work with edp-panel. You typically shouldve have image even without it, so its probably something else. But you can edp-panel driver, and set timings eg. as some other L G D panels.

12:59 <JeromedeBretagne[m]> these are my next steps indeed, certainly later today or tomorrow

13:08 <JeromedeBretagne[m]> I get a Call trace: line, that doesn't look normal:

13:08 <JeromedeBretagne[m]> https://gist.github.com/JeromeDeBretagne/8434c73dbdbfa2e8d5d9cdab61f8cdbd

15:11 <JensGlathe[m]> jdb: the last line says `Unknown panel LGD 0x06b2, using conservative timings` which is normal for undefined panels. The splat disappears when the panel is in the list for L G D panels.

16:06 <freekurt[m]> Is this bad?

16:08 <freekurt[m]> Was I supposed to run this command while running linux on a USB stick?

16:25 <freekurt[m]> Ok, seems like the bios firmware has been upgraded just fine and those warnings weren't anything important.

16:31 <travmurav[m]> did it try to update display edid or what xD

16:32 <JensGlathe[m]> panel firmware?

16:37 <freekurt[m]> i had an external monitor plugged in. i assume it was something related to that.

17:14 <steev> i've never seen that message, but i don't use external monitor at the moment

17:14 <steev> would be curious if someone else sees that while its trying to write the bios update, but glad it worked for you as well!

17:48 <freekurt[m]> Speaking of the external monitor, I am experiencing a regression on recent kernels where the external monitor doesn't wake back up after suspend, but Ubuntu thinks it is still connected. Disconnecting the external monitor results in a shutdown.

19:15 <freekurt[m]> It seems like maybe this is only happening when resuming from Automatic Suspend. When I manually suspend the external monitor wakes back up.

20:58 <alexVinarskis[m]> jdb: does Gnome now recognize internal display and correct resolution in settings? If yes, try backing up and then wiping ~/. config/monitors.xml*. Then reboot without external display attached. Sometimes im also getting (external) screens detected but no image, wiping this config helps. This would reset userland monitor settings eg. Layout/order/resolution...

21:00 <JeromedeBretagne[m]> alexVinarskis: I can't get Gnome to display anything, so I'm continuing my investigations remotely from ssh...

21:01 <alexVinarskis[m]> Ohh, i thought you said the external display works. Well, can wipe that file anyway then, nothing to loose.

21:02 <JeromedeBretagne[m]> It does, but when I try to get the built-in display enabled, I get in a very weird situation where the external one is not usable anymore

21:03 <JeromedeBretagne[m]> I can still see the cursor but it is in a weird state so I can't login (or I don't understand what's going on)

21:03 <JeromedeBretagne[m]> the issue is that I have a 4K external display and I think it doesn't help the situation (with only 2 lanes being supported)

21:10 <JeromedeBretagne[m]> thanks for the tip, I will give it a try !

21:13 <alexVinarskis[m]> 4k shouldn't matter, 2lanes can do 30hz in hbr2 (default) and 60hz if u specified link frequencies to include 8.1gbps/hbr3.

21:25 <HdkR> Interestingly my three 4k panels don't support 4k30 so they end up needing to drop down to 1080

21:27 <JeromedeBretagne[m]> I've borrowed another external screen, it powers up and I can login into Gnome

21:27 <JeromedeBretagne[m]> Now, I need to find the kbd shortcut to move windows to this external screen

21:28 <JeromedeBretagne[m]> as the built-in one is the default, so everthing happens there

21:36 <alexVinarskis[m]> HdkR: good know, haven't seen that issue luckily. Have you tried enabling HBR3?

21:37 <JeromedeBretagne[m]> ok, I made some improvements, by reconnecting this other external display

21:38 <JeromedeBretagne[m]> I can confirm that Gnome properly detects the resolution and refresh rate now

21:38 <HdkR> alexVinarskis[m]: Haven't tried on the X1E since last time I couldn't get DP-alt mode working at all

21:38 <JeromedeBretagne[m]> 2880 x 1920, by default it was at 120Hz, I've switched it to 60Hz, but still a black screen

21:39 <alexVinarskis[m]> jdb: nice! Did you try deleting that config file and rebooting now?

21:39 <alexVinarskis[m]> HdkR: you need adsp firmware loaded for alt mode notifications to work, perhaps it was missing?

21:39 <JeromedeBretagne[m]> not yet, I've struggled to get there so I'm playing a little bit

21:41 <HdkR> alexVinarskis[m]: I think I have all the firmwares but it's been a while since I've looked at it

21:41 <JeromedeBretagne[m]> I've tried to disable the built-in screen from the Gnome settings, it was applied (but nothing visible on the actual display, I can still control the backlight while it is disabled)

21:42 <JeromedeBretagne[m]> now trying to reenable it, Gnome settings can't change its state back to enable anymore

21:55 <kuruczgy[m]> I also managed to get the camera working on the slim7x. The physical kill switch doesn't do anything and the recording led does not turn on, so... very secure :D

21:55 <kuruczgy[m]> It's only green in low light, with proper lighting the colors seem fine. So I don't think the debayering pattern is broken, it probably just needs some parameters tweaked. (E.g. the green pixels might be more sensitive?)

21:56 <JeromedeBretagne[m]> btw, I've patched panel-edp.c so that I don't get the error message anymore, now I have the following lines via dmesg:... (full message at <https://matrix.org/oftc/media/v1/media/download/AYuVkvkyIQqcIDu4coy787JhJhxS7kOfe7rPofYDMmrN784M7S1v7J6YtzvVFRnxHCHx68BBj9ppp1OEmrodvRdCeXKFh3lAAG1hdHJpeC5vcmcvR1NmRmh1RmFnR1FldW5GUVdDUURUV2ZT>)

21:57 <JeromedeBretagne[m]> and I don't know what these lines mean:... (full message at <https://matrix.org/oftc/media/v1/media/download/AVKigVTlSeqLu1Fxi6duPeusxjmWJ702urZTocxBZS0eLk8fLDtdV79-SgJYyHcPra8Hq2-UU5cwDwDjj4teaqFCeXKFl8UQAG1hdHJpeC5vcmcva3NRUXNMVUlCRHBEc0dlcWt6cERaTmdV>)

21:59 <alexVinarskis[m]> jdb: its a known issue, switching resolution/framerate/on/off may break it... but deleting ~/.config/monitors.xml will make it forget it was disabled. 1 Dmesgs looks good now. 2nd one not sure tbh... perhaps someone else knows. Not getting them on x1p

22:00 <JeromedeBretagne[m]> otherwise, I don't see a single error message in dmesg

22:05 <alexVinarskis[m]> kuruczgy: afaik de-greening is to be improved in libcameraisp, but I may recall it wrong. Indicator is indeed a funny one... locally I patched ov02c10 to set/unset LED on stream start/stop, but it seems its not a desired solution as its too device specific + sensor itsled does not have LED output, so the binding would be lying. Issue with defining LED as LED/gpio and create a camera trigger or something is that anyone with

22:05 <alexVinarskis[m]> root access can overwrite LED state from trigger XYZ to off state... sure you still need root access, but otherwise its pretty useless privacy feature. If gpio for LED would be passed to camera driver, disabling it would've require recompiling (and re-signing) the module, which would make it more USB camera like (root access alone isn't enough to disable LED indicator), or unloading the module, which will disable both the LED

22:05 <alexVinarskis[m]> and the camera.

22:06 <JeromedeBretagne[m]> I can see a weird flash when the panel is tentatively being enabled, as if the backlight was blinking on the bottom side of the display

22:07 <JeromedeBretagne[m]> I have tried to delete ~/.config/monitors.xml , still the same

22:08 <JeromedeBretagne[m]> I will look at the various settings offered for other edp panels next I think

22:11 <JeromedeBretagne[m]> and one last info, I see the built-in efifb console getting off very quickly during the initial boot messages, I don't know if there could be an interaction with something else that switches the built-in panel somehow

22:16 <alexVinarskis[m]> Maybe try running kmscube directly?

22:20 <JeromedeBretagne[m]> I see the weird flashing of the backlight at the bottom of the screen when I try kmscube directly

22:21 <JeromedeBretagne[m]> and it ends with : failed to set mode: Invalid argument

22:25 <JeromedeBretagne[m]> enough for today, quite some progress already!

23:57 <nirik> humf. Finally had time again to fire up my slim7x... but I can't seem to get wireless on the recent kernels. I thought it might be the firmware issue ( https://bugzilla.redhat.com/show_bug.cgi?id=2365882 ) but even downgrading doesn't seem to help. Odd. On the plus side display/etc all come up fine now with the stock fedora rawhide kernel...

23:58 <anthony25> that is strange, I have the slim 7x, and downgrading the firmware made it work

23:58 <anthony25> on which linux-firmware release did you downgrade?

23:59 <anthony25> and the firmware might be included in your initramfs, have you tried rebuilding your initramfs after downgrading the firmware?