Re: [gentoo-user] [Resolved] Absolutely no sound whatsoever after latest emerge update
On Sat, Sep 27, 2008 at 08:05:06PM -0500, Dale wrote > This may be waaay off here, do you have that parallel start up thing > turned on? You know, where multiple services can be started at > the same time without waiting for the startup to complete. I read > somewhere a while back where some were having various trouble but > not lately. If you do, may want to try it with it turned off and > see if that helps. I hadn't thought of that, but my/etc/conf.d/rc has RC_PARALLEL_STARTUP="no" Thanks for the sauggetsion anyways. -- Walter Dnes <[EMAIL PROTECTED]>
Re: [gentoo-user] [Resolved] Absolutely no sound whatsoever after latest emerge update
Walter Dnes wrote: On Sat, Sep 27, 2008 at 09:47:27PM +0200, Tamer Higazi wrote why do you guys make it more complicated as it is?! Just write in the shell: rc-update add alsasound default I *DO* have alsasound in my default. Since you obviously have not read the URL I pointed to, here is a partial quote... I stopped esound (esd) and alsasound systems (this is under Gentoo). Upon restarting the alsasound system, the low level sound driver modules (snd_intel8x0m, snd_intel8x0, snd_ac97_codec, ac97_bus), perhaps others, got loaded and they were not loaded when the "unable to open slave" message was being generated. Subsequently mplayer was able to load and play audio tracks. So this message may be associated with hardware level drivers being unavailable for some reason. The problem seems to be a dependancy on some resource that is not available early on in the boot process. Re-starting the alsasound daemon later on works around that problem. This may be waaay off here, do you have that parallel start up thing turned on? You know, where multiple services can be started at the same time without waiting for the startup to complete. I read somewhere a while back where some were having various trouble but not lately. If you do, may want to try it with it turned off and see if that helps. Just something to think about just in case. Dale :-) :-)
Re: [gentoo-user] [Resolved] Absolutely no sound whatsoever after latest emerge update
On Sat, Sep 27, 2008 at 09:47:27PM +0200, Tamer Higazi wrote > why do you guys make it more complicated as it is?! > > Just write in the shell: > > rc-update add alsasound default I *DO* have alsasound in my default. Since you obviously have not read the URL I pointed to, here is a partial quote... > I stopped esound (esd) and alsasound systems (this is under Gentoo). > Upon restarting the alsasound system, the low level sound driver > modules (snd_intel8x0m, snd_intel8x0, snd_ac97_codec, ac97_bus), > perhaps others, got loaded and they were not loaded when the "unable > to open slave" message was being generated. Subsequently mplayer > was able to load and play audio tracks. > > So this message may be associated with hardware level drivers being > unavailable for some reason. The problem seems to be a dependancy on some resource that is not available early on in the boot process. Re-starting the alsasound daemon later on works around that problem. -- Walter Dnes <[EMAIL PROTECTED]>
Re: [gentoo-user] [Resolved] Absolutely no sound whatsoever after latest emerge update
why do you guys make it more complicated as it is?! Just write in the shell: rc-update add alsasound default or for boot time: rc-update add alsasound boot and then the problem is solved for all times! Tamer Willie Wong schrieb: On Sat, Sep 27, 2008 at 03:35:04AM -0400, Penguin Lover Walter Dnes squawked: Namely, restart alsasound (as root). /etc/init.d/alsasound restart I've put this in my /etc/conf.d/local.start Why is it necessary to put that in /etc/conf.d/local.start? Shouldn't the reboot make alsasound start clean already? W
Re: [gentoo-user] [Resolved] Absolutely no sound whatsoever after latest emerge update
On Sat, Sep 27, 2008 at 03:35:04AM -0400, Penguin Lover Walter Dnes squawked: > Namely, restart alsasound (as root). > > /etc/init.d/alsasound restart > > I've put this in my /etc/conf.d/local.start Why is it necessary to put that in /etc/conf.d/local.start? Shouldn't the reboot make alsasound start clean already? W -- A man's home is his castle, in a manor of speaking. Sortir en Pantoufles: up 659 days, 18:15
[gentoo-user] [Resolved] Absolutely no sound whatsoever after latest emerge update
On Fri, Sep 26, 2008 at 10:27:14AM -0400, Willie Wong wrote > On Fri, Sep 26, 2008 at 02:14:48AM -0400, Penguin Lover Walter Dnes squawked: > > [AO_ALSA] alsa-lib: pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave > > [AO_ALSA] Playback open error: Device or resource busy > > DVB card number must be between 1 and 4 > > AO: [null] 22050Hz 2ch s16le (2 bytes per sample) > > This points to an issue with your alsa configuration/installation. > > > mpg123 doesn't work > > > > [d530][waltdnes][~] mpg123 > > /home/misc/music/pop_standards/Tennessee_Waltz_-_Patti_Page.mp3 > > ALSA lib pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave > > [alsa.c:146] error: cannot open device default > > [audio.c:517] error: failed to open audio device > > [mpg123.c:709] error: Failed to initialize output, goodbye. > > Same error as above, a problem with alsa. Another Google search. In addition to a bunch of people with problems, this time around, someone had a solution... http://www.nabble.com/Re%3A--Bug-37649--pulseaudio%2C-REOPENED%3A-ALSA-lib-pcm_dmix.c%3A996%3A%28-snd_pcm_dmix_open%29-unable-to-open-slave-p16659896.html Namely, restart alsasound (as root). /etc/init.d/alsasound restart I've put this in my /etc/conf.d/local.start -- Walter Dnes <[EMAIL PROTECTED]>
