Bug#279718: modprobe: FATAL: Error inserting apm
On Fri, Nov 05, 2004 at 01:26:46AM +0800, Dan Jacobson wrote:
> Package: kernel-image-2.6.8-1-k7
> Version: 2.6.8-4
> Severity: minor
> File: /lib/modules/2.6.8-1-k7/kernel/arch/i386/kernel/apm.ko
>
> It seems thru several upgrades we are unable to bid adieu to messages
> at boot like
>
> modprobe: FATAL: Error inserting apm
> (/lib/modules/2.6.8-1-k7/kernel/arch/i386/kernel/apm.ko): No such
> device
>
> modprobe: FATAL: Error inserting pciehp
> (/lib/modules/2.6.8-1-k7/kernel/drivers/pci/hotplug/pciehp.ko):
> Operation not permitted
>
>
> modprobe: FATAL: Error inserting shpchp
> (/lib/modules/2.6.8-1-k7/kernel/drivers/pci/hotplug/shpchp.ko):
> Operation not permitted
> shpchp: can't be loaded
> missing kernel or user mode driver shpchp
>
>
> Instead of scaring the user, perhaps some checking could like
> /usr/bin/apm_available can do, first. But all that is over my head.
I am curious to know what is trying to insert these modules.
Are they in the initrd image, or are the listed in /etc/modules and
/etc/init.d/modutils is trying to insert them? Or both?
I stronly suspect that it is a configuration problem,
although perhaps making /etc/init.d/modutils a bit smarter would be a
good idea.
> P.S., I notice
> apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
> apm: overridden by ACPI.
> Hmmm, and perhaps every 1/2 hour repeated in the logs.
Why do you have the apm module insterted on a system that has ACPI?
> Anyways, one hopes to not see "FATAL" unless something is wrong with
> one's hardware.
Where are you seeing "FATAL" ?
In the logs telling you that modprobe failed?
You could try asking the modprobe maintainer to change the message
if you like. But as far as modprobe is concerned the opperation was
fatal.
> P.S., reportbug says:
> There may be a problem with your installation of kernel-image-2.6.8-1-k7;
> the following files appear to be missing or changed:
> debsums: checksum mismatch kernel-image-2.6.8-1-k7 file lib/modules/2.6.8-1-k7/modules.pcimap
> debsums: checksum mismatch kernel-image-2.6.8-1-k7 file lib/modules/2.6.8-1-k7/modules.dep
> debsums: checksum mismatch kernel-image-2.6.8-1-k7 file lib/modules/2.6.8-1-k7/modules.ieee1394map
> debsums: checksum mismatch kernel-image-2.6.8-1-k7 file lib/modules/2.6.8-1-k7/modules.usbmap
> debsums: checksum mismatch kernel-image-2.6.8-1-k7 file lib/modules/2.6.8-1-k7/modules.isapnpmap
> debsums: checksum mismatch kernel-image-2.6.8-1-k7 file lib/modules/2.6.8-1-k7/modules.alias
> debsums: checksum mismatch kernel-image-2.6.8-1-k7 file lib/modules/2.6.8-1-k7/modules.symbols
> Do you still want to file a report [y|N|q|?]? y
This looks suspiciously similar to
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=258979
which I haven't had a chance to look into yet.
--
Horms
Reply to: