po/sv/boot-installer.po

# Swedish translation of boot-installer.
# Copyright (C) 2006 Free Software Foundation, Inc.
# Daniel Nylander <po@danielnylander.se>, 2006.
#
msgid ""
msgstr ""
"Project-Id-Version: installation-guide 20051025 boot-installer\n"
"POT-Creation-Date: 2006-03-07 20:30+0000\n"
"PO-Revision-Date: 2006-03-05 09:59+0100\n"
"Last-Translator: Daniel Nylander <po@danielnylander.se>\n"
"Language-Team: Swedish <tp-sv@listor.tp-sv.se>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Tag: title
#: boot-installer.xml:4
#, no-c-format
msgid "Booting the Installation System"
msgstr "Starta upp installationssystemet"

#. Tag: title
#: boot-installer.xml:9
#, no-c-format
msgid "Booting the Installer on &arch-title;"
msgstr "Starta upp installeraren på &arch-title;"

#. Tag: title
#: boot-installer.xml:20
#, no-c-format
msgid "Alpha Console Firmware"
msgstr "Konsollfirmware för Alpha"

#. Tag: para
#: boot-installer.xml:21
#, no-c-format
msgid ""
"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:"
msgstr ""
"Konsollfirmware lagras i ett flash-rom och startas när ett Alpha-system slås "
"på eller startas om. Det finns två olika konsollspecifikationer som används "
"på Alpha-system och därför finns två klasser av konsollfirmware tillgängliga:"

#. Tag: para
#: boot-installer.xml:31
#, no-c-format
msgid ""
"<emphasis>SRM console</emphasis>, based on the Alpha Console Subsystem "
"specification, which provides an operating environment for OpenVMS, Tru64 "
"UNIX, and Linux operating systems."
msgstr ""
"<emphasis>SRM-konsoll</emphasis>, baserad på specifikationen Alpha Console "
"Subsystem, som tillhandahåller ett operativmiljö för operativsystemen "
"OpenVMS, Tru64 UNIX och Linux."

#. Tag: para
#: boot-installer.xml:38
#, no-c-format
msgid ""
"<emphasis>ARC, AlphaBIOS, or ARCSBIOS console</emphasis>, based on the "
"Advanced RISC Computing (ARC) specification, which provides an operating "
"environment for Windows NT."
msgstr ""
"<emphasis>ARC, AlphaBIOS eller ARCSBIOS-konsoll</emphasis>, baserad på "
"specifikationen Advanced RISC Computing (ARC), som tillhandahåller en "
"operativmiljö för Windows NT."

#. Tag: para
#: boot-installer.xml:47
#, no-c-format
msgid ""
"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."
msgstr ""
"Från användarens perspektiv är den mest viktiga skillnaden mellan SRM och "
"ARC den att valet av konsoll begränsar det möjliga diskpartitionsschemat för "
"hårddisken som du önskar starta upp från."

#. Tag: para
#: boot-installer.xml:54
#, no-c-format
msgid ""
"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."
msgstr ""
"ARC kräver att du använder en MS-DOS-partitionstabell (som skapas av "
"<command>cfdisk</command>) för uppstartsdisken. Därför är MS-DOS-"
"partitionstabeller det <quote>ursprungliga</quote> partitionsformatet vid "
"uppstarter från ARC. Faktum är att eftersom AlphaBIOS innehåller ett "
"diskpartitioneringsverktyg kanske du föredrar att partitionera dina diskar "
"från firmwaremenyerna före installation av Linux."

#. Tag: para
#: boot-installer.xml:63
#, no-c-format
msgid ""
"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."
msgstr ""
"Motsatt är SRM <emphasis>inkompatibel</emphasis><footnote> <para> Specifikt "
"är formatet på uppstartssektorn som krävs av Console Subsystem Specification "
"i konflikt med placeringen av DOS-partitionstabellen. </para> </footnote> "
"med MS-DOS-partitionstabeller. Eftersom Tru64 Unix använder formatet för BSD-"
"disketiketter, är det här det ursprungliga (<quote>native</quote>) "
"partitionsformatet för SRM-installationer."

#. Tag: para
#: boot-installer.xml:76
#, no-c-format
msgid ""
"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."
msgstr ""
"GNU/Linux är det enda operativsystemet på Alpha som kan startas upp från "
"båda konsolltyperna, men &debian; &release; har endast stöd för uppstart på "
"SRM-baserade system. Om du har en Alpha som det inte finns någon SRM-version "
"tillgänglig för, om du vill använda dubbel-uppstart tillsammans med Windows "
"NT, eller om din uppstartsenhet kräver stöd för ARC-konsoll för initiering "
"av BIOS kommer du inte kunna använda installeraren för &debian; &release;. "
"Du kan fortfarande köra &debian; &release; på sådana system genom att "
"använda andra installationsmedia, till exempel kan du installera Debian "
"woody med MILO och uppgradera."

#. Tag: para
#: boot-installer.xml:87
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:95
#, no-c-format
msgid ""
"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."
msgstr ""
"Följande tabell sammanställer tillgängliga och systemtyper/"
"konsollkombinationer som stöds (se <xref linkend=\"alpha-cpus\"/> för namnen "
"på systemtyperna). Ordet <quote>ARC</quote> nedan below indikerar någon av "
"de ARC-godkända konsollerna."

#. Tag: entry
#: boot-installer.xml:107
#, no-c-format
msgid "System Type"
msgstr "Systemtyp"

#. Tag: entry
#: boot-installer.xml:108
#, no-c-format
msgid "Console Type Supported"
msgstr "Konsolltyper som stöds"

#. Tag: entry
#: boot-installer.xml:114
#, no-c-format
msgid "alcor"
msgstr "alcor"

#. Tag: entry
#: boot-installer.xml:115 boot-installer.xml:118 boot-installer.xml:124
#: boot-installer.xml:130 boot-installer.xml:133 boot-installer.xml:136
#: boot-installer.xml:139 boot-installer.xml:145 boot-installer.xml:148
#: boot-installer.xml:151 boot-installer.xml:160 boot-installer.xml:169
#: boot-installer.xml:184 boot-installer.xml:187
#, no-c-format
msgid "ARC or SRM"
msgstr "ARC eller SRM"

#. Tag: entry
#: boot-installer.xml:117
#, no-c-format
msgid "avanti"
msgstr "avanti"

#. Tag: entry
#: boot-installer.xml:120
#, no-c-format
msgid "book1"
msgstr "book1"

#. Tag: entry
#: boot-installer.xml:121 boot-installer.xml:127 boot-installer.xml:142
#: boot-installer.xml:154 boot-installer.xml:163 boot-installer.xml:166
#: boot-installer.xml:172 boot-installer.xml:178 boot-installer.xml:181
#, no-c-format
msgid "SRM only"
msgstr "Endast SRM"

#. Tag: entry
#: boot-installer.xml:123
#, no-c-format
msgid "cabriolet"
msgstr "cabriolet"

#. Tag: entry
#: boot-installer.xml:126
#, no-c-format
msgid "dp264"
msgstr "dp264"

#. Tag: entry
#: boot-installer.xml:129
#, no-c-format
msgid "eb164"
msgstr "eb164"

#. Tag: entry
#: boot-installer.xml:132
#, no-c-format
msgid "eb64p"
msgstr "eb64p"

#. Tag: entry
#: boot-installer.xml:135
#, no-c-format
msgid "eb66"
msgstr "eb66"

#. Tag: entry
#: boot-installer.xml:138
#, no-c-format
msgid "eb66p"
msgstr "eb66p"

#. Tag: entry
#: boot-installer.xml:141
#, no-c-format
msgid "jensen"
msgstr "jensen"

#. Tag: entry
#: boot-installer.xml:144
#, no-c-format
msgid "lx164"
msgstr "lx164"

#. Tag: entry
#: boot-installer.xml:147
#, no-c-format
msgid "miata"
msgstr "miata"

#. Tag: entry
#: boot-installer.xml:150
#, no-c-format
msgid "mikasa"
msgstr "mikasa"

#. Tag: entry
#: boot-installer.xml:153
#, no-c-format
msgid "mikasa-p"
msgstr "mikasa-p"

#. Tag: entry
#: boot-installer.xml:156
#, no-c-format
msgid "nautilus"
msgstr "nautilus"

#. Tag: entry
#: boot-installer.xml:157
#, no-c-format
msgid "ARC (see motherboard manual) or SRM"
msgstr "ARC (se manualen för moderkortet) eller SRM"

#. Tag: entry
#: boot-installer.xml:159
#, no-c-format
msgid "noname"
msgstr "noname"

#. Tag: entry
#: boot-installer.xml:162
#, no-c-format
msgid "noritake"
msgstr "noritake"

#. Tag: entry
#: boot-installer.xml:165
#, no-c-format
msgid "noritake-p"
msgstr "noritake-p"

#. Tag: entry
#: boot-installer.xml:168
#, no-c-format
msgid "pc164"
msgstr "pc164"

#. Tag: entry
#: boot-installer.xml:171
#, no-c-format
msgid "rawhide"
msgstr "rawhide"

#. Tag: entry
#: boot-installer.xml:174
#, no-c-format
msgid "ruffian"
msgstr "ruffian"

#. Tag: entry
#: boot-installer.xml:175 boot-installer.xml:190 boot-installer.xml:193
#, no-c-format
msgid "ARC only"
msgstr "Endast ARC"

#. Tag: entry
#: boot-installer.xml:177
#, no-c-format
msgid "sable"
msgstr "sable"

#. Tag: entry
#: boot-installer.xml:180
#, no-c-format
msgid "sable-g"
msgstr "sable-g"

#. Tag: entry
#: boot-installer.xml:183
#, no-c-format
msgid "sx164"
msgstr "sx164"

#. Tag: entry
#: boot-installer.xml:186
#, no-c-format
msgid "takara"
msgstr "takara"

#. Tag: entry
#: boot-installer.xml:189
#, no-c-format
msgid "<entry>xl</entry>"
msgstr "<entry>xl</entry>"

#. Tag: entry
#: boot-installer.xml:192
#, no-c-format
msgid "<entry>xlt</entry>"
msgstr "<entry>xlt</entry>"

#. Tag: para
#: boot-installer.xml:200
#, no-c-format
msgid ""
"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>."
msgstr ""

#. Tag: para
#: boot-installer.xml:209
#, no-c-format
msgid ""
"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."
msgstr ""
"Följande paragrafer kommer från installationsmanualen för woody och "
"inkluderas här som referens: de kan vara användbara för någon vid ett senare "
"datum när Debian har stöd för MILO-baserade installationer igen."

#. Tag: para
#: boot-installer.xml:215
#, no-c-format
msgid ""
"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>."
msgstr ""

#. Tag: para
#: boot-installer.xml:221
#, no-c-format
msgid ""
"<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>."
msgstr ""

#. Tag: para
#: boot-installer.xml:231
#, no-c-format
msgid ""
"<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>."
msgstr ""

#. Tag: para
#: boot-installer.xml:238
#, no-c-format
msgid ""
"Thus, three scenarios are generally possible, depending on the system's "
"console firmware and whether or not <command>MILO</command> is available: "
"<informalexample><screen>\n"
"SRM -&gt; aboot\n"
"SRM -&gt; MILO\n"
"ARC -&gt; MILO\n"
"</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."
msgstr ""

#. Tag: para
#: boot-installer.xml:253
#, no-c-format
msgid ""
"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;."
msgstr ""

#. Tag: para
#: boot-installer.xml:264
#, no-c-format
msgid ""
"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 &mdash; 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>."
msgstr ""
"Som på andra arkitekturer, bör du installera de senaste tillgängliga "
"revisionen av firmware<footnote> <para> Utom på Jensen, där Linux inte stöds "
"på firmware-versioner senareän 1.7 &mdash; se <ulink url=\"&url-jensen-howto;"
"\"></ulink> för mer information. </para> </footnote> före installation av "
"&debian;. För Alpha, uppdateringar av firmware kan hämtas från <ulink url="
"\"&url-alpha-firmware;\">Alpha Firmware Updates</ulink>."

#. Tag: title
#: boot-installer.xml:283 boot-installer.xml:1007 boot-installer.xml:1498
#: boot-installer.xml:1993 boot-installer.xml:2075 boot-installer.xml:2164
#: boot-installer.xml:2508 boot-installer.xml:2604
#, no-c-format
msgid "Booting with TFTP"
msgstr "Uppstart via TFTP"

#. Tag: para
#: boot-installer.xml:284
#, no-c-format
msgid ""
"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>\n"
"&gt;&gt;&gt; show dev\n"
"ewa0.0.0.9.0               EWA0              08-00-2B-86-98-65\n"
"ewb0.0.0.11.0              EWB0              08-00-2B-86-98-54\n"
"ewc0.0.0.2002.0            EWC0              00-06-2B-01-32-B0\n"
"</screen></informalexample> You first need to set the boot protocol: "
"<informalexample><screen>\n"
"&gt;&gt;&gt; set ewa0_protocol bootp\n"
"</screen></informalexample> Then check the medium type is correct: "
"<informalexample><screen>\n"
"&gt;&gt;&gt; set ewa0_mode <replaceable>mode</replaceable>\n"
"</screen></informalexample> You can get a listing of valid modes with "
"<userinput>&gt;&gt;&gt;set ewa0_mode</userinput>."
msgstr ""

#. Tag: para
#: boot-installer.xml:302
#, no-c-format
msgid ""
"Then, to boot from the first Ethernet interface, you would type: "
"<informalexample><screen>\n"
"&gt;&gt;&gt; boot ewa0 -flags \"\"\n"
"</screen></informalexample> This will boot using the default kernel "
"parameters as included in the netboot image."
msgstr ""
"Sedan, för att starta upp från det första Ethernet-gränssnittet, kan du "
"skriva: <informalexample><screen>\n"
"&gt;&gt;&gt; boot ewa0 -flags \"\"\n"
"</screen></informalexample> Det här kommer att starta upp med de "
"kärnparametrar som är standard och som inkluderats i netboot-avbilden."

#. Tag: para
#: boot-installer.xml:311
#, no-c-format
msgid ""
"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:"
msgstr ""

#. Tag: screen
#: boot-installer.xml:323
#, no-c-format
msgid ""
"&gt;&gt;&gt; boot ewa0 -flags &quot;root=/dev/ram ramdisk_size=16384 "
"console=ttyS0&quot;"
msgstr ""
"&gt;&gt;&gt; boot ewa0 -flags &quot;root=/dev/ram ramdisk_size=16384 "
"console=ttyS0&quot;"

#. Tag: title
#: boot-installer.xml:328
#, no-c-format
msgid "Booting from CD-ROM with the SRM Console"
msgstr "Uppstart från cd-rom med SRM-konsoll"

#. Tag: para
#: boot-installer.xml:329
#, no-c-format
msgid ""
"Type <informalexample><screen>\n"
"&gt;&gt;&gt; boot xxxx -flags 0\n"
"</screen></informalexample> where <replaceable>xxxx</replaceable> is your CD-"
"ROM drive in SRM notation."
msgstr ""
"Ange <informalexample><screen>\n"
"&gt;&gt;&gt; boot xxxx -flags 0\n"
"</screen></informalexample> där <replaceable>xxxx</replaceable> är din cd-"
"rom-enhet i SRM-notation."

#. Tag: title
#: boot-installer.xml:341
#, no-c-format
msgid "Booting from CD-ROM with the ARC or AlphaBIOS Console"
msgstr "Uppstart från cd-rom med ARC eller AlphaBIOS-konsoll"

#. Tag: para
#: boot-installer.xml:342
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: title
#: boot-installer.xml:358
#, no-c-format
msgid "Booting from Floppies with the SRM Console"
msgstr "Uppstart från startdisketter med SRM-konsoll"

#. Tag: para
#: boot-installer.xml:359
#, no-c-format
msgid ""
"At the SRM prompt (<prompt>&gt;&gt;&gt;</prompt>), issue the following "
"command: <informalexample><screen>\n"
"&gt;&gt;&gt; boot dva0 -flags 0\n"
"</screen></informalexample> possibly replacing <filename>dva0</filename> "
"with the actual device name. Usually, <filename>dva0</filename> is the "
"floppy; type <informalexample><screen>\n"
"&gt;&gt;&gt; show dev\n"
"</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."
msgstr ""

#. Tag: para
#: boot-installer.xml:376
#, no-c-format
msgid ""
"If you want to specify kernel parameters when booting via <command>aboot</"
"command>, use the following command: <informalexample><screen>\n"
"&gt;&gt;&gt; boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 "
"load_ramdisk=1 arguments\"\n"
"</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>."
msgstr ""
"Om du vill ange kärnparametrar vid uppstart med <command>aboot</command>, "
"använd följande kommando: <informalexample><screen>\n"
"&gt;&gt;&gt; boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 "
"load_ramdisk=1 arguments\"\n"
"</screen></informalexample> (angivet på en rad), som ersätter, om "
"nödvändigt, det faktiska namnet på uppstartsenheten i SRM för "
"<filename>dva0</filename>, namnet för uppstartsenheten för Linux för "
"<filename>fd0</filename>, och de önskade kärnparametrarna för "
"<filename>arguments</filename>."

#. Tag: para
#: boot-installer.xml:388
#, no-c-format
msgid ""
"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\"/>."
msgstr ""
"Om du vill ange kärnparametrar vid uppstart med <command>MILO</command>, "
"måste du avbryta bootstrap när du kommit in i MILO. Se <xref linkend="
"\"booting-from-milo\"/>."

#. Tag: title
#: boot-installer.xml:398
#, no-c-format
msgid "Booting from Floppies with the ARC or AlphaBIOS Console"
msgstr "Uppstart från startdisketter med ARC eller AlphaBIOS-konsoll"

#. Tag: para
#: boot-installer.xml:400
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: title
#: boot-installer.xml:409
#, no-c-format
msgid "Booting with MILO"
msgstr "Uppstart med MILO"

#. Tag: para
#: boot-installer.xml:410
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:416
#, no-c-format
msgid ""
"If you want to specify all the bits explicitly (for example, to supply "
"additional parameters), you can use a command like this: "
"<informalexample><screen>\n"
"MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 <!-- arguments -->\n"
"</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."
msgstr ""

#. Tag: title
#: boot-installer.xml:435
#, no-c-format
msgid "Booting from TFTP"
msgstr "Uppstart från TFTP"

#. Tag: para
#: boot-installer.xml:441 boot-installer.xml:1013 boot-installer.xml:1516
#: boot-installer.xml:1999 boot-installer.xml:2514 boot-installer.xml:2610
#, no-c-format
msgid ""
"Booting from the network requires that you have a network connection and a "
"TFTP network boot server (DHCP, RARP, or BOOTP)."
msgstr ""
"Uppstart från nätverket kräver att du har en nätverksanslutning och en TFTP-"
"server konfigurerad för uppstarter (DHCP, RARP eller BOOTP)."

#. Tag: para
#: boot-installer.xml:446 boot-installer.xml:1018 boot-installer.xml:1521
#: boot-installer.xml:2004 boot-installer.xml:2519 boot-installer.xml:2615
#, no-c-format
msgid ""
"Older systems such as the 715 might require the use of an RBOOT server "
"instead of a BOOTP server."
msgstr ""

#. Tag: para
#: boot-installer.xml:451 boot-installer.xml:1023 boot-installer.xml:1526
#: boot-installer.xml:2009 boot-installer.xml:2524 boot-installer.xml:2620
#, no-c-format
msgid ""
"The installation method to support network booting is described in <xref "
"linkend=\"install-tftp\"/>."
msgstr ""
"Installationsmetoden som har stöd för nätverksuppstart finns beskriven i "
"<xref linkend=\"install-tftp\"/>."

#. Tag: title
#: boot-installer.xml:459
#, fuzzy, no-c-format
msgid "Booting from TFTP on Netwinder"
msgstr "Uppstart från TFTP på NetWinder"

#. Tag: para
#: boot-installer.xml:460
#, no-c-format
msgid ""
"Netwinders have two network interfaces: A 10Mbps NE2000-compatible card "
"(which is generally referred to as <literal>eth0</literal>) and a 100Mbps "
"Tulip card. There may be problems loading the image via TFTP using the "
"100Mbps card so it is recommended that you use the 10Mbps interfaced (the "
"one labeled with <literal>10 Base-T</literal>)."
msgstr ""

