Messages in this thread | | | Date | Mon, 20 Feb 2006 12:15:18 +0100 | From | Takashi Iwai <> | Subject | Re: No sound from SB live! |
| |
At Sun, 19 Feb 2006 23:25:33 +0100, Pavel Machek wrote: > > On Ne 19-02-06 16:54:34, Lee Revell wrote: > > On Sun, 2006-02-19 at 22:49 +0100, Pavel Machek wrote: > > > Hi! > > > > > > > > I run Ubuntu Breezy, which has: > > > > > > > > > > alsa-utils = 1.0.9a-4ubuntu5 > > > > > > > > The alsa-utils version should not matter, it's alsa-lib that must be > > > > kept in sync with the ALSA version in the kernel. > > > > > > I tried to play with mpg123 using OSS emulation, so that it does not > > > have anything to do with ALSA. No luck. Trying aplay: > > > > > > root@hobit:/dev/snd# aplay > > > /usr/share/xemacs21/xemacs-packages/etc/sounds/hammer.wav > > > aplay: main:533: audio open error: No such file or directory > > > > > > while stracing: > > > > > > open("/dev/snd/pcmC0D0p", O_RDWR) = -1 ENOENT (No such file or > > > directory) > > > close(3) = 0 > > > write(2, "aplay: main:533: ", 17aplay: main:533: ) = 17 > > > write(2, "audio open error: No such file o"..., 43audio open error: No > > > such file or directory) = 43 > > > write(2, "\n", 1 > > > > > > ... but pcmC0D0p is not described in devices.txt...? > > > > Hmm, that's a udev problem or something. If you have a static dev the > > snddevices script that comes with ALSA will create the device files. > > I'm using static /dev... snddevices script indeed fixed that, but it > still does not work. (Is earphone in green connector enough?)
Likely -EUDEV?
> Ouch and that device should be still listed in devices.txt, no?
The minor numbers can be assigned dyanmically if CONFIG_SND_DYNAMIC_MINORS is set, so it may be even confusing to list up there as if static only.
> root@hobit:/dev/snd# aplay > /usr/share/xemacs21/xemacs-packages/etc/sounds/hammer.wav > Playing WAVE > '/usr/share/xemacs21/xemacs-packages/etc/sounds/hammer.wav' : Unsigned > 8 bit, Rate 8000 Hz, Mono > root@hobit:/dev/snd# > > Actually, in a quiet room I think I can hear *something*. Too faint to > recognize :-(.
If you hear something, it's definitely a mixer configuration problem, maybe screwed up by some reason. In such a case, it's easier to re-initialize from the scratch:
Unload the module first, then remove /etc/asound.state (or whatever the distro uses) to prevent the automatic "alsactl restore". Reload the module, then unmute/adjust the volume "PCM" and "Master". The other volumes should have been initialized to be audible.
Takashi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |