diff options
Diffstat (limited to 'nl/boot-installer')
-rw-r--r-- | nl/boot-installer/arm.xml | 206 | ||||
-rw-r--r-- | nl/boot-installer/boot-installer.xml | 6 | ||||
-rw-r--r-- | nl/boot-installer/intro-firmware.xml | 18 | ||||
-rw-r--r-- | nl/boot-installer/mipsel.xml | 96 |
4 files changed, 267 insertions, 59 deletions
diff --git a/nl/boot-installer/arm.xml b/nl/boot-installer/arm.xml index 505a05323..8b273d74e 100644 --- a/nl/boot-installer/arm.xml +++ b/nl/boot-installer/arm.xml @@ -1,94 +1,101 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 28672 untranslated --> +<!-- original version: 35328 untranslated --> <sect2 arch="arm" id="boot-tftp"><title>Booting from TFTP</title> &boot-installer-intro-net.xml; - <sect3 arch="arm"><title>Booting from TFTP on NetWinder</title> - + <sect3 arch="arm"><title>Booting from TFTP on Netwinder</title> <para> -NetWinders have two network interfaces: The 10Mbps NE2000-compatible -card is <filename>eth0</filename> and the 100Mbps Tulip card is -<filename>eth1</filename>. - -</para><note><para> - -You need NeTTrom 2.2.1 or later to boot the -installation system. NeTTrom 2.3.3 is recommended: get these files -from -<ulink url="ftp://ftp.netwinder.org/pub/netwinder/firmware/"></ulink>: -<itemizedlist> -<listitem><para> - -<filename>nettrom-2.3-3.armv4l.rpm</filename> - -</para></listitem> -<listitem><para> +Netwinders have two network interfaces: A 10Mbps NE2000-compatible +card (which is generally referred to as <literal>eth0</literal>) 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 <literal>10 Base-T</literal>). -<filename>nettrom-2.3.3.bin</filename> +</para> +<note><para> -</para></listitem> -<listitem><para> +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 <ulink url="http//www.netwinder.org/"></ulink>. -<filename>nettrom-2.3.3.bin.md5sum</filename> +</para></note> +<para> -</para></listitem> -</itemizedlist> +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: -</para></note><para> +<informalexample><screen> + NeTTrom command-> load-defaults +</screen></informalexample> -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: <informalexample><screen> + NeTTrom command-> setenv netconfig_eth0 flash NeTTrom command-> setenv eth0_ip 192.168.0.10/24 </screen></informalexample> where 24 is the number of set bits in the netmask, or a dynamic address: <informalexample><screen> - NeTTrom command-> boot diskless + NeTTrom command-> setenv netconfig_eth0 dhcp </screen></informalexample> You may also need to configure the <userinput>route1</userinput> -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. <informalexample><screen> NeTTrom command-> setenv kerntftpserver 192.168.0.1 NeTTrom command-> setenv kerntftpfile boot.img NeTTrom command-> save-all - NeTTrom command-> setenv netconfig_eth0 flash +</screen></informalexample> + +Now you have to tell the firmware that the TFTP image should be booted: + +<informalexample><screen> NeTTrom command-> setenv kernconfig tftp NeTTrom command-> setenv rootdev /dev/ram - NeTTrom command-> setenv cmdappend root=/dev/ram </screen></informalexample> -Only the last four of these interfere with normal disk booting, so it is -safe to issue <command>save-all</command> 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: <informalexample><screen> NeTTrom command-> setenv cmdappend root=/dev/ram console=ttyS0,115200 </screen></informalexample> -Use the <command>printenv</command> command to review your -environment settings. Finally, if your <envar>cmdappend</envar> -NeTTrom variable has the <option>noinitrd</option> 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: -</para> - </sect3> +<informalexample><screen> + NeTTrom command-> setenv cmdappend root=/dev/ram +</screen></informalexample> + +You can use the <command>printenv</command> command to review your +environment settings. After you have verified that the settings are +correct, you can load the image: + +<informalexample><screen> + NeTTrom command-> boot +</screen></informalexample> + +In case you run into any problems, a <ulink +url="http://www.netwinder.org/howto/Firmware-HOWTO.html">detailed +HOWTO</ulink> is available. - <sect3 arch="arm"><title>Booting from TFTP on CATS</title> +</para> + </sect3> + <sect3 arch="arm"><title>Booting from TFTP on CATS</title> <para> On CATS machines, use <command>boot de0:</command> or similar at the @@ -99,7 +106,6 @@ Cyclone prompt. </sect2> - <sect2 arch="arm"><title>Booting from CD-ROM</title> &boot-installer-intro-cd.xml; @@ -111,3 +117,103 @@ To boot a CD-ROM from the Cyclone console prompt, use the command </para> </sect2> + + + <sect2 arch="arm" id="boot-firmware"><title>Booting from Firmware</title> + +&boot-installer-intro-firmware.xml; + + <sect3 arch="arm" id="boot-firmware-nslu2"><title>Booting the NSLU2</title> +<para> + +There are three ways how to put the installer firmware into flash: + +</para> + + <sect4 arch="arm"><title>Using the NSLU2 web interface</title> +<para> + +Go to the administration section and choose the menu item +<literal>Upgrade</literal>. You can then browse your disk for the +installer image you have previously downloaded. Then press the +<literal>Start Upgrade</literal> button, confirm, wait for a few minutes +and confirm again. The system will then boot straight into the installer. + +</para> + </sect4> + + <sect4 arch="arm"><title>Via the network using Linux/Unix</title> +<para> + +You can use <command>upslug2</command> 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: + +<orderedlist> +<listitem><para> + +Disconnect any disks and/or devices from the USB ports. + +</para></listitem> +<listitem><para> + +Power off the NSLU2 + +</para></listitem> +<listitem><para> + +Press and hold the reset button (accessible through the small hole on the +back just above the power input). + +</para></listitem> +<listitem><para> + +Press and release the power button to power on the NSLU2. + +</para></listitem> +<listitem><para> + +Wait for 10 seconds watching the ready/status LED. After 10 seconds it +will change from amber to red. Immediately release the reset button. + +</para></listitem> +<listitem><para> + +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. + +</para></listitem> +</orderedlist> + +See the <ulink +url="http://www.nslu2-linux.org/wiki/OpenSlug/UsingTheBinary">NSLU2-Linux +pages</ulink> if you have problems with this. + +Once your NSLU2 is in upgrade mode, you can flash the new image: + +<informalexample><screen> +sudo upslug2 -i di-nslu2.bin +</screen></informalexample> + +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. + +</para> + </sect4> + + <sect4 arch="arm"><title>Via the network using Windows</title> +<para> + +There is <ulink +url="http://www.everbesthk.com/8-download/sercomm/firmware/all_router_utility.zip">a +tool</ulink> for Windows to upgrade the firmware via the network. + +</para> + </sect4> + </sect3> + </sect2> diff --git a/nl/boot-installer/boot-installer.xml b/nl/boot-installer/boot-installer.xml index ab8ab9784..0a5a08799 100644 --- a/nl/boot-installer/boot-installer.xml +++ b/nl/boot-installer/boot-installer.xml @@ -1,11 +1,11 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 24701 untranslated --> +<!-- original version: 35310 untranslated --> <chapter id="boot-installer"><title>Booting the Installation System</title> <!-- Include only archs that are documented to avoid build-errors --> <!-- The arch="..." condition can be deleted when al archs are present --> - <sect1 arch="alpha;arm;i386;ia64;m68k;mips;s390;powerpc;sparc"> + <sect1 arch="alpha;arm;i386;ia64;m68k;mips;mipsel;s390;powerpc;sparc"> <title>Booting the Installer on &arch-title;</title> <!-- This info is so architecture dependent, that I have turned the --> @@ -19,7 +19,7 @@ &boot-installer-ia64.xml; &boot-installer-m68k.xml; &boot-installer-mips.xml; -<!-- &boot-installer-mipsel.xml; --> +&boot-installer-mipsel.xml; &boot-installer-s390.xml; &boot-installer-powerpc.xml; &boot-installer-sparc.xml; diff --git a/nl/boot-installer/intro-firmware.xml b/nl/boot-installer/intro-firmware.xml new file mode 100644 index 000000000..fe869608e --- /dev/null +++ b/nl/boot-installer/intro-firmware.xml @@ -0,0 +1,18 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 35309 untranslated --> + +<para> + +There is an increasing number of consumer devices that directly boot from a +flash chip on the device. The installer can be written to flash so it will +automatically start when you reboot your machines. + +</para><note><para> + +In many cases, changing the firmware of an embedded device voids your +warranty. Sometimes you are also not able to recover your device if there +are problems during the flashing process. Therefore, please take care and +follow the steps precisely. + +</para></note> + diff --git a/nl/boot-installer/mipsel.xml b/nl/boot-installer/mipsel.xml index 270390c53..a059ba7ce 100644 --- a/nl/boot-installer/mipsel.xml +++ b/nl/boot-installer/mipsel.xml @@ -1,12 +1,96 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 24701 untranslated --> +<!-- original version: 35328 untranslated --> - <sect2 arch="mipsel"> - <title></title> + <sect2 arch="mipsel" id="boot-tftp"><title>Booting with TFTP</title> + + <sect3> + <title>Cobalt TFTP Booting</title> <para> -<!-- Placeholder document; please write and include in - boot-installer.xml and build/templates/docstruct.ent --> +Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to +install an NFS server and put the installer files in +<filename>/nfsroot</filename>. When you boot your Cobalt, you have to +press the left and the right cursor buttons at the same time and the +machine will boot via the network from NFS. It will then display several +options on the display. There are the following two installation methods: + +<itemizedlist> +<listitem><para> + +Via SSH (default): In this case, the installer will configure the network +via DHCP and start an SSH server. It will then display a random password +and other login information (such as the IP address) on the Cobalt LCD. +When you connect to the machine with an SSH client you can start with +the installation. + +</para></listitem> +<listitem><para> + +Via serial console: Using a null modem cable, you can connect to the serial +port of your Cobalt machine (using 115200 bps) and perform the installation +this way. This option is not available on Qube 2700 (Qube1) machines since +they have no serial port. + +</para></listitem> +</itemizedlist> </para> - </sect2> + </sect3> + + <sect3> +<!-- Note to translators: this is the same section as in mips.xml --> + <title>Broadcom BCM91250A TFTP Booting</title> +<para> + +On the Broadcom BCM91250A evaluation board, you have to load the SiByl boot +loader via TFTP which will then load and start the Debian installer. In +most cases, you will first obtain an IP address via DHCP but it is also +possible to configure a static address. In order to use DHCP, you can +enter the following command on the CFE prompt: + +<informalexample><screen> +ifconfig eth0 -auto +</screen></informalexample> + +Once you have obtained an IP address, you can load SiByl with the following +command: + +<informalexample><screen> +boot 192.168.1.1:/boot/sibyl +</screen></informalexample> + +You need to substitute the IP address listed in this example with either +the name or the IP address of your TFTP server. Once you issue this +command, the installer will be loaded automatically. + +</para> +</sect3> + </sect2> + + <sect2 arch="mipsel"><title>Boot Parameters</title> + + <sect3> + <title>Cobalt TFTP Booting</title> +<para> + +You cannot pass any boot parameters directly. Instead, you have to edit +the <filename>/nfsroot/default.colo</filename> file on the NFS server and +add your parameters to the <replaceable>args</replaceable> variable. + +</para> + </sect3> + + <sect3> +<!-- Note to translators: this is the same section as in mips.xml --> + <title>Broadcom BCM91250A TFTP Booting</title> +<para> + +You cannot pass any boot parameters directly from the CFE prompt. Instead, +you have to edit the <filename>/boot/sibyl.conf</filename> file on the TFTP +server and add your parameters to the <replaceable>extra_args</replaceable> +variable. + +</para> + </sect3> + + </sect2> |