Nvidia HW probs? [fixed]

For whatever reason, my nvidia card has decided not to talk to the drivers, or something. I can delete my xorg.conf, and I'm assuming use the riva driver, have no probs, everything loads, looks good. But when I try to load the nvidia driver, I get
NVIDIA: could not open the device file /dev/nvidia0 (Input/output error).
(EE) NVIDIA(0): The NVIDIA kernel module does not appear to be receiving
(EE) NVIDIA(0): interrupts generated by the NVIDIA graphics device.
(EE) NVIDIA(0): Please see the FREQUENTLY ASKED QUESTIONS section in the
(EE) NVIDIA(0): README for additional information.
(EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device!
(EE) NVIDIA(0): *** Aborting ***
(EE) Screen(s) found, but none have a usable configuration.
Fatal server error:
no screens found
with the verbosity set to maximum. dmesg provides nothing, so I'm pretty lost. I've googled this and it always comes up as a supposed hardware problem, but if it's hardware, how can the default linux drivers work?

Yup, I tried many variations on un/installing the kernel and re/loading the nvidia drivers/module with no luck. I had no clue what to do, so I just figured it'd be best to swap the card out. I ended up taking it out and putting it back in since I couldn't find the card I wanted to replace it with, and now it works. Somehow?
thanks for the advice in any event.

Similar Messages

[SOLVED] Nvidia problems after fixing glibc borkgasm... [SOLVED]

First -- Yes, I was an idiot and borked my system. I had been on vacation for a week and came to a mile long list of updates. I also went ahead and ran everything without looking for any relevant news bits on the home page.
Second -- I'm mostly certain that I've gotten that all straightened out.
However -- Ever since nothing installed from the nvidia-utils package will run.
hal@oa ~ > nvidia-settings
bash: /usr/bin/nvidia-settings: No such file or directory
hal@oa ~ > file /usr/bin/nvidia-settings
/usr/bin/nvidia-settings: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.4.0, stripped
hal@oa ~ > uname -m
x86_64
it does however work if i use
$ /lib/ld-linux-x86-64.so.2 /usr/bin/nvidia-settings
Andy ideas?
[SOLUTION]
I swear I had done it again already after fixing the /lib symlink, but for s/gs I ran one more pacman -Sy glibc lib32-glibc, and it seems to have gone through this time.
Pacman REALLY needs some form of news alert to let you know about updates like that. Nothing obtrusive, just a nice little reminder to check the homepage for notices. It would save me a _LOT_ of money on asprin.
Last edited by HalJordan (2012-07-16 02:34:28)

--Fixed the name.
--And that's the first thing I did. After running pacman -Rdd on anything nvidia, I ran pacman -Sy on everything removed. After that didn't fix it I came looking here, where I found the bit about the linker. It was frustrating as hell, I kept getting back "File or directory not found" but ls showed it right there.

HT203254 MBP Nvidia not fully fixed - Apple, please, company image at stake here

I have a case opened regarding a MBP 2008, NVidia error as stated by others. I have opened a ticket to Apple and they also claim that even AHT shows a VideoAdapter Hardware error, they say that the recall is for the NVidia "specific test" that they do. I particularly will try to show to them that there is no point delaying the replacement of the failing components, bacause this is the right thing to do when you are a big company and you expect to have better (and pricy) hardware with a theoretical better lifetime. I have older (and newer MBP) and this one failed. Not sure if this the start of a sequence of frustrations on Apple HW. I hope the Apple Support team keep an eye on this post and all other complains and just fix the customer request. nVdia may be good but they should simply put the dolars aside and think on the product image and fix all and every computer that shows defective under "close" relatonship to the problem. I do not believe they can state that half of the chip failed bacause of manufacturing and the other half due to regular use. This is insane and we (the customers) paid a LOT for high quality devices, which is not the case. I just hope that the Company IMAGE is also worth preserving. My contact information is [email protected]

This is one of them times I should have wrote down what steps i had completed and had not, I reread the information on this page, http://wiki.manjaro.org/index.php?title … on_Startup. Obviously i missed a vitel step while i was half asleep a few nights ago... Anyway This is solved.
P.S. I will be getting a refurbished Dell Latitude e7440 next week and I will be playing with it and a pure Arch experiance, can't wait. Catch you later.

Nvidia 295.40 fix

Hi all. I was wondering if there is any fix on the horizion for older nvidia cards other than downgrading to 295.33, and if so, how can one know when it's safe to upgrade. Will the updated driver show up with a pacman -Syu?
Thanks

This isn't an Arch packing problem, it is an upstream problem. Arch will package what ever version upstream releases when upstream releases it. Updates are available through pacman as you noted.

Nvidia Failed, Apple fixing free of charge.

I have a 2007 Mac Book Pro. The nvidia chipset failed, no display and the external nothing as well. It would boot with the chime and hard drive chattering away like normal, but nothing on the screen (nor external).
Made a appointment with genius bar and they ran some tests, tried everytying, and said it was covered under some nvidia whatever and everything will be fixed no charge to me.
I was very impressed, I arrived on time and was called up to the bar on time.
I miss having my laptop, but oh well.
Anyway, just a good experience to relate.
That darn store was so crowded, i was sure that i was in for a long wait no matter that i had a reservation. But it all went smooth.

Hi Jason,
Unfortunately I can't see my MacBook Pro with the System Restore disc inserted on my internal network using Remote Desktop, possibly because it doesn't load a network driver from the DVD/CD startup system?
Anyway, I booked a genius appointment. I described in detail what had happened and the methods I had used to try a fix - the assistant knowingly nodded and plugged in what looked like an external drive with a nVidia sticker on it into my MacBookPro. A dialogue box popped up and he was able to determine immediately that my mac was eligible for the replacement of the whole motherboard - at nVidia's expense. He said that they had seen many of these Macs coming back recently and had a back order on the parts taking between 7-14 days.
I asked about the graphics card and what the replacement would be, but he was unsure. I originally bought this MacBookPro from the Apple refurb store. I'm just glad that I'm not having to pay the 750+ UK pounds he guessed at for an out of warranty motherboard replacement :–)

Nvidia sound driver fix for Neo 2

Hi
I was after the fix that gets the nvidia sound drivers to work for this motherboard or for most nf3 chipset motherboards.
I found a thread before that details what needs to be done but i have lost it now cant find it anymore. If anyone knows how to fix this dreadful sound issue on the Neo2 it would be much appreciated.
Cheers

y'ain't got an nVidia soundchip on that mobo, but a realtec... so install the sound drivers from cd, or the realtec website, not the sounddrivers from the nvidia chipset install thingy

Cannot load nvidia driver module [SOLVED]

OK so for some reason I can no longer load the nvidia (proprietary) driver.
I have a laptop with optimus, on board intel and discrete nvidia GTX680M. I use this laptop for cuda development so I don't care about games etc, I just need the driver loaded to debug and run my cuda apps. bbswitch still works fine as does bumblebee which I don't use normally but I do have it setup and running in case. Also I didn't really work much on coding last week so not sure exactly when this started.
So here is what happens when I try to insert the nvidia module or use optirun:
$ sudo modprobe nvidia
modprobe: ERROR: could not insert 'nvidia': No such device
$ sudo insmod nvidia
insmod: ERROR: could not load module nvidia: No such file or directory
$ optirun -vv glxspheres
[ 27.485342] [DEBUG]Reading file: /etc/bumblebee/bumblebee.conf
[ 27.485506] [INFO]Configured driver: nvidia
[ 27.485635] [DEBUG]optirun version 3.2.1 starting...
[ 27.485642] [DEBUG]Active configuration:
[ 27.485645] [DEBUG] bumblebeed config file: /etc/bumblebee/bumblebee.conf
[ 27.485662] [DEBUG] X display: :8
[ 27.485674] [DEBUG] LD_LIBRARY_PATH: /usr/lib/nvidia:/usr/lib32/nvidia
[ 27.485676] [DEBUG] Socket path: /var/run/bumblebee.socket
[ 27.485679] [DEBUG] Accel/display bridge: primus
[ 27.485681] [DEBUG] VGL Compression: xv
[ 27.485684] [DEBUG] VGLrun extra options:
[ 27.485686] [DEBUG] Primus LD Path: /usr/lib:/usr/lib32
[ 27.560627] [INFO]Response: No - error: Could not load GPU driver
[ 27.560647] [ERROR]Cannot access secondary GPU - error: Could not load GPU driver
[ 27.560651] [DEBUG]Socket closed.
[ 27.560666] [ERROR]Aborting because fallback start is disabled.
[ 27.560671] [DEBUG]Killing all remaining processes.
I don't have an xorg file for the intel gpu.
device nodes are created:
$ ls /dev/ | grep nv
crw-rw-rw- 1 root root 195, 0 Sep 24 14:58 nvidia0
crw-rw-rw- 1 root root 195, 255 Sep 24 14:58 nvidiactl
log info:
$cat /var/log/Xorg.0.log | grep EE
[ 3.385] Current Operating System: Linux gpumonster 3.11.1-1-ARCH #1 SMP PREEMPT Sat Sep 14 19:30:21 CEST 2013 x86_64
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 4.299] Initializing built-in extension MIT-SCREEN-SAVER
[ 4.308] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 4.308] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 4.309] (EE) Failed to load module "fbdev" (module does not exist, 0)
$ cat /var/log/Xorg.8.log
[ 11367.762]
X.Org X Server 1.14.3
Release Date: 2013-09-12
[ 11367.762] X Protocol Version 11, Revision 0
[ 11367.762] Build Operating System: Linux 3.11.0-1-ARCH x86_64
[ 11367.762] Current Operating System: Linux gpumonster 3.11.1-1-ARCH #1 SMP PREEMPT Sat Sep 14 19:30:21 CEST 2013 x86_64
[ 11367.762] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=1c3a736e-6aab-45e1-a9ad-5d2f6195cd7d ro quiet
[ 11367.762] Build Date: 13 September 2013 01:28:59PM
[ 11367.762]
[ 11367.762] Current version of pixman: 0.30.2
[ 11367.762] Before reporting problems, check [url]http://wiki.x.org[/url]
to make sure that you have the latest version.
[ 11367.762] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 11367.762] (==) Log file: "/var/log/Xorg.8.log", Time: Thu Sep 19 23:04:24 2013
[ 11367.762] (++) Using config file: "/etc/bumblebee/xorg.conf.nvidia"
[ 11367.762] (++) Using config directory: "/etc/bumblebee/xorg.conf.d"
[ 11367.762] (==) ServerLayout "Layout0"
[ 11367.762] (==) No screen section available. Using defaults.
[ 11367.762] (**) |-->Screen "Default Screen Section" (0)
[ 11367.762] (**) | |-->Monitor "<default monitor>"
[ 11367.762] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[ 11367.762] (**) | |-->Device "DiscreteNvidia"
[ 11367.762] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 11367.762] (**) Option "AutoAddDevices" "false"
[ 11367.762] (**) Option "AutoAddGPU" "false"
[ 11367.762] (**) Not automatically adding devices
[ 11367.762] (==) Automatically enabling devices
[ 11367.762] (**) Not automatically adding GPU devices
[ 11367.762] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 11367.762] Entry deleted from font path.
[ 11367.762] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 11367.762] Entry deleted from font path.
[ 11367.762] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 11367.762] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 11367.762] Entry deleted from font path.
[ 11367.762] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 11367.762] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/
[ 11367.762] (++) ModulePath set to "/usr/lib/nvidia/xorg/,/usr/lib/xorg/modules"
[ 11367.762] (==) |-->Input Device "<default pointer>"
[ 11367.763] (==) |-->Input Device "<default keyboard>"
[ 11367.763] (==) The core pointer device wasn't specified explicitly in the layout.
Using the default mouse configuration.
[ 11367.763] (==) The core keyboard device wasn't specified explicitly in the layout.
Using the default keyboard configuration.
[ 11367.763] (II) Loader magic: 0x7fdc20
[ 11367.763] (II) Module ABI versions:
[ 11367.763] X.Org ANSI C Emulation: 0.4
[ 11367.763] X.Org Video Driver: 14.1
[ 11367.763] X.Org XInput driver : 19.1
[ 11367.763] X.Org Server Extension : 7.0
[ 11367.763] (II) xfree86: Adding drm device (/dev/dri/card1)
[ 11367.763] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 11367.763] setversion 1.4 failed
[ 11367.764] (--) PCI:*(0:1:0:0) 10de:11a0:1558:5105 rev 161, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 11367.764] Initializing built-in extension Generic Event Extension
[ 11367.764] Initializing built-in extension SHAPE
[ 11367.764] Initializing built-in extension MIT-SHM
[ 11367.764] Initializing built-in extension XInputExtension
[ 11367.764] Initializing built-in extension XTEST
[ 11367.764] Initializing built-in extension BIG-REQUESTS
[ 11367.764] Initializing built-in extension SYNC
[ 11367.764] Initializing built-in extension XKEYBOARD
[ 11367.764] Initializing built-in extension XC-MISC
[ 11367.764] Initializing built-in extension SECURITY
[ 11367.764] Initializing built-in extension XINERAMA
[ 11367.764] Initializing built-in extension XFIXES
[ 11367.764] Initializing built-in extension RENDER
[ 11367.764] Initializing built-in extension RANDR
[ 11367.764] Initializing built-in extension COMPOSITE
[ 11367.764] Initializing built-in extension DAMAGE
[ 11367.764] Initializing built-in extension MIT-SCREEN-SAVER
[ 11367.764] Initializing built-in extension DOUBLE-BUFFER
[ 11367.764] Initializing built-in extension RECORD
[ 11367.764] Initializing built-in extension DPMS
[ 11367.764] Initializing built-in extension X-Resource
[ 11367.764] Initializing built-in extension XVideo
[ 11367.764] Initializing built-in extension XVideo-MotionCompensation
[ 11367.764] Initializing built-in extension XFree86-VidModeExtension
[ 11367.764] Initializing built-in extension XFree86-DGA
[ 11367.764] Initializing built-in extension XFree86-DRI
[ 11367.764] Initializing built-in extension DRI2
[ 11367.764] (II) LoadModule: "glx"
[ 11367.764] (II) Loading /usr/lib/nvidia/xorg/modules/extensions/libglx.so
[ 11367.773] (II) Module glx: vendor="NVIDIA Corporation"
[ 11367.773] compiled for 4.0.2, module version = 1.0.0
[ 11367.773] Module class: X.Org Server Extension
[ 11367.773] (II) NVIDIA GLX Module 325.15 Wed Jul 31 18:12:00 PDT 2013
[ 11367.773] Loading extension GLX
[ 11367.773] (II) LoadModule: "nvidia"
[ 11367.773] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 11367.773] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 11367.773] compiled for 4.0.2, module version = 1.0.0
[ 11367.773] Module class: X.Org Video Driver
[ 11367.773] (II) LoadModule: "mouse"
[ 11367.773] (II) Loading /usr/lib/xorg/modules/input/mouse_drv.so
[ 11367.773] (II) Module mouse: vendor="X.Org Foundation"
[ 11367.773] compiled for 1.14.0, module version = 1.9.0
[ 11367.773] Module class: X.Org XInput Driver
[ 11367.773] ABI class: X.Org XInput driver, version 19.1
[ 11367.773] (II) LoadModule: "kbd"
[ 11367.774] (WW) Warning, couldn't open module kbd
[ 11367.774] (II) UnloadModule: "kbd"
[ 11367.774] (II) Unloading kbd
[ 11367.774] (EE) Failed to load module "kbd" (module does not exist, 0)
[ 11367.774] (II) NVIDIA dlloader X Driver 325.15 Wed Jul 31 17:50:57 PDT 2013
[ 11367.774] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 11367.774] (--) using VT number 7
[ 11367.774] (II) Loading sub module "fb"
[ 11367.774] (II) LoadModule: "fb"
[ 11367.774] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 11367.774] (II) Module fb: vendor="X.Org Foundation"
[ 11367.774] compiled for 1.14.3, module version = 1.0.0
[ 11367.774] ABI class: X.Org ANSI C Emulation, version 0.4
[ 11367.774] (WW) Unresolved symbol: fbGetGCPrivateKey
[ 11367.774] (II) Loading sub module "wfb"
[ 11367.774] (II) LoadModule: "wfb"
[ 11367.774] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 11367.774] (II) Module wfb: vendor="X.Org Foundation"
[ 11367.774] compiled for 1.14.3, module version = 1.0.0
[ 11367.774] ABI class: X.Org ANSI C Emulation, version 0.4
[ 11367.774] (II) Loading sub module "shadow"
[ 11367.774] (II) LoadModule: "shadow"
[ 11367.774] (II) Loading /usr/lib/xorg/modules/libshadow.so
[ 11367.774] (II) Module shadow: vendor="X.Org Foundation"
[ 11367.774] compiled for 1.14.3, module version = 1.1.0
[ 11367.774] ABI class: X.Org ANSI C Emulation, version 0.4
[ 11367.774] (II) Loading sub module "ramdac"
[ 11367.774] (II) LoadModule: "ramdac"
[ 11367.774] (II) Module "ramdac" already built-in
[ 11367.774] (II) NVIDIA(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 11367.774] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[ 11367.775] (==) NVIDIA(0): RGB weight 888
[ 11367.775] (==) NVIDIA(0): Default visual is TrueColor
[ 11367.775] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 11367.775] (**) NVIDIA(0): Option "NoLogo" "true"
[ 11367.775] (**) NVIDIA(0): Option "ProbeAllGpus" "false"
[ 11367.775] (**) NVIDIA(0): Option "UseEDID" "false"
[ 11367.775] (**) NVIDIA(0): Option "UseDisplayDevice" "none"
[ 11367.775] (**) NVIDIA(0): Enabling 2D acceleration
[ 11367.775] (**) NVIDIA(0): Ignoring EDIDs
[ 11367.775] (**) NVIDIA(0): Option "UseDisplayDevice" set to "none"; enabling NoScanout
[ 11367.775] (**) NVIDIA(0): mode
[ 11368.299] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20130102)
[ 11368.300] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 680M (GK104) at PCI:1:0:0 (GPU-0)
[ 11368.300] (--) NVIDIA(0): Memory: 4194304 kBytes
[ 11368.300] (--) NVIDIA(0): VideoBIOS: 80.04.29.00.01
[ 11368.300] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 11368.300] (--) NVIDIA(0): Valid display device(s) on GeForce GTX 680M at PCI:1:0:0
[ 11368.300] (--) NVIDIA(0): none
[ 11368.300] (II) NVIDIA(0): Validated MetaModes:
[ 11368.300] (II) NVIDIA(0): "nvidia-auto-select"
[ 11368.300] (II) NVIDIA(0): Virtual screen size determined to be 640 x 480
[ 11368.300] (WW) NVIDIA(0): Unable to get display device for DPI computation.
[ 11368.300] (==) NVIDIA(0): DPI set to (75, 75); computed from built-in default
[ 11368.300] (--) Depth 24 pixmap format is 32 bpp
[ 11368.300] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
[ 11368.300] (II) NVIDIA: access.
[ 11368.304] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 11368.304] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 11368.304] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 11368.304] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 11368.304] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 11368.304] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 11368.304] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 11368.304] (II) NVIDIA(0): Config Options in the README.
[ 11368.304] (II) NVIDIA(0): Setting mode "nvidia-auto-select"
[ 11368.308] Loading extension NV-GLX
[ 11368.312] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 11368.312] (==) NVIDIA(0): Backing store disabled
[ 11368.312] (==) NVIDIA(0): Silken mouse enabled
[ 11368.312] (==) NVIDIA(0): DPMS enabled
[ 11368.312] Loading extension NV-CONTROL
[ 11368.312] (II) Loading sub module "dri2"
[ 11368.312] (II) LoadModule: "dri2"
[ 11368.312] (II) Module "dri2" already built-in
[ 11368.312] (II) NVIDIA(0): [DRI2] Setup complete
[ 11368.312] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 11368.312] (--) RandR disabled
[ 11368.316] (II) Initializing extension GLX
[ 11368.342] (II) Using input driver 'mouse' for '<default pointer>'
[ 11368.342] (**) Option "CorePointer" "on"
[ 11368.342] (**) <default pointer>: always reports core events
[ 11368.342] (WW) <default pointer>: No Device specified, looking for one...
[ 11368.422] (II) <default pointer>: Setting Device option to "/dev/input/mice"
[ 11368.422] (--) <default pointer>: Device: "/dev/input/mice"
[ 11368.422] (==) <default pointer>: Protocol: "Auto"
[ 11368.422] (**) <default pointer>: always reports core events
[ 11368.422] (**) Option "Device" "/dev/input/mice"
[ 11368.475] (==) <default pointer>: Emulate3Buttons, Emulate3Timeout: 50
[ 11368.475] (**) <default pointer>: ZAxisMapping: buttons 4 and 5
[ 11368.475] (**) <default pointer>: Buttons: 9
[ 11368.475] (II) XINPUT: Adding extended input device "<default pointer>" (type: MOUSE, id 6)
[ 11368.475] (**) <default pointer>: (accel) keeping acceleration scheme 1
[ 11368.475] (**) <default pointer>: (accel) acceleration profile 0
[ 11368.475] (**) <default pointer>: (accel) acceleration factor: 2.000
[ 11368.475] (**) <default pointer>: (accel) acceleration threshold: 4
[ 11368.475] (II) <default pointer>: Setting mouse protocol to "ExplorerPS/2"
[ 11368.769] (II) <default pointer>: ps2EnableDataReporting: succeeded
[ 11368.769] (II) LoadModule: "kbd"
[ 11368.769] (WW) Warning, couldn't open module kbd
[ 11368.769] (II) UnloadModule: "kbd"
[ 11368.769] (II) Unloading kbd
[ 11368.769] (EE) Failed to load module "kbd" (module does not exist, 0)
[ 11368.769] (EE) No input driver matching `kbd'
[ 11368.771] (II) config/udev: Adding input device Power Button (/dev/input/event6)
[ 11368.771] (II) AutoAddDevices is off - not adding device.
[ 11368.771] (II) config/udev: Adding input device Video Bus (/dev/input/event11)
[ 11368.771] (II) AutoAddDevices is off - not adding device.
[ 11368.771] (II) config/udev: Adding input device Video Bus (/dev/input/event9)
[ 11368.771] (II) AutoAddDevices is off - not adding device.
[ 11368.771] (II) config/udev: Adding input device Power Button (/dev/input/event5)
[ 11368.771] (II) AutoAddDevices is off - not adding device.
[ 11368.771] (II) config/udev: Adding input device Lid Switch (/dev/input/event3)
[ 11368.771] (II) AutoAddDevices is off - not adding device.
[ 11368.772] (II) config/udev: Adding input device Sleep Button (/dev/input/event4)
[ 11368.772] (II) AutoAddDevices is off - not adding device.
[ 11368.772] (II) config/udev: Adding drm device (/dev/dri/card1)
[ 11368.772] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 11368.772] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 11368.772] setversion 1.4 failed
[ 11368.772] (II) config/udev: Adding input device HP HP Link-5 micro dongle (/dev/input/event1)
[ 11368.772] (II) AutoAddDevices is off - not adding device.
[ 11368.773] (II) config/udev: Adding input device HP HP Link-5 micro dongle (/dev/input/event2)
[ 11368.773] (II) AutoAddDevices is off - not adding device.
[ 11368.773] (II) config/udev: Adding input device HP HP Link-5 micro dongle (/dev/input/mouse0)
[ 11368.773] (II) AutoAddDevices is off - not adding device.
[ 11368.773] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event12)
[ 11368.773] (II) AutoAddDevices is off - not adding device.
[ 11368.773] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=7 (/dev/input/event13)
[ 11368.773] (II) AutoAddDevices is off - not adding device.
[ 11368.773] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event14)
[ 11368.773] (II) AutoAddDevices is off - not adding device.
[ 11368.773] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event15)
[ 11368.773] (II) AutoAddDevices is off - not adding device.
[ 11368.774] (II) config/udev: Adding input device HDA Intel PCH Line Out (/dev/input/event16)
[ 11368.774] (II) AutoAddDevices is off - not adding device.
[ 11368.774] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event17)
[ 11368.774] (II) AutoAddDevices is off - not adding device.
[ 11368.774] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event18)
[ 11368.774] (II) AutoAddDevices is off - not adding device.
[ 11368.774] (II) config/udev: Adding input device BisonCam, NB Pro (/dev/input/event8)
[ 11368.774] (II) AutoAddDevices is off - not adding device.
[ 11368.774] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 11368.774] (II) AutoAddDevices is off - not adding device.
[ 11368.774] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event10)
[ 11368.774] (II) AutoAddDevices is off - not adding device.
[ 11368.775] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse1)
[ 11368.775] (II) AutoAddDevices is off - not adding device.
[ 11368.775] (II) config/udev: Adding input device PC Speaker (/dev/input/event7)
[ 11368.775] (II) AutoAddDevices is off - not adding device.
[ 11374.183] (II) UnloadModule: "mouse"
[ 11374.199] (II) NVIDIA(GPU-0): Deleting GPU-0
[ 11374.200] (EE) Server terminated successfully (0). Closing log file.
I'm not willing to give up and install/build the drivers from the cuda SDK just yet so any help would be greatly appreciated.
Last edited by tim (2013-10-02 08:20:49)

So in simple terms, the fix invovled ensuring the nvidia module is loaded before the bbswitch module. I'm not sure about the necessity of the things that follow but the fix may possibly also require removing bumblebee and possibly requires removing nvidia from repos and building the driver downloaded from nvidia.
This fix could be completely unrelated to the problems I was having with arch but I cannot verify the fix on arch specifically cos I installed every distro under the sun trying to get it all working and I got it to work on a non arch distro.
So... I'm not sure if I should really mark this a solved because I haven't/can't verify it on arch and technically the solution involved changing to another distro but in fact, I know it has absolutely nothing to do with arch since I saw the same behaviour on 3 other distros. If I have time, I will reinstall arch and verify but for the moment, I have a lot of work to catch up on now that I have a working nvidia driver I can actually use for dev
Anyway, what I think is going on is there is some bizarre issue with bbswitch that stops the nvidia driver from being found because on the current distro I have installed, if I have no bbswitch, no bumblebee and no nvidia modules loaded or services running etc. I can modprobe the nvidia driver and all works fine. I can then modprobe the bbswitch driver and that works too. IF I modprobe the bbswitch driver first and then modprobe the nvidia driver, I get this error that says the nvidia module cant be found. The location it prints is in some updates directory whcih is odd too because I installed from nvidia source and never installed updates at all and made sure that there were absolutely no repo nvidia drivers or updates etc.
Last edited by tim (2013-10-02 08:35:39)

[SOLVED] What is the nvidia-304xx-lts?

What is the nvidia-304xx-lts driver for a card? What is it for special about the "lts" ?
Last edited by amandus (2013-03-24 07:17:15)

This particular version enjoys long-term support (LTS) from upstream(NVIDIA), including security fixes and some feature backports, especially useful for Arch users seeking for the most stable packages arround.
But you must remember that because this packages are less times updated, it may come without support for some newer cards and capabilities.
Last edited by s1ln7m4s7r (2013-03-23 13:44:42)

Photoshop CS5 and NVIDIA GeForce GTX 295 Crash

My specifications:
Photoshop CS5 (x64)
Windows 7 x64
NVIDIA GeForce GTX 295 (latest v197.45 driver)
Intel i7 920 2.67 GHz
My card is listed as a tested card for CS5 and NVIDIA says this is compatible with CS5, but today after using it, my screen went blank and the display driver recovered itself. It took about 5 minutes until Photoshop CS5 became responsive again and the GPU features were disabled. I am going to try GPU advanced mode and basic mode instead of normal mode to see what happens, but this is a shame that I have issues like this. I also had issues with CS4 like this.
What I did to cause this issue: I clicked" Place.." to place an object and that is when it crashed. It only happens randomly as I use Photoshop. Please NVIDIA or Adobe fix this issue. I love the GPU features and I want to run them, but this crashing is annoying for spending so much on buying this product. I hate to have to pay to contact Adobe technical support, it should be included with the purchase of software!
How to fix this without having to go to basic GPU mode or disabled GPU mode?

function(){return A.apply(null,[this].concat($A(arguments)))}
SteveR From UK wrote:
With my own problems and a keen observer of this thread it making me think that I should stay away from Nvidia cards cards completed and go ATI
It comes down to policies within companies that in some cases we simply cannot know.
For example:
Does nVidia or ATI have a better plan to support cards with new drivers into the future? My experience is that right now, with my particular video card, ATI does a better job of making new features available (and making them work right) than nVidia. Is this based on support policy or simply what the engineers can and can't do? Maybe it's partially a matter of funding.
Who has a better handle on how to develop unified software and keep it working on all a whole family of cards? What is their software quality? I am active on Windows forums, and it sure seemed to take nVidia a lot longer to stabilize their drivers for Windows 7 than ATI.
Who has a better test lab? You can imagine that if one company has a better built/funded/maintained test lab, they're more likely to make new versions of drivers for old cards work properly if they have a computer set aside somewhere with that old card in it just waiting to try out new drivers. Unfortunately you can imagine with these companies making many, many new models all the time that funding that lab (and funding the MAINTENANCE of that lab) could get to be HUGE!
Lastly, how much do Marketing or other greedy business people influence company direction, vs. Engineers? Imagine a Marketing person's thoughts: "Stop making new drivers for that old card; we're not selling those and haven't for a long time. If a person has one and can't run the latest game or graphics software, he'll go buy a new one, and that's more money for us."
By the way, just to get an idea of how many different cards we're talking about, look at the sheer number of models listed in the various lists on this page: http://www.videocardbenchmark.net/
Just food for thought.
-Noel

New Nvidia Driver ver 260 for Mac Mini 2010 and HDMI problems.

So this is the first release from Nvidia that is installable "out of the box" directly from Nvidia. Unfortunately, I'm now running into problems with getting the resolution to scale on my HDMI connected HDTV.
When I go into Nvidia properties and select "Adjust desktop size and position", I'm only give 4 options to change the scaling. Unlike the old Bootcamp version which had an option to manually adjust the screen by make the arrows fit on all sides, this new version has the options of:
When using a resolution lower than my displays native resolution...
-Use NVIDIA scaling
-Use NVIDIA scaling with fixed aspect ratio
-Use my display's built-in scaling
-Do not scale
So when I set my display to 1176x664, The resolution changes, however, it still goes beyond the visible border. Changing any of the options above doesn't seem to change anything-
I'm wondering if anyone is experiencing these same issues, or knows how to remedy it?

I completely agree with your assessment for Problem #1, but here we have it.
I will try re-installing and will also double check with the drivers for the monitor. Thanks for the advice. If all else fails, I will just use parallels.

XP PRO, nvidia cards and refreshing frekvency 60 hz

i have upgraded my comuter. now, what is the problem.
when i run programs (3dmark2001,03 and games like ut2003) it shows the correct resolution but nor the refreshing frekvency. it only shows 60 hz. the card can 2048x1536x85 hz and monitor 1280x1024 85hz and 1024x768 100 hz. How to correcz this ???? i read some articles, and it looks like there is a huge bug somewhere, but i didnt found a fix from microsoft or nvidia. the only program i found is NVIDIA REFRESH RATE FIX 2.10E. it can correct the frekvency to 85 hz. but ist not enough for me. i want 100 hz for 1024x768 or lower. how can i do this ?????? please if anyone has or had problems wiht this, write here.
i need help thanks people. ;(

for all who play games on WIN XP. itsnot old driver. i found here http://www.xp-refresh.net/ final solution. ITS a general problem of WIN XP, and the service pack1 doesnt solve this problem. read the whole article.
there is a program that can solve this.
man, i wonder and wonder again ...... how can microsoft do something like this, its HUGE BUG

Fx 5900 ultra flickering fix

if you have the problem
http://www.nvnews.net/vbulletin/showindex.php?s=&postid=190078#post190078
NVIDIA was made aware of an issue involving the GeForce FX 5900 series of graphics cards where some users have reported a slight "flickering" of the image on their screen, visible on a light color background in certain 3D scenes.
In examining the information available, NVIDIA has determined that the issue may involve an interaction between select combinations of the graphics card, system, monitor, other electronic components and the application which creates noise or signal interference.
If you are experiencing this issue on a GeForce FX 5900 or GeForce FX 5900 Ultra card, you can download this driver fix (9.28 MB). It is available on our affiliate sites:
http://www.3dgpu.com/modules/wfsect...hp?articleid=72
http://www.bjorn3d.com/ubbthreads/s...sb=5&o=&fpart=1
http://www.nvnews.net/files/drivers/nvidia/45.33_xp.zip
If you experience any other issues - please email us at [email protected]
Other web sites hosting these drivers include:
http://www.3dchipset.com/drivers/of...ia/nt5/4533.php

O.K, I took a chance & Just installed em right over the Omega drivers and the flickering has stopped in games and it appears I still have the capabilities of the Omega drivers such as overclocking, AGP settings, artifacts testing, and Texture sharpening as well as performance/high performance/Quality settings for the Omega Drivers.
I haven't tested to see if these still work or not Yet- But I will & report back what I find.
The Flickering Has Stopped- Kudo's To Nvidia for the fix- Now, If I can just stop My Eyes from flickering I'll be all set =)
BTW, For anyone that is interested, These Omega Drivers are sanctioned By Nvidia so to speak (They've given the developpers permission & Blessings I guess to modify the drivers for performance as well as Quality optimizations)
My 3dmark 2003 score went from 4913 with the 45.23 drivers from Nvidia to 5122 with these Omega drivers installed under the performance installation (There are 2 installations, one for Quality and one for performance-I chose performance)
The good thing about these drivers is You just instal directly over the Nvida drivers- No worries-it tells You right in the help file to do this-So no leangthy uninstals and clean reinstals are necessary =)
With these drivers, You get an overclock setting (Which is nice because it has a utility built right in to test Your new settings on the fly) and You get a new agp settings GUI too- check em out, they are nice drivers for sure.

Pacman segfault when installing nvidia

ok so i have been trying to reinstall arch linux on my comp for the last couple of days.... was testing some other ditros but got bored so time to come back to arch and so i completed an ftp install and issued pacman -Sy and got synched and then when i tried to pacman -S nvidia (i refuse to run xorg without the nvidia driver for my 6800gs card) i got a segmentation fault. i thought maybe i screwged the install so i went ahead and reinstalled arch.... no luck. so now pacman refuses to work untill i reboot.... so i do and then i think alright well i'll just pacman -S xorg and deal with nvidia when its fixed but for whatever reason it seems that xorg in extra is broken.... not all the packages downloaded.... and yes i have tried diferent servers.... i have run arch linux with NO problems in the past, what am i doing wrong? is the nvidia package messed up at the moment and should i download the one off the nvidia site or have i not confgured something right? hope you guys can help!
Grama

ok but when i ran:
pacman -S xorg
some files were missing or unable to download or SOMETHING when i tried to install xorg last night. and i am pretty sure it completely failed.... problem was i had already taken my sleeping meds and wasn't thinking clearly enough to write down the output before trying a reisntall so ????? i will try again (btw its openbox) and we'll see i guess.
Grama

Howto save nvidia brightness settings?

Hey Folks,
i'm currently running Arch on my Mediacenter PC, with a GeForce4 Something connected to my TV via TV-Out (SVideo). Everything is working quite nicely, apart from the fact that the graphics appear kinda dark on the TV.
I can adjust the brightness settings without a problem with nvidia-settings, but after every X restart/reboot those are back to standard again. Running nvidia-settings once fixes this tho.
So, is there a way to save the brightness settings?
Thanks in advance,
Schro

nevermind, found it myself
just added "nvidia-settings -l" to run automatically when X starts....

Nvidia: video tearing when compositing is enabled

Hi all,
I have a very persistent problem which affects many people apparently, but after extensive searching I haven't found a conclusive fix that works for me. I have a nice Nvidia GeForce GTX 660 Ti graphics card, and I'm using the proprietary Nvidia driver (I'm using the latest version available in the official repositories).
My desktop environment is KDE 4, and with compositing enabled (and I do want compositing enabled), the top third of my screen suffers significant tearing when there's movement, whether that be moving windows around, playing videos in mplayer, VLC or Chromium, or playing 3D games (fullscreen 3D games I've tested don't even seem to work with compositing disabled, fyi).
In nvidia-settings, I've set the resolution and frequency of my monitor to 1680x1050 and 60Hz manually, instead of just using 'Auto' for those settings. 'Sync to VBlank' and 'Allow Flipping' are checked in the OpenGL Settings section, and the 'Image Settings' slider is set to 'High Performance'. My PowerMizer settings are set to 'Prefer Maximum Performance' for obvious reasons, but this doesn't stay set when I reboot (even with a custom line in xorg.conf added).
This tearing is incredibly frustrating, and annoyingly I'm sure Nvidia could have fixed it by now. The issue has been discussed on forums Internet-wide for at least three years now.
Anyway, have my xorg.conf, if it's any help. The line with 'PowerMizer' in it was found on some other forum, and it's intended to keep my PowerMizer settings on maximum performance, but that doesn't happen either. You can also see that I have TripleBuffer enabled.
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 313.26 (buildmeister@swio-display-x86-rhel47-05) Wed Feb 27 13:56:11 PST 2013
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 313.26 (buildmeister@swio-display-x86-rhel47-05) Wed Feb 27 13:55:59 PST 2013
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
Option "Xinerama" "0"
EndSection
Section "Files"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Samsung SyncMaster"
HorizSync 30.0 - 81.0
VertRefresh 56.0 - 75.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GTX 660 Ti"
Option "RegistryDwords" "PowerMizerEnable=0x1; PerfLevelSrc=0x3322; PowerMizerDefaultAC=0x1"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "TripleBuffer" "True"
Option "Stereo" "0"
Option "metamodes" "1680x1050_60 +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
The history of this issue means there's unlikely to be a comprehensive fix any time soon, but I'm really hoping. This is driving me closer and closer to Windows.
Last edited by Archimaredes (2013-04-03 16:36:40)

vvd wrote:
bwat47 wrote:You should be able to remove tearing in fullscreen videos at least, if you enable "unredirect fullscreen windows" in kwin and enable vsync in the nvidia driver, (and make sure you use opengl or vdpau output in the video player) because doing this makes the fullscreen window bypass kwin's composting and only use the nvidia driver's vsync
My experience (with nvidia, vdpau, composite, vsync, tearing and all that crap) is that the window manager must support un-redirecting fullscreen windows AND vsync. If the (compositing) WM doesn't support vsync then even un-redirected windows are not vsync'ed and you get tearing (nvidia settings make no difference).
For example, when I was using the xfce window manager (which supports un-redirecting fullscreen windows but not vsync) I still got tearing. It was only when I switched to compiz (with vsync and un-redirect FS-windows enabled) that I could get tearing free video.
I have also found that, for smooth video playback, refresh rates do matter. This has something to do with inter-frame modulation that the video player has to do, because it has to compensate for the difference between the frame rate of the video and the refresh rate of the display. So - If you get micro stuttering (slow moving scenes do not appear like moving smooth) try switching your display refresh rates (try something like 50Hz, 59Hz and 60Hz).
Currently I happily use gnome 3 with CLUTTER_PAINT=disable-clipped-redraws:disable-culling in /etc/environment and mplayer2 with vdpau for tearing free video. I use a script to quickly switch monitor refresh rates (since gnome doesn"t allow me to switch refresh rates - they probably never watch videos...).
Edit: I use nvidia's High Quality settings and the adaptive (default) powermizer. Also, triple buffering is not needed for smooth video playback and it adds input latency on a vsynced composite desktop.
With undirected fullscreen windows enabled the compositor's vsync support is irrelevant, because the whole purpose of that option is to allow the window to completely bypass the compositor. At that point it is down to the driver and the video players opengl implementation. If the compositor's vsync works properly with your driver then you don't want undirected fullscreen windows enabled for your video players anyway.
Last edited by bwat47 (2013-04-06 18:32:11)

Nvidia HW probs? [fixed]

Similar Messages

Maybe you are looking for