Go Back   nV News Forums > Linux Support Forums > NVIDIA Linux

Newegg Daily Deals

Reply
 
Thread Tools
Old 06-09-04, 04:57 PM   #1
Draylath
Registered User
 
Join Date: Jun 2004
Location: Cambridge
Posts: 5
Default I can't get X working with nvidia drivers

Hi there,

I need a bit of help, I've got Fedora Core 1 running great apart from the graphics side of things. I have a GeForce 4 MX 420 and it is currently running with the generic drivers suplied on my distro. I got the drivers and the install seemed to go Ok and I folloewed the instructions about editing XF86Config but I get error messages and no X. It says something about Screen(s) found but none have a useable configuration. I have enclosed the files that the sticky thread asked for and would appreciate any help to get the bast out of my card.

Many thanks in advance,
Draylath
Attached Files
File Type: txt showlog.txt (3.1 KB, 146 views)
File Type: txt showlog2.txt (15.4 KB, 132 views)
Draylath is offline   Reply With Quote
Old 06-10-04, 06:13 AM   #2
rednuht
GeForce FX5600 (1.0-5336)
 
rednuht's Avatar
 
Join Date: Sep 2003
Location: uk
Posts: 164
Default Re: I can't get X working with nvidia drivers

Please post your config file

usualy in /etc/X11
rednuht is offline   Reply With Quote
Old 06-10-04, 12:37 PM   #3
Draylath
Registered User
 
Join Date: Jun 2004
Location: Cambridge
Posts: 5
Default Re: I can't get X working with nvidia drivers

Ok, here it is, though I did think I sent it as an attachemnt.

# XFree86 4 configuration created by pyxf86config

Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "DevInputMice" "AlwaysCore"
EndSection

Section "Files"
# RgbPath is the location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.

# Multiple FontPath entries are allowed (they are concatenated together)
# By default, Red Hat 6.0 and later now use a font server independent of
# the X server to render fonts.

RgbPath "/usr/X11R6/lib/X11/rgb"
FontPath "unix/:7100"
EndSection

Section "Module"
Load "dbe"
Load "extmod"
Load "fbdevhw"
Load "glx"
Load "record"
Load "freetype"
Load "type1"

EndSection

Section "InputDevice"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"

# To disable the XKEYBOARD extension, uncomment XkbDisable.
# Option "XkbDisable"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# Or if you just want both to be control, use:
# Option "XkbOptions" "ctrl:nocaps"
#
Identifier "Keyboard0"
Driver "keyboard"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc105"
Option "XkbLayout" "gb"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/psaux"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"
EndSection

Section "InputDevice"
# If the normal CorePointer mouse is not a USB mouse then
# this input device can be used in AlwaysCore mode to let you
# also use USB mice at the same time.
Identifier "DevInputMice"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Delta DE-570"
DisplaySize 280 210
HorizSync 30.0 - 70.0
VertRefresh 50.0 - 120.0
Option "dpms"
EndSection

Section "Device"
Identifier "Videocard0"
Driver "nvidia"
VendorName "Videocard vendor"
BoardName "NVIDIA GeForce 4 (generic)"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "DRI"
Group 0
Mode 0666
EndSection

Hope this is what you need and thanks for replying
Draylath is offline   Reply With Quote
Old 06-10-04, 02:51 PM   #4
utanja
Debian All the Way
 
Join Date: May 2004
Location: Salzburg Austria & Orlando Florida
Posts: 59
Default Re: I can't get X working with nvidia drivers

i believe the BusID is missing in X86Config-4

this is from my X86Config-4
Section "Device"
Identifier "Generic Video Card"
Driver "nvidia"
BusID "PCI:1:0:0"
EndSection

the BusID may be different for your MB..
__________________
utanja
i am female and i don't do windows.. and i don't do macs ..i fly a Lear Jet
"Wer fremde Sprachen nicht kennt, weiss nichts von seiner eigenen."
- Goethe, Maximen und Reflexionen
Intel 3I-core 2d.gen -3.1GHz;8 gig ram;PureDebian SID[3.2[custom kernel] 8 Debian workstations
plus HP Win7 64bit Wireless Laptop Network/Citrix/NX/VMware
Mozilla/Firebird browsers
my american friends call me tonya
utanja is offline   Reply With Quote
Old 06-10-04, 05:20 PM   #5
Draylath
Registered User
 
Join Date: Jun 2004
Location: Cambridge
Posts: 5
Default Re: I can't get X working with nvidia drivers

Thanks for replying,

I don't have XF86Config-4 just XF86Config

I'm quite a linux newbie so could you tell me what all that means please, if PCI means the type of posrt it is plugged into I think it is AGP.

Sorry to be akward
Draylath is offline   Reply With Quote
Old 06-10-04, 05:58 PM   #6
utanja
Debian All the Way
 
Join Date: May 2004
Location: Salzburg Austria & Orlando Florida
Posts: 59
Default Re: I can't get X working with nvidia drivers

no problem...we all were newbies at one time....all devices have an address on the MB bus systems....the address for your video card seems to be missing....
i used to run fedora core 1 on a test machine and never had a problem with fedora identifying the location...but if i remember correctly. i did have the above mentioned location in my XF86Config-4 files.....i would suggest that you reinstall the video drivers again...
__________________
utanja
i am female and i don't do windows.. and i don't do macs ..i fly a Lear Jet
"Wer fremde Sprachen nicht kennt, weiss nichts von seiner eigenen."
- Goethe, Maximen und Reflexionen
Intel 3I-core 2d.gen -3.1GHz;8 gig ram;PureDebian SID[3.2[custom kernel] 8 Debian workstations
plus HP Win7 64bit Wireless Laptop Network/Citrix/NX/VMware
Mozilla/Firebird browsers
my american friends call me tonya
utanja is offline   Reply With Quote
Old 06-10-04, 06:07 PM   #7
utanja
Debian All the Way
 
Join Date: May 2004
Location: Salzburg Austria & Orlando Florida
Posts: 59
Default Re: I can't get X working with nvidia drivers

this is taken from
http://www.xfree86.org/4.3.0/XF86Config.5.html#sect6

The config file may have multiple Device sections. There must be at least one, for the video card being used.

Device sections have the following format:


Section "Device"
Identifier "name"
Driver "driver"
entries
...
EndSection

The Identifier entry specifies the unique name for this graphics device. The Driver entry specifies the name of the driver to use for this graphics device. When using the loadable server, the driver module "driver" will be loaded for each active Device section. A Device section is considered active if it is referenced by an active Screen section.

Device sections recognise some driver-independent entries and Options, which are described here. Not all drivers make use of these driver-independent entries, and many of those that do don't require them to be specified because the information is auto-detected. See the individual graphics driver manual pages for further information about this, and for a description of the device-specific options. Note that most of the Options listed here (but not the other entries) may be specified in the Screen section instead of here in the Device section.

BusID "bus-id"
This specifies the bus location of the graphics card. For PCI/AGP cards, the bus-id string has the form PCI:bus:device:function (e.g., "PCI:1:0:0" might be appropriate for an AGP card). This field is usually optional in single-head configurations when using the primary graphics card. In multi-head configurations, or when using a secondary graphics card in a single-head configuration, this entry is mandatory. Its main purpose is to make an unambiguous connection between the device section and the hardware it is representing. This information can usually be found by running the X server with the -scanpci command line option.

Screen number
This option is mandatory for cards where a single PCI entity can drive more than one display (i.e., multiple CRTCs sharing a single graphics accelerator and video memory). One Device section is required for each head, and this parameter determines which head each of the Device sections applies to. The legal values of number range from 0 to one less than the total number of heads per entity. Most drivers require that the primary screen (0) be present.
Chipset "chipset"
This usually optional entry specifies the chipset used on the graphics board. In most cases this entry is not required because the drivers will probe the hardware to determine the chipset type. Don't specify it unless the driver-specific documentation recommends that you do.
Ramdac "ramdac-type"
This optional entry specifies the type of RAMDAC used on the graphics board. This is only used by a few of the drivers, and in most cases it is not required because the drivers will probe the hardware to determine the RAMDAC type where possible. Don't specify it unless the driver-specific documentation recommends that you do.
DacSpeed speed
DacSpeed speed-8 speed-16 speed-24 speed-32
This optional entry specifies the RAMDAC speed rating (which is usually printed on the RAMDAC chip). The speed is in MHz. When one value is given, it applies to all framebuffer pixel sizes. When multiple values are give, they apply to the framebuffer pixel sizes 8, 16, 24 and 32 respectively. This is not used by many drivers, and only needs to be specified when the speed rating of the RAMDAC is different from the defaults built in to driver, or when the driver can't auto-detect the correct defaults. Don't specify it unless the driver-specific documentation recommends that you do.
Clocks clock ...
specifies the pixel that are on your graphics board. The clocks are in MHz, and may be specified as a floating point number. The value is stored internally to the nearest kHz. The ordering of the clocks is important. It must match the order in which they are selected on the graphics board. Multiple Clocks lines may be specified, and each is concatenated to form the list. Most drivers do not use this entry, and it is only required for some older boards with non-programmable clocks. Don't specify this entry unless the driver-specific documentation explicitly recommends that you do.
ClockChip "clockchip-type"
This optional entry is used to specify the clock chip type on graphics boards which have a programmable clock generator. Only a few X servers support programmable clock chips. For details, see the appropriate X server manual page.
VideoRam mem
This optional entry specifies the amount of video ram that is installed on the graphics board. This is measured in kBytes. In most cases this is not required because the X server probes the graphics board to determine this quantity. The driver-specific documentation should indicate when it might be needed.
BiosBase baseaddress
This optional entry specifies the base address of the video BIOS for the VGA board. This address is normally auto-detected, and should only be specified if the driver-specific documentation recommends it.
MemBase baseaddress
This optional entry specifies the memory base address of a graphics board's linear frame buffer. This entry is not used by many drivers, and it should only be specified if the driver-specific documentation recommends it.
IOBase baseaddress
This optional entry specifies the IO base address. This entry is not used by many drivers, and it should only be specified if the driver-specific documentation recommends it.
ChipID id
This optional entry specifies a numerical ID representing the chip type. For PCI cards, it is usually the device ID. This can be used to override the auto-detection, but that should only be done when the driver-specific documentation recommends it.
ChipRev rev
This optional entry specifies the chip revision number. This can be used to override the auto-detection, but that should only be done when the driver-specific documentation recommends it.
TextClockFreq freq
This optional entry specifies the pixel clock frequency that is used for the regular text mode. The frequency is specified in MHz. This is rarely used.
Options
Option flags may be specified in the Device sections. These include driver-specific options and driver-independent options. The former are described in the driver-specific documentation. Some of the latter are described below in the section about the Screen section, and they may also be included here.
__________________
utanja
i am female and i don't do windows.. and i don't do macs ..i fly a Lear Jet
"Wer fremde Sprachen nicht kennt, weiss nichts von seiner eigenen."
- Goethe, Maximen und Reflexionen
Intel 3I-core 2d.gen -3.1GHz;8 gig ram;PureDebian SID[3.2[custom kernel] 8 Debian workstations
plus HP Win7 64bit Wireless Laptop Network/Citrix/NX/VMware
Mozilla/Firebird browsers
my american friends call me tonya
utanja is offline   Reply With Quote
Old 06-11-04, 06:42 AM   #8
rednuht
GeForce FX5600 (1.0-5336)
 
rednuht's Avatar
 
Join Date: Sep 2003
Location: uk
Posts: 164
Default Re: I can't get X working with nvidia drivers

do not worry about only having XF86Config just be aware that if you did have a XF86Config-4 file it would take preference.
rednuht is offline   Reply With Quote

Old 06-11-04, 03:14 PM   #9
Draylath
Registered User
 
Join Date: Jun 2004
Location: Cambridge
Posts: 5
Default Re: I can't get X working with nvidia drivers

thanks for the help peeps but I'm afraid to say I've had no luck. I added the BusID "1:0:0" and got the same error messages back. I then ( as i'm not sure that I had the right bus info) ran "startx -scanpci", I was told that this was a bad argument or something.

anything else would be great as I have got the sheer bloody mindednes that is making me want to crack this if it kills me, thanks,
draylath
Draylath is offline   Reply With Quote
Old 06-11-04, 03:40 PM   #10
LordMorgul
Electrical Engineer
 
LordMorgul's Avatar
 
Join Date: Dec 2002
Location: San Luis Obispo, CA
Posts: 872
Default Re: I can't get X working with nvidia drivers

Quote:
Originally Posted by XFree86.0.log
(EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device!
(EE) NVIDIA(0): *** Aborting ***
Without the nvidia kernel module loaded the driver will not function. Does it load manually? modprobe nvidia
If you find you aren't making any progress with this.. I suggest you uninstall the driver and go get one of the RPM install options from my sig -- the Livna.org nvidia packages are very nice. You will first have to update your kernel -- you should do this anyway since you are running a kernel with security flaws. See the download.fedora.redhat.com or use yum / up2date to get the newer kernel.
__________________
"..the triumph of evil is for good men to do nothing." (Edmond Burke)
nVIDIA video driver RPMs for Fedora :: see yum repo at livna.org.
LordMorgul is offline   Reply With Quote
Reply


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


Similar Threads
Thread Thread Starter Forum Replies Last Post
NVIDIA Drivers Receive Windows 8 Certification News Archived News Items 0 06-01-12 05:30 AM
Radeon 9700 not all that? sancheuz Other Desktop Graphics Cards 200 10-12-02 09:31 PM
Nvidia Stereo Drivers Soudontsay NVIDIA Windows Graphics Drivers 2 08-26-02 10:48 AM
nvidia drivers in a motherboard with AGP 1.0 (motherboard MVP3+) knocker NVIDIA Linux 1 08-19-02 01:57 AM
NVIDIA 2960 Drivers & RH 7.3 W/2.4.18-5 XASCompuGuy NVIDIA Linux 6 08-02-02 11:53 AM

All times are GMT -5. The time now is 04:48 AM.


Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.