ALC892 not supported in 10.04 default kernel

Bug #573378 reported by Daan Willems
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: linux-image-2.6.32-21-generic

The default kernel installed with Ubuntu 10.04 has no full support for ALC892 Audio chip, available on for example the ASUS P7H55-M Pro motherboard. Instead, it reverts to a generic intel HD Audio chip, offering only stereo playback. In alsamixer, only a master, pcm and iec slider appear. Support for the ALC892 Intel G45 DEVIBX was added in 2.3.33. A mainline kernel from the kernel ppa (i.e. - linux-2.6.33-02063303-generic) successfully recognizes the chip and offers the full range of sliders in alsamixer, offering the intended 5.1/7.1 support. My suggestion is to backport the 2.6.33.x kernel module for ALC892 to the current 2.6.32 ubuntu kernel to add the correct support of this chip.

#cat /proc/asound/card0/codec#* | grep Codec
Codec: Realtek ID 892
Codec: Intel G45 DEVIBX

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-21-generic 2.6.32-21.32
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: d3vlin 1677 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfbdf4000 irq 22'
   Mixer name : 'Intel G45 DEVIBX'
   Components : 'HDA:10ec0892,10438436,00100302 HDA:80862804,80860101,00100000'
   Controls : 8
   Simple ctrls : 4
Date: Sun May 2 01:41:44 2010
HibernationDevice: RESUME=UUID=1f43f3bb-945c-4686-b783-ee23bcc89d02
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: System manufacturer System Product Name
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=f4add25a-22c0-436d-b60d-847acc2dc160 ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34
RfKill:

SourcePackage: linux
dmi.bios.date: 12/30/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0601
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P7H55-M PRO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0601:bd12/30/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7H55-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Daan Willems (daan-daanwillems) wrote :
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Daan,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Daan Willems (daan-daanwillems) wrote :

Hi Jeremy,

As stated in the initial bugreport, I have found the issue resolved in
the mainline kernel from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.33.3-lucid/
specifically: linux-image-2.6.33-02063303-generic_2.6.33-02063303_amd64.deb

This was the suspected result, since support for ALC892 was only added to the linux kernel in 2.6.33, see: http://kernelnewbies.org/Linux_2_6_33

If you require any additional information, let me know.

tags: removed: needs-upstream-testing
Changed in linux (Ubuntu):
status: Incomplete → Triaged
importance: Undecided → Medium
Revision history for this message
stenzn (stenzn) wrote :

Is this working for anyone who backported a newer Maverick kernel to Lucid? I'm running 2.6.35-9-generic on Lucid from the kernel mainline PPA to try to get my sound working with pulseaudio. alsactl still says it's unknown hardware (but analog output works fine with alsa).

$ uname -r
2.6.35-9-generic

$ cat /proc/asound/cards
 0 [SB ]: HDA-Intel - HDA ATI SB
                      HDA ATI SB at 0xfe3f4000 irq 16
$ alsactl init
Unknown hardware: "HDA-Intel" "Realtek ALC892" "HDA:10ec0892,104383c0,00100302" "0x1043" "0x8410"
Hardware is initialized using a guess method

Revision history for this message
szbab (szbab-club) wrote :
Revision history for this message
penalvch (penalvch) wrote :

Dean Willems, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12-rc1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Daan Willems (daan-daanwillems) wrote :

Hi Christopher, please see my comment from 2010-05-04. Ever since, I found no more problems related to this issue, up until my current 13.04 install. Best regards, Daan Willems

Revision history for this message
penalvch (penalvch) wrote :

Daan Willems, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/573378/comments/7 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. For the potential regression in Raring, please file a new report via a terminal:
ubuntu-bug linux

Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
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.