LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 11-09-2007, 04:30 PM   #1
jroggow
Member
 
Registered: Mar 2006
Distribution: Slackware
Posts: 33

Rep: Reputation: 15
nVidia Drivers fail on Slackware 12 and Xorg 1.4


Hello all. I'm building an HTPC with Linux and MythTV and all that good stuff. Sadly, I'm having some trouble getting things off the ground.

The machine is a dual core 64 bit AMD processor with an nVidia Geforce 7300 GT. I built a custom 2.6.23.1 kernel based on the 2.6.21 generic smp kernel that ships with Slack 12.

I'm trying to install the nVidia x86 100.14.19 driver from nVidia. The thing installs well enough, but X croaks when I startx. The generic vesa driver works just fine, but I kind of need hardware acceleration so . . . I ran across a post that suggested Xorg 1.3 might be buggy so I removed 1.3 from my Slackware and built v1.4 and it works (quite nicely, I might add; it seems very responsive).

However, the nVidia driver still breaks X. A look at the Xorg.0.log shows all the modules and drivers loading successfully, but X crashes with
Code:
(II) NVIDIA(0): Initialized GART.
(II) NVIDIA(0): Initialized GART.

Backtrace:
0: X(xf86SigHandler+0x74) [0x80c8e34]
1: [0xffffe420]

Fatal server error:
Caught signal 11.  Server aborting
My xorg.conf file looks like so:

Code:
Section "Module"

# This loads the DBE extension module.

    Load        "dbe"  	# Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
    SubSection  "extmod"
      Option    "omit xfree86-dga"   # don't initialise the DGA extension
    EndSubSection

# This loads the font modules
    Load        "type1"
    Load        "freetype"
    #Load        "speedo"

# This loads the GLX module
    Load       "glx"

EndSection

Section "Files"

# 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.

    RgbPath	"/usr/share/X11/rgb"


    FontPath   "/usr/share/fonts/local/"
    FontPath   "/usr/share/fonts/misc/"
    FontPath   "/usr/share/fonts/OTF/"
    FontPath   "/usr/share/fonts/TTF/"
    FontPath   "/usr/share/fonts/Type1/"
    FontPath   "/usr/share/fonts/CID/"
    FontPath   "/usr/share/fonts/Speedo/"
    FontPath   "/usr/share/fonts/75dpi/:unscaled"
    FontPath   "/usr/share/fonts/100dpi/:unscaled"
    FontPath   "/usr/share/fonts/75dpi/"
    FontPath   "/usr/share/fonts/100dpi/"
    FontPath   "/usr/share/fonts/cyrillic/"

EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

EndSection

# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************

Section "InputDevice"

    Identifier	"Keyboard1"
    Driver	"kbd"

EndSection


# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

    Identifier	"Mouse1"
    Driver	"mouse"

EndSection

# **********************************************************************
# Monitor section
# **********************************************************************

# Any number of monitor sections may be present

Section "Monitor"

    Identifier  "My Monitor"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    HorizSync   31.5 - 50.0

#    HorizSync	30-64         # multisync
#    HorizSync	31.5, 35.2    # multiple fixed sync frequencies
#    HorizSync	15-25, 30-50  # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    VertRefresh 40-90

EndSection


# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

Section "Device"
    Identifier  "nVidia"
    Driver      "nvidia"
    #VideoRam    4096
    # Insert Clocks lines here if appropriate
EndSection

# **********************************************************************
# Screen sections
# **********************************************************************

# Any number of screen sections may be present.  Each describes
# the configuration of a single screen.  A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
    Identifier  "Screen 1"
    Device      "nVidia"
    Monitor     "My Monitor"

# If your card can handle it, a higher default color depth (like 24 or 32)
# is highly recommended.

#   DefaultDepth 8
#   DefaultDepth 16
   DefaultDepth 24
#   DefaultDepth 32

# "1024x768" is also a conservative usable default resolution.  If you
# have a better monitor, feel free to try resolutions such as
# "1152x864", "1280x1024", "1600x1200", and "1800x1400" (or whatever your
# card/monitor can produce)

    Subsection "Display"
        Depth       8
        Modes "1024x768" "800x600" "640x480"
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes "1024x768" "800x600" "640x480"
    EndSubsection
    Subsection "Display"
        Depth       24
        Modes "1024x768" "800x600" "640x480"
    EndSubsection
    Subsection "Display"
        Depth       32
        Modes "1024x768" "800x600" "640x480"
    EndSubsection

EndSection

# **********************************************************************
# ServerLayout sections.
# **********************************************************************

# Any number of ServerLayout sections may be present.  Each describes
# the way multiple screens are organised.  A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option.  In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section "ServerLayout"

# The Identifier line must be present
    Identifier  "Simple Layout"

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens.  The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen.  In this example, screen 2 is located to the
# right of screen 1.

    Screen "Screen 1"

# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used.  Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".

    InputDevice "Mouse1" "CorePointer"
    InputDevice "Keyboard1" "CoreKeyboard"

EndSection
I can swap the nvidia device driver with vesa and the darned thing works like a charm. I don't have the open-source nvidiafb or rivafb drivers compiled, and they're blacklisted in any case.

It seems a pretty common problem, but none of the solutions I've found have solved anything. I'm stumped. I think my next step might be to try a 64 bit Linux like Slamd64. Perhaps the architecture is the problem and 64 bit software on a 64 bit software will be the solution.

Anyhow, if you have any information or ideas, I would appreciate it.

J.
 
Old 11-10-2007, 04:08 AM   #2
Bruce Hill
HCL Maintainer
 
