From 99c0ce2062388ace5ecd6088c272f709dfb0c6fe Mon Sep 17 00:00:00 2001 From: Frans Pop Date: Sun, 26 Jul 2009 01:05:09 +0000 Subject: Dutch translation update for untranslated files --- nl/boot-installer/accessibility.xml | 12 +- nl/boot-installer/arm.xml | 218 +++++++++++++++++++----------------- nl/boot-installer/mipsel.xml | 5 +- nl/boot-installer/parameters.xml | 16 ++- nl/boot-installer/x86.xml | 4 +- 5 files changed, 140 insertions(+), 115 deletions(-) (limited to 'nl/boot-installer') diff --git a/nl/boot-installer/accessibility.xml b/nl/boot-installer/accessibility.xml index 34cac97a1..7e8c4f46f 100644 --- a/nl/boot-installer/accessibility.xml +++ b/nl/boot-installer/accessibility.xml @@ -1,5 +1,5 @@ - + Accessibility @@ -28,7 +28,9 @@ of the installer will then be automatically selected, and support for the braille display will be automatically installed on the target system. You can thus just press &enterkey; at the boot menu. Once brltty is started, you can choose a braille -table by entering the preference menu. +table by entering the preference menu. Documentation on key +bindings for braille devices is available on the brltty website. @@ -49,7 +51,9 @@ serial port the display is connected to, ttyS0 is the default. table is the name of the braille table to be used (see the table code list); the English table is the default. Note that the table can -be changed later by entering the preference menu. +be changed later by entering the preference menu. Documentation on key +bindings for braille devices is available on the brltty website. @@ -62,6 +66,8 @@ Support for hardware speech synthesis devices is available only alongside support for graphical installer. You thus need to select the Graphical install entry in the boot menu. + + Hardware speech synthesis devices cannot be automatically detected. You thus need to append the speakup.synth=driver diff --git a/nl/boot-installer/arm.xml b/nl/boot-installer/arm.xml index 5e17ac9ac..81de776e2 100644 --- a/nl/boot-installer/arm.xml +++ b/nl/boot-installer/arm.xml @@ -1,108 +1,10 @@ - + Booting from TFTP &boot-installer-intro-net.xml; - Booting from TFTP on Netwinder - - -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 -interface (the one labeled with 10 Base-T). - - - - -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 . - - - - -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 - - -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-> setenv netconfig_eth0 dhcp - - -You may also need to configure the route1 -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 - - -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 - - -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 - - -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 - - -On CATS machines, use boot de0: or similar at the -Cyclone prompt. - - - @@ -110,12 +12,6 @@ Cyclone prompt. &boot-installer-intro-cd.xml; - - -To boot a CD-ROM from the Cyclone console prompt, use the command -boot cd0:cats.bin - - @@ -216,4 +112,116 @@ tool for Windows to upgrade the firmware via the network. + + + Booting the SS4000-E + + +Due to limitations in the SS4000-E firmware, it unfortunately is not +possible to boot the installer without the use of a serial port at +this time. To boot the installer, you will need a serial nullmodem +cable; a computer with a serial port + + +A USB serial converter will also work. + + +; and a ribbon cable with a male DB9 connector at one end, +and a 10-pin .1" IDC header at the other + + +This cable is often found in older desktop machines with builtin 9-pin +serial ports. + + +. + + + +To boot the SS4000-E, first load the Debian-provided firmware image +(ss4000e.pkg) through the SS4000-E's web interface (go to +administration, then to firmware, and +upload the image). Next, +use your serial nullmodem cable and the ribbon cable to connect to the +serial port of the SS4000-E, and reboot the machine. You need to use a +serial terminal application to communicate with the machine; a good +option on a Debian GNU/Linux is to use the cu +program, in the package of the same name. Assuming the serial port on +your computer is to be found on /dev/ttyS0, use the +following command line: + + + + +cu -lttyS0 -s115200 + + + + +If using Windows, you may want to consider using the program +hyperterminal. Use a baud rate of 115200, +8 bits word length, no stop bits, and one parity bit. + + + +When the machine boots, you will see the following line of output: + + + + +No network interfaces found + +EM-7210 ver.T04 2005-12-12 (For ver.AA) +== Executing boot script in 1.000 seconds - enter ^C to abort + + + + +At this point, hit Control-C to interrupt the boot +loader + + +Note that you have only one second to do so; if you miss this window, +just powercycle the machine and try again. + + +. This will give you the RedBoot prompt. Enter the +following command: + + + + +fconfig boot_script_data + + + + +RedBoot is now waiting for you to enter the boot script. Make sure to +exactly enter the following script: + + + + +fis load ramdisk.gz +fis load zImage +exec -c "console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000" -r 0x01800000 + + + + +Finish the script with an empty line, and enter y at the +prompt to update the non-volatile configuration. Finally, use +reset to restart the system, and allow it to boot normally. +The installer should now come up as normal. You can either install Debian +through the serial port, or use an SSH client to connect through SSH. + + + +Note that it is not necessary to update the boot script after the +installation. The system will be configured to take the root device from +system configuration, rather than from the kernel command line. It will +not do any harm to do so anyway, however. + + + diff --git a/nl/boot-installer/mipsel.xml b/nl/boot-installer/mipsel.xml index 69245e3fd..4249e5b4c 100644 --- a/nl/boot-installer/mipsel.xml +++ b/nl/boot-installer/mipsel.xml @@ -1,5 +1,5 @@ - + Booting with TFTP @@ -28,8 +28,7 @@ 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. +this way. diff --git a/nl/boot-installer/parameters.xml b/nl/boot-installer/parameters.xml index 0f9543b58..9aeaff7a9 100644 --- a/nl/boot-installer/parameters.xml +++ b/nl/boot-installer/parameters.xml @@ -1,5 +1,5 @@ - + Boot Parameters @@ -53,7 +53,19 @@ to pass the console=device argument to the kernel, where device is your serial device, which is usually something like -ttyS0. +ttyS0 + + +In order to ensure the terminal type used by the installer matches your +terminal emulator, the parameter +TERM=type can be added. +Note that the installer only supports the following terminal types: +linux, bterm, ansi, +vt102 and dumb. The default for +serial console in &d-i; is vt102. + + +. diff --git a/nl/boot-installer/x86.xml b/nl/boot-installer/x86.xml index 5bcd4203a..f6f04e18a 100644 --- a/nl/boot-installer/x86.xml +++ b/nl/boot-installer/x86.xml @@ -1,5 +1,5 @@ - + Booting from a CD-ROM @@ -154,7 +154,7 @@ drive unchanged during the install, you can download the hd-media/initrd.gz file and its kernel, as well as copy a CD (or DVD) iso to the drive (make sure the file is named ending in .iso). The installer can then boot from the drive -and install from the CD image, without needing the network. +and install from the CD/DVD image, without needing the network. -- cgit v1.2.3