My recent upgrade caused my sound card not working any more. Checking back
at my packages version log, the only related upgrade is that
alsa-base_1.0.17.dfsg-2 is upgraded to alsa-base_1.0.17.dfsg-4.
The rest are still the same:
$ ls /dev/dsp
ls: cannot access /dev/dsp: No such file or directory
$ cat /dev/sndstat
Sound Driver:3.8.1a-980706 (ALSA v1.0.16 emulation code)
Kernel: Linux helios.selfip.org 2.6.26-grml #1 SMP PREEMPT Wed Nov 26 21:41:43 UTC 2008 i686
Config options: 0
Installed drivers:
Type 10: ALSA emulation
Card config:
VIA 8237 with AD1980 at 0xc800, irq 22
Audio devices: NOT ENABLED IN CONFIG
Synth devices: NOT ENABLED IN CONFIG
Midi devices: NOT ENABLED IN CONFIG
Timers:
31: system timer
Mixers: NOT ENABLED IN CONFIG
How should I fix that?
FYI, the upgrade problem was more than that, I was able to fix another one:
amixer: Mixer attach default error: No such device
which is what I get after successfully done the alsaconfig
Loading driver...
Setting default volumes...
amixer: Mixer attach default error: No such device
. . .
Now ALSA is ready to use
Here is a run-down of my sound card info:
(Ref: http://groups.google.com/group/linux.debian.bugs.dist/browse_thread/
thread/40209b7807c493d0/329f7bac986a6a93?lnk=raot&pli=1)
$ cat /etc/modules
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
# Parameters can be specified after the module name.
$ cat /etc/modprobe.d/sound
alias snd-card-0 snd-via82xx
options snd-via82xx index=0
My "amixer: Mixer attach default error" problem was solved by
But I can't go any further via googling. E.g., among many other tryings,
following Florian Kulzer's advice on merely unloading and reloading the
modules didn't work for me:
% modprobe -r snd_via82xx snd_pcm snd_seq
FATAL: Module snd_pcm is in use.
% modprobe snd_via82xx
% modprobe snd_seq
Thanks
--
Tong (remove underscore(s) to reply)
http://xpt.sourceforge.net/techdocs/
http://xpt.sourceforge.net/tools/
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
02-15-2009, 04:17 PM
Michael Pobega
ALSA devices: NOT ENABLED IN CONFIG
On Sun, Feb 15, 2009 at 04:25:19PM +0000, T o n g wrote:
> [warning, long post]
>
> Hi,
>
> My recent upgrade caused my sound card not working any more. Checking back
> at my packages version log, the only related upgrade is that
> alsa-base_1.0.17.dfsg-2 is upgraded to alsa-base_1.0.17.dfsg-4.
> The rest are still the same:
>
> alsa-oss_1.0.15-1
> alsa-utils_1.0.16-2
> alsamixergui_0.9.0rc2-1-9
>
> Yet, now I've got:
>
> $ ls /dev/dsp
> ls: cannot access /dev/dsp: No such file or directory
>
> $ cat /dev/sndstat
> Sound Driver:3.8.1a-980706 (ALSA v1.0.16 emulation code)
> Kernel: Linux helios.selfip.org 2.6.26-grml #1 SMP PREEMPT Wed Nov 26 21:41:43 UTC 2008 i686
> Config options: 0
>
> Installed drivers:
> Type 10: ALSA emulation
>
> Card config:
> VIA 8237 with AD1980 at 0xc800, irq 22
>
> Audio devices: NOT ENABLED IN CONFIG
>
> Synth devices: NOT ENABLED IN CONFIG
>
> Midi devices: NOT ENABLED IN CONFIG
>
> Timers:
> 31: system timer
>
> Mixers: NOT ENABLED IN CONFIG
>
> How should I fix that?
>
> FYI, the upgrade problem was more than that, I was able to fix another one:
>
> amixer: Mixer attach default error: No such device
>
> which is what I get after successfully done the alsaconfig
>
> Loading driver...
> Setting default volumes...
> amixer: Mixer attach default error: No such device
> . . .
> Now ALSA is ready to use
>
> Here is a run-down of my sound card info:
> (Ref: http://groups.google.com/group/linux.debian.bugs.dist/browse_thread/
> thread/40209b7807c493d0/329f7bac986a6a93?lnk=raot&pli=1)
>
> $ hwinfo --sound
> 14: PCI 11.5: 0401 Multimedia audio controller
> [Created at pci.310]
> Unique ID: Ssy1.KzJ6TO9PmfB
> SysFS ID: /devices/pci0000:00/0000:00:11.5
> SysFS BusID: 0000:00:11.5
> Hardware Class: sound
> Model: "VIA VT8233/A/8235/8237 AC97 Audio Controller"
> Vendor: pci 0x1106 "VIA Technologies, Inc."
> Device: pci 0x3059 "VT8233/A/8235/8237 AC97 Audio Controller"
> SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
> SubDevice: pci 0x80b0 "A7V600/K8V-X/K8V Deluxe motherboard (ADI AD1980 codec [SoundMAX])"
> Revision: 0x60
> Driver: "VIA 82xx Audio"
> Driver Modules: "snd_via82xx"
> I/O Ports: 0xc800-0xc8ff (rw)
> IRQ: 22 (no events)
> Module Alias: "pci:v00001106d00003059sv00001043sd000080B0bc04sc0 1i00"
> Driver Info #0:
> Driver Status: snd_via82xx is active
> Driver Activation Cmd: "modprobe snd_via82xx"
> Config Status: cfg=new, avail=yes, need=no, active=unknown
>
> $ dpkg -l | grep asou
> ii libasound2 1.0.16-2 ALSA library
>
> $ dpkg -l | grep alsa
> ii alsa-base 1.0.17.dfsg-4 ALSA driver configuration files
> ii alsa-oss 1.0.15-1 ALSA wrapper for OSS applications
> ii alsa-utils 1.0.16-2 ALSA utilities
> ii alsamixergui 0.9.0rc2-1-9 graphical soundcard mixer for ALSA soundcard
> ii libesd-alsa0 0.2.36-3 Enlightened Sound Daemon (ALSA) - Shared lib
>
> $ lsmod | grep snd
> snd_via82xx 22808 0
> gameport 11788 1 snd_via82xx
> snd_mpu401_uart 7936 1 snd_via82xx
> snd_via82xx_modem 12040 0
> snd_ac97_codec 91428 2 snd_via82xx,snd_via82xx_modem
> snd_seq_midi 7680 0
> snd_seq_midi_event 7552 1 snd_seq_midi
> snd_rawmidi 19200 2 snd_mpu401_uart,snd_seq_midi
> ac97_bus 3584 1 snd_ac97_codec
> snd_pcm 59396 3 snd_via82xx,snd_via82xx_modem,snd_ac97_codec
> snd_seq 42816 2 snd_seq_midi,snd_seq_midi_event
> snd_timer 18696 2 snd_pcm,snd_seq
> snd_seq_device 7692 3 snd_seq_midi,snd_rawmidi,snd_seq
> snd 44344 9
> snd_via82xx,snd_mpu401_uart,snd_via82xx_modem,snd_ ac97_codec,snd_rawmidi,snd_pcm,snd_seq,snd_timer,s nd_seq_device
> snd_page_alloc 9096 3 snd_via82xx,snd_via82xx_modem,snd_pcm
> soundcore 7496 1 snd
>
> $ cat /proc/asound/version
> Advanced Linux Sound Architecture Driver Version 1.0.16.
>
> $ cat /proc/asound/cards
> 0 [V8237 ]: VIA8237 - VIA 8237
> VIA 8237 with AD1980 at 0xc800, irq 22
>
> $ cat /proc/interrupts
> CPU0
> 0: 76 IO-APIC-edge timer
> 1: 1192 IO-APIC-edge i8042
> 6: 3 IO-APIC-edge floppy
> 8: 5 IO-APIC-edge rtc0
> 9: 0 IO-APIC-fasteoi acpi
> 12: 105467 IO-APIC-edge i8042
> 14: 40 IO-APIC-edge pata_via
> 15: 99 IO-APIC-edge pata_via
> 16: 0 IO-APIC-fasteoi radeon@pci:0000:01:00.0
> 17: 3184 IO-APIC-fasteoi eth0
> 20: 32542 IO-APIC-fasteoi sata_via
> 21: 0 IO-APIC-fasteoi uhci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb3, uhci_hcd:usb4, ehci_hcd:usb5
> 22: 0 IO-APIC-fasteoi VIA8237
> NMI: 0 Non-maskable interrupts
> LOC: 122874 Local timer interrupts
> RES: 0 Rescheduling interrupts
> CAL: 0 function call interrupts
> TLB: 0 TLB shootdowns
> TRM: 0 Thermal event interrupts
> SPU: 0 Spurious interrupts
> ERR: 0
> MIS: 0
>
> $ cat /etc/modules
> # /etc/modules: kernel modules to load at boot time.
> #
> # This file contains the names of kernel modules that should be loaded
> # at boot time, one per line. Lines beginning with "#" are ignored.
> # Parameters can be specified after the module name.
>
>
> $ cat /etc/modprobe.d/sound
> alias snd-card-0 snd-via82xx
> options snd-via82xx index=0
>
> My "amixer: Mixer attach default error" problem was solved by
>
> % aptitude install libesd-alsa0
>
> (Ref: http://www.linuxquestions.org/questions/debian-26/no-sound-debian-lenny-amd64-gigabyte-ga-
> ma78gm-s2h-amd-780g-677646/)
>
> But I can't go any further via googling. E.g., among many other tryings,
> following Florian Kulzer's advice on merely unloading and reloading the
> modules didn't work for me:
>
> % modprobe -r snd_via82xx snd_pcm snd_seq
> FATAL: Module snd_pcm is in use.
>
> % modprobe snd_via82xx
> % modprobe snd_seq
>
> Thanks
>
Have you tried running alsaconf as root? Usually when there are upgrades
to alsa you have to do it, things tend to change pretty often in the
ALSA setup.
On Sun, 15 Feb 2009 12:17:00 -0500, Michael Pobega wrote:
> Have you tried running alsaconf as root? Usually when there are upgrades
> to alsa you have to do it, things tend to change pretty often in the
> ALSA setup.
Yes. 1st thing that I did.
thanks all the same.
--
Tong (remove underscore(s) to reply)
http://xpt.sourceforge.net/techdocs/
http://xpt.sourceforge.net/tools/
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
02-15-2009, 05:18 PM
T o n g
ALSA devices: NOT ENABLED IN CONFIG
On Sun, 15 Feb 2009 16:25:19 +0000, T o n g wrote:
> My "amixer: Mixer attach default error" problem was solved by
>
> % aptitude install libesd-alsa0
>
> (Ref:
> http://www.linuxquestions.org/questions/debian-26/no-sound-debian-lenny-amd64-gigabyte-ga-
> ma78gm-s2h-amd-780g-677646/)
Hmm, not any more.
While trying to OP problem myself, I tried the remove and re-install approach:
% alsaconf
Loading driver...
Setting default volumes...
amixer: Mixer attach default error: No such file or directory
Saving the mixer setup used for this in /var/lib/alsa/asound.state.
I have this "amixer: Mixer attach default error" again.
Please help.
thanks
--
Tong (remove underscore(s) to reply)
http://xpt.sourceforge.net/techdocs/
http://xpt.sourceforge.net/tools/
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
02-15-2009, 06:33 PM
Florian Kulzer
ALSA devices: NOT ENABLED IN CONFIG
On Sun, Feb 15, 2009 at 16:25:19 +0000, T o n g wrote:
> [warning, long post]
>
> Hi,
>
> My recent upgrade caused my sound card not working any more. Checking back
> at my packages version log, the only related upgrade is that
> alsa-base_1.0.17.dfsg-2 is upgraded to alsa-base_1.0.17.dfsg-4.
> The rest are still the same:
>
> alsa-oss_1.0.15-1
> alsa-utils_1.0.16-2
> alsamixergui_0.9.0rc2-1-9
>
> Yet, now I've got:
>
> $ ls /dev/dsp
> ls: cannot access /dev/dsp: No such file or directory
>
> $ cat /dev/sndstat
> Sound Driver:3.8.1a-980706 (ALSA v1.0.16 emulation code)
> Kernel: Linux helios.selfip.org 2.6.26-grml #1 SMP PREEMPT Wed Nov 26 21:41:43 UTC 2008 i686
> Config options: 0
>
> Installed drivers:
> Type 10: ALSA emulation
>
> Card config:
> VIA 8237 with AD1980 at 0xc800, irq 22
>
> Audio devices: NOT ENABLED IN CONFIG
>
> Synth devices: NOT ENABLED IN CONFIG
>
> Midi devices: NOT ENABLED IN CONFIG
>
> Timers:
> 31: system timer
>
> Mixers: NOT ENABLED IN CONFIG
[ snip: You checked all the usual suspects already; I did not notice
anything that gave me a clue what is going on. ]
> But I can't go any further via googling. E.g., among many other tryings,
> following Florian Kulzer's advice on merely unloading and reloading the
> modules didn't work for me:
>
> % modprobe -r snd_via82xx snd_pcm snd_seq
> FATAL: Module snd_pcm is in use.
In that case you have to remove the module that uses snd_pcm (probably
snd_pcm_oss) before you can remove snd_pcm.
> % modprobe snd_via82xx
> % modprobe snd_seq
There is some problem with the driver, therefore it is important to have
more details about what is going on when the modules are loaded. Try to
unload all snd* modules so that "lsmod | grep snd" returns no output.
(If this is not possible then you should find out which modules are the
blockers to help isolate the problem.)
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
02-16-2009, 04:00 AM
T o n g
ALSA devices: NOT ENABLED IN CONFIG
On Sun, 15 Feb 2009 20:33:05 +0100, Florian Kulzer wrote:
> [ snip: You checked all the usual suspects already; I did not notice
> anything that gave me a clue what is going on. ]
Thank you Florian for your reply.
>> But I can't go any further via googling. E.g., among many other
>> tryings, following Florian Kulzer's advice on merely unloading and
>> reloading the modules didn't work for me:
>>
>> % modprobe -r snd_via82xx snd_pcm snd_seq FATAL: Module snd_pcm is in
>> use.
>
> In that case you have to remove the module that uses snd_pcm (probably
> snd_pcm_oss) before you can remove snd_pcm.
>
>> % modprobe snd_via82xx
>> % modprobe snd_seq
>
> There is some problem with the driver, therefore it is important to have
> more details about what is going on when the modules are loaded. Try to
> unload all snd* modules so that "lsmod | grep snd" returns no output.
> (If this is not possible then you should find out which modules are the
> blockers to help isolate the problem.)
>
> If you can unload all sound modules, run
>
> modprobe -v snd_via82xx snd_pcm_oss snd_seq
>
> as root and post the output here.
# modprobe -v snd_via82xx snd_pcm snd_seq
FATAL: Error inserting snd_via82xx (/lib/modules/2.6.26-grml/kernel/sound/pci/snd-via82xx.ko): Unknown symbol in module, or unknown parameter (see dmesg)
Maybe the grml kernel is for some reason not compatible with Debian's
ALSA setup. (Grml is based on Debian, but I don't know which changes its
maintainers introduce to their kernels. They are focused on system
rescue so maybe they don't bother too much about ALSA.) Do you have the
same problem with a stock Debian kernel?
> # modprobe -v snd_pcm
>
> # modprobe -v snd_seq
That means the modules were already loaded together with snd_via82xx. I
do see such additional modules listed when I "modprobe -v" my main sound
module; maybe the "--quiet" in the command above suppresses this output
for you.
> $ cat /dev/sndstat
> Sound Driver:3.8.1a-980706 (ALSA v1.0.16 emulation code)
> Kernel: Linux helios.selfip.org 2.6.26-grml #1 SMP PREEMPT Wed Nov 26 21:41:43 UTC 2008 i686
> Config options: 0
>
> Installed drivers:
> Type 10: ALSA emulation
>
> Card config:
> VIA 8237 with AD1980 at 0xc800, irq 22
>
> Audio devices: NOT ENABLED IN CONFIG
... and it is still broken. You already tried to purge and reinstall the
ALSA packages, so I am afraid the next step is to recompile your kernel
with CONFIG_SND_DEBUG enabled and hope that something useful shows up in
the syslog.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
02-16-2009, 03:04 PM
T o n g
ALSA devices: NOT ENABLED IN CONFIG
On Mon, 16 Feb 2009 10:42:51 +0100, Florian Kulzer wrote:
> Maybe the grml kernel is for some reason not compatible with Debian's
> ALSA setup. . .
Thanks a lot for the analysis Florian. Basing it, I diverted the discussion to grml .
Thanks again.
--
Tong (remove underscore(s) to reply)
http://xpt.sourceforge.net/techdocs/
http://xpt.sourceforge.net/tools/
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
02-17-2009, 01:51 PM
Mark Neidorff
ALSA devices: NOT ENABLED IN CONFIG
On Sunday 15 February 2009 11:25 am, T o n g wrote:
>
> Hi,
>
> My recent upgrade caused my sound card not working any more. Checking back
> at my packages version log, the only related upgrade is that
> alsa-base_1.0.17.dfsg-2 is upgraded to alsa-base_1.0.17.dfsg-4.
> The rest are still the same:
>
{snip}
(putting on flame proof suit)
I've run into sound problems like this, and would like to know if I just don't
know where to go for the solution. ALSA is very good at what it does. But,
unlike servers that I have to tweak and monitor on a regular basis, ALSA is
in (or "should be in" ) the category of set it up, and it works and its done.
My recent experience was:
The sound chip on my motherboard was not supported in ALSA. Reasonable, I
found an old well supported sound card and put that in. Now that the well
supported sound card is installed, and the drivers are installed, etc.,
getting the card to the right levels, and "connecting" the software so that
sound coming into the sound card could be listened to or recorded was a
matter or trial and error, and error and error and error. The best advice I
got was go into alsamixer and try various settings until something works for
you. Such things as "Line" "Line in" "Line 1" "Line 2" "ICE958 In Monitor",
etc. etc. etc. aren't helpful. Sure, if I do this every day (or week) I'd
know what to do, but when it is once in a great while???
I'd love to see a graphical front end to the sound system where there is a
CLEARLY labeled representation of the physical card's inputs and outputs that
can be click/dragged to appropriately CEARLY labeled software inputs, to
CLEARLY labeled outputs.
Is there a solution to configuring sound? If not, where is the proper place
to ask for one?
Thanks,
Mark
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
03-03-2009, 01:10 PM
Arthur Marsh
ALSA devices: NOT ENABLED IN CONFIG
Mark Neidorff wrote, on 2009-02-18 01:21:
Is there a solution to configuring sound? If not, where is the proper place
to ask for one?
There is an alsa-user mailing list
http://www.alsa-project.org/main/index.php/Mailing-lists
I've found part of the fun being that there isn't a clear mapping
between what
cat /proc/asound/cards
shows and what modules are needed. The pcspkr module also added to the
confusion.
I'd like a graphical front end a bit like alsaconf but geared towards
handling multiple sound cards and letting the user pick which card
should be default, even to the point of allowing a just-plugged in usb
sound device (which may even be a web-cam's microphone) to become the
default device while it's plugged in, and reverting to an on-board sound
card when disconnected (if that's what the user wants).
Arthur.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
ALSA devices: NOT ENABLED IN CONFIG
