Re: Bug#236343: udev breaks alsamixer settings

Re: Bug#236343: udev breaks alsamixer settings

[Daniel Drake]

Marco d'Itri wrote:
> 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_id\x1470&alloc_id638&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Bug#236343: udev breaks alsamixer settings

[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?

----- Forwarded message from Sam Halliday <fommil@yahoo.ie> -----

Subject: Bug#236343: udev breaks alsamixer settings
Reply-To: Sam Halliday <fommil@yahoo.ie>, 236343@bugs.debian.org
From: Sam Halliday <fommil@yahoo.ie>

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
-- 
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 <tore@linpro.no> -----

Subject: Bug#236343: udev breaks alsamixer settings
Reply-To: Tore Anderson <tore@linpro.no>, 236343@bugs.debian.org
From: Tore Anderson <tore@linpro.no>
To: 236343@bugs.debian.org


  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_id\x1470&alloc_id638&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: Bug#236343: udev breaks alsamixer settings

[Olaf Hering]

 On Sat, Mar 06, Marco d'Itri wrote:

> 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.

-- 
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_id\x1470&alloc_id638&opÃk
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: Bug#236343: udev breaks alsamixer settings

[Alexander E. Patrakov]

On Saturday 06 March 2004 21:27, Marco d'Itri wrote:
> 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>
>   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?
-- 
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_id\x1470&alloc_id638&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: Bug#236343: udev breaks alsamixer settings

[Marco d'Itri]

On Mar 06, Olaf Hering <olh@suse.de> wrote:

 > On Sat, Mar 06, Marco d'Itri wrote:
 >
 >> 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.

-- 
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_id\x1470&alloc_id638&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: Bug#236343: udev breaks alsamixer settings

[Olaf Hering]

 On Sun, Mar 07, Marco d'Itri wrote:

> On Mar 06, Olaf Hering <olh@suse.de> wrote:
> 
>  > On Sat, Mar 06, Marco d'Itri wrote:
>  >
>  >> 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.

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. 

-- 
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_id\x1470&alloc_id638&opÃk
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: Bug#236343: udev breaks alsamixer settings

[Marco d'Itri]

On Mar 07, Olaf Hering <olh@suse.de> wrote:

 >> 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.

 >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.

-- 
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_id\x1470&alloc_id638&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: Bug#236343: udev breaks alsamixer settings

[Olaf Hering]

 On Sun, Mar 07, Marco d'Itri wrote:

> On Mar 07, Olaf Hering <olh@suse.de> wrote:
> 
>  >> 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.

>  >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.

-- 
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_id\x1470&alloc_id638&opÃk
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: Bug#236343: udev breaks alsamixer settings

[Marco d'Itri]

On Mar 07, Olaf Hering <olh@suse.de> wrote:

 >>  >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.

-- 
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_id\x1470&alloc_id638&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel