> > Gerhard Magnus wrote:
> > > > > My old CRT monitor burned out and I've
> > replaced it with a ViewSonic
> > > > > VG2030WM, which has a resolution of 1680 X
> > 1050 @ 60Hz. Kudzu (or
> > > > > whatever configures new hardware) set it to
> > 1280 X 1024 & 60Hz, which
> > > > > works fine, although everything is a little
> > larger than I want. The
> > > > > monitor model isn't listed in
> > system-config-display so I've set this to
> > > > > the generic "LCD Panel 1680 X 1050". But when
> > under "Display Settings"
> > > > > I set the resolution to 1680 X 1050, the next
> > time I try logging in or
> > > > > rebooting the monitor hangs the system.
> > Exactly how I get around this
> > > > > isn't clear -- sometimes the system goes back
> > to 1280 X 1024 after
> > > > > several attempts to reboot, and once I got the
> > screen back by starting
> > > > > to type something at the command line login
> > prompt that appears briefly
> > > > > before X starts.
> >
> > On Sun, 2007-07-08 at 12:22 -0700, Antonio Olivares
> > wrote:
> Reboot and press e to edit when grub starts up and
> enter into level 3 (non-gui). Try to configure
> xorg.conf by Xorg. Login as root user
>
> type
> # Xorg -configure
> and then test the X configuration and the mouse should
> appear at the middle (press ctrl+alt+backspace) to get
> back to the terminal.
>
> copy it over to /etc/X11/
> # cp /root/xorg.conf.new /etc/X11/xorg.conf
> replace existing xorg.conf? Select yes
> and try to login by typing
> # startx
> Does it give you 1680x1050? If it does not, then
> check the
> Lines with
> HorizSync 24.0 - 92.0
> VertRefresh 50.0 - 85.0
> and the modes in the bottom and put in the lines to
> all Depths from the beginning till the end.
>
> SubSection "Display"
> Viewport 0 0
> Depth 15
> Modes "1680 X 1050" "1280x1024"
> "1152x864" "1024x768"
> "832x624" "800x600" "720x400" "640x480"
>
> Configuring this to the maximum resolution is
> sometimes a pain. This should not happen as Fedora
> should do this out of the box with minimal problems.
> But different hardware and not enough testing with
> more hardware, issues like this arise as a result of
> that.
My new xorg.conf was generated by Xorg -configure. I added the
HorizSync, VertRefresh and Option lines and changed the Identifier,
VendorName and ModelName entries in the "Monitor" section. In the
"Screen" section I changed the "Monitor" entry and added a "Modes" line
to each of the "Display" subsections. Here's the new xorg.conf:
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
RgbPath "/usr/share/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
FontPath "unix/:7100"
FontPath "built-ins"
EndSection
Section "Module"
Load "extmod"
Load "dbe"
Load "record"
Load "xtrap"
Load "vnc"
Load "glx"
Load "dri"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "ViewSonic"
VendorName "ViewSonic"
ModelName "VG2030wm"
HorizSync 24.0 - 92.0
VertRefresh 50.0 - 85.0
Option "dpms"
EndSection
Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
#Option "NoAccel" # [<bool>]
#Option "SWcursor" # [<bool>]
#Option "ColorKey" # <i>
#Option "CacheLines" # <i>
#Option "Dac6Bit" # [<bool>]
#Option "DRI" # [<bool>]
#Option "NoDDC" # [<bool>]
#Option "ShowCache" # [<bool>]
#Option "XvMCSurfaces" # <i>
#Option "PageFlip" # [<bool>]
Identifier "Card0"
Driver "intel"
VendorName "Intel Corporation"
BoardName "82915G/GV/910GL Express Chipset Family Graphics
Controller"
BusID "PCI:0:2:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "ViewSonic"
SubSection "Display"
Viewport 0 0
Depth 1
Modes "1680 X 1050" "1280x1024" "1152x864" "1024x768"
"832x624" "800x600" "720x400" "640x480"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
Modes "1680 X 1050" "1280x1024" "1152x864" "1024x768"
"832x624" "800x600" "720x400" "640x480"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
Modes "1680 X 1050" "1280x1024" "1152x864" "1024x768"
"832x624" "800x600" "720x400" "640x480"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
Modes "1680 X 1050" "1280x1024" "1152x864" "1024x768"
"832x624" "800x600" "720x400" "640x480"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
Modes "1680 X 1050" "1280x1024" "1152x864" "1024x768"
"832x624" "800x600" "720x400" "640x480"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1680 X 1050" "1280x1024" "1152x864" "1024x768"
"832x624" "800x600" "720x400" "640x480"
EndSubSection
EndSection
I can now logon successfully without getting the monitor error message:
Out of Range
H.Frequency 93 KHZ
V.Frequency 87 Hz
But I'm still stuck in the 1280 X 1024 resolution. When I try to change
this using /usr/bin/system-config-display I get these error messages:
root@PuteB Mon Jul 09 15:43:00
[576] /home/magnusg $ Traceback (most recent call last):
File "/usr/share/system-config-display/xconf.py", line 311, in ?
hardware_state = XF86HardwareState(xconfig)
File "/usr/lib/python2.4/site-packages/rhpxl/xhwstate.py", line 177,
in __init__
self.init_from_xconfig(xconfig)
File "/usr/lib/python2.4/site-packages/rhpxl/xhwstate.py", line 296,
in init_from_xconfig
self.all_resolutions.sort (compare_resolution)
File "/usr/lib/python2.4/site-packages/rhpxl/xhwstate.py", line 60, in
compare_resolution
(w1, h1) = resolution_from_string(res1)
File "/usr/lib/python2.4/site-packages/rhpxl/xhwstate.py", line 49, in
resolution_from_string
(w, h) = string.split (res, "x")
ValueError: need more than 1 value to unpack
These results are the same regardless if I comment out any combination
of the HorizSync, VertRefresh and Option lines of the "Monitor" section
in xorg.conf.
Regards, Jerry
