I originally set up this monitor with an analogue lead. Everything seemed fine, so I didn't check xorg.conf at all. Then I bought a digital lead, and since then the monitor blinks. Running system-config-display identifies it as a 1280 x 1084 CRT monitor. It is an LCD monitor.
That model is not on the drop-down list, so assuming that a specific driver wasn't available for it, I tried telling system-config-display that it is a generic LCD 1280 x 1024 monitor - restarted X, then went back to system-config-display, where it showed up as a CRT monitor.
The refresh rate set was way outside the manufacturer's recommendations (1280 x 1024 @ 60Hz). so I tried manually setting refresh rates to match the manual's recommendations. At the moment my xorg.conf has
### Comment all HorizSync and VertSync values to use DDC: Identifier "Monitor0" ModelName "Monitor 1280x1024" ### Comment all HorizSync and VertSync values to use DDC: HorizSync 60.0 - 72.0 VertRefresh 60.0 - 72.0 Option "dpms" EndSection
Section "Device" Identifier "Videocard0" Driver "nv" EndSection
Section "Screen" Identifier "Screen0" Device "Videocard0" Monitor "Monitor0" DefaultDepth 16 SubSection "Display" Viewport 0 0 Depth 24 EndSubSection SubSection "Display" Viewport 0 0 Depth 16 EndSubSection EndSection
Attached is the relevant part of the specification page. Any advice, please?
Anne
On Feb 18, 2008 12:24 PM, Anne Wilson cannewilson@googlemail.com wrote:
Any advice, please?
I am not an expert, but maybe ...
### Comment all HorizSync and VertSync values to use DDC: Identifier "Monitor0" ModelName "Monitor 1280x1024" ### Comment all HorizSync and VertSync values to use DDC:
^^^^ try what it says above or, from the spec sheet, use
HorizSync 60.0 - 72.0
HorizSync 30 - 82
VertRefresh 60.0 - 72.0
VertRefresh 56 - 75
Option "dpms"EndSection
Section "Device" Identifier "Videocard0" Driver "nv" EndSection
Section "Screen" Identifier "Screen0" Device "Videocard0" Monitor "Monitor0" DefaultDepth 16 SubSection "Display" Viewport 0 0 Depth 24 EndSubSection SubSection "Display" Viewport 0 0 Depth 16 EndSubSection EndSection
HTH, -Bob
On Monday 18 February 2008 18:44, Bob Beers wrote:
### Comment all HorizSync and VertSync values to use DDC: Identifier "Monitor0" ModelName "Monitor 1280x1024" ### Comment all HorizSync and VertSync values to use DDC:
^^^^ try what it says above or
I didn't know what DDC is. After checking it sounded promising, so I tried it. Unfortunately it didn't help.
HorizSync 30 - 82
VertRefresh 60.0 - 72.0
VertRefresh 56 - 75
Tried that as well. It's still blinking.
Anne
On Monday 18 February 2008 12:24, Anne Wilson wrote:
I originally set up this monitor with an analogue lead. Everything seemed fine, so I didn't check xorg.conf at all. Then I bought a digital lead, and since then the monitor blinks. Running system-config-display identifies it as a 1280 x 1084 CRT monitor. It is an LCD monitor.
That model is not on the drop-down list, so assuming that a specific driver wasn't available for it, I tried telling system-config-display that it is a generic LCD 1280 x 1024 monitor - restarted X, then went back to system-config-display, where it showed up as a CRT monitor.
The refresh rate set was way outside the manufacturer's recommendations (1280 x 1024 @ 60Hz). so I tried manually setting refresh rates to match the manual's recommendations. At the moment my xorg.conf has
### Comment all HorizSync and VertSync values to use DDC: Identifier "Monitor0" ModelName "Monitor 1280x1024" ### Comment all HorizSync and VertSync values to use DDC: HorizSync 60.0 - 72.0 VertRefresh 60.0 - 72.0 Option "dpms" EndSection
Section "Device" Identifier "Videocard0" Driver "nv" EndSection
Section "Screen" Identifier "Screen0" Device "Videocard0" Monitor "Monitor0" DefaultDepth 16 SubSection "Display" Viewport 0 0 Depth 24 EndSubSection SubSection "Display" Viewport 0 0 Depth 16 EndSubSection EndSection
Attached is the relevant part of the specification page. Any advice, please?
Anne
Have you tried running system-config-display --reconfig?
The reconfig argument starts with a fresh config file and seems to detect the hardware better.
On Monday 18 February 2008 18:49, Terry Polzin wrote:
Have you tried running system-config-display --reconfig?
The reconfig argument starts with a fresh config file and seems to detect the hardware better.
That writes an xorg.conf with no monitor lines at all, then gives you the option of Generic CRT or Generic LCD. I chose the right resolution f rom the LCD list and re-started X. Unfortunately it's still blinking.
Anne
Anne Wilson wrote:
<snip>
### Comment all HorizSync and VertSync values to use DDC: Identifier "Monitor0" ModelName "Monitor 1280x1024" ### Comment all HorizSync and VertSync values to use DDC: HorizSync 60.0 - 72.0 VertRefresh 60.0 - 72.0 Option "dpms" EndSection
Section "Device" Identifier "Videocard0" Driver "nv" EndSection
Section "Screen" Identifier "Screen0" Device "Videocard0" Monitor "Monitor0" DefaultDepth 16 SubSection "Display" Viewport 0 0 Depth 24 EndSubSection SubSection "Display" Viewport 0 0 Depth 16 EndSubSection EndSection
try this: # ### Comment all HorizSync and VertSync values to use DDC: Identifier "Monitor0" ModelName "Monitor 1280x1024" ### Comment all HorizSync and VertSync values to use DDC: HorizSync 30.0 - 82.0 VertRefresh 56.0 - 75.0 Option "dpms" EndSection
Section "Device" Identifier "Videocard0" Driver "nv" EndSection
Section "Screen" Identifier "Screen0" Device "Videocard0" Monitor "Monitor0" DefaultDepth 16 SubSection "Display" Viewport 0 0 Depth 24 Modes "1280x1024" "1280x960" "1280x800" "1152x864" "1152x768" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Viewport 0 0 Depth 16 Modes "1280x1024" "1280x960" "1280x800" "1152x864" "1152x768" "1024x768" "800x600" "640x480" EndSubSection EndSection #
(the "modes" lines will wrap ... but all the resolutions should be all on one line, separated by spaces and inside quotes)
Also, if "DefaultDepth 16" does not work, try "DefaultDepth 24"
You say that you bought a digital lead ... meaning I guess that you are using a different PORT on your video card and monitor. It is possible that he standard "nv" driver does not support that port on your video card and that you will need to instead download the proprietary drivers from nvidia's website to get that port to function. Regardless of which driver and cable you use, the resolution/freq of the screen is going to be the same ... why not just use the old cable :D
Thanks, Johnny Hughes
On Tuesday 19 February 2008 13:02, Johnny Hughes wrote:
You say that you bought a digital lead ... meaning I guess that you are using a different PORT on your video card and monitor. It is possible that he standard "nv" driver does not support that port on your video card and that you will need to instead download the proprietary drivers from nvidia's website to get that port to function. Regardless of which driver and cable you use, the resolution/freq of the screen is going to be the same ... why not just use the old cable :D
Hi, Johnny. Sorry for the delay in answering, but I was trying to make sure that I had a fair amount of time to work with the server.
Before I read your message I had the bright idea of seeing what knoppix thought about the monitor. The result was surprising. Attached is what it reported. I fed that info into xorg.conf and hoped. Unfortunately I am still seeing the blink from time to time, though.
Maybe you are right about the driver not handling the dvi port correctly. I really didn't want to go down the route of the proprietary drivers, so maybe I will have to go back to the analogue cable.
I will try your version this morning and let you know whether it helps. This is the last ditch. If it doesn't help, I'll change the cable back and re-run system-config-display.
Thanks again
Anne
On Thursday 21 February 2008 09:56, Anne Wilson wrote:
On Tuesday 19 February 2008 13:02, Johnny Hughes wrote:
You say that you bought a digital lead ... meaning I guess that you are using a different PORT on your video card and monitor. It is possible that he standard "nv" driver does not support that port on your video card and that you will need to instead download the proprietary drivers from nvidia's website to get that port to function. Regardless of which driver and cable you use, the resolution/freq of the screen is going to be the same ... why not just use the old cable :D
Hi, Johnny. Sorry for the delay in answering, but I was trying to make sure that I had a fair amount of time to work with the server.
Before I read your message I had the bright idea of seeing what knoppix thought about the monitor. The result was surprising. Attached is what it reported. I fed that info into xorg.conf and hoped. Unfortunately I am still seeing the blink from time to time, though.
Maybe you are right about the driver not handling the dvi port correctly. I really didn't want to go down the route of the proprietary drivers, so maybe I will have to go back to the analogue cable.
I will try your version this morning and let you know whether it helps. This is the last ditch. If it doesn't help, I'll change the cable back and re-run system-config-display.
Comparing your scripts with what I'd actually put into xorg.conf, there were some extra modelins from knoppix, but the only real difference was that I'd put the dri section in. I thought it unlikely that this affect it, but I've taken it out anyway. It still is blinking.
One last thought. I did install a wireless mouse and keyboard at the same time as the dvi cable. I have a feeling that the blinking tends to happen when I move the cursor with the mouse. Is it possible that there is interference from the mouse?
Anne
Anne Wilson wrote:
On Thursday 21 February 2008 09:56, Anne Wilson wrote:
On Tuesday 19 February 2008 13:02, Johnny Hughes wrote:
<snip>
Maybe you are right about the driver not handling the dvi port correctly. I really didn't want to go down the route of the proprietary drivers, so maybe I will have to go back to the analogue cable.
I will try your version this morning and let you know whether it helps. This is the last ditch. If it doesn't help, I'll change the cable back and re-run system-config-display.
Comparing your scripts with what I'd actually put into xorg.conf, there were some extra modelins from knoppix, but the only real difference was that I'd put the dri section in. I thought it unlikely that this affect it, but I've taken it out anyway. It still is blinking.
If knoppix works perfectly and does not ever blink, then I would say it is a problem with the nv Xorg driver in centos-5. If knoppix also sometimes messes up .. still might be a nv driver issue that is common to both OSes.
The proprietary nvidia driver might fix that, it also adds much better 3D performance if you are using that.
The modeline stuff with the CentOS-5 nv driver might also make it work correctly, if we were able to exactly define the 14 modes that I saw the monitor supported from your initial sheet. I have to admit that I am not an expert on constructing these modeline settings, but google probably can explain exactly how to construct them. Found this:
http://xtiming.sourceforge.net
But if the analog cable works OK, that might be the easiest option.
One last thought. I did install a wireless mouse and keyboard at the same time as the dvi cable. I have a feeling that the blinking tends to happen when I move the cursor with the mouse. Is it possible that there is interference from the mouse?
I have never heard of this happening before, but it would be theoretically possible, though not probable IMHO. If you hook up a normal mouse and it goes away ... maybe so, that should be a fairly easy test.
Thanks, Johnny Hughes
On Thursday 21 February 2008 12:04:48 Johnny Hughes wrote:
Anne Wilson wrote:
On Thursday 21 February 2008 09:56, Anne Wilson wrote:
On Tuesday 19 February 2008 13:02, Johnny Hughes wrote:
<snip>
Maybe you are right about the driver not handling the dvi port correctly. I really didn't want to go down the route of the proprietary drivers, so maybe I will have to go back to the analogue cable.
I will try your version this morning and let you know whether it helps. This is the last ditch. If it doesn't help, I'll change the cable back and re-run system-config-display.
Comparing your scripts with what I'd actually put into xorg.conf, there were some extra modelins from knoppix, but the only real difference was that I'd put the dri section in. I thought it unlikely that this affect it, but I've taken it out anyway. It still is blinking.
If knoppix works perfectly and does not ever blink, then I would say it is a problem with the nv Xorg driver in centos-5. If knoppix also sometimes messes up .. still might be a nv driver issue that is common to both OSes.
The proprietary nvidia driver might fix that, it also adds much better 3D performance if you are using that.
No. 3D doesn't have any attraction for me, so that's not a problem.
The modeline stuff with the CentOS-5 nv driver might also make it work correctly, if we were able to exactly define the 14 modes that I saw the monitor supported from your initial sheet. I have to admit that I am not an expert on constructing these modeline settings, but google probably can explain exactly how to construct them. Found this:
http://xtiming.sourceforge.net
But if the analog cable works OK, that might be the easiest option.
Agreed.
One last thought. I did install a wireless mouse and keyboard at the same time as the dvi cable. I have a feeling that the blinking tends to happen when I move the cursor with the mouse. Is it possible that there is interference from the mouse?
I have never heard of this happening before, but it would be theoretically possible, though not probable IMHO. If you hook up a normal mouse and it goes away ... maybe so, that should be a fairly easy test.
I doubt if it is the culprit. Logic aside, I have watched it carefully while I was working there this morning, and it blinked occasionally when I was not touching either keyboard or mouse. OTOH, it could be a sort of ping to the transmitter, I suppose, but if it were that I'd expect a regular pattern.
I'll try the old PS/2 keyboard and mouse next time I have a longish session with the server. If I get any likely answers I'll let you know. Thanks for the help.
Anne
On Tuesday 19 February 2008 13:02:31 Johnny Hughes wrote:
Anne Wilson wrote:
<snip>
### Comment all HorizSync and VertSync values to use DDC: Identifier "Monitor0" ModelName "Monitor 1280x1024" ### Comment all HorizSync and VertSync values to use DDC: HorizSync 60.0 - 72.0 VertRefresh 60.0 - 72.0 Option "dpms" EndSection
Section "Device" Identifier "Videocard0" Driver "nv" EndSection
Section "Screen" Identifier "Screen0" Device "Videocard0" Monitor "Monitor0" DefaultDepth 16 SubSection "Display" Viewport 0 0 Depth 24 EndSubSection SubSection "Display" Viewport 0 0 Depth 16 EndSubSection EndSection
try this: # ### Comment all HorizSync and VertSync values to use DDC: Identifier "Monitor0" ModelName "Monitor 1280x1024" ### Comment all HorizSync and VertSync values to use DDC: HorizSync 30.0 - 82.0 VertRefresh 56.0 - 75.0 Option "dpms" EndSection
Section "Device" Identifier "Videocard0" Driver "nv" EndSection
Section "Screen" Identifier "Screen0" Device "Videocard0" Monitor "Monitor0" DefaultDepth 16 SubSection "Display" Viewport 0 0 Depth 24 Modes "1280x1024" "1280x960" "1280x800" "1152x864" "1152x768" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Viewport 0 0 Depth 16 Modes "1280x1024" "1280x960" "1280x800" "1152x864" "1152x768" "1024x768" "800x600" "640x480" EndSubSection EndSection #
(the "modes" lines will wrap ... but all the resolutions should be all on one line, separated by spaces and inside quotes)
Also, if "DefaultDepth 16" does not work, try "DefaultDepth 24"
You say that you bought a digital lead ... meaning I guess that you are using a different PORT on your video card and monitor. It is possible that he standard "nv" driver does not support that port on your video card and that you will need to instead download the proprietary drivers from nvidia's website to get that port to function. Regardless of which driver and cable you use, the resolution/freq of the screen is going to be the same ... why not just use the old cable :D
Johnny, this afternoon I got around to putting the old cable back in, only to find that I can't get X correctly configured again. I have no X. I managed to get to a text screen and vi xorg.conf, putting in exactly what you recommended above (maybe that was for digital, not analogue?). I still can't startx. I see
(==) Using config file: "/etc/X11/xorg.conf" (EE) NV(0): No valid initial configuration found (EE) Screen(s) found, but none have a usable configuration.
Fatal server error: no screens found XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining.
Can you recommend a really basic xorg.conf to get me started? Thanks
Anne
On Thu, 2008-02-28 at 19:17 +0000, Anne Wilson wrote:
On Tuesday 19 February 2008 13:02:31 Johnny Hughes wrote:
Anne Wilson wrote:
<snip>
### Comment all HorizSync and VertSync values to use DDC: Identifier "Monitor0" ModelName "Monitor 1280x1024" ### Comment all HorizSync and VertSync values to use DDC: HorizSync 60.0 - 72.0 VertRefresh 60.0 - 72.0 Option "dpms" EndSection
Section "Device" Identifier "Videocard0" Driver "nv" EndSection
Section "Screen" Identifier "Screen0" Device "Videocard0" Monitor "Monitor0" DefaultDepth 16 SubSection "Display" Viewport 0 0 Depth 24 EndSubSection SubSection "Display" Viewport 0 0 Depth 16 EndSubSection EndSection
try this: # ### Comment all HorizSync and VertSync values to use DDC: Identifier "Monitor0" ModelName "Monitor 1280x1024" ### Comment all HorizSync and VertSync values to use DDC: HorizSync 30.0 - 82.0 VertRefresh 56.0 - 75.0 Option "dpms" EndSection
Section "Device" Identifier "Videocard0" Driver "nv" EndSection
Section "Screen" Identifier "Screen0" Device "Videocard0" Monitor "Monitor0" DefaultDepth 16 SubSection "Display" Viewport 0 0 Depth 24 Modes "1280x1024" "1280x960" "1280x800" "1152x864" "1152x768" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Viewport 0 0 Depth 16 Modes "1280x1024" "1280x960" "1280x800" "1152x864" "1152x768" "1024x768" "800x600" "640x480" EndSubSection EndSection #
(the "modes" lines will wrap ... but all the resolutions should be all on one line, separated by spaces and inside quotes)
Also, if "DefaultDepth 16" does not work, try "DefaultDepth 24"
You say that you bought a digital lead ... meaning I guess that you are using a different PORT on your video card and monitor. It is possible that he standard "nv" driver does not support that port on your video card and that you will need to instead download the proprietary drivers from nvidia's website to get that port to function. Regardless of which driver and cable you use, the resolution/freq of the screen is going to be the same ... why not just use the old cable :D
Johnny, this afternoon I got around to putting the old cable back in, only to find that I can't get X correctly configured again. I have no X. I managed to get to a text screen and vi xorg.conf, putting in exactly what you recommended above (maybe that was for digital, not analogue?). I still can't startx. I see
(==) Using config file: "/etc/X11/xorg.conf" (EE) NV(0): No valid initial configuration found (EE) Screen(s) found, but none have a usable configuration.
Fatal server error: no screens found XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining.
Can you recommend a really basic xorg.conf to get me started? Thanks
---- init 3 system-config-display --reconfig
Craig
On Thursday 28 February 2008 19:29:07 Craig White wrote:
On Thu, 2008-02-28 at 19:17 +0000, Anne Wilson wrote:
On Tuesday 19 February 2008 13:02:31 Johnny Hughes wrote:
Anne Wilson wrote:
<snip>
### Comment all HorizSync and VertSync values to use DDC: Identifier "Monitor0" ModelName "Monitor 1280x1024" ### Comment all HorizSync and VertSync values to use DDC: HorizSync 60.0 - 72.0 VertRefresh 60.0 - 72.0 Option "dpms" EndSection
Section "Device" Identifier "Videocard0" Driver "nv" EndSection
Section "Screen" Identifier "Screen0" Device "Videocard0" Monitor "Monitor0" DefaultDepth 16 SubSection "Display" Viewport 0 0 Depth 24 EndSubSection SubSection "Display" Viewport 0 0 Depth 16 EndSubSection EndSection
try this: # ### Comment all HorizSync and VertSync values to use DDC: Identifier "Monitor0" ModelName "Monitor 1280x1024" ### Comment all HorizSync and VertSync values to use DDC: HorizSync 30.0 - 82.0 VertRefresh 56.0 - 75.0 Option "dpms" EndSection
Section "Device" Identifier "Videocard0" Driver "nv" EndSection
Section "Screen" Identifier "Screen0" Device "Videocard0" Monitor "Monitor0" DefaultDepth 16 SubSection "Display" Viewport 0 0 Depth 24 Modes "1280x1024" "1280x960" "1280x800" "1152x864" "1152x768" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Viewport 0 0 Depth 16 Modes "1280x1024" "1280x960" "1280x800" "1152x864" "1152x768" "1024x768" "800x600" "640x480" EndSubSection EndSection #
(the "modes" lines will wrap ... but all the resolutions should be all on one line, separated by spaces and inside quotes)
Also, if "DefaultDepth 16" does not work, try "DefaultDepth 24"
You say that you bought a digital lead ... meaning I guess that you are using a different PORT on your video card and monitor. It is possible that he standard "nv" driver does not support that port on your video card and that you will need to instead download the proprietary drivers from nvidia's website to get that port to function. Regardless of which driver and cable you use, the resolution/freq of the screen is going to be the same ... why not just use the old cable :D
Johnny, this afternoon I got around to putting the old cable back in, only to find that I can't get X correctly configured again. I have no X. I managed to get to a text screen and vi xorg.conf, putting in exactly what you recommended above (maybe that was for digital, not analogue?). I still can't startx. I see
(==) Using config file: "/etc/X11/xorg.conf" (EE) NV(0): No valid initial configuration found (EE) Screen(s) found, but none have a usable configuration.
Fatal server error: no screens found XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining.
Can you recommend a really basic xorg.conf to get me started? Thanks
init 3 system-config-display --reconfig
Couldn't start X server on card 0 Error, failed to start X server
Anne
Anne Wilson wrote:
On Thursday 28 February 2008 19:29:07 Craig White wrote:
On Thu, 2008-02-28 at 19:17 +0000, Anne Wilson wrote:
On Tuesday 19 February 2008 13:02:31 Johnny Hughes wrote:
Anne Wilson wrote:
<snip>
### Comment all HorizSync and VertSync values to use DDC: Identifier "Monitor0" ModelName "Monitor 1280x1024" ### Comment all HorizSync and VertSync values to use DDC: HorizSync 60.0 - 72.0 VertRefresh 60.0 - 72.0 Option "dpms" EndSection
Section "Device" Identifier "Videocard0" Driver "nv" EndSection
Section "Screen" Identifier "Screen0" Device "Videocard0" Monitor "Monitor0" DefaultDepth 16 SubSection "Display" Viewport 0 0 Depth 24 EndSubSection SubSection "Display" Viewport 0 0 Depth 16 EndSubSection EndSection
try this: # ### Comment all HorizSync and VertSync values to use DDC: Identifier "Monitor0" ModelName "Monitor 1280x1024" ### Comment all HorizSync and VertSync values to use DDC: HorizSync 30.0 - 82.0 VertRefresh 56.0 - 75.0 Option "dpms" EndSection
Section "Device" Identifier "Videocard0" Driver "nv" EndSection
Section "Screen" Identifier "Screen0" Device "Videocard0" Monitor "Monitor0" DefaultDepth 16 SubSection "Display" Viewport 0 0 Depth 24 Modes "1280x1024" "1280x960" "1280x800" "1152x864" "1152x768" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Viewport 0 0 Depth 16 Modes "1280x1024" "1280x960" "1280x800" "1152x864" "1152x768" "1024x768" "800x600" "640x480" EndSubSection EndSection #
(the "modes" lines will wrap ... but all the resolutions should be all on one line, separated by spaces and inside quotes)
Also, if "DefaultDepth 16" does not work, try "DefaultDepth 24"
You say that you bought a digital lead ... meaning I guess that you are using a different PORT on your video card and monitor. It is possible that he standard "nv" driver does not support that port on your video card and that you will need to instead download the proprietary drivers from nvidia's website to get that port to function. Regardless of which driver and cable you use, the resolution/freq of the screen is going to be the same ... why not just use the old cable :D
Johnny, this afternoon I got around to putting the old cable back in, only to find that I can't get X correctly configured again. I have no X. I managed to get to a text screen and vi xorg.conf, putting in exactly what you recommended above (maybe that was for digital, not analogue?). I still can't startx. I see
(==) Using config file: "/etc/X11/xorg.conf" (EE) NV(0): No valid initial configuration found (EE) Screen(s) found, but none have a usable configuration.
Fatal server error: no screens found XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining.
Can you recommend a really basic xorg.conf to get me started? Thanks
init 3 system-config-display --reconfig
Couldn't start X server on card 0 Error, failed to start X server
Anne,
Here is a simple Vesa config that should work on most cards and monitors, I use it here at work during kickstart installs.
Section "ServerLayout" Identifier "Default Layout" Screen 0 "Screen0" 0 0 InputDevice "Keyboard0" "CoreKeyboard" EndSection
Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbModel" "pc105" Option "XkbLayout" "us" EndSection
Section "Device" Identifier "Videocard0" Driver "vesa" EndSection
Section "Screen" Identifier "Screen0" Device "Videocard0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 Modes "1280x1024" "1024x768" "800x600" "640x480" EndSubSection EndSection
Cheers,
-Ross
______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.
On Thursday 28 February 2008 20:00:25 Ross S. W. Walker wrote:
Here is a simple Vesa config that should work on most cards and monitors, I use it here at work during kickstart installs.
Section "ServerLayout" Identifier "Default Layout" Screen 0 "Screen0" 0 0 InputDevice "Keyboard0" "CoreKeyboard" EndSection
Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbModel" "pc105" Option "XkbLayout" "us" EndSection
Section "Device" Identifier "Videocard0" Driver "vesa" EndSection
Section "Screen" Identifier "Screen0" Device "Videocard0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 Modes "1280x1024" "1024x768" "800x600" "640x480" EndSubSection EndSection
Hi, Ross. Thanks for that. It got me in, but at a horrid 800x600, so I ran system-config-display, setting it to generic 1280x1024, and leaving the vesa driver. Then I got
"out of range H.Frequency: 75KHZ V.Frequency: 60HZ"
Back into vi, and set the refresh rates, and eureka! I'm back in business. Is it worth trying the nv driver again, or should I leave well alone?
Thanks for the help. That config is going to be printed out for my "Emergencies" file. :-)
Anne
On Thu, 2008-02-28 at 20:31 +0000, Anne Wilson wrote:
On Thursday 28 February 2008 20:00:25 Ross S. W. Walker wrote:
Here is a simple Vesa config that should work on most cards and monitors, I use it here at work during kickstart installs.
Section "ServerLayout" Identifier "Default Layout" Screen 0 "Screen0" 0 0 InputDevice "Keyboard0" "CoreKeyboard" EndSection
Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbModel" "pc105" Option "XkbLayout" "us" EndSection
Section "Device" Identifier "Videocard0" Driver "vesa" EndSection
Section "Screen" Identifier "Screen0" Device "Videocard0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 Modes "1280x1024" "1024x768" "800x600" "640x480" EndSubSection EndSection
Hi, Ross. Thanks for that. It got me in, but at a horrid 800x600, so I ran system-config-display, setting it to generic 1280x1024, and leaving the vesa driver. Then I got
"out of range H.Frequency: 75KHZ V.Frequency: 60HZ"
Back into vi, and set the refresh rates, and eureka! I'm back in business. Is it worth trying the nv driver again, or should I leave well alone?
Thanks for the help. That config is going to be printed out for my "Emergencies" file. :-)
---- I was reluctant to state this because I have no authoritative knowledge on these things but if you change video cables, I think that you need to reboot to get the video chipset to properly recognize the cable/monitor connected.
Craig
On Thursday 28 February 2008 21:23:54 Craig White wrote:
On Thu, 2008-02-28 at 20:31 +0000, Anne Wilson wrote:
On Thursday 28 February 2008 20:00:25 Ross S. W. Walker wrote:
Here is a simple Vesa config that should work on most cards and monitors, I use it here at work during kickstart installs.
Section "ServerLayout" Identifier "Default Layout" Screen 0 "Screen0" 0 0 InputDevice "Keyboard0" "CoreKeyboard" EndSection
Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbModel" "pc105" Option "XkbLayout" "us" EndSection
Section "Device" Identifier "Videocard0" Driver "vesa" EndSection
Section "Screen" Identifier "Screen0" Device "Videocard0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 Modes "1280x1024" "1024x768" "800x600" "640x480" EndSubSection EndSection
Hi, Ross. Thanks for that. It got me in, but at a horrid 800x600, so I ran system-config-display, setting it to generic 1280x1024, and leaving the vesa driver. Then I got
"out of range H.Frequency: 75KHZ V.Frequency: 60HZ"
Back into vi, and set the refresh rates, and eureka! I'm back in business. Is it worth trying the nv driver again, or should I leave well alone?
Thanks for the help. That config is going to be printed out for my "Emergencies" file. :-)
I was reluctant to state this because I have no authoritative knowledge on these things but if you change video cables, I think that you need to reboot to get the video chipset to properly recognize the cable/monitor connected.
I'm pretty sure you do. I had done that, though.
Anne
Anne Wilson wrote:
I was reluctant to state this because I have no authoritative knowledge on these things but if you change video cables, I think that you need to reboot to get the video chipset to properly recognize the cable/monitor connected.
I'm pretty sure you do. I had done that, though.
on VGA, yes, the video controller can only read the "VESA ID" extended format information when its reset, its a horrible mess of a kludge interface as IBM had only alloted like 3 pins for a 1-of-8 model monitor specification back in 1984 or whenever the first VGA was designed. VESA created this very complex dance where the V sync line is used to clock serial data over those pins, and its only read when the monitor sync is stopped for some length of time, then started, the video controllers capture this data and save it so the host can later read it. I forget all the specifics, I had to work with this stuff in the mid 1990s when it was devised.
I /think/ on DVI its a lot better, but I've not actually worked with that at a low level so I can't confirm this from direct experience.
On Thursday 28 February 2008 22:24:08 John R Pierce wrote:
Anne Wilson wrote:
I was reluctant to state this because I have no authoritative knowledge on these things but if you change video cables, I think that you need to reboot to get the video chipset to properly recognize the cable/monitor connected.
I'm pretty sure you do. I had done that, though.
on VGA, yes, the video controller can only read the "VESA ID" extended format information when its reset, its a horrible mess of a kludge interface as IBM had only alloted like 3 pins for a 1-of-8 model monitor specification back in 1984 or whenever the first VGA was designed. VESA created this very complex dance where the V sync line is used to clock serial data over those pins, and its only read when the monitor sync is stopped for some length of time, then started, the video controllers capture this data and save it so the host can later read it. I forget all the specifics, I had to work with this stuff in the mid 1990s when it was devised.
I /think/ on DVI its a lot better, but I've not actually worked with that at a low level so I can't confirm this from direct experience.
My problem was that the monitor blinked, when on DVI. One possible explanation is that the lead is fitting poorly. I don't know the technical details, but you know how these leads have a barrel-shaped thingy that I think is a power-smoother or some such? That is pretty close to the rectangular lead, bot possibly not close enough. I got the feeling that the 'stylish' design of the monitor stand may be pushing it slightly. I don't know whether I can get a lead where it is either shorter or longer at that point.
The other possibility that has been suggested is that the DVI interface on the monitor may be poorly supported on the current kernel. If that's so, it may be cured on later ones.
Both are possibilities that I can test, though not immediately.
Anne
on 2-28-2008 12:31 PM Anne Wilson spake the following:
On Thursday 28 February 2008 20:00:25 Ross S. W. Walker wrote:
Here is a simple Vesa config that should work on most cards and monitors, I use it here at work during kickstart installs.
Section "ServerLayout" Identifier "Default Layout" Screen 0 "Screen0" 0 0 InputDevice "Keyboard0" "CoreKeyboard" EndSection
Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbModel" "pc105" Option "XkbLayout" "us" EndSection
Section "Device" Identifier "Videocard0" Driver "vesa" EndSection
Section "Screen" Identifier "Screen0" Device "Videocard0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 Modes "1280x1024" "1024x768" "800x600" "640x480" EndSubSection EndSection
Hi, Ross. Thanks for that. It got me in, but at a horrid 800x600, so I ran system-config-display, setting it to generic 1280x1024, and leaving the vesa driver. Then I got
"out of range H.Frequency: 75KHZ V.Frequency: 60HZ"
Back into vi, and set the refresh rates, and eureka! I'm back in business. Is it worth trying the nv driver again, or should I leave well alone?
Thanks for the help. That config is going to be printed out for my "Emergencies" file. :-)
Anne
Just save a copy so you can cp it into place in an emergency.
On Thursday 28 February 2008 21:24:02 Scott Silva wrote:
That config is going to be printed out for my "Emergencies" file. :-)
Anne
Just save a copy so you can cp it into place in an emergency.
I'm a "belt, braces (suspenders) and piece-of-string" type :-) It's saved as a file on my laptop, will be copied to the server before I switch off tonight, and it's printed out for my System file. I shouldn't have any trouble finding a copy when I need it next :-)
Anne
Anne Wilson wrote:
On Thursday 28 February 2008 20:00:25 Ross S. W. Walker wrote:
Here is a simple Vesa config that should work on most cards
and monitors,
I use it here at work during kickstart installs.
Section "ServerLayout" Identifier "Default Layout" Screen 0 "Screen0" 0 0 InputDevice "Keyboard0" "CoreKeyboard" EndSection
Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbModel" "pc105" Option "XkbLayout" "us" EndSection
Section "Device" Identifier "Videocard0" Driver "vesa" EndSection
Section "Screen" Identifier "Screen0" Device "Videocard0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 Modes "1280x1024" "1024x768" "800x600" "640x480" EndSubSection EndSection
Hi, Ross. Thanks for that. It got me in, but at a horrid 800x600, so I ran system-config-display, setting it to generic 1280x1024, and leaving the vesa driver. Then I got
"out of range H.Frequency: 75KHZ V.Frequency: 60HZ"
Back into vi, and set the refresh rates, and eureka! I'm back in business. Is it worth trying the nv driver again, or should I leave well alone?
Thanks for the help. That config is going to be printed out for my "Emergencies" file. :-)
I really don't see a real need to use any of the stock drivers that ship with Linux since if you really want to use the acceleration features of the card you need the manufacturer drivers and libraries, so I always default to vesa. Maybe if your card doesn't support vesa (which don't these days?) or want multi-monitor support only you would use a stock driver but that's all I can think of
-Ross
______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.
On Thursday 28 February 2008 21:47:35 Ross S. W. Walker wrote:
Anne Wilson wrote:
On Thursday 28 February 2008 20:00:25 Ross S. W. Walker wrote:
Here is a simple Vesa config that should work on most cards
and monitors,
I use it here at work during kickstart installs.
Section "ServerLayout" Identifier "Default Layout" Screen 0 "Screen0" 0 0 InputDevice "Keyboard0" "CoreKeyboard" EndSection
Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbModel" "pc105" Option "XkbLayout" "us" EndSection
Section "Device" Identifier "Videocard0" Driver "vesa" EndSection
Section "Screen" Identifier "Screen0" Device "Videocard0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 Modes "1280x1024" "1024x768" "800x600" "640x480" EndSubSection EndSection
Hi, Ross. Thanks for that. It got me in, but at a horrid 800x600, so I ran system-config-display, setting it to generic 1280x1024, and leaving the vesa driver. Then I got
"out of range H.Frequency: 75KHZ V.Frequency: 60HZ"
Back into vi, and set the refresh rates, and eureka! I'm back in business. Is it worth trying the nv driver again, or should I leave well alone?
Thanks for the help. That config is going to be printed out for my "Emergencies" file. :-)
I really don't see a real need to use any of the stock drivers that ship with Linux since if you really want to use the acceleration features of the card you need the manufacturer drivers and libraries, so I always default to vesa. Maybe if your card doesn't support vesa (which don't these days?) or want multi-monitor support only you would use a stock driver but that's all I can think of
I've not felt the need for the proprietary drivers, as I don't use any 3D, so you could be right. Maybe I'll stick with this, for now at least.
Thanks again
Anne
-
Anne Wilson -
Bob Beers -
Craig White -
John R Pierce -
Johnny Hughes -
Ross S. W. Walker -
Scott Silva -
Terry Polzin