Insmod errors at boot time before usplash

[Charles Majola]

/init: 63: cannot open /sys/bus/scsi/devices/*/type: No such file
insmod: error inserting
'/lib/modules/2.6.12-8-386/kernel/drivers/video/console/bitblit.ko': -1 File Exists
insmod: error inserting
'/lib/modules/2.6.12-8-386/kernel/drivers/video/console/font.ko': -1 File Exists
insmod: error inserting
'/lib/modules/2.6.12-8-386/kernel/drivers/video/console/tileblit.ko': -1 File Exists
insmod: error inserting
'/lib/modules/2.6.12-8-386/kernel/drivers/video/console/fbcon.ko': -1 File Exists
insmod: error inserting
'/lib/modules/2.6.12-8-386/kernel/drivers/video/cfbcopyarea.ko': -1 File Exists
insmod: error inserting
'/lib/modules/2.6.12-8-386/kernel/drivers/video/cfbfillrect.ko': -1 File Exists
insmod: error inserting
'/lib/modules/2.6.12-8-386/kernel/drivers/video/cfbimgblit.ko': -1 File Exists
insmod: error inserting
'/lib/modules/2.6.12-8-386/kernel/drivers/video/softcursor.ko': -1 File Exists

[Charles Majola (chmj)]

This happens with the preview release

[Fabio Massimo Di Nitto (fabbione)]

Jeff, do we attempt to load module twice?

Charles, these errors are harmless.

[Matt Zimmerman (mdz)]

*** Bug 21823 has been marked as a duplicate of this bug. ***

[Alvaro Muñoz (alvaro-munoz)]

I get the exact same output right after grub loads the kernel. Then it goes to
Usplash.
It doesnt affect the system (as far as I've experienced), but they're still
errors...

[Alvaro Muñoz (alvaro-munoz)]

FIXED in 2.6.12-9-386 kernel.

[Alvaro Muñoz (alvaro-munoz)]

after todays upgrade, the messages appear again, but now pointing at the -9 kernel.
Also, at restart/shutdown, something along the lines of "K01usplash: bootsplash
command not found" appears...

[Marc Wiriadisastra (strikeforce)]

Yeah exactly the same for me as well. Only just noticed in on reboot but thats
about it. Hasn't affected me in any way but the errors are there.

[Matt Zimmerman (mdz)]

*** Bug 22723 has been marked as a duplicate of this bug. ***

[Matt Zimmerman (mdz)]

Why can we not simply use modprobe for this?

[Matthew Garrett (mjg59)]

A good question. I asked Jeff, but I can't remember the explanation. Jeff?

[Jeff Bailey (jbailey)]

(In reply to comment #10)
> A good question. I asked Jeff, but I can't remember the explanation. Jeff?

It runs before depmod is run.

We could use modprobe --dry-run to generate the insmod commands at built time
and make sure we get them right, though.

[Matt Zimmerman (mdz)]

(In reply to comment #11)
> (In reply to comment #10)
> > A good question. I asked Jeff, but I can't remember the explanation. Jeff?
>
> It runs before depmod is run.
>
> We could use modprobe --dry-run to generate the insmod commands at built time
> and make sure we get them right, though.

depmod should be run when the initramfs is generated. Since no modules are
added to the initramfs at boot time, there should not even be a need to run
depmod from initramfs.

But if this is necessary for some reason of which I'm unaware, why don't we just
run it earlier?

[Yvan AMILIN (yvanamilin-deactivatedaccount)]

Hint: the file /usr/share/initramfs-tools/scripts/init-top/usplash contains the
following lines:

if [ $SPLASH = "true" -a $VESA = "false" ]; then
 insmod /lib/modules/`uname -r`/kernel/drivers/video/console/bitblit.ko
 insmod /lib/modules/`uname -r`/kernel/drivers/video/console/font.ko
 insmod /lib/modules/`uname -r`/kernel/drivers/video/console/tileblit.ko
 insmod /lib/modules/`uname -r`/kernel/drivers/video/console/fbcon.ko
 insmod /lib/modules/`uname -r`/kernel/drivers/video/cfbcopyarea.ko
 insmod /lib/modules/`uname -r`/kernel/drivers/video/cfbfillrect.ko
 insmod /lib/modules/`uname -r`/kernel/drivers/video/cfbimgblt.ko
 insmod /lib/modules/`uname -r`/kernel/drivers/video/softcursor.ko
 insmod /lib/modules/`uname -r`/kernel/drivers/video/vgastate.ko
 insmod /lib/modules/`uname -r`/kernel/drivers/video/vga16fb.ko
 mknod /dev/fb0 c 29 0
 mknod /dev/tty0 c 4 0
 /sbin/usplash -c &
fi

[Jeff Bailey (jbailey)]

(In reply to comment #12)
>
> depmod should be run when the initramfs is generated. Since no modules are
> added to the initramfs at boot time, there should not even be a need to run
> depmod from initramfs.
>
> But if this is necessary for some reason of which I'm unaware, why don't we just
> run it earlier?

initramfs allows other modules to be concatenated on to the end, either after
its built or at boot time by the boot loader. Long term, the idea is that the
bootloader should be able to add the modules that it wants and not load others
(So that an initramfs that doesn't need network drivers doesn't have them and
it's assembled at boot time out of generic pieces). Because the modules in the
initramfs then isn't known at boot time, the depmod has to be done at runtime.

(Sorry about the lag, I apparnetly didn't click "commit")

Tks,
Jeff Bailey

[Matt Zimmerman (mdz)]

Since we don't actually do this yet, and since usplash works by hooking into the
initramfs build, it is safe for depmod to run before usplash's runtime hook

[Matt Zimmerman (mdz)]

*** Bug 22823 has been marked as a duplicate of this bug. ***

[Matt Zimmerman (mdz)]

*** Bug 22831 has been marked as a duplicate of this bug. ***

[Matt Zimmerman (mdz)]

At any rate, in case it wasn't clear, this needs to be addressed for 5.10. The
user community is confused and worried by these errors.

[Jeff Bailey (jbailey)]

I've seen two confirmations that this is fixed by usplash 0.1-12. If you're
seeing this, please regenerate, your initramfs with dpkg-reconfigure
linux-image-$(uname -r)

Tks,
Jeff Bailey

[Sam Argiro (argirosa)]

(In reply to comment #19)
> I've seen two confirmations that this is fixed by usplash 0.1-12. If you're
> seeing this, please regenerate, your initramfs with dpkg-reconfigure
> linux-image-$(uname -r)
>
> Tks,
> Jeff Bailey

Hi Mr Bailey,

I had this error and it disappeared w/ one of the Usplash updates and now it's
back...I currently have Usplash 0.1-16. Should we wait for a fix via synaptic
or apply the reconfigure mentioned here? I'm not quite sure how the command
above works, would you mind replying w/ and example? Thank you.

[Jeff Bailey (jbailey)]

sudo dpkg-reconfigure linux-image-$(uname -r)

is the command you literally type in to regenerate the initramfs. Then reboot
and the errors should be gone.

Tks,
Jeff Bailey

[Matt Zimmerman (mdz)]

*** Bug 22927 has been marked as a duplicate of this bug. ***