Can't get the sound going at all. I installed fresh CRUX 2.3, KDE with kdemultimedia package, esound, compiled Soundcard (Realtek ALC850 integrated in NVidia 6100) support in kernel, esound has started, still have a message popping up in KDE: Device: default can't be opened for playback (No such device). The same message does not appear, when logging as root, but still no sound. Sound support in kernel: $dmesg ... Intel 810 + AC97 Audio, version 1.01, 20:01:43 Apr 16 2007 Advanced Linux Sound Architecture Driver Version 1.0.14rc1 (Tue Jan 09 09:56:17 2007 UTC). ACPI: PCI Interrupt Link [LACI] enabled at IRQ 23 ACPI: PCI Interrupt 0000:00:10.2[C] -> Link [LACI] -> GSI 23 (level, low) -> IRQ 16 PCI: Setting latency timer of device 0000:00:10.2 to 64 intel8x0_measure_ac97_clock: measured 56004 usecs intel8x0: clocking to 44803 ALSA device list: #0: Intel ICH with ALC850 at 0xfebdc000, irq 16 oprofile: using NMI interrupt. ... No devices /dev/dsp or anything like that, only: ls /dev/* ... /dev/snd: controlC0 pcmC0D0c pcmC0D0p pcmC0D1c pcmC0D2p timer ... Can't find any manual either. Any suggestions, please? Alexei
Can't get the sound going at all. I installed fresh CRUX 2.3, KDE with kdemultimedia package, esound, compiled Soundcard (Realtek ALC850 integrated in NVidia 6100) support in kernel, esound has started, still have a message popping up in KDE: Device: default can't be opened for playback (No such device).
I suggest against using esound, it sucks. The only added benefit for using sound daemons is forwarding sound through your network, if you don't need it, then why use it? If your drivers don't support hardware mixing and you need it, try using the dmix plugin from alsa. Refer to the alsa documentation for detailed instructions. Finally, if you still want to use a sound daemon, use artsd instead of esound. Also, make sure you select alsa as the sound device.
...
No devices /dev/dsp or anything like that, only: ls /dev/*
/dev/dsp is for OSS only. If you need it, use the oss layer modules. Notice that new versions of skype and flash already support alsa, so OSS isn't needed for them anymore.
Any suggestions, please?
About permissions: There are several approaches to setting up permissions for the alsa devices. One of them is using the "audio" group. You can use udev to set up the device permissions at boot time for the "audio" group, or for everybody. I think the best approach in a multi-user environment is to chown /dev/snd/* devices at login time in /etc/X11/kdm/Xstartup. The only problem with this is that KDE support for "user switching" will run Xstartup when logging in any additional users. This will chown the sound devices to the new user, eliminating them for the first user logged in. If you come up with something better, let me know. Regards, Alan
Alan Mizrahi [2007-04-16 15:04]:
I think the best approach in a multi-user environment is to chown /dev/snd/* devices at login time in /etc/X11/kdm/Xstartup. The only problem with this is that KDE support for "user switching" will run Xstartup when logging in any additional users. This will chown the sound devices to the new user, eliminating them for the first user logged in. If you come up with something better, let me know.
udev puts those devices in the "audio" group -- so just add your user(s) to that group as well, and things should work nicely :) Regards, Tilman -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?
participants (3)
-
Alan Mizrahi -
Alexei Danchenkov -
Tilman Sauerbeck