Issue #2853 has been updated by arc...@b1t.name.
File Xorg.vesa.log added
One more funny thing. When I switch driver to VESA it reads EDID from monitor
correctly even under DragonFly:
Bug #2853: kms/radeon/Xorg (?) don't know, devices are detected
Issue #2853 has been updated by arc...@b1t.name.
File dmesg.cl added
I tried substituting EDID via firmware from dports/sysutils/devedid-data and my
monitor works well. On the other hand sysutils/edid-decode reports problems
with my monitor edid:
EDID block does NOT conform to EDID 1.3!
Issue #2853 has been updated by arc...@b1t.name.
Tried with Calculate Linux 15 (kernel 3.18.20) - everything works ok. I'll
attach dmesg when I find another thumb drive.
Bug #2853: kms/radeon/Xorg (?) don't know, devices are detected differently as
Issue #2853 has been updated by ftigeot.
Some versions of these distros could fit the bill:
http://distrowatch.com/search.php?pkg=linux=3.18=InAny#pkgsearch
Bug #2853: kms/radeon/Xorg (?) don't know, devices are detected differently as
under freebsd
Issue #2853 has been updated by arc...@b1t.name.
File dmesg.dfly added
Attached full dmesg with drm.debug=1.
Any pointers to a linux distro with 3.18?
Bug #2853: kms/radeon/Xorg (?) don't know, devices are detected differently as
under freebsd
Issue #2853 has been updated by ftigeot.
Updating to master will allow you to force the use of a specific EDID block but
it won't allow your monitor to be detected by itself.
As far as I know, the FreeBSD version you tested is partly based on Linux 3.8
and DragonFly on Linux 3.18.
It would be
Issue #2853 has been updated by arc...@b1t.name.
FreeBSD 10-STABLE like 2/3 days old (minor patches for threads/swap/-O3 for
everything), DragonFly master like 2 days old, already retested after recent
EDID commit.
Bug #2853: kms/radeon/Xorg (?) don't
