LinuxQuestions.org
Visit Jeremy's Blog.
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
 
LinkBack Search this Thread
Old 03-14-2010, 11:39 AM   #1
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current & "True Multilib." PC-BSD.
Posts: 2,092

Rep: Reputation: 147Reputation: 147
Udev events failed


Noticed this on boot up the other day, but it doesn't seem to have a negative effect. Everything appears to be running just fine.

"Triggering udev events: /sbin/udevadm trigger --type=failed"

Is this something that needs to be resolved or ignored?
Thanks.
 
Click here to see the post LQ members have rated as the most helpful post in this thread.
Old 03-14-2010, 11:51 AM   #2
sahko
Senior Member
 
Registered: Sep 2008
Distribution: Slackware
Posts: 1,041

Rep: Reputation: Disabled
Did you even bother reading the udevadm man page?
 
1 members found this post helpful.
Old 03-14-2010, 11:56 AM   #3
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current & "True Multilib." PC-BSD.
Posts: 2,092

Original Poster
Rep: Reputation: 147Reputation: 147
Quote:
Originally Posted by sahko View Post
Did you even bother reading the udevadm man page?
Actually, yes, I have read that page.
Thank you for your most helpful response... not.
 
0 members found this post helpful.
Old 03-14-2010, 12:08 PM   #4
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 2,364
Blog Entries: 3

Rep: Reputation: 169Reputation: 169
I noticed this way back to 12.1 I bet if I followed it back on or more of the scripts that UDEV is supposed to load. And one of those was my pcmcia I turned it off on my desktop. check pkgtool run scripts it is just trying to load hardware that is not there no big deal leave it alone or play with it.
any way you look at it the program Failed to load that device.
 
2 members found this post helpful.
Old 03-14-2010, 12:10 PM   #5
catkin
LQ 5k Club
 
Registered: Dec 2008
Location: Tamil Nadu, India
Distribution: Servers: Debian Squeeze and Wheezy. Desktop: Slackware64 14.0. Netbook: Slackware 13.37
Posts: 8,514
Blog Entries: 27

Rep: Reputation: 1174Reputation: 1174Reputation: 1174Reputation: 1174Reputation: 1174Reputation: 1174Reputation: 1174Reputation: 1174Reputation: 1174
AFAIK the same message has appeared at boot since installation. At first it was alarming to see "failed" in a boot message but I figured it is a command parameter rather than a condition so never worried about it since.
 
2 members found this post helpful.
Old 03-14-2010, 01:09 PM   #6
vdemuth
Member
 
Registered: Oct 2003
Location: West Midlands, UK
Distribution: Slackware 14 (Server),Suse 13.1 (Desktop),, Mepis on the wifes lappy
Posts: 760

Rep: Reputation: 90
IIRC, this is there to trigger any udev events that failed first time around in the boot process at /etc/rc.d/rc.S. The message is for info puposes.
 
2 members found this post helpful.
Old 03-14-2010, 02:19 PM   #7
gnashley
Amigo developer
 
Registered: Dec 2003
Location: Germany
Distribution: Slackware
Posts: 4,724

Rep: Reputation: 449Reputation: 449Reputation: 449Reputation: 449Reputation: 449
That shows the second time that udev is run and is meant to find devices which were already plugged in at boot-time -it's called coldplugging as opposed to hotplugging which detects events as they happen.
Devices which are already plugged in when booting generate a kernel-event before udev is started and so udev is run a second time with '--type=failed' to detect any such events.
udev is first started at the top of rc.S, but the line you are seeing is from late during rc.M.
 
2 members found this post helpful.
Old 03-14-2010, 09:12 PM   #8
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current & "True Multilib." PC-BSD.
Posts: 2,092

Original Poster
Rep: Reputation: 147Reputation: 147
Thank you Drakeo, Catkin, Vdemuth, and, especially, Gnashley for your replies. Greatly appreciated!
 
2 members found this post helpful.
  


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
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Hang on triggering udev events- is there a buildup of events? sonichedgehog Slackware 20 07-11-2008 02:49 AM
/dev/.udev/failed crazy8 Linux - Newbie 9 04-11-2008 01:06 PM
udevd - rmdir(/dev/.udev/failed) failed: Permission denied pbhj Slackware 20 03-21-2008 10:46 AM
udev failed on FC5 bootup ekdya Fedora 2 05-23-2007 10:00 PM
Starting mdmpd: Kernerl md module does not support events [Failed] dr_zayus69 Linux - Software 3 01-18-2005 04:12 AM


All times are GMT -5. The time now is 02:51 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