|
|
257.
|
|
|
Currently, the only &arch-title; subarchitectures that support CD-ROM booting are PReP (though not all systems) 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.
|
|
|
Tag: para
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:2417
|
|
|
265.
|
|
|
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"/>. You will now have to boot into OpenFirmware (see <xref linkend="invoking-openfirmware"/>). 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. |
|
|
Tag: para
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:2502
|
|
|
274.
|
|
|
On machines with Open Firmware, such as NewWorld Power Macs, enter the boot monitor (see <xref linkend="invoking-openfirmware"/>) and use the command <informalexample><screen>
0 > boot enet:0
</screen></informalexample> If this doesn't work, you might have to add the filename like this: <informalexample><screen>
0 > boot enet:0,yaboot
</screen></informalexample> PReP and CHRP boxes may have different ways of addressing the network. On a PReP machine, you should try <informalexample><screen>
boot net:<replaceable>server_ipaddr</replaceable>,<replaceable>file</replaceable>,<replaceable>client_ipaddr</replaceable>
</screen></informalexample> On some PReP systems (e.g. Motorola PowerStack machines) the command <userinput>help boot</userinput> may give a description of syntax and available options. |
|
|
Tag: para
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:2619
|
|
|
281.
|
|
|
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.
|
|
|
Tag: para
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:2724
|
|
|
289.
|
|
|
If you are booting with a serial console, generally the kernel will autodetect this. If you have a videocard (framebuffer) and a keyboard also attached to the computer which you wish to boot via serial console, you may have to pass the <userinput>console=<replaceable>device</replaceable></userinput> argument to the kernel, where <replaceable>device</replaceable> is your serial device, which is usually something like <filename>ttyS0</filename>.
|
|
|
Tag: para
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:2846
|
|
|
297.
|
|
|
If you add <userinput>priority=medium</userinput> as boot parameter, you will be shown the installation menu and gain more control over the installation. When <userinput>priority=low</userinput> is used, all messages are shown (this is equivalent to the <emphasis>expert</emphasis> boot method). With <userinput>priority=critical</userinput>, the installation system will display only critical messages and try to do the right thing without fuss.
|
|
|
Tag: para
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:2907
|
|
|
299.
|
|
|
This boot parameter controls the type of user interface used for the installer. The current possible parameter settings are: <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=gtk</userinput></para> </listitem> </itemizedlist> The default frontend is <userinput>DEBIAN_FRONTEND=newt</userinput>. <userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial console installs. Generally, only the <userinput>newt</userinput> frontend is available on default install media. On architectures that support it, the graphical installer uses the <userinput>gtk</userinput> frontend.
|
|
|
Tag: para
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:2922
|
|
|
316.
|
|
|
Some architectures use the kernel framebuffer to offer installation in a number of languages. If framebuffer causes a problem on your system you can disable the feature by the parameter <userinput>fb=false</userinput>. Problem symptoms are error messages about bterm or bogl, a blank screen, or a freeze within a few minutes after starting the install.
|
|
|
Tag: para
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:3020
|
|
|
317.
|
|
|
The <userinput>video=vga16:off</userinput> argument may also be used to disable the kernel's use of the framebuffer. Such problems have been reported on a Dell Inspiron with Mobile Radeon card.
|
|
|
Tag: para
|
|
|
|
|
(no translation yet)
|
|
Translated and reviewed by
Paco Molinero
|
|
|
|
Located in
boot-installer.xml:3029
|
|
|
320.
|
|
|
Because of display problems on some systems, framebuffer support is <emphasis>disabled by default</emphasis> for &arch-title;. This can result in ugly display on systems that do properly support the framebuffer, like those with ATI graphical cards. If you see display problems in the installer, you can try booting with parameter <userinput>debian-installer/framebuffer=true</userinput> or <userinput>fb=true</userinput> for short.
|
|
|
Tag: para
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:3043
|
