Browsing Spanish translation

82.

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: <informalexample><screen>
NeTTrom command-&gt; load-defaults
</screen></informalexample> Furthermore, you must configure the network, either with a static address: <informalexample><screen>
NeTTrom command-&gt; setenv netconfig_eth0 flash
NeTTrom command-&gt; 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-&gt; 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. 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-&gt; setenv kerntftpserver 192.168.0.1
NeTTrom command-&gt; setenv kerntftpfile boot.img
NeTTrom command-&gt; save-all
</screen></informalexample> Now you have to tell the firmware that the TFTP image should be booted: <informalexample><screen>
NeTTrom command-&gt; setenv kernconfig tftp
NeTTrom command-&gt; setenv rootdev /dev/ram
</screen></informalexample> If you use a serial console to install your Netwinder, you need to add the following setting: <informalexample><screen>
NeTTrom command-&gt; setenv cmdappend root=/dev/ram console=ttyS0,115200
</screen></informalexample> Alternatively, for installations using a keyboard and monitor you have to set: <informalexample><screen>
NeTTrom command-&gt; 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-&gt; 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.

99.

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.

139.

Choosing the <quote>Help</quote> entry will result in the first help screen being displayed which gives an overview of all available help screens. Note that it is not possible to return to the boot menu after the help screens have been displayed. However, the F3 and F4 help screens list commands that are equivalent to the boot methods listed in the menu. All help screens have a boot prompt at which the boot command can be typed: <informalexample><screen>
Press F1 for the help index, or ENTER to boot:
</screen></informalexample> At this boot prompt you can either just press &enterkey; to boot the installer with default options or enter a specific boot command and, optionally, boot parameters. A number of boot parameters which might be useful can be found on the various help screens. If you do add any parameters to the boot command line, be sure to first type the boot method (the default is <userinput>install</userinput>) and a space before the first parameter (e.g., <userinput>install fb=false</userinput>).

142.

To bypass the graphical boot screen you can either blindly press &escapekey; to get a text boot prompt, or (equally blindly) press <quote>H</quote> followed by &enterkey; to select the <quote>Help</quote> option described above. After that your keystrokes should be echoed at the prompt. To prevent the installer from using the framebuffer for the rest of the installation, you will also want to add <userinput>fb=false</userinput> to the boot prompt, as described in the help text.

182.

A suitable TFTP entry for network booting an IA-64 system looks something like this: <informalexample><screen>
host mcmuffin {
hardware ethernet 00:30:6e:1e:0e:83;
fixed-address 10.0.0.21;
filename "debian-installer/ia64/elilo.efi";
}
</screen></informalexample> Note that the goal is to get <command>elilo.efi</command> running on the client.

222.

Macs require the <command>Penguin</command> bootloader, which can be downloaded from <ulink url="&url-m68k-mac;">the Linux/mac68k sourceforge.net project</ulink>. If you do not have the tools to handle a <command>Stuffit</command> archive, you can put it on a MacOS-formatted floppy using a second GNU/Linux machine of any architecture and the <command>hmount</command>, <command>hcopy</command>, and <command>humount</command> tools from the <classname>hfsutils</classname> suite.

239.

After entering the command monitor use <informalexample><screen>
bootp():
</screen></informalexample> on SGI machines to boot linux and to begin installation of the Debian Software. In order to make this work you may have to unset the <envar>netaddr</envar> environment variable. Type <informalexample><screen>
unsetenv netaddr
</screen></informalexample> in the command monitor to do this.

241.

On the Broadcom BCM91250A and BCM91480B evaluation boards, 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.

248.

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:

256.

On S/390 you can append boot parameters in the parm file. This file can either be in ASCII or EBCDIC format. A sample parm file <filename>parmfile.debian</filename> is provided with the installation images.