LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 05-28-2008, 08:26 AM   #1
Chaves
Member
 
Registered: Mar 2008
Posts: 33

Rep: Reputation: 15
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
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
boot hangs at udevtrigger retry-failed after attempt to set up wireless Greenfuse Slackware 3 06-23-2008 07:51 AM
Disk error 01, AX = 4209, drive 9F Boot failed: press a key to retry. ... katemiz Linux - Hardware 1 09-11-2006 07:19 AM
X takes ages and ages to load! dcdbutler Slackware 9 03-23-2005 07:53 AM
'Whatever' login takes ages... Worstje Slackware 7 10-15-2004 03:06 PM
SuSE 9.1 Pro takes ages to boot - In fact so long, I just switched over to Windows. eBopBob Linux - Newbie 16 09-29-2004 06:36 PM


All times are GMT -5. The time now is 05:52 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration