© 1995-2008 by The FreeBSD Project. All rights reserved.URL: http://www.FreeBSD.de
jkois 2007-08-19 18:10:03 UTC
FreeBSD ports repository
Modified files:
books/handbook/install chapter.sgml
Log:
MFen 1.370 Den Abschnitt "Installationsprobleme" aus den Notes aufgenommen.
Revision Changes Path
1.65 +332 -2 de-docproj/books/handbook/install/chapter.sgml
Index: chapter.sgml
===================================================================
RCS file: /home/cvs/de-docproj/books/handbook/install/chapter.sgml,v
retrieving revision 1.64
retrieving revision 1.65
diff -u -I$FreeBSDde.*$ -r1.64 -r1.65
--- chapter.sgml 7 Aug 2007 07:15:52 -0000 1.64
+++ chapter.sgml 19 Aug 2007 18:10:03 -0000 1.65
@@ -2,8 +2,8 @@
The FreeBSD Documentation Project
$FreeBSD$
- $FreeBSDde: de-docproj/books/handbook/install/chapter.sgml,v 1.64 2007/08/07 07:15:52 jkois Exp $
- basiert auf: 1.369
+ $FreeBSDde: de-docproj/books/handbook/install/chapter.sgml,v 1.65 2007/08/19 18:10:03 jkois Exp $
+ basiert auf: 1.370
-->
<chapter id="install">
@@ -4452,8 +4452,338 @@
<para>Analog werden NTFS-Partitionen mit dem
Kommando &man.mount.ntfs.8; eingehangen.</para>
</sect2>
+<!-- xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx -->
+ <sect2>
+ <title>Troubleshooting Questions and Answers</title>
+
+ <qandaset>
+ <qandaentry>
+ <question>
+ <para>My system hangs while probing hardware during boot, or it
+ behaves strangely during install, or the floppy drive isn't
+ probed.</para>
+ </question>
+ <answer>
+ <para>&os; 5.0 and above makes extensive use of the system ACPI
+ service on the i386, amd64 and ia64 platforms to aid in system
+ configuration if it's detected during boot. Unfortunately,
+ some bugs still exist in both the ACPI driver and within system
+ motherboards and BIOS. The use of ACPI can be disabled by setting
+ the <quote>hint.acpi.0.disabled</quote> hint in the third stage
+ boot loader:</para>
+
+ <screen>set hint.acpi.0.disabled="1"</screen>
+
+ <para>This is reset each time the system is booted, so it is
+ necessary to add <literal>hint.acpi.0.disabled="1"</literal>
+ to the file
+ <filename>/boot/loader.conf</filename>. More information about the
+ boot loader can be found in the &os; Handbook.</para>
+ </answer>
+ </qandaentry>
+ <qandaentry>
+ <question>
+ <para>My legacy ISA device used to be recognized in previous versions
+ of &os;, but now it's not. What happened?</para>
+ </question>
+ <answer>
+ <para>Some device drivers, like matcd, were removed over time due to
+ lack of maintainership or other reasons. Others still exist but
+ are disabled because of their intrusive hardware probe routines.
+ The following ISA device drivers fall into this category and can
+ re-enabled from the third stage boot loader: aha, ahv, aic, bt, ed,
+ cs, sn, ie, fe, le, and lnc. To do this, stop the loader during
+ it's 10 second countdown and enter the following at the
+ prompt:</para>
+
+ <screen>unset hint.foo.0.disabled</screen>
+
+ <para>where <replaceable>foo</replaceable> is the name of the driver
+ to re-enable. This can be set permanently by editing the file
+ <filename>/boot/device.hints</filename> and removing the appropriate
+ <quote>disabled</quote> entry.</para>
+ </answer>
+ </qandaentry>
+ <qandaentry>
+ <question>
+ <para>I go to boot from the hard disk for the first time
+ after installing &os;, the kernel loads and probes my
+ hardware, but stops with messages like:</para>
+
+ <screen>changing root device to ad1s1a panic: cannot mount root</screen>
+ <para>What is wrong? What can I do?</para>
+
+ <para>What is this
+ <literal>bios_drive:interface(unit,partition)kernel_name</literal>
+ thing that is displayed with the boot help?</para>
+ </question>
+ <answer>
+ <para>There is a longstanding problem in the case where the
+ boot disk is not the first disk in the system. The BIOS
+ uses a different numbering scheme to &os;, and working
+ out which numbers correspond to which is difficult to get
+ right.</para>
+
+ <para>In the case where the boot disk is not the first disk
+ in the system, &os; can need some help finding it. There
+ are two common situations here, and in both of these cases,
+ you need to tell &os; where the root filesystem is. You
+ do this by specifying the BIOS disk number, the disk type
+ and the &os; disk number for that type.</para>
+
+ <para>The first situation is where you have two IDE disks,
+ each configured as the master on their respective IDE
+ busses, and wish to boot &os; from the second disk. The
+ BIOS sees these as disk 0 and disk 1, while &os; sees
+ them as <devicename>ad0</devicename> and
+ <devicename>ad2</devicename>.</para>
+
+ <para>&os; is on BIOS disk 1, of type
+ <literal>ad</literal> and the &os; disk number is 2, so
+ you would say:</para>
+
+ <screen><userinput>1:ad(2,a)kernel</userinput></screen>
+
+ <para>Note that if you have a slave on the primary bus, the
+ above is not necessary (and is effectively wrong).</para>
+
+ <para>The second situation involves booting from a SCSI disk
+ when you have one or more IDE disks in the system. In this
+ case, the &os; disk number is lower than the BIOS disk
+ number. If you have two IDE disks as well as the SCSI disk,
+ the SCSI disk is BIOS disk 2, type <literal>da</literal> and
+ &os; disk number 0, so you would say:</para>
+
+ <screen><userinput>2:da(0,a)kernel</userinput></screen>
+
+ <para>To tell &os; that you want to boot from BIOS disk
+ 2, which is the first SCSI disk in the system. If you only
+ had one IDE disk, you would use '1:' instead.</para>
+
+ <para>Once you have determined the correct values to use,
+ you can put the command exactly as you would have typed it
+ in the <filename>/boot.config</filename> file using a
+ standard text editor. Unless instructed otherwise, &os;
+ will use the contents of this file as the default response
+ to the <literal>boot:</literal> prompt.</para>
+ </answer>
+ </qandaentry>
+ <qandaentry>
+ <question>
+ <para>I go to boot from the hard disk for the first time
+ after installing &os;, but the Boot Manager prompt just
+ prints <literal>F?</literal> at the boot menu each time but
+ the boot won't go any further.</para>
+ </question>
+ <answer>
+ <para>The hard disk geometry was set incorrectly in the
+ Partition editor when you installed &os;. Go back into
+ the partition editor and specify the actual geometry of your
+ hard disk. You must reinstall &os; again from the
+ beginning with the correct geometry.</para>
+
+ <para>If you are failing entirely in figuring out the
+ correct geometry for your machine, here's a tip: Install a
+ small DOS partition at the beginning of the disk and install
+ &os; after that. The install program will see the DOS
+ partition and try to infer the correct geometry from it,
+ which usually works.</para>
+
+ <para>The following tip is no longer recommended, but is left here
+ for reference:</para>
+
+ <blockquote>
+ <para>If you are setting up a truly dedicated &os;
+ server or workstation where you don't care for (future)
+ compatibility with DOS, Linux or another operating system,
+ you've also got the option to use the entire disk (`A' in
+ the partition editor), selecting the non-standard option
+ where &os; occupies the entire disk from the very first
+ to the very last sector. This will leave all geometry
+ considerations aside, but is somewhat limiting unless
+ you're never going to run anything other than &os; on a
+ disk.</para>
+ </blockquote>
+ </answer>
+ </qandaentry>
+ <qandaentry>
+ <question>
+ <para>The &man.mcd.4; driver keeps thinking that it has
+ found a device and this stops my Intel EtherExpress card
+ from working.</para>
+ </question>
+ <answer>
+ <para>Set the hints
+ <quote>hint.mcd.0.disabled="1"</quote> and
+ <quote>hint.mcd.1.disabled="1"</quote>
+ in the third stage boot loader to disable the probing
+ of the <devicename>mcd0</devicename> and
+ <devicename>mcd1</devicename> devices. Generally speaking,
+ you should only leave the devices that you will be using
+ enabled in your kernel.</para>
+ </answer>
+ </qandaentry>
+ <qandaentry>
+ <question>
+ <para>The system finds my &man.ed.4; network card, but I
+ keep getting device timeout errors.</para>
+ </question>
+ <answer>
----------------------------------------------
Diff block truncated. (Max lines = 200)
----------------------------------------------
To Unsubscribe: send mail to majordomo(at)de.FreeBSD.org
with "unsubscribe de-cvs-doc" in the body of the message
Received on Sun 19 Aug 2007 - 20:11:45 CEST