Wrong Resolution Detected

mravatarish · June 29, 2024 at 10:47 PM

Hello! I'm running LibreELEC on an old laptop with a Pentium processor, connected to my receiver through a USB-C hub over HDMI. After following the instructions on the wiki/forum for creating/updating the edid info and sysconfig files I was able to get it to display only on the external display.

The issue I am facing is that it seems the OS is only recognizing up to 1280x800p. This is the same on another USB-C dock as well (included edid update), and I have also completely reinstalled and re-set up LibreELEC from scratch.

With Windows installed on the device I was able to get a 4K resolution on my TV with the same set up, so I'd love to try to get this working here too! Any help would be greatly appreciated, thanks!

Logs:https://paste.libreelec.tv/resolved-anteater.log

**chewitt** · June 30, 2024 at 6:20 AM

I'd guess the USB-C dock advertises 'monitor' capabilities not AVR/TV capabilities. If you connect direct to the receiver over HDMI do you get the normal resolutions?

**mglae** · June 30, 2024 at 9:40 AM

Code

 APPEND boot=UUID=2C69-D520 disk=UUID=6f40d61e-1655-4716-85d8-2e5ab914d778  quiet initrd=/edid.cpio drm.edid_firmware=edid/edid.bin video=DP-1:D Video=eDP-1=d

Kernel parameters are case sensitive use video=eDP-1=d and check eDP-1 dis-connectivity afterwards, must not:

Code

========== kmsprint ==========
Connector 0 (95) eDP-1 (connected)

mravatarish · June 30, 2024 at 8:39 PM

Quote from chewitt

I'd guess the USB-C dock advertises 'monitor' capabilities not AVR/TV capabilities. If you connect direct to the receiver over HDMI do you get the normal resolutions?

There’s a built in display that’s like ~1200p, but unfortunately there’s no hdmi out. I’m using the hub for power, Ethernet, and hdmi as the device only has usbc.

Quote from mglae
Code
 APPEND boot=UUID=2C69-D520 disk=UUID=6f40d61e-1655-4716-85d8-2e5ab914d778  quiet initrd=/edid.cpio drm.edid_firmware=edid/edid.bin video=DP-1:D Video=eDP-1=d
Kernel parameters are case sensitive use video=eDP-1=d and check eDP-1 dis-connectivity afterwards, must not:
Code
========== kmsprint ==========
Connector 0 (95) eDP-1 (connected)

My main issue is the resolution on the external display. I was able to blank the primary internal display. I made this update to see if that changed anything but the issue persists.

Thinking about it, I’m not sure if this dock specifically calls out Linux as a compatible OS so this may be a driver/hardware compatibility issue too.

**mglae** · July 1, 2024 at 5:20 PM

A few thoughts:

a) As long you are testing remove the getedid config from your append line. You will never see a change in resolutions with this static config. But keep disabling eDP-1.

b) IWD is spamming the journal. In worst case disable WIFI before reboot to create a meaningful boot log.

c) Activate debug logging in Kodi (before reboot too).

mravatarish · July 1, 2024 at 6:36 PM

Quote from mglae

A few thoughts:
a) As long you are testing remove the getedid config from your append line. You will never see a change in resolutions with this static config. But keep disabling eDP-1.
b) IWD is spamming the journal. In worst case disable WIFI before reboot to create a meaningful boot log.
c) Activate debug logging in Kodi (before reboot too).

a) I'm not too familiar here, it sounds like you're asking to have this section removed correct?

Code

initrd=/edid.cpio drm.edid_firmware=edid/edid.bin

b/c) I will turn wifi off and enable debug logging when I get back, and upload the logs after! Thank you!

**mglae** · July 1, 2024 at 10:40 PM

Quote from mravatarish

a) I'm not too familiar here, it sounds like you're asking to have this section removed correct?

Just do getedid delete. Afterwards correct the eDP-1 parameter to video=eDP-1:d (unfortunately I have not "seen" this before).

mravatarish · July 2, 2024 at 2:07 AM

Alright!

I ran getedid delete and it said "you did not use this script to create the custom EDID Therefore we can't be sure the script is working properly. Exiting", and after rebooting nothing changed. (Maybe the real issue is I messed up creating

the custom edid?[I just tried to run through the instructions on the wiki real quick but no change])

For gits and shiggles I removed the "intrid=/edid.../edid.bin" part from the APPEND line in syslinux.cfg, leaving "video=DP-1:D Video=eDP-1=d" and after rebooting it blanked my external display and showed on its internal display. After adding the part back to the APPEND line it switched back to the external display.

Anyway, I turned off WIFI and enabled debug logging :): https://paste.libreelec.tv/welcome-panther.log

**mglae** · July 2, 2024 at 5:05 PM

Again: please generate a log with the APPEND (even you don't get a picture):

Code

APPEND boot=UUID=2C69-D520 disk=UUID=6f40d61e-1655-4716-85d8-2e5ab914d778  quiet video=eDP-1:d

Note: video=eDP-1:d instead of Video=eDP-1=d

mravatarish · July 3, 2024 at 11:06 PM

Sorry for the late response! Bad things are happening after updating the append line to what you said (I miss understood). The device boots and outputs a garbled video and goes in and out, I can make out some of the UI but not much (see attached), but it outputs on the external display (intended)!

Here are the logs: https://paste.libreelec.tv/sweet-bat.log

**mglae** · July 4, 2024 at 6:53 PM

When having garbled video it is always worth testing with a different HDMI cable and/or without the AVR.

Please always post a kodi debug log. You can hide the debug OSD with:

Code: /storage/.kodi/userdata/advancedsettings.xml

<advancedsettings version="1.0">
<loglevel>1</loglevel> 
</advancedsettings>

mravatarish · July 4, 2024 at 11:14 PM

My bad! Here are two sets of logs.

Original set up (Dock>AVR>TV): https://paste.libreelec.tv/pumped-sunfish.log

Here I get the same garbled output.

Connected with a brand new (but tested) HDMI cable directly to the TV: https://paste.libreelec.tv/immortal-arachnid.log

Here I get no output at all on the TV, and no sound from the AVR (w/ eARC), but I can connect via SSH.

Edit: Typo

**mglae** · July 5, 2024 at 7:44 PM

Both logs are looking good. You are getting additional modes when directly connected to the TV, e.g. 1080p 50/60Hz.

You can try LE12 Generic-legacy with the X11 graphics stack or LE13 nightly with a more recent kernel and mesa.

They can be tested from USB stick using boot mode run but you always have to add the video=eDP-1:d parameter to avoid the notebook cloning mode.

mravatarish · July 6, 2024 at 12:55 AM

After running the generic-legacy LE12 it worked perfectly! Kodi even recognized both displays, and successfully recognized the correct resolution. Ended up installing and recovering my back up and all is good. Thank you so much for all the help!!

**mglae** · July 6, 2024 at 9:23 AM

Great.

Please post a final log for my education.

mravatarish · July 10, 2024 at 12:31 AM

Here are the logs after installing: https://paste.libreelec.tv/big-monster.log

**mglae** · July 10, 2024 at 4:48 PM

Thanks for your effort, but no Kodi Debug Log and iwd is spamming the journal.

Wrong Resolution Detected

Similar Threads

Intel x86 Wrong Resolution Detected, Ignoring Config File?