[PlanetCCRMA] Soundcard module insertion error

Fernando Lopez-Lezcano nando@ccrma.Stanford.EDU
Mon Nov 21 11:36:01 2005

On Mon, 2005-11-21 at 20:28 +0100, Michael E. Smith wrote:
> Hello:
> Yesterday I accomplished an apt-get dist-upgrade after which I had a
> several hours long mix-down session (primarily ardour) which went quite
> well from the standpoint of computer stability.
> This morning I boot up to a machine that won't load its sound cards'
> modules:
>         Starting sound driver snd-hdsp FATAL: Error inserting snd_hdsp
>         (/lib/modules/2.6 .13-0.3.rdt.rhfc4.ccrma/updates/pci/rme9652/snd-hdsp.ko): Unknown symbol in modu le, or unknown parameter (see dmesg)
>                                                            [FAILED]
>         Starting sound driver snd-intel8x0 FATAL: Error inserting
>         snd_intel8x0
>         (/lib/modules/2.6.13-0.3.rdt.rhfc4.ccrma/updates/pci/snd-intel8x0.ko): Unknown symbol in module, or unknown parameter (see dmesg)
>                                                            [FAILED]
> dmesg:
>         snd_hdsp: Unknown parameter `'
>         snd_intel8x0: Unknown parameter `'

Check /etc/modprobe.conf, look at the "options" line and in an editor
erase anything at the end of the line that looks like spaces. I've seen
this happen before, something rewrites modprobe.conf and puts stuff at
the end of the lines that the module does not like. 

After editing the file do a "/sbin/depmod -a" and try reloading the

-- Fernando

> I've been using this latest edge kernel without problems since it came
> out, and FC4 has been really quite nice until now.
> My CCRMA FC4 laptop got the same upgrade and exhibits none of the
> symptoms.
> I know I'm an idiot for blindly dist-upgrading the day of a session, and
> worse still, I'm not even sure what was even upgraded, though I remember
> hwdata was one of several (ca. 15) packages which were upgraded. I
> upgrade regularly and I believe the day before there were no new
> packages, if that's helpful identifying what I've done.
> Aside from the obvious question of how I can get this dead-in-the-water
> situation resolved, I'd also like to know if there's some sort of
> apt-get history or install log one might view to id possible culprits
> post-upgrade. Further, how can I, assuming CCRMA repos and s.o.p., how
> can I downgrade any suspect packages?