#. Tag: para
#: boot-installer.xml:469
#, no-c-format
msgid ""
"You need NeTTrom 2.2.1 or later to boot the installation system, and version "
"2.3.3 is recommended. Unfortunately, firmware files are currently not "
"available for download because of license issues. If this situation changes, "
"you may find new images at <ulink url=\"http//www.netwinder.org/\"></ulink>."
msgstr ""

#. Tag: para
#: boot-installer.xml:477
#, no-c-format
msgid ""
"When you boot your Netwinder you have to interrupt the boot process during "
"the countdown. This allows you to set a number of firmware settings needed "
"in order to boot the installer. First of all, start by loading the default "
"settings: <informalexample><screen>\n"
"    NeTTrom command-&gt; load-defaults\n"
"</screen></informalexample> Furthermore, you must configure the network, "
"either with a static address: <informalexample><screen>\n"
"    NeTTrom command-&gt; setenv netconfig_eth0 flash\n"
"    NeTTrom command-&gt; setenv eth0_ip 192.168.0.10/24\n"
"</screen></informalexample> where 24 is the number of set bits in the "
"netmask, or a dynamic address: <informalexample><screen>\n"
"    NeTTrom command-&gt; setenv netconfig_eth0 dhcp\n"
"</screen></informalexample> You may also need to configure the "
"<userinput>route1</userinput> settings if the TFTP server is not on the "
"local subnet. Following these settings, you have to specify the TFTP server "
"and the location of the image. You can then store your settings to flash. "
"<informalexample><screen>\n"
"    NeTTrom command-&gt; setenv kerntftpserver 192.168.0.1\n"
"    NeTTrom command-&gt; setenv kerntftpfile boot.img\n"
"    NeTTrom command-&gt; save-all\n"
"</screen></informalexample> Now you have to tell the firmware that the TFTP "
"image should be booted: <informalexample><screen>\n"
"    NeTTrom command-&gt; setenv kernconfig tftp\n"
"    NeTTrom command-&gt; setenv rootdev /dev/ram\n"
"</screen></informalexample> If you use a serial console to install your "
"Netwinder, you need to add the following setting: <informalexample><screen>\n"
"    NeTTrom command-&gt; setenv cmdappend root=/dev/ram "
"console=ttyS0,115200\n"
"</screen></informalexample> Alternatively, for installations using a "
"keyboard and monitor you have to set: <informalexample><screen>\n"
"    NeTTrom command-&gt; setenv cmdappend root=/dev/ram\n"
"</screen></informalexample> You can use the <command>printenv</command> "
"command to review your environment settings. After you have verified that "
"the settings are correct, you can load the image: <informalexample><screen>\n"
"    NeTTrom command-&gt; boot\n"
"</screen></informalexample> In case you run into any problems, a detailed "
"HOWTO is <ulink url=\"http://www.netwinder.org/howto/Firmware-HOWTO.html\"></"
"ulink> is available."
msgstr ""

#. Tag: title
#: boot-installer.xml:529
#, no-c-format
msgid "Booting from TFTP on CATS"
msgstr "Uppstart från TFTP på CATS"

#. Tag: para
#: boot-installer.xml:530
#, no-c-format
msgid ""
"On CATS machines, use <command>boot de0:</command> or similar at the Cyclone "
"prompt."
msgstr ""

#. Tag: title
#: boot-installer.xml:540
#, no-c-format
msgid "Booting from CD-ROM"
msgstr "Uppstart från cd-rom"

#. Tag: para
#: boot-installer.xml:546 boot-installer.xml:716 boot-installer.xml:1135
#: boot-installer.xml:1956 boot-installer.xml:2296 boot-installer.xml:2650
#, no-c-format
msgid ""
"The easiest route for most people will be to use a set of Debian CDs. If you "
"have a CD set, and if your machine supports booting directly off the CD, "
"great! Simply <phrase arch=\"i386\"> configure your system for booting off a "
"CD as described in <xref linkend=\"boot-dev-select\"/>, </phrase> insert "
"your CD, reboot, and proceed to the next chapter."
msgstr ""
"Den enklaste vägen för de flesta personer är att använda en uppsättning "
"Debian-cd-skivor. Om du har en cd-uppsättning och om din maskin har stöd för "
"att starta upp direkt från cd, bra! Bara att <phrase arch=\"i386\"> "
"konfigurera ditt system för att starta upp från en cd som beskrivs i <xref "
"linkend=\"boot-dev-select\"/>, </phrase> mata in din cd, starta om och "
"fortsätt till nästa kapitel."

#. Tag: para
#: boot-installer.xml:557 boot-installer.xml:727 boot-installer.xml:1146
#: boot-installer.xml:1967 boot-installer.xml:2307 boot-installer.xml:2661
#, no-c-format
msgid ""
"Note that certain CD drives may require special drivers, and thus be "
"inaccessible in the early installation stages. If it turns out the standard "
"way of booting off a CD doesn't work for your hardware, revisit this chapter "
"and read about alternate kernels and installation methods which may work for "
"you."
msgstr ""
"Notera att vissa cd-enheter kan kräver speciella drivrutiner och kan därför "
"vara otillgängliga i de tidiga stegen av installationen. Om det visar sig "
"att det vanliga sättet att starta upp från en cd inte fungerar på din "
"hårdvara, besök det här kapitlet igen och läs om alternativa kärnor och "
"installationsmetoder som kan fungera för dig."

#. Tag: para
#: boot-installer.xml:565 boot-installer.xml:735 boot-installer.xml:1154
#: boot-installer.xml:1975 boot-installer.xml:2315 boot-installer.xml:2669
#, no-c-format
msgid ""
"Even if you cannot boot from CD-ROM, you can probably install the Debian "
"system components and any packages you want from CD-ROM. Simply boot using a "
"different media, such as floppies. When it's time to install the operating "
"system, base system, and any additional packages, point the installation "
"system at the CD-ROM drive."
msgstr ""
"Även om du inte kan starta upp från cd-rom kan du antagligen installera "
"Debians systemkomponenter och de paket du vill från cd-rom. Starta helt "
"enkelt upp på ett annat media, såsom disketter. När det är dags att "
"installera operativsystemet, grundsystemet och eventuellt andra paket, peka "
"installationssystemet till cd-rom-enheten."

#. Tag: para
#: boot-installer.xml:573 boot-installer.xml:743 boot-installer.xml:1162
#: boot-installer.xml:1983 boot-installer.xml:2323 boot-installer.xml:2677
#, no-c-format
msgid ""
"If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>."
msgstr ""
"Om du har problem att starta upp, se <xref linkend=\"boot-troubleshooting\"/"
">."

#. Tag: para
#: boot-installer.xml:580
#, no-c-format
msgid ""
"To boot a CD-ROM from the Cyclone console prompt, use the command "
"<command>boot cd0:cats.bin</command>"
msgstr ""

#. Tag: title
#: boot-installer.xml:589
#, fuzzy, no-c-format
msgid "Booting from Firmware"
msgstr "Starta upp CHRP från OpenFirmware"

#. Tag: para
#: boot-installer.xml:595
#, no-c-format
msgid ""
"There is an increasing number of consumer devices that directly boot from a "
"flash chip on the device. The installer can be written to flash so it will "
"automatically start when you reboot your machines."
msgstr ""

#. Tag: para
#: boot-installer.xml:601
#, no-c-format
msgid ""
"In many cases, changing the firmware of an embedded device voids your "
"warranty. Sometimes you are also not able to recover your device if there "
"are problems during the flashing process. Therefore, please take care and "
"follow the steps precisely."
msgstr ""

#. Tag: title
#: boot-installer.xml:612
#, fuzzy, no-c-format
msgid "Booting the NSLU2"
msgstr "Uppstart med MILO"

#. Tag: para
#: boot-installer.xml:613
#, no-c-format
msgid "There are three ways how to put the installer firmware into flash:"
msgstr ""

#. Tag: title
#: boot-installer.xml:619
#, no-c-format
msgid "Using the NSLU2 web interface"
msgstr ""

#. Tag: para
#: boot-installer.xml:620
#, no-c-format
msgid ""
"Go to the administration section and choose the menu item <literal>Upgrade</"
"literal>. You can then browse your disk for the installer image you have "
"previously downloaded. Then press the <literal>Start Upgrade</literal> "
"button, confirm, wait for a few minutes and confirm again. The system will "
"then boot straight into the installer."
msgstr ""

#. Tag: title
#: boot-installer.xml:631
#, no-c-format
msgid "Via the network using Linux/Unix"
msgstr ""

#. Tag: para
#: boot-installer.xml:632
#, no-c-format
msgid ""
"You can use <command>upslug2</command> from any Linux or Unix machine to "
"upgrade the machine via the network. This software is packaged for Debian. "
"First, you have to put your NSLU2 in upgrade mode: <orderedlist> "
"<listitem><para> Disconnect any disks and/or devices from the USB ports. </"
"para></listitem> <listitem><para> Power off the NSLU2 </para></listitem> "
"<listitem><para> Press and hold the reset button (accessible through the "
"small hole on the back just above the power input). </para></listitem> "
"<listitem><para> Press and release the power button to power on the NSLU2. </"
"para></listitem> <listitem><para> Wait for 10 seconds watching the ready/"
"status LED. After 10 seconds it will change from amber to red. Immediately "
"release the reset button. </para></listitem> <listitem><para> The NSLU2 "
"ready/status LED will flash alternately red/green (there is a 1 second delay "
"before the first green). The NSLU2 is now in upgrade mode. </para></"
"listitem> </orderedlist> See the <ulink url=\"http://www.nslu2-linux.org/"
"wiki/OpenSlug/UsingTheBinary\">NSLU2-Linux pages</ulink> if you have "
"problems with this. Once your NSLU2 is in upgrade mode, you can flash the "
"new image: <informalexample><screen>\n"
"sudo upslug2 -i di-nslu2.bin\n"
"</screen></informalexample> Note that the tool also shows the MAC address of "
"your NSLU2, which may come in handy to configure your DHCP server. After the "
"whole image has been written and verified, the system will automatically "
"reboot. Make sure you connect your USB disk again now, otherwise the "
"installer won't be able to find it."
msgstr ""

#. Tag: title
#: boot-installer.xml:693
#, no-c-format
msgid "Via the network using Windows"
msgstr ""

#. Tag: para
#: boot-installer.xml:694
#, no-c-format
msgid ""
"There is <ulink url=\"http://www.everbesthk.com/8-download/sercomm/firmware/"
"all_router_utility.zip\">a tool</ulink> for Windows to upgrade the firmware "
"via the network."
msgstr ""

#. Tag: title
#: boot-installer.xml:710 boot-installer.xml:1129 boot-installer.xml:1944
#: boot-installer.xml:2290 boot-installer.xml:2644
#, no-c-format
msgid "Booting from a CD-ROM"
msgstr "Uppstart från en cd-rom"

#. Tag: title
#: boot-installer.xml:848
#, no-c-format
msgid ""
"Booting from Linux Using <command>LILO</command> or <command>GRUB</command>"
msgstr ""
"Uppstart från Linux med <command>LILO</command> eller <command>GRUB</command>"

#. Tag: para
#: boot-installer.xml:851
#, no-c-format
msgid ""
"To boot the installer from hard disk, you must first download and place the "
"needed files as described in <xref linkend=\"boot-drive-files\"/>."
msgstr ""
"För att starta upp installeraren från hårddisk måste du första hämta och "
"placera de nödvändiga filerna som beskrivs i <xref linkend=\"boot-drive-files"
"\"/>."

#. Tag: para
#: boot-installer.xml:856
#, no-c-format
msgid ""
"If you intend to use the hard drive only for booting and then download "
"everything over the network, you should download the <filename>netboot/"
"debian-installer/i386/initrd.gz</filename> file and its corresponding "
"kernel. This will allow you to repartition the hard disk from which you boot "
"the installer, although you should do so with care."
msgstr ""
"Om du bara tänkte använda hårddisken för att starta upp och sedan hämta allt "
"över nätverket, bör du hämta filen <filename>netboot/debian-installer/i386/"
"initrd.gz</filename> och dess korresponderande kärna. Den låter dig "
"partionera om hårddisken från vilken du startar upp installeraren, fastän du "
"bör göra det med försiktighet."

#. Tag: para
#: boot-installer.xml:864
#, no-c-format
msgid ""
"Alternatively, if you intend to keep an existing partition on the hard drive "
"unchanged during the install, you can download the <filename>hd-media/initrd."
"gz</filename> file and its kernel, as well as copy a CD iso to the drive "
"(make sure the file is named ending in <literal>.iso</literal>). The "
"installer can then boot from the drive and install from the CD image, "
"without needing the network."
msgstr ""
"Alternativt, om du tänker behålla en existerande partition på hårddisken i "
"oförändrat skick under installationen, kan du hämta filen <filename>hd-media/"
"initrd.gz</filename> och dess kärna, såväl som en kopia av en cd-avbild till "
"enheten (se till att filens namn slutar på <literal>.iso</literal>). "
"Installeraren kan sedan starta upp från enheten och installera från cd-"
"avbilden, utan behov av nätverk."

#. Tag: para
#: boot-installer.xml:873
#, no-c-format
msgid ""
"For <command>LILO</command>, you will need to configure two essential things "
"in <filename>/etc/lilo.conf</filename>: <itemizedlist> <listitem><para> to "
"load the <filename>initrd.gz</filename> installer at boot time; </para></"
"listitem> <listitem><para> have the <filename>vmlinuz</filename> kernel use "
"a RAM disk as its root partition. </para></listitem> </itemizedlist> Here is "
"a <filename>/etc/lilo.conf</filename> example:"
msgstr ""
"För <command>LILO</command>, behöver du konfigurera två viktiga saker i "
"<filename>/etc/lilo.conf</filename>: <itemizedlist> <listitem><para> för att "
"läsa in <filename>initrd.gz</filename> installeraren vid uppstart; </para></"
"listitem> <listitem><para> få kärnan <filename>vmlinuz</filename> att "
"använda en RAM-disk som sin rotpartition. </para></listitem> </itemizedlist> "
"Här är ett exempel på en <filename>/etc/lilo.conf</filename>:"

#. Tag: screen
#: boot-installer.xml:894
#, no-c-format
msgid ""
"image=/boot/newinstall/vmlinuz\n"
"       label=newinstall\n"
"       initrd=/boot/newinstall/initrd.gz\n"
"       root=/dev/ram0\n"
"       append=\"ramdisk_size=12000\""
msgstr ""
"image=/boot/newinstall/vmlinuz\n"
"       label=newinstall\n"
"       initrd=/boot/newinstall/initrd.gz\n"
"       root=/dev/ram0\n"
"       append=\"ramdisk_size=12000\""

#. Tag: para
#: boot-installer.xml:894
#, no-c-format
msgid ""
"For more details, refer to the <citerefentry><refentrytitle>initrd</"
"refentrytitle> <manvolnum>4</manvolnum></citerefentry> and "
"<citerefentry><refentrytitle>lilo.conf</refentrytitle> <manvolnum>5</"
"manvolnum></citerefentry> man pages. Now run <userinput>lilo</userinput> and "
"reboot."
msgstr ""
"För fler detaljer, referera till manualsidorna "
"<citerefentry><refentrytitle>initrd</refentrytitle> <manvolnum>4</"
"manvolnum></citerefentry> och <citerefentry><refentrytitle>lilo.conf</"
"refentrytitle> <manvolnum>5</manvolnum></citerefentry>. Kör nu "
"<userinput>lilo</userinput> och starta om."

#. Tag: para
#: boot-installer.xml:903
#, no-c-format
msgid ""
"The procedure for <command>GRUB</command> is quite similar. Locate your "
"<filename>menu.lst</filename> in the <filename>/boot/grub/</filename> "
"directory (sometimes in the <filename>/boot/boot/grub/</filename>), add the "
"following lines: <informalexample><screen>\n"
"title  New Install\n"
"kernel (hd0,0)/boot/newinstall/vmlinuz root=/dev/ram0 ramdisk_size=12000\n"
"initrd (hd0,0)/boot/newinstall/initrd.gz\n"
"</screen></informalexample> and reboot."
msgstr ""
"Proceduren för <command>GRUB</command> är ganska lik. Leta upp din "
"<filename>menu.lst</filename> i katalogen <filename>/boot/grub/</filename>  "
"(ibland finns den i <filename>/boot/boot/grub/</filename>), lägg till "
"följande rader: <informalexample><screen>\n"
"title  Ny installation\n"
"kernel (hd0,0)/boot/newinstall/vmlinuz root=/dev/ram0 ramdisk_size=12000\n"
"initrd (hd0,0)/boot/newinstall/initrd.gz\n"
"</screen></informalexample> och starta om."

#. Tag: para
#: boot-installer.xml:914
#, no-c-format
msgid ""
"Note that the value of the <userinput>ramdisk_size</userinput> may need to "
"be adjusted for the size of the initrd image. From here on, there should be "
"no difference between <command>GRUB</command> or <command>LILO</command>."
msgstr ""
"Notera att värden för <userinput>ramdisk_size</userinput> kan behöva "
"justeras efter initrd-avbildens storlek. Från och med nu bör det inte vara "
"några skillnader mellan <command>GRUB</command> och <command>LILO</command>."

#. Tag: title
#: boot-installer.xml:925
#, no-c-format
msgid "Booting from USB Memory Stick"
msgstr "Uppstart från USB-minne"

#. Tag: para
#: boot-installer.xml:926
#, no-c-format
msgid ""
"Let's assume you have prepared everything from <xref linkend=\"boot-dev-"
"select\"/> and <xref linkend=\"boot-usb-files\"/>. Now just plug your USB "
"stick into some free USB connector and reboot the computer. The system "
"should boot up, and you should be presented with the <prompt>boot:</prompt> "
"prompt. Here you can enter optional boot arguments, or just hit &enterkey;."
msgstr ""
"Låt oss anta att du har förberett allt från <xref linkend=\"boot-dev-select"
"\"/> och <xref linkend=\"boot-usb-files\"/>. Anslut ditt USB-minne i någon "
"ledig USB-kontakt och starta om datorn. Systemet bör starta upp och du bör "
"se prompten <prompt>boot:</prompt>. Här kan du ange ytterligare "
"uppstartsargument eller bara trycka &enterkey;."

#. Tag: para
#: boot-installer.xml:935
#, no-c-format
msgid ""
"In case your computer doesn't support booting from USB memory devices, you "
"can still use a single floppy to do the initial boot and then switch to USB. "
"Boot your system as described in <xref linkend=\"floppy-boot\"/>; the kernel "
"on the boot floppy should detect your USB stick automatically. When it asks "
"for the root floppy, simply press &enterkey;. You should see &d-i; starting."
msgstr ""
"I fall att din dator inte har stöd för uppstart från USB-minnesenheter kan "
"du fortfarande använda en enda diskett för att göra den initiala uppstarten "
"och sedan byta till USB. Starta upp ditt system som beskrivs i <xref linkend="
"\"floppy-boot\"/>; kärnan på startdisketten ska automatiskt identifiera ditt "
"USB-minne. När den frågar efter rotdisketten, tryck bara &enterkey;. Du bör "
"nu se &d-i; starta."

#. Tag: title
#: boot-installer.xml:948 boot-installer.xml:2056 boot-installer.xml:2550
#: boot-installer.xml:2698
#, no-c-format
msgid "Booting from Floppies"
msgstr "Uppstart från startdisketter"

#. Tag: para
#: boot-installer.xml:949 boot-installer.xml:2558
#, no-c-format
msgid ""
"You will have already downloaded the floppy images you needed and created "
"floppies from the images in <xref linkend=\"create-floppy\"/>."
msgstr ""
"Du ska redan ha hämtat diskettavbilderna du behövde och skapat disketterna "
"från avbilderna i <xref linkend=\"create-floppy\"/>."

#. Tag: para
#: boot-installer.xml:956
#, no-c-format
msgid ""
"To boot from the installer boot floppy, place it in the primary floppy "
"drive, shut down the system as you normally would, then turn it back on."
msgstr ""
"För att starta upp från installerarens startdiskett, placera den i primära "
"diskettenheten, stäng ner systemet som vanligt och starta upp det igen."

