Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I can't disable fuzzy format match #1047

Closed
ghost opened this issue Sep 29, 2018 · 11 comments
Closed

I can't disable fuzzy format match #1047

ghost opened this issue Sep 29, 2018 · 11 comments

Comments

@ghost
Copy link

ghost commented Sep 29, 2018

I've edited /boot/config.txt and added this line:
avoid_edid_fuzzy_match=1
But edidparser still promts: Enabling fuzzy format match...
Raspberry selects lower resolution, because it has higher mhz

@popcornmix
Copy link
Contributor

avoid_edid_fuzzy_match was removed from firmware in August 2012 so it will have no effect.

You'll need to post your edid and explain what hdmi mode you are getting and what mode you think you should get.

@ghost
Copy link
Author

ghost commented Oct 1, 2018

@popcornmix any ideas?

@popcornmix
Copy link
Contributor

The actual edid.dat file would be more useful. Can you upload to a hosting site (e.g. dropbox/google drive) and provide a link.

@ghost
Copy link
Author

ghost commented Oct 1, 2018

@popcornmix https://drive.google.com/file/d/1uOqMulmqXOxtB5jygvyidwwEzrjZew-M/view?usp=sharing - edid.dat
Actually, I don't want to fix problem in my current case. I want to do something like avoid_edid_fuzzy_match=1, i want to fix it globally - Raspberry Pi select the best resolution and fps, no matter what is the pixel clock

@popcornmix
Copy link
Contributor

I posted in #1046 the basic rules used for choosing the default resolution. I think the reason DMT51 is chosen over DMT82 is 51 is listed in the standard timings and 82 is not.
That is considered a preference by the monitor for those listed resolutions.

@ghost
Copy link
Author

ghost commented Oct 1, 2018

@popcornmix so can I do something to prevent this behavior?
I prefer this algorithm:

  1. Get all available modes from edid
  2. Select the ones with the biggest resolution
  3. Select the one with the best framerate (fps)

@popcornmix
Copy link
Contributor

That's not generally desired. Highest resolution is not necessarily best.
A monitor that is natively (i.e. has this many physical pixels) 1360x768 may support 1920x1080 but will provide a sharper image at its native resolution.

@ghost
Copy link
Author

ghost commented Oct 2, 2018

@popcornmix if I connect my Pi to the same monitor but HDMI-HDMI, Pi selects 1920x1080. But there are black borders, that can be disabled by disable_overscan=1.

@popcornmix
Copy link
Contributor

Yes - DVI connection prefers DMT modes.
HDMI connection prefers CEA modes. 1600x1200 isn't a standard CEA mode.

@JamesH65
Copy link
Contributor

JamesH65 commented Jan 9, 2019

@zervankoru I believe that your questions have been answered, can this issue be closed?

@ghost
Copy link
Author

ghost commented Jan 12, 2019

Yea

@ghost ghost closed this as completed Jan 12, 2019
@raspberrypi raspberrypi deleted a comment Jan 25, 2023
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants