| Chaves |
05-28-2008 08:26 AM |
udevtrigger --retry-failed takes ages on boot
Hi everyone.
After mooving to a self-compiled kernel (2.6.24.4) the
"udevtrigger --retry-failed" step takes much more time that it used to.
Here is the .udev/failed folder:
Quote:
/dev/.udev/failed# ls
%2fdevices%2fLNXSYSTM:00
%2fdevices%2fLNXSYSTM:00%2fACPI0007:00
%2fdevices%2fLNXSYSTM:00%2fACPI0007:01
%2fdevices%2fLNXSYSTM:00%2fLNXPWRBN:00
%2fdevices%2fLNXSYSTM:00%2fLNXTHERM:00
%2fdevices%2fLNXSYSTM:00%2fLNXTHERM:00%2fLNXTHERM:01
%2fdevices%2fLNXSYSTM:00%2fdevice:00%2fPNP0A03:00
%2fdevices%2fLNXSYSTM:00%2fdevice:00%2fPNP0A03:00%2fACPI0003:00
%2fdevices%2fLNXSYSTM:00%2fdevice:00%2fPNP0A03:00%2fPNP0C0A:00
%2fdevices%2fLNXSYSTM:00%2fdevice:00%2fPNP0A03:00%2fdevice:01%2fNSC6001:00
%2fdevices%2fLNXSYSTM:00%2fdevice:00%2fPNP0A03:00%2fdevice:01%2fPNP0000:00
%2fdevices%2fLNXSYSTM:00%2fdevice:00%2fPNP0A03:00%2fdevice:01%2fPNP0100:00
%2fdevices%2fLNXSYSTM:00%2fdevice:00%2fPNP0A03:00%2fdevice:01%2fPNP0200:00
%2fdevices%2fLNXSYSTM:00%2fdevice:00%2fPNP0A03:00%2fdevice:01%2fPNP0303:00
%2fdevices%2fLNXSYSTM:00%2fdevice:00%2fPNP0A03:00%2fdevice:01%2fPNP0401:00
%2fdevices%2fLNXSYSTM:00%2fdevice:00%2fPNP0A03:00%2fdevice:01%2fPNP0800:00
%2fdevices%2fLNXSYSTM:00%2fdevice:00%2fPNP0A03:00%2fdevice:01%2fPNP0B00:00
%2fdevices%2fLNXSYSTM:00%2fdevice:00%2fPNP0A03:00%2fdevice:01%2fPNP0C02:00
%2fdevices%2fLNXSYSTM:00%2fdevice:00%2fPNP0A03:00%2fdevice:01%2fPNP0C02:01
%2fdevices%2fLNXSYSTM:00%2fdevice:00%2fPNP0A03:00%2fdevice:01%2fPNP0C04:00
%2fdevices%2fLNXSYSTM:00%2fdevice:00%2fPNP0A03:00%2fdevice:01%2fPNP0C09:00
%2fdevices%2fLNXSYSTM:00%2fdevice:00%2fPNP0A03:00%2fdevice:01%2fPNP0C0D:00
%2fdevices%2fLNXSYSTM:00%2fdevice:00%2fPNP0A03:00%2fdevice:01%2fSYN0801:00
%2fdevices%2fLNXSYSTM:00%2fdevice:00%2fPNP0C01:00
%2fdevices%2fLNXSYSTM:00%2fdevice:00%2fPNP0C0C:00
%2fdevices%2fLNXSYSTM:00%2fdevice:00%2fPNP0C0E:00
%2fdevices%2fLNXSYSTM:00%2fdevice:00%2fPNP0C0F:00
%2fdevices%2fLNXSYSTM:00%2fdevice:00%2fPNP0C0F:01
%2fdevices%2fLNXSYSTM:00%2fdevice:00%2fPNP0C0F:02
%2fdevices%2fLNXSYSTM:00%2fdevice:00%2fPNP0C0F:03
%2fdevices%2fLNXSYSTM:00%2fdevice:00%2fPNP0C0F:04
%2fdevices%2fLNXSYSTM:00%2fdevice:00%2fPNP0C0F:05
%2fdevices%2fLNXSYSTM:00%2fdevice:00%2fPNP0C0F:06
%2fdevices%2fLNXSYSTM:00%2fdevice:00%2fPNP0C0F:07
%2fdevices%2fpci0000:00%2f0000:00:01.0%2f0000:01:00.0
%2fdevices%2fpci0000:00%2f0000:00:02.0
%2fdevices%2fpci0000:00%2f0000:00:02.3
%2fdevices%2fpci0000:00%2f0000:00:02.5%2fide0%2f0.0
%2fdevices%2fpci0000:00%2f0000:00:02.5%2fide1%2f1.0
%2fdevices%2fpci0000:00%2f0000:00:02.6
%2fdevices%2fpci0000:00%2f0000:00:03.0
%2fdevices%2fpci0000:00%2f0000:00:03.0%2fusb2%2f2-0:1.0
%2fdevices%2fpci0000:00%2f0000:00:03.1
%2fdevices%2fpci0000:00%2f0000:00:03.1%2fusb3%2f3-0:1.0
%2fdevices%2fpci0000:00%2f0000:00:03.2
%2fdevices%2fpci0000:00%2f0000:00:03.2%2fusb4%2f4-0:1.0
%2fdevices%2fpci0000:00%2f0000:00:03.2%2fusb4%2f4-1%2f4-1:1.0
%2fdevices%2fpci0000:00%2f0000:00:03.3
%2fdevices%2fpci0000:00%2f0000:00:03.3%2fusb1%2f1-0:1.0
%2fdevices%2fpci0000:00%2f0000:00:09.2
%2fdevices%2fplatform%2ffujitsu-laptop
%2fdevices%2fplatform%2fi8042
%2fdevices%2fplatform%2fi8042%2fserio0
%2fdevices%2fplatform%2fpcspkr
%2fdevices%2fplatform%2fserial8250
%2fdevices%2fplatform%2fvesafb.0
%2fdevices%2fpnp0%2f00:00
%2fdevices%2fpnp0%2f00:01
%2fdevices%2fpnp0%2f00:02
%2fdevices%2fpnp0%2f00:03
%2fdevices%2fpnp0%2f00:04
%2fdevices%2fpnp0%2f00:05
%2fdevices%2fpnp0%2f00:06
%2fdevices%2fpnp0%2f00:07
%2fdevices%2fpnp0%2f00:08
%2fdevices%2fpnp0%2f00:09
%2fdevices%2fpnp0%2f00:0a
%2fdevices%2fpnp0%2f00:0b
%2fdevices%2fvirtual%2fdmi%2fid
|
Running Slackware 12
Dunno if this would help:
Quote:
ls /var/log/packages/{sysvinit,udev}*
/var/log/packages/sysvinit-2.86-i486-5
/var/log/packages/sysvinit-functions-8.53-i486-2
/var/log/packages/sysvinit-scripts-1.2-noarch-13
/var/log/packages/udev-111-i486-5
|
I only found a couple of posts on this problem which were saying that udev might not be recognising the drivers build into the kernel=\
Any ideas what is wrong and how this can be fixed?
Thanks |