#. Tag: para
#: boot-installer.xml:962
#, no-c-format
msgid ""
"For installing from an LS-120 drive (ATAPI version) with a set of floppies, "
"you need to specify the virtual location for the floppy device. This is done "
"with the <emphasis>root=</emphasis> boot argument, giving the device that "
"the ide-floppy driver maps the device to. For example, if your LS-120 drive "
"is connected as the first IDE device (master) on the second cable, you enter "
"<userinput>linux root=/dev/hdc</userinput> at the boot prompt. Installation "
"from LS-120 is only supported by 2.4 and later kernels."
msgstr ""
"För att installera från en LS-120-enhet (ATAPI-versionen) med en uppsättning "
"disketter, behöver du ange den virtuella platsen för diskettenheten. Det här "
"gör man med uppstartargumentet <emphasis>root=</emphasis>, som anger enheten "
"som drivrutinen kan mappa enheten till. Till exempel, om din LS-120-enhet är "
"ansluten som första IDE-enhet (master) på andra kabeln, anger du "
"<userinput>linux root=/dev/hdc</userinput> vid uppstartsprompten. "
"Installation från LS-120 stöds endast av kärnor i 2.4-serien och senare."

#. Tag: para
#: boot-installer.xml:973
#, no-c-format
msgid ""
"Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</"
"keycap> <keycap>Delete</keycap></keycombo> does not properly reset the "
"machine, so a <quote>hard</quote> reboot is recommended. If you are "
"installing from an existing operating system (e.g., from a DOS box) you "
"don't have a choice. Otherwise, please do a hard reboot when booting."
msgstr ""
"Notera att på vissa maskiner, <keycombo><keycap>Control</keycap> "
"<keycap>Alt</keycap> <keycap>Delete</keycap></keycombo> återställer inte "
"korrekt maskinen, så en <quote>hård</quote> omstart rekommenderas. Om du "
"installerar från ett existerande operativsystem (exempelvis från en DOS-"
"burk) har du inget val. Om inte, vänligen gör en hård omstart vid uppstart."

#. Tag: para
#: boot-installer.xml:982
#, no-c-format
msgid ""
"The floppy disk will be accessed, and you should then see a screen that "
"introduces the boot floppy and ends with the <prompt>boot:</prompt> prompt."
msgstr ""
"Disketten kommer att läsas från och du bör sedan se en skärm som "
"introducerar startdisketten och slutar med prompten <prompt>boot:</prompt>."

#. Tag: para
#: boot-installer.xml:988
#, no-c-format
msgid ""
"Once you press &enterkey;, you should see the message "
"<computeroutput>Loading...</computeroutput>, followed by "
"<computeroutput>Uncompressing Linux...</computeroutput>, and then a "
"screenfull or so of information about the hardware in your system. More "
"information on this phase of the boot process can be found below in <xref "
"linkend=\"kernel-msgs\"/>."
msgstr ""
"När du trycker &enterkey;, bör du se meddelandet <computeroutput>Loading...</"
"computeroutput>, följt av <computeroutput>Uncompressing Linux...</"
"computeroutput>, och sedan en skärm full av information om hårdvaran i ditt "
"system. Mer information angående den här fasen i uppstartsprocessen kan "
"hittas under i <xref linkend=\"kernel-msgs\"/>."

#. Tag: para
#: boot-installer.xml:997
#, no-c-format
msgid ""
"After booting from the boot floppy, the root floppy is requested. Insert the "
"root floppy and press &enterkey;, and the contents are loaded into memory. "
"The installer program <command>debian-installer</command> is automatically "
"launched."
msgstr ""
"Efter uppstart från startdisketten kommer rotdisketten att efterfrågas. Mata "
"in rotdisketten och tryck &enterkey;, och dess innehåll kommer att läsas in "
"i minnet. Installeringsprogrammet <command>debian-installer</command> "
"startas automatiskt."

#. Tag: para
#: boot-installer.xml:1031
#, no-c-format
msgid "There are various ways to do a TFTP boot on i386."
msgstr "Det finns olika sätt att göra en TFTP-uppstart på i386."

#. Tag: title
#: boot-installer.xml:1037
#, no-c-format
msgid "NIC or Motherboard that support PXE"
msgstr "Nätverkskort eller moderkort med stöd för PXE"

#. Tag: para
#: boot-installer.xml:1038
#, no-c-format
msgid ""
"It could be that your Network Interface Card or Motherboard provides PXE "
"boot functionality. This is a <trademark class=\"trade\">Intel</trademark> "
"re-implementation of TFTP boot. If so you may be able to configure your BIOS "
"to boot from the network."
msgstr ""
"Det kan vara så att ditt nätverkskort eller moderkort erbjuder "
"funktionalitet för uppstart via PXE. Det är en åter-implementation av TFTP-"
"uppstart från <trademark class=\"trade\">Intel</trademark>. Om så är fallet "
"kan du konfigurera ditt BIOS att starta upp från nätverket."

#. Tag: title
#: boot-installer.xml:1049
#, no-c-format
msgid "NIC with Network BootROM"
msgstr "Nätverkskort med Network BootROM"

#. Tag: para
#: boot-installer.xml:1050
#, no-c-format
msgid ""
"It could be that your Network Interface Card provides TFTP boot "
"functionality."
msgstr ""
"Det kan vara så att ditt nätverkskort erbjuder funktionalitet för att starta "
"upp via TFTP."

#. Tag: para
#: boot-installer.xml:1055
#, no-c-format
msgid ""
"Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. "
"Please refer to this document."
msgstr ""
"Låt oss (<email>&email-debian-boot-list;</email>) veta hur du gjorde det. "
"Vänligen referera till det här dokumentet."

#. Tag: title
#: boot-installer.xml:1063
#, no-c-format
msgid "Etherboot"
msgstr "Etherboot"

#. Tag: para
#: boot-installer.xml:1064
#, no-c-format
msgid ""
"The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> "
"provides bootdiskettes and even bootroms that do a TFTPboot."
msgstr ""
"<ulink url=\"http://www.etherboot.org\">Etherboot-projektet</ulink> erbjuder "
"startdisketter och även ROM-filer som kan göra uppstarter via TFTP."

#. Tag: title
#: boot-installer.xml:1073
#, no-c-format
msgid "The Boot Prompt"
msgstr "Uppstartsprompten"

#. Tag: para
#: boot-installer.xml:1074
#, no-c-format
msgid ""
"When the installer boots, you should be presented with a friendly graphical "
"screen showing the Debian logo and the boot prompt: "
"<informalexample><screen>\n"
"Press F1 for help, or ENTER to boot:\n"
"</screen></informalexample> At the boot prompt you can either just press "
"&enterkey; to boot the installer with default options or enter a specific "
"boot method and, optionally, boot parameters."
msgstr ""
"När installeraren startar upp bör du presenteras med en snäll grafisk skärm "
"som visar Debians logotyp och en uppstartsprompt: <informalexample><screen>\n"
"Press F1 for help, or ENTER to boot:\n"
"</screen></informalexample> Vid uppstartsprompten kan du antingen bara "
"trycka &enterkey; för att starta upp installeraren med standardalternativ "
"eller ange en specifik uppstartsmetod och, valfritt, uppstartsparametrar."

#. Tag: para
#: boot-installer.xml:1086
#, no-c-format
msgid ""
"Information on available boot methods and on boot parameters which might be "
"useful can be found by pressing <keycap>F2</keycap> through <keycap>F8</"
"keycap>. If you add any parameters to the boot command line, be sure to type "
"the boot method (the default is <userinput>linux</userinput>) and a space "
"before the first parameter (e.g., <userinput>linux debconf/priority=medium</"
"userinput>)."
msgstr ""
"Information om tillgängliga uppstartsmetoder och om uppstartsparametrar som "
"kan vara användbara kan hittas genom att trycka <keycap>F2</keycap> till "
"<keycap>F8</keycap>. Om du lägger till några parametrar till kommandoraden, "
"tänk på att ange uppstartsmetoden (standard är <userinput>linux</userinput>) "
"och ett blanksteg före den första parametern (exempelvis <userinput>linux "
"debconf/priority=medium</userinput>)."

#. Tag: para
#: boot-installer.xml:1095
#, no-c-format
msgid ""
"If you are installing the system via a remote management device that "
"provides a text interface to the VGA console, you may not be able to see the "
"initial graphical splash screen upon booting the installer; you may even not "
"see the boot prompt. Examples of these devices include the text console of "
"Compaq's <quote>integrated Lights Out</quote> (iLO) and HP's "
"<quote>Integrated Remote Assistant</quote> (IRA). You can blindly press "
"F1<footnote> <para> In some cases these devices will require special escape "
"sequences to enact this keypress, for example the IRA uses <keycombo> "
"<keycap>Ctrl</keycap> <keycap>F</keycap> </keycombo>,&nbsp;<keycap>1</"
"keycap>. </para> </footnote> to bypass this screen and view the help text. "
"Once you are past the splash screen and at the help text your keystrokes "
"will be echoed at the prompt as expected. To prevent the installer from "
"using the framebuffer for the rest of the installation, you will also want "
"to add <userinput>debian-installer/framebuffer=false</userinput> to the boot "
"prompt, as described in the help text."
msgstr ""
"Om du installerar systemet via en fjärrhanteringsenhet som tillhandahåller "
"ett textgränssnitt till VGA-konsollen, kan du inte se den initiala grafiska "
"uppstartsskärmen under uppstarten av installeraren; du kanske inte heller "
"kan se uppstartsprompten. Exempel på de här enheterna inkluderar "
"textkonsollen för Compaqs <quote>integrated Lights Out</quote> (iLO) och HP:"
"s <quote>Integrated Remote Assistant</quote> (IRA). Du kan helt blint trycka "
"F1<footnote> <para> I vissa fall kräver de här enheterna en speciell "
"tangentsekvens för att göra den här tangenttryckningen, till exempel "
"använder IRA <keycombo> <keycap>Ctrl</keycap> <keycap>F</keycap> </keycombo>,"
"&nbsp;<keycap>1</keycap>. </para> </footnote> för att komma förbi den här "
"skärmen och visa hjälptexten. När du har kommit förbi uppstartsskärmen och "
"är vid hjälptexten kommer dina tangenttryckning att ekas vid prompten som "
"förväntat. För att förhindra att installeraren använder grafikkortet i "
"resten av installationen, kan du också lägga till <userinput>debian-"
"installer/framebuffer=false</userinput> till uppstartsprompten, som beskrivs "
"i hjälptexten."

