Recording on ice1724 cards is broken

Bug #474141 reported by Sam Davies
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Alsa in Ubuntu Jaunty with the stock kernel has an odd interaction issue with ice1724 based cards that causes no recording functions including line and mic inputs to work or show up in pulseaudio.

Examples of some ice1724-based cards:

    * Terratec Aureon Space 7.1
    * Terratec Aureon Sky/Fun 5.1
    * M-Audio Revolution 5.1
    * M-Audio Revolution 7.1
    * M-Audio Audiophile 192 (Experimental Output support in HG)
    * ESI Juli
    * ESI MAYA44 PCI

This is a pretty common chip, and these cards have fairly high recording quality so this is quite a big deal. A one line patch has been merged into mainline that fixes this issue completely, this patch can be found here: http://git.kernel.org/?p=linux/kernel/git/tiwai/sound-2.6.git;a=commitdiff;h=bd3c200e6d5495343c91db66d2acf1853b57a141;hp=43189a38dada053b820fafc47de8ba665dd3a618

I strongly recommend that the Ubuntu kernel developers integrate this patch with the Ubuntu kernel to get recording working on all of these ice1724 cards.

ProblemType: Bug
Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf9ff8000 irq 22'
   Mixer name : 'Realtek ALC1200'
   Components : 'HDA:10ec0888,104382fe,00100101'
   Controls : 40
   Simple ctrls : 22
Card1.Amixer.info:
 Card hw:1 'Revolution71'/'M Audio Revolution-7.1 at 0xec00, irq 17'
   Mixer name : 'ICE1724 - multitrack'
   Components : ''
   Controls : 27
   Simple ctrls : 22
Date: Wed Nov 4 12:51:16 2009
DistroRelease: Ubuntu 9.10
MachineType: System manufacturer P5QL PRO
NonfreeKernelModules: nvidia
Package: linux-generic 2.6.31.14.27
ProcCmdLine: root=UUID=f9c198f6-df39-49bf-9444-a1ad71d16bf6 ro elevator=deadline quiet splash
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
RfKill:

SourcePackage: linux-meta
Uname: Linux 2.6.31.5-bfs204-test-ice1724patch x86_64
WpaSupplicantLog:

dmi.bios.date: 11/28/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0902
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5QL 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.:bvr0902:bd11/28/2008:svnSystemmanufacturer:pnP5QLPRO:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QLPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5QL PRO
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Sam Davies (seivadmas) wrote :
Revision history for this message
Andy Whitcroft (apw) wrote :

[This is an automated message. Apologies if it has reached you inappropriately.]

This bug was reported against the linux-meta package when it likely should have been reported against the linux package instead. We are automatically transitioning this to the linux kernel package so that the appropriate teams are notified and made aware of this issue.

If this bug really is a bug in the linux-meta package you can move it back to linux-meta and set the Status to Confirmed, or contact us on the #ubuntu-kernel channel on the FreeNode IRC server. Thanks.

affects: linux-meta (Ubuntu) → linux (Ubuntu)
Revision history for this message
madbiologist (me-again) wrote :

There is a patch in the upstream kernel 2.6.32.14 which sounds like it should fix this issue. From the changelog:

commit 2a3097f24a0e4224e89f4e7e1ed75ef372d11068
Author: Takashi Iwai
Date: Wed May 12 16:43:32 2010 +0200

    ALSA: ice1724 - Fix ESI Maya44 capture source control

    commit 8213466596bf10b75887754773ee13c10cf86f5c upstream.

    The capture source control of maya44 was wrongly coded with the bit
    shift instead of the bit mask. Also, the slot for line-in was
    wrongly assigned (slot 5 instead of 4).

    Reported-by: Alex Chernyshoff
    Signed-off-by: Takashi Iwai
    Signed-off-by: Greg Kroah-Hartman

It's not the same patch as the one you mentioned in the opening description of this bug, but it sounds like is should fix the problem.

Revision history for this message
Sam Davies (seivadmas) wrote :

This bug can be closed it was fixed a while ago.

madbiologist (me-again)
Changed in linux (Ubuntu):
status: New → 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.