Nvidia Driver Caught Signal 11

monsieurdozier · 2007-08-30 00:29:44

After receiving word that I should try Archlinux, I gave is a shot.

I followed the Beginner's Guide for installation here: http://wiki.archlinux.org/index.php/Beginners_Guide

I installed my Nvidia GeForce 2 MX/MX Driver as it told me. Downloading the Nvidia 96xx driver. I ran nvidia-xconfig and it did it's thing. I installed Xterm and ran it to see if everything's working okay. My screen went black and after a few seconds several large grey boxes appeared on my screen with small flashing white boxes in them. I Ctrl+Alt+Backspaced out of xterm and created an xorg.conf file, not having done so previously. I reran nvidia-config, this time it changing xorg.conf. I ran xterm againa nd I got the same problem.

The only deciferable information I can get off of my screen is Fatal Server Error. Signal 11 Caught. Server aborting.

Any help will be glady appreciated.

Monsieur Dozier

fwojciec · 2007-08-30 00:33:25

What happens when you type "startx"? Could you try that and then post the contents of the file /var/log/Xorg.0.log file? Also, while we at it, could you post the contents of your xorg.conf file? That should give us something more concrete to work with...

Welcome to arch

monsieurdozier · 2007-08-30 01:56:51

Okay, What's in the Log File:

X Windows System Version 7.2.0
Release Date: 22 January 2007
X Protocol Version 11, Revision 0, Release 7.2
Build Operating System: UNKNOWN
Current Operating System: Linux localhost 2.6.22-ARCH #1 SMP PREEMPT Thu Augh 2 $
Build Date: 08 April 2007
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 30 00:36:11 2007
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Layout 0"
(**) |-->Screen "Screen 0" (0)
(**) | |-->Monitor "Monitor 0"
(**) | |-->Device "Device0"
(**) |-->Input Device "Keyboard0"
(==) Keyboard:CustomKeyCode disabled
(**) |-->Input Device "Mouse0"
(WW) 'fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi".
Entry deleted from font path.
(Run 'mkfontdir' on "/usr/share/fonts/100dpi"
(WW) 'fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi".
Entry deleted from font path.
(Run 'mkfontdir' on "/usr/share/fonts/75dpi"
(WW) The directory "usr/share/fonts/TTF" does not exist.
Entry deleted from font path.
(WW) The directory "usr/share/fonts/Type1" does not exist.
Entry deleted from font path.
(==)FontPath set to:
/usr/share/fonts/misc
(**) RgbPath set to "/usr/lib/X11/rgb"
(==) Mondule Path set to "usr/lib/xorg/modules"
(WW_ Open ACPI failed (var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or KERNEL
(II) Loader magic: 0x81c44a0
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.3
X.Org Video Driver: 1.1
X.Org XInput driver : 0.7
X.Org Server Extension : 0.3
X.Org Font Renderer : 0.5
(II) Loader running on Linux
(II) Load Module: "pcidata"
(II) Loading /usr/lib/xorg/modules//libpcidata.so
(II) Module pcidata: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.1
(--) Using VT number 7

(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 1106,0691 card 0000,0000 rev c4 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 1106,8598 card 0000,0000 rev 00 class 06,04,00 hdr 01
(II) PCI: 00:07:0: chip 1106,0596 card 1106,0000 rev 23 class 06,01,00 hdr 80
(II) PCI: 00:07:1: chip 1106,0571 card 0000,0000 rev 10 class 01,01,8a hdr 00
(II) PCI: 00:07:2: chip 1106,3038 card 0925,1234 rev 11 class 0c,03,00 hdr 00
(II) PCI: 00:07:3: chip 1106,3050 card 0000,0000 rev 30 class 06,00,00 hdr 00
(II) PCI: 00:0f:0: chip 1274,1371 card 1274,1371 rev 08 class 04,01,00 hdr 00
(II) PCI: 00:12:0: chip 10b7,9055 card 10b7,9055 rev 24 class 02,00,00 hdr 00
(II) PCI: 01:00:0: chip 10de,0110 card 10de,0110 rev b2 class 03,00,00 hdr 00
(II) PCI: End of PCI scan
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 0 I/O range:
[0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[b]
(II) Bus 0 non-prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[b]
(II) Bus 0 prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[b]
(II) PCI-to-PCI Bridge:
(II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x000c (VGA_EN is set)
(II) Bus 1 non-prefetchable memory range:
[0] -1 0 0xdc000000 - 0xddffffff (0x2000000) MX[b]
(II) Bus 0 prefetchable memory range:
[0] -1 0 0xd0000000 - 0xd7ffffff (0x8000000) MX[b]
(II) PCI-to-ISA bridge:
(II) Bus -1: bridge is at (0:7:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
(--)PCI:*(1:0:0) vVidia Corporation NV11 [GeForce 2 MX/MX 400] rev 178, Mem @ 0$
(II) Addressable resource ranges are

(I'm typing this manually, so I'll come back to all this hex stuff if I need to, I'm going to skip to all the warnings and errors.)

(Skipping down a bit)

(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:

(More hex stuff. Please do tell me if I need to post all this. I'm just goin crosseyed looking at it.)

(EE) NVIDIA(0): Error recovery failed.
(EE) NVIDIA(0): *** Aborting ***
(II) NVIDIA(0): Setting mode "1280x1024"
(WW) NVIDIA(0): The NVIDIA X driver has encountered too many errors. Falling
(WW) NVIDIA(0): falling back to legacy PCI mode.
(EE) NVIDIA(0): Error recovery failed.
(EE) NVIDIA(0): *** Aborting ***
(EE) NVIDIA(0): Error recovery failed.
(EE) NVIDIA(0): *** Aborting ***
(II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(**) Option "dpms"
(**) NVIDIA(0): DPMS enabled
(II) Loading extension NC-CONTROL
(EE) NVIDIA(0): Error recovery failed.
(EE) NVIDIA(0): *** Aborting ***
(==) RandR enabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension XAccessControlExtension
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(II) Initializing extension GLX
(**) Option "CoreKeyboard"
(**) Keyboard0: Core Keyboard
(**) Option "Protocol" "standard"
(**) Keyboard0: Protocol: standard
(**) Option "AutoRepear" "500 30"
(**) Option "XkbRules" "xorg"
(**) Keyboard0: XkbRules: "xorg"
(**) Option "Xkbmodel" "pc105"
(**) Keyboard0: XkbModel: "pc105"

(More Mouse and Keyboard setup stuff)

(--) Mouse0: PnP-detected protocol: "ExplorerPS/2"
(II) Mouse0: ps2EnableDataReporting: succeeded
(EE) NVIDIA(0): Error recovery failed.
(EE) NVIDIA(0): *** Aborting ***
(EE) NVIDIA(0): Error recovery failed.
(EE) NVIDIA(0): *** Aborting ***
(EE) NVIDIA(0): Error recovery failed.
(EE) NVIDIA(0): *** Aborting ***
(EE) NVIDIA(0): Error recovery failed.
(EE) NVIDIA(0): *** Aborting ***

Backtrace:
0: X(xf86SigHandler+0x84) [0x80d0574]
1: [0xb7f99420]

Fatal Server Error:
Caught Signal 11. Server aborting

(WW) NVIDIA(0): Failed to free video decoder object
(WW) NVIDIA(0): Failed to tear down video overlay

(I'll put in the x.org file here in a bit. I hope this helps for now.)

Monsieur Dozier

Last edited by monsieurdozier (2007-08-30 01:57:10)

fwojciec · 2007-08-30 04:01:25

Instead of typing things out you can use, for example, a usb stick if you have it to copy the files to a computer where you can cut and paste...

Insert usb stick, and check what it's called by typing (as root, actually all commands here need to be used as root):

1) "fdisk -l" - see what device is your usb stick (it should be /dev/sd[something]. /dev/sdc or something like that)
2) make a mountpoint in /mnt folder: "mkdir /mnt/usbstick"
3) mount the usb stick: "mount /dev/sd? /mnt/usbstick" (use the sd-something name from the fdisk -l output)
4) "cp -v /var/log/Xorg.0.log /mnt/usbstick" (-v options basically gives you confirmation what was copied)
5) "cp -v /etc/X11/xorg.conf /mnt/usbstick"
6) "umount /dev/sd?" (again, use the actual device name)

(I think something like this should work)
Now you can just open these files on another computer and copy and paste...

As for what you've typed thus far... apparently the nvidia driver fails to load for some reason - all the (EE) entries basically mean errors.

Try doing what this wiki says (http://wiki.archlinux.org/index.php/Xorg7), the part with hwd specifically, and try using the xorg.conf that hwd creates for you.

I won't be back at my computer until tomorrow, so I won't be able to help for now, but maybe someone else will be able to come up with some suggestions. Don't get discouraged, the beginnings are difficult but as long as you're willing to learn you will be able to figure it out in the end. Good luck!

harlekin · 2007-08-30 04:53:56

I guess he is willing to learn as he typed a bunch of logs. I hadn't done that.

Anyway, please use code tags the next time or a pastebin for long logs: pastebin.archlinux.org. This is clearer.

To you problem: I suggest tweaking your xorg.conf using the vesa driver instead of nvidia until everything is configure properly (with vesa) and then you can easily switch to the nvidia driver by just changing one line. This should eliminate the possible sources of the problem as the vesa driver happens to be less error prone.

Misfit138 · 2007-08-30 12:26:37

harlekin wrote:

I guess he is willing to learn as he typed a bunch of logs. I hadn't done that.
Anyway, please use code tags the next time or a pastebin for long logs: pastebin.archlinux.org. This is clearer.
To you problem: I suggest tweaking your xorg.conf using the vesa driver instead of nvidia until everything is configure properly (with vesa) and then you can easily switch to the nvidia driver by just changing one line. This should eliminate the possible sources of the problem as the vesa driver happens to be less error prone.

Excellent advice, I agree. Get it going with Vesa and then tweak over to nVIDIA.

monsieurdozier · 2007-08-30 13:51:31

I tried mounting my USB stick, but to no avail. It kept asking for the file system type, which I assumed meant FAT, but apparently not because it didn't recognize it. So no more log files until I can either figure this out, or have the time and patience to type it all up again.

I took the other suggestions and editted my xorg.conf. I changed the Driver "nvidia" to Driver "vesa". Went back to my user and startx. My monitor menu said, OUT OF FREQUENCY RANGE Attention Out of Range H: 74.8KHz V: 59.8Hz I'm using an old Dell 17" CRT Monitor that came with my other computer.

I also tried reinstalling nvidia-96xx and XF86-video-vesa. I still get the respective errors.

Monsieur Dozier

Last edited by monsieurdozier (2007-08-30 13:53:00)

harlekin · 2007-08-30 14:41:57

Double check the values for HorizSync and VertSync device options and adjust them according to your monitor's manual. (Or according to some websites if you don't want to search for the manual.)

Do you have a window manager installed and specified in ~/.xinitrc? A friend of mine kept getting similar errors because of this. Though I thought X has it's own "fallback" WM. Seems not to be the case anymore. Maybe since it's modular.

To send an file to a pastebin without the ability of copy and paste, you can use curl. Though I don't know the syntax to accomplish this.

Last edited by harlekin (2007-08-30 14:43:36)

fwojciec · 2007-08-30 18:19:44

As far as mounting is concerned (I guess my advice was incomplete)
try something like "mount -t vfat /dev/sd[something] /mnt/usbstick"

If you keep having problems with x configuration, here is another idea, try downloading something like "archie" (it's an arch based live cd that can also install arch linux - more info here: http://bbs.archlinux.org/viewtopic.php?id=35876) and run it on your computer. It should be able to automatically configure xorg for you - you could run the archie cd on your computer, copy the xorg.conf that archie generates via a usb stick to your arch install and that, if all goes well, should get your x server working at least.

monsieurdozier · 2007-08-30 18:21:45

harlekin wrote:

Double check the values for HorizSync and VertSync device options and adjust them according to your monitor's manual. (Or according to some websites if you don't want to search for the manual.)

Where would I find these values? (What file on the computer.)

I created my ~/.xinitrc and all that is in there is:

exec xterm

Monsieur Dozier

Edit:

Okay here's the log and xorg.conf respectively:

http://pastebin.archlinux.org/13583

http://pastebin.archlinux.org/13584

Last edited by monsieurdozier (2007-08-30 18:31:02)

fwojciec · 2007-08-30 19:03:28

Great! It seems like we are moving closer to a solution. The only actual xorg error I see at the moment is this:

(EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)

which is because you're using vesa driver not nvidia. This can be fixed by commenting out a line in Section "Module: (line 24 in pastebin) so it looks like this:

#Load           "glx"

Secondly, I would make some changes to your Screen and Monitor sections, since there are warning in the logs about xorg not being able to determine the correct resolution for your screen.

1) Try adding 'Option "DMPS"' to the Section Monitor - for example in my xorg.conf it looks like this.

Section "Monitor"
        Identifier      "SyncMaster 940bx"
        Option          "DPMS"                        #<-------------------
EndSection

This should enable xorg to automatically detect the correct refresh rates for your screens and such, as long as your monitor is not completely ancient.

2) You have to set the correct resolution for your monitor. For reference, this is what the "Screen" section in my xorg.conf looks like:

Section "Screen"
        Identifier      "Default Screen"
        Device          "NVIDIA GeForce 7900GS"
        Monitor         "SyncMaster 940bx"
        DefaultDepth    24                            #<-------------------
        SubSection "Display"
                Viewport        0 0
                Depth           24
                Modes           "1280x1024" "1024x768"          #<-----------------
        EndSubSection
EndSection

You should try adding the "Default Depth" (24 is pretty much the standard choice here) line right after the "monitor" line to your xorg.conf (after line 61 or so) and also Modes line to the appropriate Subsection "Display" part (the one that uses your specified default depth, for example 24, is the most important as it will be used if only possible). Use the resolution that you need for your setup, of course. Hopefully this explanation is not too confusing

3) "startx" needs to point to something meaningful. Personally I've never tried executing x with just "exec xterm", so I can't be sure that this would work... I would suggest installing something like xfce4 for now (pacman -S xfce4) and adding "exec xfce4-session" to your .xinitrc instead. That should work and give you a graphical environment to work with for now. Later you could remove it and installing different DE/WM if you prefer something else instead.

Last edited by fwojciec (2007-08-30 19:06:16)

monsieurdozier · 2007-08-31 01:44:20

Well, after doing what you said, I got xfce working. Thanks much.

Time to give it Arch a spin.

Monsieur Dozier

fwojciec · 2007-08-31 03:20:50

Cool - have fun setting up Arch the way you like it!

duko · 2007-11-20 16:50:06

Hello all,

I have a similar error unless the Xorg log-file and version of nvidia card. My log is OK except last few lines:

....
<many lines skipped>
...
(II) Mouse0: ps2EnableDataReporting: succeeded

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x6a) [0x49518a]
1: /lib/libc.so.6 [0x2b69078e5120]
2: /lib/libc.so.6(realloc+0x76) [0x2b6907926d76]
3: /usr/bin/X(Xrealloc+0x1b) [0x56296b]
4: /usr/bin/X [0x4baa29]
5: /usr/lib/xorg/modules/drivers//nvidia_drv.so [0x2b6909d5f7a3]

Fatal server error:
Caught signal 11. Server aborting

(II) Screen 0 shares mem & io resources
(II) Screen 1 shares mem & io resources

<EOF>

My ArchLinux and my Xorg version:

X.Org X Server 1.4.0
Release Date: 5 September 2007
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-rc1-ARCH x86_64
Current Operating System: Linux mypc 2.6.23-ARCH #1 SMP PREEMPT Sat Nov 17 18:23:00 CET 2007 x86_64
Build Date: 07 November 2007 10:56:33AM

Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present

nvidia is GeForce 7, tried to use both nvidia 100.14.19-5 (http://www.archlinux.org/packages/5419/) or driver from nvidia of the same version (NVIDIA-Linux-x86_64-100.14.19-pkg2.run).

Nothing helps. The xorg.conf was OK untill upgrade to 1.4.0 of the xorg-server during complete system upgrade.

Any hints?

Thank you!

Arch Linux

#1 2007-08-30 00:29:44

Nvidia Driver Caught Signal 11

#2 2007-08-30 00:33:25

Re: Nvidia Driver Caught Signal 11

#3 2007-08-30 01:56:51

Re: Nvidia Driver Caught Signal 11

#4 2007-08-30 04:01:25

Re: Nvidia Driver Caught Signal 11

#5 2007-08-30 04:53:56

Re: Nvidia Driver Caught Signal 11

#6 2007-08-30 12:26:37

Re: Nvidia Driver Caught Signal 11

#7 2007-08-30 13:51:31

Re: Nvidia Driver Caught Signal 11

#8 2007-08-30 14:41:57

Re: Nvidia Driver Caught Signal 11

#9 2007-08-30 18:19:44

Re: Nvidia Driver Caught Signal 11

#10 2007-08-30 18:21:45

Re: Nvidia Driver Caught Signal 11

#11 2007-08-30 19:03:28

Re: Nvidia Driver Caught Signal 11

#12 2007-08-31 01:44:20

Re: Nvidia Driver Caught Signal 11

#13 2007-08-31 03:20:50

Re: Nvidia Driver Caught Signal 11

#14 2007-11-20 16:50:06

Re: Nvidia Driver Caught Signal 11

Board footer