Hello all,
Last week I bought myself a new monitor to replace my old 24" monitor.
The new monitor is a Samsung S27C500, which is connected via hdmi. The
monitor has two inputs: one hdmi, and one vga. I do not have a VGA input
on my video card, so I use the hdmi connector. The monitor did not
include a vga-to-dvi adapter.
When replacing my old monitor, i used the the aticonfig utility to
generate a new xorg.conf as I've done in the past, and while the monitor
was usable, I am stuck with a problem where the screen size is limited
to about the size of my old 24" monitor, with black space surrounding
the entire usable screen.
If I send an ctrl+alt+f2 to switch to tty2, I am able to use the
entirety of the monitor, which tells me that this is an issue somewhere
in X. I dug into the documentation for X, and found that the
"DisplaySize" option in xorg.conf can be used to dictate size of a
monitor, but that unfortunately did not resolve my issues either.
I've dug deep, and tried the following, all of which did not resolve the
problem:
1) Configured DisplaySize in xorg.conf
2) Used parse-edid (from read-edid pkg) to read the monitor config &
used it's output to adjust my MONITOR section in xorg.conf
3) `xrandr --prop` displays the incorrect dimensions for the monitor,
shouldn't those details be overrode by my ScreenSize declaration?
4) I've restarted gdm3 many times - could gdm3 be caching an old
xorg.conf?
Links to my configs:
xrandr --prop: http://paste2.org/m8gpIbss
xorg.conf: http://paste2.org/hmIJVWJ0 (monitor block comes from
parse-edid)
xorg.0.log: http://paste2.org/GXNpZpB3
lspci block for video card: http://paste2.org/KLNPJnvn
I notice two things in my xorg.0.log:
[254760.941] (II) fglrx(0): Using hsync ranges from config file
[254760.941] (II) fglrx(0): Using vrefresh ranges from config file
It does not note that it is using ScreenSize from the config file -
could this value be getting ignored? I am not receiving any parse errors
when starting gdm3
Debian wheezy 7.5, 3.2.0-4-amd64, xorg 1:7.7+3~deb7u1, Beta ATI
proprietary driver because the stable one would not work.
I do believe I have tried everything, but maybe there's a tiny piece to
this puzzle that I'm missing. I haven't gone to a linux support group
for help in some years, as I like to try and hack out problems myself,
but I've run out of options and everything I've read hasn't helped yet.
I appreciate any help any of you are able to toss my way.
Thanks a bunch!
--
Love,
Mike Bailey
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/c3df2247b406e7ed53c3a602c1159...@0day4hax.com
