/var/log/syslog is full of these insmod errors. Do they matter?

Alan


Nov 10 19:29:20 RubinPC insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Nov 10 19:29:20 RubinPC insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 10 19:29:20 RubinPC insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Nov 10 19:29:20 RubinPC insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Nov 10 19:29:20 RubinPC insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Nov 10 19:29:20 RubinPC insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Nov 10 19:29:21 RubinPC kernel: usb.c: USB device 2 (vend/prod 0x56a/0x13) is not claimed by any active driver.
Nov 10 19:29:21 RubinPC kernel: shpchp: shpc_init: cannot reserve MMIO region
Nov 10 19:29:21 RubinPC insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Nov 10 19:29:21 RubinPC insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg

It seems your bootup scripts are trying to insert modules that do not exist.
As long as your system is currently functional, then these can probably just be ignored, but they're probably wasting valuable miliseconds at boot time .

Maybe these modules have been installed into the kernel, but your system thinks that they were compiled as modules.

On the other hand, if you are having difficulty using some of your hardware then I would definitely investigate these module errors in greater detail.

There's my two cents.

Did you boot at that time ? at 19:28-29 ?
These modules are for pci hotplugging. 99% the hotplug infrastracture tries to load them, but they don't get loaded. These modules
are not useful so you can ignore the errors.
In order for them not to be loaded, you can do 2 things.
1) Disable hotplug completely ("/etc/rc.d/rc.hotplug" in slackware)
2) If you want the hotplug functionality (hotplug loads automatically the modules for all devices that are not needed in boot e.g sound
card,usb,ethernet etc) then modify "/etc/hotplug/blacklist" adding these modules.