FS#9701 - udev-118-2 don't blacklist nvidiafb
Attached to Project:
Arch Linux
Opened by Isenmann Daniel (ise) - Wednesday, 27 February 2008, 06:28 GMT
Last edited by Isenmann Daniel (ise) - Thursday, 13 March 2008, 20:56 GMT
Opened by Isenmann Daniel (ise) - Wednesday, 27 February 2008, 06:28 GMT
Last edited by Isenmann Daniel (ise) - Thursday, 13 March 2008, 20:56 GMT
|
Details
Description:
udev-118-2 don't blacklist nvidiafb at startup. Packages are the latest from testing repo, so initscripts are up2date. I know, that this bug don't appear on all machines, don't know why. But after two forum posts of other users, this should be reported here. Steps to reproduce: Install the latest packages from testing repo. @Dan and Aaron: I'm willing to help out, because this bug appears on my machine, I can give better feedback on this. But I need some startup assistance from one which are familiar with udev. |
This task depends upon
Closed by Isenmann Daniel (ise)
Thursday, 13 March 2008, 20:56 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in latest udev pacakge in testing.
Thursday, 13 March 2008, 20:56 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in latest udev pacakge in testing.
My system take a lot of time to boot and continue to take 10-15 of my CPU.
Udev take 23 seconds to load, console font 12 seconds...
Some details:
nvidia-96xx
nvidia-96xx-utils
udev-118-2
2008.02-1
I do not notice any slowdown with loading Udev on my computer, but that is the slowest part of the boot sequence.
I tried adding !nvidiafb to my modules array in rc.conf, but nvidia still failed to load when starting X.
My computer boots into runlevel 3, could this make a difference?(although I doubt it would)
nvidia-169.09-2
nvidia-utils-169.09-1
udev-118-2
intiscripts-2008.02-1
thank you for your time
:D
What you can do instead is putting "blacklist nvidiafb" in your /etc/modprobe.conf. But this is just a workaround and shouldn't be there for ages.
I'm sure that 95% of the guys on this bugtracker are experienced enough to see that it's a stupid workaround to get the system booting.
And now, back to topic again ;)