(EE) NV: The PCI device 0x10de06c4 ((null)) at 01@00:00:0 has a kernel module claiming it
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
(EE) NV: The PCI device 0x10de06c4 ((null)) at 01@00:00:0 has a kernel module claiming it
Hi, I'm a linux newbie trying to install slackware. Not sure if this Q pertains to this thread topic but I think it does.
I have been following the 'How to install slackware: a complete tutorial' on notebookreview and I have it installed and logged in as root but when I type startx the desktop comes up for a sec then crashes back to command line. I have tried all the color settings under xorgsetup. This is basically the error that I get;
(EE) NV: The PCI device 0x10de06c4 ((null)) at 01@00:00:0 has a kernel module claiming it
(EE) NV: This driver cannot operate until it has been unloaded.
(EE) No devices detected.
Fatal server error:
no screens found
I'm stuck here. Do I need to manually install the vid card driver? If so, how do I do that? I've googled some and tried to mount and access my cd drive with #mount /dev/hdc -t iso9660 -r /cdrom just to see if I could use it to install a driver, with no luck. The tutorials I've read for installing it download and install it from the desktop GUI which I can't get to, so maybe the driver is not even my problem??? very confusing.... It's disheartening to come this far and crash on the finish line.
Last edited by unSpawn; 09-29-2011 at 03:05 PM.
Reason: //Pruned from http://www.linuxquestions.org/questions/slackware-14/a-guide-enabling-3d-acceleration-in-x11-402003/
Did you run the xorgsetup tool? xorg.conf might not have been generated if you haven't ran this tool.
Usually the first things I do when installing Slackware for the first time is to run the following commands in this order:
"alsaconf" (to setup the auto device)
"alsamixer" (to set the audio levels)
"alsactl store" (to save the audio levels I set from alsamixer)
"xorgsetup" (to generate an xorg.conf file)
"vi /etc/X11/xorg.conf" (to confirm or reconfigure my video card to the appropriate driver, in my case nouveau)
Slackware does not create a '/etc/X11/xorg.conf' by default. When one does a 'startx' attempts are made to load necessary modules & configs. If you look at '/etc/X11', you will find a sample configuration file: 'xorg.conf-vesa'. If all else fails you can either move or copy that file to '/etc/X11//xorg.conf'.
You should get in the habit of reading the available Slackware documentation on your install media;
Quote:
excerpt from CHANGES_AND_HINTS.TXT
The version of Xorg in Slackware 13.37 will not (in most cases) require an
/etc/X11/xorg.conf file. Input hotplugging is no longer done using hal;
instead, it now uses udev for input device detection and keyboard mapping.
/usr/share/X11/xorg.conf.d/ is the "packaged" configuration directory; all
files ending with ".conf" in this directory are used by the X server
unless there is an identically-named file in the local sysadmin directory.
The local sysadmin config directory is /etc/X11/xorg.conf.d/ - all files
ending with ".conf" in this directory are parsed.
There are several default config files in /usr/share/X11/xorg.conf.d/:
* 10-evdev.conf
a "catchall" file for input devices using the evdev driver; this
should work for most hardware in the absence of a better driver
* 50-synaptics.conf
overrides the earlier 10-evdev.conf file and uses the synaptics
driver for all touchpads
* 50-wacom.conf
overrides the earlier 10-evdev.conf file and uses the wacom driver
for Wacom tablets
* 90-keyboard-layout.conf
this sample ("normal" en layout) keeps the "old" default of
allowing Zap'ing the Xserver.
If you need to modify any of these defaults, then copy the relevant file
from /usr/share/X11/xorg.conf.d/ to /etc/X11/xorg.conf.d/ and edit the
copy.
You can still create an xorg.conf file if you wish, or you can create some
minimal xorg.conf snippets with only the specific contents that you wish
to override (as an example, to use a binary-only video driver) as separate
files in the /etc/X11/xorg.conf.d/ directory.
Regardless of your chipset (though it seems more common with intel), if KDE
crashes on startup, try disabling the Composite extension (which will also
disable all of the fancy desktop effects). Place the following content in
a file at /etc/X11/xorg.conf.d/disable-composite.conf:
Section "Extensions"
Option "Composite" "Disable"
EndSection
Yes I did xorgconfig. I was able to see the file with 'more /etc/X11/org.conf' and see it from ubuntu, but I couldn't figure out how to get permission to write to it. I tried chmod 777 with no luck, so someone else suggested to use 12.2 so I tried that and it installed with no hiccups. When I did xorgsetup and clicked ok for detect there was a flash and noticeable change in screen resolution, which it didn't do before, and then it asked me all kinds of keyboard questions like navajo cherokee etc. which it didn't get to at all in 13.37.
I'm looking at slacktop desktop now and going to dive right in! Thanks for the help!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.