Hello,

I'm using Sarge(Debian) with a 2.6.7 kernel. I compiled a custom kernel using the debian kpkg programme (which works like a charm!). After installing the kernel, there suddenly is no initrd.img in /boot anymore! In / I find a symlink initrd.OLD that points to the initrd image in /boot of the previous kernel. However, there is no (new) initrd.img symlink in / nor is there a initrd image of my new kernel in /boot...

How can this be? Is there a way I can create (or recreate) a initrd.img for my new kernel? Any help greatly appreciated. If any additional info is needed: I gladly supply that for you.

check out this url, same exact problem ... start with post 8, it is the solution ...

make sure to apt-get update and upgrade first to make sure u've got initrd-tools and newest gcc and g++ since i know u use make-kpkg.

If you follow mine, this is so wierd, that in fact I believe that I installed initrd-tools and a bunch of other stuff-->like in an upgrade or something the stuff wasn't upgraded and blah blah blah cause I thought make-kpkg fixed it all for ya.

Anyway thisll getcha goin.

Thank yates.

http://www.linuxquestions.org/questi...hreadid=217811

outabux,

thanks for your suggestions, I am going to read the thing now. I reckon I've got the latest pakages you mentioned because I did a clean netinstall only two days ago with Sarge. I just find it WEIRD that kpkg didn't create a initrd image for the new kernel....

Off to read now. Will be back!
denniz

Thanks outabux for pointing me to that thread. Post #8 has the solution I think.
I believe I have forgotten to add the --initrd flag to the make-kpkg command!
Hence it didn't build any initrd image (but it did rename the symlink to the OLD initrd in / !!! For the old kernel). I'm starting to appreciate debian and it's packages more and more! They are very cleverly build!!! Now, on to my box. Will check to see if I've got the packages you suggested (initrd-tools and dash (got mkinitrd already)).

Will come back but am 99% sure this is it!
denniz

That's an answer to my post that worked (read down further), however, after an apt-get update, upgrade and dist-upgrade(to make sure), i got new gcc and g++ again (hmm). Would it be fair to say that 2.6.8-1 and 2.6.7-3 & -3 would not compile properly under the versions (off all the stuff listed in the documentation for one reason or another...upgrading packages, etc..) we might have had, cause I restored from backup my working partition and kernel development os partitions and voila, with and without them they worked.

I restored again and did it without an --initrd switch (i dont need one) in both for 2.6.8-1 cause It's here

READ the rest of the posts on down. Had same exact problem, however, i apt-get update/upgrade daily, sometimes twice or more depending on how packages are hitting)

Well we shall see after subsequent 2.6.8-X kernels and 2.6.9 which I might stay away from (those odd numbered boys, mmm, dunno) Parts of 5 and 7 gave me fits.

Anyway please read the rest of the posts and see what u make of it.

Rememver the pover is n z apt-get !

SLater!

Oh Yes kde3.3 is here!
6111 Nvidia kiks server sometimes -->5336 ok, 4996 if it would work w/2.6 then i'd rather have the quality

Good Luck. REPLY

I double checked and the proposed solution worked indeed!

However, I checked my packages (initrd-tools, dash, cramfs) and they were the latest versions for TESTING. And there were no problems whatsoever. Perhaps you are experiencing problems because of a mix of versions (stable, testing and unstable).

Thanks again Outabux, on to the next stage now...