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