AD1988B : Sound stopped working after upgrading to Hardy

Bug #184725 reported by Mahesh Asolkar
10
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

I am using Asus P5K-E Wifi/AP motherboard's on board sound.

-------
Codec: Analog Devices AD1988B
Address: 0
Vendor Id: 0x11d4198b
Subsystem Id: 0x1043829b
Revision Id: 0x100400
-------

Sound used to work just fine in Gutsy. After I upgraded to Hardy, sound has stopped working.

What information can I provide to further investigate this issue?

Thanks,
Mahesh.

Revision history for this message
Daniel T Chen (crimsun) wrote :

Please attach the contents of /proc/asound/card*/*codec* .

Revision history for this message
Mahesh Asolkar (asolkar) wrote :
Revision history for this message
josef (ok1dtm) wrote :

I am using ASUS P5B-PLUS motherboard sound on board.
Codec-ADI 1988 8 channel
Sound in Hardy no work. Alsamixer displayed "no sound device". In Kubuntu 8.04 the same problem. In Dapper and Gusty soun is OK.

Revision history for this message
Mahesh Asolkar (asolkar) wrote :

Is there a guide or something I can use to debug this further? May be generate some useful data for the developers? Is there something I can refer to, to find where exactly the sound is failing?

Revision history for this message
josef (ok1dtm) wrote :

Moment I wait Alpha 5 and install again.

Revision history for this message
josef (ok1dtm) wrote :

Hardy Alpha sound no work! I using ASUS P5B-PLUS motherboard sound on board. Chip ADI 1988 8 channel
/proc/asound is empty. Also /proc/asound/card is empty. Problem is in kernel 2.6.24-8 generic. In Gusty Ubuntu/Kubuntu sound work perfectly, but when I loading kernel from Heron sound also no play and sound device is no detected.

Revision history for this message
Mahesh Asolkar (asolkar) wrote :

Josef, thanks for pointing to alsamixer in your earlier comment - somehow I missed it before this. When I ran alsamixer I found that some channels were muted - specifically Front. I increased the level on that and now I have sound. I think it is slightly attenuated as compared to what it was in Gutsy, but there's sound.

Revision history for this message
Sylvain Pasche (sylvain-pasche) wrote :

What's the status of this issue with kernel 2.6.24-12?

I'm wondering if this is the same issue as bug 194816. I have a AD1988B chip (Asus P5B Deluxe wifi) and I have no sound since Hardy. However the issue is that the snd-hda-intel module fails when loading.

Revision history for this message
hithwen (hithwen) wrote :

I have the same problem, the sound stopped working after upgrading...

aplay -l
**** Lista de PLAYBACK Dispositivos Hardware ****
card 0: Intel [HDA Intel], device 0: ALC883 Analog [ALC883 Analog]

Revision history for this message
Farhad Shakiba (fshakiba) wrote :

I confirm this issue on an Asus p5b Plus. No sound in Hardy. Sound has been working fine for the past 2 distributions.

:/proc/asound$ aplay -l
**** List of PLAYBACK Hardware Devices ****

Revision history for this message
josef (ok1dtm) wrote :

Farhad Shakiba : please use pnpacpi=off in kernel option. This bug is in 2.6.24.xx version. In 2.4.25 is fully fixed

Revision history for this message
Farhad Shakiba (fshakiba) wrote :

Thanks josef.

pnpacpi=off workaround fixed the issue and I have sound again. Looking at the intel hda module loading error it seems to have memory space overlap issues as it fails to allocate memory for that specific device. But it seems you already know the solution.

Revision history for this message
Sylvain Pasche (sylvain-pasche) wrote :

Do people having this bug see messages like "Unable to reserve mem region #1:4000@febf8000 for device 0000:00:1b.0" in the kernel logs?

If so, this bug should be marked as a duplicate of bug 194816.

The issue in bug 194816 is fixed in the next kernel 2.6.25 or by applying a patch (there's the link in that bug).

Revision history for this message
klmorgan (klm3030) wrote :
Revision history for this message
klmorgan (klm3030) wrote :

It's working now but I don't know what fixed it. I tried several things.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Sylvain Pasche (sylvain-pasche) wrote :

I can confirm the sound card works fine on Intrepid

Revision history for this message
klmorgan (klm3030) wrote : Re: [Bug 184725] Re: AD1988B : Sound stopped working after upgrading to Hardy

I have it working now although not sure just what fixed it.

On Fri, 2008-08-29 at 06:16 +0000, Sylvain Pasche wrote:

> I can confirm the sound card works fine on Intrepid
>

Revision history for this message
ElisaCollins (elisa-terese) wrote :

We got a brand new Dell delivered yesterday with 7.10, and upgraded to 8.04 today and the sound stopped working.

aplay -l gives us:
blah blah no soundcard

and
lspci -v gives us:

Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)

yet clicking on the volume control tells us:

No volume control GStreamer plugins and/or devices found.

According to some digging around in the forums, this may be a driver issue, but I can't find the driver I need through ALSA. The same forum post mentions that it could be a bug, so I'm here.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Setting this to "Fix Released" based on the decision to stick with the 2.6.27 kernel for Intrepid - https://lists.ubuntu.com/archives/kernel-team/2008-September/003107.html

@ElisaCollins - if you could try the latest Intrepid Ibex 8.10 Alpha that would be appreciated. Thanks.

Changed in linux:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.