[regression]Cannot modprobe snd-hda-intel following upgrade to Feisty

[MQ]

Binary package hint: linux-source-2.6.20

I have a Compaq Presario V6030us, which contains an nVidia MCP51 audio chip. I am running Kubuntu.

Under Edgy, I needed to recompile the kernel and then install alsa version 13, since the version 14rc1 which came with Edgy did not work. Whenever there was a minor update to the Linux headers I simply recompiled the kernel and reinstalled alsa version 13. If I did not do this, it was impossible to modprobe snd-hda-intel, and aplay reported no sound card present (even though lspci recognised it) but if I did, it was possible, and the sound worked.

Since taking the upgrade to Feisty today, I have not been able to get any sound at all. I have removed and reinstalled alsa using Adept, and also by doing the manual install of the modules (compile, make, make install) of alsa versions 12, 13, 14, 14rc1, 14rc4 - all to no avail. All of them result in no sound card being detected by commands like aplay -l. Reboots, recompiling headers galore. I cannot modprobe the sound card driver, and instead get errors like:

FATAL: Error inserting snd_hda_intel (/lib/modules/2.6.20-16-generic/kernel/sound/pci/hda/snd-hda-intel.ko): Unknown symbol in module, or unknown parameter (see dmesg)

I am, of course, incredibly frustrated that something which worked before no longer works following a Ubuntu upgrade. I can't think of what else to try - this must surely be a bug and isn't just my fault.

[Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount)]

Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description doesn't yet have enough information.

Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] http://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance!

[MQ (martinquested)]

uname -a
Linux MQlaptop-kubuntu 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux

[MQ (martinquested)]

Hi,
thanks for the request - here are the two files and the uname result.
Martin

[jmspeex (jean-marc-valin)]

I've experienced exactly the same problem on my Dell D820 laptop (x86-64) and a Dell Precision 390 desktop (x86-64), which also use the snd-hda-intel driver. The same driver loads find on another Dell laptop (i386), although that one doesn't actually have that card. From this sampling, I would assume that the driver is broken only on x86-64. FYI I compiled the ALSA 1.0.14 drivers and they worked on both my x86-64 machines. Also note that kernel 2.6.20-15 worked fine even on the x86-64 machines, so it's really a *regression* that happened in 2.6.20-16. Not very good.

[Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount)]

Thank you, I'm marking this as triaged.

[karynn (skryn-hotmail)]

Same problem for Lenovo C200, realtek ALC861-VD

[Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount)]

karynn : with gutsy or feisty ?

[phaserman (stephen-fahey)]

On Friday 28 September 2007 14:57:29 Jérôme Guelfucci wrote:
> karynn : with gutsy or feisty ?
>
> ** Summary changed:
>
> - Cannot modprobe snd-hda-intel following upgrade to Feisty
> + [regression]Cannot modprobe snd-hda-intel following upgrade to Feisty

Fiesty.

I finally solved the problem by following the instructions here,
https://help.ubuntu.com/community/HdaIntelSoundHowto , and install the latest
alsa drivers, pointing them at the hda-intel.
It's worth a try.

--
Steve

[karynn (skryn-hotmail)]

Feisty. Hope this isn't the wrong place for reporting this. I've tried going through the instructions at https://help.ubuntu.com/community/HdaIntelSoundHowto and at https://wiki.ubuntu.com/LaptopTestingTeam/Lenovo3000C200_8922AZG many times, with older drivers, the current stable drivers, and the latest development drivers. It never works because I run into errors during. aplay -l returns: aplay: device_list:222: no soundcards found...

I've tried everything I could google, it seems.

[karynn (skryn-hotmail)]

edit to last post: I always run into errors during the compilation of the alsa driver/lib/utils.

[jmspeex (jean-marc-valin)]

phaserman: This is not the same problem as your link. The link is about disabling the soundcard if it hangs on boot. In the case of this bug, the machine doesn't hang, we're just trying to get the card to actually work (and disabling it in the BIOS isn't exactly a good way to do that).

[phaserman (stephen-fahey)]

On Saturday 29 September 2007 10:55:23 jmspeex wrote:
> phaserman: This is not the same problem as your link. The link is about
> disabling the soundcard if it hangs on boot. In the case of this bug,
> the machine doesn't hang, we're just trying to get the card to actually
> work (and disabling it in the BIOS isn't exactly a good way to do that).

My original contribution didn't say anything about 'hangs' or disabling the
sound card.
My problem was that after a routine update I lost sound and doing a 'aplay -l'
returned 'no sound card'
I tried a couple of things one of which didn't seem to work at all hence the
original report.
I solved my problem following the guidance
at 'https://help.ubuntu.com/community/HdaIntelSoundHowto'.
I think the key part of this is the
line 'sudo ./configure --with-cards=hda-intel' which points alsa at the
driver and installs your downloaded version alsa.

--
Steve

[jmspeex (jean-marc-valin)]

Until that gets fixed, is it at least possible to stop kernel upgrades from overwriting the drivers I install? This is really annoying. Not only do I need to work around the problem by compiling alsa drivers myself, but on top of that, every kernel "upgrade" breaks everything again.

[Rob Lanphier (robla)]

I'm not sure whether to file a separate issue or change the title of this issue from "Feisty" to "Gutsy" (or keep looking for an issue that's already been filed that I missed). Sound worked on my Feisty machine (albeit as installed by System76, rather than a fresh install performed myself). Upon upgrade to Gutsy, sound no longer worked. Turns out I had the same problem as several others described here: http://ubuntuforums.org/showthread.php?p=3599191

[jmspeex (jean-marc-valin)]

Rob,

I had a quick look and I believe it's a different bug. The bug here is:
1) About the snd-hda-intel module
2) The module does not load at all (even when using modprobe explicitly) due to missing symbols
3) As far as I understand, it's specific to x86-64

[jmspeex (jean-marc-valin)]

Just upgraded my machine to Gusty 64-bit, which I can confirm doesn't have the bug in that hda driver (yet!). It also means I will not be able to test this anymore. Yet another bug heading for a DONTCARE resolution, which is sad considering it's a regression introduced *after* the Feisty release. Sigh!

[Leann Ogasawara (leannogasawara)]

Hi All,

jmspeex had commented that this issue went away in Gutsy. Can anyone else also confirm? Also, the Hardy Heron Alpha series is currently under development and contains an updated version of the kernel. It also has ALSA version 1.0.16. It would be helpful if you could test the latest Hardy Alpha release: http://www.ubuntu.com/testing . You should be able to then test the new kernel via the LiveCD. If you can, please verify if this bug still exists or not and report back your results. We'll keep this report open against the actively developed kernel bug against 2.6.20 this will be closed. Thanks.

[Leann Ogasawara (leannogasawara)]

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.

[jmspeex (jean-marc-valin)]

Considering that this Fiesty regression is marked as WONT_FIX, please just close this bug like all the others I reported.

[Daniel Hollocher (chogydan)]

on IRC today, I was notified that this problem has been resolved for the latest releases

[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.