Hi there, since yesterday I'm trying to boot Linux with an initrd image with the CVS version of Garux and it gives me all kinds of strange errors. First I found that the boot commandline was not being passed to the kernel and I hardcoded it. Now it seems that the initrd image gets corrupted at some point. Sometimes gunzip reports "RAMDISK: ran out of compressed data" which means that the image was shortened, but if it succeeds then the ext2 driver reports reads out of device boundaries, or cramfs reports decompression errors.
What might be the problem?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi there, since yesterday I'm trying to boot Linux with an initrd image with the CVS version of Garux and it gives me all kinds of strange errors. First I found that the boot commandline was not being passed to the kernel and I hardcoded it. Now it seems that the initrd image gets corrupted at some point. Sometimes gunzip reports "RAMDISK: ran out of compressed data" which means that the image was shortened, but if it succeeds then the ext2 driver reports reads out of device boundaries, or cramfs reports decompression errors.
What might be the problem?
There was a discussian about this on the Hack&Dev forums. See http://hackndev.com/e107_plugins/forum/forum_viewtopic.php?567
To me it sounds likie you might be passing the wrong initrd size value in the kernel command-line.