#. Tag: title
#: boot-installer.xml:1170
#, no-c-format
msgid "CD Contents"
msgstr "Cd-innehåll"

#. Tag: para
#: boot-installer.xml:1172
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1188
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1204
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1213
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1225
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: title
#: boot-installer.xml:1244
#, no-c-format
msgid "IMPORTANT"
msgstr "VIKTIGT"

#. Tag: para
#: boot-installer.xml:1245
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: title
#: boot-installer.xml:1257
#, no-c-format
msgid "Option 1: Booting from the Boot Option Maintenance Menu"
msgstr "Alternativ 1: Starta upp från Boot Option Maintenance Menu"

#. Tag: para
#: boot-installer.xml:1264
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1270
#, no-c-format
msgid ""
"Select <command>Boot Maintenance Menu</command> from the menu with the arrow "
"keys and press <command>ENTER</command>. This will display a new menu."
msgstr ""

#. Tag: para
#: boot-installer.xml:1276
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1287
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1298
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1310
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: title
#: boot-installer.xml:1320
#, no-c-format
msgid "Option 2: Booting from the EFI Shell"
msgstr "Alternativ 2: Starta upp från EFI-skalet"

#. Tag: para
#: boot-installer.xml:1321
#, no-c-format
msgid ""
"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:"
msgstr ""

#. Tag: para
#: boot-installer.xml:1332
#, no-c-format
msgid ""
"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."
msgstr ""
"Mata in cd-skivan i dvd/cd-enheten och starta om maskinen. Firmware kommer "
"att visa EFI Boot Manager-sidan och menyn efter den färdigställer "
"systeminitieringen."

#. Tag: para
#: boot-installer.xml:1338
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1352
#, no-c-format
msgid ""
"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>."
msgstr ""
"Undersök utskriften från skalet som letar efter cd-rom-enheten. Det är "
"antagligen enheten <filename>fs0:</filename> även om andra enheter med "
"startbara partitioner också kommer att visas som <filename>fs<replaceable>n</"
"replaceable></filename>."

#. Tag: para
#: boot-installer.xml:1359
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1366
#, no-c-format
msgid ""
"Enter <command>elilo</command> and press <command>ENTER</command>. This will "
"start the boot load sequence."
msgstr ""

#. Tag: para
#: boot-installer.xml:1373
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: title
#: boot-installer.xml:1387
#, no-c-format
msgid "Installing using a Serial Console"
msgstr "Installation med en seriellkonsoll"

#. Tag: para
#: boot-installer.xml:1389
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1400
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1407
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1418
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1427
#, no-c-format
msgid ""
"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."
msgstr ""
"Om du väljer fel konsolltyp kommer du kunna välja kärna och ange parametrar "
"men både skärmen och din inmatning kommer att försvinna så snart som kärnan "
"startat och kräver att du startar om före du kan påbörjar installationen."

#. Tag: title
#: boot-installer.xml:1436
#, no-c-format
msgid "Selecting the Boot Kernel and Options"
msgstr "Välj uppstartskärna och inställningar"

#. Tag: para
#: boot-installer.xml:1438
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1450
#, no-c-format
msgid ""
"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:"
msgstr ""

#. Tag: para
#: boot-installer.xml:1468
#, no-c-format
msgid ""
"Select the kernel version and installation mode most appropriate to your "
"needs with the arrow keys."
msgstr ""
"Välj kärnversionen och installationsläget som är mest lämplig för dina behov "
"med piltangenterna."

#. Tag: para
#: boot-installer.xml:1473
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1480
#, no-c-format
msgid ""
"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."
msgstr ""
"Tryck <command>ENTER</command>. Det kommer att läsa in och starta kärnan. "
"Kärnan kommer att visa dess vanliga initieringsmeddelanden följt av första "
"skärmen av Debian Installer."

#. Tag: para
#: boot-installer.xml:1489
#, no-c-format
msgid ""
"Proceed to the next chapter to continue the installation where you will set "
"up the language locale, network, and disk partitions."
msgstr ""
"Fortsätt till nästa kapitel för att fortsätta installationen där du kommer "
"att ställa in språkanpassning, nätverk och diskpartitioner."

#. Tag: para
#: boot-installer.xml:1500
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1534
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: title
#: boot-installer.xml:1545
#, no-c-format
msgid "Configuring the Server"
msgstr "Konfiguration av servern"

#. Tag: para
#: boot-installer.xml:1546
#, no-c-format
msgid ""
"A suitable TFTP entry for network booting an ia64 system looks something "
"like this: <informalexample><screen>\n"
"host mcmuffin {\n"
"        hardware ethernet 00:30:6e:1e:0e:83;\n"
"        fixed-address 10.0.0.21;\n"
"        filename \"debian-installer/ia64/elilo.efi\";\n"
"}\n"
"</screen></informalexample> Note that the goal is to get <command>elilo.efi</"
"command> running on the client."
msgstr ""
"En lämplig TFTP-post för att starta upp via nätverket på ett ia64-system ser "
"ut ungefär som den här: <informalexample><screen>\n"
"host mcmuffin {\n"
"        hardware ethernet 00:30:6e:1e:0e:83;\n"
"        fixed-address 10.0.0.21;\n"
"        filename \"debian-installer/ia64/elilo.efi\";\n"
"}\n"
"</screen></informalexample> Notera att målet är att få <command>elilo.efi</"
"command> att köra på klienten."

#. Tag: para
#: boot-installer.xml:1556
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: screen
#: boot-installer.xml:1566
#, no-c-format
msgid ""
"# cd /var/lib/tftp\n"
"# tar xvfz /home/user/netboot.tar.gz\n"
"./\n"
"./debian-installer/\n"
"./debian-installer/ia64/\n"
"[...]"
msgstr ""
"# cd /var/lib/tftp\n"
"# tar xvfz /home/user/netboot.tar.gz\n"
"./\n"
"./debian-installer/\n"
"./debian-installer/ia64/\n"
"[...]"

#. Tag: para
#: boot-installer.xml:1566
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: title
#: boot-installer.xml:1583
#, no-c-format
msgid "Configuring the Client"
msgstr "Konfiguration av klienten"

#. Tag: para
#: boot-installer.xml:1584
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1616
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1625
#, no-c-format
msgid ""
"Proceed to the next chapter to continue the installation where you will set "
"up the language locale, network, and the disk partitions."
msgstr ""
"Fortsätt till nästa kapitel för att fortsätta installationen där du kommer "
"att ställa in språkanpassning, nätverk och diskpartitionerna."

#. Tag: title
#: boot-installer.xml:1638
#, no-c-format
msgid "Choosing an Installation Method"
msgstr "Välja en installationsmetod"

#. Tag: para
#: boot-installer.xml:1640
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1648
#, no-c-format
msgid ""
"If you are using a 2.2.x linux kernel, then you need to use the "
"&ramdisksize; kernel parameter."
msgstr ""
"Om du använder en Linux-kärna med version 2.2.x, behöver du använda "
"kärnparametern &ramdisksize;."

#. Tag: para
#: boot-installer.xml:1653
#, no-c-format
msgid ""
"Make sure <userinput>root=/dev/ram</userinput> is one of your kernel "
"parameters."
msgstr ""
"Se till att <userinput>root=/dev/ram</userinput> är en av dina "
"kärnparametrar."

#. Tag: para
#: boot-installer.xml:1658
#, no-c-format
msgid ""
"If you're having trouble, check <ulink url=\"&url-m68k-cts-faq;\">cts's "
"&arch-title; debian-installer FAQ</ulink>."
msgstr ""
"Om du får problem, ta en titt i <ulink url=\"&url-m68k-cts-faq;\">cts's "
"&arch-title; debian-installer FAQ</ulink>."

#. Tag: title
#: boot-installer.xml:1675
#, no-c-format
msgid "Amiga"
msgstr "Amiga"

#. Tag: para
#: boot-installer.xml:1676
#, no-c-format
msgid ""
"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>"
msgstr ""
"Den enda installationsmetoden tillgänglig för amiga är via hårddisken (se "
"<xref linkend=\"m68k-boot-hd\"/>). <emphasis>Med andra ord, cd-skivan är "
"inte startbar.</emphasis>"

#. Tag: para
#: boot-installer.xml:1682
#, no-c-format
msgid ""
"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>."
msgstr ""
"Amiga fungerar för tillfället inte med bogl, så om du ser fel från bogl "
"behöver du inkludera kärnparametern <userinput>debian-installer/"
"framebuffer=false</userinput>."

#. Tag: title
#: boot-installer.xml:1691
#, no-c-format
msgid "Atari"
msgstr "Atari"

#. Tag: para
#: boot-installer.xml:1692
#, no-c-format
msgid ""
"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>"
msgstr ""
"Installeraren för atari kan startas från antingen hårddisken (se <xref "
"linkend=\"m68k-boot-hd\"/>) eller från disketter (se <xref linkend=\"boot-"
"from-floppies\"/>). <emphasis>Med andra ord, cd-skivan är inte startbar.</"
"emphasis>"

#. Tag: para
#: boot-installer.xml:1699
#, no-c-format
msgid ""
"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>."
msgstr ""
"Atari fungerar för närvarande inte med bogl så om du ser fel från bogl "
"behöver du inkludera kärnparametern <userinput>debian-installer/"
"framebuffer=false</userinput>."

#. Tag: title
#: boot-installer.xml:1708
#, no-c-format
msgid "BVME6000"
msgstr "BVME6000"

#. Tag: para
#: boot-installer.xml:1709
#, no-c-format
msgid ""
"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\"/>)."
msgstr ""

#. Tag: title
#: boot-installer.xml:1719
#, no-c-format
msgid "Macintosh"
msgstr "Macintosh"

#. Tag: para
#: boot-installer.xml:1720
#, no-c-format
msgid ""
"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."
msgstr ""
"Den enda installationsmetoden som är tillgänglig för mac är från hårddisken "
"(se <xref linkend=\"m68k-boot-hd\"/>). <emphasis>Med andra ord, cd-skivan är "
"inte startbar.</emphasis> Mac har ingen fungerande 2.4.x-kärna."

#. Tag: para
#: boot-installer.xml:1727
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: title
#: boot-installer.xml:1742
#, no-c-format
msgid "MVME147 and MVME16x"
msgstr "MVME147 och MVME16x"

#. Tag: para
#: boot-installer.xml:1743
#, no-c-format
msgid ""
"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>"
msgstr ""

#. Tag: title
#: boot-installer.xml:1753
#, no-c-format
msgid "Q40/Q60"
msgstr "Q40/Q60"

#. Tag: para
#: boot-installer.xml:1754
#, no-c-format
msgid ""
"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>"
msgstr ""
"Den enda installationsmetoden som är tillgänglig för Q40/Q60 är från "
"hårddisken (se <xref linkend=\"m68k-boot-hd\"/>). <emphasis>Med andra ord, "
"cd-skivan är inte startbar.</emphasis>"

#. Tag: title
#: boot-installer.xml:1765
#, no-c-format
msgid "Booting from a Hard Disk"
msgstr "Starta upp från en hårddisk"

#. Tag: para
#: boot-installer.xml:1771 boot-installer.xml:2369
#, no-c-format
msgid ""
"Booting from an existing operating system is often a convenient option; for "
"some systems it is the only supported method of installation."
msgstr ""
"Uppstart från ett existerande operativsystem är ofta ett bekvämt alternativ, "
"för vissa system är det den enda installationsmetoden som stöds."

#. Tag: para
#: boot-installer.xml:1777 boot-installer.xml:2375
#, no-c-format
msgid ""
"To boot the installer from hard disk, you will have already completed "
"downloading and placing the needed files in <xref linkend=\"boot-drive-files"
"\"/>."
msgstr ""
"För att starta upp installeraren från hårddisk måste du redan ha hämtat och "
"placerat de filer som behövs i <xref linkend=\"boot-drive-files\"/>."

#. Tag: para
#: boot-installer.xml:1786
#, no-c-format
msgid ""
"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)."
msgstr ""
"Åtminstone sex olika ramdiskar kan användas för att starta upp från "
"hårddisken, tre olika typer vardera med och utan stöd för en Linuxkärna "
"version 2.2.x (se <ulink url=\"&disturl;/main/installer-&architecture;/"
"current/images/MANIFEST\">MANIFEST</ulink> för detaljer)."

#. Tag: para
#: boot-installer.xml:1794
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: title
#: boot-installer.xml:1815
#, no-c-format
msgid "Booting from AmigaOS"
msgstr "Starta upp från AmigaOS"

#. Tag: para
#: boot-installer.xml:1816
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1822
#, no-c-format
msgid ""
"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\"/>."
msgstr ""

#. Tag: title
#: boot-installer.xml:1837
#, no-c-format
msgid "Booting from Atari TOS"
msgstr "Starta upp från Atari TOS"

#. Tag: para
#: boot-installer.xml:1838
#, no-c-format
msgid ""
"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."
msgstr ""
"I skrivbordsmiljön GEM, starta Linux-installationsprocessen genom att "
"dubbelklicka på ikonen <guiicon>bootstra.prg</guiicon> i katalogen "
"<filename>debian</filename> och klicka <guibutton>Ok</guibutton> i "
"programmets inställningsruta."

#. Tag: para
#: boot-installer.xml:1845
#, no-c-format
msgid ""
"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\"/>."
msgstr ""

#. Tag: title
#: boot-installer.xml:1860
#, no-c-format
msgid "Booting from MacOS"
msgstr "Starta upp från MacOS"

#. Tag: para
#: boot-installer.xml:1861
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1872
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1881
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1896
#, no-c-format
msgid ""
"To set the boot parameters in Penguin, choose <guimenu>File</guimenu> -&gt; "
"<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> -&gt; <guimenuitem>Save Settings as Default</"
"guimenuitem>."
msgstr ""

#. Tag: para
#: boot-installer.xml:1905
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1912
#, no-c-format
msgid ""
"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\"/>."
msgstr ""

#. Tag: title
#: boot-installer.xml:1927
#, no-c-format
msgid "Booting from Q40/Q60"
msgstr "Starta upp från Q40/Q60"

#. Tag: para
#: boot-installer.xml:1929
#, no-c-format
msgid "FIXME"
msgstr "FIXME"

#. Tag: para
#: boot-installer.xml:1933
#, no-c-format
msgid ""
"The installation program should start automatically, so you can continue "
"below at <xref linkend=\"d-i-intro\"/>."
msgstr ""

#. Tag: para
#: boot-installer.xml:1945
#, no-c-format
msgid ""
"Currently, the only &arch-title; subarchitecture that supports CD-ROM "
"booting is the BVME6000."
msgstr ""
"För närvarande, den enda underarkitekturen av &arch-title; som har stöd för "
"uppstart via cd-rom är BVME6000."

#. Tag: para
#: boot-installer.xml:2017
#, no-c-format
msgid ""
"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:"
msgstr ""

#. Tag: para
#: boot-installer.xml:2028
#, no-c-format
msgid "type <screen>i6000 &enterkey;</screen> to install a BVME4000/6000"
msgstr ""
"ange <screen>i6000 &enterkey;</screen> för att installera en BVME4000/6000"

#. Tag: para
#: boot-installer.xml:2033
#, no-c-format
msgid "type <screen>i162 &enterkey;</screen> to install an MVME162"
msgstr "ange <screen>i162 &enterkey;</screen> för att installera en MVME162"

#. Tag: para
#: boot-installer.xml:2038
#, no-c-format
msgid "type <screen>i167 &enterkey;</screen> to install an MVME166/167"
msgstr ""
"ange <screen>i167 &enterkey;</screen> för att installera en MVME166/167"

#. Tag: para
#: boot-installer.xml:2045
#, no-c-format
msgid ""
"You may additionally append the string <screen>TERM=vt100</screen> to use "
"vt100 terminal emulation, e.g., <screen>i6000 TERM=vt100 &enterkey;</screen>."
msgstr ""

#. Tag: para
#: boot-installer.xml:2057
#, no-c-format
msgid ""
"For most &arch-title; architectures, booting from a local filesystem is the "
"recommended method."
msgstr ""

#. Tag: para
#: boot-installer.xml:2062
#, no-c-format
msgid ""
"Booting from the boot floppy is supported only for Atari and VME (with a "
"SCSI floppy drive on VME) at this time."
msgstr ""
"Uppstart från startdisketten stöds endast på Atari och VME (med en SCSI-"
"diskettenhet på VME) för tillfället."

#. Tag: title
#: boot-installer.xml:2078 boot-installer.xml:2125
#, no-c-format
msgid "SGI Indys TFTP Booting"
msgstr "Uppstart för SGI Indy via TFTP"

#. Tag: para
#: boot-installer.xml:2079
#, no-c-format
msgid ""
"After entering the command monitor use <informalexample><screen>\n"
"bootp():\n"
"</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>\n"
"unsetenv netaddr\n"
"</screen></informalexample> in the command monitor to do this."
msgstr ""

#. Tag: title
#: boot-installer.xml:2098 boot-installer.xml:2147 boot-installer.xml:2202
#: boot-installer.xml:2241
#, no-c-format
msgid "Broadcom BCM91250A TFTP Booting"
msgstr "Uppstart för Broadcom BCM91250A via TFTP"

#. Tag: para
#: boot-installer.xml:2099 boot-installer.xml:2203
#, no-c-format
msgid ""
"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>\n"
"ifconfig eth0 -auto\n"
"</screen></informalexample> Once you have obtained an IP address, you can "
"load SiByl with the following command: <informalexample><screen>\n"
"boot 192.168.1.1:/boot/sibyl\n"
"</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."
msgstr ""

#. Tag: title
#: boot-installer.xml:2122 boot-installer.xml:2226 boot-installer.xml:2749
#, no-c-format
msgid "Boot Parameters"
msgstr "Uppstartsparametrar"

#. Tag: para
#: boot-installer.xml:2126
#, no-c-format
msgid ""
"On SGI Indys you can append boot parameters to the <command>bootp():</"
"command> command in the command monitor."
msgstr ""

#. Tag: para
#: boot-installer.xml:2131
#, no-c-format
msgid ""
"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>\n"
"bootp():/boot/tftpboot.img\n"
"</screen></informalexample> Further kernel parameters can be passed via "
"<command>append</command>:"
msgstr ""

#. Tag: screen
#: boot-installer.xml:2141
#, no-c-format
msgid "bootp(): append=\"root=/dev/sda1\""
msgstr "bootp(): append=\"root=/dev/sda1\""

#. Tag: para
#: boot-installer.xml:2148 boot-installer.xml:2242
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: title
#: boot-installer.xml:2167 boot-installer.xml:2229
#, fuzzy, no-c-format
msgid "Cobalt TFTP Booting"
msgstr "Uppstart för SGI Indy via TFTP"

#. Tag: para
#: boot-installer.xml:2168
#, no-c-format
msgid ""
"Strictly speaking, Cobalt does not ue TFTP but NFS to boot. You need to "
"install an NFS server and put the installer files in <filename>/nfsroot</"
"filename>. When you boot your Cobalt, you have to press the left and the "
"right cursor buttons at the same time and the machine will boot via the "
"network from NFS. It will then display several options on the display. There "
"are the following two installation methods:"
msgstr ""

#. Tag: para
#: boot-installer.xml:2178
#, no-c-format
msgid ""
"Via SSH (default): In this case, the installer will configure the network "
"via DHCP and start an SSH server. It will then display a random password and "
"other login information (such as the IP address) on the Cobalt LCD. When you "
"connect to the machine with an SSH client you can start with the "
"installation."
msgstr ""

#. Tag: para
#: boot-installer.xml:2187
#, no-c-format
msgid ""
"Via serial console: Using a null modem cable, you can connect to the serial "
"port of your Cobalt machine (using 115200 bps) and perform the installation "
"this way. This option is not available on Qube 2700 (Qube1) machines since "
"they have no serial port."
msgstr ""

#. Tag: para
#: boot-installer.xml:2230
#, no-c-format
msgid ""
"You cannot pass any boot parameters directly. Instead, you have to edit the "
"<filename>/nfsroot/default.colo</filename> file on the NFS server and add "
"your parameters to the <replaceable>args</replaceable> variable."
msgstr ""

#. Tag: title
#: boot-installer.xml:2258
#, no-c-format
msgid "s390 Limitations"
msgstr "Begränsningar för s390"

#. Tag: para
#: boot-installer.xml:2259
#, no-c-format
msgid ""
"In order to run the installation system a working network setup and ssh "
"session is needed on S/390."
msgstr ""
"För att kunna köra installationssystemet på S/390 behövs en fungerande "
"nätverkskonfiguration och en ssh-session."

#. Tag: para
#: boot-installer.xml:2264
#, no-c-format
msgid ""
"The booting process starts with a network setup that prompts you for several "
"network parameters. If the setup is successful, you will login to the system "
"by starting a ssh session which will launch the standard installation system."
msgstr ""

#. Tag: title
#: boot-installer.xml:2275
#, no-c-format
msgid "s390 Boot Parameters"
msgstr "Uppstartsparametrar för s390"

#. Tag: para
#: boot-installer.xml:2276
#, no-c-format
msgid ""
"On S/390 you can append boot parameters in the parm file. This file can "
"either be in ASCII or EBCDIC format. Please read <ulink url=\"&url-s390-"
"devices;\">Device Drivers and Installation Commands</ulink> for more "
"information about S/390-specific boot parameters."
msgstr ""

#. Tag: para
#: boot-installer.xml:2330
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:2339
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:2348
#, no-c-format
msgid ""
"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"
msgstr ""

#. Tag: screen
#: boot-installer.xml:2357
#, no-c-format
msgid "0 &gt; boot cd:,\\install\\yaboot"
msgstr "0 &gt; boot cd:,\\install\\yaboot"

#. Tag: title
#: boot-installer.xml:2363
#, no-c-format
msgid "Booting from Hard Disk"
msgstr "Starta upp från hårddisk"

#. Tag: title
#: boot-installer.xml:2384
#, no-c-format
msgid "Booting CHRP from OpenFirmware"
msgstr "Starta upp CHRP från OpenFirmware"

#. Tag: emphasis
#: boot-installer.xml:2388
#, no-c-format
msgid "Not yet written."
msgstr "Ännu inte skriven."

#. Tag: title
#: boot-installer.xml:2393
#, no-c-format
msgid "Booting OldWorld PowerMacs from MacOS"
msgstr "Starta upp OldWorld PowerMac från MacOS"

#. Tag: para
#: boot-installer.xml:2394
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: title
#: boot-installer.xml:2412
#, no-c-format
msgid "Booting NewWorld Macs from OpenFirmware"
msgstr "Starta upp NewWorld Mac från OpenFirmware"

#. Tag: para
#: boot-installer.xml:2413
#, no-c-format
msgid ""
"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>\n"
"0 &gt; boot hd:<replaceable>x</replaceable>,yaboot\n"
"</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>\n"
"boot:\n"
"</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."
msgstr ""

#. Tag: title
#: boot-installer.xml:2448
#, no-c-format
msgid "Booting from USB memory stick"
msgstr "Starta upp från USB-minne"

#. Tag: para
#: boot-installer.xml:2449
#, no-c-format
msgid "Currently, NewWorld PowerMac systems are known to support USB booting."
msgstr ""

#. Tag: para
#: boot-installer.xml:2455
#, no-c-format
msgid ""
"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. 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\"/>)."
msgstr ""

#. Tag: para
#: boot-installer.xml:2467
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:2479
#, no-c-format
msgid ""
"Having worked out the device path, use a command like this to boot the "
"installer: <informalexample><screen>\n"
"boot <replaceable>usb0/disk</replaceable>:<replaceable>2</replaceable>,\\\\:"
"tbxi\n"
"</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>."
msgstr ""

#. Tag: para
#: boot-installer.xml:2493
#, no-c-format
msgid ""
"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;."
msgstr ""

#. Tag: para
#: boot-installer.xml:2499
#, no-c-format
msgid ""
"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\"/>."
msgstr ""

#. Tag: para
#: boot-installer.xml:2532
#, no-c-format
msgid "Currently, PReP and New World PowerMac systems support netbooting."
msgstr ""

#. Tag: para
#: boot-installer.xml:2536
#, no-c-format
msgid ""
"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>."
msgstr ""

#. Tag: para
#: boot-installer.xml:2551
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:2563
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:2569
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:2576
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: title
#: boot-installer.xml:2587
#, no-c-format
msgid "PowerPC Boot Parameters"
msgstr "Uppstartsparametrar för PowerPC"

#. Tag: para
#: boot-installer.xml:2588
#, no-c-format
msgid ""
"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> ."
msgstr ""

#. Tag: para
#: boot-installer.xml:2628
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:2684
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:2699
#, no-c-format
msgid ""
"To boot from floppy on a Sparc, use <informalexample><screen>\n"
"Stop-A -&gt; OpenBoot: \"boot floppy\"\n"
"</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."
msgstr ""

#. Tag: para
#: boot-installer.xml:2711
#, no-c-format
msgid ""
"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>."
msgstr ""

#. Tag: para
#: boot-installer.xml:2718
#, no-c-format
msgid ""
"If you are booting from the floppy, and you see messages such as "
"<informalexample><screen>\n"
"Fatal error: Cannot read partition\n"
"Illegal or malformed device name\n"
"</screen></informalexample> then it is possible that floppy booting is "
"simply not supported on your machine."
msgstr ""

#. Tag: title
#: boot-installer.xml:2730
#, no-c-format
msgid "IDPROM Messages"
msgstr "IDPROM-meddelanden"

#. Tag: para
#: boot-installer.xml:2731
#, no-c-format
msgid ""
"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."
msgstr ""

#. Tag: para
#: boot-installer.xml:2750
#, no-c-format
msgid ""
"Boot parameters are Linux kernel parameters which are generally used to make "
"sure that peripherals are dealt with properly. For the most part, the kernel "
"can auto-detect information about your peripherals. However, in some cases "
"you'll have to help the kernel a bit."
msgstr ""
"Uppstartsparametrar är parametrar för Linux-kärnan som generellt sett "
"används för att se till att kringutrustning hanteras korrekt. För det mesta "
"kan kärnan automatiskt identifiera information om din kringutrustning. Dock, "
"i vissa fall, behöver du hjälpa kärnan en bit på vägen."

#. Tag: para
#: boot-installer.xml:2757
#, no-c-format
msgid ""
"If this is the first time you're booting the system, try the default boot "
"parameters (i.e., don't try setting parameters) and see if it works "
"correctly. It probably will. If not, you can reboot later and look for any "
"special parameters that inform the system about your hardware."
msgstr ""
"Om det här är första gången du startar upp systemet kan du prova de "
"uppstartsparametrar som är standard (alltså, ställ inte in några parametrar) "
"och se om det fungerar korrekt. Det kommer säkert att göra det. Om inte, kan "
"du starta om senare och leta efter några speciella parametrar som informerar "
"systemet om din hårdvara."

#. Tag: para
#: boot-installer.xml:2764
#, no-c-format
msgid ""
"Information on many boot parameters can be found in the <ulink url=\"http://"
"www.tldp.org/HOWTO/BootPrompt-HOWTO.html\"> Linux BootPrompt HOWTO</ulink>, "
"including tips for obscure hardware. This section contains only a sketch of "
"the most salient parameters. Some common gotchas are included below in <xref "
"linkend=\"boot-troubleshooting\"/>."
msgstr ""
"Information om många uppstartsparametrar kan hittas i <ulink url=\"http://"
"www.tldp.org/HOWTO/BootPrompt-HOWTO.html\"> Linux BootPrompt HOWTO</ulink>, "
"inklusive tips för obskyr hårdvara. Den här sektion innehåller endast en del "
"av de mest vanliga parametrarna. Vissa vanliga problem finns beskrivna i "
"<xref linkend=\"boot-troubleshooting\"/>."

#. Tag: para
#: boot-installer.xml:2773
#, no-c-format
msgid ""
"When the kernel boots, a message <informalexample><screen>\n"
"Memory:<replaceable>avail</replaceable>k/<replaceable>total</replaceable>k "
"available\n"
"</screen></informalexample> should be emitted early in the process. "
"<replaceable>total</replaceable> should match the total amount of RAM, in "
"kilobytes. If this doesn't match the actual amount of RAM you have "
"installed, you need to use the <userinput>mem=<replaceable>ram</"
"replaceable></userinput> parameter, where <replaceable>ram</replaceable> is "
"set to the amount of memory, suffixed with <quote>k</quote> for kilobytes, "
"or <quote>m</quote> for megabytes. For example, both <userinput>mem=65536k</"
"userinput> and <userinput>mem=64m</userinput> mean 64MB of RAM."
msgstr ""
"När kärnan startar upp bör meddelandet<informalexample><screen>\n"
"Memory:<replaceable>tillgängligt</replaceable>k/<replaceable>totalt</"
"replaceable>k available\n"
"</screen></informalexample> visas tidigt i processen. <replaceable>totalt</"
"replaceable> bör stämma med totalt RAM-minne i kilobyte. Om det inte stämmer "
"med den faktiska mängden RAM-minne du har installerad behöver du använda "
"parametern <userinput>mem=<replaceable>ram</replaceable></userinput>, där "
"<replaceable>ram</replaceable> är inställd till mängden minne och ändelsen "
"<quote>k</quote> för kilobyte eller <quote>m</quote> för megabyte. Till "
"exempel, både <userinput>mem=65536k</userinput> och <userinput>mem=64m</"
"userinput> betyder 64MB RAM-minne."

#. Tag: para
#: boot-installer.xml:2789
#, no-c-format
msgid ""
"If you are booting with a serial console, generally the kernel will "
"autodetect this<phrase arch=\"mipsel\"> (although not on DECstations)</"
"phrase>. 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>."