From b85b6607b7997b902eb43fe5a8f55211cbd3e110 Mon Sep 17 00:00:00 2001 From: Frans Pop Date: Wed, 15 Mar 2006 17:29:49 +0000 Subject: Update of original English docs --- fi/boot-installer/arm.xml | 206 +++++++++++++++++++++++++++++++++++----------- 1 file changed, 156 insertions(+), 50 deletions(-) (limited to 'fi/boot-installer/arm.xml') diff --git a/fi/boot-installer/arm.xml b/fi/boot-installer/arm.xml index 505a05323..8b273d74e 100644 --- a/fi/boot-installer/arm.xml +++ b/fi/boot-installer/arm.xml @@ -1,94 +1,101 @@ - + Booting from TFTP &boot-installer-intro-net.xml; - Booting from TFTP on NetWinder - + Booting from TFTP on Netwinder -NetWinders have two network interfaces: The 10Mbps NE2000-compatible -card is eth0 and the 100Mbps Tulip card is -eth1. - - - -You need NeTTrom 2.2.1 or later to boot the -installation system. NeTTrom 2.3.3 is recommended: get these files -from -: - - - -nettrom-2.3-3.armv4l.rpm - - - +Netwinders have two network interfaces: A 10Mbps NE2000-compatible +card (which is generally referred to as eth0) and +a 100Mbps Tulip card. There may be problems loading the image via TFTP +using the 100Mbps card so it is recommended that you use the 10Mbps +interfaced (the one labeled with 10 Base-T). -nettrom-2.3.3.bin + + - - +You need NeTTrom 2.2.1 or later to boot the installation system, and +version 2.3.3 is recommended. Unfortunately, firmware files are currently +not available for download because of license issues. If this situation +changes, you may find new images at . -nettrom-2.3.3.bin.md5sum + + - - +When you boot your Netwinder you have to interrupt the boot process during the +countdown. This allows you to set a number of firmware settings needed in +order to boot the installer. First of all, start by loading the default +settings: - + + NeTTrom command-> load-defaults + -After rebooting and interrupting the boot process during the countdown, you -must first configure the network either with a static address: +Furthermore, you must configure the network, either with a static address: + NeTTrom command-> setenv netconfig_eth0 flash NeTTrom command-> setenv eth0_ip 192.168.0.10/24 where 24 is the number of set bits in the netmask, or a dynamic address: - NeTTrom command-> boot diskless + NeTTrom command-> setenv netconfig_eth0 dhcp You may also need to configure the route1 -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): +settings if the TFTP server is not on the local subnet. + +Following these settings, you have to specify the TFTP server and the +location of the image. You can then store your settings to flash. NeTTrom command-> setenv kerntftpserver 192.168.0.1 NeTTrom command-> setenv kerntftpfile boot.img NeTTrom command-> save-all - NeTTrom command-> setenv netconfig_eth0 flash + + +Now you have to tell the firmware that the TFTP image should be booted: + + NeTTrom command-> setenv kernconfig tftp NeTTrom command-> setenv rootdev /dev/ram - NeTTrom command-> setenv cmdappend root=/dev/ram -Only the last four of these interfere with normal disk booting, so it is -safe to issue save-all right before them, which will -store the network settings in case you need to boot from the network -again. - -If you want to use the serial console to install your NetWinder, you also -need the following setting: +If you use a serial console to install your Netwinder, you need to add the +following setting: NeTTrom command-> setenv cmdappend root=/dev/ram console=ttyS0,115200 -Use the printenv command to review your -environment settings. Finally, if your cmdappend -NeTTrom variable has the option, you must -remove it so the downloaded kernel can boot with its attached ramdisk. +Alternatively, for installations using a keyboard and monitor you have to +set: - - + + NeTTrom command-> setenv cmdappend root=/dev/ram + + +You can use the printenv command to review your +environment settings. After you have verified that the settings are +correct, you can load the image: + + + NeTTrom command-> boot + + +In case you run into any problems, a detailed +HOWTO is available. - Booting from TFTP on CATS + + + Booting from TFTP on CATS On CATS machines, use boot de0: or similar at the @@ -99,7 +106,6 @@ Cyclone prompt. - Booting from CD-ROM &boot-installer-intro-cd.xml; @@ -111,3 +117,103 @@ To boot a CD-ROM from the Cyclone console prompt, use the command + + + Booting from Firmware + +&boot-installer-intro-firmware.xml; + + Booting the NSLU2 + + +There are three ways how to put the installer firmware into flash: + + + + Using the NSLU2 web interface + + +Go to the administration section and choose the menu item +Upgrade. You can then browse your disk for the +installer image you have previously downloaded. Then press the +Start Upgrade button, confirm, wait for a few minutes +and confirm again. The system will then boot straight into the installer. + + + + + Via the network using Linux/Unix + + +You can use upslug2 from any Linux or Unix machine to +upgrade the machine via the network. This software is packaged for +Debian. + +First, you have to put your NSLU2 in upgrade mode: + + + + +Disconnect any disks and/or devices from the USB ports. + + + + +Power off the NSLU2 + + + + +Press and hold the reset button (accessible through the small hole on the +back just above the power input). + + + + +Press and release the power button to power on the NSLU2. + + + + +Wait for 10 seconds watching the ready/status LED. After 10 seconds it +will change from amber to red. Immediately release the reset button. + + + + +The NSLU2 ready/status LED will flash alternately red/green (there is a 1 +second delay before the first green). The NSLU2 is now in upgrade mode. + + + + +See the NSLU2-Linux +pages if you have problems with this. + +Once your NSLU2 is in upgrade mode, you can flash the new image: + + +sudo upslug2 -i di-nslu2.bin + + +Note that the tool also shows the MAC address of your NSLU2, which may come +in handy to configure your DHCP server. After the whole image has been +written and verified, the system will automatically reboot. Make sure you +connect your USB disk again now, otherwise the installer won't be able to +find it. + + + + + Via the network using Windows + + +There is a +tool for Windows to upgrade the firmware via the network. + + + + + -- cgit v1.2.3