Registered: Jun 2003
Location: Tupelo, MS
Distribution: Gentoo
Posts: 6,926

Rep: Reputation: 124Reputation: 124
Are you using NVIDIA-Linux-x86_64-100.14.19-pkg2.run or NVIDIA-Linux-x86-100.14.19-pkg1.run?
Did you get this file from Nvidia?

What do you mean by "The generic vesa driver works just fine, but I kind of need hardware acceleration"?

My system is Slackware-12.0 with the default kernel and Xorg:
Code:
mingdao@wired_silas:~$ Xorg :0.0 -version

X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Slackware 12.0 Slackware Linux Project
Current Operating System: Linux wired_silas 2.6.21.5-smp #2 SMP Tue Jun 19 14:58:11 CDT 2007 i686
Build Date: 09 May 2007
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Module Loader present
I've got the same (well, almost) video card. Mine is a little bit tricked, being a Galaxy card produced here in China:
Code:
01:00.0 VGA compatible controller: nVidia Corporation GeForce 7300 GT (rev a2) (prog-if 00 [VGA])
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 248 (1250ns min, 250ns max)
        Interrupt: pin A routed to IRQ 20
        Region 0: Memory at fc000000 (32-bit, non-prefetchable) [size=16M]
        Region 1: Memory at d0000000 (32-bit, prefetchable) [size=256M]
        Region 2: Memory at fb000000 (32-bit, non-prefetchable) [size=16M]
        [virtual] Expansion ROM at fd800000 [disabled] [size=128K]
        Capabilities: [60] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [44] AGP version 3.0
                Status: RQ=256 Iso- ArqSz=0 Cal=3 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3+ Rate=x4,x8
                Command: RQ=32 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x8
However, my glxgears is the same with "VESA framebuffer" as it is with your "nVidia" setting:
Code:
mingdao@wired_silas:~$ cat glxgears-vesa
mingdao@wired_silas:~$ glxgears
46266 frames in 5.0 seconds = 9253.155 FPS
47567 frames in 5.0 seconds = 9513.362 FPS
47551 frames in 5.0 seconds = 9510.162 FPS
47425 frames in 5.0 seconds = 9484.892 FPS
47534 frames in 5.0 seconds = 9506.718 FPS
47510 frames in 5.0 seconds = 9501.876 FPS
47434 frames in 5.0 seconds = 9486.734 FPS
47582 frames in 5.0 seconds = 9516.215 FPS
47109 frames in 5.0 seconds = 9421.693 FPS
XIO:  fatal IO error 22 (Invalid argument) on X server ":0.0"
      after 39 requests (39 known processed) with 0 events remaining.
XIO:  fatal IO error 22 (Invalid argument) on X server ":0.0"
      after 39 requests (39 known processed) with 0 events remaining.
Code:
mingdao@wired_silas:~$ cat glxgears-nvidia
mingdao@wired_silas:~$ glxgears
47842 frames in 5.0 seconds = 9568.272 FPS
46926 frames in 5.0 seconds = 9385.140 FPS
47872 frames in 5.0 seconds = 9574.362 FPS
48011 frames in 5.0 seconds = 9602.092 FPS
47922 frames in 5.0 seconds = 9584.256 FPS
48135 frames in 5.0 seconds = 9626.821 FPS
48151 frames in 5.0 seconds = 9630.183 FPS
47671 frames in 5.0 seconds = 9534.110 FPS
48249 frames in 5.0 seconds = 9649.769 FPS
47970 frames in 5.0 seconds = 9593.875 FPS
29925 frames in 5.2 seconds = 5783.387 FPS
XIO:  fatal IO error 22 (Invalid argument) on X server ":0.0"
      after 36 requests (36 known processed) with 0 events remaining.
XIO:  fatal IO error 22 (Invalid argument) on X server ":0.0"
      after 36 requests (36 known processed) with 0 events remaining.
Is that all that your Backtrace output?

Last edited by Bruce Hill; 11-10-2007 at 04:12 AM.
 
Old 11-10-2007, 12:43 PM   #3
jroggow
Member
 
Registered: Mar 2006
Distribution: Slackware
Posts: 33

Original Poster
Rep: Reputation: 15
Hello;

I'm using the NVIDIA-Linux-x86-100.14.19-pkg1.run from nVidia. It seems when I was working on this project several months back I discovered that the vesa driver doesn't support hardware acceleration, but I may be mistaken. In any case, at the time I had MythTV installed and my tuner card working but I only got about 5 frames per second. A little poking around and I found that my machine wasn't using hardware acceleration. Also at the time the nVidia drivers weren't working with the 2.6 kernel so I put the project on hold.

Anyhow, the snippet of Xorg.0.log I posted is the complete backtrace. The rest of the log file is informational module loading. No other errors are reported.

I did find that I don't have a glx library installed. The nVidia installer does install the nVidia glx module and it seems to load properly according to the log file. I'm going to install Mesa 3D and see how that does. And perhaps strace will give me some more information.

Thanks,

J.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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 Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Nvidia Drivers fail after install of transcode wabbalee Linux - Hardware 15 12-13-2006 07:52 AM
New Xorg broke my nvidia drivers? GL1800 Fedora 3 09-01-2005 08:34 AM
Xorg and NVIDIA drivers crash and burn JamieMcLaughlin Linux - Hardware 3 05-07-2005 02:00 PM
XOrg Hangs With NVidia Drivers damicatz Linux - Software 3 08-26-2004 05:39 AM
Mandrake 10.0/AMD 64/Nvidia drivers fail TravisOSF Mandriva 6 05-21-2004 12:02 AM


All times are GMT -5. The time now is 03:09 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration