using mkinitrd for new kernel, but /lib/modules/[kernel] doesn't exist any more

slacker_ · 09-20-2013, 12:40 PM

I say anymore because I ran this:

Code:

mkinitrd -c -k 3.2.45 -m ext3 -f ext3 -r /dev/sda1

and it completed fine, made my initrd tree and the initrd.gz, but I realized that I called the wrong module because my fs is ext4, not ext3. So I just thought "well, I'll run it again," but now it's kicking back this error:

Code:

ERROR: No /lib/modules/3.2.45 kernel modules tree found for kernel "3.2.45"

And this is reflected in the /lib/modules directory as there is no longer a 3.2.45 directory there.

I'm not sure how to 'reload' that directory or what I have to do to fix this, any I would appreciate any and all help, thanks!

Didier Spaier · 09-20-2013, 12:54 PM

I answered you here.

I suggest you don't open new threads if not needed, your questions won't get more exposure and that makes harder for people trying to help you to know your context - that they need to make relevant suggestions.

slacker_ · 09-20-2013, 03:08 PM

Quote:

Originally Posted by Didier Spaier

I answered you here.

I suggest you don't open new threads if not needed, your questions won't get more exposure and that makes harder for people trying to help you to know your context - that they need to make relevant suggestions.

Right, yes, sorry. I had typed this up and meant to just leave it open without submitting it yet with the intention of submitting it if no one get back to the other thread after a few hours.