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/appendix/preseed.xml | 58 ++++++++-- fi/boot-installer/arm.xml | 206 ++++++++++++++++++++++++++--------- fi/boot-installer/boot-installer.xml | 6 +- fi/boot-installer/intro-firmware.xml | 18 +++ fi/boot-installer/mipsel.xml | 96 +++++++++++++++- fi/hardware/hardware-supported.xml | 18 +-- fi/hardware/network-cards.xml | 4 +- fi/hardware/supported/arm.xml | 30 ++--- fi/hardware/supported/mips.xml | 4 +- fi/hardware/supported/mipsel.xml | 14 ++- fi/install-methods/download/arm.xml | 23 +++- fi/preparing/needed-info.xml | 7 +- fi/using-d-i/components.xml | 3 +- fi/using-d-i/modules/baseconfig.xml | 17 --- 14 files changed, 370 insertions(+), 134 deletions(-) create mode 100644 fi/boot-installer/intro-firmware.xml delete mode 100644 fi/using-d-i/modules/baseconfig.xml (limited to 'fi') diff --git a/fi/appendix/preseed.xml b/fi/appendix/preseed.xml index 4b3bc8def..520dfe9bf 100644 --- a/fi/appendix/preseed.xml +++ b/fi/appendix/preseed.xml @@ -1,5 +1,5 @@ - + - + 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. + + + + + diff --git a/fi/boot-installer/boot-installer.xml b/fi/boot-installer/boot-installer.xml index ab8ab9784..0a5a08799 100644 --- a/fi/boot-installer/boot-installer.xml +++ b/fi/boot-installer/boot-installer.xml @@ -1,11 +1,11 @@ - + Booting the Installation System - + Booting the Installer on &arch-title; @@ -19,7 +19,7 @@ &boot-installer-ia64.xml; &boot-installer-m68k.xml; &boot-installer-mips.xml; - +&boot-installer-mipsel.xml; &boot-installer-s390.xml; &boot-installer-powerpc.xml; &boot-installer-sparc.xml; diff --git a/fi/boot-installer/intro-firmware.xml b/fi/boot-installer/intro-firmware.xml new file mode 100644 index 000000000..fe869608e --- /dev/null +++ b/fi/boot-installer/intro-firmware.xml @@ -0,0 +1,18 @@ + + + + + +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. + + + +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. + + + diff --git a/fi/boot-installer/mipsel.xml b/fi/boot-installer/mipsel.xml index 270390c53..a059ba7ce 100644 --- a/fi/boot-installer/mipsel.xml +++ b/fi/boot-installer/mipsel.xml @@ -1,12 +1,96 @@ - + - - + Booting with TFTP + + + Cobalt TFTP Booting - +Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to +install an NFS server and put the installer files in +/nfsroot. 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: + + + + +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. + + + + +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. + + + - + + + + + Broadcom BCM91250A TFTP Booting + + +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: + + +ifconfig eth0 -auto + + +Once you have obtained an IP address, you can load SiByl with the following +command: + + +boot 192.168.1.1:/boot/sibyl + + +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. + + + + + + Boot Parameters + + + Cobalt TFTP Booting + + +You cannot pass any boot parameters directly. Instead, you have to edit +the /nfsroot/default.colo file on the NFS server and +add your parameters to the args variable. + + + + + + + Broadcom BCM91250A TFTP Booting + + +You cannot pass any boot parameters directly from the CFE prompt. Instead, +you have to edit the /boot/sibyl.conf file on the TFTP +server and add your parameters to the extra_args +variable. + + + + + diff --git a/fi/hardware/hardware-supported.xml b/fi/hardware/hardware-supported.xml index 48a47becb..b0216fdea 100644 --- a/fi/hardware/hardware-supported.xml +++ b/fi/hardware/hardware-supported.xml @@ -1,5 +1,5 @@ - + Supported Hardware @@ -91,16 +91,16 @@ variations of each architecture known as flavors. - ARM and StrongARM - arm - + ARM and StrongARM + arm + Netwinder and CATS netwinder - riscpc - - shark + Linksys NSLU2 + nslu2 - lart + RiscPC and Riscstation + riscpc @@ -193,7 +193,7 @@ encounter a few bugs. Use our Bug Tracking System to report any problems; make sure to mention the fact that the bug is on the &arch-title; platform. It can be necessary to use the -debian-&architecture; mailing list +debian-&arch-listname; mailing list as well. diff --git a/fi/hardware/network-cards.xml b/fi/hardware/network-cards.xml index d296a821e..f24a7f481 100644 --- a/fi/hardware/network-cards.xml +++ b/fi/hardware/network-cards.xml @@ -1,5 +1,5 @@ - + Network Connectivity Hardware @@ -157,7 +157,7 @@ OSA-Express in QDIO mode, HiperSockets and Guest-LANs The following network interface cards are supported directly by the -boot disks on NetWinder and CATS machines: +boot disks on Netwinder and CATS machines: diff --git a/fi/hardware/supported/arm.xml b/fi/hardware/supported/arm.xml index 9ae4bef4e..e15f41c20 100644 --- a/fi/hardware/supported/arm.xml +++ b/fi/hardware/supported/arm.xml @@ -1,5 +1,5 @@ - + CPU, Main Boards, and Video Support @@ -15,22 +15,24 @@ a number of the most common systems. The Debian userland however may be used by Most ARM CPUs may be run in either endian mode (big or little). However, -almost every current system implementation uses little-endian mode. +the majority of current system implementation uses little-endian mode. Debian currently only supports little-endian ARM systems. -The commonly supported systems are +The supported systems are: + Netwinder This is actually the name for the group of machines -based upon the StrongARM 110 CPU and Intel 21285 Northbridge. It +based upon the StrongARM 110 CPU and Intel 21285 Northbridge (also known +as Footbridge). It comprises of machines like: Netwinder (possibly one of the most common ARM boxes), CATS (also known as the EB110ATX), EBSA 285 and Compaq personal server (cps, aka skiff). @@ -39,13 +41,13 @@ personal server (cps, aka skiff). -Bast +NSLU2 -This is a modern ARM 920 board with a 266MHz Samsung -processor. It has integrated IDE, USB, Serial, Parallel, audio, video, -flash and two ethernet ports. This system has a good bootloader which -is also found on the CATS and Riscstation systems. +The Linksys NSLU2 (Network Storage Link for USB 2.0 Disk Drives) is a small +device which allows you to easily provide storage via the network. It +comes with an Ethernet connection and two USB ports to which hard drives +can be connected. @@ -79,16 +81,6 @@ simple bootloader. - -LART - - -This is a modular open hardware platform intended to be built -by enthusiasts. To be useful to install Debian it requires its KSB -expansion board. - - - diff --git a/fi/hardware/supported/mips.xml b/fi/hardware/supported/mips.xml index 7ea1a2bf7..9dd0e3716 100644 --- a/fi/hardware/supported/mips.xml +++ b/fi/hardware/supported/mips.xml @@ -1,5 +1,5 @@ - + CPU, Main Boards, and Video Support @@ -28,7 +28,7 @@ at the Linux-MIPS homepage. In the following, only the systems supported by the Debian installer will be covered. If you are looking for support for other subarchitectures, please contact the -debian-&architecture; mailing list. +debian-&arch-listname; mailing list. diff --git a/fi/hardware/supported/mipsel.xml b/fi/hardware/supported/mipsel.xml index 63d5a5bc1..823f18eb9 100644 --- a/fi/hardware/supported/mipsel.xml +++ b/fi/hardware/supported/mipsel.xml @@ -1,5 +1,5 @@ - + CPU, Main Boards, and Video Support @@ -15,8 +15,8 @@ DECstation: various models of the DECstation are supported. -Cobalt Microserver: only MIPS based Cobalt machines are covered here. -This included the Cobalt Qube, RaQ, Qube2 and RaQ2, and the Gateway +Cobalt Microserver: only MIPS based Cobalt machines are covered here. This +includes the Cobalt Qube 2700 (Qube1), RaQ, Qube2 and RaQ2, and the Gateway Microserver. @@ -33,7 +33,7 @@ at the Linux-MIPS homepage. In the following, only the systems supported by the Debian installer will be covered. If you are looking for support for other subarchitectures, please contact the -debian-&architecture; mailing list. +debian-&arch-listname; mailing list. @@ -97,8 +97,10 @@ The Debian installation system works on the following machines: -All Cobalt machines are supported which have a serial console (which is -needed for the installation). +All Cobalt machines are supported. In the past, only machines with a +serial console were supported (that is, all machines except for the Qube +2700, aka Qube1). However, installations are now also possible through +SSH. diff --git a/fi/install-methods/download/arm.xml b/fi/install-methods/download/arm.xml index b21ad3ef1..d5c5b1014 100644 --- a/fi/install-methods/download/arm.xml +++ b/fi/install-methods/download/arm.xml @@ -1,5 +1,5 @@ - + @@ -16,10 +16,10 @@ Download this file onto the RISC OS machine, copy the - NetWinder Installation Files + Netwinder Installation Files -The easiest way to boot a NetWinder is over the network, using the +The easiest way to boot a Netwinder is over the network, using the supplied TFTP image &netwinder-boot-img;. @@ -29,9 +29,20 @@ supplied TFTP image &netwinder-boot-img;. CATS Installation Files -The only supported boot method for CATS is to use the combined image -&cats-boot-img;. This can be loaded from any device accessible to the -Cyclone bootloader. +CATS can be booted either via the network or from CD-ROM. The kernel and +initrd can be obtained from &cats-boot-img;. + + + NSLU2 Installation Files + + +A firmware image is provided for the Linksys NSLU2 which will automatically +boot debian-installer. This firmware image can be +obtained from &nslu2-firmware-img;. + + + + diff --git a/fi/preparing/needed-info.xml b/fi/preparing/needed-info.xml index 4a2e392a0..042a13c15 100644 --- a/fi/preparing/needed-info.xml +++ b/fi/preparing/needed-info.xml @@ -1,5 +1,5 @@ - + Information You Will Need @@ -214,9 +214,12 @@ networking and e-mail. How many you have. Their order on the system. - + Whether IDE or SCSI (most computers are IDE). + + Whether IDE or SCSI (most m68k computers are SCSI). + Available free space. Partitions. diff --git a/fi/using-d-i/components.xml b/fi/using-d-i/components.xml index e619cdcdc..2d3228e49 100644 --- a/fi/using-d-i/components.xml +++ b/fi/using-d-i/components.xml @@ -1,5 +1,5 @@ - + Using Individual Components @@ -182,6 +182,5 @@ user in case something goes wrong. &module-cdrom-checker.xml; &module-shell.xml; &module-network-console.xml; -&module-baseconfig.xml; diff --git a/fi/using-d-i/modules/baseconfig.xml b/fi/using-d-i/modules/baseconfig.xml deleted file mode 100644 index a189aa11d..000000000 --- a/fi/using-d-i/modules/baseconfig.xml +++ /dev/null @@ -1,17 +0,0 @@ - - - - - Running <command>base-config</command> From Within &d-i; - - - -It is possible to configure the base system within the first stage -installer (before rebooting from the hard drive), by running -base-config in a chroot -environment. This is mainly useful for testing the installer and -should normally be avoided. - - - - -- cgit v1.2.3