Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[Solved] udevd failed to execute '/usr/sbin/alsactl'
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
buptwugh
Tux's lil' helper
Tux's lil' helper


Joined: 16 Jan 2012
Posts: 92
Location: Beijing,China

PostPosted: Wed Feb 29, 2012 3:07 am    Post subject: [Solved] udevd failed to execute '/usr/sbin/alsactl' Reply with quote

When the system boot
Some confuse message show:

Code:

udev[16025]: failed to execute '/usr/sbin/alsactl' '/usr/sbin/alsactl restore 0': No such file or directory
udev[16029]: failed to execute '/usr/sbin/alsactl' '/usr/sbin/alsactl restore 1': No such file or directory


How to fix it?

I find the answer by Google.

And It seem that I can not put "/usr" on separate partition.


Thank you,
Wugh


Last edited by buptwugh on Wed Feb 29, 2012 12:07 pm; edited 1 time in total
Back to top
View user's profile Send private message
VoidMage
Watchman
Watchman


Joined: 14 Oct 2006
Posts: 5433

PostPosted: Wed Feb 29, 2012 4:29 am    Post subject: Reply with quote

The simple answer is that /usr needs to be accessible when udev is run - it means if /usr is separate, initramfs needs to mount it.
Back to top
View user's profile Send private message
buptwugh
Tux's lil' helper
Tux's lil' helper


Joined: 16 Jan 2012
Posts: 92
Location: Beijing,China

PostPosted: Wed Feb 29, 2012 4:45 am    Post subject: Reply with quote

Thanks,
But is there any method to fix it except changing my partitions
Back to top
View user's profile Send private message
aCOSwt
Moderator
Moderator


Joined: 19 Oct 2007
Posts: 2537
Location: Hilbert space

PostPosted: Wed Feb 29, 2012 8:19 am    Post subject: Reply with quote

VoidMage is indeed correct and initramfs is probably a solution for you.

However :

1/ Keep in mind that your problems might not be limited to /usr.
alsactl restore will need /var/lib/alsa/asound.state
So, if your /var tree is also in a separate partition...

2/ If this is the only problem you face with udev at boot then it should not be a problem.
I get this kind of messages too but my system works perfectly well and the mixer levels are actually restored.
Check if they are correctly restored on your system and if it is the case then...
You can safely ignore these messages and the initramfs workaround becomes needless.

How comes ?
udev-postmount wrote:

# Run the events that failed at first udev trigger
udevadm trigger --type=failed -v


Basically, all the scripts that will have failed before localmount are put into a queue and will be retried after localmount.

As you do not get you error repeated, it simply means that these scripts were successful at postmount.

There is an interesting debate about all this (and more) you can find there : http://archives.gentoo.org/gentoo-dev/msg_948f10553ba75ca1b99b08f17e842f9d.xml
_________________
Back to top
View user's profile Send private message
buptwugh
Tux's lil' helper
Tux's lil' helper


Joined: 16 Jan 2012
Posts: 92
Location: Beijing,China

PostPosted: Wed Feb 29, 2012 12:06 pm    Post subject: Reply with quote

Thanks aCOSwt,

My Audio device work perfectly , So The Message should not be a problem.

Just Ignore this.
Back to top
View user's profile Send private message
VoidMage
Watchman
Watchman


Joined: 14 Oct 2006
Posts: 5433

PostPosted: Wed Feb 29, 2012 2:37 pm    Post subject: Reply with quote

@aCOSwt: bzzzzt, wrong - at least partially.
See the NEWS file in the udev tarball, the last block in 174 part.
Back to top
View user's profile Send private message
aCOSwt
Moderator
Moderator


Joined: 19 Oct 2007
Posts: 2537
Location: Hilbert space

PostPosted: Wed Feb 29, 2012 3:26 pm    Post subject: Reply with quote

VoidMage wrote:
@aCOSwt: bzzzzt, wrong - at least partially.
See the NEWS file in the udev tarball, the last block in 174 part.

:oops:
Do you mean
udev-174-news wrote:
The support for 'udevadm trigger --type=failed, and the
RUN{fail_event_on_error} attribute was removed.
?
:evil:
Well well... I was forced to fetch this 174 version on sources.buildroot.net
BTW, I am running Gentoo you know and latest portage's normally available version for udev is 171 :wink:
I infered it was buptwugh's case as well.

Thank you for the warning anyway. I'll take care on some future update. :evil:
_________________
Back to top
View user's profile Send private message
viralex
Apprentice
Apprentice


Joined: 24 Apr 2008
Posts: 223
Location: Viareggio (Lu,Italy)

PostPosted: Fri Apr 13, 2012 9:30 pm    Post subject: Reply with quote

I have to manually run "udevadm trigger" to get soundcard revealed by pulseaudio ... every boot with udev-182-r3 :evil:
udev-postmount script doesn't call udevadm trigger on new udev versions...

I could change postmount scpript myself :?
but i'd rather prefer to understand what's going on
Back to top
View user's profile Send private message
MerlinYoda
n00b
n00b


Joined: 23 May 2007
Posts: 8
Location: Indiana, United States, Earth, Sol System, Milky Way Galaxy, "The Universe"

PostPosted: Wed Sep 19, 2012 6:28 am    Post subject: Reply with quote

I realize I'm a little late to the game on this one, but I just figured out that the root source of the error messages which the OP posted is actually due to a script placed into udev's rules.d directory by the media-sound/alsa-utils package (specific file being /lib/udev/rules.d/90-alsa-restore.rules).

My particular solution was to have /usr in the root file system (a partition on a (Fake)RAID1 HDD array) so that the necessary files would be present prior to the "real" /usr partition (residing on an SSD) being mounted over the afformentioned /usr folder. This way I get both a speed boost and redundancy out of the deal (as long as I make a point to back up the data in the SSD partition to the underlying the root file system as needed). However, in cases where such data duplication is either not desired or not an option, the aformentioned script file may be set aside (either deleted or tucked out of the way somewhere else in the filesystem) and the errors should disappear on startup.

Also, since the alsasound init script should (and seems to) *already* handle this, as it was touched upon earlier posts, the udev script shouldn't be necessary to have working sound. Given this, it would apper that alsa-utils really *shouldn't* be adding this script to udev rules.d directory in the first place but handling these details itself (and only once everything in fstab has actually been *mounted* first!!!) rather than to shuffe this particular task off through the udev init script for whatever reasons they had for doing so in the first place.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum