[gutsy] no sound on Dell Latitude D630/D830/Precision M4300/Vostro 1500/1700/Apple Aluminium iMac/Acer TM6292 pci id 8086:284b

[stivani]

I have no sound in Gutsy x86_64. In Feisty, sound worked fine.

My laptop is a Dell Latitude D830.

Found in dmesg log file:

[ 23.252496] hda_intel: azx_get_response timeout, switching to polling mode...
[ 23.550621] ipw3945: Detected geography ABG (13 802.11bg channels, 23 802.11a channels)
[ 23.775888] hda_intel: azx_get_response timeout, switching to single_cmd mode...
[ 27.251189] hda_codec: No auto-config is available, default to model=ref
[ 30.733510] hda-intel: no codecs initialized

See
* https://wiki.ubuntu.com/Gutsy_Intel_HD_Audio_Controller

* https://wiki.ubuntu.com/LaptopTestingTeam/DellLatitudeD830#head-40a4e1f238b3be666f63c6efefdfd883caf0bf4d for a (temporary, must be repeated whenever the kernel package is updated) fix.

[Gabriel Ambuehl (gabriel-ambuehl)]

I confirm to have the same issue on my Latitude D830 in x86-32. Can't comment on Feisty as I haven't used it on it so far (and don't really plan to, either).

[Gabriel Ambuehl (gabriel-ambuehl)]

This is quite possibly the same bug as #122560 and even more likely, because the hardware is nearly identical #124590.

#126249 could be related, too.

[Gabriel Ambuehl (gabriel-ambuehl)]

I now tested Feisty on my D830, sound works on Feisty, so this clearly is a
regression.

[Gabriel Ambuehl (gabriel-ambuehl)]

Sound on the D830 be fixed by using a newer version of ALSA:
make sure you have all requirements to build the kernel installed (i.e.
sources, corresponding compilers etc)
get one of the packages from (for me, 18 Aug works)
ftp://ftp.suse.com/pub/projects/alsa/snapshot/driver/
untar it
in the newly create folder, run
./configure --with-cards=hda-intel
make
sudo make install

then reboot

[Martin Gros (m-gros)]

I confirm that sound does not work with Gutsy Tribe-5 amd64 on my Dell D830

[Martin Gros (m-gros)]

lspci -vv:

00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)
        Subsystem: Dell Unknown device 01fe
        Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Interrupt: pin A routed to IRQ 21
        Region 0: Memory at fe9fc000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: [50] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
                Address: 0000000000000000 Data: 0000
        Capabilities: [70] Express Unknown type IRQ 0
                Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
                Device: Latency L0s unlimited, L1 unlimited
                Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
                Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
                Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
                Link: Supported Speed unknown, Width x0, ASPM unknown, Port 0
                Link: Latency L0s <64ns, L1 <1us
                Link: ASPM Disabled CommClk- ExtSynch-
                Link: Speed unknown, Width x0

[Achim Bohnet (allee)]

Ditto: no sound on D830 with Kubuntu Gutsy Tribe 5 i386.

There was one little change over this week end: Before I saw a PCM slider in kmixer.
Now after dist-upgrading the pkgs updated between Thursday and Monday night,
kmix shows a 'device not found'. icon (after reboot).

[dbrobert (dr-edgeoftheearth)]

Sound was fixed with linux-ubuntu-modules-2.6.22-10.23 but broken again when they reverted back to the stock snd-hda-intel code in linux-ubuntu-modules-2.6.22-10.24. On a semi-related note, that version also fixed the issue of the DVD-RW drive not being recognized. Alas that too was re-broken with linux-ubuntu-modules-2.6.22-10.24.

[kubasa (beryk)]

add gabriel-ambuehl
THX for your information :) on my D630 working sound very well!!! I' m testing kubuntu 2.6.22-10-generic #1
Intel Corporation 82801H with Sound Driver: 3.8.1a-98.07.06 (ALSA v1.0.15rc1 emulation code)
Many thanks!
erix

[Achim Bohnet (allee)]

Uhm, a fix is not yet declared a release goal for Gusty. A bit frightening as this intel
chips (AFAIU) are pretty common.

Any comments snd-hda-intel was removed?

[Gabriel Ambuehl (gabriel-ambuehl)]

This issue persists on 2.6.22-11

[Olivier Cortès (olive)]

Hi, the problem is the same on Dell Precision M4300.
No audio is detected with Gutsy 32bits on 2.6.22-11-generic (can't remember how it was with Gutsy 64bits, i don't use it yet), or sometimes it is detected but no sound can be heard and only ONE "master" canal exists (this is not easily reproducible, most of the time no audio card is detected).
Downloading a recent alsa source, replacing alsa-source.tar.bz2 (from 'alsa-source' package) in /usr/src and recompiling "alsa" modules with "module-assistant" makes soundcard work great at next boot, and reliably (tested with 2.6.22-10-generic, 2.6.22-11-generic and 2.6.22-11-rt).

[BotLobsta (kjenks-deactivatedaccount)]

I have the same problem with 2.6.22-11 on a D830. Under the latest version of 2.6.22-10 I could get everything to work if in installed the kernel version of the snd-hda-intel module instead of the one from the linux-ubuntu-module package. However, in 2.6.22-11 the kernel version does not exist and so I can not get any sound to work in 2.6.22-11.

[Gabriel Ambuehl (gabriel-ambuehl)]

Todays kernel, namely
Linux host 2.6.22-11-generic #1 SMP Mon Sep 17 03:45:58 GMT 2007 i686
GNU/Linux
does not fix it either.

[craigeherring (craigeherring)]

Confirmed on another Dell D830.

Suse patch works though.

[Emanuel Goscinski (emu--deactivatedaccount)]

For me even the newest Alsa-Drivers doesn't solved the problem on my D630.

I compiled the newest alsa modules, but everyhing is like before. There is still no sound device...

[Gabriel Ambuehl (gabriel-ambuehl)]

Emanuel: could you post your dmesg?

[Emanuel Goscinski (emu--deactivatedaccount)]

Yes I Can:
Full output of dmesg ist attached.

Output of "dmesg | grep snd":
[ 16.052000] snd_hda_intel: disagrees about version of symbol snd_ctl_add
[ 16.052000] snd_hda_intel: Unknown symbol snd_ctl_add
[ 16.052000] snd_hda_intel: disagrees about version of symbol snd_pcm_new
[ 16.052000] snd_hda_intel: Unknown symbol snd_pcm_new
[ 16.052000] snd_hda_intel: disagrees about version of symbol snd_pcm_limit_hw_rates
[ 16.052000] snd_hda_intel: Unknown symbol snd_pcm_limit_hw_rates
[ 16.052000] snd_hda_intel: disagrees about version of symbol snd_card_register
[ 16.052000] snd_hda_intel: Unknown symbol snd_card_register
[ 16.052000] snd_hda_intel: disagrees about version of symbol snd_card_free
[ 16.052000] snd_hda_intel: Unknown symbol snd_card_free
[ 16.052000] snd_hda_intel: disagrees about version of symbol snd_pcm_lib_preallocate_pages_for_all
[ 16.052000] snd_hda_intel: Unknown symbol snd_pcm_lib_preallocate_pages_for_all
[ 16.052000] snd_hda_intel: disagrees about version of symbol snd_card_proc_new
[ 16.052000] snd_hda_intel: Unknown symbol snd_card_proc_new
[ 16.052000] snd_hda_intel: disagrees about version of symbol snd_ctl_find_id
[ 16.052000] snd_hda_intel: Unknown symbol snd_ctl_find_id
[ 16.052000] snd_hda_intel: disagrees about version of symbol snd_ctl_new1
[ 16.052000] snd_hda_intel: Unknown symbol snd_ctl_new1
[ 16.052000] snd_hda_intel: disagrees about version of symbol snd_component_add
[ 16.052000] snd_hda_intel: Unknown symbol snd_component_add
[ 16.052000] snd_hda_intel: disagrees about version of symbol snd_card_new
[ 16.052000] snd_hda_intel: Unknown symbol snd_card_new
[ 16.052000] snd_hda_intel: disagrees about version of symbol snd_pcm_lib_malloc_pages
[ 16.052000] snd_hda_intel: Unknown symbol snd_pcm_lib_malloc_pages
[ 16.052000] snd_hda_intel: disagrees about version of symbol snd_pcm_lib_ioctl
[ 16.052000] snd_hda_intel: Unknown symbol snd_pcm_lib_ioctl
[ 16.052000] snd_hda_intel: disagrees about version of symbol snd_pcm_lib_free_pages
[ 16.052000] snd_hda_intel: Unknown symbol snd_pcm_lib_free_pages
[ 16.052000] snd_hda_intel: Unknown symbol snd_ctl_elem_read
[ 16.052000] snd_hda_intel: Unknown symbol snd_ctl_elem_write
[ 16.052000] snd_hda_intel: disagrees about version of symbol snd_pcm_set_ops
[ 16.052000] snd_hda_intel: Unknown symbol snd_pcm_set_ops
[ 16.052000] snd_hda_intel: disagrees about version of symbol snd_pcm_hw_constraint_list
[ 16.052000] snd_hda_intel: Unknown symbol snd_pcm_hw_constraint_list
[ 16.052000] snd_hda_intel: disagrees about version of symbol snd_device_new
[ 16.052000] snd_hda_intel: Unknown symbol snd_device_new
[ 16.052000] snd_hda_intel: disagrees about version of symbol snd_pcm_suspend_all
[ 16.052000] snd_hda_intel: Unknown symbol snd_pcm_suspend_all
[ 16.052000] snd_hda_intel: disagrees about version of symbol snd_card_disconnect
[ 16.052000] snd_hda_intel: Unknown symbol snd_card_disconnect
[ 16.052000] snd_hda_intel: disagrees about version of symbol snd_pcm_hw_constraint_integer
[ 16.052000] snd_hda_intel: Unknown symbol snd_pcm_hw_constraint_integer
[ 16.052000] snd_hda_intel: disagree...

[BotLobsta (kjenks-deactivatedaccount)]

I can confirm that compiling the alsa-source from 9/18 does not work on a D830. Off the top of my head I dont remember if it was exactly the same but the dmesg output I got was very similar. (unknown symbol xxxxxx, disagrees about version of symbol xxxxx)

[Gabriel Ambuehl (gabriel-ambuehl)]

Try alsa-driver-1.0.15rc1, later versions sometimes worked for me but crashed
upon resume from suspend.

[Carl-Christian Salvesen (ccsalvesen)]

Dell Latitude D830, pci id 8086:284b rev 02. Works for me with this module, compiled from alsa-driver-hg20070808.tar.bz2 which i downloaded at ftp://ftp.suse.com/pub/projects/alsa/snapshot/driver/

ccs@lappie:~$ modinfo snd-hda-intel
filename: /lib/modules/2.6.22-11-generic/kernel/sound/pci/hda/snd-hda-intel.ko
description: Intel HDA driver
license: GPL
srcversion: A4432B22E47F568ED531734
alias: pci:v000010DEd00000777sv*sd*bc*sc*i*
alias: pci:v000010DEd00000776sv*sd*bc*sc*i*
alias: pci:v000010DEd00000775sv*sd*bc*sc*i*
alias: pci:v000010DEd00000774sv*sd*bc*sc*i*
alias: pci:v000010DEd000007FDsv*sd*bc*sc*i*
alias: pci:v000010DEd000007FCsv*sd*bc*sc*i*
alias: pci:v000010DEd0000055Dsv*sd*bc*sc*i*
alias: pci:v000010DEd0000055Csv*sd*bc*sc*i*
alias: pci:v000010DEd0000044Bsv*sd*bc*sc*i*
alias: pci:v000010DEd0000044Asv*sd*bc*sc*i*
alias: pci:v000010DEd000003F0sv*sd*bc*sc*i*
alias: pci:v000010DEd000003E4sv*sd*bc*sc*i*
alias: pci:v000010DEd00000371sv*sd*bc*sc*i*
alias: pci:v000010DEd0000026Csv*sd*bc*sc*i*
alias: pci:v000010B9d00005461sv*sd*bc*sc*i*
alias: pci:v00001039d00007502sv*sd*bc*sc*i*
alias: pci:v00001106d00003288sv*sd*bc*sc*i*
alias: pci:v00001002d0000AA00sv*sd*bc*sc*i*
alias: pci:v00001002d0000960Csv*sd*bc*sc*i*
alias: pci:v00001002d00007919sv*sd*bc*sc*i*
alias: pci:v00001002d0000793Bsv*sd*bc*sc*i*
alias: pci:v00001002d00004383sv*sd*bc*sc*i*
alias: pci:v00001002d0000437Bsv*sd*bc*sc*i*
alias: pci:v00008086d0000293Fsv*sd*bc*sc*i*
alias: pci:v00008086d0000293Esv*sd*bc*sc*i*
alias: pci:v00008086d0000284Bsv*sd*bc*sc*i*
alias: pci:v00008086d0000269Asv*sd*bc*sc*i*
alias: pci:v00008086d000027D8sv*sd*bc*sc*i*
alias: pci:v00008086d00002668sv*sd*bc*sc*i*
depends: snd-pcm,snd-page-alloc,snd,snd-hwdep,snd
vermagic: 2.6.22-11-generic SMP mod_unload 586
parm: index:Index value for Intel HD audio interface. (int)
parm: id:ID string for Intel HD audio interface. (charp)
parm: model:Use the given board model. (charp)
parm: position_fix:Fix DMA pointer (0 = auto, 1 = none, 2 = POSBUF, 3 = FIFO size). (int)
parm: probe_mask:Bitmask to probe codecs (default = -1). (int)
parm: single_cmd:Use single command to communicate with codecs (for debugging only). (bool)
parm: enable_msi:Enable Message Signaled Interrupt (MSI) (int)
parm: enable:bool

I added this at the bottom of /etc/modprobe.d/alsa-base:

options snd-hda-intel model=3stack

Please let me know if you need any more info/testing from me, I'll be happy to help.

[Frank Lynch (frank-lynch)]

+1 thanks to Carl-Christian Salvesen's tip above I was also able to get sound on my D830.
I wasn't able to find alsa-driver-hg20070808.tar.bz2 on the site that Carl-Christian pointed to, but I was able to find it (via google) at:
  http://www.gtlib.gatech.edu/pub/suse/projects/alsa/snapshot/driver/

Thank you Carl-Christian, I've finally got sound on my new laptop with Gutsy!

[Nick Rossow (rossow)]

Well after much stuffing around I got my D630 sound working.

I compile alsa version 1.0.15 rc2 with the following command ./configure --with-cards=hda-intel (then make and make install)
and then added the line

options snd-hda-intel model=3stack

to my /etc/modprobe.d/alsa-base

file.

thanks to Gabriel Ambuehl and Carl-Christian Salvesen for the tips.

Nick

[Nick Rossow (rossow)]

although i should point out...

the gnome applet for volume control is still crashing and the volume is very soft. even at full volume... but hey... at least it kinda works :)

[Gabriel Ambuehl (gabriel-ambuehl)]

> I compile alsa version 1.0.15 rc2 with the following command ./configure
> --with-cards=hda-intel (then make and make install) and then added the line
>
> options snd-hda-intel model=3stack
>
> to my /etc/modprobe.d/alsa-base

Can you suspend and resume with rc2? That only worked with rc1 for me (but I'm
on D830)... I didn't need modprobe config myself.

[Carl-Christian Salvesen (ccsalvesen)]

Suspend/resume works fine.

[Emanuel Goscinski (emu--deactivatedaccount)]

>I compile alsa version 1.0.15 rc2 with the following command ./configure --with-cards=hda-intel (then make and make install)
>and then added the line
>
>options snd-hda-intel model=3stack
>
>to my /etc/modprobe.d/alsa-base

I did this too, but it hasn't changed anything.

I also added
snd-hda-intel model=3stack
to my "/etc/modules" but nothing changed.

What do i did wrong?
Compiling ended without any errors...
And I will wonder if my D630 is different, then the one from Nick Rossow

[Gabriel Ambuehl (gabriel-ambuehl)]

On Thursday 20 September 2007 11:43:18 Emanuel Goscinski wrote:
> What do i did wrong?

Says something about version mismatch in your dmesg. Maybe you should try
reinstalling you kernel and recompile 1.0.15rc1?

[Nick Rossow (rossow)]

Emanuel,
did you do the compile with the command ./configure --with-cards=hda-intel

sorry if its a typical help desk support question... but then i was until very recently working on a help desk

Nick

[Tobias Heinemann (theine)]

So is this bug likely to be fixed in Gutsy final? Recompiling ALSA is all fine and dandy, but having sound out of the box would actually be very nice.

Also, does the microphone work for anybody in here? Mine doesn't, but I only tried the drivers that come with the alsa-source package in Gusty. Those do make the speakers work, but not the microphone.

[Gabriel Ambuehl (gabriel-ambuehl)]

On Friday 21 September 2007 02:39:14 Tobias Heinemann wrote:
> Also, does the microphone work for anybody in here? Mine doesn't, but I
> only tried the drivers that come with the alsa-source package in Gusty.
> Those do make the speakers work, but not the microphone.

The internal microphone did work for me. As for external ones, I don't use
those.

[Emanuel Goscinski (emu--deactivatedaccount)]

"Emanuel,
did you do the compile with the command ./configure --with-cards=hda-intel"

Yes I did.

And I installed Gutsy completly new, to get a clean system. Then I updatet and compiled alsa, and added "options snd-hda-intel model=3stack" to alsa-base
but I still have no sound!
dmesg output is the same as I posted before.

the I compiled the daily snapshot of the alsa-driver.
But still nothing has changed....

Any other suggestions?

But I think this should not be solved with compiling alsa. Because my Feisty Kernel works very fine with the compiled 1.0.15rc2 alsa-driver, so it is definitly a regression in the kernel.

[Emanuel Goscinski (emu--deactivatedaccount)]

After reinstalling the kernel and all alsa related packages my dmesg looks like this:

dmesg
[ 0.000000] Linux version 2.6.22-11-generic (buildd@palmer) (gcc version 4.1.3 20070831 (prerelease) (Ubuntu 4.1.2-16ubuntu1)) #1 SMP Mon Sep 17 03:45:58 GMT 2007 (Ubuntu 2.6.22-11.33-generic)
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
[ 0.000000] BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 000000007fe80400 (usable)
[ 0.000000] BIOS-e820: 000000007fe80400 - 0000000080000000 (reserved)
[ 0.000000] BIOS-e820: 00000000f4000000 - 00000000f8000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
[ 0.000000] BIOS-e820: 00000000fed18000 - 00000000fed1c000 (reserved)
[ 0.000000] BIOS-e820: 00000000fed20000 - 00000000fed90000 (reserved)
[ 0.000000] BIOS-e820: 00000000feda0000 - 00000000feda6000 (reserved)
[ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee10000 (reserved)
[ 0.000000] BIOS-e820: 00000000ffe00000 - 0000000100000000 (reserved)
[ 0.000000] 1150MB HIGHMEM available.
[ 0.000000] 896MB LOWMEM available.
[ 0.000000] Entering add_active_range(0, 0, 523904) 0 entries of 256 used
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0 -> 4096
[ 0.000000] Normal 4096 -> 229376
[ 0.000000] HighMem 229376 -> 523904
[ 0.000000] early_node_map[1] active PFN ranges
[ 0.000000] 0: 0 -> 523904
[ 0.000000] On node 0 totalpages: 523904
[ 0.000000] DMA zone: 32 pages used for memmap
[ 0.000000] DMA zone: 0 pages reserved
[ 0.000000] DMA zone: 4064 pages, LIFO batch:0
[ 0.000000] Normal zone: 1760 pages used for memmap
[ 0.000000] Normal zone: 223520 pages, LIFO batch:31
[ 0.000000] HighMem zone: 2301 pages used for memmap
[ 0.000000] HighMem zone: 292227 pages, LIFO batch:31
[ 0.000000] DMI 2.4 present.
[ 0.000000] ACPI: RSDP 000FBB00, 0024 (r2 DELL )
[ 0.000000] ACPI: XSDT 7FE81E00, 0064 (r1 DELL M08 27D70717 ASL 61)
[ 0.000000] ACPI: FACP 7FE81C9C, 00F4 (r4 DELL M08 27D70717 ASL 61)
[ 0.000000] ACPI: DSDT 7FE82400, 613B (r2 INT430 SYSFexxx 1001 INTL 20050624)
[ 0.000000] ACPI: FACS 7FE90C00, 0040
[ 0.000000] ACPI: HPET 7FE81F00, 0038 (r1 DELL M08 1 ASL 61)
[ 0.000000] ACPI: APIC 7FE82000, 0068 (r1 DELL M08 27D70717 ASL 47)
[ 0.000000] ACPI: ASF! 7FE81C00, 007E (r32 DELL M08 27D70717 ASL 61)
[ 0.000000] ACPI: MCFG 7FE81FC0, 003E (r16 DELL M08 27D70717 ASL 61)
[ 0.000000] ACPI: SLIC 7FE8209C, 0176 (r1 DELL M08 27D70717 ASL 61)
[ 0.000000] ACPI: TCPA 7FE82300, 0032 (r1 0 ASL 0)
[ 0.000000] ACPI: SSDT 7FE806EF, 04CC (r1 PmRef CpuPm 3000 INTL 20050624)
[ 0.000000] ACPI: PM-Timer IO Port: 0x1008
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[ 0.000000] Processor #0 6:15 APIC version 20
[ 0.000000] A...

[Gabriel Ambuehl (gabriel-ambuehl)]

Problem persists in
Linux 2.6.22-12-generic #1 SMP Thu Sep 20 18:51:18 GMT 2007 i686

[don hardaway (don-hardaway)]

i have a dell latitude d800 and earlier version of gusty had sound but no sound thru 9/22. Since suse seems to have it working why can't ubuntu engineers just use their patch? As far as I am concerned this should be a top priority.

[Gabriel Ambuehl (gabriel-ambuehl)]

Just for clarification: the packages on the suse server were NOT patched, they
are just daily dumps from alsa's mercurial repository. The main issue is that
alsa fixes and breaks hda_intel repeatedly it seems. And that Ubuntu uses a
version where it is broken.

[don hardaway (don-hardaway)]

OK.

Net-net---when do you think the problem will be resolved.

[Stefano Pedretti (stefano-pedretti)]

I can confirm this on Dell Vostro 1700 notebook.

sudo lspci -vv :

00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)
        Subsystem: Dell Unknown device 0229
        Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Interrupt: pin A routed to IRQ 20
        Region 0: Memory at febfc000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: [50] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
                Address: 0000000000000000 Data: 0000
        Capabilities: [70] Express Unknown type IRQ 0
                Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
                Device: Latency L0s unlimited, L1 unlimited
                Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
                Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
                Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
                Link: Supported Speed unknown, Width x0, ASPM unknown, Port 0
                Link: Latency L0s <64ns, L1 <1us
                Link: ASPM Disabled CommClk- ExtSynch-
                Link: Speed unknown, Width x0

[Gabriel Ambuehl (gabriel-ambuehl)]

With yesterdays linux-image, i.e.
Linux buznote 2.6.22-12-generic #1 SMP Sat Sep 22 18:14:28 GMT 2007 i686 GNU/Linux
it seems like alsa is completely out of sync now:
dmesg | grep hda
[ 17.168000] snd_hda_intel: disagrees about version of symbol snd_ctl_add
[ 17.168000] snd_hda_intel: Unknown symbol snd_ctl_add
[ 17.168000] snd_hda_intel: disagrees about version of symbol snd_card_register
[ 17.168000] snd_hda_intel: Unknown symbol snd_card_register
[ 17.168000] snd_hda_intel: disagrees about version of symbol snd_card_free
[ 17.168000] snd_hda_intel: Unknown symbol snd_card_free
[ 17.168000] snd_hda_intel: disagrees about version of symbol snd_card_proc_new
[ 17.168000] snd_hda_intel: Unknown symbol snd_card_proc_new
[ 17.168000] snd_hda_intel: disagrees about version of symbol snd_ctl_find_id
[ 17.168000] snd_hda_intel: Unknown symbol snd_ctl_find_id
[ 17.168000] snd_hda_intel: Unknown symbol snd_verbose_printk
[ 17.168000] snd_hda_intel: disagrees about version of symbol snd_ctl_new1
[ 17.168000] snd_hda_intel: Unknown symbol snd_ctl_new1
[ 17.168000] snd_hda_intel: disagrees about version of symbol snd_component_add
[ 17.168000] snd_hda_intel: Unknown symbol snd_component_add
[ 17.168000] snd_hda_intel: disagrees about version of symbol snd_card_new
[ 17.168000] snd_hda_intel: Unknown symbol snd_card_new
[ 17.172000] snd_hda_intel: Unknown symbol snd_ctl_boolean_mono_info
[ 17.172000] snd_hda_intel: disagrees about version of symbol snd_hwdep_new
[ 17.172000] snd_hda_intel: Unknown symbol snd_hwdep_new
[ 17.172000] snd_hda_intel: disagrees about version of symbol snd_device_new
[ 17.172000] snd_hda_intel: Unknown symbol snd_device_new
[ 17.172000] snd_hda_intel: disagrees about version of symbol snd_card_disconnect
[ 17.172000] snd_hda_intel: Unknown symbol snd_card_disconnect

ii linux-headers-2.6.22-12-generic 2.6.22-12.38 Linux kernel headers for version 2.6.22 on x
ii linux-image-2.6.22-12-generic 2.6.22-12.38 Linux kernel image for version 2.6.22 on x86
ii linux-restricted-modules-2.6.22-12-generic 2.6.22.4-12.1 Non-free Linux 2.6.22 modules on x86/x86_64
ii linux-ubuntu-modules-2.6.22-12-generic 2.6.22-12.31 Ubuntu supplied Linux modules for version 2.

Looks to me like linux-ubuntu-modules may not have been updated?

[Michael Krufky (mkrufky)]

I also confirm the same behavior on a Latitude D830 under Gutsy:

2.6.22-12-generic

[ 33.004313] hda_intel: azx_get_response timeout, switching to polling mode...
[ 33.075375] hda_intel: azx_get_response timeout, switching to single_cmd mode...
[ 43.812505] hda-intel: no codecs initialized

Sound worked in Feisty, but not Gutsy, just as everybody else above has described.

[JGJones (jgjones)]

Confirmed not working for Dell Vostro 1500 - Dell's are pretty popular and I often get them for Ubuntu because it almost always works out of the box for me and with Dell's pre-packaging Ubuntu's these days, IMHO this bug should be a priority to be fixed before Gutsy is finally released since it won't look good to have Dell's with no sound in Ubuntu.

lsipci -vv

00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)
        Subsystem: Dell Unknown device 0228
        Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Interrupt: pin A routed to IRQ 20
        Region 0: Memory at febfc000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: [50] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
                Address: 0000000000000000 Data: 0000
        Capabilities: [70] Express Unknown type IRQ 0
                Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
                Device: Latency L0s unlimited, L1 unlimited
                Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
                Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
                Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
                Link: Supported Speed unknown, Width x0, ASPM unknown, Port 0
                Link: Latency L0s <64ns, L1 <1us
                Link: ASPM Disabled CommClk- ExtSynch-
                Link: Speed unknown, Width x0

[Martin Gros (m-gros)]

I confirm it does not work on D830.

It did not work with Tribe-5, after 1st update it worked, but since second update it does not.

[don hardaway (don-hardaway)]

Still does not work on my latitude d800 either. Please fix it.

[zeddock (zeddock)]

I have D800 and sound seems to work.
Is there a specific test you would like for me to run? (As I did notice that the Login "drums" do not play as they did in Feisty)
I am on a 32bit CPU, too.... not the 64 as described in summary.

Let me know if I can help.

Gusty Fresh install from CD with format, then updates.
zeddock

[don hardaway (don-hardaway)]

First, do you have pulseaudio or esound installed? I am not sure what to check?

[Jason Davies (jason-davies)]

I can confirm this bug on my Dell Latitude D630.

[zeddock (zeddock)]

Me neither. Don't know how to check. OK putting in commandline stuff and
copy paste here, but don't know exactly what command to get useful
information.

zeddock

On 9/25/07, don hardaway <email address hidden> wrote:
>
> First, do you have pulseaudio or esound installed? I am not sure what to
> check?
>
> --
> [gutsy] no sound on Dell Latitude D630/D830/Precision M4300/Vostro
> 1500/1700 pci id 8086:284b
> https://bugs.launchpad.net/bugs/131133
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Gabriel Ambuehl (gabriel-ambuehl)]

On Tuesday 25 September 2007 22:23:37 zeddock wrote:
> I have D800 and sound seems to work.
> Is there a specific test you would like for me to run? (As I did notice
> that the Login "drums" do not play as they did in Feisty) I am on a 32bit
> CPU, too.... not the 64 as described in summary.
>
I don't think the D800 has even remotely the same sound hardware as the newest
Dells.

[Achim Bohnet (allee)]

to check what audio chipset you have run:

     lspci | grep -i audio

then check the nn:mm.x number at the start of the line. Then

    lspci -n | grep nn.mm.x

The third number is the PCI (chipset) id.

E.g. for the chip set of this bug report: 8086:284b. Like

00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)

and

00:1b.0 0403: 8086:284b (rev 02)

Achim

[don hardaway (don-hardaway)]

Here is the data. Also, this hardware played sound just fine under feisty.

hardaway@hardaway-laptop:~$ lspci | grep -i audio
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
hardaway@hardaway-laptop:~$ lspci -n | grep 00:1f.5
00:1f.5 0401: 8086:24c5 (rev 01)

[Michael (mike984)]

Is this bug connected to this one? https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/129972

Still no sound on HP DV6500 laptops...

[Achim Bohnet (allee)]

Seems, so both have the same pciid. The #129972 is older than this bug report,
but this is triaged, median and assigned to Audio Team already.
I would not like to loose this assignement ;)

@Audio Team: can you merge and adjust status, importance and assigned to?
Maybe adding the affected laptop from this report to #129972 subject is a
good idea too.

[zeddock (zeddock)]

Thanx for the info. Sorry I can't help.

Jim

On 9/26/07, allee <email address hidden> wrote:
>
> to check what audio chipset you have run:
>
> lspci | grep -i audio
>
> then check the nn:mm.x number at the start of the line. Then
>
> lspci -n | grep nn.mm.x
>
> The third number is the PCI (chipset) id.
>
>
> E.g. for the chip set of this bug report: 8086:284b. Like
>
> 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio
> Controller (rev 02)
>
> and
>
> 00:1b.0 0403: 8086:284b (rev 02)
>
> Achim
>
> --
> [gutsy] no sound on Dell Latitude D630/D830/Precision M4300/Vostro
> 1500/1700 pci id 8086:284b
> https://bugs.launchpad.net/bugs/131133
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Bram Bonné (brambonne)]

Confirmed on my D830 with yesterday's last daily build. Even compiling the alsa driver manually didn't work for me.
modprobe snd-hda-intel model=3stack gives me the following error:
FATAL: Error inserting snd_hda_intel (/lib/modules/2.6.22-12-generic/ubuntu/media/snd-hda-intel/snd-hda-intel.ko): Unknown symbol in module, or unknown parameter (see dmesg)

Please fix this before Gutsy's release, this is a very critical bug!

[dbrobert (dr-edgeoftheearth)]

To get sound to work on a Dell D830, do the following:

1. Download ALSA driver 1.0.15 rc2 (alsa-driver-1.0.15rc2).
2. Extract somewhere.
3. ./configure --with-cards=hda-intel
4. make
5. sudo make install
6. edit /lib/modules/2.6.22-12-generic/modules.dep
7. replace the start of the line with hda-intel in it so that it starts with this:

/lib/modules/2.6.22-12-generic/kernel/sound/pci/hda/snd-hda-intel.ko:

8. remove the directory /lib/modules/2.6.22-12-generic/ubuntu/media/snd-hda-intel
9. reboot

[Bram Bonné (brambonne)]

That worked! Apparently, the rc3 DOESN'T work, whereas rc2 does. I haven't got a clue why, but with the above steps it only works for rc2.

[Emanuel Goscinski (emu--deactivatedaccount)]

Also the latest hint from dbrobert doen't changed anything.
Damn I liked Gutsy a the first glance.

But this Bug isn't critical because it doesn`t makes your system unstable or unusable.

Is there anybody out there working on this issue????

[bepernoot (betercore)]

After droberts procedure, my snd-hda-intel module still did not load (due to unresolved symbols). Google suggested using "--with-cards=hda-intel,emu10k1" and now it finally works!

[Gabriel Ambuehl (gabriel-ambuehl)]

On Wednesday 26 September 2007 22:35:20 `GooZ´ wrote:
> That worked! Apparently, the rc3 DOESN'T work, whereas rc2 does. I
> haven't got a clue why, but with the above steps it only works for rc2.

On my machine, it won't resume from suspend to RAM with rc2 but rc1.

[Bram Bonné (brambonne)]

Just now I noticed that I still have quite a big problem after following above steps. The sound is working now, but when I change the volume, the sound drops to nothing, and slightly becomes more. When it is at its top again, it sounds all distorted. Anyone got an idea of how to fix this?

[Bram Bonné (brambonne)]

Extra info: This only happens when changing the MAIN volume switch, not on changing the 'Front' switch. Also, on boot (when I haven't changed the volume yet) everything sounds normal.

[Michael (mike984)]

This may be related to https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/129972

[muszek (muszek)]

 * I've just booted beta - nothing's changed.
 * I'm on Dell Inspiron 1720.

Side note... 1720 is a bigger brother of Ubuntu-based 1420N - pretty much the same hardware (I guess). So tens of thousands of people are about to lose sound when they dist-upgrade. They bought Dellbuntu to make sure everything works... and this bug is marked as being of "medium importance"?

[Jose De la Rosa (jose-de-la-rosa)]

I have a Dell 1420 with this sound card that also does not work with latest Gutsy updates.

[Tim Gardner (timg-tpi)]

My 1420 is working fine. Make sure your mixer outputs are not muted. My favorite mixer is gnome-alsamixer which clearly shows which outputs are muted.

sudo apt-get install gnome-alsamixer

After checking that your outputs are not muted, you can play the startup tune:

aplay /usr/share/sounds/startup.wav

[Tobias Heinemann (theine)]

Hey Tim, I'm glad that sound does work on your 1420, but surely not everyone in this thread just forgot to unmute the mixer outputs...

[Jon Leighton (jonleighton)]

Sound was broken for me on a Vostro 1500. Installing alsa-driver-1.0.15rc3 fixed it. Yay :)

[Achim Bohnet (allee)]

@Jon: great. Did you try suspending (to RAM)? Does it still work? This seems to be still a problem with upstream alsa-driver releases.

[Ferrix Hovi (ferrix)]

I updated to version 1.0.15rc3. I packaged using the 1.0.14-1ubuntu2 patch and it worked as is. I haven't checked on any other cards but it works as a first aid for D630. The packages for amd64 and 2.6.22-12-generic kernel can be found in the URL below.

http://earlypenguin.fi/software/packages/alsa/

[Gabriel Ambuehl (gabriel-ambuehl)]

On Friday 28 September 2007 09:54:44 allee wrote:
> @Jon: great. Did you try suspending (to RAM)? Does it still work?
> This seems to be still a problem with upstream alsa-driver releases.

Suspend-to-RAM works with 1.0.15rc1 for me but not rc2. I will try rc3 later.

[Gabriel Ambuehl (gabriel-ambuehl)]

I can suspend but not resume with 1.0.15rc3. Sticking with 1.0.15rc1.

Also, I have submitted an alsa bug about this a while ago, but got absolutely
no response, maybe some more comments would help.

See https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3392

[Emanuel Goscinski (emu--deactivatedaccount)]

Finally I have sound too.

Compiled alsa-driver-1.0.15rc3
with "configure --with-cards=hda-intel,emu10k1

I think it is highly recommended to find a solution so this cards can work out of the box. Because nearly all modern Laptops come with these sound-cards and many many people will ran into this bug.

[Gabriel Ambuehl (gabriel-ambuehl)]

At the very least, if alsa can't be updated due to fear of regressions (which
is ironic but somewhat understandable) add a precompiled deb that installs it
and have restricted-manager pop up and *tell* the user its available,
however maybe even tell it's not supported.

[Marcin Gałązka (hipnoizz)]

Confirmed for Dell Latitude D830. Relevant output from lspci:

00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)
        Subsystem: Dell Unknown device 01fe
        Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Interrupt: pin A routed to IRQ 20
        Region 0: Memory at fe9fc000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: [50] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
                Address: 0000000000000000 Data: 0000
        Capabilities: [70] Express Unknown type IRQ 0
                Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
                Device: Latency L0s unlimited, L1 unlimited
                Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
                Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
                Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
                Link: Supported a unknown, Width x0, ASPM unknown, Port 0
                Link: Latency L0s <64ns, L1 <1us
                Link: ASPM Disabled CommClk- ExtSynch-
                Link: Speed unknown, Width x0

I would say that getting the audio to work on the desktop distribution should have a high priority but I am clearly biased :s

[Michael Krufky (mkrufky)]

I forgot to mention earlier that I am using Gutsy - AMD64 ... After today's apt updates, I still have no sound. I have not tested the 32 bit version on my Dell Latitude D830.

Following the instructions here fixes sound for me, but I'd like to see the regression fixed before Gutsy release.

https://wiki.ubuntu.com/LaptopTestingTeam/DellLatitudeD830#head-40a4e1f238b3be666f63c6efefdfd883caf0bf4d

Has anybody tested vanilla 2.6.22.y on their hardware? Is this problem specific to Gutsy, or does it affect upstream 2.6.22.y also?

I'll assume that it's probably fixed in 2.6.23, given that the external build from the alsa subsystem works.

[Gabriel Ambuehl (gabriel-ambuehl)]

On Saturday 29 September 2007 15:11:57 Michael Krufky wrote:
> Has anybody tested vanilla 2.6.22.y on their hardware? Is this problem
> specific to Gutsy, or does it affect upstream 2.6.22.y also?
>
> I'll assume that it's probably fixed in 2.6.23, given that the external
> build from the alsa subsystem works.

IIRC, in 2.6.23rc5 it wasn't.

[vlombardino (vincelombardino)]

I am booting between two kernels (2.6.20-16-generic & 2.6.22-12-generic) on a Dell Latitude D630

2.6.20-16-generic - Sound works fine

2.6.22-12-generic - Does not detect sound device

Also....Many of the recommended fixes for the D830 I've tried for the D630 on the 2.6.22-12-generic have not worked.

[Jon Leighton (jonleighton)]

@Achim Bohnet: I tried suspending to RAM. It goes down but when it comes back up the screen is all messed up and I have to press the on/off button to restart it. However, I'm not sure it worked coming back up from suspend *before* I upgraded alsa-driver.

[Gabriel Ambuehl (gabriel-ambuehl)]

On Saturday 29 September 2007 22:29:42 Jon Leighton wrote:
> @Achim Bohnet: I tried suspending to RAM. It goes down but when it comes
> back up the screen is all messed up and I have to press the on/off
> button to restart it. However, I'm not sure it worked coming back up
> from suspend *before* I upgraded alsa-driver.

I'm seeing that too, with alsa-driver-1.0.15rc2 and later. With rc1 it works.

[Jon Leighton (jonleighton)]

How do we know alsa-driver is to blame though? I wouldn't thought it would be the most obvious culprit... (But then again I don't really have a clue ;))

[Bram Bonné (brambonne)]

If we want this to be fixed before the final release, I'm afraid we have to be quick, since the Kernel Freeze is scheduled for the 4th of October (https://wiki.ubuntu.com/GutsyReleaseSchedule). So is it possible to have someone do something about this really quick, since this seems like a real showstopper bug to me!

[Gabriel Ambuehl (gabriel-ambuehl)]

On Sunday 30 September 2007 12:04:07 Jon Leighton wrote:
> How do we know alsa-driver is to blame though? I wouldn't thought it
> would be the most obvious culprit... (But then again I don't really have
> a clue ;))

Well, if certain versions of alsa-driver work and others don't, then,
everything else equal, alsa-driver would likely be at fault ;)

[Mats Taraldsvik (meastp)]

[QUOTE]
taken directly from config-2.6.22-generic
# CONFIG_SND_HDA_INTEL is not set

Which explains why the module was not present in my custom kernel either. Once I compiled it, I got sound.
[/QUOTE]

from https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/131577

[Emanuel Goscinski (emu--deactivatedaccount)]

On Sunday 30 September 2007Gabriel Ambuehl wrote:
> Well, if certain versions of alsa-driver work and others don't, then,
> everything else equal, alsa-driver would likely be at fault ;)

I don`t think the fault is only at alsa-driver:
In Feisty (Kernel 2.6.20-16) with alsa-driver 1.0.13-3ubuntu1 my soundcard worked out of the box. Only mic wasn't recognized.
With self compiled alsa-driver (+ alsa-lib, alsa-utils) 1.0.15rc2 all worked fine in Feisty.

Gutsy (Kernel 2.6.22-12) with alsa-driver 1.0.14 absolutely nothing worked. It also doesn`t worked with 1.0.15rc2,
only the whole 1.0.15rc3 alsa package made it.

Also I think there is no chance to get the latest alsa-driver in the final Gutsy release.

But a good workaround would be to backport the alsa-driver, alsa-lib and alsa-utils, so that we could provide a fast solution for the users, who will run into this and are afraid compiling things by themself.

[Ryan Cresawn (jrcresawn)]

I have a Dell Vostro 1500 which is in the same situation as most of the laptops here. Sound worked with Tribe 5 but 'apt-get dist-upgrade' broke it. I haven't finished downloading Beta yet. I have followed the instructions here for building alsa-driver-1.0.15rc3 using "configure --with-cards=hda-intel,emu10k1" and sound now works fine for me. I, like everyone else, would like this fixed before release.

[drstamm (drstamm)]

This bug is also present on my Gutsy beta installation on an Inspiron 1520.

Any access to the volume control (or any program that accesses the sound controller, one supposes) yields:

"""
The volume control did not find any elements and/or devices to control. This means either that you do not have the right GStreamer plugins installed, or that you do not have a sound card configured.

You can remove the volume control from the panel by right-clicking the speaker icon on the panel and selecting "Remove From Panel" from the menu.
"""

If there is any other data needed, let me know.

[Frank (sittas)]

I had the same issue as Ryan. I have Dell Vostro 1500 and sound worked fine in Tribe 4 and was broken after a clean install of the Beta. Following Gabriel's instructions for new ALSA drivers solved the issue.

[ricolai (ricolai)]

http://ubuntuforums.org/showthread.php?t=564581&highlight=82801h

here is a solution for that chipset, that worked on Tribe 4 on a D630 for _Doc_, and worked on gusty beta on a D830 for me :

sudo apt-get install module-assistant
sudo m-a update
sudo m-a prepare
sudo m-a a-i alsa

+reboot ( or restart alsa components)

I had compiled Alsa version 1.0.15rc1 as described on https://wiki.ubuntu.com/LaptopTestingTeam/DellLatitudeD830 , but it didn't work.

maybe it's necessary to have that version of Alsa, and to do that trick to make it work.....

At last i have sound !!!

[ricolai (ricolai)]

 if i remember well, during the execution of those commands, it downloads the version 1.0.14 of Alsa ... it's odd !!

[ricolai (ricolai)]

just 1 problem with that solution: the speakers don't turn off when I plug headphones...

[Marcus Granado (mrc-gran)]

hi, ricolai, your solution worked great for a dell inspiron 1720.

[Bram Bonné (brambonne)]

Now it works for me too! Only problem is, indeed, that it doesn't turn off the speakers when I plug in my headphone. Just noticed this IN CLASS, when I read the previous comment, by getting my headphone off. I now know why everyone was looking that strange at me.

[Olivier Cortès (olive)]

Hi. Last kernel/alsa-source update (2007-10-05 night) didn't solve the problem for me. HDA soundcard is not detected with stock kernel/alsa modules.

[Olivier Cortès (olive)]

Recompiling alsa module (with module-assistant), having replaced alsa-source.tar.bz2 with alsa-driver-hg-20070905.tar.bz2 makes soundcard work again, and boot process much quicker (see my comment on #149834).

[Martinus Larsen (martinus)]

Confirm on Presicion M90

The reason for this not beeing adressed as critical because it's not affecting the system itself, is for me - and I do have to excuse my language, a lousy ass reason. These kind of problems are for the inexperienced user what the whole computing thing is about, and this not being adressed as critical, directly contributes to bug #1.

Martinus

[Rainer (rainerf)]

I can confirm that the fix using module-assistant works on a Dell Precision M4300, too.

[irwjager (jager49)]

Hi all,

The 2007-10-05/night update actually broke my flawless sound under Gutsy (Vostro 1400).
Up until then i achieved perfect operation (bar the internal mic) by compiling the latest ALSA 1.0.15rc3 driver and libs and adding

options snd-intel-hda probe_mask=1

to the /etc/modprobe.d/alsa-base file. The "probe_mask=1" should alleviate the timeout issues which some people have been experiencing.

Unfortunately since the 2007-10-05/night update i have not been able to get this setup back to work (bug #131133). Running with the latest kernel from kernel.org (2.6.23-rc9) did not resolve this...

Ivo

[elyk (elyk53)]

The module assistant fix works partially on my Vostro 1500, in that it allows my machine to play sound at all. But I still experience the behavior described in #141656 - no internal sound if headphones present at boot, and failure to mute internal speakers if headphones not present at boot.

[Bram Bonné (brambonne)]

After the last kernel update none of the previous methods work anymore for me! I just spent 1,5 hours trying every method I tried last time, but they wouldn't work!

[Omegamormegil (omegamormegil)]

So, it looks like this isn't going to be fixed for Gutsy, huh. https://lists.ubuntu.com/archives/ubuntu-devel-announce/2007-October/000345.html

That's really discouraging. I have no sound on a Dell Inspiron 1300. Compiling the new Alsa stuff didn't do any good, and I downgraded to Feisty before ricolai posted his suggestion. I need a fix I can be sure will work before taking the risk of upgrading and having no sound again. I need my Skype to work.

[elyk (elyk53)]

Bug #131577 is set as a milestone for rc1, as are several other related bugs, and this but is listed in the comments as being related, so maybe the fix for those will also fix this one. https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/131577/comments/20 also gives hope that even if this doesn't make it into gutsy final we'll get a fix whenever alsa releases, which should be soon as they're already at rc3

[ricolai (ricolai)]

After the last kernel update, it broke sound again, but I did gain my solution module assistant, and IT WORKS AGAIN !!!

there is still the problem of the speakers that aren't mute with headphones...

[Bram Bonné (brambonne)]

Did you do anything special? Because for me it won't work anymore. I really need my sound!

[ricolai (ricolai)]

i just did as before

sudo apt-get install module-assistant (useless cause you already have it if it's not the first time you do the trick)
sudo m-a update
sudo m-a prepare
sudo m-a a-i alsa

and it works as before.

[Bram Bonné (brambonne)]

Well, that didn't quite do the trick for me anymore...

On 10/7/07, ricolai <email address hidden> wrote:
>
> i just did as before
>
> sudo apt-get install module-assistant (useless cause you
> already have it if it's not the first time you do the trick)
> sudo m-a update
> sudo m-a prepare
> sudo m-a a-i alsa
>
> and it works as before.
>
> --
> [gutsy] no sound on Dell Latitude D630/D830/Precision M4300/Vostro
> 1500/1700 pci id 8086:284b
> https://bugs.launchpad.net/bugs/131133
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Gabriel Ambuehl (gabriel-ambuehl)]

On Sunday 07 October 2007 12:21:48 `GooZ´ wrote:
> Well, that didn't quite do the trick for me anymore...
>
Maybe someone should contact a higher-up about this issue. It's rather
embarassing for both Dell and Canonical if recommended hardware stops working
over something as easily fixed!

[Faan (fdsg72-lux)]

I have a D630 and the module-assistant workaround works for me to get the speakers going (but have external speaker problem where internal speakers don't mute when using phone jack). Now I have one serious issue left which is getting the internal microphone working, I need Skype and I need it bad! I enabled all the recording volume settings (InVol and InMux) but don't have any success, is there a specific recording volume setting that I should check for this to work? I also have the 'Options' tab enable and 'Input Source' is 'Mic'. Tried with 'Line In as Output' checked and unchecked without any success or change in results.

Here are my details (let me know if somebody needs more/other details?):

root@myubu:~# lspci | grep -i audio
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)
root@myubu:~# lspci -n | grep 00:1b.0
00:1b.0 0403: 8086:284b (rev 02)
root@myubu:~# uname -a
Linux myubu 2.6.22-13-generic #1 SMP Thu Oct 4 17:18:44 GMT 2007 i686 GNU/Linux
root@myubu:~#

I truly hope this gets resolved before Gutsy goes GA as I would cringe to shamefully admit that sound is broken on my favorite laptop OS until you build ALSA from source and then still don't have the microphone working :-((

[Marcin Gałązka (hipnoizz)]

Maybe we should make an authoritative list of the affected laptops (wiki...)? Maybe devs does not realize how many laptops suffers from this bug. :/

[Gabriel Ambuehl (gabriel-ambuehl)]

Does anybody know for sure, if the Inspiron 1420 N (AKA THE Dell Ubuntu machine) is affected? If so, maybe Dell could get Canonical to fix it...

[Gabriel Ambuehl (gabriel-ambuehl)]

I too confirm 2.6.22-13 is not fixing the issue, either. Compiling
alsa-driver-1.0.15rc1 by handdid solve the issue. I did not try
module-assistant.

[Bram Bonné (brambonne)]

Great idea! We should really make them aware about the fact that this is a
really serious bug which affects a lot of people, including everyone
studying Computer Science at my university who bought a laptop here! This is
quite serious, since now no one of them is willing to use Ubuntu!

On 10/8/07, haen <email address hidden> wrote:
>
> Maybe we should make an authoritative list of the affected laptops
> (wiki...)? Maybe devs does not realize how many laptops suffers from
> this bug. :/
>
> --
> [gutsy] no sound on Dell Latitude D630/D830/Precision M4300/Vostro
> 1500/1700 pci id 8086:284b
> https://bugs.launchpad.net/bugs/131133
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[elyk (elyk53)]

Has anybody checked whether this problem is present under debian testing/unstable (I'm planning on trying within the next week if nobody else has)? That would make it easier to make backport or update packages to fix the problem, even if they aren't integrated into the official release.

[Achim Bohnet (allee)]

FWIW: if your laptop model is not listed in the bug summary add it:
Actions: Edit description/tags: -> add it to summary field

[Marcin Gałązka (hipnoizz)]

See https://wiki.ubuntu.com/Gutsy_Intel_HD_Audio_Controller. The list was compiled from this thread, feel free to edit/correct/whatever.

[Achim Bohnet (allee)]

Rebuilding alsa with module assistant and rebooting make sound with 2.6.22-13 on my Latitude D830
working.

ii alsa-modules-2.6.22-13-generic 1.0.14-1ubuntu2+2.6.22-13.40 ALSA modules for kernel 2.6.22-13-generic

Pending problems with this approach:
 a) output jack does not mute internal speakers
 b) found no way in kmix to mute internal speakers and output jack independently (as an alternative to a)
 c) output jack in the docking station is not working/recognized. the one on the left of the laptop works

I've never used/tested inter/extern microphone with intel hda snd hardware, as I use a USB headset.

[Michael (mike984)]

This is also related to https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/130559

[Achim Bohnet (allee)]

@Micheal: this is listed already on Gutsy_Intel_HD_Audio_Controller wiki page. See also my comment
https://bugs.edge.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/131133/comments/58

@all: dded the wikipage to the bug description

I've added the workaround that works for me to the Gutsy_Intel_HD_Audio_Controller
wiki page as it's get more and more complicated to find infos as the length of the thread
grows. We should still report here any detail try. Summary to wiki

Anyone feels like adding a table with working / broken features versus workarounds X?

[Jon Leighton (jonleighton)]

2 questions:

1) Why are there several different bugs linked from the wiki page - should they all be consolidated to one bug or are there several different issues here?
2) Are the people affected by this bug also having trouble using a microphone (I am)?

Thanks

[Fred (frederic-lespez)]

Jon: The Intel HD Audio Controller is implemented by several codecs (from Realtek, Connexant, Sigmatel...): My laptop for instance has a Realtek AL268 codec.
The current HD Intel driver fully supports some codecs, partially supports some others and doesn't support at all others.
Hence the multiple bugs. Hence the different support : For some mics works, for some speakers are automuted...

You can check your codec with this command :
cat /proc/asound/card0/codec#* | grep Codec

I think we should complete the description on the wiki (and the bugs too) with the codec name.

[Achim Bohnet (allee)]

Thx Fred for the clarification.

My docked Dell D830 gives:

$ cat /proc/asound/card0/codec#* | grep Codec
Codec: SigmaTel STAC9205
Codec: Conexant ID 2c06

$ lspci | grep -i audio
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)
 $ lspci -n | grep 00:1b.0
00:1b.0 0403: 8086:284b (rev 02)

I'll add it to the wiki page

[Jon Leighton (jonleighton)]

I'm also SigmaTel STAC9205 on a Vostro 1500, will also edit the wiki page.

[Marcin Gałązka (hipnoizz)]

I suppose that one have to update ALSA (as described earlier) to get the codec info? There is no card* in my /proc/asound/ folder (stock Ubuntu packages, no custom ALSA).

[Jose De la Rosa (jose-de-la-rosa)]

The Inspiron 1420 is not affected. Sound is fine on mine (has been ok for a while). Is anyone having sound issues on the 1420? If not, can we remove it from https://wiki.ubuntu.com/Gutsy_Intel_HD_Audio_Controller?

Codec: SigmaTel STAC9228
Codec: Conexant ID 2c06

00:1b.0 0403: 8086:284b (rev 02)

[Marcin Gałązka (hipnoizz)]

I've removed Inspiron 1420 from the list.

We should gather additional data (primarily codec info) as fast as possible than point Audio Team (or some higher power) to the page.

[Gabriel Ambuehl (gabriel-ambuehl)]

Another thing: with 2.6.22-13 and either alsa-driver-1.0.15rc3 or rc1, resume
from suspend to RAM stopped working for me on my Latitude D830. With
2.6.22-12 it at least worked with rc1...

[Jose De la Rosa (jose-de-la-rosa)]

If sound stops working after suspend-to-ram or suspend-to-disk, try the workaround specified at http://linux.dell.com/wiki/index.php/Ubuntu_7.04/Issues/Audio_not_working_properly. This works on Gutsy. Only thing about it is that upon resuming, you may get a pop-up window about Volume Control quitting unexpectedly, just click Reload and you're fine.

[Gabriel Ambuehl (gabriel-ambuehl)]

It's not that sound stops (I had that, can deal with it) but resume doesn't
work at all. All I see is a yellow "Linu" on the screen (near the top), not
even Crtl-Alt-Delete helps after that. Only hard reset.

[ricolai (ricolai)]

"Bonjour Monsieur,
Je vous remercie d'avoir contacté le support Dell e-mail.
Je viens de faire une remontée concernant ce problème.
Des tests seront menés dans ce sens.
Je vous remercie pour votre implication.
Je reste à votre disposition pour toute information complémentaire.
Cordialement.
Anas BOULKHIR.
Support technique E-mail Dell."

Tests will be done by Dell! (if we are optimistic ...)

[Jose Gonzalez (savant)]

savant@savant-desktop:~$ cat /proc/asound/card0/codec#* | grep Codec
Codec: SigmaTel STAC9205
Codec: Conexant ID 2c06

Gutsy has no sound out of the box. WIll try fixes once I install a testing partition.

[elyk (elyk53)]

cat /proc/asound/card0/codec#* | grep Codec
Codec: SigmaTel STAC9205
Codec: Conexant ID 2c06
(I think the second one is my modem)

No Sound out of box, module-assistant lets sound play but with the aforementioned headphones problems. Microphone does not appear to work.

[Fred (frederic-lespez)]

JGonzalez : Could you precise the brand and the model of your laptop and add it to the following page if it is missing (with the codec) please ?
 https://wiki.ubuntu.com/Gutsy_Intel_HD_Audio_Controller
Thanks.

[elyk (elyk53)]

Did today's kernel update break sound for anyone else? After installing it for me the module-assistant fix no longer works (Vostro 1500 STAC9205)

[alecwh (alecwh)]

elyk: Yes, it broke it for me. I'm on a Dell Latitude D630.

Annoying. :P

[Bram Bonné (brambonne)]

I can confirm that.

On 10/10/07, elyk <email address hidden> wrote:
>
> Did today's kernel update break sound for anyone else? After installing
> it for me the module-assistant fix no longer works (Vostro 1500
> STAC9205)
>
> --
> [gutsy] no sound on Dell Latitude D630/D830/Precision M4300/Vostro
> 1500/1700/Apple Aluminium iMac/Acer TM6292 pci id 8086:284b
> https://bugs.launchpad.net/bugs/131133
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[don hardaway (don-hardaway)]

Sound does not work on my dell d800 latitude either.

[Achim Bohnet (allee)]

Status unchanged with -14 kernel: By default no sound.
Latitude D830 with:

   module-assistant -l 2.6.22-14-generic auto-install alsa # builds: 1.0.14-1ubuntu2+2.6.22-14.41

and sound works again after reboot as with -13 kernel.

[Marcin Gałązka (hipnoizz)]

don hardaway:

could you post output of

lspci -nn | grep audio

and

grep Codec /proc/asound/card0/codec#*

for your Latitude D800?

[don hardaway (don-hardaway)]

Here you go. I just update the kernel again but still no sound. I also did the module-assistant -l 2.6.22-14-generic auto-install alsa # builds: 1.0.14-1ubuntu2+2.6.22-14.41 and it did not make the sound work either. I sure hope this is fixed by the 18th or else they should move the go live date. No sound is a show stopper.

hardaway@hardaway-laptop:~$ sudo lspci -nn | grep audio
[sudo] password for hardaway:
00:1f.5 Multimedia audio controller [0401]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller [8086:24c5] (rev 01)
hardaway@hardaway-laptop:~$ sudo grep Codec /proc/asound/card0/codec#*
grep: /proc/asound/card0/codec#*: No such file or directory
hardaway@hardaway-laptop:~$

[SeL (seb-lepers)]

I do confirm that with kernel 2.6.22-14-generic of today's update, the sound doesn't work anymore.
I'm on Dell Inspiron 1720.

With kernel 2.6.22-13-generic and method B (work around at https://wiki.ubuntu.com/Gutsy_Intel_HD_Audio_Controller) it worked.
I had to configure with:
# ./configure --with-cards=hda-intel,emu10k1

This method no longer works with new kernel 2.6.22-14-generic.

[SeL (seb-lepers)]

I finally made sound work on Inspiron 1720 and kernel 2.6.22-14-generic by doing the following:

1. Download ALSA driver 1.0.15 rc2 (alsa-driver-1.0.15rc2):
wget ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.15rc1.tar.bz2
2. Extract somewhere.
3. ./configure --with-cards=hda-intel,emu10k1
4. make
5. sudo make install
6. sudo gedit /lib/modules/2.6.22-14-generic/modules.dep
7. replace the start of the line with hda-intel in it so that it starts with this:
/lib/modules/2.6.22-14-generic/kernel/sound/pci/hda/snd-hda-intel.ko:

8. remove the directory /lib/modules/2.6.22-14-generic/ubuntu/media/snd-hda-intel
9. reboot

I'm going to write a new method in https://wiki.ubuntu.com/Gutsy_Intel_HD_Audio_Controller

[elyk (elyk53)]

I installed the newly-released kernel 2.6.23 and sound works nearly flawlessly (the only thing I've noticed is the internal speakers get disabled if you have headphones plugged in when resuming from suspend, and maybe if they're present at boot as well). I'm still trying out options to see if I can get the microphone to work. I added instructions to the wiki page for the kernel compile (not really anything special vs. any other kernel recompile other than making sure that the intel hda driver is selected during kernel config - which it should be if you're basing on the default ubuntu kernel configuration).
One note though if you do get sound working this way - don't install any updates from ubuntu for kernel 2.6.22.14 - I let it do that and I had to recompile cause it killed my sound again.

[elyk (elyk53)]

scratch that - it appears that (at least on my machine) 2.6.23 only works for the first reboot after installing the new kernel - after that it goes back to not recognizing the sound card. Anyone have any idea why this could be?

[Gabriel Ambuehl (gabriel-ambuehl)]

On Thursday 11 October 2007 09:03:08 elyk wrote:
> scratch that - it appears that (at least on my machine) 2.6.23 only
> works for the first reboot after installing the new kernel - after that
> it goes back to not recognizing the sound card. Anyone have any idea why
> this could be?

Are you sure you did boot into 2.6.23 the second time? I'm currently compiling
2.6.23 and will give it a try, too.

[Marcin Gałązka (hipnoizz)]

Ok, I think that we got enough info and we should raise this issue to the Ubuntu devs. Compiling and fiddling with the settings is nice and all, but a desktop distribution without a sound out-of-box (for quite big set of a hardware) is a silly joke.

What is the correct/fast way to draw an attention Ubuntu folks to the particular issue? Irc? Mail? Some dedicated channel?

[Gabriel Ambuehl (gabriel-ambuehl)]

> What is the correct/fast way to draw an attention Ubuntu folks to the
> particular issue? Irc? Mail? Some dedicated channel?

Seeing that not working sound on the Dell's may well be a PR disaster (I'm
still not sure if the Ubuntu pre-loaded Inspiron 1420 is affected or not,
some say their's is, other claim it works for them), I already emailed Mark
Shuttleworth's secretary on Monday (explaining just how bad PR it would be),
she quickly replied saying he's travelling but she'd forward the issue. Text
available on request.

[Kevin McGehee (kevin-mcgehee)]

Although it seems there's a lot of confirmations on the subject, I can confirm with the Ubuntu 2.6.22-14-generic kernel, sound doesn't work out of the box for Latitude D630.

[Jose De la Rosa (jose-de-la-rosa)]

Dell is working with the Ubuntu folks to get this issue resolved.

[Ben Collins (ben-collins)]

Fixed with alsa backport in linux-backports-modules-2.6.22. Will be uploaded soon, and can be installed properly using the linux-backports-modules-generic package (which will ensure proper upgrades).

[Ben Collins (ben-collins)]

Should not mark this fix-committed. Needs testing.

[elyk (elyk53)]

Gabriel: I did check that I wasn't booting into a different kernel. uname -a still reported 2.6.23. I also tried booting 2.6.23 in recover mode, and the bootup messages included something like "hda audio: no codecs loaded". I'll try recompiling again and see what dmesg says on the first boot (when sound is working properly), but it has caused other problems (I can't get Intel 3945 wireless drivers working) so I think the backported alsa is probably a better solution for most people.

[llamahunter (ubuntu-richardlee)]

This needs to be fixed still... latest ubuntu kernel/driver updates killed sound again.

[David Chart (ubuntu-davidchart)]

Still no sound with RC on an aluminium iMac. linux-backports-modules seems to be unavailable as yet; I'll try to test that once they are uploaded.

[Jose De la Rosa (jose-de-la-rosa)]

For those of you with Dell systems, install linux-backports-modules-2.6.22-14-generic using synaptic and report your results. This package is already uploaded.

[alecwh (alecwh)]

Jose De la Rosa:

I'm on the Gusty beta, Dell latitude D630. I'm not seeing the package linux-backports-modules-2.6.22-14-generic on Synaptic. I refreshed my sources a few times.

[Mathieu Marquer (slasher-fun)]

Synaptic and apt-get can't find linux-backports-modules-2.6.22-14-generic, even after enabling the backport repository...
The bug is still present in Ubuntu 7.10 RC.

[ricolai (ricolai)]

here is the error message:

linux-backports-modules-generic:
 Depend: linux-backports-modules-2.6.22-14-generic but it is not installable

i'm not seeing linux-backports-modules-2.6.22-14-generic...

thank you for the involvement of Dell and Ubuntu!

[darthkhamul (emmanuel-strobbe)]

same problem on a Dell Vostro 1500 using gutsy RC for X86_64bits
m-a solutions works for 32bits install but not for 64 bits
linux-backports-modules-generic not found

[Gabriel Ambuehl (gabriel-ambuehl)]

module-assistant on 2.6.22-14 gives sound on D830, but only through notebook,
not through docking station and hooking up phones doesn't deactivate speakers
as reported by others.

[Gabriel Ambuehl (gabriel-ambuehl)]

elyk: I did build 2.6.23 for myself, and did not get sound even upon first
boot. The alsa version it ships with seems broken, too. As for ipw3945 not
working, that's because stock kernel doesn't ship the required drivers,
Ubuntu thankfully adds them for their releases.

[Ben Collins (ben-collins)]

linux-backports-modules-2.6.22 was just uploaded, so give it a few hours to be available.

Thanks

[Trev Peterson (trev-advanced-reality)]

The dependency chain is not complete. Each " -> " is a depends on. There is no linux-backports-modules-2.6.22-14.

linux-backports-modules -> linux-backports-modules-generic -> linux-backports-modules-2.6.22-14-generic (which is not available).

[Trev Peterson (trev-advanced-reality)]

Sorry, I see someone already pointed that out. Helps to refresh the browser before submitting.

[Joseph Garvin (k04jg02)]

@Ben: It's been over 24 hours since the package was uploaded and I'm still getting this error:

xxxxx@yyyyyyy:~$ sudo aptitude install linux-backports-modules
[sudo] password for prophet:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Building tag database... Done
The following packages are BROKEN:
  linux-backports-modules-generic
The following NEW packages will be installed:
  linux-backports-modules
0 packages upgraded, 2 newly installed, 0 to remove and 2 not upgraded.
Need to get 50.6kB of archives. After unpacking 106kB will be used.
The following packages have unmet dependencies:
  linux-backports-modules-generic: Depends: linux-backports-modules-2.6.22-14-generic which is a virtual package.
Resolving dependencies...
Unable to resolve dependencies! Giving up...
Abort.

Should it be up by now or does it sometimes take longer? I'm using the main default repositories. I double checked that backports was uncommented in sources.list.

[don hardaway (don-hardaway)]

Yeah---Whats up with the unreliable info. I have been waiting for the backports module to work also.

[Kevin McGehee (kevin-mcgehee)]

Confirmed. The package is still uninstallable for me as of 4:53 EST today.

[llamahunter (ubuntu-richardlee)]

So... what's the story on this missing backport package?

[Blue (vali-dragnuta)]

The backport package should be just a temp workaround. I expect the problem to be solved in the default kernel. As someone said before :
"Compiling and fiddling with the settings is nice and all, but a desktop distribution without a sound out-of-box (for quite big set of a hardware) is a silly joke."

I can also confirm the sound problem on Latitude D630, 32bit install.

[Mats Taraldsvik (meastp)]

Hmm... Hope this is resolved in the final release...
Confirmed on Dell Latitude D830

[kaelev7 (kaelev7)]

Still the same problem on Vostro 1500 with 64Bit Gutsy.
Still not able to install the backport package, and the module-assistant dosn't help.

[Moritz Breit (mbreit)]

The new linux-backports-modules package seems to solve the problem here on a Dell Latitude D830.

[Kevin McGehee (kevin-mcgehee)]

Confirmed working with Gutsy 64-bit on Latitude D630.

Kevin

On 10/15/07, Moritz Breit <email address hidden> wrote:
>
> The new linux-backports-modules package seems to solve the problem here
> on a Dell Latitude D830.
>
> --
> [gutsy] no sound on Dell Latitude D630/D830/Inspiron 1300/Precision
> M4300/Vostro 1500/1700/Apple Aluminium iMac/Acer TM6292 pci id 8086:284b
> https://bugs.launchpad.net/bugs/131133
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[JGJones (jgjones)]

Confirmed working with Gutsy 32 bits on Vostro 1500

JGJones

[don hardaway (don-hardaway)]

Well mine is not working on my D800 dell latitude. What are the settings that everyone is using?

[Kevin McGehee (kevin-mcgehee)]

I didn't change any settings; it worked out of the box after installing the
linux-backports-modules-generic package. The module that took is
'snd_hda_intel'.

Here's my output from lshw:
*-multimedia
             description: Audio device
             product: 82801H (ICH8 Family) HD Audio Controller
             vendor: Intel Corporation
             physical id: 1b
             bus info: pci@0000:00:1b.0
             version: 02
             width: 64 bits
             clock: 33MHz
             capabilities: pm msi pciexpress bus_master cap_list
             configuration: driver=HDA Intel latency=0 module=snd_hda_intel

and lspci -v:

00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio
Controller (rev 02)
        Subsystem: Dell Unknown device 01f9
        Flags: bus master, fast devsel, latency 0, IRQ 21
        Memory at febfc000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: [50] Power Management version 2
        Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+
Queue=0/0 Enable-
        Capabilities: [70] Express Unknown type IRQ 0

Let me know if you want any other information from my system.

Kevin

On 10/15/07, don hardaway <email address hidden> wrote:
>
> Well mine is not working on my D800 dell latitude. What are the
> settings that everyone is using?
>
> --
> [gutsy] no sound on Dell Latitude D630/D830/Inspiron 1300/Precision
> M4300/Vostro 1500/1700/Apple Aluminium iMac/Acer TM6292 pci id 8086:284b
> https://bugs.launchpad.net/bugs/131133
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[David Chart (ubuntu-davidchart)]

Also not working on my aluminium iMac. I'll try to poke around a bit more later.

[Mary Gardiner (puzzlement)]

Working on a Dell Latitude 630, except that microphone capture is unacceptable Has anyone else tested microphone?

[Ryan Cresawn (jrcresawn)]

After installing linux-backports-modules-2.6.22-14-generic sound works on my Dell Vostro 1500 with a current Gutsy. I'm happy. :-)

[Mary Gardiner (puzzlement)]

On Mon, Oct 15, 2007, Mary Gardiner wrote:
> Working on a Dell Latitude 630, except that microphone capture is
> unacceptable Has anyone else tested microphone?

My microphone problems have been filed at bug 153119.

[Mathieu Marquer (slasher-fun)]

Working as well for me on Dell Vostro 1500 (Ubuntu 7.10 RC1 i386).

[Marcin Gałązka (hipnoizz)]

Working after installing linux-backports-modules.

Now, this solution is acceptable for people who are determinated enough to search through forums/bug database. What about common folks?

The number of the comments in this thread and the number of duplicates is a clear evidence that this bug is a serious and common one. As Gabriel noted earlier - this can be PR disaster. For me this issue is critical enough to delay release but it is up to the Ubuntu folks to make their judgement.

@don hardaway

I think that you have a different hardware - Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) vs Intel Corporation 82801H (ICH8 Family).

[Gabriel Ambuehl (gabriel-ambuehl)]

On Tuesday 16 October 2007 09:48:12 haen wrote:
> Working after installing linux-backports-modules.
>
> Now, this solution is acceptable for people who are determinated enough
> to search through forums/bug database. What about common folks?
>

If the release can't be delayed, then I think restricted-manager should pop up
and offer installing the driver.

[Blue (vali-dragnuta)]

Agree, somehow the default install should work out of the box by fixing the default kernel or by adding the backported modules in the default install....until the default kernel is finally fixed and the backported modules will not be needed any more.

[don hardaway (don-hardaway)]

Ok sports fans---Does this mean that my dell d800 latitude that has sound under feisty is out of luck for Gusty---this would be a tragedy.

[Achim Bohnet (allee)]

@don:

this only means that the d600 has a different problem.
Find out your pci id and codec, google/search launchpad if there
already a bug report. If not open a new one and add a ref
to https://wiki.kubuntu.org/LaptopTestingTeam/DellLatitudeD800

[don hardaway (don-hardaway)]

Here is everything from the lspci command.

hardaway@hardaway-laptop:~$ lspci
00:00.0 Host bridge: Intel Corporation 82855PM Processor to I/O Controller (rev 03)
00:01.0 PCI bridge: Intel Corporation 82855PM Processor to AGP Controller (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01)
00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 81)
00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 01)
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 01)
01:00.0 VGA compatible controller: nVidia Corporation NV34M [GeForce FX Go5200 64M] (rev a1)
02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5705M Gigabit Ethernet (rev 01)
02:01.0 CardBus bridge: Texas Instruments PCI7510 PC card Cardbus Controller (rev 01)
02:01.1 CardBus bridge: Texas Instruments PCI7510,7610 PC card Cardbus Controller (rev 01)
02:01.2 FireWire (IEEE 1394): Texas Instruments PCI7410,7510,7610 OHCI-Lynx Controller
02:01.3 System peripheral: Texas Instruments PCI7410,7510,7610 PCI Firmware Loading Function
02:03.0 Network controller: Intel Corporation PRO/Wireless 2200BG Network Connection (rev 05)

[Bram Bonné (brambonne)]

+1 for letting the restricted drivers manager handle this!

On 10/16/07, Gabriel Ambuehl <email address hidden> wrote:
>
> On Tuesday 16 October 2007 09:48:12 haen wrote:
> > Working after installing linux-backports-modules.
> >
> > Now, this solution is acceptable for people who are determinated enough
> > to search through forums/bug database. What about common folks?
> >
>
> If the release can't be delayed, then I think restricted-manager should
> pop up
> and offer installing the driver.
>
> --
> [gutsy] no sound on Dell Latitude D630/D830/Inspiron 1300/Precision
> M4300/Vostro 1500/1700/Apple Aluminium iMac/Acer TM6292 pci id 8086:284b
> https://bugs.launchpad.net/bugs/131133
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[BotLobsta (kjenks-deactivatedaccount)]

The linux-backports-module-386 package did not work for me on a D830 with the 2.6.22-14-386 kernel. I am currently using alsa-driver-1.0.15rc2 on 2.6.22-11. That is the only combination that I have found to work for me.

[dbrobert (dr-edgeoftheearth)]

The linux-backports-module-386 package won't work if you've deleted the snd-hda-intel directory in the /lib/modules/2.6.22-14-generic/ubuntu/media/ directory, which you would have needed to do if you've been compiling the alsa-driver manually. You'll need to either restore that directory (if you've kept it somewhere) or re-install the package that provides snd-hda-intel (I don't know the package name off hand).

[ricolai (ricolai)]

you have to use the generic package, not the 386 one...

[Mats Taraldsvik (meastp)]

+1 for restricted manager. No need to "clutter" every system with this extra module.

[Blue (vali-dragnuta)]

But is it a "restricted" module ?! If it's not, why mix it with the restricted stuff ?

[Michael (mike984)]

On my hp dv6500t laptop, I have sound now with the backports-generic. However, the light on the keyboard that would normally turn red if muted does not - it stays blue. Also, pressing the mute button has no effect on the headphones. Pressing mute does mute the internal speakers. The volume control only controls the internal speakers. I have to set the volume and then plug in the headphones otherwise it plays through both. The microphone does not work at all.

[Horrendus (stefan-derkits-net)]

fix with backports-generic works on Inspiron 1520

[Gabriel Ambuehl (gabriel-ambuehl)]

linux-backports-modules-generic 2.6.22.14.21
does NOT fully fix the problem. I still can't get sound through the docking
station which is possible with alsa-driver-1.0.15rc1!

[don hardaway (don-hardaway)]

I read that they are getting the servers ready with gusty. Guess that means those of us with dell latitude d800 laptops are losers. My sound still does not work. This will call for a reevaluation of purchase policies at my university.

[Winckler (winckler)]

Michael,

About the capture, I discover, thought the bug in alsa bugzilla, that if you set the Capture (Recording), Digital (Recording) and Mic Boost (Playback) to about 50%, it works.

I have the same notebook, but I'm using direct alsa drivers (I couldn't test the ubuntu package yet).

Of course this isn't the solution, but might help.

[Julian Edwards (julian-edwards)]

The backports module does not fix sound on my D630. I am having to compile alsa 1.0.15rc1 to get sound (which works flawlessly, including suspend and hibernate).

00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)

[Gabriel Ambuehl (gabriel-ambuehl)]

On Wednesday 17 October 2007 10:22:06 Julian Edwards wrote:
> The backports module does not fix sound on my D630. I am having to
> compile alsa 1.0.15rc1 to get sound (which works flawlessly, including
> suspend and hibernate).

Suspend and hibernate do NOT work with the backport module for me either (on
D830), but as Julian says, 1.0.15rc1 works perfectly. I will stick to
compiling my own module as it seems.

[Jon Leighton (jonleighton)]

Sound works with linux-backports-module on my Vostro 1500. However, microphone does *NOT* work.

[SeL (seb-lepers)]

Sound works too with linux-backports-module on my Inspiron 1720, but NOT the microphone.

[Florian Snow (floriansnow)]

Works fine on Latitude D630 after compiling alsa 1.0.15 and adding options snd-hda-intel model=dell-m42 in /etc/modprobe.d/alsa-base. Microphone doesn't seem to work, but may have picked the wrong input device.
Without model=dell-m42, the sound keeps getting louder until the volume is changed.

[Bram Bonné (brambonne)]

It seems to work, although now I'm getting the problem I had in the very
beginning, that is that when I mute the sound (or put it lower than the
maximum volume), it keeps getting louder (yes, even when muted!). It helps
just to use the 'Front' volume switch instead of the 'Main' one, just the
way the module-assistant fix handled it (it attached the hardware volume
controls to the 'Front' slider).

[Nico (nico-rdo)]

Here we go, let me add one to the list...

Gutsy, 7.10
x64
up-to-date

Dell Precision M4300 laptop
4 GB RAM
160 GB HDD
1920x1200 screen
nVidia Quadro FX 360M
Intel 3945ABG wi-fi
Broadcom BCM5755M GigE

PCI Id: 00:1b.0 0403: 8086:284b (rev 02)

00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)

Codec: SigmaTel STAC9205

$ lsmod | grep snd
snd_hda_intel 375848 0
snd_pcm_oss 47488 0
snd_mixer_oss 20096 1 snd_pcm_oss
snd_pcm 93832 2 snd_hda_intel,snd_pcm_oss
snd_page_alloc 12560 2 snd_hda_intel,snd_pcm
snd_hwdep 12168 1 snd_hda_intel
snd_seq_dummy 5380 0
snd_seq_oss 36864 0
snd_seq_midi 11008 0
snd_rawmidi 29824 1 snd_seq_midi
snd_seq_midi_event 9984 2 snd_seq_oss,snd_seq_midi
snd_seq 62624 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_timer 27400 2 snd_pcm,snd_seq
snd_seq_device 10260 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
snd 69544 10 snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_hwdep,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
soundcore 10272 1 snd

$ modinfo snd-hda-intel
filename: /lib/modules/2.6.22-14-generic/updates/sound/pci/hda/snd-hda-intel.ko
description: Intel HDA driver
license: GPL
srcversion: 7C05112D0C9214E90DF6E16
alias: pci:v000010DEd00000777sv*sd*bc*sc*i*
alias: pci:v000010DEd00000776sv*sd*bc*sc*i*
alias: pci:v000010DEd00000775sv*sd*bc*sc*i*
alias: pci:v000010DEd00000774sv*sd*bc*sc*i*
alias: pci:v000010DEd000007FDsv*sd*bc*sc*i*
alias: pci:v000010DEd000007FCsv*sd*bc*sc*i*
alias: pci:v000010DEd0000055Dsv*sd*bc*sc*i*
alias: pci:v000010DEd0000055Csv*sd*bc*sc*i*
alias: pci:v000010DEd0000044Bsv*sd*bc*sc*i*
alias: pci:v000010DEd0000044Asv*sd*bc*sc*i*
alias: pci:v000010DEd000003F0sv*sd*bc*sc*i*
alias: pci:v000010DEd000003E4sv*sd*bc*sc*i*
alias: pci:v000010DEd00000371sv*sd*bc*sc*i*
alias: pci:v000010DEd0000026Csv*sd*bc*sc*i*
alias: pci:v000010B9d00005461sv*sd*bc*sc*i*
alias: pci:v00001039d00007502sv*sd*bc*sc*i*
alias: pci:v00001106d00003288sv*sd*bc*sc*i*
alias: pci:v00001002d0000AA00sv*sd*bc*sc*i*
alias: pci:v00001002d0000960Csv*sd*bc*sc*i*
alias: pci:v00001002d00007919sv*sd*bc*sc*i*
alias: pci:v00001002d0000793Bsv*sd*bc*sc*i*
alias: pci:v00001002d00004383sv*sd*bc*sc*i*
alias: pci:v00001002d0000437Bsv*sd*bc*sc*i*
alias: pci:v00008086d0000293Fsv*sd*bc*sc*i*
alias: pci:v00008086d0000293Esv*sd*bc*sc*i*
alias: pci:v00008086d0000284Bsv*sd*bc*sc*i*
alias: pci:v00008086d0000269Asv*sd*bc*sc*i*
alias: pci:v00008086d000027D8sv*sd*bc*sc*i*
alias: pci:v00008086d00002668sv*sd*bc*sc*i*
depends: snd-pcm,snd-page-alloc,snd,snd-hwdep,snd
vermagic: 2.6.22-14-generic SMP mod_unload
parm: power_save:Automatic power-saving timeout (in second, 0 = disable). (int)
...

[Gabriel Ambuehl (gabriel-ambuehl)]

On Thursday 18 October 2007 12:34:59 Nico wrote:

> I have the linux-backport-modules installed.
>
> I am plagued with the sound volume increasing on its own.
>
> I'll try options snd-hda-intel model=dell-m42 or dell-m43 or dell-m44 or
> ref
>
You may want to try compiling alsa-driver-1.0.15rc1 or the final. They both
seem to work on my D830.

[Nico (nico-rdo)]

Adding options snd-hda-intel model=dell-m42 in /etc/modprobe.d/alsa-base keeps the volume stable when using linux-backports-module on my M4300.

Nico

[Florian Snow (floriansnow)]

I can now confirm that compiling alsa drivers is not necessary on the Dell Latitude D630. Installing linux-backports-modules and adding "options snd-hda-intel model=dell-m42" in /etc/modprobe.d/alsa-base activates sound at a stable volume. Hibernate and sleep also work and muting when headphones are plugged in.

[Omegamormegil (omegamormegil)]

So, why isn't this fix explained in the Gutsy Final release notes?

[Marcin Gałązka (hipnoizz)]

After installing linux-backports-modules (no custom alsa compiling):

- a sound playback is not resumed after wake up from a suspend - I must rerun Totem/Rhytmbox/whatever to get sound again
- gnome-volume-control is a bit weird - to get sensible behavior I have maxed 'Main' and 'Front' sliders and use 'PCM' for volume adjusting
- switching between internal speakers and the headphones is ok, although there is not separate 'Headphone' slider in gvc
- multimedia keys (VolumeUp/VolumeDown/Mute') are working although the sound is muted before the 'PCM' slider reaches minimum position

I've played a bit with /etc/modprobe.d/alsa-base in hope of getting the 'Headphone' slider. I could not achieve anything, so I've removed a custom entry from this file.

Everything above on Dell Latitude D830 with SigmaTel STAC9205.

[Johannes Schauer Marin Rodrigues (josch-deactivatedaccount)]

Compiling ALSA 1.0.15 with ./configure --with-cards=hda-intel fixed everything for me on ubuntu gutsy 64bit.
I now can even suspend hibernate without loosing sound!
note: I removed /lib/modules/2.6.22-14-generic/ubuntu/media/snd-hda-intel since the driver gets installed into /lib/modules/2.6.22-14-generic/kernel/sound/pci/hda/snd-hda-intel.ko

[Johannes Schauer Marin Rodrigues (josch-deactivatedaccount)]

forgot to add: this is on a Dell D830 and as expected this bug still exists in Gutsy final I upgraded to today

[Gabriel Ambuehl (gabriel-ambuehl)]

On Thursday 18 October 2007 17:38:31 JoSch wrote:
> Compiling ALSA 1.0.15 with ./configure --with-cards=hda-intel fixed
> everything for me on ubuntu gutsy 64bit. I now can even suspend hibernate

I agree, alsa 1.0.15final seems to fix it on 32bit as well, minus the mixer
sliding weirdness as described by haen, above.

In my case, Master doesn't do a thing, but PCM instead changes volume just
fine.

[Michael (mike984)]

When testing, please be sure to report which of the following works or not:

suspend/hibernate
microphone
headsets
internal speakers
volume control
etc

[Mary Gardiner (puzzlement)]

On Thu, Oct 18, 2007, Michael wrote:
> When testing, please be sure to report which of the following works or
> not:

Dell Latitude D630

00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)
        Subsystem: Dell Unknown device 01f9

> suspend/hibernate

Sound works after resuming and any playback that was going on at the time of suspending continues.

> microphone

Working, but not well, filed as bug 153119.

> headsets

Working. Plugging/unplugging in a headset mutes/unmutes the internal speakers as expected.

> internal speakers

Working.

> volume control

Working.

[muszek (muszek)]

Dell Inspiron 1720 (I submitted relevant info @ https://wiki.ubuntu.com/Gutsy_Intel_HD_Audio_Controller - look for "1720")
Fresh install of Gutsy (I left /home almost intact, but it's not relevant...)

= microphone =
== external ==
works pretty much as expected (after fiddling with settings for a bit - it was muted and sliders weren't set to be visible)

weird thing though: when I start a skype conversation, the "Capture" slider in volume control (ubuntu app, not something in skype) goes down gradually, but only if I say something to the microphone. It goes down to around 15-20%. When the conversation is over, it immediately goes back to 100%. When I start another conversation, it immediately goes back to 15-20%. This thing doesn't appear to make a microphone any less loud, though.

external mic didn't work at all in feisty.
== internal ==
doesn't work. I started a conversation with "skype test call" (user echo123) and only heard some noise when my message was being played back. I played around

= headphones =
they work. and finally they mute/unmute internal speakers (I used to do like 3 reboots per day on Feisty).

= internal speakers =
they work as expected. I kinda hoped that Ubuntu would magically improve their crappy quality, but none such thing happened.

= suspend =
it killed the sound. I killed gnome - sound was fine again.

= hibernate =
sound works as expected. wifi doesn't, but that's another story (haven't tested that enough).

Please contact me if you need more info. muszek ATno!!SPAM gmail d0t com

[Félim Whiteley (felimwhiteley)]

Can confimr this also occurs on Inspiron 1520. The Module Assistant does allow audio to be played, but with headphone problem, where speakers are not deactivated.

[don hardaway (don-hardaway)]

Here is some information for engineering. While my sound would never work from the updates, I did a fresh install once gusty was available and my dell latitude d800 sounds works fine.

[mendesof1234 (josemendesilva)]

I tried all the methods of the site: https://wiki.ubuntu.com/Gutsy_Intel_HD_Audio_Controller
Nothing it gave resulted. I continue without sound.
My portable one is one clasus dynamic SR.-512 (equal to compal FL90).
Help me!!!!!!!!!

[Id2ndR (id2ndr)]

On a Toshiba Satellite U200, sound is OK on feisty and gutsy (without any modification).

The only remaining troubles are :
- mute, as explain in comment #96 of ricolai). Look at bug #151108.
- [0-50%] level of master channel that don't work. Look at bug #93600.
- Sometime, an "azx_get_response timeout" just before going to hibernate. There is two part : "switching to polling mode..." and " switching to single_cmd mode..." (after about 20 seconds). On resume no sound can be heard from speakers but it can be heard on headphones if there are plugged.

There troubles aren't so important to be fixed, but I hope this can help to fix one part of this bug, different of the part you all have encountered. I also think these tree troubles are linked and may all be fixed at the same time.
Please add any comment about these troubles on bug #151108 and #93600 (as this is not the main trouble of this bug).

[Uphaar Agrawalla (uphaar)]

Thanks for this update Ben. I have an Acer Aspire 4520 which has nVidia HDA card with Realtek ALC268 codec. Installing linux-backports-modules-generic solved my sound problem.
Only thing is that I had to manually add this line at the bottom of /etc/modprobe.d/alsa-base to make the sound work:
options snd-hda-intel model=acer

Perhaps this line can be added automatically, for better user experience.

I'm hoping this will be included in the gutsy-updates, since it solves so many sound problems.

[Tom Schumm (phong)]

I've got a Dell inspiron 1420 and it IS affected by this problem. I installed linux-backports-modules-generic, and it DID NOT solve the problem. I've got no audio at all.

[Jeffrey Magder (jeff-magder)]

I tried everything in this thread, but none of it worked on an Inspiron 1721. However, I was surprisingly able to fix my problems by removing the alsa package with:

sudo apt-get remove alsa

I think the problem (in my case) may be that Dell model numbers ending in a 1 (ie, 1721, 1521, 1421, as opposed to 1720, 1520, and 1420) are ATI/AMD based systems, but the ALSA package is mistaking installing drivers for Intel based systems. After removing alsa running:

lspci | grep udio

Now returns:

00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia

Also, running:

asoundconf list

Now returns:

SB

Before removing the alsa package, "asoundcond list" returned nothing.

[Jose De la Rosa (jose-de-la-rosa)]

For the Inspiron 1420, make sure you install linux-backports-modules-2.6.22-14-generic, not linux-backports-modules-generic. These 2 are different:

http://packages.ubuntu.com/gutsy/base/linux-backports-modules-2.6.22-14-generic
http://packages.ubuntu.com/gutsy/devel/linux-backports-modules-generic

[Jose De la Rosa (jose-de-la-rosa)]

In fact, you don't need backports on the Inspiron 1420, you should get sound out-of-the-box.

[Mathieu Marquer (slasher-fun)]

linux-backports-modules-generic will automatically install linux-backports-modules-2.6.22-14-generic, so that doesn't change anything.

But anyway, he says he can now see "Audio device: ATI Technologies Inc", so I think he has a Inspiron 1421, that can't be concerned by this bug since it concerns Intel platforms...

[christophre (cbgb)]

to reiterate what has already been said by a couple others:

you might need to add the following line to your /etc/modprobe.d/alsa-base (i certainly had to!) *in addition* to installing the linux-backports-modules package:

options snd-hda-intel model=<MODEL>

where <MODEL> is an entry found in /usr/share/doc/alsa-base/driver/ALSA-Configuration.txt.gz (for my dv9500t, it is "model=hp" -- search for "snd-hda-intel" in the file...). note that you may have to make a guess as to the entry to which model your particular laptop corresponds.

in addition, some people have reported needing to add "position_fix=1" in addition to "model=<MODEL>" -- whether or not you require that will likely come down to trial-and-error.

best of luck everyone!

-c

[Tom Schumm (phong)]

Still no dice on my 1420. I tried seveal combinations in /etc/modprobe.d/alsa-base after installing linux-backports-modules. No sound of any kind. This is a fresh install of Gutsy.

Anything else I should try or post here for developers to try to track this down, or should I just flatten the system again and go back to Feisty (which worked)?

[Tom Schumm (phong)]

OK, forget me, I'm an idiot. Finally found out how to unmute the sound with alsamixer. Having the audio muted is probably not a useful default setting, but that's a different bug.

[Uphaar Agrawalla (uphaar)]

On 10/23/07, Tom Schumm <email address hidden> wrote:
> Still no dice on my 1420. I tried seveal combinations in
> /etc/modprobe.d/alsa-base after installing linux-backports-modules. No
> sound of any kind. This is a fresh install of Gutsy.
>
> Anything else I should try or post here for developers to try to track
> this down, or should I just flatten the system again and go back to
> Feisty (which worked)?

Did you look for your model in the file /usr/share/doc/alsa-base/driver/ALSA-
Configuration.txt.gz, as mentioned by christophre? Your model has to
be present there, under the correct driver.

[Lorenzo Di Gregorio (lorenzo-digregorio)]

I'm having the same problem on a desktop with a Realtek ALC850 (Board Asus K8N-E Deluxe). The modules 2.6.20 work fine, the 2.6.22-14 and the backport don't. I can actually boot with 2.6.20, make a soft reset, reboot with 2.6.22-14 and everything seems ok, but when cold-starting with 2.6.22-14 there is no sound and in fact I get:

"ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave"

which is also reported here https://bugs.launchpad.net/bugs/150129

I'm not really familiar with the sound drivers (just used to work ;-)) and I tried most of the suggestions I found (recompile, use backports, set options) already. Any further idea on what could be broken?

[Tim Gardner (timg-tpi)]

Definite fix for D630 (needs model=dell-m42). Inspiron 1420, XPS 1330 definitely fixed. Probably the Vostro family as well. iMac is another problem altogether.

[Jon Leighton (jonleighton)]

Tim: Has an update been released today or are you referring to the previous linux-backports-modules? How do you define "definite fix"? Whilst sound works on my Vostro 1500, mic does not.

[cavanagh (kimsoe)]

My HP 9575 still doesn't have sound. I've tried everything that has been posted here.

[David Chart (ubuntu-davidchart)]

If iMac is another problem altogether, the bug reporting that should be de-duplicated from this one. As long as all the sound problems with the Intel card are being put into this bug, this bug is not yet fixed.

[Marcin Gałązka (hipnoizz)]

Sorry, by accident I've reassigned this bug to linux-source-2.6.22. I don't see a way to undo this action.

[Daniel Aleksandersen (da2x)]

I have the same problemon my Lenovo N100 3000 (but sound card is 8086:27d8).

[Faan (fdsg72-lux)]

On Dell D630 using backports workaround i.e. method G from Wiki, I still don't have external speakers working from the docking station headset jack. Only works if plugged directly into the D630's phone jack. As mentioned on the Wiki page, the internal microphone is still a problem with being way too soft and has noise on the playback.

Pertinent info is as follows when D630 is docked:

Here's my output from lshw:

        *-multimedia
             description: Audio device
             product: 82801H (ICH8 Family) HD Audio Controller
             vendor: Intel Corporation
             physical id: 1b
             bus info: pci@0000:00:1b.0
             version: 02
             width: 64 bits
             clock: 33MHz
             capabilities: pm msi pciexpress bus_master cap_list
             configuration: driver=HDA Intel latency=0 module=snd_hda_intel

and lspci -v:

00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)
        Subsystem: Dell Unknown device 01f9
        Flags: bus master, fast devsel, latency 0, IRQ 20
        Memory at febfc000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: [50] Power Management version 2
        Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
        Capabilities: [70] Express Unknown type IRQ 0

and Codec info:

cat /proc/asound/card0/codec#* | grep Codec
Codec: SigmaTel STAC9205
Codec: Conexant ID 2c06

Any idea what happened to the call for help directly to Mark posted earlier in this bug report? Any idea of an ETA to fix this without messing with backports as well as getting the latest ALSA release into Gutsy?

-f

[Gabriel Ambuehl (gabriel-ambuehl)]

On Monday 29 October 2007 18:35:58 Faan wrote:
> On Dell D630 using backports workaround i.e. method G from Wiki, I still
> don't have external speakers working from the docking station headset
> jack. Only works if plugged directly into the D630's phone jack. As
> mentioned on the Wiki page, the internal microphone is still a problem
> with being way too soft and has noise on the playback.
>
With alsa-driver-1.0.15 it works for me thru the docking station but the
master slider in kmix doesn't do anything.

[Jose Gonzalez (savant)]

By default, the Gutsy install cds seem to install a real-time kernel instead of the generic package. This means that anyone who installs from scratch will have to install the linux-backports-modules-rt package instead, or move to the generic kernel completely. That may be why the solution does not work for some users (it will work if you upgrade from Feisty because Feisty installs the generic kernel, at least for me. You still have to add the option snd_hda_intel etc. line to the alsa file as outlined by the wiki. So if the solution appears not to work, check that you are installing the correct backported modules.

[Jon Leighton (jonleighton)]

I have come across a workaround which gets the microphone working on my Dell Vostro 1500 (SigmaTel STAC9205 card). I've added a microphone fixes section to the wiki and written it up: https://wiki.ubuntu.com/Gutsy_Intel_HD_Audio_Controller#head-1f2c18721a2ecb093f6cf8f64d1ad8ddb13c4d0c

It would be great if people on different configurations whose microphones don't work could test it out and report back.

[Mary Gardiner (puzzlement)]

The microphone fix from Jon Leighton does not work for me (Dell Latitude
630m 82801H (ICH8 Family)). Even with all the options turned on in Edit
Preferences, I cannot set "Digital Input Source" to "Digital Mic 1". It
can only be set to "Analog Inputs".

[Florian Snow (floriansnow)]

Unfortunately, the microphone fix does not work on the Dell Latitude D630. I also added this piece of information to the wiki.

[Faan (fdsg72-lux)]

Yip, does not work on D630 and I am able to set "Digital Input Source" to "Digital Mic 1", so that is not the problem. Note I'm using the backports workaround i.e. method G from the Wiki.

[Marco (koansoftware)]

I have the same problem
Bug #159374, first reported on 2007-11-01
acer TM6292 Alsa sound fails snd_hda_intel

Subject: acer TM6292 Alsa sound fails snd_hda_intel

Ubuntu 7.10 with ACER Travel Mate 6292
Sound doesn't work, No sound at all.
I followed this topic without success
https://help.ubuntu.com/community/HdaIntelSoundHowto

Main problem is visible with dmesg
[ 16.468000] parport_pc 00:0c: reported by Plug and Play ACPI
[ 16.468000] nsc-ircc, Found chip at base=0x164e
[ 16.468000] nsc-ircc, driver loaded (Dag Brattli)
[ 16.468000] nsc_ircc_open(), can't get iobase of 0x2f8
[ 16.468000] nsc-ircc, Found chip at base=0x164e
[ 16.468000] nsc-ircc, driver loaded (Dag Brattli)
[ 16.468000] nsc_ircc_open(), can't get iobase of 0x2f8
[ 16.468000] parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,EPP,ECP,DMA]
[ 16.540000] snd_hda_intel: disagrees about version of symbol snd_ctl_add
[ 16.540000] snd_hda_intel: Unknown symbol snd_ctl_add
[ 16.540000] snd_hda_intel: disagrees about version of symbol snd_pcm_new
[ 16.540000] snd_hda_intel: Unknown symbol snd_pcm_new
[ 16.540000] snd_hda_intel: disagrees about version of symbol snd_pcm_limit_hw_rates
[ 16.540000] snd_hda_intel: Unknown symbol snd_pcm_limit_hw_rates
[ 16.540000] snd_hda_intel: disagrees about version of symbol snd_card_register
[ 16.540000] snd_hda_intel: Unknown symbol snd_card_register
[ 16.540000] snd_hda_intel: disagrees about version of symbol snd_card_free
[ 16.540000] snd_hda_intel: Unknown symbol snd_card_free
[ 16.540000] snd_hda_intel: disagrees about version of symbol snd_pcm_lib_preallocate_pages_for_all
[ 16.540000] snd_hda_intel: Unknown symbol snd_pcm_lib_preallocate_pages_for_all
[ 16.540000] snd_hda_intel: disagrees about version of symbol snd_card_proc_new
[ 16.540000] snd_hda_intel: Unknown symbol snd_card_proc_new
[ 16.540000] snd_hda_intel: disagrees about version of symbol snd_ctl_find_id
[ 16.540000] snd_hda_intel: Unknown symbol snd_ctl_find_id
[ 16.540000] snd_hda_intel: disagrees about version of symbol snd_ctl_new1
[ 16.540000] snd_hda_intel: Unknown symbol snd_ctl_new1
[ 16.540000] snd_hda_intel: disagrees about version of symbol snd_component_add
[ 16.540000] snd_hda_intel: Unknown symbol snd_component_add
[ 16.540000] snd_hda_intel: disagrees about version of symbol snd_card_new
[ 16.540000] snd_hda_intel: Unknown symbol snd_card_new
[ 16.540000] snd_hda_intel: disagrees about version of symbol snd_pcm_lib_malloc_pages
[ 16.540000] snd_hda_intel: Unknown symbol snd_pcm_lib_malloc_pages
[ 16.540000] snd_hda_intel: disagrees about version of symbol snd_pcm_lib_ioctl
[ 16.540000] snd_hda_intel: Unknown symbol snd_pcm_lib_ioctl
[ 16.540000] snd_hda_intel: disagrees about version of symbol snd_pcm_lib_free_pages
[ 16.540000] snd_hda_intel: Unknown symbol snd_pcm_lib_free_pages
[ 16.540000] snd_hda_intel: Unknown symbol snd_ctl_elem_read
[ 16.540000] snd_hda_intel: Unknown symbol snd_ctl_elem_write
[ 16.540000] snd_hda_intel: disagrees about version of symbol snd_pcm_set_ops
[ 16.540000] snd_hda_intel: Unknown symbol snd_pcm_set_ops
[ 16.540000] snd_hda_intel: disagrees about version of symbol snd_pcm_hw_constraint_list
[ 16.540000] snd_hda...

[Fred (frederic-lespez)]

Koan:

Have you read the following ressources ?
https://wiki.ubuntu.com/LaptopTestingTeam/AcerTravelmate6292
https://wiki.ubuntu.com/Gutsy_Intel_HD_Audio_Controller

The bug #159374 you opened is a duplicate of this one :
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/116326

In order to have sound works, you just have to follow the instruction of Method G described in this page :
https://wiki.ubuntu.com/Gutsy_Intel_HD_Audio_Controller

Hope it helps.

[gf (gf-interlinks-deactivatedaccount)]

I have the same problem of no sound on Gutsy
Notebook computer: Gateway M4520GZ
(Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller [8086:24c5] (rev 03))
Dual booted with Windows XP - sound works fine on XP

After following the instructions in the document: Debugging Sound Problems
still no sound
Here is the output from various commands (as instructed in the Debugging Sound Problems document)
(attached document)

Can someone please help? I don't see many other gateway complaints but I am getting discouraged with several problems.
Thanks in advance
Glady

[Obleak (fraser-arkhostings)]

I've restored sound (wouldn't say fixed) on my Toshiba A100 (with SB450) by installing linux-backports-modules and REMOVING alsa altogether.

[Ken Pratt (kenpratt)]

Adding the Dell Precision M6300 to the list of affected computers. It has the aforementioned sound hardware.

[reto.koenig (reto-koenig)]

Adding the Dell 1720 (32bit) to the list of affected computers.
Workaround:
1. Install the linux-backport-modules as mentioned before
2. Make the trick via the /etc/modprobe.d/alsa-base
  (options snd-hda-intel model=dell-m42)

[apetrelli (antonio-petrelli)]

Adding Asus F3SA to the list. I only checked method A for the moment (that does not work), this evening I will try the other methods.

[aleman (nah-corral-hotmail)]

On an HP Pavillion dv6568 sound would not work even after installing alsa 1.0.15.
The only single thing that made sound work was to change model to acer.
I added at the end of /etc/modprobe.d/alsa-base the following line:
options snd-hda-intel model=acer
After a reboot that worked fine.
(Haven't really tried headphones or mic yet though)

[Nick Andrik (andrikos)]

I have a Latitude D630 and I followed the method G, but I have these cases:

If I put model=dell-m42 like proposed I don't have the rising volume problem, but the mic is hardly heard.
If I put model=5stack I can have the mic working, but I have the problem that the volume of the central channel starts rising automatically.
Does anyone else have the same problem?

Thanks in advance

[Mathieu Marquer (slasher-fun)]

Nick --> Filed as bug 153119 :)

[Francis De Brabandere (francisdb)]

Sound solution for dell vostro 1400:
http://www.linux-on-laptops.com/hosted/Dell-Vostro-1400-Ubuntu-Gutsy.html
(did not test the headphones inserted speaker not shutting down problem)

[Alex G (ogxela-yahoo)]

I've installed linux-backports-modules-2.6.22-14-generic, but still get no audio whatsoever. snd_hda_intel shows up in lsmod. Running gutsy with all recent updates. Verified that channels are turned up and unmuted in alsamixer. Even tried "cat /dev/urandom > /dev/dsp". I've attached some text with various diagnostics (lspci, lsmod, dmesg, etc).

[David Chart (ubuntu-davidchart)]

If this bug is invalid, could someone please un-dupe the bugs for the lack of sound on the Aluminum iMac, because the fix for this bug did not fix that.

[Mary Gardiner (puzzlement)]

On Fri, Nov 30, 2007, David Chart wrote:
> If this bug is invalid, could someone please un-dupe the bugs for the
> lack of sound on the Aluminum iMac, because the fix for this bug did not
> fix that.

Check the top of the bug: the 'Invalid' status only applies to one of
the particular components it was filed against.

That said, since the other statuses are 'Fix Released' the Aluminum iMac
probably should be un-duped if the fix didn't work.

[David Chart (ubuntu-davidchart)]

They didn't work, which is why I complained at this point. As long as the bug was open against one component, there wasn't a serious problem, but that's no longer the case.

[Brian Murray (brian-murray)]

I'm uncertain as to which of the approximately 12 duplicates of this bug report applies to Aluminum iMacs. However, if you would like to unduplicate your bug report you can do this by performing the following steps.

1) Visit the duplicate bugs web page
2) Click on "Mark as duplicate" in the left hand pane
3) Remove the number (131133) that appears there

[Dan (dan-pologea)]

I have Dell Latitude D830
1) I've installed linux-backports-modules-2.6.22-14.10 (method G).
3) Made the trick via the /etc/modprobe.d/alsa-base (options snd-hda-intel model=dell-m42)

Results:
1) Sound is working
2) Internal and external mic is not working at all.

What I want:
1) Have at least internal mic working.

Voice recording is critical for me. Thanks.

[Omegamormegil (omegamormegil)]

I'd just like to say that sound works perfectly find for me now, in Gutsy, on my Dell Inspiron 1300, after little more than a simple upgrade.

I finally worked up the nerve to try upgrading to Gutsy again - something I haven't wanted to attempt since sound didn't work for me with the Gutsy RC. After upgrading from Feisty, my speakers worked without any fiddling! It took me 10 minutes to get my external mic working - I had to turn up all the capture levels in alsamixer, which defaulted to 0. That got capture working, but anytime I tried to record my voice, the playback sounded like I made the recording standing outside in a high wind. I eventually realized that holding the mic at arm's length produces crystal clear audio capture! Skype works! The capture quality is MUCH clearer and louder than I ever had with Feisty.

As I haven't seen anyone else with an Inspiron 1300 complaining about Gutsy sound, I think I'll take my model off the list.

Thanks to everyone who's been working on this issue!

[xmedh02 (hynek)]

Maybe you did the same mistake as I did, I have accidentally moved away /lib/modules/2.6.22-14-generic/kernel/sound/soundcore.ko
-- this file is not par of alsa, but of linux-image-2.6.22-14-generic. To get your symbols back, just move soundcore.ko to the original location, in case you lost it altogether, sudo apt-get install --reinstall linux-image-2.6.22-14-generic should also do the trick..

[Omegamormegil (omegamormegil)]

Have the people reporting sound problems in Gutsy tested the issues with the new version (which comes out in less than a month)? If not, burn a Hardy beta liveCD, and check to see if your sound works now. Disk images can be downloaded from here: http://www.ubuntu.com/testing/hardy/beta

[Mathieu Marquer (slasher-fun)]

No more sound problem using Hardy on Dell Vostro 1500.

[Julian Edwards (julian-edwards)]

Sound works on my Latitude D630, but the volume control is still non-linear. It starts very, very quiet until you get to about 70% and then it SUDDENLY GETS VERY LOUD!

[Spheerys (contact-spheerys)]

On my Dell Precision M6300, the sound works well out of the box now.
Thanks :)

[Jack (ubuntu-chrisjs)]

Same with Julian Edwards on Inspiron 1525. Up until around 50%, there's little to no sound, while 60% to 100% is decent. Basically, the solved/remaining problems listed in Method G of https://wiki.ubuntu.com/Gutsy_Intel_HD_Audio_Controller appear to be correct under Hardy

[Jack (ubuntu-chrisjs)]

Same with Julian Edwards on Inspiron 1525. Up until around 50%, there's little to no sound, while 60% to 100% is decent. Basically, the solved/remaining problems listed in Method G of https://wiki.ubuntu.com/Gutsy_Intel_HD_Audio_Controller appear to be the same under Hardy

[David Chart (ubuntu-davidchart)]

Sound on the iMac wasn't fixed in Hardy Beta, but the (separate) bug for that has been marked Fix Released since then, so I'm optimistic. The fix on the wiki (Method I, I think) works, although sound quality still isn't great, and I think the issue was finding a way to autodetect the hardware.

[Emanuel Goscinski (emu--deactivatedaccount)]

On my Latitude D630 Sound is working too. The nonlinear volume Control appears here too, but this is an other issue. I think.

[alecwh (alecwh)]

Hello, thanks for answering my questions before!

Off topic (the topic being sound...), but are desktop effects working on
the Latitude D630? Last time I checked, there was a problem playing
videos with desktop enabled.

Still an issue?

Thanks a bunch!

On Mon, 2008-03-31 at 19:05 +0000, Julian Edwards wrote:
> Sound works on my Latitude D630, but the volume control is still non-
> linear. It starts very, very quiet until you get to about 70% and then
> it SUDDENLY GETS VERY LOUD!
>
--
Alec Henriksen <email address hidden> @ http://alecwh.com

[Angelo Lisco (angystardust-gmail)]

Hi Alecwh...i think it's fixed in hardy...
Take a look here:

https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/184720
http://www.realistanew.com/2008/01/12/compiz-updates/#comment244

2008/4/4, alecwh <email address hidden>:
>
> Hello, thanks for answering my questions before!
>
> Off topic (the topic being sound...), but are desktop effects working on
> the Latitude D630? Last time I checked, there was a problem playing
> videos with desktop enabled.
>
> Still an issue?
>
> Thanks a bunch!
>
> On Mon, 2008-03-31 at 19:05 +0000, Julian Edwards wrote:
> > Sound works on my Latitude D630, but the volume control is still non-
> > linear. It starts very, very quiet until you get to about 70% and then
> > it SUDDENLY GETS VERY LOUD!
> >
> --
> Alec Henriksen <email address hidden> @ http://alecwh.com
>
>
> --
> [gutsy] no sound on Dell Latitude D630/D830/Precision M4300/Vostro
> 1500/1700/Apple Aluminium iMac/Acer TM6292 pci id 8086:284b
> https://bugs.launchpad.net/bugs/131133
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

[Félim Whiteley (felimwhiteley)]

My Dell Inspiron 1520 sound is working properly now. When I plug in a headphone it cuts off the speakerslike it should Nice work folks, Many thanks !

[apetrelli (antonio-petrelli)]

My Asus F3SA does not work with Kubuntu Hardy/KDE 4 remix :-(
Anyway, applying the H method, it works:

https://wiki.ubuntu.com/Gutsy_Intel_HD_Audio_Controller

[Marco Mariani (birbag)]

I have a Precision M4300, that worked fine under Gutsy after method A (with the headphone jack problem, but sound was ok)

Now I have a fresh install of Hardy in another partition, no sound at all, tried both methods A and G, nothing yet.

If you need more info, I'm here.

[alecwh (alecwh)]

Reporting from a Latitude D630 running Hardy: Everything looks good,
sound works although the volume buttons are inaccurate (volume
completely inaudible around 65%).

[David Chart (ubuntu-davidchart)]

As noted in bug 147087, the fix that worked for my Aluminium iMac under Gutsy no longer works under Hardy.

[alan ezust (alan-ezust)]

Someone please test this with a DELL D630 and an external microphone.
The problem with the older version was that you can plug an external mic but it always uses the internal mic.

[Mike (triple-eh)]

This is also an issue with the Acer Aspire 6920G notebook.

I've tried the recommendations at https://wiki.ubuntu.com/Gutsy_Intel_HD_Audio_Controller without success.

Attached are the various outputs of common "diagnostic" commands recommended in the various bug threads I've read regarding no sound.

Let me know how I can further assist with the resolution of this bug.

[savantelite (savantelite)]

My dell Lattitude D610 sound worked in Gutsy and intailly worked in intreped but nolonger works with newest kernal, not sure if this goes here or if I should put this in Intrepid?

[Mario Limonciello (superm1)]

Make a new bug

savantelite wrote:
> My dell Lattitude D610 sound worked in Gutsy and intailly worked in
> intreped but nolonger works with newest kernal, not sure if this goes
> here or if I should put this in Intrepid?
>
>

--
Mario Limonciello
*Dell | Linux Engineering*
<email address hidden>

[richard (richard-lang)]

My hardware: Dell Latitude D830, Audio device: Intel 82801H
Diagnostics: no sound. In particular:
    'asound list' detects no sound card.
     alsamixer complains: snd_ctl_open failed for default: No such file or directory

I tested Ubuntu 8.10 release candidate. The problem is solved. Sound available.

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[ethana2 (ethana2)]

Bug present, Ubuntu 9.10 x64, Dell Inspiron 1420N.

[Timothy R. Chavez (timrchavez)]

The bug task for the somerville project has been removed by an automated script. This bug has been cloned on that project and is available here: https://bugs.launchpad.net/bugs/1305851