[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#139043: [ARM] Please mention conflict with "noinitrd" boot option

On Thu, 21 Mar 2002, Adam C Powell IV wrote:

> Let's start with section 5.4, "Booting from TFTP," here's my suggestion:
> Booting from the network requires that you have a network connection
> supported by the boot floppies, including either a static network
> address or a DHCP server, and also a TFTP server. RARP or BOOTP servers
> may also be needed for non-NetWinder machires.  The installation method
> to support TFTP booting is described in (link)Preparing Files for TFTP
> Net Booting, Section 4.4.
> On NetWinder machines, the 10Mbps NE2000-compatible card is interface
> eth0 and the 100Mbps Tulip card is interface eth1. NOTE: You need
> NeTTrom 2.2.1 or later to boot the installation system. NeTTrom 2.3.3 is
> recommended: get it from
> |<tt>ftp://ftp.netwinder.org/devteam/andrewm/redhat/RPMS/| </tt>. After

This should be: ftp://ftp.netwinder.org/pub/netwinder/firmware/

Maybe a link to how to upgrade your firmware.

> rebooting and interrupting the boot process during the countdown, you
> must first configure the network either with a static address:
>     NeTTrom command-> setenv eth0_ip
> where 24 is the number of set bits in the netmask, or a dynamic address:
>     NeTTrom command-> (I don't know how to do this)
> You may also need to configure the <tt>route1</tt> settings if the tftp
> server is not on the local subnet.  The rest of the config is pretty
> standard (the save-all step is optional):
>     NeTTrom command-> setenv netconfig_eth0 flash
>     NeTTrom command-> setenv kerntftpserver
>     NeTTrom command-> setenv kerntftpfile tftpboot.img
>     NeTTrom command-> save-all
>     NeTTrom command-> setenv kernconfig tftp
> Only the last of these interferes with normal disk booting, so it is
> safe to save-all right before it, which will store the network settings
> in case you need to boot from the network again. Use the "printenv"
> command to review your environment settings. Finally, if your
> "cmdappend" NeTTrom variable has the "noinitrd" option (which is
> necessary to boot 2.4 kernels), you must remove it so the downloaded
> kernel can boot with its attached ramdisk.

You probably do not want the 'netconfig_eth0 flash' set in the firmware
with save-all.

> Okay.  This is kind of NetWinder-centric, but that's what I have so
> others can add their subarch's stuff.  Section 4.4 should also be modified:

And in big comments say something along the lines of:
	You must use eth0 (10-baseT) ne2k(piece of crap) for the tftpboot.
Yes, it is possible to boot off eth1, but the Debian kernels do not
support it, and you have to pass lots of parameters with cmdappend, it is

I forget the exact commands for booting via dhcp, but 'boot diskless' will
work, provided you dhcp server is setup to send all the info which the
NeTTrom wants.  'load diskless' should work as well, without doing the
boot, although there was a bug in it in the past which may be fixed in


Reply to: