loadlin corrupts large initrd

		LinuxQuestions.org > Forums > Linux Forums > Linux - General
loadlin corrupts large initrd

Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices

Welcome to LinuxQuestions.org, a friendly and active Linux Community.

You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!

Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.

Are you new to LinuxQuestions.org? Visit the following links:
Site Howto | Site FAQ | Sitemap | Register Now

If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.

Having a problem logging in? Please visit this page to clear all LQ-related cookies.

Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.

Exclusive for LQ members, get up to 45% off per month. Click here for more info.

Search this Thread

07-17-2004, 01:19 PM	#1
jsmerritt LQ Newbie Registered: Jul 2004 Posts: 2 Rep:	loadlin corrupts large initrd When I use LOADLIN (1.6c) to boot a linux system, it appears that LOADLIN loads a corrupted image of the initial ramdisk (initrd=) when the compressed size of the ram disk image exceeds about 5.8 Mbytes ! The symptoms of a corrupted image vary: sometimes the Kernel will complain about an invalid compressed RAMDISK image, other times errors will be generated by attempts to read beyond the bounds of the image, and sometimes the Kernel will just "hang". I have carefully read the "constraints" in the LOADLIN documentation and I do not appear to be in violation of any of the listed contraints. This problem appears on old computers (100 MHZ, Pentium-S with 64MBytes of RAM) as well as newer computers (3.00 GHZ P4 with 2 GBytes of RAM). The Kernel being loaded is 2.4.20-31-9 (updated RedHat 9). - Can anyone else confirm this behavior ? - Any solutions (other than using a smaller ramdisk ? Thanks, Scott.

Posting Rules
You may not post new threads You may not post replies You may not post attachments You may not edit your posts BB code is On Smilies are On [IMG] code is On HTML code is Off Forum Rules

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
problems with very large initrd	softwizz	Fedora	2	05-13-2005 08:11 AM
bittorrent always corrupts downloads	snecklifter	Linux - Software	2	05-11-2005 09:57 AM
genhdlist corrupts install tree	hspahr	Fedora - Installation	0	03-22-2005 05:00 AM
my XP box downloads but corrupts all	ChopSueyX	General	8	09-25-2004 09:45 PM
Large drive- too much space lost by large block size?	tome	Linux - General	5	12-14-2001 01:32 PM

All times are GMT -5. The time now is 11:40 AM.

Main Menu

(Con't)

My LQ

Write for LQ

LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.

Main Menu

Syndicate

Latest Threads

LQ News

Twitter: @linuxquestions