2 $FreeBSD: src/release/doc/en_US.ISO8859-1/installation/common/trouble.sgml,v 1.1.2.4 2002/10/15 21:42:51 bmah Exp $
3 $DragonFly: src/release/doc/en_US.ISO8859-1/installation/common/Attic/trouble.sgml,v 1.2 2003/06/17 04:27:19 dillon Exp $
5 This file contains the comments of the old TROUBLE.TXT file.
8 <title>Troubleshooting</title>
10 <sect2 id="repairing">
11 <title>Repairing an Existing &os; Installation</title>
14 <quote>Fixit</quote> option in the top menu of the boot floppy.
15 To use it, you will also need either a
16 <filename>fixit.flp</filename> image floppy, generated in the same
17 fashion as the boot floppy, or the <quote>live filesystem</quote>
18 CDROM; typically the second CDROM in a multi-disc &os;
21 <para>To invoke fixit, simply boot the
22 <filename>kern.flp</filename> floppy, choose the
23 <quote>Fixit</quote> item and insert the fixit floppy or CDROM
24 when asked. You will then be placed into a shell with a wide
25 variety of commands available (in the <filename>/stand</filename>
26 and <filename>/mnt2/stand</filename> directories) for checking,
27 repairing and examining file systems and their contents. Some
28 UNIX administration experience <emphasis>is</emphasis> required to
29 use the fixit option.</para>
33 <title>Common Installation Problems, Q&A</title>
38 <para>I go to boot from the hard disk for the first time
39 after installing &os;, the kernel loads and probes my
40 hardware, but stops with messages like:</para>
42 <screen>changing root device to wd1s1a panic: cannot mount root</screen>
43 <para>What is wrong? What can I do?</para>
46 <literal>bios_drive:interface(unit,partition)kernel_name</literal>
47 thing that is displayed with the boot help?</para>
50 <para>There is a longstanding problem in the case where the
51 boot disk is not the first disk in the system. The BIOS
52 uses a different numbering scheme to &os;, and working
53 out which numbers correspond to which is difficult to get
56 <para>In the case where the boot disk is not the first disk
57 in the system, &os; can need some help finding it. There
58 are two common situations here, and in both of these cases,
59 you need to tell &os; where the root filesystem is. You
60 do this by specifying the BIOS disk number, the disk type
61 and the &os; disk number for that type.</para>
63 <para>The first situation is where you have two IDE disks,
64 each configured as the master on their respective IDE
65 busses, and wish to boot &os; from the second disk. The
66 BIOS sees these as disk 0 and disk 1, while &os; sees
67 them as <devicename>wd0</devicename> and
68 <devicename>wd2</devicename>.</para>
70 <para>&os; is on BIOS disk 1, of type
71 <literal>wd</literal> and the &os; disk number is 2, so
74 <screen><userinput>1:wd(2,a)kernel</userinput></screen>
76 <para>Note that if you have a slave on the primary bus, the
77 above is not necessary (and is effectively wrong).</para>
79 <para>The second situation involves booting from a SCSI disk
80 when you have one or more IDE disks in the system. In this
81 case, the &os; disk number is lower than the BIOS disk
82 number. If you have two IDE disks as well as the SCSI disk,
83 the SCSI disk is BIOS disk 2, type <literal>da</literal> and
84 &os; disk number 0, so you would say:</para>
86 <screen><userinput>2:da(0,a)kernel</userinput></screen>
88 <para>To tell &os; that you want to boot from BIOS disk
89 2, which is the first SCSI disk in the system. If you only
90 had one IDE disk, you would use '1:' instead.</para>
92 <para>Once you have determined the correct values to use,
93 you can put the command exactly as you would have typed it
94 in the <filename>/boot.config</filename> file using a
95 standard text editor. Unless instructed otherwise, &os;
96 will use the contents of this file as the default response
97 to the <literal>boot:</literal> prompt.</para>
102 <para>I go to boot from the hard disk for the first time
103 after installing &os;, but the Boot Manager prompt just
104 prints <literal>F?</literal> at the boot menu each time but
105 the boot won't go any further.</para>
108 <para>The hard disk geometry was set incorrectly in the
109 Partition editor when you installed &os;. Go back into
110 the partition editor and specify the actual geometry of your
111 hard disk. You must reinstall &os; again from the
112 beginning with the correct geometry.</para>
114 <para>If you are failing entirely in figuring out the
115 correct geometry for your machine, here's a tip: Install a
116 small DOS partition at the beginning of the disk and install
117 &os; after that. The install program will see the DOS
118 partition and try to infer the correct geometry from it,
119 which usually works.</para>
121 <para>The following tip is no longer recommended, but is left here
122 for reference:</para>
125 <para>If you are setting up a truly dedicated &os;
126 server or workstation where you don't care for (future)
127 compatibility with DOS, Linux or another operating system,
128 you've also got the option to use the entire disk (`A' in
129 the partition editor), selecting the non-standard option
130 where &os; occupies the entire disk from the very first
131 to the very last sector. This will leave all geometry
132 considerations aside, but is somewhat limiting unless
133 you're never going to run anything other than &os; on a
141 <title>Known Hardware Problems, Q&A</title>
144 <para>Please send hardware tips for this section to &a.jkh;.</para>
150 <para>The &man.mcd.4; driver keeps thinking that it has
151 found a device and this stops my Intel EtherExpress card
155 <para>Use the UserConfig utility (see
156 <filename>HARDWARE.TXT</filename>) and disable the probing
157 of the <devicename>mcd0</devicename> and
158 <devicename>mcd1</devicename> devices. Generally speaking,
159 you should only leave the devices that you will be using
160 enabled in your kernel.</para>
165 <para>&os; claims to support the 3Com PCMCIA card, but my
166 card isn't recognized when it's plugged into my
170 <para>There are a couple of possible problems. First of
171 all, &os; does not support multi-function cards, so if
172 you have a combo Ethernet/modem card (such as the 3C562), it
173 won't work. The default driver for the 3C589 card was
174 written just like all of the other drivers in &os;, and
175 depend on the card's own configuration data stored in NVRAM
176 to work. You must correctly configure &os;'s driver to
177 match the IRQ, port, and IOMEM stored in NVRAM.</para>
179 <para>Unfortunately, the only program capable of reading
180 them is the 3COM supplied DOS program. This program must be
181 run on a absolutely clean system (no other drivers must be
182 running), and the program will whine about CARD-Services not
183 being found, but it will continue. This is necessary to
184 read the NVRAM values. You want to know the IRQ, port, and
185 IOMEM values (the latter is called the CIS tuple by 3COM).
186 The first two can be set in the program, the third is
187 un-settable, and can only be read. Once you have these
188 values, set them in UserConfig and your card will be
194 <para>&os; finds my PCMCIA network card, but no packets
195 appear to be sent even though it claims to be working.</para>
198 <para>Many PCMCIA cards have the ability to use either the
199 10-Base2 (BNC) or 10-BaseT connectors for connecting to the
200 network. The driver is unable to <quote>auto-select</quote>
201 the correct connector, so you must tell it which connector
202 to use. In order to switch between the two connectors, the
203 link flags must be set. Depending on the model of the card,
204 <option>-link0 link1</option> or <option>-link0
205 -link1</option> will choose the correct network connector.
206 You can set these in &man.sysinstall.8; by using the
207 <literal>Extra options to ifconfig:</literal> field in the
208 network setup screen.</para>
213 <para>The system finds my &man.ed.4; network card, but I
214 keep getting device timeout errors.</para>
217 <para>Your card is probably on a different IRQ from what is
218 specified in the kernel configuration. The ed driver does
219 not use the `soft' configuration by default (values entered
220 using EZSETUP in DOS), but it will use the software
221 configuration if you specify <literal>?</literal> in the IRQ field of your
222 kernel config file.</para>
224 <para>Either move the jumper on the card to a hard
225 configuration setting (altering the kernel settings if
226 necessary), or specify the IRQ as <literal>-1</literal> in UserConfig or <literal>?</literal>
227 in your kernel config file. This will tell the kernel to
228 use the soft configuration.</para>
230 <para>Another possibility is that your card is at IRQ 9,
231 which is shared by IRQ 2 and frequently a cause of problems
232 (especially when you have a VGA card using IRQ 2!). You
233 should not use IRQ 2 or 9 if at all possible.</para>
238 <para>I booted the install floppy on my IBM ThinkPad (tm)
239 laptop, and the keyboard is all messed up.</para>
242 <para>Older IBM laptops use a non-standard keyboard
243 controller, so you must tell the keyboard driver (atkbd0) to
244 go into a special mode which works on the ThinkPads. Change
245 the atkbd0 'Flags' to 0x4 in UserConfig and it should work
246 fine. (Look in the Input Menu for 'Keyboard'.)</para>
251 <para>When I try to boot the install floppy, I see the
252 following message and nothing seems to be happening. I
253 cannot enter anything from the keyboard either.</para>
255 <screen>Keyboard: no</screen>
258 <para>Due to lack of space, full support for old XT/AT
259 (84-key) keyboards is no longer available in the bootblocks.
260 Some notebook computers may also have this type of keyboard.
261 If you are still using this kind of hardware, you will see
262 the above message appears when you boot from the CD-ROM or
263 an install floppy.</para>
265 <para>As soon as you see this message, hit the space bar,
266 and you will see the prompt:</para>
268 <screen>>> FreeBSD/i386 BOOT
269 Default: x:xx(x,x)/boot/loader
272 <para>Then enter <userinput>-Dh</userinput>, and things
273 should proceed normally.</para>
278 <para>I have a Matsushita/Panasonic CR-522, a
279 Matsushita/Panasonic CR-523 or a TEAC CD55a drive, but it is
280 not recognized even when the correct I/O port is set.</para>
283 <para>These CD-ROM drives are currently not supported by
284 &os;. The command sets for these drives are not compatible
285 with the double-speed CR-562 and CR-563 drives.</para>
287 <para>The single-speed CR-522 and CR-523 drives can be
288 identified by their use of a CD-caddy. </para>
293 <para>I'm trying to install from a tape drive but all I get
294 is something like this on the screen:</para>
296 <screen>sa0(aha0:1:0) NOT READY csi 40,0,0,0</screen>
299 <para>There's a limitation in the current &man.sysinstall.8;
300 that the tape <emphasis>must</emphasis> be in the drive
301 while &man.sysinstall.8; is started or it won't be detected.
302 Try again with the tape in the drive the whole time.</para>
307 <para>I've installed &os; onto my system, but it hangs
308 when booting from the hard drive with the message:</para>
310 <screen>Changing root to /dev/da0a</screen>
313 <para>his problem may occur in a system with a 3com 3c509
314 Ethernet adapter. The &man.ep.4; device driver appears to
315 be sensitive to probes for other devices that also use
316 address 0x300. Boot your &os; system by power cycling
317 the machine (turn off and on). At the
318 <literal>Boot:</literal> prompt specify the
319 <option>-c</option>. This will invoke UserConfig (see
320 <xref linkend="repairing"> above).
321 Use the <literal>disable</literal>
322 command to disable the device probes for all devices at
323 address 0x300 except the ep0 driver. On exit, your machine
324 should successfully boot &os;.</para>
329 <para>My system can not find my Intel EtherExpress 16 card.</para>
332 <para>You must set your Intel EtherExpress 16 card to be
333 memory mapped at address 0xD0000, and set the amount of
334 mapped memory to 32K using the Intel supplied
335 <filename>softset.exe</filename> program.</para>
340 <para>When installing on an EISA HP Netserver, my on-board
341 AIC-7xxx SCSI controller isn't detected.</para>
344 <para>This is a known problem, and will hopefully be fixed
345 in the future. In order to get your system installed at
346 all, boot with the <option>-c</option> option into
347 UserConfig, but <emphasis>don't</emphasis> use the pretty
348 visual mode but the plain old CLI mode. Type:</para>
350 <screen><userinput>eisa 12</userinput>
351 <userinput>quit</userinput></screen>
353 <para>at the prompt. (Instead of `quit', you might also
354 type `visual', and continue the rest of the configuration
355 session in visual mode.) While it's recommended to compile
356 a custom kernel, dset now also understands to save
359 <para>Refer to the FAQ topic 3.16 for an explanation of the
360 problem, and for how to continue. Remember that you can
361 find the FAQ on your local system in /usr/share/doc/FAQ,
362 provided you have installed the `doc' distribution.</para>
367 <para>I have a Panasonic AL-N1 or Rios Chandler Pentium
368 machine and I find that the system hangs before ever getting
369 into the installation now.</para>
372 <para>Your machine doesn't like the new
373 <literal>i586_copyout</literal> and
374 <literal>i586_copyin</literal> code for some reason. To
375 disable this, boot the installation boot floppy and when it
376 comes to the very first menu (the choice to drop into kernel
377 UserConfig mode or not) choose the command-line interface
378 (<quote>expert mode</quote>) version and type the following
381 <screen><userinput>flags npx0 1</userinput></screen>
383 <para>Then proceed normally to boot. This will be saved
384 into your kernel, so you only need to do it once.</para>
389 <para>I have this CMD640 IDE controller that is said to be
393 <para>Yes, it is. &os; does not support this controller
394 except through the legacy wdc driver.</para>
399 <para>On a Compaq Aero notebook, I get the message <quote>No
400 floppy devices found! Please check ...</quote> when trying to
401 install from floppy.</para>
404 <para>With Compaq being always a little different from other
405 systems, they do not announce their floppy drive in the CMOS
406 RAM of an Aero notebook. Therefore, the floppy disk driver
407 assumes there is no drive configured. Go to the UserConfig
408 screen, and set the Flags value of the fdc0 device to 0x1.
409 This pretends the existence of the first floppy drive (as a
410 1.44 MB drive) to the driver without asking the CMOS at
416 <para>When I go to boot my Intel AL440LX
417 (<quote>Atlanta</quote>) -based system from the hard disk the
418 first time, it stops with a <literal>Read Error</literal>
422 <para>There appears to be a bug in the BIOS on at least some
423 of these boards, this bug results in the &os; bootloader
424 thinking that it is booting from a floppy disk. This is
425 only a problem if you are not using the BootEasy boot
426 manager. Slice the disk in <quote>compatible</quote>mode
427 and install BootEasy during the &os; installation to
428 avoid the bug, or upgrade the BIOS (see Intel's website for
434 <para>When installing on an Dell Poweredge XE, Dell
435 proprietary RAID controller DSA (Dell SCSI Array) isn't
439 <para>Configure the DSA to use AHA-1540 emulation using EISA
440 configuration utility. After that &os; detects the DSA
441 as an Adaptec AHA-1540 SCSI controller, with irq 11 and port
442 340. Under emulation mode system will use DSA RAID disks,
443 but you cannot use DSA-specific features such as watching
449 <para>My Ethernet adapter is detected as an AMD PCnet-FAST
450 (or similar) but it doesn't work. (Eg. onboard Ethernet on
451 IBM Netfinity 5xxx or 7xxx)</para>
454 <para>The &man.lnc.4; driver is currently faulty, and will
455 often not work correctly with the PCnet-FAST and
456 PCnet-FAST+. You need to install a different Ethernet
462 <para>I have an IBM EtherJet PCI card, it is detected by the
463 &man.fxp.4; driver correctly, but the lights on the card don't
464 come on and it doesn't connect to the network.</para>
467 <para>We don't understand why this happens. Neither do IBM
468 (we asked them). The card is a standard Intel EtherExpress
469 Pro/100 with an IBM label on it, and these cards normally
470 work just fine. You may see these symptoms only in some IBM
471 Netfinity servers. The only solution is to install a
472 different Ethernet adapter.</para>
477 <para>When I configure the network during installation on an
478 IBM Netfinity 3500, the system freezes.</para>
481 <para>There is a problem with the onboard Ethernet in the
482 Netfinity 3500 which we have not been able to identify at
483 this time. It may be related to the SMP features of the
484 system being misconfigured. You will have to install
485 another Ethernet adapter and avoid attempting to configure
486 the onboard adapter at any time.</para>
491 <para>When I install onto a drive managed by a Mylex PCI
492 RAID controller, the system fails to boot (eg. with a
493 <literal>read error</literal> message).</para>
496 <para>There is a bug in the Mylex driver which results in it
497 ignoring the <quote>8GB</quote> geometry mode setting in the
498 BIOS. Use the 2GB mode instead.</para>