| 1 |
john <jdm@××××××××××××.uk> wrote: |
| 2 |
|
| 3 |
> On Tue, 29 Dec 2015 11:05:12 +0200 |
| 4 |
> Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
| 5 |
> |
| 6 |
> > On 29/12/2015 11:01, Mick wrote: |
| 7 |
> > > On Tuesday 29 Dec 2015 02:00:33 wabenbau@×××××.com wrote: |
| 8 |
> > > |
| 9 |
> > >> There is a kernel option DRM_LOAD_EDID_FIRMWARE. It allows you to |
| 10 |
> > >> specify an EDID data set instead of probing for it. If your |
| 11 |
> > >> problem is caused by broken EDID data, this option maybe will |
| 12 |
> > >> help you to run the monitor at its full resolution. |
| 13 |
> > >> |
| 14 |
> > >> -- |
| 15 |
> > >> Regards |
| 16 |
> > >> wabe |
| 17 |
> > > |
| 18 |
> > > How would you know what to specify for EDID data, unless the |
| 19 |
> > > monitor told you what it is? |
| 20 |
> > > |
| 21 |
> > |
| 22 |
> > or if the monitor manufacturer told you what it should be |
| 23 |
> > |
| 24 |
> > /alanm |
| 25 |
> > |
| 26 |
> |
| 27 |
> I have had a play with that but no success yet. I have followed the |
| 28 |
> howto but no success yet but I think now I will have to find .bin file |
| 29 |
> or settings from manufacturer. |
| 30 |
|
| 31 |
Maybe you can somehow extract it (hexedit?) from the windows monitor |
| 32 |
driver that was probably delivered with the monitor. |
| 33 |
|
| 34 |
After I installed the driver for the LG monitor, I was able to use it |
| 35 |
at full resolution under windows. So I think that the EDID data (or |
| 36 |
something equivalent) was included in the driver. |
| 37 |
|
| 38 |
I never used that kernel option. So I can't tell you more. |
| 39 |
|
| 40 |
-- |
| 41 |
Regards |
| 42 |
wabe |
Archives