Very low volume with HDA/ALC883

Bug #107232 reported by Gioele Barabucci
26
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ALSA driver
Invalid
Undecided
Unassigned
linux (Ubuntu)
Invalid
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

I have an Intel ICH8 + Realtek ALC883 onboard chip on my motherboard.

Everything works fine but the volume is very low even when all the controls are at 100%.

I found this line in dmesg:
  hda_codec: Unknown model for ALC883, trying auto-probe from BIOS...
This bug is probably related to bug #77024 (nVidia based mb) and bug #64356 (ICH3 chipset).

This happens with Feisty beta (16 April 2007) and alsa-driver 1.0.13.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 3133 F.... pulseaudio
CRDA:
 country GB:
  (2402 - 2482 @ 40), (N/A, 20)
  (5170 - 5250 @ 40), (N/A, 20)
  (5250 - 5330 @ 40), (N/A, 20), DFS
  (5490 - 5710 @ 40), (N/A, 27), DFS
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfe9f4000 irq 43'
   Mixer name : 'Realtek ALC883'
   Components : 'HDA:10ec0883,1462f603,00100002'
   Controls : 47
   Simple ctrls : 22
CasperVersion: 1.311
DistroRelease: Ubuntu 12.04
LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120319)
MachineType: To Be Filled By O.E.M. MS-7276
Package: linux-image-3.2.0-19-generic-pae 3.2.0-19.30
PackageArchitecture: i386
ProcEnviron:
 TERM=xterm
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
ProcVersionSignature: Ubuntu 3.2.0-19.30-generic-pae 3.2.11
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-19-generic-pae N/A
 linux-backports-modules-3.2.0-19-generic-pae N/A
 linux-firmware 1.71
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: precise
Uname: Linux 3.2.0-19-generic-pae i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 12/08/06
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V7.1
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: MS-7276
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV7.1:bd12/08/06:svnToBeFilledByO.E.M.:pnMS-7276:pvr1.0:rvnMSI:rnMS-7276:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: MS-7276
dmi.product.version: 1.0
dmi.sys.vendor: To Be Filled By O.E.M.

Revision history for this message
Gioele Barabucci (gioele) wrote :

The same problem happens with latest Feisty (28 Aug 2007).

Revision history for this message
Gioele Barabucci (gioele) wrote :

The volume is higher on Gutsy tribe5, but still very soft even at 100%.

Revision history for this message
Jens Landgré (jens-landgre) wrote :

I suggest you to edit:
    /etc/modprobe.d/alsa-base
Adding the following line:
    options snd-hda-intel model=3stack-6ch

That worked for me, the volume is still not high, but at least high enough to be usable.
Possibly you have one of the other models available for this chipset:

ALC883/888
   3stack-dig 3-jack with SPDIF I/O
   6stack-dig 6-jack digital with SPDIF I/O
   3stack-6ch 3-jack 6-channel
   3stack-6ch-dig 3-jack 6-channel with SPDIF I/O
   6stack-dig-demo 6-jack digital for Intel demo board
   acer Acer laptops (Travelmate 3012WTMi, Aspire 5600, etc)
   medion Medion Laptops
   targa-dig Targa/MSI
   targa-2ch-dig Targs/MSI with 2-channel
   laptop-eapd 3-jack with SPDIF I/O and EAPD (Clevo M540JE, M550JE)
   auto auto-config reading BIOS (default)

I haven't been able to make the microphone work tho, the driver seem to have bugs in several areas.

Revision history for this message
Lark (florent-g) wrote :

Same problem with nvidia MCP51, chip ALC883 onboard.
Sound is very low on every audio output (speaker, headphones)
Syslog and dmesg output "hda_codec: Unknown model for ALC883, trying auto-probe from BIOS..."
I tried to unload then reload kernel module snd-hda-intel with every chipset model without any result.

System: Ubuntu Hardy, kernel 2.6.24-16, ALSA 1.0.16

Attached file contains :
 - lspci -vvnn
 - lsmod
 - alsa-info
 - alsa-base
 - cat /proc/asound/card0/codec#0

I've posted a bug ticket on alsa project bug tracker : https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3932
If you're encountering this problem, please report it on the bugtracker.

Revision history for this message
Alastair Sherringham (asherringham) wrote :

I also have this problem.

7.10 Feisty i386 ---- OK
8.04 Hardy i386 ---- sound very quiet (upgrade last week)
8.10 Intrepid i386 -- sound very quiet (alpha 3)

I have reverted to Feisty for now.

Tried all "model" options to snd-hda-intel module.
Tried rebuilding and reinstalling ALSA (module-assistant).

All channels unmuted (alsamixer).
All channels at 100%.
Using ALSA throughout (pulseaudio not working at all).

I have to turn up my amplifier/speakers) /way/ too high to hear decent sound.

However - in Intrepid a3 (at least), this appears to be mainly a problem with audacious (1.5.1-2ubuntu2). Rhythmbox, VLC and xine all seem OK (although not perfect - volume controls still at max).

Hardware :

Shuttle SG33G5 2x Q6600 (quad-core2)

card 0: Intel [HDA Intel], device 0: ALC883 Analog [ALC883 Analog]
Codec: Realtek ALC888

aplay -l :

**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC883 Analog [ALC883 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 1: ALC883 Digital [ALC883 Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 3: ATI HDMI [ATI HDMI]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

See attachment for codec#0.

See attachment

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

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
Alastair Sherringham (asherringham) wrote :

Dist :

Ubuntu 8.10 Alpha5
+ full update as of 2008-09-13 13:00 GMT

2.6.27-3-generic
alsa-base 1.0.17.dfsg-1ubuntu1

The problem is still occurring.

Sound works, but a decent listening volume level means - all controls have to be maximised. But even now, the sound is not loud, just "normal" small quiet room level. I am outputting sound through my stereo (line in) and have the stereo set to a normal volume level (always been perfectly OK).

I currently run Gutsy (I wrongly said Feisty above).
The sound problem was in Hardy when I updated a few months ago, and in Intrepid when I first tested it. I have reverted to Gutsy for now.

Note however - I have purchased a Soundblaster PCI card (which I removed for this re-test) and this works much better. So ... I will just stop using onboard audio and ignore this issue.

-----------------------------------------------------------------------------------------------------

Tested mp3 on :

Rhythmbox 0.11.6
Audacious 1.5.1

-----------------------------------------------------------------------------------------------------
Shuttle SG33G5 2x Q6600 (quad-core2)
Intel ICH9
HDA Intel audio

Volume levels all at 100% (no muting)
 - Master, PCM, Front (tried adding some others)
Gnome Volume Control device set as "HDA Intel (Alsa Mixer)"

System/Preferences/Sound - all "Autodetect" and Test OK.

---------------------------------------------------------------------------------------------------------------------------------------

NOTES

Shuttle SG33G5 is on the latest BIOS. However, unless I boot with kernel option "acpi=off", I hang at boot.

dmesg :

HDA Intel 0000:00:1b.0: setting latency timer to 64
hda_codec: Unknown model for ALC883, trying auto-probe from BIOS...

lspci -v :

00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 02)
 Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer Device 3106
 Flags: bus master, fast devsel, latency 0, IRQ 22
 Memory at fdff8000 (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 Root Complex Integrated Endpoint, MSI 00
 Kernel driver in use: HDA Intel
 Kernel modules: snd-hda-intel

Revision history for this message
DavidGN (davidgn) wrote :

Same problem here running 8.10 with updates to date on HDA Intel ALC888 analog / digital.

It's consistent across all apps - Firefox, Songbird, VLC, Rhythmbox, Totem, etc. I'm using headphones.

Every volume control is set to 100% (Alsa, PulseAudio, Alsamixergui) and also tried pushing playback stream over 100% in PulseAudio Manager, but this caused distortion.

I've tried every device available in Sound Preferences.

I found the following in /var/log/messages:

HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
alsa-util.c: Device hw:1 doesn't support 44100 Hz, changed to 16000 Hz.
alsa-util.c: Device hw:1 doesn't support 2 channels, changed to 1.

I haven't been able to find instructions on how to change that 'low' level - or even if it is relevant.

Changed in linux:
status: Incomplete → New
Revision history for this message
Moises Marangoni (moises-marangon) wrote :

Workaround
Works well for me

Unlike my previous machines, my Thinkpad T61 doesn't have a hardware volume
control. Since most media isn't normalised, the built-in speakers often
struggle to be heard over environmental noise. Eventually I got fed up with
this and found out how to get around it with some magic in /etc/asound.conf
(system-wide) or ~/.asoundrc (per-user):

    pcm.!default {
        type plug
        slave.pcm "softvol"
    }

    pcm.softvol {
        type softvol
        slave {
            pcm "dmix"
        }
        control {
            name "Pre-Amp"
            card 0
        }
        min_dB -5.0
        max_dB 20.0
        resolution 6
    }

I now have a "Pre-Amp" control that goes from line level to +20 dB in
increments of 5 dB. Unfortunately min_dB must be set below zero, but oddly
enough setting the control to the lowest position seems to force it to mute.
The final result is:
┌─────┐
│ 100 │ +20 dB
│ 80 │ +15 dB
│ 60 │ +10 dB
│ 40 │ +5 dB
│ 20 │ Line Level (No Amp.)
│ 00 │ Mute
└─────┘

Now when I play something soft I can temporarily pump up the volume much
higher than the software mixer would otherwise allow, then lower it afterwards
to not distort loud or normalised audio.

Hope someone else finds this useful!
Thanks Matthew Rosewarne

Revision history for this message
kernel-janitor (kernel-janitor) wrote :

Hi gioele,

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? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

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

apport-collect -p linux-image-`uname -r` 106447

Also, if you could 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: kernel-sound
tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
xq19space (tuxlux) wrote :

OK kernel-janitor,

Thanks for keeping up with this bug.

I can confirm it's still a problem. We just installed Jaunty on two new Malibal notebooks.

We can't get the sound volume up at all. It's so low that a pin dropping will drown it out.

We've tried all the recommended solutions to no avail.

Nothing seems to work and it's embarrassing for business applications when you can't even show your software products to customers because no one can hear anything.

We'll have to drop Ubuntu if this isn't corrected. There's no excuse for this. Ubuntu has a long history of sound issues and it's obvious that nothing is being done about it.

We're looking at a launchpad page at this moment and I see over a thousand pages regarding sound/volume issues.

What is up with Ubuntu's sound/volume? It's been years and it's a big problem with every release.

We have this problem on different makes and models. We've had this same issue over and over with various versions; from Feisty to Jaunty.

You guys have got to get this right. It will kill you in the long run. Unfortunately, I believe the long run is already here.

I'm going to run your command for "auto gather and attached updating"

I sincerely hope this helps you decipher how we can all overcome this debacle.

We are trying very hard to get other companies in the oil and gas industry interested in Ubuntu. One of the biggest complaints we hear about is that Ubuntu is unreliable regarding sound/volume; excluding printers and projectors.

Business can tolerate a lot compared to Microsoft, however, having no sound is the bullet that will deliver the kill shot for the Ubuntu OS. People just will not use a system that offers a "Cheese-Weenie" sound config. What's worse is this issue is very old and it's not being address at all by Canonical.

We have all of our machines dual booted with XP on half and Ubuntu on the other half. Sound works fine on all machines when booted into XP, nevertheless, Ubuntu has virtually no sound volume on any of our machines. That goes for desktops, workstations, and field engineer notebooks.

So.....this is not just an isolated case of some quirky brand or model. Its a very real issue for most brands and models.

Changed in alsa-driver:
status: Unknown → New
Revision history for this message
Gioele Barabucci (gioele) wrote :

This problem is still present in Ubuntu 10.04.2 using the kernel Linux 2.6.32-31-generic.

Revision history for this message
Gioele Barabucci (gioele) wrote :

This problem is still present in Ubuntu Precise 12.04 (daily live CD from 2012-03-19).

The kernel version is 3.2.0-19-generic-pae.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: removed: needs-upstream-testing
Revision history for this message
Gioele Barabucci (gioele) wrote : AcpiTables.txt

apport information

tags: added: apport-collected precise
description: updated
Revision history for this message
Gioele Barabucci (gioele) wrote : AlsaDevices.txt

apport information

Revision history for this message
Gioele Barabucci (gioele) wrote : AplayDevices.txt

apport information

Revision history for this message
Gioele Barabucci (gioele) wrote : ArecordDevices.txt

apport information

Revision history for this message
Gioele Barabucci (gioele) wrote : BootDmesg.txt

apport information

Revision history for this message
Gioele Barabucci (gioele) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
Gioele Barabucci (gioele) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
Gioele Barabucci (gioele) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Gioele Barabucci (gioele) wrote : Dependencies.txt

apport information

Revision history for this message
Gioele Barabucci (gioele) wrote : IwConfig.txt

apport information

Revision history for this message
Gioele Barabucci (gioele) wrote : Lspci.txt

apport information

Revision history for this message
Gioele Barabucci (gioele) wrote : Lsusb.txt

apport information

Revision history for this message
Gioele Barabucci (gioele) wrote : PciMultimedia.txt

apport information

Revision history for this message
Gioele Barabucci (gioele) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Gioele Barabucci (gioele) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Gioele Barabucci (gioele) wrote : ProcModules.txt

apport information

Revision history for this message
Gioele Barabucci (gioele) wrote : PulseList.txt

apport information

Revision history for this message
Gioele Barabucci (gioele) wrote : UdevDb.txt

apport information

Revision history for this message
Gioele Barabucci (gioele) wrote : UdevLog.txt

apport information

Revision history for this message
Gioele Barabucci (gioele) wrote : WifiSyslog.txt

apport information

tags: removed: cft-2.6.27 linux-source-2.6.20 needs-kernel-logs
Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.2.0-19.31)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.2.0-19.31
Revision history for this message
Gioele Barabucci (gioele) wrote :

The problem is still present with kernel 3.2.0-20.32 in the precise daily-live image from 2012-03-23.

tags: removed: kernel-request-3.2.0-19.31
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.2.0-20.32)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.2.0-20.32
Revision history for this message
Gioele Barabucci (gioele) wrote :

As I said, what I tested it with is kernel 3.2.0-20.32. Where should I write this so that the bot understand this? Also, given how many boards are sold with this audio chip, can this bug be triaged and confirmed by an Ubuntu kernel developer?

tags: removed: kernel-request-3.2.0-20.32
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Brad Figg (brad-figg) wrote :

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.2.0-20.32
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: bot-stop-nagging
removed: kernel-request-3.2.0-20.32
Revision history for this message
penalvch (penalvch) wrote :

Gioele Barabucci, thank you for reporting this bug and helping make Ubuntu better. 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.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Gioele Barabucci (gioele) wrote :

The problem is still present in today's upstream kernel: linux-image-3.4.0-999-generic_3.4.0-999.201206020420_i386 + linux-image-extra-3.4.0-999-generic_3.4.0-999.201206020420_i386.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Gioele Barabucci, please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/daily/current/ . If the issue remains, please run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

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

Also, if you could 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.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thanks in advance.

tags: added: fiesty gutsy needs-upstream-testing
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
dino99 (9d9) wrote :

closing that old report, as it has not got recent comment.

Changed in alsa-driver:
importance: Unknown → Undecided
status: New → Invalid
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.