1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta name="generator" content="HTML Tidy, see www.w3.org">
<title>FreeBSD/i386 4.7-RELEASE Installation
Instructions</title>
<meta name="GENERATOR" content=
"Modular DocBook HTML Stylesheet Version 1.73 ">
<link rel="STYLESHEET" type="text/css" href="docbook.css">
</head>
<body class="ARTICLE" bgcolor="#FFFFFF" text="#000000" link=
"#0000FF" vlink="#840084" alink="#0000FF">
<div class="ARTICLE">
<div class="TITLEPAGE">
<h1 class="TITLE"><a name="AEN2">FreeBSD/i386 4.7-RELEASE
Installation Instructions</a></h1>
<h3 class="CORPAUTHOR">The FreeBSD Project</h3>
<p class="COPYRIGHT">Copyright © 2000, 2001, 2002 by
The FreeBSD Documentation Project</p>
<hr>
</div>
<blockquote class="ABSTRACT">
<div class="ABSTRACT">
<a name="AEN10"></a>
<p>This article gives some brief instructions on
installing FreeBSD/i386 4.7-RELEASE, with particular
emphasis given to obtaining a FreeBSD distribution. Some
notes on troubleshooting and frequently-asked questions
are also given.</p>
</div>
</blockquote>
<div class="SECT1">
<hr>
<h1 class="SECT1"><a name="AEN12">1 Installing
FreeBSD</a></h1>
<p>This section documents the process of installing a new
distribution of FreeBSD. These instructions pay particular
emphasis to the process of obtaining the FreeBSD
4.7-RELEASE distribution and to beginning the installation
procedure. The <a href=
"http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install.html"
target="_top">``Installing FreeBSD''</a> chapter of the <a
href=
"http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/"
target="_top">FreeBSD Handbook</a> provides more in-depth
information about the installation program itself,
including a guided walkthrough with screenshots.</p>
<p>If you are upgrading from a previous release of FreeBSD,
please see <a href="#UPGRADING">Section 3</a> for
instructions on upgrading.</p>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="GETTING-STARTED">1.1 Getting
Started</a></h2>
<p>Probably the most important pre-installation step that
can be taken is that of reading the various instruction
documents provided with FreeBSD. A roadmap of documents
pertaining to this release of FreeBSD can be found in <tt
class="FILENAME">README.TXT</tt>, which can usually be
found in the same location as this file; most of these
documents, such as the release notes and the hardware
compatability list, are also accessible in the
Documentation menu of the installer.</p>
<p>Note that on-line versions of the FreeBSD <a href=
"http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/"
target="_top">FAQ</a> and <a href=
"http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/"
target="_top">Handbook</a> are also available from the
<a href="http://www.FreeBSD.org/" target="_top">FreeBSD
Project Web site</a>, if you have an Internet
connection.</p>
<p>This collection of documents may seem daunting, but
the time spent reading them will likely be saved many
times over. Being familiar with what resources are
available can also be helpful in the event of problems
during installation.</p>
<p>The best laid plans sometimes go awry, so if you run
into trouble take a look at <a href="#TROUBLE">Section
4</a>, which contains valuable troubleshooting
information. You should also read an updated copy of <tt
class="FILENAME">ERRATA.TXT</tt> before installing, since
this will alert you to any problems which have reported
in the interim for your particular release.</p>
<div class="IMPORTANT">
<blockquote class="IMPORTANT">
<p><b>Important:</b> While FreeBSD does its best to
safeguard against accidental loss of data, it's still
more than possible to <span class="emphasis"><i
class="EMPHASIS">wipe out your entire disk</i></span>
with this installation if you make a mistake. Please
do not proceed to the final FreeBSD installation menu
unless you've adequately backed up any important data
first.</p>
</blockquote>
</div>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN35">1.2 Hardware
Requirements</a></h2>
<p>FreeBSD for the IA-32 requires an 80386 or better
processor. The <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+4.7-RELEASE">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">sysinstall</span>(8)</span></a>
installation program requires 16MB of RAM; after
installation, FreeBSD itself can be run in 4-8MB of RAM
with a pared-down kernel. You will need at least 100MB of
free hard drive space for the most minimal installation;
a more realistic minimum is on the order of 250-350MB.
See below for ways of shrinking existing DOS partitions
in order to install FreeBSD.</p>
<p>If you are not familiar with configuring hardware for
FreeBSD, you should be sure to read the <tt class=
"FILENAME">HARDWARE.TXT</tt> file; it contains important
information on what hardware is supported by FreeBSD.</p>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="FLOPPIES">1.3 Floppy Disk
Image Instructions</a></h2>
<p>Depending on how you choose to install FreeBSD, you
may need to create a set of floppy disks (usually two) to
begin the installation process. This section briefly
describes how to create these disks, either from a CDROM
installation or from the Internet. Note that in the
common case of installing FreeBSD from CDROM, on a
machine that supports bootable CDROMs, the steps outlined
in this section will not be needed and can be
skipped.</p>
<p>For a normal CDROM or network installation, all you
need to copy onto actual floppies from the <tt class=
"FILENAME">floppies/</tt> directory are the <tt class=
"FILENAME">kern.flp</tt> and <tt class=
"FILENAME">mfsroot.flp</tt> images (for 1.44MB
floppies).</p>
<p>Getting these images over the network is easy. Simply
fetch the <tt class="REPLACEABLE"><i>release</i></tt><tt
class="FILENAME">/floppies/kern.flp</tt> and <tt class=
"REPLACEABLE"><i>release</i></tt><tt class=
"FILENAME">/floppies/mfsroot.flp</tt> files from <a href=
"ftp://ftp.FreeBSD.org/" target=
"_top">ftp://ftp.FreeBSD.org/</a> or one of the many
mirrors listed at <a href=
"http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html"
target="_top">FTP Sites</a> section of the Handbook, or
on the <a href="http://mirrorlist.FreeBSD.org/" target=
"_top">http://mirrorlist.FreeBSD.org/</a> Web pages.</p>
<p>Get two blank, freshly formatted floppies and image
copy <tt class="FILENAME">kern.flp</tt> onto one and <tt
class="FILENAME">mfsroot.flp</tt> onto the other. These
images are <span class="emphasis"><i class=
"EMPHASIS">not</i></span> DOS files. You cannot simply
copy them to a DOS or UFS floppy as regular files, you
need to ``image'' copy them to the floppy with <tt class=
"FILENAME">fdimage.exe</tt> under DOS (see the <tt class=
"FILENAME">tools</tt> directory on your CDROM or FreeBSD
FTP mirror) or the <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=dd&sektion=1&manpath=FreeBSD+4.7-RELEASE">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">dd</span>(1)</span></a> command in
UNIX.</p>
<p>For example, to create the kernel floppy image from
DOS, you'd do something like this:</p>
<pre class="SCREEN">
<tt class="PROMPT">C></tt> <tt class=
"USERINPUT"><b>fdimage kern.flp a:</b></tt>
</pre>
<p>Assuming that you'd copied <tt class=
"FILENAME">fdimage.exe</tt> and <tt class=
"FILENAME">kern.flp</tt> into a directory somewhere. You
would do the same for <tt class=
"FILENAME">mfsroot.flp</tt>, of course.</p>
<p>If you're creating the boot floppy from a UNIX
machine, you may find that:</p>
<pre class="SCREEN">
<tt class="PROMPT">#</tt> <tt class=
"USERINPUT"><b>dd if=floppies/kern.flp of=/dev/rfd0</b></tt>
</pre>
<p>or</p>
<pre class="SCREEN">
<tt class="PROMPT">#</tt> <tt class=
"USERINPUT"><b>dd if=floppies/kern.flp of=/dev/floppy</b></tt>
</pre>
<p>work well, depending on your hardware and operating
system environment (different versions of UNIX have
different names for the floppy drive).</p>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="START-INSTALLATION">1.4
Installing FreeBSD from CDROM or the Internet</a></h2>
<p>The easiest type of installation is from CDROM. If you
have a supported CDROM drive and a FreeBSD installation
CDROM, there are 2 ways of starting the installation from
it:</p>
<ul>
<li>
<p>If your system supports bootable CDROM media
(usually an option which can be selectively enabled
in the controller's setup menu or in the PC BIOS for
some systems) and you have it enabled, FreeBSD
supports the ``El Torrito'' bootable CD standard.
Simply put the installation CD in your CDROM drive
and boot the system to begin installation.</p>
</li>
<li>
<p>Build a set of FreeBSD boot floppies from the <tt
class="FILENAME">floppies/</tt> directory in every
FreeBSD distribution. Either simply use the <tt
class="FILENAME">makeflp.bat</tt> script from DOS or
read <a href="#FLOPPIES">Section 1.3</a> for more
information on creating the bootable floppies under
different operating systems. Then you simply boot
from the first floppy and you should soon be in the
FreeBSD installation.</p>
</li>
</ul>
<br>
<br>
<p>If you don't have a CDROM (or your computer does not
support booting from CDROM) and would like to simply
install over the net using PPP, SLIP or a dedicated
connection. You should start the installation by building
a set of FreeBSD boot floppies from the files <tt class=
"FILENAME">floppies/kern.flp</tt> and <tt class=
"FILENAME">floppies/mfsroot.flp</tt> using the
instructions found in <a href="#FLOPPIES">Section
1.3</a>. Restart your computer using the <tt class=
"FILENAME">kern.flp</tt> disk; when prompted, insert the
<tt class="FILENAME">mfsroot.flp</tt> disk. Then, please
go to <a href="#FTPNFS">Section 1.5.5</a> for additional
tips on installing via FTP or NFS.</p>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN131">1.5 Detail on various
installation types</a></h2>
<p>Once you've gotten yourself to the initial
installation screen somehow, you should be able to follow
the various menu prompts and go from there. If you've
never used the FreeBSD installation before, you are also
encouraged to read some of the documentation in the
Documentation submenu as well as the general ``Usage''
instructions on the first menu.</p>
<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> If you get stuck at a screen, press
the <b class="KEYCAP">F1</b> key for online
documentation relevant to that specific section.</p>
</blockquote>
</div>
<p>If you've never installed FreeBSD before, or even if
you have, the ``Standard'' installation mode is the most
recommended since it makes sure that you'll visit all the
various important checklist items along the way. If
you're much more comfortable with the FreeBSD
installation process and know <span class="emphasis"><i
class="EMPHASIS">exactly</i></span> what you want to do,
use the ``Express'' or ``Custom'' installation options.
If you're upgrading an existing system, use the
``Upgrade'' option.</p>
<p>The FreeBSD installer supports the direct use of
floppy, DOS, tape, CDROM, FTP, NFS and UFS partitions as
installation media; further tips on installing from each
type of media are listed below.</p>
<div class="SECT3">
<hr>
<h3 class="SECT3"><a name="AEN170">1.5.1 Installing
from a Network CDROM</a></h3>
<p>If you simply wish to install from a local CDROM
drive then see <a href="#START-INSTALLATION">Section
1.4</a>. If you don't have a CDROM drive on your system
and wish to use a FreeBSD distribution CD in the CDROM
drive of another system to which you have network
connectivity, there are also several ways of going
about it:</p>
<ul>
<li>
<p>If you would be able to FTP install FreeBSD
directly from the CDROM drive in some FreeBSD
machine, it's quite easy: You simply add the
following line to the password file (using the <a
href=
"http://www.FreeBSD.org/cgi/man.cgi?query=vipw&sektion=8&manpath=FreeBSD+4.7-RELEASE">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">vipw</span>(8)</span></a>
command):</p>
<pre class="SCREEN">
ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin
</pre>
<p>On the machine on which you are running the
install, go to the Options menu and set Release
Name to <tt class="LITERAL">any</tt>. You may then
choose a Media type of <tt class="LITERAL">FTP</tt>
and type in <tt class="FILENAME">ftp://<tt class=
"REPLACEABLE"><i>machine</i></tt></tt> after
picking ``URL'' in the ftp sites menu.</p>
<div class="WARNING">
<blockquote class="WARNING">
<p><b>Warning:</b> This may allow anyone on the
local network (or Internet) to make ``anonymous
FTP'' connections to this machine, which may
not be desirable.</p>
</blockquote>
</div>
</li>
<li>
<p>If you would rather use NFS to export the CDROM
directly to the machine(s) you'll be installing
from, you need to first add an entry to the <tt
class="FILENAME">/etc/exports</tt> file (on the
machine with the CDROM drive). The example below
allows the machine <tt class=
"HOSTID">ziggy.foo.com</tt> to mount the CDROM
directly via NFS during installation:</p>
<pre class="SCREEN">
/cdrom -ro ziggy.foo.com
</pre>
<p>The machine with the CDROM must also be
configured as an NFS server, of course, and if
you're not sure how to do that then an NFS
installation is probably not the best choice for
you unless you're willing to read up on <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=rc.conf&sektion=5&manpath=FreeBSD+4.7-RELEASE">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">rc.conf</span>(5)</span></a> and
configure things appropriately. Assuming that this
part goes smoothly, you should be able to enter:
<tt class="FILENAME"><tt class=
"REPLACEABLE"><i>cdrom-host</i></tt>:/cdrom</tt> as
the path for an NFS installation when the target
machine is installed, e.g. <tt class=
"FILENAME">wiggy:/cdrom</tt>.</p>
</li>
</ul>
</div>
<div class="SECT3">
<hr>
<h3 class="SECT3"><a name="AEN202">1.5.2 Installing
from Floppies</a></h3>
<p>If you must install from floppy disks, either due to
unsupported hardware or just because you enjoy doing
things the hard way, you must first prepare some
floppies for the install.</p>
<p>First, make your boot floppies as described in <a
href="#FLOPPIES">Section 1.3</a>.</p>
<p>Second, peruse <a href="#LAYOUT">Section 2</a> and
pay special attention to the ``Distribution Format''
section since it describes which files you're going to
need to put onto floppy and which you can safely
skip.</p>
<p>Next you will need, at minimum, as many 1.44MB
floppies as it takes to hold all files in the <tt
class="FILENAME">bin</tt> (binary distribution)
directory. If you're preparing these floppies under
DOS, then these floppies <span class="emphasis"><i
class="EMPHASIS">must</i></span> be formatted using the
MS-DOS <tt class="FILENAME">FORMAT</tt> command. If
you're using Windows, use the Windows File Manager
format command.</p>
<div class="IMPORTANT">
<blockquote class="IMPORTANT">
<p><b>Important:</b> Frequently, floppy disks come
``factory preformatted''. While convenient, many
problems reported by users in the past have
resulted from the use of improperly formatted
media. Re-format them yourself, just to make
sure.</p>
</blockquote>
</div>
<p>If you're creating the floppies from another FreeBSD
machine, a format is still not a bad idea though you
don't need to put a DOS filesystem on each floppy. You
can use the <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=disklabel&sektion=8&manpath=FreeBSD+4.7-RELEASE">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">disklabel</span>(8)</span></a> and <a
href=
"http://www.FreeBSD.org/cgi/man.cgi?query=newfs&sektion=8&manpath=FreeBSD+4.7-RELEASE">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">newfs</span>(8)</span></a> commands to
put a UFS filesystem on a floppy, as the following
sequence of commands illustrates:</p>
<pre class="SCREEN">
<tt class="PROMPT">#</tt> <tt class=
"USERINPUT"><b>fdformat -f 1440 fd0.1440</b></tt>
<tt class="PROMPT">#</tt> <tt class=
"USERINPUT"><b>disklabel -w -r fd0.1440 floppy3</b></tt>
<tt class="PROMPT">#</tt> <tt class=
"USERINPUT"><b>newfs -t 2 -u 18 -l 1 -i 65536 /dev/fd0</b></tt>
</pre>
<p>After you've formatted the floppies for DOS or UFS,
you'll need to copy the files onto them. The
distribution files are split into chunks conveniently
sized so that 5 of them will fit on a conventional
1.44MB floppy. Go through all your floppies, packing as
many files as will fit on each one, until you've got
all the distributions you want packed up in this
fashion. Each distribution should go into its own
subdirectory on the floppy, e.g.: <tt class=
"FILENAME">a:\bin\bin.inf</tt>, <tt class=
"FILENAME">a:\bin\bin.aa</tt>, <tt class=
"FILENAME">a:\bin\bin.ab</tt>, ...</p>
<div class="IMPORTANT">
<blockquote class="IMPORTANT">
<p><b>Important:</b> The <tt class=
"FILENAME">bin.inf</tt> file also needs to go on
the first floppy of the <tt class=
"FILENAME">bin</tt> set since it is read by the
installation program in order to figure out how
many additional pieces to look for when fetching
and concatenating the distribution. When putting
distributions onto floppies, the <tt class=
"FILENAME">distname.inf</tt> file <span class=
"emphasis"><i class="EMPHASIS">must</i></span>
occupy the first floppy of each distribution set.
This is also covered in <tt class=
"FILENAME">README.TXT</tt>.</p>
</blockquote>
</div>
<p>Once you come to the Media screen of the install,
select ``Floppy'' and you'll be prompted for the
rest.</p>
</div>
<div class="SECT3">
<hr>
<h3 class="SECT3"><a name="AEN244">1.5.3 Installing
from a DOS partition</a></h3>
<p>To prepare for installation from an MS-DOS partition
you should simply copy the files from the distribution
into a directory called <tt class=
"FILENAME">FREEBSD</tt> on the Primary DOS partition
(<tt class="DEVICENAME">C:</tt>). For example, to do a
minimal installation of FreeBSD from DOS using files
copied from the CDROM, you might do something like
this:</p>
<pre class="SCREEN">
<tt class="PROMPT">C:\></tt> <tt class=
"USERINPUT"><b>MD C:\FREEBSD</b></tt>
<tt class="PROMPT">C:\></tt> <tt class=
"USERINPUT"><b>XCOPY /S E:\BIN C:\FREEBSD\BIN</b></tt>
</pre>
<p>Assuming that <tt class="DEVICENAME">E:</tt> was
where your CD was mounted.</p>
<p>For as many distributions as you wish to install
from DOS (and you have free space for), install each
one in a directory under <tt class=
"FILENAME">C:\FREEBSD</tt> - the <tt class=
"FILENAME">BIN</tt> dist is only the minimal
requirement.</p>
<p>Once you've copied the directories, you can simply
launch the installation from floppies as normal and
select ``DOS'' as your media type when the time
comes.</p>
</div>
<div class="SECT3">
<hr>
<h3 class="SECT3"><a name="AEN261">1.5.4 Installing
from QIC/SCSI Tape</a></h3>
<p>When installing from tape, the installation program
expects the files to be simply tar'ed onto it, so after
fetching all of the files for the distributions you're
interested in, simply use <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=tar&sektion=1&manpath=FreeBSD+4.7-RELEASE">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">tar</span>(1)</span></a> to get them
onto the tape with a command something like this:</p>
<pre class="SCREEN">
<tt class="PROMPT">#</tt> <tt class="USERINPUT"><b>cd <tt
class="REPLACEABLE"><i>/where/you/have/your/dists</i></tt></b></tt>
<tt class="PROMPT">#</tt> <tt class=
"USERINPUT"><b>tar cvf /dev/rsa0 <tt class=
"REPLACEABLE"><i>dist1</i></tt> .. <tt class=
"REPLACEABLE"><i>dist2</i></tt></b></tt>
</pre>
<p>When you go to do the installation, you should also
make sure that you leave enough room in some temporary
directory (which you'll be allowed to choose) to
accommodate the <span class="emphasis"><i class=
"EMPHASIS">full</i></span> contents of the tape you've
created. Due to the non-random access nature of tapes,
this method of installation requires quite a bit of
temporary storage. You should expect to require as much
temporary storage as you have stuff written on
tape.</p>
<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> When going to do the installation,
the tape must be in the drive <span class=
"emphasis"><i class="EMPHASIS">before</i></span>
booting from the boot floppies. The installation
``probe'' may otherwise fail to find it.</p>
</blockquote>
</div>
<p>Now create a boot floppy as described in <a href=
"#FLOPPIES">Section 1.3</a> and proceed with the
installation.</p>
</div>
<div class="SECT3">
<hr>
<h3 class="SECT3"><a name="FTPNFS">1.5.5 Installing
over a Network using FTP or NFS</a></h3>
<p>After making the boot floppies as described in the
first section, you can load the rest of the
installation over a network using one of 3 types of
connections: serial port, parallel port, or
Ethernet.</p>
<div class="SECT4">
<hr>
<h4 class="SECT4"><a name="AEN286">1.5.5.1 Serial
Port</a></h4>
<p>SLIP support is rather primitive, and is limited
primarily to hard-wired links, such as a serial cable
running between two computers. The link must be
hard-wired because the SLIP installation doesn't
currently offer a dialing capability. If you need to
dial out with a modem or otherwise dialog with the
link before connecting to it, then I recommend that
the PPP utility be used instead.</p>
<p>If you're using PPP, make sure that you have your
Internet Service Provider's IP address and DNS
information handy as you'll need to know it fairly
early in the installation process. You may also need
to know your own IP address, though PPP supports
dynamic address negotiation and may be able to pick
up this information directly from your ISP if they
support it.</p>
<p>You will also need to know how to use the various
``AT commands'' for dialing out with your particular
brand of modem as the PPP dialer provides only a very
simple terminal emulator.</p>
</div>
<div class="SECT4">
<hr>
<h4 class="SECT4"><a name="AEN292">1.5.5.2 Parallel
Port</a></h4>
<p>If a hard-wired connection to another FreeBSD or
Linux machine is available, you might also consider
installing over a ``laplink'' style parallel port
cable. The data rate over the parallel port is much
higher than what is typically possible over a serial
line (up to 50k/sec), thus resulting in a quicker
installation. It's not typically necessary to use
``real'' IP addresses when using a point-to-point
parallel cable in this way and you can generally just
use RFC 1918 style addresses for the ends of the link
(e.g. <tt class="HOSTID">10.0.0.1</tt>, <tt class=
"HOSTID">10.0.0.2</tt>, etc).</p>
<div class="IMPORTANT">
<blockquote class="IMPORTANT">
<p><b>Important:</b> If you use a Linux machine
rather than a FreeBSD machine as your PLIP peer,
you will also have to specify <tt class=
"OPTION">link0</tt> in the TCP/IP setup screen's
``extra options for ifconfig'' field in order to
be compatible with Linux's slightly different
PLIP protocol.</p>
</blockquote>
</div>
</div>
<div class="SECT4">
<hr>
<h4 class="SECT4"><a name="AEN303">1.5.5.3
Ethernet</a></h4>
<p>FreeBSD supports many common Ethernet cards; a
table of supported cards is provided as part of the
FreeBSD Hardware Notes (see <tt class=
"FILENAME">HARDWARE.TXT</tt> in the Documentation
menu on the boot floppy or the top level directory of
the CDROM). If you are using one of the supported
PCMCIA Ethernet cards, also be sure that it's plugged
in <span class="emphasis"><i class=
"EMPHASIS">before</i></span> the laptop is powered
on. FreeBSD does not, unfortunately, currently
support ``hot insertion'' of PCMCIA cards during
installation.</p>
<p>You will also need to know your IP address on the
network, the <tt class="OPTION">netmask</tt> value
for your subnet and the name of your machine. Your
system administrator can tell you which values are
appropriate to your particular network setup. If you
will be referring to other hosts by name rather than
IP address, you'll also need a name server and
possibly the address of a gateway (if you're using
PPP, it's your provider's IP address) to use in
talking to it. If you want to install by FTP via an
HTTP proxy (see below), you will also need the
proxy's address.</p>
<p>If you do not know the answers to these questions
then you should really probably talk to your system
administrator <span class="emphasis"><i class=
"EMPHASIS">first</i></span> before trying this type
of installation. Using a randomly chosen IP address
or netmask on a live network is almost guaranteed not
to work, and will probably result in a lecture from
said system administrator.</p>
<p>Once you have a network connection of some sort
working, the installation can continue over NFS or
FTP.</p>
</div>
<div class="SECT4">
<hr>
<h4 class="SECT4"><a name="AEN314">1.5.5.4 NFS
installation tips</a></h4>
<p>NFS installation is fairly straight-forward:
Simply copy the FreeBSD distribution files you want
onto a server somewhere and then point the NFS media
selection at it.</p>
<p>If this server supports only ``privileged port''
access (this is generally the default for Sun and
Linux workstations), you will need to set this option
in the Options menu before installation can
proceed.</p>
<p>If you have a poor quality Ethernet card which
suffers from very slow transfer rates, you may also
wish to toggle the appropriate Options flag.</p>
<p>In order for NFS installation to work, the server
must also support ``subdir mounts'', e.g. if your
FreeBSD distribution directory lives on <tt class=
"FILENAME">wiggy:/usr/archive/stuff/FreeBSD</tt>,
then <tt class="HOSTID">wiggy</tt> will have to allow
the direct mounting of <tt class=
"FILENAME">/usr/archive/stuff/FreeBSD</tt>, not just
<tt class="FILENAME">/usr</tt> or <tt class=
"FILENAME">/usr/archive/stuff</tt>.</p>
<p>In FreeBSD's <tt class=
"FILENAME">/etc/exports</tt> file this is controlled
by the <tt class="OPTION">-alldirs</tt> option. Other
NFS servers may have different conventions. If you
are getting <tt class="LITERAL">Permission
Denied</tt> messages from the server then it's likely
that you don't have this properly enabled.</p>
</div>
<div class="SECT4">
<hr>
<h4 class="SECT4"><a name="AEN331">1.5.5.5 FTP
Installation tips</a></h4>
<p>FTP installation may be done from any mirror site
containing a reasonably up-to-date version of
FreeBSD. A full menu of reasonable choices for almost
any location in the world is provided in the FTP site
menu during installation.</p>
<p>If you are installing from some other FTP site not
listed in this menu, or you are having troubles
getting your name server configured properly, you can
also specify your own URL by selecting the ``URL''
choice in that menu. A URL can contain a hostname or
an IP address, so something like the following would
work in the absence of a name server:</p>
<pre class="SCREEN">
ftp://216.66.64.162/pub/FreeBSD/releases/i386/4.2-RELEASE
</pre>
<p>There are three FTP installation modes you can
use:</p>
<ul>
<li>
<p>FTP: This method uses the standard ``Active''
mode for transfers, in which the server initiates
a connection to the client. This will not work
through most firewalls but will often work best
with older FTP servers that do not support
passive mode. If your connection hangs with
passive mode, try this one.</p>
</li>
<li>
<p>FTP Passive: This sets the FTP "Passive" mode
which prevents the server from opening
connections to the client. This option is best
for users to pass through firewalls that do not
allow incoming connections on random port
addresses.</p>
</li>
<li>
<p>FTP via an HTTP proxy: This option instructs
FreeBSD to use HTTP to connect to a proxy for all
FTP operations. The proxy will translate the
requests and send them to the FTP server. This
allows the user to pass through firewalls that do
not allow FTP at all, but offer an HTTP proxy.
You must specify the hostname of the proxy in
addition to the FTP server.</p>
<p>In the rare case that you have an FTP proxy
that does not go through HTTP, you can specify
the URL as something like:</p>
<pre class="SCREEN">
<tt class="USERINPUT"><b>ftp://foo.bar.com:<tt class=
"REPLACEABLE"><i>port</i></tt>/pub/FreeBSD</b></tt>
</pre>
<p>In the URL above, <tt class=
"REPLACEABLE"><i>port</i></tt> is the port number
of the proxy FTP server.</p>
</li>
</ul>
<br>
<br>
</div>
</div>
<div class="SECT3">
<hr>
<h3 class="SECT3"><a name="AEN352">1.5.6 Tips for
Serial Console Users</a></h3>
<p>If you'd like to install FreeBSD on a machine using
just a serial port (e.g. you don't have or wish to use
a VGA card), please follow these steps:</p>
<div class="PROCEDURE">
<ol type="1">
<li>
<p>Connect some sort of ANSI (vt100) compatible
terminal or terminal emulation program to the <tt
class="DEVICENAME">COM1</tt> port of the PC you
are installing FreeBSD onto.</p>
</li>
<li>
<p>Unplug the keyboard (yes, that's correct!) and
then try to boot from floppy or the installation
CDROM, depending on the type of installation
media you have, with the keyboard unplugged.</p>
</li>
<li>
<p>If you don't get any output on your serial
console, plug the keyboard in again and wait for
some beeps. If you are booting from the CDROM,
proceed to <a href="#HITSPACE">step 5</a> as soon
as you hear the beep.</p>
</li>
<li>
<p>For a floppy boot, the first beep means to
remove the <tt class="FILENAME">kern.flp</tt>
floppy and insert the <tt class=
"FILENAME">mfsroot.flp</tt> floppy, after which
you should press <b class="KEYCAP">Enter</b> and
wait for another beep.</p>
</li>
<li>
<a name="HITSPACE"></a>
<p>Hit the space bar, then enter</p>
<pre class="SCREEN">
<tt class="USERINPUT"><b>boot -h</b></tt>
</pre>
<p>and you should now definitely be seeing
everything on the serial port. If that still
doesn't work, check your serial cabling as well
as the settings on your terminal emulation
program or actual terminal device. It should be
set for 9600 baud, 8 bits, no parity.</p>
</li>
</ol>
</div>
</div>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN374">1.6 Question and
Answer Section for IA-32 Architecture Users</a></h2>
<div class="QANDASET">
<dl>
<dt>1.6.1. <a href="#Q1.6.1.">Help! I have no space!
Do I need to delete everything first?</a></dt>
<dt>1.6.2. <a href="#Q1.6.2.">Can I use compressed
DOS filesystems from FreeBSD?</a></dt>
<dt>1.6.3. <a href="#Q1.6.3.">Can I mount my DOS
extended partitions?</a></dt>
<dt>1.6.4. <a href="#Q1.6.4.">Can I run DOS binaries
under FreeBSD?</a></dt>
</dl>
<div class="QANDAENTRY">
<div class="QUESTION">
<p><a name="Q1.6.1."></a><b>1.6.1.</b> Help! I have
no space! Do I need to delete everything first?</p>
</div>
<div class="ANSWER">
<p><b></b>If your machine is already running DOS
and has little or no free space available for
FreeBSD's installation, all is not lost! You may
find the <b class="APPLICATION">FIPS</b> utility,
provided in the <tt class="FILENAME">tools/</tt>
subdirectory on the FreeBSD CDROM or on the various
FreeBSD ftp sites, to be quite useful.</p>
<p><b class="APPLICATION">FIPS</b> allows you to
split an existing DOS partition into two pieces,
preserving the original partition and allowing you
to install onto the second free piece. You first
``defrag'' your DOS partition, using the DOS 6.xx
<tt class="FILENAME">DEFRAG</tt> utility or the <b
class="APPLICATION">Norton Disk Tools</b>, then run
FIPS. It will prompt you for the rest of the
information it needs. Afterwards, you can reboot
and install FreeBSD on the new partition. Also note
that FIPS will create the second partition as a
``clone'' of the first, so you'll actually see that
you now have two DOS Primary partitions where you
formerly had one. Don't be alarmed! You can simply
delete the extra DOS Primary partition (making sure
it's the right one by examining its size).</p>
<p><b class="APPLICATION">FIPS</b> does NOT
currently work with FAT32 or VFAT style partitions
as used by newer versions of Windows 95. To split
up such a partition, you will need a commercial
product such as <b class="APPLICATION">Partition
Magic</b>. Sorry, but this is just the breaks if
you've got a Windows partition hogging your whole
disk and you don't want to reinstall from
scratch.</p>
</div>
</div>
<div class="QANDAENTRY">
<div class="QUESTION">
<p><a name="Q1.6.2."></a><b>1.6.2.</b> Can I use
compressed DOS filesystems from FreeBSD?</p>
</div>
<div class="ANSWER">
<p><b></b>No. If you are using a utility such as <b
class="APPLICATION">Stacker</b>(tm) or <b class=
"APPLICATION">DoubleSpace</b>(tm), FreeBSD will
only be able to use whatever portion of the
filesystem you leave uncompressed. The rest of the
filesystem will show up as one large file (the
stacked/dblspaced file!). <span class="emphasis"><i
class="EMPHASIS">Do not remove that file</i></span>
as you will probably regret it greatly!</p>
<p>It is probably better to create another
uncompressed DOS extended partition and use this
for communications between DOS and FreeBSD if such
is your desire.</p>
</div>
</div>
<div class="QANDAENTRY">
<div class="QUESTION">
<p><a name="Q1.6.3."></a><b>1.6.3.</b> Can I mount
my DOS extended partitions?</p>
</div>
<div class="ANSWER">
<p><b></b>Yes. DOS extended partitions are mapped
in at the end of the other ``slices'' in FreeBSD,
e.g. your <tt class="DEVICENAME">D:</tt> drive
might be <tt class="FILENAME">/dev/da0s5</tt>, your
<tt class="DEVICENAME">E:</tt> drive <tt class=
"FILENAME">/dev/da0s6</tt>, and so on. This example
assumes, of course, that your extended partition is
on SCSI drive 0. For IDE drives, substitute <tt
class="LITERAL">ad</tt> for <tt class=
"LITERAL">da</tt> appropriately. You otherwise
mount extended partitions exactly like you would
mount any other DOS drive, e.g.:</p>
<pre class="SCREEN">
<tt class="PROMPT">#</tt> <tt class=
"USERINPUT"><b>mount -t msdos /dev/da0s5 /dos_d</b></tt>
</pre>
</div>
</div>
<div class="QANDAENTRY">
<div class="QUESTION">
<p><a name="Q1.6.4."></a><b>1.6.4.</b> Can I run
DOS binaries under FreeBSD?</p>
</div>
<div class="ANSWER">
<p><b></b>Ongoing work with BSDI's <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=doscmd&sektion=1&manpath=FreeBSD+4.7-RELEASE">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">doscmd</span>(1)</span></a> utility
will suffice in many cases, though it still has
some rough edges. If you're interested in working
on this, please send mail to the FreeBSD-emulation
mailing list <tt class="EMAIL"><<a href=
"mailto:freebsd-emulation@FreeBSD.org">freebsd-emulation@FreeBSD.org</a>></tt>
and indicate that you're interested in joining this
ongoing effort!</p>
<p>The <a href=
"http://www.FreeBSD.org/cgi/url.cgi?ports/emulators/pcemu/pkg-descr">
<tt class="FILENAME">emulators/pcemu</tt></a>
port/package in the FreeBSD Ports Collection which
emulates an 8088 and enough BIOS services to run
DOS text mode applications. It requires the X
Window System (XFree86) to operate.</p>
</div>
</div>
</div>
</div>
</div>
<div class="SECT1">
<hr>
<h1 class="SECT1"><a name="LAYOUT">2 Distribution
Format</a></h1>
<p>A typical FreeBSD distribution directory looks something
like this:</p>
<pre class="SCREEN">
ERRATA.HTM README.TXT compat1x dict manpages
ERRATA.TXT RELNOTES.HTM compat20 doc packages
HARDWARE.HTM RELNOTES.TXT compat21 docbook.css ports
HARDWARE.TXT XF86336 compat22 floppies proflibs
INSTALL.HTM bin compat3x games src
INSTALL.TXT catpages compat4x info tools
README.HTM cdrom.inf crypto kernel
</pre>
<p>If you want to do a CDROM, FTP or NFS installation from
this distribution directory, all you need to do is make the
1.44MB boot floppies from the floppies directory (see <a
href="#FLOPPIES">Section 1.3</a> for instructions on how to
do this), boot them and follow the instructions. The rest
of the data needed during the installation will be obtained
automatically based on your selections. If you've never
installed FreeBSD before, you also want to read the
entirety of this document (the installation instructions)
file.</p>
<p>If you're trying to do some other type of installation
or are merely curious about how a distribution is
organized, what follows is a more thorough description of
each item in more detail:</p>
<ol type="1">
<li>
<p>The <tt class="FILENAME">*.TXT</tt> and <tt class=
"FILENAME">*.HTM</tt> files contain documentation (for
example, this document is contained in both <tt class=
"FILENAME">INSTALL.TXT</tt> and <tt class=
"FILENAME">INSTALL.HTM</tt>) and should be read before
starting an installation. The <tt class=
"FILENAME">*.TXT</tt> files are plain text, while the
<tt class="FILENAME">*.HTM</tt> files are HTML files
that can be read by almost any Web browser. Some
distributions may contain documentation in other
formats as well, such as PDF or PostScript.</p>
</li>
<li>
<p><tt class="FILENAME">docbook.css</tt> is a Cascading
Style Sheet (CSS) file used by some Web browsers for
formatting the HTML documentation.</p>
</li>
<li>
<p>The <tt class="FILENAME">XF86336</tt> directory
contains the XFree86 project's 3.3.6 release and
consists of a series of gzip'd tar files which contain
each component of the XFree86 distribution.</p>
</li>
<li>
<p>The <tt class="FILENAME">bin</tt>, <tt class=
"FILENAME">catpages</tt>, <tt class=
"FILENAME">crypto</tt>, <tt class="FILENAME">dict</tt>,
<tt class="FILENAME">doc</tt>, <tt class=
"FILENAME">games</tt>, <tt class="FILENAME">info</tt>,
<tt class="FILENAME">manpages</tt>, <tt class=
"FILENAME">proflibs</tt>, and <tt class=
"FILENAME">src</tt> directories contain the primary
distribution components of FreeBSD itself and are split
into smaller files for easy packing onto floppies
(should that be necessary).</p>
</li>
<li>
<p>The <tt class="FILENAME">compat1x</tt>, <tt class=
"FILENAME">compat20</tt>, <tt class=
"FILENAME">compat21</tt>, <tt class=
"FILENAME">compat22</tt>, <tt class=
"FILENAME">compat3x</tt>, and <tt class=
"FILENAME">compat4x</tt> directories contain
distributions for compatibility with older releases and
are distributed as single gzip'd tar files - they can
be installed during release time or later by running
their <tt class="FILENAME">install.sh</tt> scripts.</p>
</li>
<li>
<p>The <tt class="FILENAME">floppies/</tt> subdirectory
contains the floppy installation images; further
information on using them can be found in <a href=
"#FLOPPIES">Section 1.3</a>.</p>
</li>
<li>
<p>The <tt class="FILENAME">packages</tt> and <tt
class="FILENAME">ports</tt> directories contain the
FreeBSD Packages and Ports Collections. Packages may be
installed from the packages directory by running the
command:</p>
<pre class="SCREEN">
<tt class="PROMPT">#</tt><tt class=
"USERINPUT"><b>/stand/sysinstall configPackages</b></tt>
</pre>
<p>Packages can also be installed by feeding individual
filenames in <tt class="FILENAME">packages</tt>/ to the
<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=pkg_add&sektion=1&manpath=FreeBSD+4.7-RELEASE">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">pkg_add</span>(1)</span></a>
command.</p>
<p>The Ports Collection may be installed like any other
distribution and requires about 100MB unpacked. More
information on the ports collection may be obtained
from <a href="http://www.FreeBSD.org/ports/" target=
"_top">http://www.FreeBSD.org/ports/</a> or locally
from <tt class="FILENAME">/usr/share/doc/handbook</tt>
if you've installed the <tt class="FILENAME">doc</tt>
distribution.</p>
</li>
<li>
<p>Last of all, the <tt class="FILENAME">tools</tt>
directory contains various DOS tools for discovering
disk geometries, installing boot managers and the like.
It is purely optional and provided only for user
convenience.</p>
</li>
</ol>
<br>
<br>
<p>A typical distribution directory (for example, the <tt
class="FILENAME">info</tt> distribution) looks like this
internally:</p>
<pre class="SCREEN">
CHECKSUM.MD5 info.ab info.ad info.inf install.sh
info.aa info.ac info.ae info.mtree
</pre>
<p>The <tt class="FILENAME">CHECKSUM.MD5</tt> file contains
MD5 signatures for each file, should data corruption be
suspected, and is purely for reference. It is not used by
the actual installation and does not need to be copied with
the rest of the distribution files. The <tt class=
"FILENAME">info.a*</tt> files are split, gzip'd tar files,
the contents of which can be viewed by doing:</p>
<pre class="SCREEN">
<tt class="PROMPT">#</tt> <tt class=
"USERINPUT"><b>cat info.a* | tar tvzf -</b></tt>
</pre>
<p>During installation, they are automatically concatenated
and extracted by the installation procedure.</p>
<p>The <tt class="FILENAME">info.inf</tt> file is also
necessary since it is read by the installation program in
order to figure out how many pieces to look for when
fetching and concatenating the distribution. When putting
distributions onto floppies, the <tt class=
"FILENAME">.inf</tt> file <span class="emphasis"><i class=
"EMPHASIS">must</i></span> occupy the first floppy of each
distribution set!</p>
<p>The <tt class="FILENAME">info.mtree</tt> file is another
non-essential file which is provided for user reference. It
contains the MD5 signatures of the <span class=
"emphasis"><i class="EMPHASIS">unpacked</i></span>
distribution files and can be later used with the <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=mtree&sektion=8&manpath=FreeBSD+4.7-RELEASE">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">mtree</span>(8)</span></a> program to
verify the installation permissions and checksums against
any possible modifications to the file. When used with the
<tt class="FILENAME">bin</tt> distribution, this can be an
excellent way of detecting trojan horse attacks on your
system.</p>
<p>Finally, the <tt class="FILENAME">install.sh</tt> file
is for use by those who want to install the distribution
after installation time. To install the info distribution
from CDROM after a system was installed, for example, you'd
do:</p>
<pre class="SCREEN">
<tt class="PROMPT">#</tt> <tt class=
"USERINPUT"><b>cd /cdrom/info</b></tt>
<tt class="PROMPT">#</tt> <tt class=
"USERINPUT"><b>sh install.sh</b></tt>
</pre>
</div>
<div class="SECT1">
<hr>
<h1 class="SECT1"><a name="UPGRADING">3 Upgrading
FreeBSD</a></h1>
<p>These instructions describe a procedure for doing a
binary upgrade from an older version of FreeBSD.</p>
<div class="WARNING">
<blockquote class="WARNING">
<p><b>Warning:</b> While the FreeBSD upgrade procedure
does its best to safeguard against accidental loss of
data, it is still more than possible to <span class=
"emphasis"><i class="EMPHASIS">wipe out your entire
disk</i></span> with this installation! Please do not
accept the final confirmation request unless you have
adequately backed up any important data files.</p>
</blockquote>
</div>
<div class="IMPORTANT">
<blockquote class="IMPORTANT">
<p><b>Important:</b> These notes assume that you are
using the version of <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+4.7-RELEASE">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">sysinstall</span>(8)</span></a>
supplied with the version of FreeBSD to which you
intend to upgrade. Using a mismatched version of <a
href=
"http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+4.7-RELEASE">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">sysinstall</span>(8)</span></a> is
almost guaranteed to cause problems and has been known
to leave systems in an unusable state. The most
commonly made mistake in this regard is the use of an
old copy of <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+4.7-RELEASE">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">sysinstall</span>(8)</span></a> from an
existing installation to upgrade to a newer version of
FreeBSD. This is <span class="emphasis"><i class=
"EMPHASIS">not</i></span> recommended.</p>
</blockquote>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN573">3.1
Introduction</a></h2>
<p>The upgrade procedure replaces distributions selected
by the user with those corresponding to the new FreeBSD
release. It preserves standard system configuration data,
as well as user data, installed packages and other
software.</p>
<p>Administrators contemplating an upgrade are encouraged
to study this section in its entirety before commencing
an upgrade. Failure to do so may result in a failed
upgrade or loss of data.</p>
<div class="SECT3">
<hr>
<h3 class="SECT3"><a name="AEN577">3.1.1 Upgrade
Overview</a></h3>
<p>Upgrading of a distribution is performed by
extracting the new version of the component over the
top of the previous version. Files belonging to the old
distribution are not deleted.</p>
<p>System configuration is preserved by retaining and
restoring the previous version of the following
files:</p>
<p><tt class="FILENAME">Xaccel.ini</tt>, <tt class=
"FILENAME">XF86Config</tt>, <tt class=
"FILENAME">adduser.conf</tt>, <tt class=
"FILENAME">aliases</tt>, <tt class=
"FILENAME">aliases.db</tt>, <tt class=
"FILENAME">amd.map</tt>, <tt class=
"FILENAME">crontab</tt>, <tt class=
"FILENAME">csh.cshrc</tt>, <tt class=
"FILENAME">csh.login</tt>, <tt class=
"FILENAME">csh.logout</tt>, <tt class=
"FILENAME">cvsupfile</tt>, <tt class=
"FILENAME">dhclient.conf</tt>, <tt class=
"FILENAME">disktab</tt>, <tt class=
"FILENAME">dm.conf</tt>, <tt class=
"FILENAME">dumpdates</tt>, <tt class=
"FILENAME">exports</tt>, <tt class=
"FILENAME">fbtab</tt>, <tt class="FILENAME">fstab</tt>,
<tt class="FILENAME">ftpusers</tt>, <tt class=
"FILENAME">gettytab</tt>, <tt class=
"FILENAME">gnats</tt>, <tt class="FILENAME">group</tt>,
<tt class="FILENAME">hosts</tt>, <tt class=
"FILENAME">host.conf</tt>, <tt class=
"FILENAME">hosts.allow</tt>, <tt class=
"FILENAME">hosts.equiv</tt>, <tt class=
"FILENAME">hosts.lpd</tt>, <tt class=
"FILENAME">inetd.conf</tt>, <tt class=
"FILENAME">kerberosIV</tt>, <tt class=
"FILENAME">localtime</tt>, <tt class=
"FILENAME">login.access</tt>, <tt class=
"FILENAME">login.conf</tt>, <tt class=
"FILENAME">mail</tt>, <tt class=
"FILENAME">mail.rc</tt>, <tt class=
"FILENAME">make.conf</tt>, <tt class=
"FILENAME">manpath.config</tt>, <tt class=
"FILENAME">master.passwd</tt>, <tt class=
"FILENAME">modems</tt>, <tt class="FILENAME">motd</tt>,
<tt class="FILENAME">namedb</tt>, <tt class=
"FILENAME">networks</tt>, <tt class=
"FILENAME">newsyslog.conf</tt>, <tt class=
"FILENAME">nsmb.conf</tt>, <tt class=
"FILENAME">pam.conf</tt>, <tt class=
"FILENAME">passwd</tt>, <tt class=
"FILENAME">periodic</tt>, <tt class=
"FILENAME">ppp</tt>, <tt class=
"FILENAME">printcap</tt>, <tt class=
"FILENAME">profile</tt>, <tt class=
"FILENAME">pwd.db</tt>, <tt class=
"FILENAME">rc.conf</tt>, <tt class=
"FILENAME">rc.conf.local</tt>, <tt class=
"FILENAME">rc.firewall</tt>, <tt class=
"FILENAME">rc.local</tt>, <tt class=
"FILENAME">remote</tt>, <tt class=
"FILENAME">resolv.conf</tt>, <tt class=
"FILENAME">rmt</tt>, <tt class=
"FILENAME">sendmail.cf</tt>, <tt class=
"FILENAME">sendmail.cw</tt>, <tt class=
"FILENAME">services</tt>, <tt class=
"FILENAME">shells</tt>, <tt class=
"FILENAME">skeykeys</tt>, <tt class=
"FILENAME">spwd.db</tt>, <tt class="FILENAME">ssh</tt>,
<tt class="FILENAME">syslog.conf</tt>, <tt class=
"FILENAME">ttys</tt>, <tt class=
"FILENAME">uucp</tt></p>
<p>The versions of these files which correspond to the
new version are moved to <tt class=
"FILENAME">/etc/upgrade/</tt>. The system administrator
may peruse these new versions and merge components as
desired. Note that many of these files are
interdependent, and the best merge procedure is to copy
all site-specific data from the current files into the
new.</p>
<p>During the upgrade procedure, the administrator is
prompted for a location into which all files from <tt
class="FILENAME">/etc/</tt> are saved. In the event
that local modifications have been made to other files,
they may be subsequently retrieved from this
location.</p>
</div>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN653">3.2 Procedure</a></h2>
<p>This section details the upgrade procedure. Particular
attention is given to items which substantially differ
from a normal installation.</p>
<div class="SECT3">
<hr>
<h3 class="SECT3"><a name="AEN656">3.2.1
Backup</a></h3>
<p>User data and system configuration should be backed
up before upgrading. While the upgrade procedure does
its best to prevent accidental mistakes, it is possible
to partially or completely destroy data and
configuration information.</p>
</div>
<div class="SECT3">
<hr>
<h3 class="SECT3"><a name="AEN659">3.2.2 Mount
Filesystems</a></h3>
<p>The disklabel editor is entered with the nominated
disk's filesystem devices listed. Prior to commencing
the upgrade, the administrator should make a note of
the device names and corresponding mountpoints. These
mountpoints should be entered here. <span class=
"emphasis"><i class="EMPHASIS">Do not</i></span>set the
``newfs flag'' for any filesystems, as this will cause
data loss.</p>
</div>
<div class="SECT3">
<hr>
<h3 class="SECT3"><a name="AEN664">3.2.3 Select
Distributions</a></h3>
<p>When selecting distributions, there are no
constraints on which must be selected. As a general
rule, the <tt class="LITERAL">bin</tt> distribution
should be selected for an update, and the <tt class=
"LITERAL">man</tt> distribution if manpages are already
installed. Other distributions may be selected beyond
those originally installed if the administrator wishes
to add additional functionality.</p>
</div>
<div class="SECT3">
<hr>
<h3 class="SECT3"><a name="FSTAB">3.2.4 After
Installation</a></h3>
<p>Once the installation procedure has completed, the
administrator is prompted to examine the new
configuration files. At this point, checks should be
made to ensure that the system configuration is valid.
In particular, the <tt class=
"FILENAME">/etc/rc.conf</tt> and <tt class=
"FILENAME">/etc/fstab</tt> files should be checked.</p>
</div>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN674">3.3 Upgrading from
Source Code</a></h2>
<p>Those interested in an upgrade method that allows more
flexibility and sophistication should take a look at <a
href=
"http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/cutting-edge.html"
target="_top">The Cutting Edge</a> in the FreeBSD
Handbook. This procedure involves rebuilding all of
FreeBSD from source code. It requires reliable network
connectivity, extra disk space, and time, but has
advantages for networks and other more complex
installations. This is roughly the same procedure as is
used for track the -STABLE or -CURRENT development
branches.</p>
<p><tt class="FILENAME">/usr/src/UPDATING</tt> contains
important information on updating a FreeBSD system from
source code. It lists various issues resulting from
changes in FreeBSD that may affect an upgrade.</p>
<p></p>
</div>
</div>
<div class="SECT1">
<hr>
<h1 class="SECT1"><a name="TROUBLE">4
Troubleshooting</a></h1>
<div class="SECT2">
<h2 class="SECT2"><a name="REPAIRING">4.1 Repairing an
Existing FreeBSD Installation</a></h2>
<p>FreeBSD features a ``Fixit'' option in the top menu of
the boot floppy. To use it, you will also need either a
<tt class="FILENAME">fixit.flp</tt> image floppy,
generated in the same fashion as the boot floppy, or the
``live filesystem'' CDROM; typically the second CDROM in
a multi-disc FreeBSD distribution.</p>
<p>To invoke fixit, simply boot the <tt class=
"FILENAME">kern.flp</tt> floppy, choose the ``Fixit''
item and insert the fixit floppy or CDROM when asked. You
will then be placed into a shell with a wide variety of
commands available (in the <tt class=
"FILENAME">/stand</tt> and <tt class=
"FILENAME">/mnt2/stand</tt> directories) for checking,
repairing and examining file systems and their contents.
Some UNIX administration experience <span class=
"emphasis"><i class="EMPHASIS">is</i></span> required to
use the fixit option.</p>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN695">4.2 Common
Installation Problems, Q&A</a></h2>
<div class="QANDASET">
<dl>
<dt>4.2.1. <a href="#Q4.2.1.">I go to boot from the
hard disk for the first time after installing
FreeBSD, the kernel loads and probes my hardware, but
stops with messages like:</a></dt>
<dt>4.2.2. <a href="#Q4.2.2.">I go to boot from the
hard disk for the first time after installing
FreeBSD, but the Boot Manager prompt just prints <tt
class="LITERAL">F?</tt> at the boot menu each time
but the boot won't go any further.</a></dt>
</dl>
<div class="QANDAENTRY">
<div class="QUESTION">
<p><a name="Q4.2.1."></a><b>4.2.1.</b> I go to boot
from the hard disk for the first time after
installing FreeBSD, the kernel loads and probes my
hardware, but stops with messages like:</p>
<pre class="SCREEN">
changing root device to wd1s1a panic: cannot mount root
</pre>
<p>What is wrong? What can I do?</p>
<p>What is this <tt class=
"LITERAL">bios_drive:interface(unit,partition)kernel_name</tt>
thing that is displayed with the boot help?</p>
</div>
<div class="ANSWER">
<p><b></b>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 FreeBSD, and working out which numbers
correspond to which is difficult to get right.</p>
<p>In the case where the boot disk is not the first
disk in the system, FreeBSD can need some help
finding it. There are two common situations here,
and in both of these cases, you need to tell
FreeBSD where the root filesystem is. You do this
by specifying the BIOS disk number, the disk type
and the FreeBSD disk number for that type.</p>
<p>The first situation is where you have two IDE
disks, each configured as the master on their
respective IDE busses, and wish to boot FreeBSD
from the second disk. The BIOS sees these as disk 0
and disk 1, while FreeBSD sees them as <tt class=
"DEVICENAME">wd0</tt> and <tt class=
"DEVICENAME">wd2</tt>.</p>
<p>FreeBSD is on BIOS disk 1, of type <tt class=
"LITERAL">wd</tt> and the FreeBSD disk number is 2,
so you would say:</p>
<pre class="SCREEN">
<tt class="USERINPUT"><b>1:wd(2,a)kernel</b></tt>
</pre>
<p>Note that if you have a slave on the primary
bus, the above is not necessary (and is effectively
wrong).</p>
<p>The second situation involves booting from a
SCSI disk when you have one or more IDE disks in
the system. In this case, the FreeBSD 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 <tt class="LITERAL">da</tt>
and FreeBSD disk number 0, so you would say:</p>
<pre class="SCREEN">
<tt class="USERINPUT"><b>2:da(0,a)kernel</b></tt>
</pre>
<p>To tell FreeBSD 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.</p>
<p>Once you have determined the correct values to
use, you can put the command exactly as you would
have typed it in the <tt class=
"FILENAME">/boot.config</tt> file using a standard
text editor. Unless instructed otherwise, FreeBSD
will use the contents of this file as the default
response to the <tt class="LITERAL">boot:</tt>
prompt.</p>
</div>
</div>
<div class="QANDAENTRY">
<div class="QUESTION">
<p><a name="Q4.2.2."></a><b>4.2.2.</b> I go to boot
from the hard disk for the first time after
installing FreeBSD, but the Boot Manager prompt
just prints <tt class="LITERAL">F?</tt> at the boot
menu each time but the boot won't go any
further.</p>
</div>
<div class="ANSWER">
<p><b></b>The hard disk geometry was set
incorrectly in the Partition editor when you
installed FreeBSD. Go back into the partition
editor and specify the actual geometry of your hard
disk. You must reinstall FreeBSD again from the
beginning with the correct geometry.</p>
<p>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 FreeBSD after that. The
install program will see the DOS partition and try
to infer the correct geometry from it, which
usually works.</p>
<p>The following tip is no longer recommended, but
is left here for reference:</p>
<a name="AEN732"></a>
<blockquote class="BLOCKQUOTE">
<p>If you are setting up a truly dedicated
FreeBSD 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 FreeBSD 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 FreeBSD on a disk.</p>
</blockquote>
</div>
</div>
</div>
</div>
<div class="SECT2">
<hr>
<h2 class="SECT2"><a name="AEN734">4.3 Known Hardware
Problems, Q&A</a></h2>
<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> Please send hardware tips for this
section to Jordan K. Hubbard <tt class=
"EMAIL"><<a href=
"mailto:jkh@FreeBSD.org">jkh@FreeBSD.org</a>></tt>.</p>
</blockquote>
</div>
<div class="QANDASET">
<dl>
<dt>4.3.1. <a href="#Q4.3.1.">The <span class=
"CITEREFENTRY"><span class=
"REFENTRYTITLE">mcd</span>(4)</span> driver keeps
thinking that it has found a device and this stops my
Intel EtherExpress card from working.</a></dt>
<dt>4.3.2. <a href="#Q4.3.2.">FreeBSD claims to
support the 3Com PCMCIA card, but my card isn't
recognized when it's plugged into my laptop.</a></dt>
<dt>4.3.3. <a href="#Q4.3.3.">FreeBSD finds my PCMCIA
network card, but no packets appear to be sent even
though it claims to be working.</a></dt>
<dt>4.3.4. <a href="#Q4.3.4.">The system finds my
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">ed</span>(4)</span> network card, but
I keep getting device timeout errors.</a></dt>
<dt>4.3.5. <a href="#Q4.3.5.">I have a
Matsushita/Panasonic drive but it isn't recognized by
the system.</a></dt>
<dt>4.3.6. <a href="#Q4.3.6.">I booted the install
floppy on my IBM ThinkPad (tm) laptop, and the
keyboard is all messed up.</a></dt>
<dt>4.3.7. <a href="#Q4.3.7.">When I try to boot the
install floppy, I see the following message and
nothing seems to be happening. I cannot enter
anything from the keyboard either.</a></dt>
<dt>4.3.8. <a href="#Q4.3.8.">I have a
Matsushita/Panasonic CR-522, a Matsushita/Panasonic
CR-523 or a TEAC CD55a drive, but it is not
recognized even when the correct I/O port is
set.</a></dt>
<dt>4.3.9. <a href="#Q4.3.9.">I'm trying to install
from a tape drive but all I get is something like
this on the screen:</a></dt>
<dt>4.3.10. <a href="#Q4.3.10.">I've installed
FreeBSD onto my system, but it hangs when booting
from the hard drive with the message:</a></dt>
<dt>4.3.11. <a href="#Q4.3.11.">My system can not
find my Intel EtherExpress 16 card.</a></dt>
<dt>4.3.12. <a href="#Q4.3.12.">When installing on an
EISA HP Netserver, my on-board AIC-7xxx SCSI
controller isn't detected.</a></dt>
<dt>4.3.13. <a href="#Q4.3.13.">I have a Panasonic
AL-N1 or Rios Chandler Pentium machine and I find
that the system hangs before ever getting into the
installation now.</a></dt>
<dt>4.3.14. <a href="#Q4.3.14.">I have this CMD640
IDE controller that is said to be broken.</a></dt>
<dt>4.3.15. <a href="#Q4.3.15.">On a Compaq Aero
notebook, I get the message ``No floppy devices
found! Please check ...'' when trying to install from
floppy.</a></dt>
<dt>4.3.16. <a href="#Q4.3.16.">When I go to boot my
Intel AL440LX (``Atlanta'') -based system from the
hard disk the first time, it stops with a <tt class=
"LITERAL">Read Error</tt> message.</a></dt>
<dt>4.3.17. <a href="#Q4.3.17.">When installing on an
Dell Poweredge XE, Dell proprietary RAID controller
DSA (Dell SCSI Array) isn't recognized.</a></dt>
<dt>4.3.18. <a href="#Q4.3.18.">My Ethernet adapter
is detected as an AMD PCnet-FAST (or similar) but it
doesn't work. (Eg. onboard Ethernet on IBM Netfinity
5xxx or 7xxx)</a></dt>
<dt>4.3.19. <a href="#Q4.3.19.">I have an IBM
EtherJet PCI card, it is detected by the <span class=
"CITEREFENTRY"><span class=
"REFENTRYTITLE">fxp</span>(4)</span> driver
correctly, but the lights on the card don't come on
and it doesn't connect to the network.</a></dt>
<dt>4.3.20. <a href="#Q4.3.20.">When I configure the
network during installation on an IBM Netfinity 3500,
the system freezes.</a></dt>
<dt>4.3.21. <a href="#Q4.3.21.">When I install onto a
drive managed by a Mylex PCI RAID controller, the
system fails to boot (eg. with a <tt class=
"LITERAL">read error</tt> message).</a></dt>
</dl>
<div class="QANDAENTRY">
<div class="QUESTION">
<p><a name="Q4.3.1."></a><b>4.3.1.</b> The <span
class="CITEREFENTRY"><span class=
"REFENTRYTITLE">mcd</span>(4)</span> driver keeps
thinking that it has found a device and this stops
my Intel EtherExpress card from working.</p>
</div>
<div class="ANSWER">
<p><b></b>Use the UserConfig utility (see <tt
class="FILENAME">HARDWARE.TXT</tt>) and disable the
probing of the <tt class="DEVICENAME">mcd0</tt> and
<tt class="DEVICENAME">mcd1</tt> devices. Generally
speaking, you should only leave the devices that
you will be using enabled in your kernel.</p>
</div>
</div>
<div class="QANDAENTRY">
<div class="QUESTION">
<p><a name="Q4.3.2."></a><b>4.3.2.</b> FreeBSD
claims to support the 3Com PCMCIA card, but my card
isn't recognized when it's plugged into my
laptop.</p>
</div>
<div class="ANSWER">
<p><b></b>There are a couple of possible problems.
First of all, FreeBSD does not support
multi-function cards, so if you have a combo
Ethernet/modem card (such as the 3C562), it won't
work. The default driver for the 3C589 card was
written just like all of the other drivers in
FreeBSD, and depend on the card's own configuration
data stored in NVRAM to work. You must correctly
configure FreeBSD's driver to match the IRQ, port,
and IOMEM stored in NVRAM.</p>
<p>Unfortunately, the only program capable of
reading them is the 3COM supplied DOS program. This
program must be run on a absolutely clean system
(no other drivers must be running), and the program
will whine about CARD-Services not being found, but
it will continue. This is necessary to read the
NVRAM values. You want to know the IRQ, port, and
IOMEM values (the latter is called the CIS tuple by
3COM). The first two can be set in the program, the
third is un-settable, and can only be read. Once
you have these values, set them in UserConfig and
your card will be recognized.</p>
</div>
</div>
<div class="QANDAENTRY">
<div class="QUESTION">
<p><a name="Q4.3.3."></a><b>4.3.3.</b> FreeBSD
finds my PCMCIA network card, but no packets appear
to be sent even though it claims to be working.</p>
</div>
<div class="ANSWER">
<p><b></b>Many PCMCIA cards have the ability to use
either the 10-Base2 (BNC) or 10-BaseT connectors
for connecting to the network. The driver is unable
to ``auto-select'' the correct connector, so you
must tell it which connector to use. In order to
switch between the two connectors, the link flags
must be set. Depending on the model of the card,
<tt class="OPTION">-link0 link1</tt> or <tt class=
"OPTION">-link0 -link1</tt> will choose the correct
network connector. You can set these in <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+4.7-RELEASE">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">sysinstall</span>(8)</span></a> by
using the <tt class="LITERAL">Extra options to
ifconfig:</tt> field in the network setup
screen.</p>
</div>
</div>
<div class="QANDAENTRY">
<div class="QUESTION">
<p><a name="Q4.3.4."></a><b>4.3.4.</b> The system
finds my <span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">ed</span>(4)</span> network card,
but I keep getting device timeout errors.</p>
</div>
<div class="ANSWER">
<p><b></b>Your card is probably on a different IRQ
from what is specified in the kernel configuration.
The ed driver does not use the `soft' configuration
by default (values entered using EZSETUP in DOS),
but it will use the software configuration if you
specify <tt class="LITERAL">?</tt> in the IRQ field
of your kernel config file.</p>
<p>Either move the jumper on the card to a hard
configuration setting (altering the kernel settings
if necessary), or specify the IRQ as <tt class=
"LITERAL">-1</tt> in UserConfig or <tt class=
"LITERAL">?</tt> in your kernel config file. This
will tell the kernel to use the soft
configuration.</p>
<p>Another possibility is that your card is at IRQ
9, which is shared by IRQ 2 and frequently a cause
of problems (especially when you have a VGA card
using IRQ 2!). You should not use IRQ 2 or 9 if at
all possible.</p>
</div>
</div>
<div class="QANDAENTRY">
<div class="QUESTION">
<p><a name="Q4.3.5."></a><b>4.3.5.</b> I have a
Matsushita/Panasonic drive but it isn't recognized
by the system.</p>
</div>
<div class="ANSWER">
<p><b></b>Make certain that the I/O port that the
<a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=matcd&sektion=4&manpath=FreeBSD+4.7-RELEASE">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">matcd</span>(4)</span></a> driver
is set to is correct for the host interface card
you have. (Some SoundBlaster DOS drivers report a
hardware I/O port address for the CD-ROM interface
that is 0x10 lower than it really is.)</p>
<p>If you are unable to determine the settings for
the card by examining the board or documentation,
you can use UserConfig to change the 'port' address
(I/O port) to -1 and start the system. This setting
causes the driver to look at a number of I/O ports
that various manufacturers use for their
Matsushita/Panasonic/Creative CD-ROM interfaces.
Once the driver locates the address, you should run
UserConfig again and specify the correct address.
Leaving the 'port' parameter set to -1 increases
the amount of time that it takes the system to
boot, and this could interfere with other
devices.</p>
<p>The double-speed Matsushita CR-562 and CR-563
are the only drives that are supported.</p>
</div>
</div>
<div class="QANDAENTRY">
<div class="QUESTION">
<p><a name="Q4.3.6."></a><b>4.3.6.</b> I booted the
install floppy on my IBM ThinkPad (tm) laptop, and
the keyboard is all messed up.</p>
</div>
<div class="ANSWER">
<p><b></b>Older IBM laptops use a non-standard
keyboard controller, so you must tell the keyboard
driver (atkbd0) to go into a special mode which
works on the ThinkPads. Change the atkbd0 'Flags'
to 0x4 in UserConfig and it should work fine. (Look
in the Input Menu for 'Keyboard'.)</p>
</div>
</div>
<div class="QANDAENTRY">
<div class="QUESTION">
<p><a name="Q4.3.7."></a><b>4.3.7.</b> When I try
to boot the install floppy, I see the following
message and nothing seems to be happening. I cannot
enter anything from the keyboard either.</p>
<pre class="SCREEN">
Keyboard: no
</pre>
</div>
<div class="ANSWER">
<p><b></b>Due to lack of space, full support for
old XT/AT (84-key) keyboards is no longer available
in the bootblocks. Some notebook computers may also
have this type of keyboard. If you are still using
this kind of hardware, you will see the above
message appears when you boot from the CD-ROM or an
install floppy.</p>
<p>As soon as you see this message, hit the space
bar, and you will see the prompt:</p>
<pre class="SCREEN">
>> FreeBSD/i386 BOOT
Default: x:xx(x,x)/boot/loader
boot:
</pre>
<p>Then enter <tt class=
"USERINPUT"><b>-Dh</b></tt>, and things should
proceed normally.</p>
</div>
</div>
<div class="QANDAENTRY">
<div class="QUESTION">
<p><a name="Q4.3.8."></a><b>4.3.8.</b> I have a
Matsushita/Panasonic CR-522, a Matsushita/Panasonic
CR-523 or a TEAC CD55a drive, but it is not
recognized even when the correct I/O port is
set.</p>
</div>
<div class="ANSWER">
<p><b></b>These CD-ROM drives are currently not
supported by FreeBSD. The command sets for these
drives are not compatible with the double-speed
CR-562 and CR-563 drives.</p>
<p>The single-speed CR-522 and CR-523 drives can be
identified by their use of a CD-caddy.</p>
</div>
</div>
<div class="QANDAENTRY">
<div class="QUESTION">
<p><a name="Q4.3.9."></a><b>4.3.9.</b> I'm trying
to install from a tape drive but all I get is
something like this on the screen:</p>
<pre class="SCREEN">
sa0(aha0:1:0) NOT READY csi 40,0,0,0
</pre>
</div>
<div class="ANSWER">
<p><b></b>There's a limitation in the current <a
href=
"http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+4.7-RELEASE">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">sysinstall</span>(8)</span></a>
that the tape <span class="emphasis"><i class=
"EMPHASIS">must</i></span> be in the drive while <a
href=
"http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+4.7-RELEASE">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">sysinstall</span>(8)</span></a> is
started or it won't be detected. Try again with the
tape in the drive the whole time.</p>
</div>
</div>
<div class="QANDAENTRY">
<div class="QUESTION">
<p><a name="Q4.3.10."></a><b>4.3.10.</b> I've
installed FreeBSD onto my system, but it hangs when
booting from the hard drive with the message:</p>
<pre class="SCREEN">
Changing root to /dev/da0a
</pre>
</div>
<div class="ANSWER">
<p><b></b>his problem may occur in a system with a
3com 3c509 Ethernet adapter. The <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=ep&sektion=4&manpath=FreeBSD+4.7-RELEASE">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">ep</span>(4)</span></a> device
driver appears to be sensitive to probes for other
devices that also use address 0x300. Boot your
FreeBSD system by power cycling the machine (turn
off and on). At the <tt class="LITERAL">Boot:</tt>
prompt specify the <tt class="OPTION">-c</tt>. This
will invoke UserConfig (see <a href=
"#REPAIRING">Section 4.1</a> above). Use the <tt
class="LITERAL">disable</tt> command to disable the
device probes for all devices at address 0x300
except the ep0 driver. On exit, your machine should
successfully boot FreeBSD.</p>
</div>
</div>
<div class="QANDAENTRY">
<div class="QUESTION">
<p><a name="Q4.3.11."></a><b>4.3.11.</b> My system
can not find my Intel EtherExpress 16 card.</p>
</div>
<div class="ANSWER">
<p><b></b>You must set your Intel EtherExpress 16
card to be memory mapped at address 0xD0000, and
set the amount of mapped memory to 32K using the
Intel supplied <tt class=
"FILENAME">softset.exe</tt> program.</p>
</div>
</div>
<div class="QANDAENTRY">
<div class="QUESTION">
<p><a name="Q4.3.12."></a><b>4.3.12.</b> When
installing on an EISA HP Netserver, my on-board
AIC-7xxx SCSI controller isn't detected.</p>
</div>
<div class="ANSWER">
<p><b></b>This is a known problem, and will
hopefully be fixed in the future. In order to get
your system installed at all, boot with the <tt
class="OPTION">-c</tt> option into UserConfig, but
<span class="emphasis"><i class=
"EMPHASIS">don't</i></span> use the pretty visual
mode but the plain old CLI mode. Type:</p>
<pre class="SCREEN">
<tt class="USERINPUT"><b>eisa 12</b></tt>
<tt class="USERINPUT"><b>quit</b></tt>
</pre>
<p>at the prompt. (Instead of `quit', you might
also type `visual', and continue the rest of the
configuration session in visual mode.) While it's
recommended to compile a custom kernel, dset now
also understands to save this value.</p>
<p>Refer to the FAQ topic 3.16 for an explanation
of the problem, and for how to continue. Remember
that you can find the FAQ on your local system in
/usr/share/doc/FAQ, provided you have installed the
`doc' distribution.</p>
</div>
</div>
<div class="QANDAENTRY">
<div class="QUESTION">
<p><a name="Q4.3.13."></a><b>4.3.13.</b> I have a
Panasonic AL-N1 or Rios Chandler Pentium machine
and I find that the system hangs before ever
getting into the installation now.</p>
</div>
<div class="ANSWER">
<p><b></b>Your machine doesn't like the new <tt
class="LITERAL">i586_copyout</tt> and <tt class=
"LITERAL">i586_copyin</tt> code for some reason. To
disable this, boot the installation boot floppy and
when it comes to the very first menu (the choice to
drop into kernel UserConfig mode or not) choose the
command-line interface (``expert mode'') version
and type the following at it:</p>
<pre class="SCREEN">
<tt class="USERINPUT"><b>flags npx0 1</b></tt>
</pre>
<p>Then proceed normally to boot. This will be
saved into your kernel, so you only need to do it
once.</p>
</div>
</div>
<div class="QANDAENTRY">
<div class="QUESTION">
<p><a name="Q4.3.14."></a><b>4.3.14.</b> I have
this CMD640 IDE controller that is said to be
broken.</p>
</div>
<div class="ANSWER">
<p><b></b>Yes, it is. FreeBSD does not support this
controller except through the legacy wdc
driver.</p>
</div>
</div>
<div class="QANDAENTRY">
<div class="QUESTION">
<p><a name="Q4.3.15."></a><b>4.3.15.</b> On a
Compaq Aero notebook, I get the message ``No floppy
devices found! Please check ...'' when trying to
install from floppy.</p>
</div>
<div class="ANSWER">
<p><b></b>With Compaq being always a little
different from other systems, they do not announce
their floppy drive in the CMOS RAM of an Aero
notebook. Therefore, the floppy disk driver assumes
there is no drive configured. Go to the UserConfig
screen, and set the Flags value of the fdc0 device
to 0x1. This pretends the existence of the first
floppy drive (as a 1.44 MB drive) to the driver
without asking the CMOS at all.</p>
</div>
</div>
<div class="QANDAENTRY">
<div class="QUESTION">
<p><a name="Q4.3.16."></a><b>4.3.16.</b> When I go
to boot my Intel AL440LX (``Atlanta'') -based
system from the hard disk the first time, it stops
with a <tt class="LITERAL">Read Error</tt>
message.</p>
</div>
<div class="ANSWER">
<p><b></b>There appears to be a bug in the BIOS on
at least some of these boards, this bug results in
the FreeBSD bootloader thinking that it is booting
from a floppy disk. This is only a problem if you
are not using the BootEasy boot manager. Slice the
disk in ``compatible''mode and install BootEasy
during the FreeBSD installation to avoid the bug,
or upgrade the BIOS (see Intel's website for
details).</p>
</div>
</div>
<div class="QANDAENTRY">
<div class="QUESTION">
<p><a name="Q4.3.17."></a><b>4.3.17.</b> When
installing on an Dell Poweredge XE, Dell
proprietary RAID controller DSA (Dell SCSI Array)
isn't recognized.</p>
</div>
<div class="ANSWER">
<p><b></b>Configure the DSA to use AHA-1540
emulation using EISA configuration utility. After
that FreeBSD detects the DSA as an Adaptec AHA-1540
SCSI controller, with irq 11 and port 340. Under
emulation mode system will use DSA RAID disks, but
you cannot use DSA-specific features such as
watching RAID health.</p>
</div>
</div>
<div class="QANDAENTRY">
<div class="QUESTION">
<p><a name="Q4.3.18."></a><b>4.3.18.</b> My
Ethernet adapter is detected as an AMD PCnet-FAST
(or similar) but it doesn't work. (Eg. onboard
Ethernet on IBM Netfinity 5xxx or 7xxx)</p>
</div>
<div class="ANSWER">
<p><b></b>The <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=lnc&sektion=4&manpath=FreeBSD+4.7-RELEASE">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">lnc</span>(4)</span></a> driver is
currently faulty, and will often not work correctly
with the PCnet-FAST and PCnet-FAST+. You need to
install a different Ethernet adapter.</p>
</div>
</div>
<div class="QANDAENTRY">
<div class="QUESTION">
<p><a name="Q4.3.19."></a><b>4.3.19.</b> I have an
IBM EtherJet PCI card, it is detected by the <span
class="CITEREFENTRY"><span class=
"REFENTRYTITLE">fxp</span>(4)</span> driver
correctly, but the lights on the card don't come on
and it doesn't connect to the network.</p>
</div>
<div class="ANSWER">
<p><b></b>We don't understand why this happens.
Neither do IBM (we asked them). The card is a
standard Intel EtherExpress Pro/100 with an IBM
label on it, and these cards normally work just
fine. You may see these symptoms only in some IBM
Netfinity servers. The only solution is to install
a different Ethernet adapter.</p>
</div>
</div>
<div class="QANDAENTRY">
<div class="QUESTION">
<p><a name="Q4.3.20."></a><b>4.3.20.</b> When I
configure the network during installation on an IBM
Netfinity 3500, the system freezes.</p>
</div>
<div class="ANSWER">
<p><b></b>There is a problem with the onboard
Ethernet in the Netfinity 3500 which we have not
been able to identify at this time. It may be
related to the SMP features of the system being
misconfigured. You will have to install another
Ethernet adapter and avoid attempting to configure
the onboard adapter at any time.</p>
</div>
</div>
<div class="QANDAENTRY">
<div class="QUESTION">
<p><a name="Q4.3.21."></a><b>4.3.21.</b> When I
install onto a drive managed by a Mylex PCI RAID
controller, the system fails to boot (eg. with a
<tt class="LITERAL">read error</tt> message).</p>
</div>
<div class="ANSWER">
<p><b></b>There is a bug in the Mylex driver which
results in it ignoring the ``8GB'' geometry mode
setting in the BIOS. Use the 2GB mode instead.</p>
</div>
</div>
</div>
</div>
</div>
</div>
<hr>
<p align="center"><small>This file, and other release-related
documents, can be downloaded from <a href=
"ftp://ftp.FreeBSD.org/">ftp://ftp.FreeBSD.org/</a>.</small></p>
<p align="center"><small>For questions about FreeBSD, read the
<a href="http://www.FreeBSD.org/docs.html">documentation</a>
before contacting <<a href=
"mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.</small></p>
<p align="center"><small>For questions about this
documentation, e-mail <<a href=
"mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</small></p>
<br>
<br>
</body>
</html>
|
