diff options
author | Joey Hess <joeyh@debian.org> | 2005-10-07 19:51:38 +0000 |
---|---|---|
committer | Joey Hess <joeyh@debian.org> | 2005-10-07 19:51:38 +0000 |
commit | 1ea73eea5ecc6a8ed901316049259aee737ee554 (patch) | |
tree | 03a077f0b1b1548f3c806bd1c5795964fba0fb52 /ca/preparing/bios-setup | |
download | installation-guide-1ea73eea5ecc6a8ed901316049259aee737ee554.zip |
move manual to top-level directory, split out of debian-installer package
Diffstat (limited to 'ca/preparing/bios-setup')
-rw-r--r-- | ca/preparing/bios-setup/i386.xml | 330 | ||||
-rw-r--r-- | ca/preparing/bios-setup/m68k.xml | 23 | ||||
-rw-r--r-- | ca/preparing/bios-setup/powerpc.xml | 52 | ||||
-rw-r--r-- | ca/preparing/bios-setup/s390.xml | 106 | ||||
-rw-r--r-- | ca/preparing/bios-setup/sparc.xml | 103 |
5 files changed, 614 insertions, 0 deletions
diff --git a/ca/preparing/bios-setup/i386.xml b/ca/preparing/bios-setup/i386.xml new file mode 100644 index 000000000..dd0d4413b --- /dev/null +++ b/ca/preparing/bios-setup/i386.xml @@ -0,0 +1,330 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 --> + + + <sect2 arch="i386" id="bios-setup"><title>Invocant el Menú de configuració de la BIOS</title> + +<para> + +La BIOS proveeix les funcions bàsiques que es necessiten per arrencar la +vostra màquina per permetre al vostre sistema operatiu accedir al maquinari. +El vostre sistema probablement proveeix un menú de configuració que s'utilitza +per configurar la BIOS. Abans d'instal·lar, <emphasis>assegureu-vos</emphasis> +que la vostra BIOS està correctament configurada; no fer-ho pot portar a +fallades intermitents que incapacite per instal·lar Debian. + +</para><para> + +La resta d'aquesta secció s'ha agafat de +<ulink url="&url-pc-hw-faq;"></ulink>, responent a la pregunta, +«Com entre al menú de configuració del CMOS?». Si accediu al menú de +configuració de la BIOS (o «CMOS») depèn del programador del programari +de la BIOS: + +</para> + +<!-- From: burnesa@cat.com (Shaun Burnet) --> +<variablelist> + +<varlistentry> + <term>AMI BIOS</term> + <listitem><para> + +Tecla <keycap>Supr</keycap> al POST (prova d'autoverificació a l'arrencada) + +</para></listitem> +</varlistentry> + +<varlistentry> + <term>Award BIOS</term> + <listitem><para> + +Tecles +<keycombo> + <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Esc</keycap> +</keycombo>, o <keycap>Supr</keycap> al POST + +</para></listitem> +</varlistentry> + +<varlistentry><term>DTK BIOS</term> + <listitem><para> + +Tecla <keycap>Esc</keycap> al POST + +</para></listitem> +</varlistentry> + +<varlistentry><term>IBM PS/2 BIOS</term> + <listitem><para> + +Tecles +<keycombo> + <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Insert</keycap> +</keycombo> +després +<keycombo> + <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Supr</keycap> +</keycombo> + +</para></listitem> +</varlistentry> + +<varlistentry> + <term>Phoenix BIOS</term> + <listitem><para> +Tecles +<keycombo> + <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Esc</keycap> +</keycombo> +o +<keycombo> + <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>S</keycap> +</keycombo> +o +<keycap>F1</keycap> + +</para></listitem> +</varlistentry> +</variablelist> + +<para> + +Podeu trobar més informació de com activar altres rutines de BIOS a +<ulink url="&url-invoking-bios-info;"></ulink>. + +</para><para> + +Algunes màquines &arch-title; no tenen menú de configuració a la BIOS. +Aquestes necessiten d'un programa de configuració del CMOS. Si no teniu +el disc d'instal·lació i/o diagnòstics, podeu provar a utilitzar programari +de prova o programari gratuït. Proveu de buscar a +<ulink url="&url-simtel;"></ulink>. + +</para> + </sect2> + + <sect2 arch="i386" id="boot-dev-select"><title>Selecció del dispositiu d'arrencada</title> + +<para> + +Molts menús de configuració de les BIOS permeten seleccionar els dispositius +que s'utilitzaran per iniciar el sistema. Canvieu-ho per buscar un sistema +operatiu arrencable a <filename>A:</filename> (el primer disquet), +aleshores opcionalment el primer CD-ROM (possiblement amb el nom +<filename>D:</filename> o <filename>E:</filename>), i aleshores de +<filename>C:</filename> (el primer dur). Aquests paràmetres permeten +l'arrencada del disquet o CD-ROM, que són dos dels més comuns dispositius +d'arrencada per instal·lar Debian. + +</para><para> + +Si disposeu d'una controladora SCSI nova i disposeu d'un CD-ROM +connectat a ella, normalment podreu arrencar del CD-ROM. Tot el +que heu de fer és habilitar l'arrencada del CD-ROM a la BIOS de +la vostra controladora SCSI. + +</para><para> + +Altra opció freqüent és arrencar d'un dispositiu emmagatzemament USB +(també es diu llapis de memòria o clau USB). +Algunes BIOS poden arrencar directament d'un dispositiu USB, i d'altres no. +Podríeu necessitar configurar la vostra BIOS per que arrenqués des d'un +<quote>disc extraïble</quote> o bé d'un <quote>USB-ZIP</quote> per poder +arrencar del dispositiu USB. + +</para><para> + +Ací trobareu alguns detalls de com triar l'ordre d'arrencada. Recordeu +de canviar l'ordre d'arrencada després d'instal·lar Linux per poder +reiniciar el vostre ordinador des del disc dur. + +</para> + + <sect3 id="ctbooi"> + <title>Canviant l'ordre d'arrencada a ordinadors IDE</title> + +<orderedlist> +<listitem><para> + +Quan s'engegue el vostre ordinador, premeu les tecles per entrar a +la BIOS. Sovint, és la tecla <keycap>Supr</keycap>. Consulteu la +documentació del vostre maquinari per conèixer les tecles exactes. + +</para></listitem> +<listitem><para> + +Busqueu l'ordre d'arrencada a la vostra utilitat de configuració. El lloc +on es trobe depèn de la vostra BIOS, però heu de buscar un camp que te una +llista de discs. + +</para><para> + +Les opcions més comuns a maquines IDE són C, A, CD-ROM o A, C, CD-ROM. + +</para><para> + +C és el disc dur, i A és el disquet. + +</para></listitem> +<listitem><para> + +Canvieu l'ordre d'arrencada de manera que tingueu primer el +CD-ROM o el disquet. Normalment, les tecles <keycap>Re Pàg</keycap> o +<keycap>Av Pàg</keycap> van desplaçant-se per les opcions possibles. + +</para></listitem> +<listitem><para> + +Deseu els vostres canvis. Les instruccions a la pantalla us diran com +desar els canvis al vostre ordinador. + +</para></listitem> +</orderedlist> + </sect3> + + <sect3 id="ctboos"> + <title>Canviant l'ordre d'arrencada a màquines SCSI</title> +<para> + +<orderedlist> +<listitem><para> + +Quan el vostre ordinador comença, premeu les tecles per entrar a la +utilitat de configuració SCSI. + +</para><para> + +Podeu arrencar la utilitat de configuració SCSI desprès de comprovar la +memòria i veure el missatge de com arrencar la utilitat de la BIOS a l'arrencar +l'ordinador. + +</para><para> + +Les combinacions de tecles depenen de la utilitat. Sovint són +<keycombo><keycap>Ctrl</keycap><keycap>F2</keycap></keycombo>. +Consulteu la documentació del vostre maquinari per conèixer les +combinacions de tecles exactes. + +</para></listitem> +<listitem><para> + +Busqueu la utilitat per canviar l'ordre d'arrencada. + +</para></listitem> +<listitem><para> + +Configureu la utilitat de forma que el SCSI IDE del CD estigui al primer +lloc a la llista. + +</para></listitem> +<listitem><para> + +Deseu els canvis. Les instruccions a la pantalla us diran com +desar els canvis al vostre ordinador. Sovint es tracta de +<keycap>F10</keycap>. + +</para></listitem> +</orderedlist> + +</para> + </sect3> + </sect2> + + <sect2 arch="i386"> + <title>Paràmetres de la BIOS miscel·lànies</title> + + <sect3 id="cd-settings"><title>Paràmetres del CD-ROM</title> +<para> + +Algunes BIOS (com les BIOS Award) permeten fixar la velocitat del CD. +Eviteu-ho, i poseu la velocitat mínima. Si trobeu missatges d'error +<userinput>seek failed</userinput>, aquest podria ser el vostre problema. + +</para> + </sect3> + + <sect3><title>Memòria estesa vs. memòria expandida</title> +<para> + +Si el vostre sistema proveeix les dos, memòria estesa i +expandida, configureu-ho de manera que tingueu el màxim possible +d'estesa i el mínim possible d'expandida. Linux necessita +memòria estesa i no pot fer ús de memòria expandida. + +</para> + </sect3> + + <sect3><title>Protecció davant virus</title> +<para> + +Deshabiliteu qualsevol característica d'avís davant virus que pugui donar-vos +la vostra BIOS. Si teniu una placa base o altre maquinari especial, +assegureu-vos que s'ha deshabilitat o extraieu-la físicament mentre executeu +GNU/Linux. Aquestes no són compatibles amb GNU/Linux; és més, pels permisos del +sistema de fitxers i la memòria protegida del nucli de Linux, pràcticament no +es coneixen virus<footnote> +<para> + +Després de la instal·lació podeu activar la protecció del sector d'arrencada +si voleu. Açò no és cap mesura addicional de seguretat a Linux, però si +utilitzeu Windows, pot prevenir una catàstrofe. No hi ha necessitat de +utilitzar el Master Boot Record (MBR) desprès de configurar el gestor +d'arrencada. + +</para> +</footnote>. + +</para> + </sect3> + + <sect3><title>«Shadow RAM»</title> +<para> + +La vostra placa base pot facilitar <emphasis>shadow RAM</emphasis> o +memòria cau per la BIOS. Podeu veure els paràmetres per «Video BIOS Shadow», +«C800-CBFF Shadow», etc. <emphasis>Deshabiliteu</emphasis> tota la +«shadow RAM». La «shadow RAM» s'utilitza per accelerar l'accés a les ROM a +la vostra placa base i a algunes targes controladores. Linux no utilitza +questes ROM després d'arrencar ja que dona el seu programari de 32 bits en +lloc del programari de 16 bits de les ROM. Deshabilitar la «shadow RAM» +podria convertir-la en disponible per a programes com memòria normal. +Deixar activada la «shadow RAM» podria interferir amb l'accés que fa Linux +als dispositius físics. + +</para> + </sect3> + + <sect3><title>«Memory Hole»</title> +<para> + +Si la vostra BIOS us ofereix alguna cosa com «15–16 MB Memory Hole», +desactiveu-ho. Linux espera trobar memòria allí si té aquesta RAM. + +</para><para> + +Es coneix de una placa base Intel Endeavor, la que te una opció que +diu «LFB» o «Linear Frame Buffer». Te dos opcions: «Disabled» i +«1 Megabyte». Configureu-ho a «1 Megabyte». Quan l'opció està +deshabilitada, el disquet d'instal·lació no es llegeix correctament i el +sistema acaba fallant. En el moment d'escriure aquest document, no s'enten +que passa amb aquest dispositiu en particular — tan sols funciona amb +aquesta opció i no sense ella. + +</para> + </sect3> + +<!-- no other platforms other than x86 provide this sort of thing, AFAIK --> + + <sect3><title>Gestió avançada d'energia</title> +<para> + +Si la vostra placa base proveeix gestió avançada d'energia (APM), +configureu de forma que la gestió d'energia es controle mitjançant APM. +Deshabiliteu els modes «doze», «standby», «suspend», «nap», «sleep» i +deshabiliteu el temporitzador d'apagat del disc. Linux pot controlar +aquestos modes, i pot fer una millor gestió de l'energia que la BIOS. + +</para> + </sect3> + </sect2> diff --git a/ca/preparing/bios-setup/m68k.xml b/ca/preparing/bios-setup/m68k.xml new file mode 100644 index 000000000..e68cb35d7 --- /dev/null +++ b/ca/preparing/bios-setup/m68k.xml @@ -0,0 +1,23 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + + <sect2 arch="m68k" id="firmware-revs"> + <title>Firmware Revisions and Existing OS Setup</title> + +<para> + +&arch-title; machines are generally self-configuring and do not require +firmware configuration. However, you should make sure that you have +the appropriate ROM and system patches. On the Macintosh, MacOS +version >= 7.1 is recommended because version 7.0.1 contains a bug in +the video drivers preventing the boot loader from deactivating the +video interrupts, resulting in a boot hang. On the BVM VMEbus systems +you should make sure you are using BVMBug revision G or higher boot ROMs. +The BVMBug boot ROMs do not come as standard on the BVM systems but are +available from BVM on request free of charge. + +</para> + + </sect2> + diff --git a/ca/preparing/bios-setup/powerpc.xml b/ca/preparing/bios-setup/powerpc.xml new file mode 100644 index 000000000..2368a0853 --- /dev/null +++ b/ca/preparing/bios-setup/powerpc.xml @@ -0,0 +1,52 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + + <sect2 arch="powerpc" id="invoking-openfirmware"> + <title>Invoking OpenFirmware</title> +<para> + +There is normally no need to set up the BIOS (called OpenFirmware) on +&arch-title; systems. PReP and CHRP are equipped with OpenFirmware, +but unfortunately, the means you use to invoke it vary from +manufacturer to manufacturer. You'll have to consult the hardware +documentation which came with your machine. + +</para><para> + +On &arch-title; Macintoshes, you invoke OpenFirmware with +<keycombo><keycap>Command</keycap> <keycap>option</keycap> +<keycap>O</keycap> <keycap>F</keycap></keycombo> while booting. Generally it +will check for these keystrokes after the chime, but the exact timing +varies from model to model. See +<ulink url="&url-netbsd-powerpc-faq;"></ulink> for more hints. + +</para><para> + +The OpenFirmware prompt looks like this: + +<informalexample><screen> +ok +0 > +</screen></informalexample> + +Note that on older model &arch-title; Macs, the default and sometimes +hardwired I/O for OpenFirmware user interaction is through the serial +(modem) port. If you invoke OpenFirmware on one of these machines, you +will just see a black screen. In that case, a terminal program running +on another computer, connected to the modem port, is needed to +interact with OpenFirmware. + +</para><para> + +The OpenFirmware on OldWorld Beige G3 machines, OF versions 2.0f1 +and 2.4, is broken. These machines will most likely not be able to +boot from the hard drive unless the firmware is patched. A firmware +patch is included in the <application>System Disk 2.3.1</application> +utility, available from Apple at +<ulink url="ftp://ftp.apple.com/developer/macosxserver/utilities/SystemDisk2.3.1.smi.bin"></ulink>. +After unpacking the utility in MacOS, and launching it, select the +Save button to have the firmware patches installed to nvram. + +</para> + </sect2> diff --git a/ca/preparing/bios-setup/s390.xml b/ca/preparing/bios-setup/s390.xml new file mode 100644 index 000000000..b2ed18855 --- /dev/null +++ b/ca/preparing/bios-setup/s390.xml @@ -0,0 +1,106 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + + <sect2 arch="s390"><title>BIOS Setup</title> +<para> + +In order to install &debian; on a &arch-title; or zSeries +machine you have first boot a kernel into the system. The boot +mechanism of this platform is inherently different to other ones, +especially from PC-like systems: there are no floppy devices available +at all. You will notice another big difference while you work with +this platform: most (if not all) of the time you will work remote, +with the help of some client session software like telnet, or a +browser. This is due to that special system architecture where the +3215/3270 console is line-based instead of character-based. + +</para><para> + +Linux on this platform runs either natively on the bare machine, in a +so-called LPAR (Logical Partition) or in a virtual machine supplied by +the VM system. You can use a boot tape on all of those systems; you +may use some other boot media, too, but those may not be generally +available. For example, you can use the virtual card reader of a +virtual machine, or boot from the HMC (Hardware Management Console) of +an LPAR if the HMC and this option is available for you. + +</para><para> + +Before you actually perform an installation, you have to go over some +design and preparation steps. IBM has made documentation available +about the whole process, e.g. how to prepare an installation medium +and how actually boot from that medium. Duplicating that information +here is neither possible nor necessary. However, we will describe +here which kind of Debian-specific data is needed and where do you +find them. Based on both sources of information you have to prepare +your machine and the installation medium and to perform a boot from +it. When you see the welcome message in your client session join this +document again for the Debian-specific installation steps. + +</para> + </sect2> + + <sect2 arch="s390"> + <title>Native and LPAR installations</title> +<para> + +Please refer to chapter 5 of the +<ulink url="http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg244987.pdf"> +Linux for &arch-title;</ulink> +Redbook and chapter 3.2 of the +<ulink url="http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf"> +Linux for IBM eServer zSeries and &arch-title;: Distributions</ulink> +Redbook on how to set up an LPAR for Linux. + +</para> + </sect2> + + <sect2 arch="s390"> + <title>Installation as a VM guest</title> + +<para> + +Please refer to chapter 6 of the +<ulink url="http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg244987.pdf"> +Linux for &arch-title;</ulink> +Redbook and chapter 3.1 of the +<ulink url="http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf"> +Linux for IBM eServer zSeries and &arch-title;: Distributions</ulink> +Redbook on how to set up a VM guest for running Linux. + +</para><para> + +You need to copy all the files from the <filename>generic</filename> +sub-directory to your CMS disk. Be sure to transfer +<filename>kernel.debian</filename> and +<filename>initrd.debian</filename> in binary mode with a fixed record +length of 80 characters. + +</para> + </sect2> + + <sect2 arch="s390"> + <title>Setting up an installation server</title> + +<para> + +If you don't have a connection to the Internet (either directly or via +a web proxy) you need to create a local installation server that can +be accessed from your S/390. This server keeps all the packages +you want to install and must make them available using NFS, HTTP or +FTP. + +</para><para> + +The installation server needs to copy the exact directory structure +from any &debian; mirror but of only the s390 and +architecture-independent files are required. You can also copy the +contents of all installation CDs into such a directory tree. + +</para><para condition="FIXME"> + +<emphasis>FIXME: more information needed — from a Redbook?</emphasis> + +</para> + </sect2> diff --git a/ca/preparing/bios-setup/sparc.xml b/ca/preparing/bios-setup/sparc.xml new file mode 100644 index 000000000..591ea1415 --- /dev/null +++ b/ca/preparing/bios-setup/sparc.xml @@ -0,0 +1,103 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + + <sect2 arch="sparc" id="invoking-openboot"><title>Invoking OpenBoot</title> + +<para> + +OpenBoot provides the basic functions needed to boot the &arch-title; +architecture. This is rather similar in function to the BIOS in the +x86 architecture, although much nicer. The Sun boot PROMs have a +built-in forth interpreter which lets you do quite a number of things +with your machine, such as diagnostics, simple scripts, etc. + +</para><para> + +To get to the boot prompt you need to hold down the +<keycap>Stop</keycap> key (on older type 4 keyboards, use the +<keycap>L1</keycap> key, if you have a PC keyboard adapter, use +the <keycap>Break</keycap> key) and press the +<keycap>A</keycap> key. The boot PROM will give you a prompt, +either <userinput>ok</userinput> or <userinput>></userinput>. It is +preferred to have the <userinput>ok</userinput> prompt. So if you get +the old style prompt, hit the <keycap>n</keycap> key to get the new +style prompt. + +</para><para> + +If you are using a serial console, send a break to the machine. With Minicom, +use <keycap>Ctrl-A F</keycap>, with cu, hit <keycap>Enter</keycap>, then type +<userinput>%~break</userinput>. Consult the documentation of your terminal +emulator if you are using a different program. + +</para> + </sect2> + + <sect2 arch="sparc" id="boot-dev-select-sun"> + <title>Boot Device Selection</title> + +<para> + +You can use OpenBoot to boot from specific devices, and also to change +your default boot device. However, you need to know some details +about how OpenBoot names devices; it's much different from Linux +device naming, described in <xref linkend="device-names"/>. +Also, the command will vary a bit, depending on what version of +OpenBoot you have. More information about OpenBoot can be found in +the <ulink url="&url-openboot;">Sun OpenBoot Reference</ulink>. + +</para><para> + +Typically, with newer revisions, you can use OpenBoot device such as +<quote>floppy</quote>, <quote>cdrom</quote>, <quote>net</quote>, +<quote>disk</quote>, or <quote>disk2</quote>. These have the obvious +meanings; the <quote>net</quote> device is for booting from the network. +Additionally, the device name can specify a particular partition of a disk, +such as <quote>disk2:a</quote> to boot disk2, first partition. Full +OpenBoot device names have the form + +<informalexample> +<screen> +<replaceable>driver-name</replaceable>@ +<replaceable>unit-address</replaceable>: +<replaceable>device-arguments</replaceable> +</screen></informalexample>. + +In older revisions of OpenBoot, device naming is a bit different: the +floppy device is called <quote>/fd</quote>, and SCSI disk devices are of +the form <quote>sd(<replaceable>controller</replaceable>, +<replaceable>disk-target-id</replaceable>, +<replaceable>disk-lun</replaceable>)</quote>. The command +<userinput>show-devs</userinput> in newer OpenBoot revisions is useful +for viewing the currently configured devices. For full information, +whatever your revision, see the +<ulink url="&url-openboot;">Sun OpenBoot Reference</ulink>. + +</para><para> + +To boot from a specific device, use the command <userinput>boot +<replaceable>device</replaceable></userinput>. You can set this +behavior as the default using the <userinput>setenv</userinput> +command. However, the name of the variable to set changed between +OpenBoot revisions. In OpenBoot 1.x, use the command +<userinput>setenv boot-from +<replaceable>device</replaceable></userinput>. In later revisions of +OpenBoot, use the command <userinput>setenv boot-device +<replaceable>device</replaceable></userinput>. Note, this is also +configurable using the <command>eeprom</command> command on Solaris, +or modifying the appropriate files in +<filename>/proc/openprom/options/</filename>, for example under Linux: + +<informalexample><screen> +# echo disk1:1 > /proc/openprom/options/boot-device +</screen></informalexample> + +and under Solaris: + +<informalexample><screen> +eeprom boot-device=disk1:1 +</screen></informalexample> + +</para> + </sect2> |