Re: [Etherboot-users] Booting kernel+initd files bigger then 1.44mb?

[Boris <bo...@mi...>]

I found out my problem. I had to specify the --param="ramdisk_size=xxxx" in
mkni-linux. In my kernel, the default was 4096k [and when I added the new
files, the image uncompressed to over 4096k so it would complain. I added a
different ramdisk_size to something bigger and it works now. :) Thanks
though for helping.
----- Original Message -----
From: "Donald J Christensen" <dj...@ci...>
To: "Boris" <bo...@mi...>
Cc: <eth...@li...>
Sent: Thursday, October 25, 2001 5:13 PM
Subject: Re: [Etherboot-users] Booting kernel+initd files bigger then
1.44mb?


> > Boris wrote:
> >
> > I am having problems booting [kernel+disk] image greater then 1.44mb. Is
this a tftp issue? If it is, What would you recommand as a good tftpd
> > server[under linux] and what parameters would I need to do to make tftpd
send more then just 512bytes at a time. Also what is the image size limited
> > too? It works perfect for complete images under 1.44mb. Each time I
create a [kernel+disk] image greater then 1.44mb, It starts up the kernel
but
> > then when it loads the ramdisk part, It keeps saying "dev: 01:00
blksize=1024 blocknr=5282 sector=10564 size=1024 count=1 attempt to access
beyond
> > end of device."
>
> The tftp server is not likely to be a problem.  Even with a very poor
> implementation, you should be able to get 16 MB.  A conformant
implementation
> should support 32 MB.  An implementation that supports the "blksize"
option
> can theoretically go to 4 GB.  Etherboot requests 1400+ bytes per block,
> which would allow something around 90MB with a server that supports the
> blksize option.
>
> The "standard" Linux tftp server does not appear to support the blksize
> option.
>
> -Don
>
> --
> Don Christensen     Senior Software Development Engineer
>   dj...@ci...     MMABU - Mid-Market Access Business Unit
>   Cisco Systems    ComLOB - Commercial Line of Business
>    San Jose, CA   "It was a new day yesterday, but it's an old day now."
>