No NVIDIA X driver for NVIDIA Quadro K5000 in Debian 7

I have an HP DL580 G7 server with Debian 7. This machine has an embedded card, namely ATI ES1000. I installed an NVIDIA Quadro K5000 and NVIDIA GeForce GTS 450 on the server and followed the instructions provided in https://wiki.debian.org/NvidiaGraphicsDrivers to set it up. I changed /etc/X11/xorg.conf in order to get rid of some well-known bugs (such as adding BusID option). Moreover, in the server BIOS, I set this card as the secodary graphics card and left the embedded one as the primary, since otherwise the iLO wouldn’t work as it is explained in http://h30499.www3.hp.com/t5/ProLiant-Servers-ML-DL-SL/DL-360-two-VGA-iLO-No-Video/td-p/5570553.

Now, Gnome still runs in the fall-back mode and when I run run nvidia-settings (through XRDP), it gives me the following error: “You do not appear to be using the nvidia x driver. Please edit your X configuration file (just run nvidia-xconfig as root), and restart the X server.” Running nvidia-xconfig does not help as well. I don’t know how to activate any one of these cards as the primary graphics card and be able to use their 3d acceleration. Please note that no monitor is attached to the system and I tried to test the graphics using iLO, VNC, and XRDP but none of them worked.

I also tried downloading and installing the latest NVIDIA driver for linux x64 (namely NVIDIA-Linux-x86_64-319.49.run) but nothing changed.

The log file of nvidia-bug-report.sh is attached.

Any help is appreciated.
nvidia-bug-report.log.gz (48.4 KB)

NVIDIA-Linux-x86_64-319.49.run is not the latest.

Try this one.

There shouldn’t be any differences. Even the nvidia’s packaged driver in Debian (version 304) supports both GeForce GTS 405 and Quadro K500.

Anyways, I just uninstalled the Debian driver and installed the version 325.15 without seeing any improvements. The log file of nvidia-bug-report.sh is attached.
nvidia-bug-report.log.gz (87 KB)

According to your log file, the Xorg server is running with the NVIDIA driver just fine. As far as I can tell, xrdp runs its own X server so if you ran nvidia-settings inside of that rather than connecting to your :0 server, that would explain why it didn’t detect the NVIDIA driver.

Please give a screen-scraping VNC server such as x11vnc a try.

Thanks for the suggestion. I tried vncserver but it didn’t change anything. The vncserver on my machine is TightVNC-1.3.9. Here’s the VNC server log file:

26/08/13 13:46:31 Xvnc version TightVNC-1.3.9
26/08/13 13:46:31 Copyright (C) 2000-2007 TightVNC Group
26/08/13 13:46:31 Copyright (C) 1999 AT&T Laboratories Cambridge
26/08/13 13:46:31 All Rights Reserved.
26/08/13 13:46:31 See http://www.tightvnc.com/ for information on TightVNC
26/08/13 13:46:31 Desktop name 'X' (myserver:1)
26/08/13 13:46:31 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
26/08/13 13:46:31 Listening for VNC connections on TCP port 5901
xrdb: No such file or directory
xrdb: can't open file '/home/home2/students/dousti/.Xresources'

26/08/13 13:48:23 Got connection from client 128.125.225.131
26/08/13 13:48:23 Using protocol version 3.8
26/08/13 13:48:26 Full-control authentication passed by 128.125.225.131
26/08/13 13:48:26 Pixel format for client 128.125.225.131:
26/08/13 13:48:26   32 bpp, depth 24, little endian
26/08/13 13:48:26   true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
26/08/13 13:48:26   no translation needed
26/08/13 13:48:26 rfbProcessClientNormalMessage: ignoring unknown encoding 16
26/08/13 13:48:26 rfbProcessClientNormalMessage: ignoring unknown encoding 17
26/08/13 13:48:26 rfbProcessClientNormalMessage: ignoring unknown encoding 10
26/08/13 13:48:26 rfbProcessClientNormalMessage: ignoring unknown encoding 9
26/08/13 13:48:26 rfbProcessClientNormalMessage: ignoring unknown encoding 8
26/08/13 13:48:26 Using tight encoding for client 128.125.225.131
26/08/13 13:48:26 Using compression level 6 for client 128.125.225.131
26/08/13 13:48:26 Enabling full-color cursor updates for client 128.125.225.131
26/08/13 13:48:26 Enabling cursor position updates for client 128.125.225.131
26/08/13 13:48:26 Using image quality level 6 for client 128.125.225.131
26/08/13 13:48:26 rfbProcessClientNormalMessage: ignoring unknown encoding -65530
26/08/13 13:48:26 Enabling LastRect protocol extension for client 128.125.225.131
26/08/13 13:48:26 rfbProcessClientNormalMessage: ignoring unknown encoding -223
26/08/13 13:48:26 rfbProcessClientNormalMessage: ignoring unknown encoding -65535
26/08/13 13:48:26 rfbProcessClientNormalMessage: ignoring unknown encoding -32768
26/08/13 13:48:26 rfbProcessClientNormalMessage: ignoring unknown encoding -32767
26/08/13 13:48:26 rfbProcessClientNormalMessage: ignoring unknown encoding -32766
26/08/13 13:48:26 rfbProcessClientNormalMessage: ignoring unknown encoding -32765
26/08/13 13:48:26 rfbProcessClientNormalMessage: ignoring unknown encoding -1063131698
26/08/13 13:48:26 Pixel format for client 128.125.225.131:
26/08/13 13:48:26   32 bpp, depth 24, little endian
26/08/13 13:48:26   true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
26/08/13 13:48:26   no translation needed
26/08/13 13:48:26 Using hextile encoding for client 128.125.225.131
26/08/13 13:48:26 rfbProcessClientNormalMessage: ignoring unknown encoding 17
26/08/13 13:48:26 rfbProcessClientNormalMessage: ignoring unknown encoding 16
26/08/13 13:48:26 rfbProcessClientNormalMessage: ignoring unknown encoding 10
26/08/13 13:48:26 rfbProcessClientNormalMessage: ignoring unknown encoding 9
26/08/13 13:48:26 rfbProcessClientNormalMessage: ignoring unknown encoding 8
26/08/13 13:48:26 Using compression level 6 for client 128.125.225.131
26/08/13 13:48:26 Enabling full-color cursor updates for client 128.125.225.131
26/08/13 13:48:26 Enabling cursor position updates for client 128.125.225.131
26/08/13 13:48:26 Using image quality level 6 for client 128.125.225.131
26/08/13 13:48:26 rfbProcessClientNormalMessage: ignoring unknown encoding -65530
26/08/13 13:48:26 Enabling LastRect protocol extension for client 128.125.225.131
26/08/13 13:48:26 rfbProcessClientNormalMessage: ignoring unknown encoding -223
26/08/13 13:48:26 rfbProcessClientNormalMessage: ignoring unknown encoding -32768
26/08/13 13:48:26 rfbProcessClientNormalMessage: ignoring unknown encoding -32767
26/08/13 13:48:26 rfbProcessClientNormalMessage: ignoring unknown encoding -32766
26/08/13 13:48:26 rfbProcessClientNormalMessage: ignoring unknown encoding -32765
26/08/13 13:48:26 rfbProcessClientNormalMessage: ignoring unknown encoding -1063131698
26/08/13 13:49:01 Client 128.125.225.131 gone
26/08/13 13:49:01 Statistics:
26/08/13 13:49:01   key events received 34, pointer events 1271
26/08/13 13:49:01   framebuffer updates 139, rectangles 726, bytes 7173986
26/08/13 13:49:01     LastRect markers 1, bytes 12
26/08/13 13:49:01     cursor shape updates 41, bytes 27242
26/08/13 13:49:01     cursor position updates 2, bytes 24
26/08/13 13:49:01     copyRect rectangles 1, bytes 16
26/08/13 13:49:01     hextile rectangles 665, bytes 7101169
26/08/13 13:49:01     tight rectangles 16, bytes 45523
26/08/13 13:49:01   raw bytes equivalent 39365152, compression ratio 5.508164

vncserver, like x11rdp, is its own X server which renders everything in software. Please try x11vnc or x0vncserver.

I tried x11vnc and it worked!
How can I have XRDP or the regular TightVNC to work with the nvidia driver?

Any answer?

You can’t. The NVIDIA driver is an Xorg driver. XDRP and TightVNC’s X servers are not Xorg.