***TOTAL EDIT OF POST***
No, I didn't get an initrd. I'm using sid.
I read dbboltons post above, but I didnt follow the link
I was trying to figure out why I couldn't boot with the new kernel, keeping myself busy trying to generate initrds and writing a lengthy post. Its shorter now.
Kernel panicked with this:
Code: Select all
no filesystem could mount root, tried:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
It wouldn't boot with an initrd borrowed from the other kernel. (The vanilla kernel wouldn't boot without an initrd either.) Maybe I don't need an initrd, a guru on irc said it was unnecessary. I guess I need to move some of the stuff that the initrd does to the kernel. What and how?
I cant see whats in the initrd. "file initrd.img-2.6.30-1-amd64" says its a gzip, but i can't gunzip it. What is it? I read in some post on a mailinglist from around 2003 that the debian initrd uses cramfs. This fails anyway:
Code: Select all
mount -o loop -t cramfs initrd.img-2.6.30-1-amd64 tmp/
***TOTAL EDIT OF POST***