Announcement

**dibl** · Oct 12, 2010, 02:54 PM

Re: Sound card not recognised in Maverick

No guarantees, but there is a long list of options for the snd_hda_intel driver here.

**doctordruidphd** · Oct 14, 2010, 08:31 AM

Re: Sound card not recognised in Maverick

Try:

arecord -l

see if your card is listed there.

If it is, then

pavucontrol > configuration

see if it is listed there, and if it is turned on.

**udippel** · Oct 16, 2010, 09:33 AM

Re: Sound card not recognised in Maverick

Don't want to hijack yours; though neither start another thread.
Here, the card is 'recognized', but not by pavucontrol:

$ arecord -l
**** List of CAPTURE Hardware Devices ****
card 0: NVidia [HDA NVidia], device 0: ALC888 Analog [ALC888 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 1: ALC888 Digital [ALC888 Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 2: ALC888 Analog [ALC888 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

So I can set it to
Analog Surround 5.1 Output + Analog Stereo Input
only, because the ALC888 is not offered, and actually set the volume(s) for the 5.1 output channels. Alas, all inputs are always on, with a high volume. Whatever I set, even mute, the signals will be there, audible in the speakers.

Any suggestion?

Uwe

**mweishaa** · Oct 16, 2010, 12:06 PM

Re: Sound card not recognised in Maverick

I am in a similar situation... except after my upgrade to 10.10, my sound was all working fine.
I wasn't getting sound in Unreal Tournament, I think because Pulse is now the deafult in Meerkat. So I was installing some alsa compatability packages, now my sound card isn't being recognized.

I get "Dummy Output" in pavucontrol. Uninstalled and reinstalled Pulse.. same scenario.

lspci -v ...
00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 01)
Subsystem: Micro-Star International Co., Ltd. Device 7529
Flags: bus master, fast devsel, latency 0, IRQ 10
Memory at fea78000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel modules: snd-hda-intel

but arecord -l gives me no results. Somehow it seems my soundcard got uninstalled AFTER it was up and working in Meerkat.

**doctordruidphd** · Oct 16, 2010, 01:21 PM

Re: Sound card not recognised in Maverick

@udippel:

I'm not sure what is messed up, there are several things to check.

padevchooser > Manager > Devices
Your card should be listed under Sources, along with a description.
Now padevchooser > Volume Control > Input Devices
Make sure the bottom box says "All input devices"
Are you saying the mute button and volume control settings do not silence your input?

Have you modified your /etc/asound.conf file in some way?

You might also try installing and running alsamixer. That might give you access to the input volume control directly.

@mweishaa

Capabilities: <access denied>

is probably why it's not working.

pavucontrol > configuration

Is your card listed there?
Also look at Systemsettings > Multimedia > phonon
and see if there is anything listed there at all.

I have noticed several threads on this board about problems with intel sound cards. You might do a search, and see if there is some special parameter that the snd-hda-intel driver needs.

**mweishaa** · Oct 16, 2010, 01:31 PM

Re: Sound card not recognised in Maverick

pavucontrol > config - no sound cards available

System > Multimedia > Phonon

Popup:
KDE detected that one or more internal sound devices were removed.
Do you want KDE to permanently forget about these devices?
This is the list of devices KDE thinks can be removed:
Capture: HDA Intel (ALC888 Analog)
Capture: HDA Intel (ALC888 Analog) #2
Output: HDA Intel (ALC888 Analog)
Output: HDA Intel (ALC888 Digital)
Output: HDA Intel, ALC888 Digital (IEC958 (S/PDIF) Digital Audio Output)

I choose NO

Then listed under Phonon devices is Dummy Output (active) and Internal Audio Analog Stereo (inactive, grayed). This is what was active and working prior to my reboot. Again, it was working fine for everything after the upgrade. After my first reboot after that (adding/removing alsa packages trying to get sound to work with unreal tournament), it's gone.

EDIT UPDATE: OK, well... I was right.. it was gone. I just added snd-hda-intel back into /etc/modules.conf and it's back. Not sure why it was removed. I also noticed that I was running 2.6.35-22-server instead of 2.6.35-22-generic. Uninstalled the server kernel... not sure why that was installed, I may have done that by accident when installing the backport modules trying to get alsa working for ut. (not liking the new look to kpackagekit, I find it unclear on what's being installed and what isn't when I select packages)

**doctordruidphd** · Oct 16, 2010, 01:55 PM

Re: Sound card not recognised in Maverick

I also noticed that I was running 2.6.35-22-server

Yes, that may well have removed your sound driver, since a server would not normally run one.
You might want to try the muon package manager, or else stick with synaptic. Might be easier to tell what they are doing.

**udippel** · Oct 16, 2010, 07:04 PM

Re: Sound card not recognised in Maverick

Originally posted by doctordruidphd

@udippel:

padevchooser > Manager > Devices
Your card should be listed under Sources, along with a description.
Now padevchooser > Volume Control > Input Devices
Make sure the bottom box says "All input devices"
Are you saying the mute button and volume control settings do not silence your input?

Have you modified your /etc/asound.conf file in some way?

You might also try installing and running alsamixer. That might give you access to the input volume control directly.

Not really. I had read about the padevchooser elsewhere, installed it, but it doesn't start. It hangs at the terminal forever and ever, until I Ctrl-C it.
Yes, 'all input devices', and mute and volume control don't silence the inputs.
No, I could not have modified the file manually. Here it is:
$ cat /etc/asound.conf
cat: /etc/asound.conf: No such file or directory

Uwe

**doctordruidphd** · Oct 16, 2010, 07:31 PM

Re: Sound card not recognised in Maverick

cat: /etc/asound.conf: No such file or directory

This is not good. I suspect that something during the upgrade process failed You may wind up removing and reinstalling your alsa and pulse packages.

padevchooser should not be hanging. If it is, it means something is wrong with pulse or alsa.

Check to see if you have the .asoundrc and .asoundconf.asoundrc files in your home directory. And check for /etc/modprobe.d/sound If those files are missing, then something has gone wrong with alsa and pulse installation.

If you do have those files, then you can create the /etc/asound.conf file using the following text:

Code:

pcm.pulse {
  type pulse
}
ctl.pulse {
  type pulse
}
pcm.!default {
  type pulse
}
ctl.!default {
  type pulse
}

**udippel** · Oct 16, 2010, 08:01 PM

Re: Sound card not recognised in Maverick

None of those files are available. Though the upgrade went smoothly, not a single error, or so.
In the old days, there used to be a 'check' option in apt-get/dpkg for all installed packages; though I can't seem to find it now.
Maybe this helps to identify what's wrong here?:

$ dpkg -l | grep alsa
ii alsa-base 1.0.23+dfsg-1ubuntu4 ALSA driver configuration files
ii alsa-oss 1.0.17-4 ALSA wrapper for OSS applications
ii alsa-utils 1.0.23-2ubuntu3 Utilities for configuring and using ALSA
ii bluez-alsa 4.69-0ubuntu2 Bluetooth audio support
ii gstreamer0.10-alsa 0.10.30-2 GStreamer plugin for ALSA
ii libsdl1.2debian-alsa 1.2.14-6ubuntu3 Simple DirectMedia Layer (with X11 and ALSA options)
ii libsox-fmt-alsa 14.3.1-1build1 SoX alsa format I/O library

$ dpkg -l | grep pulse
ii gstreamer0.10-pulseaudio 0.10.25-4ubuntu2 GStreamer plugin for PulseAudio
ii libpulse-browse0 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21 PulseAudio client libraries (zeroconf support)
ii libpulse-mainloop-glib0 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21 PulseAudio client libraries (glib support)
ii libpulse0 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21 PulseAudio client libraries
ii pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21 PulseAudio sound server
ii pulseaudio-esound-compat 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21 PulseAudio ESD compatibility layer
ii pulseaudio-module-bluetooth 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21 Bluetooth module for PulseAudio sound server
ii pulseaudio-module-gconf 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21 GConf module for PulseAudio sound server
ii pulseaudio-module-x11 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21 X11 module for PulseAudio sound server
ii pulseaudio-module-zeroconf 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21 Zeroconf module for PulseAudio sound server
ii pulseaudio-utils 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21 Command line tools for the PulseAudio sound server

Thanks for your help,

Uwe

**doctordruidphd** · Oct 16, 2010, 08:22 PM

Re: Sound card not recognised in Maverick

If those files aren't there, then alsa did not install properly.

Just a thought -- try sudo dpkg --confgure -a

If that doesn't do anything, then try sudo dpkg-reconfigure alsa-base and sudo dpkg-reconfigure alsa-utils and sudo dpkg-reconfigure gstreamer0.10-alsa

Then look for those files again.
If they are still not there, then sudo apt-get install --reinstall the alsa files.

If this works, then you may have to do the same with the pulseaudio files, after alsa is installed.

**udippel** · Oct 16, 2010, 08:56 PM

Re: Sound card not recognised in Maverick

Héhé, you might be surprised:?
All sudo dpkg --configure/reconfigure return immediately with the prompt. So neither do anything.
Then I dug through the complete list of the alsa/pulse-files and made them --reinstall. Went through, no error messages whatsoever.
Then I rebooted.

Neither file is here.

**doctordruidphd** · Oct 16, 2010, 09:41 PM

Re: Sound card not recognised in Maverick

Sorry to say, at this point I have no clue.

You might try searching the ubuntu forum, or maybe someone else has an idea.

As I understand it, padevchooser hangs, and you are unable to adjust input levels.
So you might try filing a bug report against pulseaudio on launchpad, and see if anyone there can come up with something. This is really strange.

**udippel** · Oct 17, 2010, 12:03 AM

Re: Sound card not recognised in Maverick

Too strange, yes.

And it gets worse. When I boot to recovery console, and then go to my own terminal-based logon, what I get:
...
... 2.6.35-22 ....
Ubuntu 10.10
Welcome to Ubuntu!
...
Ubuntu 10.04.1 LTS
Welcome to Ubuntu!
...
978 packages can be updated
0 updates are security updates.

And then, when I start the WiFi and make sudo apt-get update && udo apt-get upgrade, I get nothing to be upgraded.
Meaning, I get both versions, and one has stored some place that 978 packages could be updated. All my /etc/apt/sources.list are maverick:
$ sudo apt-get update | grep -v averick
Reading package lists...
$
So all are Maverick. Where does the prompt come from, and where the 978 packages to be upgradeable??

Announcement

Sound card not recognised in Maverick

Sound card not recognised in Maverick

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment