From: Daniel Drake <dan@reactivated.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev vs nvidia
Date: Wed, 25 Feb 2004 21:27:16 +0000 [thread overview]
Message-ID: <403D1334.1020504@reactivated.net> (raw)
In-Reply-To: <40312612.7070700@reactivated.net>
If anyone is interested, I have solved the below issue. It turns out that you
are supposed to load the module before starting X (even nvidia say so), and
devfs did this automatically on bootup. So, the nvidia module should be added
to an autoload list, and this issue is not a fault of udev/hotplug.
Daniel
Daniel Drake wrote:
> Hi,
>
> Since switching to udev, I have had problems when starting X relating to
> nvidia drivers. I know this is a tricky situation, with the nvidia
> drivers being closed-source, nobody really knows how they work. If it
> seems likely that this problem is not udev-related, then please tell me,
> and I will go to nvidia instead.
>
> I'm not sure if this is even anything to do with udev. The only reason I
> suspect udev might be involved, is because of the existance of /dev
> nodes seems to play a part.
>
>
> I am running nvidia drivers version 5336 with Martin Schlemmer's patch
> applied to make them export info into sysfs.
> If I manually "modprobe nvidia", then I can see that the /dev/nvidia0
> and /dev/nvidiactl nodes are created. So at this stage it seems to be
> loaded.
>
>
> Ignoring the above situation, on a normal bootup, the nvidia module is
> not loaded at the point where I "startx":
>
> # ls /dev/nvidia*
> no such file or directory
>
> # startx
> XFree86 Version 4.3.0
> Release Date: 27 February 2003
> [snip]
> (=) Using config file: "/etc/X11/XF86Config"
> Using vt 7
> (EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module!
> (EE) NVIDIA(0): *** Aborting ***
> (EE) Screen(s) found, but none have a usable configuration.
>
> Fatal server error:
> no screens found
>
> If I mknod the /dev/nvidia* nodes first, then X is able to start as
> normal. Also, strangely, if I "modprobe nvidia", and then "startx" then
> X starts as normal.
>
> I believe that this problem comes around because the /dev nodes are not
> created quickly enough.
>
> # modprobe nvidia && ls -l /dev/nv*
> ls: /dev/nv*: No such file or directory
>
> # rmmod nvidia
>
> # modprobe nvidia && sleep 2 && ls -l /dev/nv*
> crw-rw-rw- 1 root video 195, 0 Feb 16 19:47 /dev/nvidia0
> crw-rw-rw- 1 root video 195, 255 Feb 16 19:47 /dev/nvidiactl
>
>
> My theory is that X loads the "nvidia" module, and then immediately
> tries to initialize the display and whatever else. But as the nvidia*
> nodes arent in place, it dies.
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-02-25 21:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-16 20:20 udev vs nvidia Daniel Drake
2004-02-16 20:33 ` Daniel Drake
2004-02-16 20:36 ` claude
2004-02-25 21:27 ` Daniel Drake [this message]
2004-02-26 16:25 ` MALET JL
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=403D1334.1020504@reactivated.net \
--to=dan@reactivated.net \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).