Page 1 of 3 123 LastLast
Results 1 to 10 of 27

Thread: Nvidia 9500GT Driver problem

  1. #1

    Default Nvidia 9500GT Driver problem

    I know Nvidia driver issues seem to dominate these forums, but I couldn't find this question answered anywhere else. I recently put together an HTPC system and got it up and running this morning. I installed OpenSUSE 11.1 and the Vesa drivers fired up fine, although at 800x600 resolution on my Vizio VW37L. I let the updater applet get all of it's updates then "zypper up" as root from a terminal to make sure I was up to date on everything (Kde 4.1 stock from the DVD).

    Next came getting the Nvidia drivers set up (this is an HTPC after all). I first tried 1-click installs from the OpenSUSE wiki, but later manually added (after removing) the nvidia-gfx-G02-kmp-pae drivers each with the same result.

    I have used (as root) "sax2 -r", "sax2 -r -m 0=nvidia", and "nvidia-xconfig" to get the drivers installed. If I try with the session active the sax2 commands will start, screen will flicker, but then the terminal just hangs indefinately. nvidia-config succeeds but the screen doesn't survive a session restart.

    If I use sax after typing (as root) "init 3" I get this error in the xorg and sax logs after sax terminates:
    "NVIDIA: could not open the device file /dev/nvidia0 (Input/output error)"
    Rebooting and startx do not start a session until I revert xorg.conf back to vesa (either by using a backup or by "sax2 -r -m 0=VESA").

    Any ideas on what I can try? I update my BIOS this morning but same problems. Here's my hardware:

    * APEVIA Black SECC Steel / Aluminum X-MASTER-BK/500 ATX Media Center
    * GIGABYTE GA-MA770T-UD3P AM3 AMD 770 ATX AMD Motherboard
    * SPARKLE GeForce 9500 GT 512MB 128-bit GDDR2 PCI Express 2.0 x16
    * Hauppauge WinTV-HVR-1600 ATSC/ClearQAM/NTSC TV Tuner PCI w/Remote 1178 PCI Interface
    * AMD Athlon II X2 250 Regor 3.0GHz Socket AM3 65W Dual-Core Processor
    * G.SKILL 2GB (2 x 1GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10666)
    * Western Digital Caviar Green 500GB SATA 3.0Gb/s 3.5" Hard Drive
    * SAMSUNG Black 22X DVD Burner Black SATA
    * BYTECC 6 ft. HDMI Male to DVI-D Male Single Link Cable
    * And again, Vizio VW37L

    The TV has worked in both twinview and as a seperate X screen when connected to my laptop (Running a 8400gs) with the Nvidia drivers.

    Thanks for the help,
    Killsforpie

  2. #2
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    32,357
    Blog Entries
    15

    Default Re: Nvidia 9500GT Driver problem

    Quote Originally Posted by killsforpie
    I know Nvidia driver issues seem to dominate these forums, but I
    couldn't find this question answered anywhere else. I recently put
    together an HTPC system and got it up and running this morning. I
    installed OpenSUSE 11.1 and the Vesa drivers fired up fine, although at
    800x600 resolution on my Vizio VW37L. I let the updater applet get all
    of it's updates then "zypper up" as root from a terminal to make sure I
    was up to date on everything (Kde 4.1 stock from the DVD).

    Next came getting the Nvidia drivers set up (this is an HTPC after
    all). I first tried 1-click installs from the OpenSUSE wiki, but later
    manually added (after removing) the nvidia-gfx-G02-kmp-pae drivers each
    with the same result.

    I have used (as root) "sax2 -r", "sax2 -r -m 0=nvidia", and
    "nvidia-xconfig" to get the drivers installed. If I try with the session
    active the sax2 commands will start, screen will flicker, but then the
    terminal just hangs indefinately. nvidia-config succeeds but the screen
    doesn't survive a session restart.

    If I use sax after typing (as root) "init 3" I get this error in the
    xorg and sax logs after sax terminates:
    "NVIDIA: could not open the device file /dev/nvidia0 (Input/output
    error)"
    Rebooting and startx do not start a session until I revert xorg.conf
    back to vesa (either by using a backup or by "sax2 -r -m 0=VESA").

    Any ideas on what I can try? I update my BIOS this morning but same
    problems. Here's my hardware:

    * APEVIA Black SECC Steel / Aluminum X-MASTER-BK/500 ATX Media
    Center
    * GIGABYTE GA-MA770T-UD3P AM3 AMD 770 ATX AMD Motherboard
    * SPARKLE GeForce 9500 GT 512MB 128-bit GDDR2 PCI Express 2.0 x16
    * Hauppauge WinTV-HVR-1600 ATSC/ClearQAM/NTSC TV Tuner PCI w/Remote
    1178 PCI Interface
    * AMD Athlon II X2 250 Regor 3.0GHz Socket AM3 65W Dual-Core
    Processor
    * G.SKILL 2GB (2 x 1GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10666)
    * Western Digital Caviar Green 500GB SATA 3.0Gb/s 3.5" Hard Drive
    * SAMSUNG Black 22X DVD Burner Black SATA
    * BYTECC 6 ft. HDMI Male to DVI-D Male Single Link Cable
    * And again, Vizio VW37L

    The TV has worked in both twinview and as a seperate X screen when
    connected to my laptop (Running a 8400gs) with the Nvidia drivers.

    Thanks for the help,
    Killsforpie
    Hi
    Probably picked a bad day to install as there was a kernel update out.
    SO I would imagine the updates for the nvidia driver aren't there
    yet....

    You need to install the 'hard way' just some different steps at the CLI
    and extra packages to install. Following is my canned response to the
    'hard way'

    Have you installed the nvidia driver via 1-click? If not I recommend
    the hard way, else follow the easy way here;
    Nvidia

    If you have installed nvidia rpms via the easy way, I suggest removing
    the rpms installed and disabling the nvidia repository first.

    You can download the driver for your arch from;
    Nvidia Unix Drivers

    On the download page, check that your card is supported by the driver
    your about to download by using the following command;
    Code:
    echo -n "0x" && /sbin/lspci -nv |grep VGA|cut -f4 -d ":"|cut -f1 -d "("
    From the above output use the numbers from the output to look at the
    Supported Products List (link on the left) to verify your card is
    supported by the driver.

    You may wish to ensure your system is up to date. The first command
    refreshes the repositories, the second lists any updates, the third
    will apply the updates.
    Code:
     
    sudo zypper ref
    sudo zypper lu
    sudo zypper up
    NOTE: If the kernel updated, please reboot before continuing

    If you don't have the kernel source and tools etc installed then
    Code:
    sudo zypper in kernel-source linux-kernel-headers kernel-syms
    module-init-tools make gcc
    Press ctrl+alt+F1 and login as your user
    Code:
    su -
    init 3
    cd to the Nvidia Unix Driver you downloaded
    Code:
    sh NV*.run -q
    sax2 -r -m 0=nvidia
    init 5 && exit
    ctrl+alt+F1
    exit
    ctrl+alt+F7
    The ctrl+alt+F7 gets you back to the GUI (X session).

    Now after a kernel update, you don't need to run the sax2 command, just
    the others to get to run level 3, rebuild the driver and exit.

    --
    Cheers Malcolm (Linux Counter #276890)
    SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 2.6.27.29-0.1-default
    up 1:26, 2 users, load average: 0.05, 0.01, 0.00
    GPU GeForce 8600 GTS Silent - Driver Version: 190.18


  3. #3
    Join Date
    Aug 2008
    Location
    Winnipeg, Canada
    Posts
    203

    Default Re: Nvidia 9500GT Driver problem

    I would try installing the NVIDIA drivers the hard way. Go to the nvidia website and download the driver for your video card, either the 32-bit or 64-bit driver.

    Boot your system into init 3; then sudo sh the name of the driver -q

    You'll need to have the linux kernel headers installed.

    Then as root run sax2 -r -m 0=nvidia

    Cheers!

  4. #4

    Default Re: Nvidia 9500GT Driver problem

    Thanks so much for the help, downloading the headers now. If you had to hazard a guess, how long do you think it'll be before the drivers are ready? Is it painless to go back to stock Nvidia drivers from compiling my own? I really have no burning need to have this up and running now, would it be more beneficial to wait?

  5. #5
    Join Date
    Nov 2008
    Location
    N. Wales
    Posts
    1,028

    Default Re: Nvidia 9500GT Driver problem

    killsforpie adjusted his/her AFDB on Thursday 20 Aug 2009 19:56 to write:

    >
    > Thanks so much for the help, downloading the headers now. If you had to
    > hazard a guess, how long do you think it'll be before the drivers are
    > ready? Is it painless to go back to stock Nvidia drivers from compiling
    > my own? I really have no burning need to have this up and running now,
    > would it be more beneficial to wait?
    >
    >


    Personally it is just as quick to roll your own, same goes for the ATI
    drivers, one reason is that the repo versions do take a while to get in line
    and even then they may not be the latest version.

    For your hardware you need the latest version.

    it is more likely that the drivers will be updated on the Nvidia site more
    often than the kernel so you will always lag behind.

    If you have the .run package and there is a kernel update you only have to
    run again as malcolm said rather than wait for th repos to get in sync.

    On your machine it would take less than 3 minutes to drop from the GUI to
    init 3 at the console re-run the installer and then start the GUI ( init 5 )
    again.

    That is all it takes on my machines ( Nvidia and ATI ), up and running with
    no reboot all configured in approx 3 minutes.

    Painless.

    HTH

    --
    Mark
    Caveat emptor
    Nullus in verba
    Nil illegitimi carborundum

  6. #6

    Default Re: Nvidia 9500GT Driver problem

    That does seem painless enough. Even though I have less control, I tend to prefer the automatic updates. On my laptop, I've really only been updating the kernel when it was needed for the graphics drivers, and yast would do it for me then.

    Though with the more diversified use of my HTPC (tv tuner) kernel updates may become more important for me. I need this box to be as stable as possible so I can sell the idea to my wife.

  7. #7

    Default Re: Nvidia 9500GT Driver problem

    Ok so I downloaded the driver from the page you suggested, got the kernel source and tools, was able to make the module ("sh NV*.run -q") but again sax2 doesn't work. Here's the tail end of the log(SaX.log):

    Code:
    	(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
    	(==) NVIDIA(0): RGB weight 888
    	(==) NVIDIA(0): Default visual is TrueColor
    	(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
    	(==) NVIDIA(0): Using HW cursor
    	(**) NVIDIA(0): Enabling RENDER acceleration
    	(==) NVIDIA(0): Video key set to default value of 0x101fe
    	(--) NVIDIA(0): Not mapping the primary surface by default.
    	(II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
    	(II) NVIDIA(0):     enabled.
    	NVIDIA: could not open the device file /dev/nvidia0 (Input/output error).
    	(EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device PCI:1:0:0. 
    	(EE) NVIDIA(0):     Please check your system's kernel log for additional error
    	(EE) NVIDIA(0):     messages and refer to Chapter 8: Common Problems in the
    	(EE) NVIDIA(0):     README for additional information.
    	(EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device!
    	(II) UnloadModule: "nvidia"
    	(II) UnloadModule: "wfb"
    	(II) UnloadModule: "fb"
    	(EE) Screen(s) found, but none have a usable configuration.
    	
    	Fatal server error:
    	no screens found
    And I had to revert to a backup xorg.conf. I can post a broken version of that too if it would help.

  8. #8
    Join Date
    Nov 2008
    Location
    N. Wales
    Posts
    1,028

    Default Re: Nvidia 9500GT Driver problem

    killsforpie adjusted his/her AFDB on Thursday 20 Aug 2009 22:06 to write:

    >
    > Ok so I downloaded the driver from the page you suggested, got the
    > kernel source and tools, was able to make the module ("sh NV*.run -q")
    > but again sax2 doesn't work. Here's the tail end of the log(SaX.log):
    >
    >
    > Code:
    > --------------------
    > (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
    > (==) NVIDIA(0): RGB weight 888
    > (==) NVIDIA(0): Default visual is TrueColor
    > (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
    > (==) NVIDIA(0): Using HW cursor
    > (**) NVIDIA(0): Enabling RENDER acceleration
    > (==) NVIDIA(0): Video key set to default value of 0x101fe
    > (--) NVIDIA(0): Not mapping the primary surface by default.
    > (II) NVIDIA(0): Support for GLX with the Damage and Composite X
    > extensions is
    > (II) NVIDIA(0): enabled.
    > NVIDIA: could not open the device file /dev/nvidia0 (Input/output
    > error). (EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device
    > PCI:1:0:0.
    > (EE) NVIDIA(0): Please check your system's kernel log for additional
    > error
    > (EE) NVIDIA(0): messages and refer to Chapter 8: Common Problems in
    > the
    > (EE) NVIDIA(0): README for additional information.
    > (EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device!
    > (II) UnloadModule: "nvidia"
    > (II) UnloadModule: "wfb"
    > (II) UnloadModule: "fb"
    > (EE) Screen(s) found, but none have a usable configuration.
    >
    > Fatal server error:
    > no screens found
    > --------------------
    >
    >
    > And I had to revert to a backup xorg.conf. I can post a broken version
    > of that too if it would help.
    >
    >


    Did you run the nvidia-xconfig command after installing?

    This is the normal step that people miss, it is there for a reason, it
    should configure the xorg.conf so that it will use the nvidia driver.

    If you get that working then if you get to KDE and it will not allow you to
    use all the effects then drop back to init 3 as root and then run sax2 -m
    0=nvidia

    or it might be sax2 -r -m 0=nvidia

    I went through this yesterday on my sandbox with 11.2 rc5, I could get
    things part way running but I could not use parts of the driver so I went
    back and used sax and it works fine now.

    I think it is a case of finding the right combination.

    Once you get running in the GUI you can use the nvidia-setting GUI to
    configure your own prefs which you can save, the rc file will be put in your
    home dir and run on every login.

    HTH



    --
    Mark
    Caveat emptor
    Nullus in verba
    Nil illegitimi carborundum

  9. #9

    Default Re: Nvidia 9500GT Driver problem

    So is the order:
    sh NV*.run -q
    nvidia-xconfig
    sax2 -r -m 0=nvidia

    or:
    sh NV*.run -q
    sax2 -r -m 0=nvidia
    nvidia-xconfig

  10. #10

    Default Re: Nvidia 9500GT Driver problem

    Neither one works. This is what I get when trying to startx after installing (returning to init 5 does nothing)

    Code:
    xauth:  creating new authority file /root/.serverauth.22190
    
    
    X.Org X Server 1.5.2
    Release Date: 10 October 2008
    X Protocol Version 11, Revision 0
    Build Operating System: openSUSE SUSE LINUX
    Current Operating System: Linux linux-ncox 2.6.27.29-0.1-pae #1 SMP 2009-08-15 17:53:59 +0200 i686
    Build Date: 02 July 2009  08:02:13AM
     
    	Before reporting problems, check http://wiki.x.org
    	to make sure that you have the latest version.
    Module Loader present
    Markers: (--) probed, (**) from config file, (==) default setting,
    	(++) from command line, (!!) notice, (II) informational,
    	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (==) Log file: "/var/log/Xorg.0.log", Time: Thu Aug 20 17:39:36 2009
    (==) Using config file: "/etc/X11/xorg.conf"
    NVIDIA: could not open the device file /dev/nvidia0 (Input/output error).
    (EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device PCI:1:0:0. 
    (EE) NVIDIA(0):     Please check your system's kernel log for additional error
    (EE) NVIDIA(0):     messages and refer to Chapter 8: Common Problems in the
    (EE) NVIDIA(0):     README for additional information.
    (EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device!
    (EE) Screen(s) found, but none have a usable configuration.
    
    Fatal server error:
    no screens found
    giving up.
    xinit:  Connection refused (errno 111):  unable to connect to X server
    xinit:  No such process (errno 3):  Server error.

Page 1 of 3 123 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •