Re: [Alsa-user] Problem with the sound card ATI Technologies Inc SBx00 Azalia (Intel HDA)

2011-02-12 Thread Dimitrios Glentadakis
Στις Παρασκευή 11 Φεβρουάριος 2011 20:58:54 Torquil Macdonald Sørensen γράψατε: On 11/02/11 20:34, Dimitrios Glentadakis wrote: Στις Παρασκευή 11 Φεβρουάριος 2011 20:08:09 Torquil Macdonald Sørensen γράψατε: On 11/02/11 19:20, Dimitrios Glentadakis wrote: Hi i subscribed to this list to

Re: [Alsa-user] No sound, no /proc/asound/

2011-02-12 Thread Marcin Szyniszewski
Thank you all for the replies! Very appreciated! :)  $ sudo modprobe [module] FATAL: Error inserting snd (/lib/modules/2.6.35-25-generic/kernel/sound/acore/snd.ko): Unknown symbol in module, or unknown parameter (see dmesg) WARNING: Error running install command for snd WARNING: Error inserting

[Alsa-user] AudioTrak Prodigy HD2 - either no volume control, or no sound

2011-02-12 Thread greenender
I got a problem with AudioTrak Prodigy HD2.. By default, the soundcard is recognized as ICE1724 card. The sound output is perfect, but _no volume control_ in alsa (neither in amixer nor in alsamixer). I have used all models from the ice1724 driver, by changing alsa-base.conf: options

Re: [Alsa-user] No sound, no /proc/asound/

2011-02-12 Thread James Shatto
As I suspected, the modules aren't loaded so alsa isn't even running. Hence your original open error(s). How did you install alsa? Not that I think it is your issue, but it could be. If you boot with lilo, you need to re-install lilo after creating a new kernel. Even if it's technically the

Re: [Alsa-user] No sound, no /proc/asound/

2011-02-12 Thread Torsten Schenk
Like my previous speaker already told: the modules cannot be loaded because other modules are missing. Either you don't have modules installed at all (which most certainly means you have a wrong kernel image running) or the module loader cannot resolve the dependencies. To check if the module

Re: [Alsa-user] Raw Midi Bug?

2011-02-12 Thread Maxime Chevalier-Boisvert
It seems I can sidestep the bug by setting my raw midi port to nonblocking mode and then reading as much data as I can with each call. Is there somewhere I can report this bug so it will get fixed in future releases? - Maxime On 11-02-11 11:30 PM, Maxime Chevalier-Boisvert wrote:

Re: [Alsa-user] No sound, no /proc/asound/

2011-02-12 Thread Marcin Szyniszewski
On Sat, Feb 12, 2011 at 16:26, James Shatto wwwshad...@gmail.com wrote: As I suspected, the modules aren't loaded so alsa isn't even running. Hence your original open error(s). How did you install alsa? Not that I think it is your issue, but it could be. If you boot with lilo, you need to

Re: [Alsa-user] No sound, no /proc/asound/

2011-02-12 Thread James Shatto
$ sudo dpkg -l '*alsa*' Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Description

Re: [Alsa-user] No sound, no /proc/asound/

2011-02-12 Thread Marcin Szyniszewski
On Sat, Feb 12, 2011 at 22:50, James Shatto wwwshad...@gmail.com wrote: Well there's the old school ways. When all else fails, re-install. Fortunately in linux that's not as dreaded as it sounds $ sudo dpkg --purge --force-all alsa alsa-base alsa-firmware-loaders alsa-oss alsa-source

Re: [Alsa-user] No sound, no /proc/asound/

2011-02-12 Thread Bill Unruh
On Sat, 12 Feb 2011, Marcin Szyniszewski wrote: On Sat, Feb 12, 2011 at 16:26, James Shatto wwwshad...@gmail.com wrote: $ sudo depmod -a $ sudo modprobe snd-hda-intel WARNING: Error inserting snd_timer (/lib/modules/2.6.35-25-generic/kernel/sound/acore/snd-timer.ko): Unknown symbol in

Re: [Alsa-user] No sound, no /proc/asound/

2011-02-12 Thread Bill Unruh
On Sat, 12 Feb 2011, James Shatto wrote: $ sudo dpkg -l '*alsa*' Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name

Re: [Alsa-user] No sound, no /proc/asound/

2011-02-12 Thread James Shatto
Basically the same way. To redo your kernel. dpkg --purge --force-all apt-get install. Just make sure that you DO NOT do it to the kernel that you are currently running. Which might mean installing an older kernel as a safe recovery and boot to that before recovering the kernel you want to