problem using mkinitrd

[ghostbunny]

Hi @ all,

i need a bit help i set up a new pymouth theme edited the conf file for plymouth in /etc/plymouth for using the new them. now new the works on shut down. i know i have to rebuild the initrd to get the change on the start up but when i use

Code: [Select]

mkinitrd /boot/initrd-3.2.18-pclos2.bfs.img 3.2.18.pclos2.bfs
i just get

Code: [Select]

No modules available for kernel "3.2.18.pclos2.bfs".
i also tried to use the -f option in the hope that it means force but nothing changed i still get the same error.

Has someone an idea what to do is?

thanks in advance

regards
ghostbunny

[Just17]

Try it using the verbose   -v   option .....  it might tell what is the cause

[tschommer]

It's a typo in your command line: 3.2.18-pclos2.bfs instead of 3.2.18.pclos2.bfs ("-" after the version number) 

[Just17]

I was also trying to recall where I had seen that message previously ....  me of course 

http://www.pclinuxos.com/forum/index.php/topic,105588.msg901887.html#msg901887

[ghostbunny]

ok thanks. i solved it a bit other

tried to reinstall the kernel ... does not help
installed other kernel and uninstalled current... worked
installed old kernel uninstalled new kernel... worked also

but now mylivecd fails on every start. it comes to the part when creating the initrd for the livecd and aborts with
can't umount /tmp/mylivecd.<pid?>/initrd.mnt

any ideas?

[pags]

Not sure about the LiveCD question, at the moment, but a tip for mkinitrd...

If you're running it for the currently running kernel, the following helps prevent typos:

Code: [Select]

mkinitrd /boot/initrd-`uname -r`.img `uname -r`

Again, this only works for the currently running kernel!  If you need to run it for an installed kernel that isn't running (as I happened to last night, when the initrd failed during the install of the 3.4 from testing), then you'll have to type it all out, so check your syntax (command completion and copy/paste could help, some).