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/boot-installer | |
download | installation-guide-1ea73eea5ecc6a8ed901316049259aee737ee554.zip |
move manual to top-level directory, split out of debian-installer package
Diffstat (limited to 'ca/boot-installer')
-rw-r--r-- | ca/boot-installer/alpha.xml | 441 | ||||
-rw-r--r-- | ca/boot-installer/arm.xml | 113 | ||||
-rw-r--r-- | ca/boot-installer/boot-installer.xml | 32 | ||||
-rw-r--r-- | ca/boot-installer/hppa.xml | 12 | ||||
-rw-r--r-- | ca/boot-installer/i386.xml | 445 | ||||
-rw-r--r-- | ca/boot-installer/ia64.xml | 464 | ||||
-rw-r--r-- | ca/boot-installer/intro-cd.xml | 40 | ||||
-rw-r--r-- | ca/boot-installer/intro-hd.xml | 16 | ||||
-rw-r--r-- | ca/boot-installer/intro-net.xml | 19 | ||||
-rw-r--r-- | ca/boot-installer/m68k.xml | 371 | ||||
-rw-r--r-- | ca/boot-installer/mips.xml | 100 | ||||
-rw-r--r-- | ca/boot-installer/mipsel.xml | 12 | ||||
-rw-r--r-- | ca/boot-installer/parameters.xml | 323 | ||||
-rw-r--r-- | ca/boot-installer/powerpc.xml | 247 | ||||
-rw-r--r-- | ca/boot-installer/s390.xml | 30 | ||||
-rw-r--r-- | ca/boot-installer/sparc.xml | 89 | ||||
-rw-r--r-- | ca/boot-installer/trouble.xml | 274 |
17 files changed, 3028 insertions, 0 deletions
diff --git a/ca/boot-installer/alpha.xml b/ca/boot-installer/alpha.xml new file mode 100644 index 000000000..d43770c8b --- /dev/null +++ b/ca/boot-installer/alpha.xml @@ -0,0 +1,441 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 29334 untranslated --> + + <sect2 arch="alpha" id="alpha-firmware"> + <title>Alpha Console Firmware</title> +<para> + +Console firmware is stored in a flash ROM and started when an Alpha +system is powered up or reset. There are two different console +specifications used on Alpha systems, and hence two classes of console +firmware available: + +</para> + +<itemizedlist> +<listitem><para> + + <emphasis>SRM console</emphasis>, based on the Alpha Console Subsystem + specification, which provides an operating environment for OpenVMS, Tru64 + UNIX, and Linux operating systems. + +</para></listitem> +<listitem><para> + + <emphasis>ARC, AlphaBIOS, or ARCSBIOS console</emphasis>, based on the + Advanced RISC Computing (ARC) specification, which provides an operating + environment for Windows NT. + +</para></listitem> +</itemizedlist> + +<para> + +From the user's perspective, the most important difference between SRM +and ARC is that the choice of console constrains the possible +disk-partitioning scheme for the hard disk which you wish to boot off +of. + +</para><para> + +ARC requires that you use an MS-DOS partition table (as created by +<command>cfdisk</command>) for the boot disk. Therefore MS-DOS partition +tables are the <quote>native</quote> partition format when booting from +ARC. In fact, since AlphaBIOS contains a disk partitioning utility, you may +prefer to partition your disks from the firmware menus before +installing Linux. + +</para><para> + +Conversely, SRM is <emphasis>incompatible</emphasis><footnote> + +<para> +Specifically, the bootsector format required by the Console Subsystem +Specification conflicts with the placement of the DOS partition table. +</para> + +</footnote> with MS-DOS partition tables. Since Tru64 Unix uses the BSD +disklabel format, this is the <quote>native</quote> partition format for +SRM installations. + +</para><para> + +GNU/Linux is the only operating system on Alpha that can be booted from +both console types, but &debian; &release; only supports booting on +SRM-based systems. If you have an Alpha for which no version of SRM is +available, if you will be dual-booting the system with Windows NT, or if +your boot device requires ARC console support for BIOS initialization, +you will not be able to use the &debian; &release; installer. You can +still run &debian; &release; on such systems by using other install +media; for instance, you can install Debian woody with MILO and upgrade. + +</para><para> + +Because <command>MILO</command> is not available for any of the Alpha +systems currently in production (as of February 2000), and because it +is no longer necessary to buy an OpenVMS or Tru64 Unix license to have +SRM firmware on your older Alpha, it is recommended that you use SRM +when possible. + +</para><para> + +The following table summarizes available and supported system +type/console combinations (see <xref linkend="alpha-cpus"/> for the +system type names). The word <quote>ARC</quote> below denotes any of the +ARC-compliant consoles. + +</para><para> + +<informaltable><tgroup cols="2"> +<thead> +<row> + <entry>System Type</entry> + <entry>Console Type Supported</entry> +</row> +</thead> + +<tbody> +<row> + <entry>alcor</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>avanti</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>book1</entry> + <entry>SRM only</entry> +</row><row> + <entry>cabriolet</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>dp264</entry> + <entry>SRM only</entry> +</row><row> + <entry>eb164</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>eb64p</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>eb66</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>eb66p</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>jensen</entry> + <entry>SRM only</entry> +</row><row> + <entry>lx164</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>miata</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>mikasa</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>mikasa-p</entry> + <entry>SRM only</entry> +</row><row> + <entry>nautilus</entry> + <entry>ARC (see motherboard manual) or SRM</entry> +</row><row> + <entry>noname</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>noritake</entry> + <entry>SRM only</entry> +</row><row> + <entry>noritake-p</entry> + <entry>SRM only</entry> +</row><row> + <entry>pc164</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>rawhide</entry> + <entry>SRM only</entry> +</row><row> + <entry>ruffian</entry> + <entry>ARC only</entry> +</row><row> + <entry>sable</entry> + <entry>SRM only</entry> +</row><row> + <entry>sable-g</entry> + <entry>SRM only</entry> +</row><row> + <entry>sx164</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>takara</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>xl</entry> + <entry>ARC only</entry> +</row><row> + <entry>xlt</entry> + <entry>ARC only</entry> +</row> + +</tbody> +</tgroup> +</informaltable> + +</para><para> + +Generally, none of these consoles can boot Linux directly, so the +assistance of an intermediary bootloader is required. For the SRM +console, <command>aboot</command>, a small, platform-independent +bootloader, is used. See the (unfortunately outdated) <ulink +url="&url-srm-howto;">SRM HOWTO</ulink> for more information on +<command>aboot</command>. + +</para><para condition="FIXME"> + +The following paragraphs are from the woody install manual, and are +included here for reference; they may be useful to someone at a later +date when Debian supports MILO-based installs again. + +</para><para condition="FIXME"> + +Generally, none of these consoles can boot Linux directly, so the +assistance of an intermediary bootloader is required. There are two +mainstream Linux loaders: <command>MILO</command> and <command>aboot</command>. + +</para><para condition="FIXME"> + +<command>MILO</command> is itself a console, which replaces ARC or SRM in +memory. <command>MILO</command> can be booted from both ARC and SRM and is +the only way to bootstrap Linux from the ARC console. +<command>MILO</command> is platform-specific (a different <command>MILO</command> +is needed for each system type) and exist only for those systems, for +which ARC support is shown in the table above. See also the +(unfortunately outdated) <ulink url="&url-milo-howto;">MILO HOWTO</ulink>. + +</para><para condition="FIXME"> + +<command>aboot</command> is a small, platform-independent bootloader, which +runs from SRM only. See the (also unfortunately outdated) <ulink +url="&url-srm-howto;">SRM HOWTO</ulink> for more information on +<command>aboot</command>. + +</para><para condition="FIXME"> + +Thus, three scenarios are generally possible, depending on the +system's console firmware and whether or not <command>MILO</command> is +available: + +<informalexample><screen> +SRM -> aboot +SRM -> MILO +ARC -> MILO +</screen></informalexample> + +Because <command>MILO</command> is not available for any of the Alpha +systems currently in production (as of February 2000), and because it +is no longer necessary to buy an OpenVMS or Tru64 Unix license to have +SRM firmware on your older Alpha, it is recommended that you use SRM and +<command>aboot</command> on new installations of GNU/Linux, unless you wish +to dual-boot with Windows NT. + +</para><para> + +The majority of AlphaServers and all current server and workstation +products contain both SRM and AlphaBIOS in their firmware. For +<quote>half-flash</quote> machines such as the various evaluation boards, +it is possible to switch from one version to another by reflashing the +firmware. Also, once SRM is installed, it is possible to run +ARC/AlphaBIOS from a floppy disk (using the <command>arc</command> +command). For the reasons mentioned above, we recommend switching to +SRM before installing &debian;. + +</para><para> + +As on other architectures, you should install the newest available +revision of the firmware<footnote> + +<para> +Except on Jensen, where Linux is not supported on firmware versions +newer than 1.7 — see <ulink url="&url-jensen-howto;"></ulink> +for more information. +</para> + +</footnote> before installing &debian;. +For Alpha, firmware updates can be obtained from +<ulink url="&url-alpha-firmware;">Alpha Firmware Updates</ulink>. + +</para> + </sect2> + + + <sect2 arch="alpha"><title>Booting with TFTP</title> +<para> + +In SRM, Ethernet interfaces are named with the <userinput>ewa</userinput> +prefix, and will be listed in the output of the <userinput>show dev</userinput> command, +like this (edited slightly): + +<informalexample><screen> +>>> show dev +ewa0.0.0.9.0 EWA0 08-00-2B-86-98-65 +ewb0.0.0.11.0 EWB0 08-00-2B-86-98-54 +ewc0.0.0.2002.0 EWC0 00-06-2B-01-32-B0 +</screen></informalexample> + +You first need to set the boot protocol: + +<informalexample><screen> +>>> set ewa0_protocol bootp +</screen></informalexample> + +Then check the medium type is correct: + +<informalexample><screen> +>>> set ewa0_mode <replaceable>mode</replaceable> +</screen></informalexample> + +You can get a listing of valid modes with <userinput>>>>set ewa0_mode</userinput>. + +</para><para> + +Then, to boot from the first Ethernet interface, you would type: + +<informalexample><screen> +>>> boot ewa0 -flags "" +</screen></informalexample> + +This will boot using the default kernel parameters as included in the +netboot image. + +</para><para> + +If you wish to use a serial console, you <emphasis>must</emphasis> +pass the <userinput>console=</userinput> parameter to the kernel. +This can be done using the <userinput>-flags</userinput> argument to +the SRM <userinput>boot</userinput> command. The serial ports are +named the same as their corresponding files in +<userinput>/dev</userinput>. Also, when specifying additional kernel +parameters, you must repeat certain default options that are needed by +the &d-i; images. For example, to boot from <userinput>ewa0</userinput> +and use a console on the first serial port, you would type: + +<informalexample><screen> +>>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 console=ttyS0" +</screen></informalexample> + +</para> + </sect2> + + <sect2 arch="alpha"><title>Booting from CD-ROM with the SRM Console</title> +<para> + +Type + +<informalexample><screen> +>>> boot xxxx -flags 0 +</screen></informalexample> + +where <replaceable>xxxx</replaceable> is your CD-ROM drive in SRM notation. + +</para> + </sect2> + + <sect2 arch="alpha" condition="FIXME"> + <title>Booting from CD-ROM with the ARC or AlphaBIOS Console</title> +<para> + +To boot a CD-ROM from the ARC console, find your sub-architecture code +name (see <xref linkend="alpha-cpus"/>), then enter +<filename>\milo\linload.exe</filename> as the boot loader and +<filename>\milo\<replaceable>subarch</replaceable></filename> (where +<replaceable>subarch</replaceable> is the proper subarchitecture name) +as the OS Path in the `OS Selection Setup' menu. Ruffians make an +exception: You need to use <filename>\milo\ldmilo.exe</filename> as +boot loader. + +</para> + </sect2> + + + <sect2 arch="alpha" condition="supports-floppy-boot"> + <title>Booting from Floppies with the SRM Console</title> +<para> + +At the SRM prompt (<prompt>>>></prompt>), issue the following +command: + +<informalexample><screen> +>>> boot dva0 -flags 0 +</screen></informalexample> + +possibly replacing <filename>dva0</filename> with the actual device +name. Usually, <filename>dva0</filename> is the floppy; type + +<informalexample><screen> +>>> show dev +</screen></informalexample> + +to see the list of devices (e.g., if you want to boot from a CD). +Note that if you are booting via MILO, <command>-flags</command> argument +is ignored, so you can just type <command>boot dva0</command>. +If everything works OK, you will eventually see the Linux kernel boot. + +</para><para> + +If you want to specify kernel parameters when booting via +<command>aboot</command>, use the following command: + +<informalexample><screen> +>>> boot dva0 -file linux.bin.gz -flags "root=/dev/fd0 load_ramdisk=1 arguments" +</screen></informalexample> + +(typed on one line), substituting, if necessary, the actual SRM boot +device name for <filename>dva0</filename>, the Linux boot device name for +<filename>fd0</filename>, and the desired kernel parameters for +<filename>arguments</filename>. + +</para><para> + +If you want to specify kernel parameters when booting via +<command>MILO</command>, you will have to interrupt bootstrap once you get +into MILO. See <xref linkend="booting-from-milo"/>. +</para> + </sect2> + + + <sect2 arch="alpha" condition="supports-floppy-boot"> + <title>Booting from Floppies with the ARC or AlphaBIOS Console</title> + +<para> + +In the OS Selection menu, set <command>linload.exe</command> as the boot +loader, and <command>milo</command> as the OS Path. Bootstrap using the +newly created entry. + +</para> + </sect2> + + <sect2 arch="alpha" condition="FIXME" id="booting-from-milo"><title>Booting with MILO</title> +<para> + +MILO contained on the bootstrap media is configured to proceed straight +to Linux automatically. Should you wish to intervene, all you need is to +press space during MILO countdown. + +</para><para> + +If you want to specify all the bits explicitly (for example, to supply +additional parameters), you can use a command like this: + +<informalexample><screen> +MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 <!-- arguments --> +</screen></informalexample> + +If you are booting from something other than a floppy, substitute +<filename>fd0</filename> in the above example with the appropriate device name +in Linux notation. The <command>help</command> command would give you a brief +MILO command reference. + +</para> + </sect2> diff --git a/ca/boot-installer/arm.xml b/ca/boot-installer/arm.xml new file mode 100644 index 000000000..505a05323 --- /dev/null +++ b/ca/boot-installer/arm.xml @@ -0,0 +1,113 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 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> + +<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> + +<filename>nettrom-2.3.3.bin</filename> + +</para></listitem> +<listitem><para> + +<filename>nettrom-2.3.3.bin.md5sum</filename> + +</para></listitem> +</itemizedlist> + +</para></note><para> + +After rebooting and interrupting the boot process during the countdown, you +must first configure the network either with a static address: + +<informalexample><screen> + 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 +</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): + +<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 + 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: + +<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. + +</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 +Cyclone prompt. + +</para> + </sect3> + </sect2> + + + + <sect2 arch="arm"><title>Booting from CD-ROM</title> + +&boot-installer-intro-cd.xml; + +<para> + +To boot a CD-ROM from the Cyclone console prompt, use the command +<command>boot cd0:cats.bin</command> + +</para> + </sect2> diff --git a/ca/boot-installer/boot-installer.xml b/ca/boot-installer/boot-installer.xml new file mode 100644 index 000000000..e1e5d9dae --- /dev/null +++ b/ca/boot-installer/boot-installer.xml @@ -0,0 +1,32 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 24701 --> + +<chapter id="boot-installer"><title>Arrencant el sistema d'instal·lació</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"> + <title>Arrencant l'instal·lador en l'arquitectura &arch-title;</title> + +<!-- This info is so architecture dependent, that I have turned the --> +<!-- structure inside out for this chapter. Each arch has a document. --> +<!-- Note: archs hppa and mipsel are currently missing --> + +&boot-installer-alpha.xml; +&boot-installer-arm.xml; +<!-- &boot-installer-hppa.xml; --> +&boot-installer-i386.xml; +&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; + + </sect1> + +&boot-installer-parameters.xml; +&boot-installer-trouble.xml; + +</chapter> diff --git a/ca/boot-installer/hppa.xml b/ca/boot-installer/hppa.xml new file mode 100644 index 000000000..0676332b2 --- /dev/null +++ b/ca/boot-installer/hppa.xml @@ -0,0 +1,12 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 24701 --> + + <sect2 arch="hppa"> + <title></title> +<para> + +<!-- Placeholder document; please write and include in + boot-installer.xml and build/templates/docstruct.ent --> + +</para> + </sect2> diff --git a/ca/boot-installer/i386.xml b/ca/boot-installer/i386.xml new file mode 100644 index 000000000..8d9aa8b3f --- /dev/null +++ b/ca/boot-installer/i386.xml @@ -0,0 +1,445 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 25149 --> + + <sect2 arch="i386"><title>Arrencant des d'un CD-ROM</title> + +&boot-installer-intro-cd.xml; + +<!-- We'll comment the following section until we know exact layout --> +<!-- +CD #1 of official Debian CD-ROM sets for &arch-title; will present a +<prompt>boot:</prompt> prompt on most hardware. Press +<keycap>F3</keycap> to see the list of kernel options available +from which to boot. Just type your chosen flavor name (idepci, +vanilla, compact, bf24) at the <prompt>boot:</prompt> prompt +followed by &enterkey;. + +</para><para> + +If your hardware doesn't support booting of multiple images, put one +of the other CDs in the drive. It appears that most SCSI CD-ROM drives +do not support <command>isolinux</command> multiple image booting, so users +with SCSI CD-ROMs should try either CD2 (vanilla) or CD3 (compact), +or CD5 (bf2.4). + +</para><para> + +CD's 2 through 5 will each boot a +different ``flavor'' depending on which CD-ROM is +inserted. See <xref linkend="kernel-choice"/> for a discussion of the +different flavors. Here's how the flavors are laid out on the +different CD-ROMs: + +<variablelist> +<varlistentry> +<term>CD 1</term><listitem><para> + +Allows a selection of kernel images to boot from (the idepci flavor is +the default if no selection is made). + +</para></listitem></varlistentry> +<varlistentry> +<term>CD 2</term><listitem><para> + +Boots the `vanilla' flavor. + +</para></listitem></varlistentry> +<varlistentry> +<term>CD 3</term><listitem><para> + +Boots the `compact' flavor. + +</para></listitem></varlistentry> +<varlistentry> +<term>CD 4</term><listitem><para> + +Boots the `idepci' flavor. + +</para></listitem></varlistentry> +<varlistentry> +<term>CD 5</term><listitem><para> + +Boots the `bf2.4' flavor. + +</para></listitem></varlistentry> + + </variablelist> + +</para><para> + +--> + + </sect2> + +<!-- FIXME the documented procedure does not exactly work, commented out + until fixes + + <sect2 arch="i386" id="install-from-dos"> + <title>Booting from a DOS partition</title> + +&boot-installer-intro-hd.xml; + +<para> + +Boot into DOS (not Windows) without any drivers being loaded. To do +this, you have to press <keycap>F8</keycap> at exactly the right +moment (and optionally select the `safe mode command prompt only' +option). Enter the subdirectory for the flavor you chose, e.g., + +<informalexample><screen> +cd c:\install +</screen></informalexample>. + +Next, execute <command>install.bat</command>. +The kernel will load and launch the installer system. + +</para><para> + +Please note, there is currently a loadlin problem (#142421) which +precludes <filename>install.bat</filename> from being used with the +bf2.4 flavor. The symptom of the problem is an +<computeroutput>invalid compressed format</computeroutput> error. + +</para> + </sect2> + +END FIXME --> + + <sect2 arch="i386" id="boot-initrd"> + <title>Arrencant des del Linux utilitzant el <command>LILO</command> o el + <command>GRUB</command></title> + +<para> + +Per arrencar l'instal·lador des d'un disc dur, primer heu de baixar +els fitxers necessaris tal i com es descriu a +<xref linkend="boot-drive-files"/>. + +</para> + +<para> + +Si voleu utilitzar el disc dur únicament per a l'arrencada i +voleu baixar-ho tot des de la xarxa, hauríeu de baixar el fitxer +<filename>netboot/debian-installer/i386/initrd.gz</filename> +i el nucli corresponent. + +Us permetrà tornar a particionar el disc dur del qual heu arrencat +l'instal·lador, tot i això, ho hauríeu de fer amb molt de compte. + +</para> + +<para> + +Si durant la instal·lació preteneu mantenir sense modificacions una +partició existent al disc dur, podeu baixar el fitxer +<filename>hd-media/initrd.gz</filename> i el nucli corresponent, i +també copiar una imatge iso del CD al dispositiu (assegureu-vos +que el nom del fitxer acaba amb «.iso»). En aquest cas l'instal·lador +pot arrencar del dispositiu i instal·lar des de la imatge del CD sense +necessitar la xarxa. + +</para> + +<para> + +Per utilitzar el <command>LILO</command> haureu de configurar +dos punts essencials del fitxer <filename>/etc/lilo.conf</filename>: + +<itemizedlist> +<listitem><para> + +carregar l'instal·lador <filename>initrd.gz</filename> a l'arrencada; + +</para></listitem> +<listitem><para> + +obligar al nucli <filename>vmlinuz</filename> a utilitzar un disc +de RAM com a partició arrel. + +</para></listitem> +</itemizedlist> + +A continuació trobareu un exemple del fitxer +<filename>/etc/lilo.conf</filename>: + +</para><para> + +<informalexample><screen> +image=/boot/newinstall/vmlinuz + label=newinstall + initrd=/boot/newinstall/initrd.gz + root=/dev/ram0 + append="devfs=mount,dall ramdisk_size=12000" +</screen></informalexample> + +Per a més informació vegeu les pàgines del manual +<citerefentry><refentrytitle>initrd</refentrytitle> +<manvolnum>4</manvolnum></citerefentry> i +<citerefentry><refentrytitle>lilo.conf</refentrytitle> +<manvolnum>5</manvolnum></citerefentry>. Executeu l'ordre +<userinput>lilo</userinput> i reinicieu el sistema. + +</para><para> + +El procediment pel <command>GRUB</command> és similar. Cerqueu el fitxer +<filename>menu.lst</filename> al directori <filename>/boot/grub/</filename> +(en algunes ocasions al directori <filename>/boot/boot/grub/</filename>) +i afegiu-hi les línies següents: + +<informalexample><screen> +title New Install +kernel (hd0,0)/boot/newinstall/vmlinuz root=/dev/ram0 ramdisk_size=12000 +initrd (hd0,0)/boot/newinstall/initrd.gz +</screen></informalexample> + +i reinicieu el sistema. Si l'arrencada falla, podeu provar afegint +<userinput>devfs=mount,dall</userinput> a la línia <quote>kernel</quote>. + +</para><para> +Recordeu que el valor de <userinput>ramdisk_size</userinput> s'hauria +d'ajustar a la mida de la imatge initrd. A partir d'aquí no hi hauria +d'haver cap diferència entre el <command>GRUB</command> i el +<command>LILO</command>. + +</para> + </sect2> + + <sect2 arch="i386" id="usb-boot"> + <title>Arrencant des d'un llapis USB</title> +<para> + +S'assumeix que heu seguit els passos descrits a +<xref linkend="boot-dev-select"/> i <xref linkend="boot-usb-files"/>. +Només heu de connectar el llapis USB a algun connector USB lliure i +reiniciar l'ordinador. El sistema s'hauria d'arrencar i us hauria +d'aparèixer l'indicador <prompt>boot:</prompt>. Podeu introduïr-hi +els paràmetres d'arrencada opcionals o únicament prémer &enterkey; + +</para><para> + +En el cas que el vostre ordinador no permeti l'arrencada des d'un +dispositiu de memòria USB, podeu utilitzar un disquet per fer +l'arrencada inicial i posteriorment commutar a l'USB. Arrenqueu el +vostre ordinador tal com està descrit a <xref linkend="floppy-boot"/>; +el nucli del disquet d'arrencada hauria de detectar automàticament el +llapis USB. Quan se us demani el disquet arrel, premeu &enterkey;. +Hauríeu de veure com s'inicialitza el &d-i;. + +</para> + </sect2> + + <sect2 arch="i386" id="floppy-boot"> + <title>Arrencant des dels disquets</title> +<para> + +Haureu d'haver descarregat les imatges del disquet i haver-ne +creat els disquets corresponents segons <xref linkend="create-floppy"/>. +<!-- missing-doc FIXME If you need to, you can also modify the boot floppy; see +<xref linkend="rescue-replace-kernel"/>. --> + +</para><para> + +Per arrencar des del disquet d'arrencada instal·lador, introduïu-lo +a la disquetera, atureu el sistema i torneu-lo a engegar. + +</para><para> + +Per instal·lar des d'una unitat LS-120 (versió ATAPI) utilitzant +un conjunt de disquets, heu d'especificar la ubicació virtual de la +disquetera. Ho podeu fer a través del paràmetre d'arrencada +<emphasis>root=</emphasis>, especificant que el controlador de la +disquetera-ide mapeja el dispositiu. Per exemple, si la unitat LS-120 +està connectada al primer dispositiu IDE (master) del segon cable, +hauríeu d'introduir <userinput>linux root=/dev/hdc</userinput> a +l'indicador d'arrencada. La instal·lació des del LS-120 només està +suportada a partir de la versió del nucli 2.4. + +</para><para> + +Recodeu que en alguns ordinadors la combinació +<keycombo><keycap>Control</keycap> +<keycap>Alt</keycap> <keycap>Delete</keycap></keycombo> +no reinicia correctament l'ordinador i es recomana +reiniciar-lo manualment. Si ho esteu instal·lant des d'un sistema operatiu +existent (ex. des d'un DOS) teniu l'opció. Si no és el cas reinicieu-lo +manualment durant l'arrencada. + +</para><para> + +S'hauria d'accedir al disquet i hauria d'aparèixer una pantalla +relacionada amb el disquet d'arrencada i que acaba amb +l'indicador <prompt>boot:</prompt>. + +</para><para> + +Al prémer &enterkey; hauríeu de veure el missatge +<computeroutput>Loading...</computeroutput>, seguit de +<computeroutput>Uncompressing Linux...</computeroutput>, i +a continuació una pàgina amb la informació del maquinari del sistema. +Per a més informació d'aquesta fase del procés d'arrencada vegeu +<xref linkend="kernel-msgs"/>. + +</para><para> + +Un cop arrencat des del disquet d'arrencada se us sol·licitarà +el disquet arrel. Inserteu el disquet arrel i permeu &enterkey;, +seguidament es carregaran els continguts a la memòria. +El programa instal·lador <command>debian-installer</command> +s'iniciarà automàticament. + +</para> + </sect2> + + <sect2 arch="i386" id="boot-tftp"><title>Arrencant via TFTP</title> + +&boot-installer-intro-net.xml; + +<para> + +Hi ha diversos mètodes per a arrencar via TFTP en i386. + +</para> + + <sect3><title>Tarja de xarxa o placa mare que suporta PXE</title> +<para> + +És possible que la vostra tarja de xarxa o la placa mare proporcionin +la possibilitat d'arrencada via PXE. Es tracta d'una reimplementació +d'<trademark class="trade">Intel</trademark> de l'arrencada via TFTP. +Si és el vostre cas podeu configurar la BIOS perquè arrenqui via la +xarxa. + +</para> + </sect3> + + <sect3><title>Tarja de xarxa amb una ROM d'arrencada via xarxa</title> +<para> + +És possible que la vostra tarja de xarxa proporcioni la possibilitat +d'arrencar via TFTP. + +</para><para condition="FIXME"> + +Informeu-nos (<email>&email-debian-boot-list;</email>) de com us ha anat. + +</para> + </sect3> + + <sect3><title>Etherboot</title> +<para> + +El <ulink url="http://www.etherboot.org">projecte etherboot</ulink> +proporciona disquets d'arrencada i fins hi tot roms d'arrencada +que permeten l'arrencada via TFTP. + +</para> + </sect3> + </sect2> + + <sect2 arch="i386"><title>Paràmetre d'arrencada i386</title> +<para> + +Quan arrenqui l'instal·lador us apareixerà l'indicador d'arrencada +<prompt>boot:</prompt>. En l'indicador <prompt>boot:</prompt> podeu +fer dues coses. Podeu prémer les tecles de <keycap>F1</keycap> +a <keycap>F10</keycap> per visualitzar pàgines d'informació útil, +o podeu prémer <keycap>Enter</keycap> per reiniciar el sistema. + +</para><para> + +Podeu accedir a informació interessant sobre els paràmetre d'arrencada +prement les tecles de <keycap>F3</keycap> a <keycap>F7</keycap>. +Si afegiu qualsevol paràmetre a la línia d'ordres d'arrencada, +assegureu-vos d'escriure el mètode d'arrencada (el predeterminat és +<userinput>linux</userinput>) i un espai abans del primer paràmetre +(ex. <userinput>linux floppy=thinkpad</userinput>). Prémer &enterkey;, +és el mateix que escriure <userinput>linux</userinput> sense cap +paràmetre especial. + +</para><para> + +Alguns sistemes tenen disqueteres amb els "DCL invertits". Si +us apareixen errors mentre esteu llegint de la disquetera tot +i saber que funciona correctament, proveu d'utilitzar el paràmetre +<userinput>floppy=thinkpad</userinput>. + +</para><para> + +En alguns sistemes com els IBM PS/1 o el ValuePoint (que disposa +dels controladors de disc del ST-506) la unitat IDE no es reconeixerà +correctament. En aquest cas proveu-ho sense paràmetres i espereu si +es reconeix correctament. Si no és el cas, cerqueu els paràmetres +del dispositiu (cilindres, capçals i sectors) i utilitzeu el paràmetre +<userinput>hd=<replaceable>cilindres</replaceable>,<replaceable>capçals</replaceable>,<replaceable>sectors</replaceable></userinput>. + +</para><para> + +Si disposeu d'un ordinador molt vell i el nucli es penja +després de mostrar el missatge +<computeroutput>Checking 'hlt' instruction...</computeroutput>, +hauríeu de provar el paràmetre d'arrencada que inhabilita la prova +<userinput>no-hlt</userinput>. + +</para><para> + +Si durant l'arrencada del nucli apareixen caràcters estranys a la pantalla, +és possible que el sistema disposi d'una tarja de vídeo problemàtica +que no commuta correctament al mode framebuffer. En aquest cas podeu +utilitzar el paràmetre d'arrencada +<userinput>debian-installer/framebuffer=false</userinput> o +<userinput>video=vga16:off</userinput> per inhabilitar el frambuffer. +Durant la instal·lació únicament es disposarà de l'idioma anglès +arran de les limitacions de la consola. Per a més informació +vegeu +<xref linkend="boot-parms"/>. + +</para> + </sect2> + + <sect2 arch="i386"> + <title>El sistema queda congelat durant la fase de configuració de la PCMCIA</title> + +<para> + +Alguns models d'ordinadors portàtils produïts per Dell són coneguts +per penjar-se quan la detecció de dispositius PCMCIA intenta accedir a +algunes adreces de maquinari. D'altres portàtils poden descriure +problemàtiques similars. Si patiu algun problema similar i durant +la instal·lació no preciseu del suport PCMCIA, el podeu inhabilitar +utilitzant el paràmetre d'arrencada +<userinput>hw-detect/start_pcmcia=false</userinput>. +Podeu configurar el suport de PCMCIA després de la instal·lació +i excloure'n el rang de recursos problemàtic. + +</para><para> + +D'altra banda, podeu arrencar l'instal·lador en mode expert. Se us +demanarà que introduïu les opcions del rang de recursos que precisa +el vostre maquinari. Per exemple, si disposeu d'un dels ordinadors +portàtils Dell anomenats anteriorment, hauríeu d'introduir-hi +<userinput>exclude port 0x800-0x8ff</userinput>. Disposeu d'una llista +de les opcions del rangs de recursos més habituals a +<ulink url="http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12">System +resource settings section of the PCMCIA HOWTO</ulink>. +Recordeu que heu d'evitar la utilització de les comes a l'hora +d'introduir els valors a l'instal·lador. + +</para> + </sect2> + + <sect2 arch="i386"> + <title>El sistema queda congelat durant la càrrega dels mòduls USB</title> +<para> + +El nucli acostuma a intentar instal·lar els mòduls USB i els controladors +del teclat USB per suportar alguns teclats USB no estàndards. Tot i això, +hi ha alguns sistemes USB inconsistents en els quals el controlador +es penja durant la càrrega. Una possible solució és inhabilitar el controlador +USB en la configuració de la BIOS de la placa mare. Una altra opció és +passsar el paràmetre +<userinput>debian-installer/probe/usb=false</userinput> +a l'indicador d'arrencada, que evitarà que es carreguin els mòduls. + +</para> + </sect2> diff --git a/ca/boot-installer/ia64.xml b/ca/boot-installer/ia64.xml new file mode 100644 index 000000000..9afc8b61e --- /dev/null +++ b/ca/boot-installer/ia64.xml @@ -0,0 +1,464 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + <sect2 arch="ia64"><title>Booting from a CD-ROM</title> + +&boot-installer-intro-cd.xml; + + <note> + <title>CD Contents</title> + +<para> + +There are three basic variations of Debian Install CDs. +The <emphasis>Business Card</emphasis> CD has a minimal installation +that will fit on the small form factor CD media. +It requires a network connection in order to install the rest of the +base installation and make a usable system. +The <emphasis>Network Install</emphasis> CD has all of the packages +for a base install but requires a network connection to a Debian +mirror site in order to install the +extra packages one would want for a complete system . +The set of Debian CDs can install a complete system from the wide +range of packages without needing access to the network. +</para> + </note> + +<para> + +The IA-64 architecture uses the next generation Extensible Firmware Interface +(EFI) from Intel. +Unlike the traditional x86 BIOS which knows little about the boot +device other than the partition table and Master Boot Record (MBR), +EFI can read and write files from FAT16 or FAT32 formatted disk +partitions. +This simplifies the often arcane process of starting a system. +The system boot loader and the EFI firmware that supports it have +a full filesystem to store the files necessary for booting the +machine. +This means that the system disk on an IA-64 system has an additional +disk partition dedicated to EFI instead of the simple MBR or boot +block on more conventional systems. + +</para><para> + +The Debian Installer CD contains a small EFI partition where the +<command>ELILO</command> bootloader, its configuration file, the installer's +kernel, and initial filesystem (initrd) are located. +The running system also contains an EFI partition where the necessary +files for booting the system reside. +These files are readable from the EFI Shell as described below. + +</para><para> + +Most of the details of how <command>ELILO</command> actually loads and +starts a system are transparent to the system installer. +However, the installer must set up an EFI partition prior to installing +the base system. Otherwise, the installation of <command>ELILO</command> +will fail, rendering the system un-bootable. +The EFI partition is allocated and formatted in the partitioning step +of the installation prior to loading any packages on the system disk. +The partitioning task also verifies that a suitable EFI partition is +present before allowing the installation to proceed. + +</para><para> + +The EFI Boot Manager is presented as the last step of the firmware +initialization. +It displays a menu list from which the user can select +an option. +Depending on the model of system and what other software has been +loaded on the system, this menu may be different from one system +to another. +There should be at least two menu items displayed, +<command>Boot Option Maintenance Menu</command> and +<command>EFI Shell (Built-in)</command>. +Using the first option is preferred, however, if that +option is not available or the CD for some reason does not +boot with it, use the second option. + +</para> + + <warning> + <title>IMPORTANT</title> +<para> +The EFI Boot Manager will select a default boot action, typically +the first menu choice, within a pre-set number of seconds. +This is indicated by a countdown at the bottom of the screen. +Once the timer expires and the systems starts the default action, +you may have to reboot the machine in order to continue the installation. +If the default action is the EFI Shell, you can return to the Boot Manager +by running <command>exit</command> at the shell prompt. +</para> + </warning> + + <sect3 arch="ia64" id="bootable-cd"> + <title>Option 1: Booting from the Boot Option Maintenance Menu</title> +<para> + +</para> + +<itemizedlist> + +<listitem><para> +Insert the CD in the DVD/CD drive and reboot the machine. +The firmware will display the EFI Boot Manager page and menu after +it completes its system initialization. +</para></listitem> + +<listitem><para> +Select <command>Boot Maintenance Menu</command> from the menu +with the arrow keys and press <command>ENTER</command>. +This will display a new menu. +</para></listitem> + +<listitem><para> +Select <command>Boot From a File</command> from the menu +with the arrow keys and press <command>ENTER</command>. +This will display a list of devices probed by the firmware. +You should see two menu lines containing either the label +<command>Debian Inst [Acpi ...</command> or +<command>Removable Media Boot</command>. +If you examine the rest of the menu line, you will notice that +the device and controller information should be the same. +</para></listitem> + +<listitem><para> +You can choose either of the entries that refer to the CD/DVD +drive. +Select your choice with the arrow keys and press <command>ENTER</command>. +If you choose <command>Removable Media Boot</command> the machine +will immediately start the boot load sequence. +If you choose <command>Debian Inst [Acpi ...</command> instead, it +will display a directory listing of the bootable portion of the +CD, requiring you to proceed to the next (additional) step. +</para></listitem> + +<listitem><para> +You will only need this step if you chose +<command>Debian Inst [Acpi ...</command>. +The directory listing will also show +<command>[Treat like Removable Media Boot]</command> on the next to +the last line. +Select this line with the arrow keys and press <command>ENTER</command>. +This will start the boot load sequence. +</para></listitem> + +</itemizedlist> + +<para> + +These steps start the Debian boot loader which will display a +menu page for you to select a boot kernel and options. +Proceed to selecting the boot kernel and options. + +</para> + </sect3> + + <sect3 arch="ia64" id="boot-with-efi"> + <title>Option 2: Booting from the EFI Shell</title> +<para> + +If, for some reason, option 1 is not successful, reboot the machine +and when the EFI Boot Manager screen appears there should be +one option called <command>EFI Shell [Built-in]</command>. +Boot the Debian Installer CD with the following steps: + +</para> + +<itemizedlist> + +<listitem><para> +Insert the CD in the DVD/CD drive and reboot the machine. +The firmware will display the EFI Boot Manager page and menu after +it completes system initialization. +</para></listitem> + +<listitem><para> +Select <command>EFI Shell</command> from the menu with the arrow keys +and press <command>ENTER</command>. +The EFI Shell will scan all of the bootable devices and display +them to the console before displaying its command prompt. +The recognized bootable partitions on devices will show a device name of +<filename>fs<replaceable>n</replaceable>:</filename>. +All other recognized partitions will be named +<filename>blk<replaceable>n</replaceable>:</filename>. +If you inserted the CD just before entering the shell, this may +take a few extra seconds as it initializes the CD drive. +</para> +</listitem> + +<listitem><para> +Examine the output from the shell looking for the CDROM drive. +It is most likely the <filename>fs0:</filename> device although +other devices with bootable partitions will also show up as +<filename>fs<replaceable>n</replaceable></filename>. +</para></listitem> + +<listitem><para> +Enter <command>fs<replaceable>n</replaceable>:</command> and press +<command>ENTER</command> to select that +device where <replaceable>n</replaceable> is the partition number for the +CDROM. The shell will now display the partition number as its prompt. +</para></listitem> + +<listitem><para> +Enter <command>elilo</command> and press <command>ENTER</command>. +This will start the boot load sequence. +</para></listitem> + +</itemizedlist> + +<para> + +As with option 1, these steps start the Debian boot loader which will +display a menu page for you to select a boot kernel and options. +You can also enter the shorter +<command>fs<replaceable>n</replaceable>:elilo</command> command at +the shell prompt. +Proceed to selecting the boot kernel and options. + +</para> + + </sect3> + + <sect3 arch="ia64" id="serial-console"> + <title>Installing using a Serial Console</title> + +<para> + +You may choose to perform an install using a monitor and keyboard +or using a serial connection. To use a monitor/keyboard setup, +select an option containing the string [VGA console]. To install +over a serial connection, choose an option containing the string +[<replaceable>BAUD</replaceable> baud serial console], where +<replaceable>BAUD</replaceable> is the speed of your serial console. +Menu items for the most typical baud rate settings on the ttyS0 +device are preconfigured. + +</para><para> + +In most circumstances, you will want the installer to use the same +baud rate as your connection to the EFI console. If you aren't +sure what this setting is, you can obtain it using the command +<command>baud</command> at the EFI shell. + +</para><para> + +If there is not an option available that is configured for the serial +device or baud rate you would like to use, you may override the console setting +for one of the existing menu options. For example, to use a +57600 baud console over the ttyS1 device, enter +<command>console=ttyS1,57600n8</command> into +the <classname>Boot:</classname> text window. + +</para> + +<note><para> +Most IA-64 boxes ship with a default console setting of 9600 baud. +This setting is rather slow, and the normal installation process +will take a significant time to draw each screen. You should consider +either increasing the baud rate used for performing the installation, +or performing a Text Mode installation. See the <classname>Params</classname> +help menu for instructions on starting the installer in Text Mode. +</para></note> + +<warning><para> +If you select the wrong console type, you +will be able to select the kernel and enter parameters but both +the display and your input will go dead as soon as the kernel starts, +requiring you to reboot before you can begin the installation. +</para></warning> + </sect3> + + <sect3 arch="ia64" id="kernel-option-menu"> + <title>Selecting the Boot Kernel and Options</title> + +<para> + +The boot loader will display a form with a menu list and a text +window with a <classname>Boot:</classname> prompt. +The arrow keys select an item from the menu and any text typed +at the keyboard will appear in the text window. +There are also help screens which can be displayed by pressing +the appropriate function key. +The <classname>General</classname> help screen explains the menu +choices and the <classname>Params</classname> screen explains +the common command line options. + +</para><para> + +Consult the <classname>General</classname> help screen for the +description of the kernels and install modes most appropriate +for your installation. +You should also consult <xref linkend="boot-parms"/> below for any additional +parameters that you may want to set in the <classname>Boot:</classname> +text window. +The kernel version you choose selects the kernel version that will be +used for both the installation process and the installed system. +If you encounter kernel problems with the installation, you may also +have those same problems with the system you install. +The following two steps will select and start the install: + +</para> + +<itemizedlist> + +<listitem><para> +Select the kernel version and installation mode most +appropriate to your needs with the arrow keys. +</para></listitem> + +<listitem><para> +Enter any boot parameters by typing at the keyboard. +The text will be displayed directly in the text window. +This is where kernel parameters (such as serial console +settings) are specified. +</para></listitem> + +<listitem><para> +Press <command>ENTER</command>. This will load and start the +kernel. +The kernel will display its usual initialization messages followed +by the first screen of the Debian Installer. +</para></listitem> + +</itemizedlist> + +<para> + +Proceed to the next chapter to continue the installation where you will +set up the language locale, network, and disk partitions. + +</para> + </sect3> + </sect2> + + <sect2 arch="ia64" id="boot-tftp"><title>Booting with TFTP</title> + +<para> +Booting an IA64 system from the network is similar to a CD boot. +The only difference is how the installation kernel is loaded. +The EFI Boot Manager can load and start programs from a server on +the network. +Once the installation kernel is loaded and starts, the system install +will proceed thru the same steps as the CD install with the exception +that the packages of the base install will be loaded from the network +rather than the CD drive. + +</para> + +&boot-installer-intro-net.xml; + +<para> + +Network booting an ia64 system requires two architecture-specific actions. +On the boot server, DHCP and TFTP must be configured to deliver +<command>elilo</command>. +On the client a new boot option must be defined in the EFI boot manager +to enable loading over a network. + +</para> + + <sect3 arch="ia64" id="boot-tftp-server"> + <title>Configuring the Server</title> +<para> + +A suitable TFTP entry for network booting an ia64 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. + +</para><para> + +Extract the <filename>netboot.tar.gz</filename> file into the directory used +as the root for your tftp server. Typical tftp root directories include +<filename>/var/lib/tftp</filename> and <filename>/tftpboot</filename>. +This will create a <filename>debian-installer</filename> directory +tree containing the boot files for an IA-64 system. + +</para><para> + +<informalexample><screen> +# cd /var/lib/tftp +# tar xvfz /home/user/netboot.tar.gz +./ +./debian-installer/ +./debian-installer/ia64/ +[...] +</screen></informalexample> + +The <filename>netboot.tar.gz</filename> contains an +<filename>elilo.conf</filename> file that should work for most configurations. +However, should you need to make changes to this file, you can find it in the +<filename>debian-installer/ia64/</filename> directory. + +It is possible to have different config files for different clients by naming +them using the client's IP address in hex with the suffix +<filename>.conf</filename> instead of <filename>elilo.conf</filename>. +See documentation provided in the <classname>elilo</classname> package +for details. + +</para> + </sect3> + + <sect3 arch="ia64" id="boot-tftp-client"> + <title>Configuring the Client</title> +<para> + +To configure the client to support TFTP booting, start by booting to +EFI and entering the <guimenu>Boot Option Maintenance Menu</guimenu>. + +<itemizedlist> +<listitem><para> + +Add a boot option. + +</para></listitem> +<listitem><para> + +You should see one or more lines with the text +<guimenuitem>Load File [Acpi()/.../Mac()]</guimenuitem>. If more +than one of these entries exist, choose the one containing the +MAC address of the interface from which you'll be booting. +Use the arrow keys to highlight your choice, then press enter. + +</para></listitem> +<listitem><para> + +Name the entry <userinput>Netboot</userinput> or something similar, +save, and exit back to the boot options menu. + +</para></listitem> +</itemizedlist> + +You should see the new boot option you just created, and selecting it +should initiate a DHCP query, leading to a TFTP load of +<filename>elilo.efi</filename> from the server. + +</para><para> + +The boot loader will display its prompt after it has downloaded and +processed its configuration file. +At this point, the installation proceeds with the same steps as a +CD install. Select a boot option as in above and when the kernel +has completed installing itself from the network, it will start the +Debian Installer. + +</para><para> + +Proceed to the next chapter to continue the installation where +you will set up the language locale, network, and the disk partitions. + +</para> + </sect3> + </sect2> diff --git a/ca/boot-installer/intro-cd.xml b/ca/boot-installer/intro-cd.xml new file mode 100644 index 000000000..fa8770197 --- /dev/null +++ b/ca/boot-installer/intro-cd.xml @@ -0,0 +1,40 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 --> + +<para> + +La manera més fàcil per a la majoria de la gent serà utilitzar +un conjunt de CD de Debian. +Si disposeu d'un conjunt de CD i el vostre ordinador permet arrencar +directament des del CD, fantàstic! Només +<phrase arch="i386"> +heu de configurar el sistema perquè arrenqui des d'un CD tal i com es +descriu a <xref linkend="boot-dev-select"/>, +</phrase> +inseriu el CD, reinicieu l'ordinador i passeu al següent capítol. + +</para><para> + +Recordeu que alguns dispositius de CD poden necessitar controladors +especials i pot ser que aquests no siguin accessibles en els +primers passos de la instal·lació. Si el mètode estàndard +d'arrencada des d'un CD no us funciona al vostre ordinador, torneu +a repassar el capítol i pareu atenció a la utilització de nuclis +i mètodes d'instal·lació alternatius que probablement us funcionin. + +</para><para> + +Tot i que no pugueu arrencar des d'un CD, probablement podeu utilitzar-lo +per instal·lar els components del sistema debian i qualsevol paquet. +Simplement heu d'arrencar utilitzant un altre mitjà com podria +ser un disc. A l'hora d'instal·lar el sistema operatiu, el sistema +base i qualsevol paquet addicional, enllaceu el sistema +d'instal·lació amb el dispositiu CD-ROM. + +</para><para> + +Si teniu problemes en l'arrencada, vegeu +<xref linkend="boot-troubleshooting"/>. + +</para> + diff --git a/ca/boot-installer/intro-hd.xml b/ca/boot-installer/intro-hd.xml new file mode 100644 index 000000000..f494737e2 --- /dev/null +++ b/ca/boot-installer/intro-hd.xml @@ -0,0 +1,16 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 --> + +<para> + +L'arrencada des d'un sistema operatiu existent sovint és una opció +convenient. Per a alguns sistemes és l'únic mètode d'instal·lació +suportat. + +</para><para> + +Per arrencar l'instal·lador des d'un disc dur, prèviament haureu +d'haver baixat els fitxers necessaris +<xref linkend="boot-drive-files"/>. + +</para> diff --git a/ca/boot-installer/intro-net.xml b/ca/boot-installer/intro-net.xml new file mode 100644 index 000000000..cc1cd2a67 --- /dev/null +++ b/ca/boot-installer/intro-net.xml @@ -0,0 +1,19 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 11648 --> + +<para> + +Per arrencar des de la xarxa necessitareu una connexió +i un servidor d'arrencada de xarxa TFTP (DHCP, RARP o BOOTP). + +</para><para arch="hppa"> + +Els sistemes antics com el 715 poden necessitar utilitzar un servidor +d'RBOOT en comptes d'un BOOTP. + +</para><para> + +El mètode d'instal·lació per suportar l'arrencada de la xarxa és descriu a +<xref linkend="install-tftp"/>. + +</para> diff --git a/ca/boot-installer/m68k.xml b/ca/boot-installer/m68k.xml new file mode 100644 index 000000000..1dc18c6ec --- /dev/null +++ b/ca/boot-installer/m68k.xml @@ -0,0 +1,371 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 30283 untranslated --> + + <sect2 arch="m68k"><title>Choosing an Installation Method</title> + +<para> + +Some &arch-title; subarchs have the option of booting using either a +2.4.x or 2.2.x linux kernel. When such a choice exists, try the 2.4.x +linux kernel. The installer should also require less memory when using +a 2.4.x linux kernel as 2.2.x support requires a fixed-sized ramdisk +and 2.4.x uses tmpfs. + +</para><para condition="etch"> + +If you are using a 2.2.x linux kernel, then you need to use the &ramdisksize; +kernel parameter. + +</para><para> + +</para><para condition="sarge"> + +Also, if you are using a 2.2.x linux kernel, then you must make sure you +are using a ramdisk built to accommodate it, see the +<ulink url="&disturl;/main/installer-&architecture;/current/images/MANIFEST">MANIFEST</ulink>. +In general, this means you need to use the initrd22.gz ramdisk from the respective +directory. + +</para><para> + +Make sure <userinput>root=/dev/ram</userinput> is one of your kernel +parameters. + +</para><para> + +If you're having trouble, check +<ulink url="&url-m68k-cts-faq;">cts's &arch-title; debian-installer FAQ</ulink>. + +</para> + +<itemizedlist> + <listitem><para><xref linkend="m68k-boot-amiga"/></para></listitem> + <listitem><para><xref linkend="m68k-boot-atari"/></para></listitem> + <listitem><para><xref linkend="m68k-boot-bvme6000"/></para></listitem> + <listitem><para><xref linkend="m68k-boot-mac"/></para></listitem> + <listitem><para><xref linkend="m68k-boot-mvme"/></para></listitem> + <listitem><para><xref linkend="m68k-boot-q40"/></para></listitem> +</itemizedlist> + + + <sect3 id="m68k-boot-amiga"><title>Amiga</title> +<para> + +The only method of installation available to amiga is the hard drive +(see <xref linkend="m68k-boot-hd"/>). +<emphasis>In other words the cdrom is not bootable.</emphasis> + +</para><para> + +Amiga does not currently work with bogl, so if +you are seeing bogl errors, you need to include the kernel parameter +<userinput>debian-installer/framebuffer=false</userinput>. + +</para> + </sect3> + + <sect3 id="m68k-boot-atari"><title>Atari</title> +<para> + +The installer for atari may be started from either the hard +drive (see <xref linkend="m68k-boot-hd"/>) or from floppies +(see <xref linkend="boot-from-floppies"/>). +<emphasis>In other words the cdrom is not bootable.</emphasis> + +</para><para> + +Atari does not currently work with bogl, so if +you are seeing bogl errors, you need to include the kernel parameter +<userinput>debian-installer/framebuffer=false</userinput>. + +</para> + </sect3> + + <sect3 id="m68k-boot-bvme6000"><title>BVME6000</title> +<para> + +The installer for BVME6000 may be started from a cdrom +(see <xref linkend="m68k-boot-cdrom"/>), floppies +(see <xref linkend="boot-from-floppies"/>), or the net +(see <xref linkend="boot-tftp"/>). + +</para> + </sect3> + + <sect3 id="m68k-boot-mac"><title>Macintosh</title> +<para> + +The only method of installation available to mac is from +the hard drive (see <xref linkend="m68k-boot-hd"/>). +<emphasis>In other words the cdrom is not bootable.</emphasis> +Macs do not have a working 2.4.x kernel. + +</para><para> + +If your hardware uses a 53c9x-based scsi bus, then you may need to +include the kernel parameter <userinput>mac53c9x=1,0</userinput>. +Hardware with two such scsi buses, such as the Quadra 950, will need +<userinput>mac53c9x=2,0</userinput> instead. Alternatively, the +parameter can be specified as <userinput>mac53c9x=-1,0</userinput> +which will leave autodetection on, but which will disable SCSI +disconnects. Note that specifying this parameter is only necessary +if you have more than one hard disk; otherwise, the system will run +faster if you do not specify it. + +</para> + </sect3> + + <sect3 id="m68k-boot-mvme"><title>MVME147 and MVME16x</title> +<para> + +The installer for MVME147 and MVME16x may be started from +either floppies (see <xref linkend="boot-from-floppies"/>) +or the net (see <xref linkend="boot-tftp"/>). +<emphasis>In other words the cdrom is not bootable.</emphasis> + +</para> + </sect3> + + <sect3 id="m68k-boot-q40"><title>Q40/Q60</title> +<para> + +The only method of installation available to Q40/Q60 is +from the hard drive (see <xref linkend="m68k-boot-hd"/>). +<emphasis>In other words the cdrom is not bootable.</emphasis> + +</para> + </sect3> + + </sect2> + + <sect2 arch="m68k" id="m68k-boot-hd"><title>Booting from a Hard Disk</title> + +&boot-installer-intro-hd.xml; + +<para> + +At least six different ramdisks may be used to boot from the hard +drive, three different types each with and without support for a +2.2.x linux kernel (see +<ulink url="&disturl;/main/installer-&architecture;/current/images/MANIFEST">MANIFEST</ulink> +for details). + +</para><para> + +The three different types of ramdisks are <filename>cdrom</filename>, +<filename>hd-media</filename>, and <filename>nativehd</filename>. These +ramdisks differ only in their source for installation packages. +The <filename>cdrom</filename> ramdisk uses a cdrom to get +debian-installer packages. The <filename>hd-media</filename> ramdisk +uses an iso image file of a cdrom currently residing on a hard disk. +Finally, the <filename>nativehd</filename> ramdisk uses the net to +install packages. + +</para> + +<itemizedlist> + <listitem><para><xref linkend="m68k-boothd-amiga"/></para></listitem> + <listitem><para><xref linkend="m68k-boothd-atari"/></para></listitem> + <listitem><para><xref linkend="m68k-boothd-mac"/></para></listitem> + <listitem><para><xref linkend="m68k-boothd-q40"/></para></listitem> +</itemizedlist> + + + <sect3 id="m68k-boothd-amiga"><title>Booting from AmigaOS</title> +<para> + +In the <command>Workbench</command>, start the Linux installation +process by double-clicking on the <guiicon>StartInstall</guiicon> icon +in the <filename>debian</filename> directory. + +</para><para> + +You may have to press the &enterkey; key twice after the Amiga +installer program has output some debugging information into a window. +After this, the screen will go grey, there will be a few seconds' +delay. Next, a black screen with white text should come up, displaying +all kinds of kernel debugging information. These messages may scroll +by too fast for you to read, but that's OK. After a couple of +seconds, the installation program should start automatically, so you +can continue down at <xref linkend="d-i-intro"/>. + +</para> + </sect3> + + + <sect3 id="m68k-boothd-atari"><title>Booting from Atari TOS</title> +<para> + +At the GEM desktop, start the Linux installation process by +double-clicking on the <guiicon>bootstra.prg</guiicon> icon in the +<filename>debian</filename> directory and clicking +<guibutton>Ok</guibutton> at the program options dialog box. + +</para><para> + +You may have to press the &enterkey; key after the Atari +bootstrap program has output some debugging information into a +window. After this, the screen will go grey, there will be a few +seconds' delay. Next, a black screen with white text should come up, +displaying all kinds of kernel debugging information. These messages +may scroll by too fast for you to read, but that's OK. After a couple +of seconds, the installation program should start automatically, so +you can continue below at <xref linkend="d-i-intro"/>. + +</para> + </sect3> + + + <sect3 id="m68k-boothd-mac"><title>Booting from MacOS</title> +<para> + +You must retain the original Mac system and +boot from it. It is <emphasis>essential</emphasis> that, when booting +MacOS in preparation for booting the Penguin linux loader, you +hold the <keycap>shift</keycap> key down to prevent extensions from +loading. If you don't use MacOS except for loading linux, you can +accomplish the same thing by removing all extensions and control +panels from the Mac's System Folder. Otherwise extensions may be left +running and cause random problems with the running linux kernel. + +</para><para> + +Macs require the <command>Penguin</command> +bootloader. If you do not have the tools to handle +a <command>Stuffit</command> archive, &penguin19.hfs; is an +hfs disk image with <command>Penguin</command> unpacked. +<xref linkend="create-floppy"/> describes how to copy this +image to a floppy. + +</para><para> + +At the MacOS desktop, start the Linux installation process by +double-clicking on the <guiicon>Penguin Prefs</guiicon> icon in +the <filename>Penguin</filename> directory. The +<command>Penguin</command> booter will start up. Go to the +<guimenuitem>Settings</guimenuitem> item in the +<guimenu>File</guimenu> menu, click the +<guilabel>Kernel</guilabel> tab. Select the kernel +(<filename>vmlinuz</filename>) and ramdisk +(<filename>initrd.gz</filename>) images in the +<filename>install</filename> directory by clicking on the corresponding +buttons in the upper right corner, and navigating the file select +dialogs to locate the files. + +</para><para> + +To set the boot parameters in Penguin, choose <guimenu>File</guimenu> -> +<guimenuitem>Settings...</guimenuitem>, then switch to the +<guilabel>Options</guilabel> tab. Boot parameters may be typed in to +the text entry area. If you will always want to use these settings, +select <guimenu>File</guimenu> -> <guimenuitem>Save Settings as +Default</guimenuitem>. + +</para><para> + +Close the <guilabel>Settings</guilabel> +dialog, save the settings and start the bootstrap using the +<guimenuitem>Boot Now</guimenuitem> item in the +<guimenu>File</guimenu> menu. + +</para><para> + +The <command>Penguin</command> booter will output some debugging +information into a window. After this, the screen will go grey, there +will be a few seconds' delay. Next, a black screen with white text +should come up, displaying all kinds of kernel debugging +information. These messages may scroll by too fast for you to read, +but that's OK. After a couple of seconds, the installation program +should start automatically, so you can continue below at +<xref linkend="d-i-intro"/>. + +</para> + + </sect3> + + <sect3 id="m68k-boothd-q40"><title>Booting from Q40/Q60</title> + +<para> + +FIXME + +</para><para> + +The installation program should start automatically, so you can +continue below at <xref linkend="d-i-intro"/>. + +</para> + + </sect3> + </sect2> + + + <sect2 arch="m68k" id="m68k-boot-cdrom"><title>Booting from a CD-ROM</title> +<para> + +Currently, the only &arch-title; subarchitecture that +supports CD-ROM booting is the BVME6000. + +</para> + +&boot-installer-intro-cd.xml; + + </sect2> + + + <sect2 arch="m68k" id="boot-tftp"><title>Booting with TFTP</title> + +&boot-installer-intro-net.xml; + +<para> + +After booting the VMEbus systems you will be presented with the LILO +<prompt>Boot:</prompt> prompt. At that prompt enter one of the +following to boot Linux and begin installation proper of the Debian +software using vt102 terminal emulation: + +<!-- Because the &enterkey; definition uses <keycap>, --> +<!-- we use <screen> instead of <userinput> in this list --> + +<itemizedlist> +<listitem><para> + +type <screen>i6000 &enterkey;</screen> to install a BVME4000/6000 + +</para></listitem> +<listitem><para> + +type <screen>i162 &enterkey;</screen> to install an MVME162 + +</para></listitem> +<listitem><para> + +type <screen>i167 &enterkey;</screen> to install an MVME166/167 + +</para></listitem> + </itemizedlist> + +</para><para> + +You may additionally append the string +<screen>TERM=vt100</screen> to use vt100 terminal emulation, +e.g., <screen>i6000 TERM=vt100 &enterkey;</screen>. + +</para> + </sect2> + + + <sect2 arch="m68k" id="boot-from-floppies"> + <title>Booting from Floppies</title> +<para> + +For most &arch-title; architectures, booting from a local filesystem is the +recommended method. + +</para><para> + +Booting from the boot floppy is supported only for Atari and VME +(with a SCSI floppy drive on VME) at this time. + +</para> + </sect2> diff --git a/ca/boot-installer/mips.xml b/ca/boot-installer/mips.xml new file mode 100644 index 000000000..f237aa957 --- /dev/null +++ b/ca/boot-installer/mips.xml @@ -0,0 +1,100 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 24663 untranslated --> + + + <sect2 arch="mips" id="boot-tftp"><title>Booting with TFTP</title> + + <sect3> + <title>SGI Indys TFTP Booting</title> +<para> + +After entering the command monitor use + +<informalexample><screen> +bootp(): +</screen></informalexample> + +on SGI Indys 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. + +</para> + </sect3> + + <sect3> + <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="mips"><title>Boot Parameters</title> + + <sect3> + <title>SGI Indys TFTP Booting</title> +<para> + +On SGI Indys you can append boot parameters to the +<command>bootp():</command> command in the command monitor. + +</para><para> + +Following the <command>bootp():</command> command you can give the +path and name of the file to boot if you did not give an explicit name +via your bootp/dhcp server. Example: + +<informalexample><screen> +bootp():/boot/tftpboot.img +</screen></informalexample> + +Further kernel parameters can be passed via <command>append</command>: + +<informalexample><screen> +bootp(): append="root=/dev/sda1" +</screen></informalexample> + +</para> + </sect3> + + <sect3> + <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> diff --git a/ca/boot-installer/mipsel.xml b/ca/boot-installer/mipsel.xml new file mode 100644 index 000000000..8bb5106b5 --- /dev/null +++ b/ca/boot-installer/mipsel.xml @@ -0,0 +1,12 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 24701 --> + + <sect2 arch="mipsel"> + <title></title> +<para> + +<!-- Placeholder document; please write and include in + boot-installer.xml and build/templates/docstruct.ent --> + +</para> + </sect2> diff --git a/ca/boot-installer/parameters.xml b/ca/boot-installer/parameters.xml new file mode 100644 index 000000000..280204c83 --- /dev/null +++ b/ca/boot-installer/parameters.xml @@ -0,0 +1,323 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 25171 --> + + <sect1 id="boot-parms"><title>Paràmetres d'arrencada</title> +<para> + +Els paràmetres d'arrencada són paràmetres del nucli de Linux que +s'utilitzen per assegurar que els perifèrics es gestionen +correctament. En la majoria de casos el nucli és capaç +de detectar automàticament la informació dels perifèrics. +Tot i això, en algunes ocasions haureu d'ajudar-lo. + +</para><para> + +Si és la primera vegada que arrenqueu el sistema utilitzeu +els paràmetres d'arrencada predeterminats (ex. no intenteu +especificar cap paràmetre) i observeu si s'executa +correctament; probablement ho farà. Si no és el cas, +podeu tornar a arrencar més tard i buscar qualsevol +paràmetre especial que informi al sistema respecte +al vostre maquinari. + +</para><para> + +Podeu trobar informació referent a molts paràmetre de l'arrencada a +<ulink url="http://www.tldp.org/HOWTO/BootPrompt-HOWTO.html">Linux +BootPrompt HOWTO</ulink>, inclosos alguns trucs per a maquinari +obscur. Aquesta secció conté únicament una representació dels paràmetres +més destacats. Podeu trobar una petita selecció dels problemes més +habituals a <xref linkend="boot-troubleshooting"/>. + +</para><para> + +A l'inici de l'arrencada del nucli hauria d'aparèixer el missatge + +<informalexample><screen> +Memòria:<replaceable>dispo</replaceable>k/<replaceable>total</replaceable>k disponible +</screen></informalexample> + +<replaceable>total</replaceable> hauria d'indicar la quantitat +total de RAM en kilobytes. Si no coincideix amb la quantitat de RAM que +teniu instal·lada utilitzeu el paràmetre +<userinput>mem=<replaceable>ram</replaceable></userinput>, +on <replaceable>ram</replaceable> correspon a la quantitat de memòria, +amb el sufix 'k' pels kilobytes, o 'm' per les megabytes. Per exemple, +<userinput>mem=65536K</userinput> i <userinput>mem=64M</userinput> +corresponen a 65MB de RAM. + +</para><para condition="supports-serial-console"> + +Si esteu arrencant via una consola sèrie el nucli ho detectarà +automàticament <phrase arch="mipsel"> (no en el cas de les estacions +DEC)</phrase>. +Si disposeu d'una tarja de vídeo (framebuffer) i un teclat connectats +a l'ordinador del qual voleu arrencar, hauríeu de passar passar el +paràmetre +<userinput>console=<replaceable>device</replaceable></userinput> +al nucli; <replaceable>device</replaceable> correspon al dispositiu +sèrie, que acostuma a ser similar a <filename>ttyS0</filename>. + +</para><para arch="sparc"> + +Per a l'arquitectura &arch-title; els dispositius sèrie són els +<filename>ttya</filename> o <filename>ttyb</filename>. +D'altra banda, definiu les variables OpenROM <envar>input-device</envar> +i <envar>output-device</envar> com a <filename>ttya</filename>. + +</para> + + <sect2 id="installer-args"><title>Paràmetres de l'instal·lador de Debian</title> +<para> + +El sistema d'instal·lació reconeix un conjunt de paràmetres +d'arrencada<footnote> + +<para> + +Tingueu en compte que el nucli accepta un màxim de 8 paràmetres de línia +d'ordres i 8 paràmetres d'entorn (incloent qualsevol paràmetre afegit de +forma predeterminada per l'instal·lador). Si s'excedeixen aquests números, +els nuclis 2.4 ignoraran qualsevol paràmetre restant i els nuclis 2.6 +produiran un pànic. + +</para> + +</footnote> addicionals que us podrien ser d'utilitat. + +</para> + +<variablelist> +<varlistentry> +<term>debconf/priority</term> +<listitem><para> + +Aquest paràmetre definirà la prioritat més alta dels missatges a mostrar. + +</para><para> + +La instal·lació predeterminada utilitza +<userinput>debconf/priority=high</userinput>. +En aquest cas es mostraran els missatges amb prioritat high i critical, +però s'anul·laran els missatges amb prioritat medium i low. Si +l'instal·lador detecta algun problema, ajustarà la prioritat en +funció de les necessitats que n'esdevinguin. + +</para><para> + +Si utilitzeu el paràmetre d'arrencada +<userinput>debconf/priority=medium</userinput>, se us mostrarà el +menú d'instal·lació i disposareu de més control sobre la instal·lació. +Quan s'utilitza el paràmetre <userinput>debconf/priority=low</userinput> +es mostraran tots els missatges (és equivalent al mètode d'arrencada +<emphasis>expert</emphasis>). En el cas de +<userinput>debconf/priority=critical</userinput>, el sistema +d'instal·lació mostrarà únicament els missatges crítics i +procurarà fer la feina correctament sense mostrar missatges. + + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>DEBIAN_FRONTEND</term> +<listitem><para> + +Aquest paràmetre d'arrencada defineix el tipus d'interfície d'usuari +utilitzat per l'instal·lador. Els possibles paràmetres de configuració +actuals són: + +<itemizedlist> +<listitem> +<para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></para> +</listitem><listitem> +<para><userinput>DEBIAN_FRONTEND=text</userinput></para> +</listitem><listitem> +<para><userinput>DEBIAN_FRONTEND=newt</userinput></para> +</listitem><listitem> +<para><userinput>DEBIAN_FRONTEND=slang</userinput></para> +</listitem><listitem> +<para><userinput>DEBIAN_FRONTEND=ncurses</userinput></para> +</listitem><listitem> +<para><userinput>DEBIAN_FRONTEND=bogl</userinput></para> +</listitem><listitem> +<para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> +</listitem><listitem> +<para><userinput>DEBIAN_FRONTEND=corba</userinput></para> +</listitem> +</itemizedlist> + +El tipus predeterminat és +<userinput>DEBIAN_FRONTEND=newt</userinput>. +En el cas de les instal·lacions a través de la consola sèrie s'acostuma +a utilitzar +<userinput>DEBIAN_FRONTEND=text</userinput>. En general, l'únic tipus +disponible en el mitjà d'instal·lació predeterminat és el +<userinput>newt</userinput>, i per tant actualment no és molt útil. + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>BOOT_DEBUG</term> +<listitem><para> + +Utilitzant aquest paràmetre d'arrencada induirà l'arrencada a mostrar +més missatges. + +<variablelist> +<varlistentry> +<term><userinput>BOOT_DEBUG=0</userinput></term> +<listitem><para>És el valor predeterminat.</para></listitem> +</varlistentry> + +<varlistentry> +<term><userinput>BOOT_DEBUG=1</userinput></term> +<listitem><para>Més missatges de l'habitual.</para></listitem> +</varlistentry> + +<varlistentry> +<term><userinput>BOOT_DEBUG=2</userinput></term> +<listitem><para>Molta informació de depuració.</para></listitem> +</varlistentry> + +<varlistentry> +<term><userinput>BOOT_DEBUG=3</userinput></term> +<listitem><para> + +Durant el procés d'arrencada s'executen diversos intèrprets d'ordres +que permeten una depuració més detallada. Per continuar l'arrencada +hareu de sortir de l'intèrpret d'ordres. + +</para></listitem> +</varlistentry> +</variablelist> + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>INSTALL_MEDIA_DEV</term> +<listitem><para> + +El valor del paràmetre correspon al camí al dispositiu des del qual +carregar l'instal·lador de Debian. Per exemple, +<userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</userinput> + +</para><para> + +El disquet d'arrencada, que normalment escaneja tots els disquets +i dispositius USB d'emmagatzematge per trobar el disquet arrel, es +pot substituir per aquest paràmetre per forçar que únicament busqui +en aquest dispositiu. + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>debian-installer/framebuffer</term> +<listitem><para> + +Algunes arquitectures utilitzen el framebuffer del nucli per oferir +la instal·lació en diferents idiomes. Si el framebuffer us provoca +errors al sistema, podeu habilitar la característica utilitzant +el paràmetre <userinput>debian-installer/framebuffer=false</userinput>. +Els símptomes del problema són missatges d'error referents al +bogl, una pantalla en blanc o que es quedi congelat durant uns quants +minuts després d'iniciar la instal·lació. + +</para><para arch="i386"> + +Per inhabilitar el framebuffer també podeu utilitzar l'argument +<userinput>video=vga16:off</userinput>. La problemàtica relacionada +amb aquest paràmetre s'ha detectat en ordinadors Dell Inspiron +amb una tarja Mobile Radeon. + +</para><para arch="m68k"> + +La problemàtica s'ha detectat a l'Amiga 1220 i SE/30. + +</para><para arch="hppa"> + +La problemàtica s'ha detectat a l'hppa. + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>debian-installer/probe/usb</term> +<listitem><para> + +Si l'intent d'arrencada a través d'USB us genera problemes, +el podeu evitar seleccionant <userinput>false</userinput>. + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>netcfg/disable_dhcp</term> +<listitem><para> + +El &d-i; procura, per defecte, configurar la xarxa automàticament +utilitzant el DHCP. Si la configuració es realitza correctament +no podreu revisar-ne i modificar-ne els paràmetres obtinguts. +L'accés a la configuració manual de la xarxa només es donarà +quan falli la configuració per DHCP. + +</para><para> + +Si en la vostra xarxa local disposeu d'un servidor de DHCP però +no el voleu utilitzar, perquè per exemple us retorna respostes +incorrectes, podeu evitar-lo i introduir la informació manualment +utilitzant el paràmetre <userinput>netfcg/disable_dhcp=true</userinput>. + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>hw-detect/start_pcmcia</term> +<listitem><para> + +Si us causa problemes i per evitar que s'iniciïn els serveis +PCMCIA trieu <userinput>false</userinput>. Aquest comportament +s'ha detectat en alguns ordinadors portàtils. + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>preseed/url</term> +<listitem><para> + +Especifica l'URL que enllaça a un fitxer de preconfiguració +a baixar i utilitzar per automatitzar la instal·lació. +Per a més informació vegeu <xref linkend="automatic-install"/>. + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>preseed/file</term> +<listitem><para> + +Especifica l'URL que enllaça a un fitxer de preconfiguració +a carregar per automatitzar la instal·lació. Per a més +informació vegeu <xref linkend="automatic-install"/> + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>ramdisk_size</term> +<listitem><para> + +Si utilitzeu un nucli 2.2.x, probablement haureu d'especificar +la &ramdisksize;. + +</para></listitem> +</varlistentry> + +</variablelist> + </sect2> + </sect1> + diff --git a/ca/boot-installer/powerpc.xml b/ca/boot-installer/powerpc.xml new file mode 100644 index 000000000..214c176d4 --- /dev/null +++ b/ca/boot-installer/powerpc.xml @@ -0,0 +1,247 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + <sect2 arch="powerpc" id="boot-cd"><title>Booting from a CD-ROM</title> + +&boot-installer-intro-cd.xml; + +<para> + +Currently, the only &arch-title; subarchitectures that support CD-ROM +booting are PReP and New World PowerMacs. On PowerMacs, hold the +<keycap>c</keycap> key, or else the combination of +<keycap>Command</keycap>, <keycap>Option</keycap>, +<keycap>Shift</keycap>, and <keycap>Delete</keycap> +keys together while booting to boot from the CD-ROM. + +</para><para> + +OldWorld PowerMacs will not boot a Debian CD, because OldWorld +computers relied on a Mac OS ROM CD boot driver to be present on the CD, +and a free-software version of this driver is not available. All +OldWorld systems have floppy drives, so use the floppy drive to launch +the installer, and then point the installer to the CD for the needed +files. + +</para><para> + +If your system doesn't boot directly from CD-ROM, you can still use +the CD-ROM to install the system. On NewWorlds, you can also use an +OpenFirmware command to boot from the CD-ROM manually. Follow the +instructions in <xref linkend="boot-newworld"/> for booting from +the hard disk, except use the path to <command>yaboot</command> on the +CD at the OF prompt, such as + +<informalexample><screen> +0 > boot cd:,\install\yaboot +</screen></informalexample> + +</para> + </sect2> + + <sect2 arch="powerpc" id="install-drive"> + <title>Booting from Hard Disk</title> + +&boot-installer-intro-hd.xml; + + <sect3><title>Booting CHRP from OpenFirmware</title> + +<para> + + <emphasis>Not yet written.</emphasis> + +</para> + </sect3> + + <sect3><title>Booting OldWorld PowerMacs from MacOS</title> +<para> + +If you set up BootX in <xref linkend="files-oldworld"/>, you can +use it to boot into the installation system. Double click the +<guiicon>BootX</guiicon> application icon. Click on the +<guibutton>Options</guibutton> button and select <guilabel>Use +Specified RAM Disk</guilabel>. This will give you the +chance to select the <filename>ramdisk.image.gz</filename> file. You +may need to select the <guilabel>No Video Driver</guilabel> checkbox, +depending on your hardware. Then click the +<guibutton>Linux</guibutton> button to shut down MacOS and launch the +installer. + +</para> + </sect3> + + + <sect3 id="boot-newworld"> + <title>Booting NewWorld Macs from OpenFirmware</title> +<para> + +You will have already placed the <filename>vmlinux</filename>, +<filename>initrd.gz</filename>, <filename>yaboot</filename>, and +<filename>yaboot.conf</filename> files at the root level of your HFS +partition in <xref linkend="files-newworld"/>. +Restart the computer, and immediately (during the chime) hold down the +<keycap>Option</keycap>, <keycap>Command (cloverleaf/Apple)</keycap>, +<keycap>o</keycap>, and <keycap>f</keycap> keys all together. After +a few seconds you will be presented with the Open Firmware prompt. +At the prompt, type + +<informalexample><screen> +0 > boot hd:<replaceable>x</replaceable>,yaboot +</screen></informalexample> + +replacing <replaceable>x</replaceable> with the partition number of +the HFS partition where the +kernel and yaboot files were placed, followed by a &enterkey;. On some +machines, you may need to use <userinput>ide0:</userinput> instead of +<userinput>hd:</userinput>. In a few more seconds you will see a +yaboot prompt + +<informalexample><screen> +boot: +</screen></informalexample> + +At yaboot's <prompt>boot:</prompt> prompt, type either +<userinput>install</userinput> or <userinput>install video=ofonly</userinput> +followed by a &enterkey;. The +<userinput>video=ofonly</userinput> argument is for maximum +compatibility; you can try it if <userinput>install</userinput> +doesn't work. The Debian installation program should start. + +</para> + </sect3> + </sect2> + + <sect2 arch="powerpc" id="usb-boot"> + <title>Booting from USB memory stick</title> +<para> + +Currently, NewWorld PowerMac systems are known to support USB booting. + +</para> + +<para> + +Make sure you have prepared everything from <xref +linkend="boot-usb-files"/>. To boot a Macintosh system from a USB stick, +you will need to use the Open Firmware prompt, since Open Firmware does +not search USB storage devices by default. +<!-- TODO: although it could be made to; watch this space --> +To get to the prompt, hold down +<keycombo><keycap>Command</keycap> <keycap>Option</keycap> +<keycap>o</keycap> <keycap>f</keycap></keycombo> all together while +booting (see <xref linkend="invoking-openfirmware"/>). + +</para><para> + +You will need to work out where the USB storage device appears in the +device tree, since at the moment <command>ofpath</command> cannot work +that out automatically. Type <userinput>dev / ls</userinput> and +<userinput>devalias</userinput> at the Open Firmware prompt to get a +list of all known devices and device aliases. On the author's system +with various types of USB stick, paths such as +<filename>usb0/disk</filename>, <filename>usb0/hub/disk</filename>, +<filename>/pci@f2000000/usb@1b,1/disk@1</filename>, and +<filename>/pci@f2000000/usb@1b,1/hub@1/disk@1</filename> work. + +</para><para> + +Having worked out the device path, use a command like this to boot the +installer: + +<informalexample><screen> +boot <replaceable>usb0/disk</replaceable>:<replaceable>2</replaceable>,\\:tbxi +</screen></informalexample> + +The <replaceable>2</replaceable> matches the Apple_HFS or +Apple_Bootstrap partition onto which you copied the boot image earlier, +and the <userinput>,\\:tbxi</userinput> part instructs Open Firmware to +boot from the file with an HFS file type of "tbxi" (i.e. +<command>yaboot</command>) in the directory previously blessed with +<command>hattrib -b</command>. + +</para><para> + +The system should now boot up, and you should be presented with the +<prompt>boot:</prompt> prompt. Here you can enter optional boot +arguments, or just hit &enterkey;. + +</para><warning><para> + +This boot method is new, and may be difficult to get to work on some +NewWorld systems. If you have problems, please file an installation +report, as explained in <xref linkend="submit-bug"/>. + +</para></warning> + </sect2> + + <sect2 arch="powerpc" id="boot-tftp"><title>Booting with TFTP</title> + +&boot-installer-intro-net.xml; + +<para> + +Currently, PReP and New World PowerMac systems support netbooting. + +</para><para> + +On machines with Open Firmware, such as NewWorld Power Macs, enter the +boot monitor (see <xref linkend="invoking-openfirmware"/>) and +use the command <command>boot enet:0</command>. PReP and CHRP boxes +may have different ways of addressing the network. On a PReP machine, +you should try +<userinput>boot <replaceable>server_ipaddr</replaceable>,<replaceable>file</replaceable>,<replaceable>client_ipaddr</replaceable></userinput>. + +</para> + </sect2> + + + <sect2 arch="powerpc"> + <title>Booting from Floppies</title> +<para> + +Booting from floppies is supported for &arch-title;, although it is +generally only applicable for OldWorld systems. NewWorld systems are +not equipped with floppy drives, and attached USB floppy drives are +not supported for booting. + +</para><para> + +You will have already downloaded the floppy images you needed and +created floppies from the images in <xref linkend="create-floppy"/>. + +</para><para> + +To boot from the <filename>boot-floppy-hfs.img</filename> floppy, +place it in floppy drive after shutting the system down, and before +pressing the power-on button. + +</para><note><para> +For those not familiar with Macintosh +floppy operations: a floppy placed in the machine prior to boot will +be the first priority for the system to boot from. A floppy without a +valid boot system will be ejected, and the machine will then check for +bootable hard disk partitions. + +</para></note><para> + +After booting, the <filename>root.bin</filename> floppy is +requested. Insert the root floppy and press &enterkey;. The installer +program is automatically launched after the root system has been +loaded into memory. + +</para> + </sect2> + + + <sect2 arch="powerpc"><title>PowerPC Boot Parameters</title> +<para> + +Many older Apple monitors used a 640x480 67Hz mode. If your video +appears skewed on an older Apple monitor, try appending the boot +argument <userinput>video=atyfb:vmode:6</userinput> , which will +select that mode for most Mach64 and Rage video hardware. For Rage 128 +hardware, this changes to +<userinput>video=aty128fb:vmode:6</userinput> . + +</para> + </sect2> diff --git a/ca/boot-installer/s390.xml b/ca/boot-installer/s390.xml new file mode 100644 index 000000000..dcf89b594 --- /dev/null +++ b/ca/boot-installer/s390.xml @@ -0,0 +1,30 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 --> + + <sect2 arch="s390"><title>Limitacions a s390</title> +<para> + +Per tal de fer servir el sistema d'instal·lació a S/390, necessitareu +una configuració de xarxa que funcioni i una sessió ssh. + +</para><para> + +El procés d'arrencada comença amb una configuració de xarxa que us +preguntarà per diversos paràmetres de xarxa. Si la configuració té +èxit, connectareu al sistema començant una sessió ssh que +llençara el sistema estàndard d'instal·lació. + +</para> + </sect2> + + + <sect2 arch="s390"><title>Paràmetres d'arranc a s390</title> +<para> + +A S/390 podeu afegir paràmetres d'arranc al fitxer «parm». Aquest fitxer pot +estar en format ASCII o EBCDIC. Si us plau llegiu +<ulink url="&url-s390-devices;">Controladors de dispositius i ordres d'instal·lació</ulink> +per a més informació sobre paràmetres d'arranc específics de S/390. + +</para> + </sect2> diff --git a/ca/boot-installer/sparc.xml b/ca/boot-installer/sparc.xml new file mode 100644 index 000000000..81cad25e7 --- /dev/null +++ b/ca/boot-installer/sparc.xml @@ -0,0 +1,89 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + <sect2 arch="sparc" id="boot-tftp"><title>Booting with TFTP</title> + +&boot-installer-intro-net.xml; + +<para> + +On machines with OpenBoot, simply enter the boot monitor on the +machine which is being installed (see +<xref linkend="invoking-openboot"/>). +Use the command <userinput>boot net</userinput> to boot from a TFTP +and RARP server, or try <userinput>boot net:bootp</userinput> or +<userinput>boot net:dhcp</userinput> to boot from a TFTP and BOOTP +or DHCP server. Some older OpenBoot revisions require using +the device name, such as <userinput>boot le()</userinput>; these +probably don't support BOOTP nor DHCP. + +</para> + </sect2> + + + <sect2 arch="sparc"><title>Booting from a CD-ROM</title> + +&boot-installer-intro-cd.xml; + +<para> + +Most OpenBoot versions support the <userinput>boot cdrom</userinput> +command which is simply an alias to boot from the SCSI device on ID 6 +(or the secondary master for IDE based systems). You may have to use +the actual device name for older OpenBoot versions that don't support +this special command. Note that some problems have been reported on Sun4m +(e.g., Sparc 10s and Sparc 20s) systems booting from CD-ROM. + +</para> + </sect2> + + + <sect2 arch="sparc" condition="supports-floppy-boot"> + <title>Booting from Floppies</title> +<para> + +To boot from floppy on a Sparc, use + +<informalexample><screen> +Stop-A -> OpenBoot: "boot floppy" +</screen></informalexample> + +Be warned that the newer Sun4u (ultra) architecture does not support +floppy booting. A typical error message is <computeroutput>Bad magic +number in disk label - Can't open disk label package</computeroutput>. +Furthermore, a number of Sun4c models (such as the IPX) do not support +the compressed images found on the disks, so also are not supported. + +</para><para> + +Several Sparcs (e.g. Ultra 10) have an OBP bug that prevents them from +booting (instead of not supporting booting at all). The appropriate +OBP update can be downloaded as product ID 106121 from +<ulink url="http://sunsolve.sun.com"></ulink>. + +</para><para> + +If you are booting from the floppy, and you see messages such as + +<informalexample><screen> +Fatal error: Cannot read partition +Illegal or malformed device name +</screen></informalexample> + +then it is possible that floppy booting is simply not supported on +your machine. + +</para> + </sect2> + + <sect2 arch="sparc"><title>IDPROM Messages</title> +<para> + +If you cannot boot because you get messages about a problem with +<quote>IDPROM</quote>, then it's possible that your NVRAM battery, which +holds configuration information for you firmware, has run out. See the +<ulink url="&url-sun-nvram-faq;">Sun NVRAM FAQ</ulink> for more +information. + +</para> + </sect2> diff --git a/ca/boot-installer/trouble.xml b/ca/boot-installer/trouble.xml new file mode 100644 index 000000000..831d6aab5 --- /dev/null +++ b/ca/boot-installer/trouble.xml @@ -0,0 +1,274 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + <sect1 id="boot-troubleshooting"> + <title>Troubleshooting the Installation Process</title> +<para> +</para> + + <sect2 condition="supports-floppy-boot" id="unreliable-floppies"> + <title>Floppy Disk Reliability</title> + +<para> + +The biggest problem for people using floppy disks to install Debian +seems to be floppy disk reliability. + +</para><para> + +The boot floppy is the floppy with the worst problems, because it +is read by the hardware directly, before Linux boots. Often, the +hardware doesn't read as reliably as the Linux floppy disk driver, and +may just stop without printing an error message if it reads incorrect +data. There can also be failures in the Driver Floppies most of which +indicate themselves with a flood of messages about disk I/O errors. + +</para><para> + +If you are having the installation stall at a particular floppy, the +first thing you should do is re-download the floppy disk image and +write it to a <emphasis>different</emphasis> floppy. Simply +reformatting the old +floppy may not be sufficient, even if it appears that the floppy was +reformatted and written with no errors. It is sometimes useful to try +writing the floppy on a different system. + +</para><para> + +One user reports he had to write the images to floppy +<emphasis>three</emphasis> times before one worked, and then +everything was fine with the third floppy. + +</para><para> + +Other users have reported that simply rebooting a few times with the +same floppy in the floppy drive can lead to a successful boot. This is +all due to buggy hardware or firmware floppy drivers. + +</para> + </sect2> + + <sect2><title>Boot Configuration</title> + +<para> + +If you have problems and the kernel hangs during the boot process, +doesn't recognize peripherals you actually have, or drives are not +recognized properly, the first thing to check is the boot parameters, +as discussed in <xref linkend="boot-parms"/>. + +</para><para> + +If you are booting with your own kernel instead of the one supplied +with the installer, be sure that <userinput>CONFIG_DEVFS</userinput> is set in +your kernel. The installer requires +<userinput>CONFIG_DEVFS</userinput>. + +</para><para> + +Often, problems can be solved by removing add-ons and peripherals, and +then trying booting again. <phrase arch="i386">Internal modems, sound +cards, and Plug-n-Play devices can be especially problematic.</phrase> + +</para><para> + +If you have a large amount of memory installed in your machine, more +than 512M, and the installer hangs when booting the kernel, you may +need to include a boot argument to limit the amount of memory the +kernel sees, such as <userinput>mem=512m</userinput>. + +</para> + </sect2> + + <sect2 arch="i386" id="i386-boot-problems"> + <title>Common &arch-title; Installation Problems</title> +<para> + +There are some common installation problems that can be solved or avoided by +passing certain boot parameters to the installer. + +</para><para> + +Some systems have floppies with <quote>inverted DCLs</quote>. If you receive +errors reading from the floppy, even when you know the floppy is good, +try the parameter <userinput>floppy=thinkpad</userinput>. + +</para><para> + +On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506 +disk drivers), the IDE drive may not be properly recognized. Again, +try it first without the parameters and see if the IDE drive is +recognized properly. If not, determine your drive geometry +(cylinders, heads, and sectors), and use the parameter +<userinput>hd=<replaceable>cylinders</replaceable>,<replaceable>heads</replaceable>,<replaceable>sectors</replaceable></userinput>. + +</para><para> + +If you have a very old machine, and the kernel hangs after saying +<computeroutput>Checking 'hlt' instruction...</computeroutput>, then +you should try the <userinput>no-hlt</userinput> boot argument, which +disables this test. + +</para><para> + +If your screen begins to show a weird picture while the kernel boots, +eg. pure white, pure black or colored pixel garbage, your system may +contain a problematic video card which does not switch to the +framebuffer mode properly. Then you can use the boot parameter +<userinput>debian-installer/framebuffer=false</userinput> or +<userinput>video=vga16:off</userinput> to disable the framebuffer +console. Only the English +language will be available during the installation due to limited +console features. See <xref linkend="boot-parms"/> for details. + +</para> + + <sect3> + <title>System Freeze During the PCMCIA Configuration Phase</title> +<para> + +Some laptop models produced by Dell are known to crash when PCMCIA device +detection tries to access some hardware addresses. Other laptops may display +similar problems. If you experience such a problem and you don't need PCMCIA +support during the installation, you can disable PCMCIA using the +<userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can +then configure PCMCIA after the installation is completed and exclude the +resource range causing the problems. + +</para><para> + +Alternatively, you can boot the installer in expert mode. You will +then be asked to enter the resource range options your hardware +needs. For example, if you have one of the Dell laptops mentioned +above, you should enter <userinput>exclude port +0x800-0x8ff</userinput> here. There is also a list of some common +resource range options in the <ulink +url="http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12">System +resource settings section of the PCMCIA HOWTO</ulink>. Note that you +have to omit the commas, if any, when you enter this value in the +installer. + +</para> + </sect3> + + <sect3> + <title>System Freeze while Loading the USB Modules</title> +<para> + +The kernel normally tries to install USB modules and the USB keyboard driver +in order to support some non-standard USB keyboards. However, there are some +broken USB systems where the driver hangs on loading. A possible workaround +may be disabling the USB controller in your mainboard BIOS setup. Another option +is passing the <userinput>debian-installer/probe/usb=false</userinput> parameter +at the boot prompt, which will prevent the modules from being loaded. + +</para> + </sect3> + </sect2> + + <sect2 id="kernel-msgs"> + <title>Interpreting the Kernel Startup Messages</title> + +<para> + +During the boot sequence, you may see many messages in the form +<computeroutput>can't find <replaceable>something</replaceable> +</computeroutput>, or <computeroutput> +<replaceable>something</replaceable> not present</computeroutput>, +<computeroutput>can't initialize <replaceable>something</replaceable> +</computeroutput>, or even <computeroutput>this driver release depends +on <replaceable>something</replaceable> </computeroutput>. +Most of these messages are harmless. You +see them because the kernel for the installation system is built to +run on computers with many different peripheral devices. Obviously, no +one computer will have every possible peripheral device, so the +operating system may emit a few complaints while it looks for +peripherals you don't own. You may also see the system pause for a +while. This happens when it is waiting for a device to respond, and +that device is not present on your system. If you find the time it +takes to boot the system unacceptably long, you can create a +custom kernel later (see <xref linkend="kernel-baking"/>). + +</para> + </sect2> + + + <sect2 id="problem-report"> + <title>Bug Reporter</title> +<para> + +If you get through the initial boot phase but cannot complete the +install, the bug reporter menu choice may be helpful. It copies system +error logs and configuration information to a user-supplied floppy. +This information may provide clues as to what went wrong and how to +fix it. If you are submitting a bug report you may want to attach +this information to the bug report. + +</para><para> + +Other pertinent installation messages may be found in +<filename>/var/log/</filename> during the +installation, and <filename>/var/log/debian-installer/</filename> +after the computer has been booted into the installed system. + +</para> + </sect2> + + <sect2 id="submit-bug"> + <title>Submitting Installation Reports</title> +<para> + +If you still have problems, please submit an installation report. We also +encourage installation reports to be sent even if the installation is +successful, so that we can get as much information as possible on the largest +number of hardware configurations. Please use this template when filling out +installation reports, and file the report as a bug report against the +<classname>installation-reports</classname> pseudo package, by sending it to +<email>submit@bugs.debian.org</email>. + +<informalexample><screen> +Package: installation-reports + +Debian-installer-version: <Fill in date and from where you got the image> +uname -a: <The result of running uname -a on a shell prompt> +Date: <Date and time of the install> +Method: <How did you install? What did you boot off? If network + install, from where? Proxied?> + +Machine: <Description of machine (eg, IBM Thinkpad R32)> +Processor: +Memory: +Root Device: <IDE? SCSI? Name of device?> +Root Size/partition table: <Feel free to paste the full partition + table, with notes on which partitions are mounted where.> +Output of lspci and lspci -n: + +Base System Installation Checklist: +[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it + +Initial boot worked: [ ] +Configure network HW: [ ] +Config network: [ ] +Detect CD: [ ] +Load installer modules: [ ] +Detect hard drives: [ ] +Partition hard drives: [ ] +Create file systems: [ ] +Mount partitions: [ ] +Install base system: [ ] +Install boot loader: [ ] +Reboot: [ ] + +Comments/Problems: + +<Description of the install, in prose, and any thoughts, comments + and ideas you had during the initial install.> +</screen></informalexample> + +In the bug report, describe what the problem is, including the last +visible kernel messages in the event of a kernel hang. Describe the +steps that you did which brought the system into the problem state. + +</para> + </sect2> + </sect1> |