[GLLUG] Gentoo not holding sound through reboots

[Mike Szumlinski]

Sorry for the slow reply on this, been on the road for a week and  
haven't had a chance to play around.

I did some checking tonight and found that it is built as a module and  
that it is properly set up to load on boot.

Running rc-update show tells me it is set properly.

Upon further digging, it looks like it is actually X that is not  
seeing the sound card the first time it is launched and is actually  
causing a lock up of X (since sounds need to be played in  
AdvanceMenu).  If I force quit out of X (ctl-alt-backspace) and  
restart it, everything works.

This only happens after a reboot.

Something makes me think it is a latency thing and it takes longer for  
ALSA to come online than it does to fire up X, but it is a little odd.

I've found a temporary workaround by disabling all sounds in the menu,  
but I'd still like to figure out what is going on.  Anyone have any  
ideas?

-Mike

On Apr 11, 2008, at 2:18 AM, Brent Barker wrote:
> Do you have the sound drivers built into the kernel, built as a  
> module, or as a purely userspace daemon?
>
> You say it doesn't work after reboot. Was it working before reboot?  
> If so, how did you get it to work then?
>
> If it's built into the kernel, I'm not sure.
>
> If it's built as a module, then add the module name to the list here:
>
> /etc/modules.autoload.d/kernel-2.x
>
> If it is a userspace program, there should be an initscript under / 
> etc/init.d/  . If so, use the command
>
> # rc-update add <initscript> default
>
> Good luck!
>
> --brent
>
> On Thu, Apr 10, 2008 at 11:31 PM, Karl Schuttler <rexykik at gmail.com>  
> wrote:
> rc update add "module", if i remember correctly.
>
> On Thu, Apr 10, 2008 at 11:30 PM, Karl Schuttler <rexykik at gmail.com>  
> wrote:
> > Sounds like you need to add the module to the list of modules that  
> load on boot.
> >
> >
> >
> >  On Thu, Apr 10, 2008 at 10:19 PM, Mike Szumlinski  
> <szumlins at mac.com> wrote:
> >  > I just recently built my second MAME arcade cabinet and for some
> >  >  reason I'm having issues with the sound drivers not loading  
> properly
> >  >  after a reboot.
> >  >
> >  >  After booting into the system and running alsoconf, it detects  
> the
> >  >  card, activates it, and says it is loading it into /etc/ 
> modules.d/alsa
> >  >
> >  >  When I look in that file, it appears as though everything is set
> >  >  right, but I'm kind of new to sound configs in linux.  In the  
> past
> >  >  alsoconf has always just worked for me and I've never had any  
> issue.
> >  >
> >  >  Any ideas on where to start looking for the problem would be  
> much
> >  >  appreciated.
> >  >
> >  >  -Mike
> >  >  _______________________________________________
> >  >  linux-user mailing list
> >  >  linux-user at egr.msu.edu
> >  >  http://mailman.egr.msu.edu/mailman/listinfo/linux-user
> >  >
> >
> _______________________________________________
> linux-user mailing list
> linux-user at egr.msu.edu
> http://mailman.egr.msu.edu/mailman/listinfo/linux-user
>
> _______________________________________________
> linux-user mailing list
> linux-user at egr.msu.edu
> http://mailman.egr.msu.edu/mailman/listinfo/linux-user