You are not logged in.
Pages: 1
I have 24" 1920x1080 LCD. It works great on DVI, but when I change to HDMI the image quality is very poor (looks blurry, like if low resolution was setup). In LCD information menu I see it gets 1920x1080p 60Hz signal.
More than that, image doesn't fit to the screen, it's zoomed in - mouse cursor doesn't "see" the edges. I fixed that by changing LCD option "image size" from 16:9 to "auto" - even quality got a little better.
A part of xrand output:
HDMI2 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 160mm x 90mm
1920x1080 60.0*+ 50.0
I don't like this: 160mm x 90mm. It's obviously wrong. Can I do something about it?
Thanks for any help.
Extra: how do I enable the screen:
xrandr --output HDMI2 --auto --left-of HDMI1
Offline
If you are using an AMD card, plug the DVI-to-HDMI adapter into your graphics card (in a retail box it should have been included) and then use the HDMI port from that to the monitor. "Underscan" is the setting that fixes it without using the adapter but even then there is image degradation. Using the adapter gives good results however.
Offline
lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09)
I have one VGA, one DVI and one HDMI. One DVI is taken, so I need to use HDMI for the second display.
I cannot enable underscan:
xrandr --output HDMI2 --auto --left-of HDMI1 --set underscan on
X Error of failed request: BadName (named color or font does not exist)
Major opcode of failed request: 140 (RANDR)
Minor opcode of failed request: 11 (RRQueryOutputProperty)
Serial number of failed request: 38
Current serial number in output stream: 38
Offline
I have the same problem. The same physical screen size is reported by xrandr, but I have a 55" tv screen!
Before yesterday's updates it worked perfectly. Both Gnome and the nvidia driver got updated.
I have tried various tweaks to the nvidia xorg settings, but without luck so far. Is there perhaps an EDID error?
I want to use the HDMI port...
Last edited by conchyliferous (2013-10-15 16:01:12)
Offline
I tried to use --dpi. In theory it should force correct setup even if xrandr sees wrong screen size. But it doesn't help.
So I use VGA. It works good, but the quality is not satisfying - still a lot better than HDMI.
Offline
We can rule out any Nvidia-related problem. I got the exact same error at my office computer, where I have a:
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)
System is fully updated.
What do you think, Gnome or Xorg bug?
Offline
It's definitely related to HDMI, on my office computer (with the Intel gfx) I replaced the HDMI cable with a DVI cable.
The problem disappeared, Gnome shows my monitor as 24" instead of 7". And xrandr gives the correct physical size (not 160mm x 90mm).
I would guess this is a HDMI related Xorg bug (due to xrandr output).
Last edited by conchyliferous (2013-10-17 06:45:01)
Offline
I think I found the main source of the problem:
cat /var/log/Xorg.0.log | grep -A5 "EDID for output HDMI2"
[ 6.920] (II) intel(0): EDID for output HDMI2
[ 6.920] (II) intel(0): Manufacturer: SAM Model: 5cd Serial#: 1280455220
[ 6.920] (II) intel(0): Year: 2010 Week: 24
[ 6.920] (II) intel(0): EDID Version: 1.3
[ 6.920] (II) intel(0): Digital Display Input
[ 6.920] (II) intel(0): Indeterminate output size
The healthy one looks like this:
cat /var/log/Xorg.0.log | grep -A5 "EDID for output HDMI1"
[ 6.830] (II) intel(0): EDID for output HDMI1
[ 6.830] (II) intel(0): Manufacturer: DEL Model: 4072 Serial#: 1110455628
[ 6.830] (II) intel(0): Year: 2013 Week: 5
[ 6.830] (II) intel(0): EDID Version: 1.3
[ 6.830] (II) intel(0): Digital Display Input
[ 6.830] (II) intel(0): Max Image Size [cm]: horiz.: 51 vert.: 29
(my DVI is detected as HDMI1, and my HDMI as HDMI2)
Is there a way to manually set this "output size"?
Offline
Here is a workaround for a very similar problem back in 2010.
http://ubuntuforums.org/showthread.php?t=1461839
Perhaps that could work here? Since I use DVI as a workaround for now, I will not test it. I'll wait until the bug is fixed.
Offline
Pages: 1