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