2 The FreeBSD Documentation Project
3 The FreeBSD French Documentation Project
9 This file contains the comments of the old TROUBLE.TXT file.
12 <title>***Non traduit***Troubleshooting</title>
14 <sect2 id="repairing">
15 <title>Repairing an Existing &os; Installation</title>
18 <quote>Fixit</quote> option in the top menu of the boot floppy.
19 To use it, you will also need either a
20 <filename>fixit.flp</filename> image floppy, generated in the same
21 fashion as the boot floppy, or the <quote>live filesystem</quote>
22 CDROM; typically the second CDROM in a multi-disc &os;
25 <para>To invoke fixit, simply boot the
26 <filename>kern.flp</filename> floppy, choose the
27 <quote>Fixit</quote> item and insert the fixit floppy or CDROM
28 when asked. You will then be placed into a shell with a wide
29 variety of commands available (in the <filename>/stand</filename>
30 and <filename>/mnt2/stand</filename> directories) for checking,
31 repairing and examining filesystems and their contents. Some
32 UNIX administration experience <emphasis>is</emphasis> required to
33 use the fixit option.</para>
37 <title>Common Installation Problems, Q&A</title>
42 <para>I go to boot from the hard disk for the first time
43 after installing &os;, the kernel loads and probes my
44 hardware, but stops with messages like:</para>
46 <screen>changing root device to wd1s1a panic: cannot mount root</screen>
47 <para>What is wrong? What can I do?</para>
50 <literal>bios_drive:interface(unit,partition)kernel_name</literal>
51 thing that is displayed with the boot help?</para>
54 <para>There is a longstanding problem in the case where the
55 boot disk is not the first disk in the system. The BIOS
56 uses a different numbering scheme to &os;, and working
57 out which numbers correspond to which is difficult to get
60 <para>In the case where the boot disk is not the first disk
61 in the system, &os; can need some help finding it. There
62 are two common situations here, and in both of these cases,
63 you need to tell &os; where the root filesystem is. You
64 do this by specifying the BIOS disk number, the disk type
65 and the &os; disk number for that type.</para>
67 <para>The first situation is where you have two IDE disks,
68 each configured as the master on their respective IDE
69 busses, and wish to boot &os; from the second disk. The
70 BIOS sees these as disk 0 and disk 1, while &os; sees
71 them as <devicename>wd0</devicename> and
72 <devicename>wd2</devicename>.</para>
74 <para>&os; is on BIOS disk 1, of type
75 <literal>wd</literal> and the &os; disk number is 2, so
78 <screen><userinput>1:wd(2,a)kernel</userinput></screen>
80 <para>Note that if you have a slave on the primary bus, the
81 above is not necessary (and is effectively wrong).</para>
83 <para>The second situation involves booting from a SCSI disk
84 when you have one or more IDE disks in the system. In this
85 case, the &os; disk number is lower than the BIOS disk
86 number. If you have two IDE disks as well as the SCSI disk,
87 the SCSI disk is BIOS disk 2, type <literal>da</literal> and
88 &os; disk number 0, so you would say:</para>
90 <screen><userinput>2:da(0,a)kernel</userinput></screen>
92 <para>To tell &os; that you want to boot from BIOS disk
93 2, which is the first SCSI disk in the system. If you only
94 had one IDE disk, you would use '1:' instead.</para>
96 <para>Once you have determined the correct values to use,
97 you can put the command exactly as you would have typed it
98 in the <filename>/boot.config</filename> file using a
99 standard text editor. Unless instructed otherwise, &os;
100 will use the contents of this file as the default response
101 to the <literal>boot:</literal> prompt.</para>
106 <para>I go to boot from the hard disk for the first time
107 after installing &os;, but the Boot Manager prompt just
108 prints <literal>F?</literal> at the boot menu each time but
109 the boot won't go any further.</para>
112 <para>The hard disk geometry was set incorrectly in the
113 Partition editor when you installed &os;. Go back into
114 the partition editor and specify the actual geometry of your
115 hard disk. You must reinstall &os; again from the
116 beginning with the correct geometry.</para>
118 <para>If you are failing entirely in figuring out the
119 correct geometry for your machine, here's a tip: Install a
120 small DOS partition at the beginning of the disk and install
121 &os; after that. The install program will see the DOS
122 partition and try to infer the correct geometry from it,
123 which usually works.</para>
125 <para>The following tip is no longer recommended, but is left here
126 for reference:</para>
129 <para>If you are setting up a truly dedicated &os;
130 server or workstation where you don't care for (future)
131 compatibility with DOS, Linux or another operating system,
132 you've also got the option to use the entire disk (`A' in
133 the partition editor), selecting the non-standard option
134 where &os; occupies the entire disk from the very first
135 to the very last sector. This will leave all geometry
136 considerations aside, but is somewhat limiting unless
137 you're never going to run anything other than &os; on a
145 <title>Known Hardware Problems, Q&A</title>
148 <para>Please send hardware tips for this section to &a.jkh;.</para>
154 <para>The &man.mcd.4; driver keeps thinking that it has
155 found a device and this stops my Intel EtherExpress card
159 <para>Use the UserConfig utility (see
160 <filename>HARDWARE.TXT</filename>) and disable the probing
161 of the <devicename>mcd0</devicename> and
162 <devicename>mcd1</devicename> devices. Generally speaking,
163 you should only leave the devices that you will be using
164 enabled in your kernel.</para>
169 <para>&os; claims to support the 3Com PCMCIA card, but my
170 card isn't recognized when it's plugged into my
174 <para>There are a couple of possible problems. First of
175 all, &os; does not support multi-function cards, so if
176 you have a combo Ethernet/modem card (such as the 3C562), it
177 won't work. The default driver for the 3C589 card was
178 written just like all of the other drivers in &os;, and
179 depend on the card's own configuration data stored in NVRAM
180 to work. You must correctly configure &os;'s driver to
181 match the IRQ, port, and IOMEM stored in NVRAM.</para>
183 <para>Unfortunately, the only program capable of reading
184 them is the 3COM supplied DOS program. This program must be
185 run on an absolutely clean system (no other drivers must be
186 running), and the program will whine about CARD-Services not
187 being found, but it will continue. This is necessary to
188 read the NVRAM values. You want to know the IRQ, port, and
189 IOMEM values (the latter is called the CIS tuple by 3COM).
190 The first two can be set in the program, the third is
191 un-settable, and can only be read. Once you have these
192 values, set them in UserConfig and your card will be
198 <para>&os; finds my PCMCIA network card, but no packets
199 appear to be sent even though it claims to be working.</para>
202 <para>Many PCMCIA cards have the ability to use either the
203 10-Base2 (BNC) or 10-BaseT connectors for connecting to the
204 network. The driver is unable to <quote>auto-select</quote>
205 the correct connector, so you must tell it which connector
206 to use. In order to switch between the two connectors, the
207 link flags must be set. Depending on the model of the card,
208 <option>-link0 link1</option> or <option>-link0
209 -link1</option> will choose the correct network connector.
210 You can set these in &man.sysinstall.8; by using the
211 <literal>Extra options to ifconfig:</literal> field in the
212 network setup screen.</para>
217 <para>The system finds my &man.ed.4; network card, but I
218 keep getting device timeout errors.</para>
221 <para>Your card is probably on a different IRQ from what is
222 specified in the kernel configuration. The ed driver does
223 not use the `soft' configuration by default (values entered
224 using EZSETUP in DOS), but it will use the software
225 configuration if you specify <literal>?</literal> in the IRQ field of your
226 kernel config file.</para>
228 <para>Either move the jumper on the card to a hard
229 configuration setting (altering the kernel settings if
230 necessary), or specify the IRQ as <literal>-1</literal> in UserConfig or <literal>?</literal>
231 in your kernel config file. This will tell the kernel to
232 use the soft configuration.</para>
234 <para>Another possibility is that your card is at IRQ 9,
235 which is shared by IRQ 2 and frequently a cause of problems
236 (especially when you have a VGA card using IRQ 2!). You
237 should not use IRQ 2 or 9 if at all possible.</para>
242 <para>I have a Matsushita/Panasonic drive but it isn't
243 recognized by the system.</para>
246 <para>Make certain that the I/O port that the &man.matcd.4; driver
247 is set to is correct for the host interface card you have.
248 (Some SoundBlaster DOS drivers report a hardware I/O port
249 address for the CD-ROM interface that is 0x10 lower than it
252 <para>If you are unable to determine the settings for the
253 card by examining the board or documentation, you can use
254 UserConfig to change the 'port' address (I/O port) to -1 and
255 start the system. This setting causes the driver to look at
256 a number of I/O ports that various manufacturers use for
257 their Matsushita/Panasonic/Creative CD-ROM interfaces. Once
258 the driver locates the address, you should run UserConfig
259 again and specify the correct address. Leaving the 'port'
260 parameter set to -1 increases the amount of time that it
261 takes the system to boot, and this could interfere with
262 other devices.</para>
264 <para>The double-speed Matsushita CR-562 and CR-563 are the
265 only drives that are supported.</para>
270 <para>I booted the install floppy on my IBM ThinkPad (tm)
271 laptop, and the keyboard is all messed up.</para>
274 <para>Older IBM laptops use a non-standard keyboard
275 controller, so you must tell the keyboard driver (atkbd0) to
276 go into a special mode which works on the ThinkPads. Change
277 the atkbd0 'Flags' to 0x4 in UserConfig and it should work
278 fine. (Look in the Input Menu for 'Keyboard'.)</para>
283 <para>When I try to boot the install floppy, I see the
284 following message and nothing seems to be happening. I
285 cannot enter anything from the keyboard either.</para>
287 <screen>Keyboard: no</screen>
290 <para>Due to lack of space, full support for old XT/AT
291 (84-key) keyboards is no longer available in the bootblocks.
292 Some notebook computers may also have this type of keyboard.
293 If you are still using this kind of hardware, you will see
294 the above message appears when you boot from the CD-ROM or
295 an install floppy.</para>
297 <para>As soon as you see this message, hit the space bar,
298 and you will see the prompt:</para>
300 <screen>>> FreeBSD/i386 BOOT
301 Default: x:xx(x,x)/boot/loader
304 <para>Then enter <userinput>-Dh</userinput>, and things
305 should proceed normally.</para>
310 <para>I have a Matsushita/Panasonic CR-522, a
311 Matsushita/Panasonic CR-523 or a TEAC CD55a drive, but it is
312 not recognized even when the correct I/O port is set.</para>
315 <para>These CD-ROM drives are currently not supported by
316 &os;. The command sets for these drives are not compatible
317 with the double-speed CR-562 and CR-563 drives.</para>
319 <para>The single-speed CR-522 and CR-523 drives can be
320 identified by their use of a CD-caddy. </para>
325 <para>I'm trying to install from a tape drive but all I get
326 is something like this on the screen:</para>
328 <screen>sa0(aha0:1:0) NOT READY csi 40,0,0,0</screen>
331 <para>There's a limitation in the current &man.sysinstall.8;
332 that the tape <emphasis>must</emphasis> be in the drive
333 while &man.sysinstall.8; is started or it won't be detected.
334 Try again with the tape in the drive the whole time.</para>
339 <para>I've installed &os; onto my system, but it hangs
340 when booting from the hard drive with the message:</para>
342 <screen>Changing root to /dev/da0a</screen>
345 <para>his problem may occur in a system with a 3com 3c509
346 Ethernet adapter. The &man.ep.4; device driver appears to
347 be sensitive to probes for other devices that also use
348 address 0x300. Boot your &os; system by power cycling
349 the machine (turn off and on). At the
350 <literal>Boot:</literal> prompt specify the
351 <option>-c</option>. This will invoke UserConfig (see
352 <xref linkend="repairing"> above).
353 Use the <literal>disable</literal>
354 command to disable the device probes for all devices at
355 address 0x300 except the ep0 driver. On exit, your machine
356 should successfully boot &os;.</para>
361 <para>My system can not find my Intel EtherExpress 16 card.</para>
364 <para>You must set your Intel EtherExpress 16 card to be
365 memory mapped at address 0xD0000, and set the amount of
366 mapped memory to 32K using the Intel supplied
367 <filename>softset.exe</filename> program.</para>
372 <para>When installing on an EISA HP Netserver, my on-board
373 AIC-7xxx SCSI controller isn't detected.</para>
376 <para>This is a known problem, and will hopefully be fixed
377 in the future. In order to get your system installed at
378 all, boot with the <option>-c</option> option into
379 UserConfig, but <emphasis>don't</emphasis> use the pretty
380 visual mode but the plain old CLI mode. Type:</para>
382 <screen><userinput>eisa 12</userinput>
383 <userinput>quit</userinput></screen>
385 <para>at the prompt. (Instead of `quit', you might also
386 type `visual', and continue the rest of the configuration
387 session in visual mode.) While it's recommended to compile
388 a custom kernel, dset now also understands to save
391 <para>Refer to the FAQ topic 3.16 for an explanation of the
392 problem, and for how to continue. Remember that you can
393 find the FAQ on your local system in /usr/share/doc/FAQ,
394 provided you have installed the `doc' distribution.</para>
399 <para>I have a Panasonic AL-N1 or Rios Chandler Pentium
400 machine and I find that the system hangs before ever getting
401 into the installation now.</para>
404 <para>Your machine doesn't like the new
405 <literal>i586_copyout</literal> and
406 <literal>i586_copyin</literal> code for some reason. To
407 disable this, boot the installation boot floppy and when it
408 comes to the very first menu (the choice to drop into kernel
409 UserConfig mode or not) choose the command-line interface
410 (<quote>expert mode</quote>) version and type the following
413 <screen><userinput>flags npx0 1</userinput></screen>
415 <para>Then proceed normally to boot. This will be saved
416 into your kernel, so you only need to do it once.</para>
421 <para>I have this CMD640 IDE controller that is said to be
425 <para>Yes, it is. &os; does not support this controller
426 except through the legacy wdc driver.</para>
431 <para>On a Compaq Aero notebook, I get the message <quote>No
432 floppy devices found! Please check ...</quote> when trying to
433 install from floppy.</para>
436 <para>With Compaq being always a little different from other
437 systems, they do not announce their floppy drive in the CMOS
438 RAM of an Aero notebook. Therefore, the floppy disk driver
439 assumes there is no drive configured. Go to the UserConfig
440 screen, and set the Flags value of the fdc0 device to 0x1.
441 This pretends the existence of the first floppy drive (as a
442 1.44 MB drive) to the driver without asking the CMOS at
448 <para>When I go to boot my Intel AL440LX
449 (<quote>Atlanta</quote>) -based system from the hard disk the
450 first time, it stops with a <literal>Read Error</literal>
454 <para>There appears to be a bug in the BIOS on at least some
455 of these boards, this bug results in the &os; bootloader
456 thinking that it is booting from a floppy disk. This is
457 only a problem if you are not using the BootEasy boot
458 manager. Slice the disk in <quote>compatible</quote>mode
459 and install BootEasy during the &os; installation to
460 avoid the bug, or upgrade the BIOS (see Intel's web site for
466 <para>When installing on a Dell Poweredge XE, Dell
467 proprietary RAID controller DSA (Dell SCSI Array) isn't
471 <para>Configure the DSA to use AHA-1540 emulation using EISA
472 configuration utility. After that &os; detects the DSA
473 as an Adaptec AHA-1540 SCSI controller, with irq 11 and port
474 340. Under emulation mode system will use DSA RAID disks,
475 but you cannot use DSA-specific features such as watching
481 <para>My Ethernet adapter is detected as an AMD PCnet-FAST
482 (or similar) but it doesn't work. (Eg. onboard Ethernet on
483 IBM Netfinity 5xxx or 7xxx)</para>
486 <para>The &man.lnc.4; driver is currently faulty, and will
487 often not work correctly with the PCnet-FAST and
488 PCnet-FAST+. You need to install a different Ethernet
494 <para>I have an IBM EtherJet PCI card, it is detected by the
495 &man.fxp.4; driver correctly, but the lights on the card don't
496 come on and it doesn't connect to the network.</para>
499 <para>We don't understand why this happens. Neither do IBM
500 (we asked them). The card is a standard Intel EtherExpress
501 Pro/100 with an IBM label on it, and these cards normally
502 work just fine. You may see these symptoms only in some IBM
503 Netfinity servers. The only solution is to install a
504 different Ethernet adapter.</para>
509 <para>When I configure the network during installation on an
510 IBM Netfinity 3500, the system freezes.</para>
513 <para>There is a problem with the onboard Ethernet in the
514 Netfinity 3500 which we have not been able to identify at
515 this time. It may be related to the SMP features of the
516 system being misconfigured. You will have to install
517 another Ethernet adapter and avoid attempting to configure
518 the onboard adapter at any time.</para>
523 <para>When I install onto a drive managed by a Mylex PCI
524 RAID controller, the system fails to boot (eg. with a
525 <literal>read error</literal> message).</para>
528 <para>There is a bug in the Mylex driver which results in it
529 ignoring the <quote>8GB</quote> geometry mode setting in the
530 BIOS. Use the 2GB mode instead.</para>