new install on AMD64 x86 with "slight" X-windows problem
Ok, so I finally got all the bits and pieces I wanted for my 64 bit box together and have run into a slight problem. My 19" Monitor is capable of displaying 1280x1024, but only @ 75Hz. Yast seemed to detect the correct frequency range while I was installing, but when X/KDE started up my monitor reported that they sync rate was out of range. I switched to a terminal and logged in then ran YAST in text mode, but seem to be unable to change the refresh rates reported that are probed. How can I change the default refresh rate that X/KDE uses? I amsume that there is a config file I can edit while logged into a terminal, but after (a very short) google attempt I could not locate an answer. thanks Lance
You want to play with the /etc/X11/XF86Config (XFree86 at least, not sure about X.org) or simply use Sax2 (but may not work if incorrectly detecting) There may be a command line option for Sax to set. man sax or man sax2 B-) On Wednesday 27 October 2004 09:12 am, ozymandias@pt-cruiser.net wrote:
Ok, so I finally got all the bits and pieces I wanted for my 64 bit box together and have run into a slight problem. My 19" Monitor is capable of displaying 1280x1024, but only @ 75Hz. Yast seemed to detect the correct frequency range while I was installing, but when X/KDE started up my monitor reported that they sync rate was out of range. I switched to a terminal and logged in then ran YAST in text mode, but seem to be unable to change the refresh rates reported that are probed.
How can I change the default refresh rate that X/KDE uses? I amsume that there is a config file I can edit while logged into a terminal, but after (a very short) google attempt I could not locate an answer.
thanks
Lance
How can I change the default refresh rate that X/KDE uses? I amsume that there is a config file I can edit while logged into a terminal, but after (a very short) google attempt I could not locate an answer.
Log into a console as root , run init 3 ; sax2 -l and select a different monitor -Andi
Hi, have problems here with SuSE 9.2_64, FX5900XT, default kernel and the nvidia driver 6111 (and also the previous). After installing them by using the command sh NVIDIA_*.run -q --kernel-source-path=/usr/src/linux (or with --kernel-name=2.6.8-24) enabling GL support in sax2 is ending with an error. Sax.log says (EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module! (EE) NVIDIA(0): *** Aborting *** (II) UnloadModule: "nvidia" (II) UnloadModule: "vgahw" (II) Unloading /usr/X11R6/lib64/modules/libvgahw.a (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found Any suggestions, please? BTW, with SuSE 9.1, the same hardware is working fine with GL mode. Kindly regards Uwe -- PGP 2.6.3-Key auf Anfrage, PGP-Key on request
I've seen where sometime using a newer driver, the refresh rate minimum goes up, so if you monitor settings aren't high enough, it won't be able to find any screens... B-) On Thursday 28 October 2004 09:08 am, Uwe Pannecke wrote:
Hi,
have problems here with SuSE 9.2_64, FX5900XT, default kernel and the nvidia driver 6111 (and also the previous). After installing them by using the command sh NVIDIA_*.run -q --kernel-source-path=/usr/src/linux (or with --kernel-name=2.6.8-24) enabling GL support in sax2 is ending with an error. Sax.log says (EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module! (EE) NVIDIA(0): *** Aborting *** (II) UnloadModule: "nvidia" (II) UnloadModule: "vgahw" (II) Unloading /usr/X11R6/lib64/modules/libvgahw.a (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found
Any suggestions, please?
BTW, with SuSE 9.1, the same hardware is working fine with GL mode.
Kindly regards
Uwe -- PGP 2.6.3-Key auf Anfrage, PGP-Key on request
Hi Brad and all,
have problems here with SuSE 9.2_64, FX5900XT, default kernel and the nvidia driver 6111 (and also the previous). After installing them by using the command sh NVIDIA_*.run -q --kernel-source-path=/usr/src/linux (or with --kernel-name=2.6.8-24) enabling GL support in sax2 is ending with an error. Sax.log says (EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module! (EE) NVIDIA(0): *** Aborting *** (II) UnloadModule: "nvidia" (II) UnloadModule: "vgahw" (II) Unloading /usr/X11R6/lib64/modules/libvgahw.a (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found Any suggestions, please? I've seen where sometime using a newer driver, the refresh rate minimum goes up, so if you monitor settings aren't high enough, it won't be able to find any screens...
nvidia-installer.log says: ----------snip----------- -> Installing 'NVIDIA Accelerated Graphics Driver for Linux-x86_64' (1.0-6111): executing: './usr/src/nv/makedevices.sh'... executing: '/sbin/ldconfig'... executing: '/sbin/depmod -aq'... -> done. -> Driver file installation is complete. -> Running post-install sanity check: -> done. -> Sanity check passed. -> Shared memory test passed. -> Installation of the NVIDIA Accelerated Graphics Driver for Linux-x86_64 (version: 1.0-6111) is now complete. On SuSE Linux/United Linux please use SaX2 now to enable the NVIDIA driver. ----------snap----------- Sax2 identifies the monitor (LCD with max 135 MHz max pixel rate and max 83 kHz horizontal freq.) with his name and manufacturer and the nvidia card (Identifier 0x0332 for FX5900XT) correct and takes the right resolutions and refresh rate, if it is running with "sax2 -m 0=nv". But if I start sax2 with "sax2 -m 0=nvidia", then sax2 breaks and the output is ---------snip------------ xc: sorry could not start configuration server xc: this could have the following reasons: - the card is still not supported. To get further information about the driver status please have a look at: http://http://www.x.org - the card was not detected correctly. In this case please get the information which X11 module provide support for the card and set the module using the following command: sax2 -m 0=<name of the module> Note: 0 is a digit not a letter Note: Information about modules are provided on the mentioned WWW-Page - the card was detected but the server fails to start in spite of the detection. In this case something more serious had happened. Please have a look at the log file: /var/log/SaX.log ----------snap--------- and then in Sax.log I can found -----------snip----------- (EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module! (EE) NVIDIA(0): *** Aborting *** (II) UnloadModule: "nvidia" (II) UnloadModule: "vgahw" (II) Unloading /usr/X11R6/lib64/modules/libvgahw.a (EE) Screen(s) found, but none have a usable configuration. -----------snap-------------- Is the nvidia 6111 compatible with SuSE 9.2_64? Maybe that the kernel(source) or X.org cause the problem? SuSE 9.1_64 has under identical hardware that problem not. Kindly Regards Uwe -- PGP 2.6.3-Key auf Anfrage, PGP-Key on request
I had / have the same thing happening to me. I noticed that all I had to do was manually 'modprobe nvidia', then it would start. Don't know if adding a Load "nvidia" to the modules section would help or not. Almost seems like something stops it from loading correctly if it doesn't get loaded before X...... B-) On Friday 29 October 2004 09:52 am, Uwe Pannecke wrote:
Hi Brad and all,
have problems here with SuSE 9.2_64, FX5900XT, default kernel and the nvidia driver 6111 (and also the previous). After installing them by using the command sh NVIDIA_*.run -q --kernel-source-path=/usr/src/linux (or with --kernel-name=2.6.8-24) enabling GL support in sax2 is ending with an error. Sax.log says (EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module! (EE) NVIDIA(0): *** Aborting *** (II) UnloadModule: "nvidia" (II) UnloadModule: "vgahw" (II) Unloading /usr/X11R6/lib64/modules/libvgahw.a (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found Any suggestions, please?
I've seen where sometime using a newer driver, the refresh rate minimum goes up, so if you monitor settings aren't high enough, it won't be able to find any screens...
nvidia-installer.log says: ----------snip----------- -> Installing 'NVIDIA Accelerated Graphics Driver for Linux-x86_64' (1.0-6111): executing: './usr/src/nv/makedevices.sh'... executing: '/sbin/ldconfig'... executing: '/sbin/depmod -aq'... -> done. -> Driver file installation is complete. -> Running post-install sanity check: -> done. -> Sanity check passed. -> Shared memory test passed. -> Installation of the NVIDIA Accelerated Graphics Driver for Linux-x86_64 (version: 1.0-6111) is now complete. On SuSE Linux/United Linux please use SaX2 now to enable the NVIDIA driver. ----------snap-----------
Sax2 identifies the monitor (LCD with max 135 MHz max pixel rate and max 83 kHz horizontal freq.) with his name and manufacturer and the nvidia card (Identifier 0x0332 for FX5900XT) correct and takes the right resolutions and refresh rate, if it is running with "sax2 -m 0=nv".
But if I start sax2 with "sax2 -m 0=nvidia", then sax2 breaks and the output is
---------snip------------ xc: sorry could not start configuration server xc: this could have the following reasons:
- the card is still not supported. To get further information about the driver status please have a look at:
- the card was not detected correctly. In this case please get the information which X11 module provide support for the card and set the module using the following command:
sax2 -m 0=<name of the module>
Note: 0 is a digit not a letter Note: Information about modules are provided on the mentioned WWW-Page
- the card was detected but the server fails to start in spite of the detection. In this case something more serious had happened. Please have a look at the log file:
/var/log/SaX.log ----------snap---------
and then in Sax.log I can found
-----------snip----------- (EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module! (EE) NVIDIA(0): *** Aborting *** (II) UnloadModule: "nvidia" (II) UnloadModule: "vgahw" (II) Unloading /usr/X11R6/lib64/modules/libvgahw.a (EE) Screen(s) found, but none have a usable configuration. -----------snap--------------
Is the nvidia 6111 compatible with SuSE 9.2_64? Maybe that the kernel(source) or X.org cause the problem?
SuSE 9.1_64 has under identical hardware that problem not.
Kindly Regards
Uwe -- PGP 2.6.3-Key auf Anfrage, PGP-Key on request
participants (4)
-
Andi Kleen -
Brad Bourn -
ozymandias＠pt-cruiser.net -
Uwe.Pannecke＠t-online.de