Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
09-11-2006, 05:49 AM
|
#1
|
Member
Registered: Oct 2003
Location: Sweden
Distribution: Slackware64-current, SlackwareARM-15.0
Posts: 833
Rep:
|
udev error messages during boot
Apologies for this double post....
Please ignore this one.
Hi,
I have always stayed current (Slackware), but got 6 weeks behind. After I updated (using slapt-get, and yes, carefully inspected the changelog) I get loads of error messages from udev during boot. They don't seem to be harmful, since all works well, but nevertheless I would like to know what causes these messages.
I read somewhere that they were caused by stale hotplug files. Since hotplug has been taken over by udev. I tried removing the hotplug package, but it didn't help.
Anyone who knows what's going on?
A LOT of these two lines:
This is what I get (from /var/log/syslog)
Sep 10 13:40:34 sphritzs udevd-event[5719]: run_program: exec of program '/sbin/udev_run_devd' failed
Sep 10 13:40:34 sphritzs udevd-event[5721]: run_program: exec of program '/sbin/udev_run_hotplugd' failed
And after those lines during boot I see similar warnings but somehow related to modules. For some reason I don't see these in /var/log/messages or /var/log/syslog)
Cheers, Leon.
Last edited by BroX; 09-11-2006 at 05:50 AM.
|
|
|
09-11-2006, 06:58 AM
|
#2
|
Slackware Contributor
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559
|
The programs "/sbin/udev_run_devd" and "/sbin/udev_run_hotplugd" are not present on a Slackware-current installation (I just checked). So, somewhere along the way you probably forgot to check for the *.new files that get installed and that you have to manually copy over their "originals". The files /etc/rc.M.new and /etc/rc.udev.new (but perhaps others, too!) for instance should be manually copied over the existing files /etc/rc.M and /etc/rc.udev
Try finding out where the upgrades left *.new files and examine their content in relation to the originals:
Code:
for i in `find / -type f -name "*.new"` ; do echo ""; echo "**** $i ****" ; diff `dirname $i`/`basename $i .new` $i ; read -p "Press ENTER for next file comparison: " ; done
Eric
|
|
|
09-12-2006, 03:32 AM
|
#3
|
Member
Registered: Oct 2003
Location: Sweden
Distribution: Slackware64-current, SlackwareARM-15.0
Posts: 833
Original Poster
Rep:
|
Quote:
Originally Posted by Alien Bob
The programs "/sbin/udev_run_devd" and "/sbin/udev_run_hotplugd" are not present on a Slackware-current installation (I just checked). So, somewhere along the way you probably forgot to check for the *.new files that get installed and that you have to manually copy over their "originals". The files /etc/rc.M.new and /etc/rc.udev.new (but perhaps others, too!) for instance should be manually copied over the existing files /etc/rc.M and /etc/rc.udev
Try finding out where the upgrades left *.new files and examine their content in relation to the originals:
Code:
for i in `find / -type f -name "*.new"` ; do echo ""; echo "**** $i ****" ; diff `dirname $i`/`basename $i .new` $i ; read -p "Press ENTER for next file comparison: " ; done
Eric
|
All *.new files have been put into place. Thinking that I might have missed some changes in those files, I reinstalled the udev, hotplug and sysvinit packages, and then checked the *.new files, but nothing is to be found there.
Besides the two lines (but repeated loads of times) I also get a lot of messages dealing with modules where there seems to be a permission problem, such as
Code:
...
/etc/rc.d/rc.M: line 80: /dev/.udev/failed/module@snd_timer/uevent: Permission denied
/etc/rc.d/rc.M: line 80: /dev/.udev/failed/module@soundcore/uevent: Permission denied
/etc/rc.d/rc.M: line 80: /dev/.udev/failed/module@yenta_socket/uevent: Permission denied
...
But strangely enough those modules are loaded and behave as normal.
Anyone more suggestions?
Cheers, Leon.
|
|
|
09-22-2006, 04:51 AM
|
#4
|
Member
Registered: Oct 2003
Location: Sweden
Distribution: Slackware64-current, SlackwareARM-15.0
Posts: 833
Original Poster
Rep:
|
Quote:
Originally Posted by Alien Bob
The programs "/sbin/udev_run_devd" and "/sbin/udev_run_hotplugd" are not present on a Slackware-current installation (I just checked).
Eric
|
I found that /sbin/udev_run_devd and /sbin/udev_run_hotplugd are called from /etc/udev/rules.d/50-udev.rules
At the end of that file is the following:
Code:
# Be backward compatible for a while with the /etc/dev.d and /etc/hotplug.d/.
# systems run /etc/hotplug.d/ stuff only if we came from a hotplug event,
# not for udevstart:
ENV{UDEVD_EVENT}=="1", RUN+="/sbin/udev_run_hotplugd"
# always run /etc/dev.d/ stuff for now
RUN+="/sbin/udev_run_devd"
Can someone confirm that these lines are present in their Slack-current setup? Since I don't use hotplug I figure I could simply comment them out.
Cheers, Leon.
UPDATE: yep, commenting those two lines solves it. But I still don't understand why they are there if /sbin/udev_run_hotplugd and /sbin/udev_run_devd don't exist??
UPDATE 2:
Bit more digging shows that the files are part of the alternative versions of udev:
Code:
udev-064-i486-2 in extra/udev-alternate-versions
/sbin/udev_run_devd
udev-071-i486-2 in extra/udev-alternate-versions
/sbin/udev_run_devd
Last edited by BroX; 09-22-2006 at 02:35 PM.
|
|
|
All times are GMT -5. The time now is 02:06 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|