Dell 1420n audio not supported under Gutsy

In System Preferences -> Keyboard Shortcuts could you choose some "Action" and press each of the three non-functioning buttons and see what shortcut they register as if any? Thanks!

In the Keyboard Shortcuts application, I tried to set new values for the volume buttons. However, the original values were the same as when I pressed on the volume keys. So, I tested again and I got the same behavior.

I then tried setting the volume using the speaker icon in the menu bar and I got the error message: The volume control did not find any elements and/or devices to control. This means either that you don't have the right GStreamer plugins installed, or that you don't have a sound card configured.

So, it seems that the audio controller on the Dell Inspiron 1420N is not supported out of the box.

In which case could you please add the output requested in the Reporting Sound Bugs section of https://help.ubuntu.com/community/DebuggingSoundProblems as separate attachments? Thanks in advance.

SND_HDA_INTEL was not enabled in the i386 config. The Sigmatel Dell 1420 patch from feisty was also missing.

SND_HDA_INTEL was not enabled in the kernel because its now supported in Gutsy l-u-m. I've added quirk support to l-u-m for the Dell 1420 and re-disabled SND_HDA_INTEL in the kernel.

Tim,

Pardon my ignorance, what is Gutsy l-u-m?

Its linux-ubuntu-modules. This git repo contains packages that we wish to maintain outside the main kernel tree,

rtg@zinc:/srv/kernel.ubuntu.com/git/ubuntu/ubuntu-gutsy-lum.git

After the dist-upgrade to Gusty from Feisty I have no sound anymore with a Dell Latitude D610 (Intel).
The volume icons work fine I can adjust volume mute it etc... but I cant hear any sound

Hi,

The latest switch and apparently an upgrade of snd-hda-intel from linux-image to linux-ubuntu-modules broke sound of my Asus M2NPV-VM. The mixer only shows two channels (master and PCM) and no sound can be heard.

This is amixer output from linux-image-2.6.22-9-generic.

This is sndstat output from linux-image-2.6.22-9-generic. Looks like the problem is that the chip (Analog Devices AD1986A) is detected as "generic" by the newer driver.

Looks like commit b827ca9a87aac6affcc84563211fe27598529e0f could be the culprit. Defining CONFIG_SND_HDA_GENERIC seems to disable some stuff in hda_codec.c, such as finding the proper codec.

I'm running Gusty on a DELL Latitude D620 notebook with a docking station. After the latest update (to 2.6.22-10-generic), I can only control the built-in speaker of the notebook - a speaker connected to the docking stations stays mute. Before the updated, I couldn't control the volume of a speaker connected via the docking station, but at least it got the audio signal.

Additionally, I could choose whether the input-source is the built-in mic, an external mic or if it should act like an input line. This is gone now too.

N.B.: In windows, I can control the volume of a speaker connected to the docking station as well - I never could do this in linux, but I could live with it this way.

The Dell D620 is a different animal then the 1420. Please start another bug report specifically for that platform.

You are right, Tim, I've opened a new bug dedicated to the D620.

This should probably get fixed soon and pushed out in an update. The 2.6.22-9 kernel left Inspiron 1420 users without touchpad scrolling and without a CD drive. The 2.6.22-10 kernel fixed these two problems but now audio is broken. It would be great to have an actually working 1420 =)

BTW, my amixer output on the 1420 pretty much matches what smo has posted.

With 2.6.22-10, the same symptoms are present on the Compaq nc6320

No sound ouput, and the "mute" ligjht remains lit. Pressing the mute button brings up the appropriate mute / unmute graphic on screen.

alsamixer does not show a master channel.

Seems as if the hardware dependant codec drivers aren't getting compiled in. After adding to the Makefile:

EXTRA_CFLAGS := -DCONFIG_SND_HDA_GENERIC \
                -DCONFIG_SND_HDA_CODEC_REALTEK \
                -DCONFIG_SND_HDA_CODEC_CMEDIA \
                -DCONFIG_SND_HDA_CODEC_ANALOG \
                -DCONFIG_SND_HDA_CODEC_SIGMATEL \
                -DCONFIG_SND_HDA_CODEC_SI3054 \
                -DCONFIG_SND_HDA_CODEC_ATIHDMI \
                -DCONFIG_SND_HDA_CODEC_CONEXANT \
                -DCONFIG_SND_HDA_CODEC_VIA

My box works again. The chip for my HP nc6320 detects as a AD1981, thus requires the CONFIG_SND_HDA_CODEC_ANALOG option.

In the kernel sources, the unused HDA driver has in hda_patch.h

static const struct hda_codec_preset *hda_preset_tables[] = {
 snd_hda_preset_realtek,
 snd_hda_preset_cmedia,
 snd_hda_preset_analog,
 snd_hda_preset_sigmatel,
 snd_hda_preset_si3054,
 snd_hda_preset_atihdmi,
 snd_hda_preset_conexant,
 snd_hda_preset_via,
 NULL
};

in the l-u-m version in hda_patch.h:

static const struct hda_codec_preset *hda_preset_tables[] = {
#ifdef CONFIG_SND_HDA_CODEC_REALTEK
        snd_hda_preset_realtek,
#endif
#ifdef CONFIG_SND_HDA_CODEC_CMEDIA
        snd_hda_preset_cmedia,
#endif
#ifdef CONFIG_SND_HDA_CODEC_ANALOG
        snd_hda_preset_analog,
#endif
#ifdef CONFIG_SND_HDA_CODEC_SIGMATEL
        snd_hda_preset_sigmatel,
#endif
#ifdef CONFIG_SND_HDA_CODEC_SI3054
        snd_hda_preset_si3054,
#endif
#ifdef CONFIG_SND_HDA_CODEC_ATIHDMI
        snd_hda_preset_atihdmi,
#endif
#ifdef CONFIG_SND_HDA_CODEC_CONEXANT
        snd_hda_preset_conexant,
#endif
#ifdef CONFIG_SND_HDA_CODEC_VIA
        snd_hda_preset_via,
#endif
        NULL
};

Presumably we want to build all of these. CONFIG_SND_HDA_GENERIC isn't used in the linux kernel version either, just l-u-m.

Regards,

Peter Clifton

2 steps forward, one step back. Kyle says he is going to drop SND_HDA_INTEL from l-u-m, restore functionality in the kernel, then cherry-pick bug fixes from ALSA. Since this platform is one of the Ubuntu certified Dell machines, I'll make certain it works before Gutsy is released.

I think you might be over-reacting, just because l-u-m has the wrong compile flags doesn't mean you shouldn't deviate from upstream and provide an up-to-date driver. I have a gut feeling that with the latest driver out of ALSA repo, things could work out just fine (unless the ALSA repo is in a wild flux) for owners of newer hardware. Maybe a proper testing team could work this out?

Same on a dell 640m ... sound work only on build-in speakers ...

In Gusty tribe 3 the sound worked fine (except internal microphone). Now, with tribe 5 (after new install) doesn't work, no sound.

Laptop ASUS F3F:
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)

The cause of the problem is known, and the Ubuntu guys will release a fix soon enough.

This will probably either be rebuilding linux-ubuntu-modules with some new compile flags, or with a complete kernel rebuild and some patches (going back to the version of the sound driver in the main kernel + a few backported packages).

In case it helps, here's a debdiff applying Peter Clifton's EXTRA_CFLAGS fix.

I can confirm that it fixes my sound (Asus F3Jm, HDA Intel with Realtek ALC660 codec/mixer)

Peter's patch fixes audio here too.

Chris Halse Rogers his patch works for me.

The digital output of my Nvidia hda card (on a Asus p5n-e) doesn't work after the update, analog was working fine. After the patch it's all working again :)

Same here with AMD Sempron +3000 Gutsy Tribe 5 linux-ubunto-modules-2.6.22-10.23
00:0e.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 05)
        Subsystem: Creative Labs CT4760 SBLive!
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 64 (500ns min, 5000ns max)
        Interrupt: pin A routed to IRQ 22
        Region 0: I/O ports at d000 [size=32]
        Capabilities: [dc] Power Management version 1
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:0e.1 Input device controller: Creative Labs SB Live! Game Port (rev 05)
        Subsystem: Creative Labs Gameport Joystick
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 64
        Region 0: I/O ports at d400 [size=8]
        Capabilities: [dc] Power Management version 1
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

The SB Live! card you mention should use the snd-emu10k1 driver, so its not going to be this bug you're seeing - best open another. Did it break with the latest updates too?

NB: The snd-emu10k1 driver is actually provided from linux-image-2.6.22-10-generic, not the linux-ubuntu-modules, so you should file it against that package.

sorry for the newbie question, but how do you compile after you apply the patch ? no config files here !