I'm currently running a ~x86 gentoo setup with a 2.6.1-gentoo-r1 kernel.
So all bleeding edge stuff I suppose. So, this morning I performed a
periodic 'emerge -u world' to get all the latest updates, and ran into a
problem with module-init-tools-3.0_pre6 (upgraded from pre5 which worked
fine).

Having booted back into Gentoo, after a spot of tinkering with FreeBSD,
I saw a bunch of module related errors on the boot screen. Firstly,
following the "Calculating module dependencies" message I got the
following series of errors:

FATAL: Module off not found.
FATAL: Module ide-probe-mod not found.
FATAL: Module off not found.
FATAL: Module st not found.
FATAL: Module ide-probe-mod not found.
FATAL: Module ide-tape not found.
FATAL: Module off not found.
FATAL: Module st not found.
FATAL: Module ide-probe-mod not found.
FATAL: Module ide-tape not found.

Then a bit later, when loading the soundcard modules, I get:

Error inserting snd-via82xx
(/lib/modules/2.6.1-gentoo-r1/kernel/sound/pci/snd-via82xx.ko): Unknown
symbol in module, or unknown parameter (see dmesg).

And in the syslog I see:

Jan 26 21:45:14 [kernel] snd_via82xx: Unknown symbol snd_ac97_set_rate
Jan 26 21:45:14 [kernel] snd_via82xx: Unknown symbol
snd_ac97_update_bits
Jan 26 21:45:14 [kernel] snd_via82xx: Unknown symbol snd_ac97_bus
Jan 26 21:45:14 [kernel] snd_via82xx: Unknown symbol
snd_mpu401_uart_interrupt
Jan 26 21:45:14 [kernel] snd_via82xx: Unknown symbol snd_mpu401_uart_new
Jan 26 21:45:14 [kernel] snd_via82xx: Unknown symbol
snd_ac97_tune_hardware

The system seemed OK after this, other than the sound being dead, which
given the errors, was no surprise! I restored things to normality by
doing:

emerge -C module-init-tools
emerge =module-init-tools-3.0-pre5

and rebooting.

Does anyone have an inkling of what's happening here? I'm no expert on
the ins and outs of the modprobe.conf file, and unfortunately following
the reboot the modprobe.conf from the pre6 version got overwritten, so
no diff comparison, unless I upgrade the package again. Also, where else
would be a good place to take this problem? The kernel.org mailing lists
perhaps?

-Bruce





--
[EMAIL PROTECTED] mailing list

Reply via email to