Hello, I've removed kernel support for ALSA and using alsa-driver instead. Still no luck and same error. And I still don't have /etc/asound.conf or ~/.asoundrc. Is that a problem?
Thanks. On 2/27/06, Boyd Stephen Smith Jr. <[EMAIL PROTECTED]> wrote: > On Sunday 26 February 2006 22:46, Zac Slade <[EMAIL PROTECTED]> wrote > about 'Re: [gentoo-user] ALSA: All modules loaded, mixer unmuted, still no > sound': > > On Sunday 26 February 2006 22:17, Ducky Z. wrote: > > > I'm using the modules provided by the kernel, which is 2.6.15. > > > alsa-lib is 1.0.10. > > > > This should be fine. > > Hrm, is alsa-lib 1.0 backwards compatible to 0.9? 'Cause the kernel > shipped with 0.9 support for a while and my kernel now has to have an > option to provide the 0.9 abi/api. > > You could try either upgrading your kernel or downgrading your alsa-lib. > Or, you could abandon the kernel-provide modules and use alsa-drivers. > > > > When I aplay a file, it shows: > > > > > > ALSA lib pcm_direct.c:900:(snd_pcm_direct_initialize_slave) unable to > > > install hw params > > > ALSA lib pcm_dmix.c:831:(snd_pcm_dmix_open) unable to initialize slave > > > aplay: main:544: audio open error: Inappropriate ioctl for device > > > > Hrm.... Is this being done as root? I think your /etc/asound.conf file > > might need some help. I'm not sure here, but it might not be able to > > play because the wrong information is in the asound.conf file. > > Yeah, try as root and if that works, check permissions on stuff > in /dev/sound. > > If you can get the 1.0 alsa-lib to work with your kernel, you can probably > blow away your asound.conf file anyway. The move to 1.0 made dmix > automatic for devices that don't do hw mixing. > > -- > "If there's one thing we've established over the years, > it's that the vast majority of our users don't have the slightest > clue what's best for them in terms of package stability." > -- Gentoo Developer Ciaran McCreesh > -- > gentoo-user@gentoo.org mailing list > > -- gentoo-user@gentoo.org mailing list
