saa7134-alsa module is broken in 24-7 kernel

Asked by ogc

Can't load saa7134-alsa module in new 24-7 kernel. dmesg shows this:

[ 46.708330] saa7134_alsa: disagrees about version of symbol snd_pcm_new
[ 46.708337] saa7134_alsa: Unknown symbol snd_pcm_new
[ 46.708864] saa7134_alsa: disagrees about version of symbol snd_pcm_stop
[ 46.708869] saa7134_alsa: Unknown symbol snd_pcm_stop
[ 46.709627] saa7134_alsa: disagrees about version of symbol snd_pcm_lib_ioctl
[ 46.709632] saa7134_alsa: Unknown symbol snd_pcm_lib_ioctl
[ 46.709816] saa7134_alsa: disagrees about version of symbol snd_pcm_set_ops
[ 46.709821] saa7134_alsa: Unknown symbol snd_pcm_set_ops
[ 46.710106] saa7134_alsa: disagrees about version of symbol snd_pcm_hw_constraint_integer
[ 46.710111] saa7134_alsa: Unknown symbol snd_pcm_hw_constraint_integer
[ 46.710512] saa7134_alsa: disagrees about version of symbol snd_pcm_period_elapsed
[ 46.710517] saa7134_alsa: Unknown symbol snd_pcm_period_elapsed
[ 46.710611] saa7134_alsa: disagrees about version of symbol snd_pcm_hw_constraint_step
[ 46.710616] saa7134_alsa: Unknown symbol snd_pcm_hw_constraint_step

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu linux Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:

This question was originally filed as bug #190944.

Revision history for this message
Caroline Ford (secretlondon) said :
#1

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description does not yet have enough information.

Please include the following additional information, if you have not already done so (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" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo 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!

Revision history for this message
ogc (hackrez) said :
#2

uname -a
Linux giedrius-laptop 2.6.24-7-generic #1 SMP Thu Feb 7 01:29:58 UTC 2008 i686 GNU/Linux

Revision history for this message
ogc (hackrez) said :
#3
Revision history for this message
Patrice DUROUX (patrice-duroux) said :
#4

Hy,

This is the same for me even with 2.6.24-8-generic.

Regards,
Patrice.

Revision history for this message
ogc (hackrez) said :
#5

Yep, this also present in 24-8.

Revision history for this message
ogc (hackrez) said :
#6

Still happens in 24-10.

Revision history for this message
Leann Ogasawara (leannogasawara) said :
#7

Hi Guys,

This issue was already reported in bug 192559 and is actively being addressed by a member of the kernel team. I'm going to go ahead and mark this report as a duplicate of 192559. Thanks.

Revision history for this message
diamond (diamondswilldo58-deactivatedaccount) said :
#8

help me this is all so new to me thanks Cindy

Revision history for this message
Launchpad Janitor (janitor) said :
#9

This question was expired because it remained in the 'Open' state without activity for the last 15 days.