btw, about creting the nodes manually - sure i can, but thats not a real solution, only a workaround...
]]>are you sure that the nodes are created by the nvidia module?
and not only by running xorg?
According to all docs the nodes should be created during module loading (by udev in this case).
If you don't load the module in rc.conf and leave it in modules.conf then the module will be loaded when it's requested by xorg.
That's the known timeout problem: loading module triggers nodes creating but they are not created quickly enough for xorg so it fails to start.
This is supposed to be fixed by loading nvidia module from rc.conf at boot time (so it has enough time before xorg starts).
And this indeed works for me (I had timeout problem first time when I switched to udev IIRC because I wasn't loading nvidia module from rc.conf).
Z4ziggy problem is that the nodes are just not created at all during boot or xorg startup.
This also depends on the installation/upgrade method (which is really the strangest problem here since it's quite easy to create nodes manually from rc.local or something like this).
At least that's what I've found about this so far on the net. But maybe I'm missing something...
]]>tnx for all the info and help guys,
z4ziggy
tpowa nospam archlinux.org
good point when it does work right after installation
the.install file runs only
depmod -a
rmmod nvidia and
modprobe nvidia
not more
Normally this should be the "timeout issue" as it's described in the docs I posted in my previous posts.
I guess you could review them and check if something is not missing in the current installation process.
But it shouldn't happen if the driver is loaded from rc.conf during boot process IMO.
Since z4ziggy used the same driver versions but with different arch versions shouldn't this be realted to udev and not nvidia installer? Why does it work right after installation of nvidia driver and not after a reboot?
grep udev /var/log/pacman.log
[07/28/04 00:24] installed udev (030-5)
[11/14/04 18:21] upgraded udev (030-5 -> 043-1)
[11/16/04 21:07] upgraded udev (043-1 -> 044-1)
[11/27/04 23:40] upgraded udev (044-1 -> 046-1)
[12/13/04 22:22] upgraded udev (046-1 -> 048-1)
Perhaps an answer is in udev cvs history?
This is a very misterious bug :-)
]]>can you make a diff of both /etc to see what's different
perhaps we find the error this way
i'll add some patches to nvidia driver
but i don't think that will solve your problem
perhaps is modprobe.conf no longer in the noupgrade list
in newer versions on install medium