Skip to contentSkip to conversation

Bug#236343: udev breaks alsamixer settings

DISCUSSION Daniel Drake 4 participants 9 messages Mar 6, 2004 – Mar 7, 2004

lore
Share & tools
lore
#0 lore raw
Quoted 3 lines · Marco d'Itri

Can this be fixed in udev or do I need to teach all users and maintainers to put call sleep in the install statements of modprobe.conf?

BTW, I also found the same problem, and same solution.

http://bugs.gentoo.org/show_bug.cgi?id9345

Daniel

-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

#1 lore raw

Can this be fixed in udev or do I need to teach all users and maintainers to put call sleep in the install statements of modprobe.conf?

----- Forwarded message from Sam Halliday <[email protected]> -----

Subject: Bug#236343: udev breaks alsamixer settings
Reply-To: Sam Halliday <[email protected]>, [email protected]
From: Sam Halliday <[email protected]>

Package: udev
Version: 0.021-1

hi there,

i just installed udev on a debian system running the linux kernel, version 2.6.3.

i use ALSA and for some reason i needed to use alsamixer to reset my sound settings after installing udev and rebooting. i restarted the alsa daemon to save these settings /etc/init.d/alsa restart, but upon restarting; the sound was again mute.

cheers,
Sam

Signature · 47 lines
Free High School Science Texts
  http://savannah.nongnu.org/projects/fhsst
Sam's Homepages
  http://fommil.homeunix.org/~samuel
  http://www.ma.hw.ac.uk/~samuel



----- End forwarded message -----
----- Forwarded message from Tore Anderson <[email protected]> -----

Subject: Bug#236343: udev breaks alsamixer settings
Reply-To: Tore Anderson <[email protected]>, [email protected]
From: Tore Anderson <[email protected]>
To: [email protected]


  The reason why this happens is that when the ALSA init script first
 loads the modules and then goes on to restore the mixer settings, udev
 isn't quick enough to have create all the (mixer) devices.

  I added a 'sleep 2s' to /etc/init.d/alsa, right before the "alsactl
 restore" invocation, and it has been working flawlessly ever since.

  I'm not sure whether or not this should be considered a bug in
 alsa-base or udev (or perhaps some of both?), though.

-- 
Tore Anderson


----- End forwarded message -----

-- 
ciao, |
Marco | [4940 trRiDXpW4zBhA]


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
#2 lore raw
In reply to Daniel Drake
Quoted 3 lines · Marco d'Itri

Can this be fixed in udev or do I need to teach all users and maintainers to put call sleep in the install statements of modprobe.conf?

do that stuff in the sound.agent, where it belongs.

Signature · 14 lines
USB is for mice, FireWire is for men!

sUse lINUX ag, nÜRNBERG


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70&alloc_id638&op�k
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
#3 lore raw
In reply to Daniel Drake
Quoted 3 lines · Marco d'Itri

Can this be fixed in udev or do I need to teach all users and maintainers to put call sleep in the install statements of modprobe.conf?

<snip>

Quoted 3 lines

The reason why this happens is that when the ALSA init script first
loads the modules and then goes on to restore the mixer settings, udev isn't quick enough to have create all the (mixer) devices.

Is this race possible with traditional devfs?

Signature · 12 lines
Alexander E. Patrakov


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
#4 lore raw
In reply to Daniel Drake
Quoted 7 lines · Olaf Hering
Quoted 3 lines · Marco d'Itri

Can this be fixed in udev or do I need to teach all users and maintainers to put call sleep in the install statements of modprobe.conf?

do that stuff in the sound.agent, where it belongs.

I can't see how this will eliminate the race.
It even looks like that this will guarantee that sound.agent (called by default.hotplug) will be run before udev.hotplug by the hotplug multiplexer.

Signature · 13 lines
ciao, |
Marco | [4949 sfnxvTXDPylVI]


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
#5 lore raw
In reply to Daniel Drake
Quoted 8 lines · Marco d'Itri
Quoted 6 lines · Olaf Hering
Quoted 3 lines · Marco d'Itri

Can this be fixed in udev or do I need to teach all users and maintainers to put call sleep in the install statements of modprobe.conf?

Quoted 6 lines
Quoted 1 line

do that stuff in the sound.agent, where it belongs.

I can't see how this will eliminate the race.
It even looks like that this will guarantee that sound.agent (called by default.hotplug) will be run before udev.hotplug by the hotplug multiplexer.

no, sound.agent runs when the driver is ready and triggers the event. you will only need the rcalsafoo script if the driver is compiled into th kernel. and you dont need a udev.hotplug either.

Signature · 14 lines
USB is for mice, FireWire is for men!

sUse lINUX ag, nÜRNBERG


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70&alloc_id638&op�k
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
#6 lore raw
In reply to Daniel Drake
Quoted 6 lines · Olaf Hering
Quoted 4 lines

I can't see how this will eliminate the race.
It even looks like that this will guarantee that sound.agent (called by default.hotplug) will be run before udev.hotplug by the hotplug multiplexer.

no, sound.agent runs when the driver is ready and triggers the event.

But the driver does not know when udev has created the device nodes. The problem is that the mixer application is started before udev has finished creating the nodes in /dev.

Quoted 2 lines

you will only need the rcalsafoo script if the driver is compiled into th kernel. and you dont need a udev.hotplug either.

It's the symlink to udevsend.

Signature · 13 lines
ciao, |
Marco | [4950 veE9A5ARrM6c2]


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
#7 lore raw
In reply to Daniel Drake
Quoted 11 lines · Marco d'Itri
Quoted 6 lines · Olaf Hering
Quoted 4 lines

I can't see how this will eliminate the race.
It even looks like that this will guarantee that sound.agent (called by default.hotplug) will be run before udev.hotplug by the hotplug multiplexer.

no, sound.agent runs when the driver is ready and triggers the event.

But the driver does not know when udev has created the device nodes. The problem is that the mixer application is started before udev has finished creating the nodes in /dev.

the driver doesnt care, it tells you when it is ready and udev can create the device node, you can configure the device after udev. done.

Quoted 3 lines
Quoted 2 lines

you will only need the rcalsafoo script if the driver is compiled into th kernel. and you dont need a udev.hotplug either.

It's the symlink to udevsend.

yes, remove it, call udev from the *.agent if /sys/$DEVPATH/dev exists.

Signature · 14 lines
USB is for mice, FireWire is for men!

sUse lINUX ag, nÜRNBERG


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70&alloc_id638&op�k
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
#8 lore raw
In reply to Daniel Drake
Quoted 4 lines · Olaf Hering
Quoted 3 lines
Quoted 2 lines

you will only need the rcalsafoo script if the driver is compiled into th kernel. and you dont need a udev.hotplug either.

It's the symlink to udevsend.

yes, remove it, call udev from the *.agent if /sys/$DEVPATH/dev exists.

When did this change happen? The 021 Makefile still installs the /etc/hotplug.d/default/udev.hotplug symlink, and I do not remember any mailing list discussion about modifying the hotplug package to support udev.

Signature · 13 lines
ciao, |
Marco | [4954 stNeXUi.M9VpY]


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel