|
Lines 24-181
Link Here
|
| 24 |
to different hardware requirements from desktops, are |
24 |
to different hardware requirements from desktops, are |
| 25 |
discussed below.</para> |
25 |
discussed below.</para> |
| 26 |
</abstract> |
26 |
</abstract> |
| 27 |
</articleinfo> |
27 |
</articleinfo> |
| 28 |
|
28 |
|
| 29 |
<para>FreeBSD is often thought of as a server operating system, but |
29 |
<para>FreeBSD is often thought of as a server operating system, but |
| 30 |
it works just fine on the desktop, and if you want to use it on |
30 |
it works just fine on the desktop, and if you want to use it on |
| 31 |
your laptop you can enjoy all the usual benefits: systematic |
31 |
your laptop you can enjoy all the usual benefits: systematic |
| 32 |
layout, easy administration and upgrading, the ports/packages |
32 |
layout, easy administration and upgrading, the ports/packages |
| 33 |
system for adding software, and so on. (Its other benefits, |
33 |
system for adding software, and so on. (Its other benefits, |
| 34 |
such as stability, network performance, and performance under |
34 |
such as stability, network performance, and performance under |
| 35 |
a heavy load, may not be obvious on a laptop, of course.) |
35 |
a heavy load, may not be obvious on a laptop, of course.) |
| 36 |
However, installing it on laptops often involves problems which |
36 |
However, installing it on laptops often involves problems which |
| 37 |
are not encountered on desktop machines and are not commonly |
37 |
are not encountered on desktop machines and are not commonly |
| 38 |
discussed (laptops, even more than desktops, are fine-tuned for |
38 |
discussed (laptops, even more than desktops, are fine-tuned for |
| 39 |
Microsoft Windows). This article aims to discuss some of these |
39 |
Microsoft Windows). This article aims to discuss some of these |
| 40 |
issues.</para> |
40 |
issues.</para> |
| 41 |
|
41 |
|
| 42 |
<sect1> |
42 |
<sect1> |
| 43 |
<title>XFree86</title> |
43 |
<title>XFree86</title> |
| 44 |
|
44 |
|
| 45 |
<para>Recent versions of XFree86 work with most display adapters |
45 |
<para>Recent versions of XFree86 work with most display adapters |
| 46 |
available on laptops these days. Acceleration may not be |
46 |
available on laptops these days. Acceleration may not be |
| 47 |
supported, but a generic SVGA configuration should work.</para> |
47 |
supported, but a generic SVGA configuration should work.</para> |
| 48 |
|
48 |
|
| 49 |
<para>Check your laptop documentation for which card you have, |
49 |
<para>Check your laptop documentation for which card you have, |
| 50 |
and check in the XFree86 documentation (or setup program) |
50 |
and check in the XFree86 documentation (or setup program) |
| 51 |
to see whether it is specifically supported. If it is not, use |
51 |
to see whether it is specifically supported. If it is not, use |
| 52 |
a generic device (do not go for a name which just looks |
52 |
a generic device (do not go for a name which just looks |
| 53 |
similar). In XFree86 version 4, you can try your luck |
53 |
similar). In XFree86 version 4, you can try your luck |
| 54 |
with the command <userinput>XFree86 -configure</userinput> |
54 |
with the command <userinput>XFree86 -configure</userinput> |
| 55 |
which auto-detects a lot of configurations.</para> |
55 |
which auto-detects a lot of configurations.</para> |
| 56 |
|
56 |
|
| 57 |
<para>The problem often is configuring the monitor. Common |
57 |
<para>The problem often is configuring the monitor. Common |
| 58 |
resources for XFree86 focus on CRT monitors; getting a |
58 |
resources for XFree86 focus on CRT monitors; getting a |
| 59 |
suitable modeline for an LCD display may be tricky. You may |
59 |
suitable modeline for an LCD display may be tricky. You may |
| 60 |
be lucky and not need to specify a modeline, or just need to |
60 |
be lucky and not need to specify a modeline, or just need to |
| 61 |
specify suitable HorizSync and VertRefresh ranges. If that |
61 |
specify suitable HorizSync and VertRefresh ranges. If that |
| 62 |
does not work, the best option is to check web resources |
62 |
does not work, the best option is to check web resources |
| 63 |
devoted to configuring X on laptops (these are often |
63 |
devoted to configuring X on laptops (these are often |
| 64 |
linux-oriented sites but it does not matter because both systems |
64 |
linux-oriented sites but it does not matter because both systems |
| 65 |
use XFree86) and copy a modeline posted by someone for similar |
65 |
use XFree86) and copy a modeline posted by someone for similar |
| 66 |
hardware.</para> |
66 |
hardware.</para> |
| 67 |
|
67 |
|
| 68 |
<para>Most laptops come with two buttons on their pointing |
68 |
<para>Most laptops come with two buttons on their pointing |
| 69 |
devices, which is rather problematic in X (since the middle |
69 |
devices, which is rather problematic in X (since the middle |
| 70 |
button is commonly used to paste text); you can map a |
70 |
button is commonly used to paste text); you can map a |
| 71 |
simultaneous left-right click in your X configuration to |
71 |
simultaneous left-right click in your X configuration to |
| 72 |
a middle button click with the line</para> |
72 |
a middle button click with the line</para> |
| 73 |
|
73 |
|
| 74 |
<programlisting> |
74 |
<programlisting> |
| 75 |
Option "Emulate3Buttons" |
75 |
Option "Emulate3Buttons" |
| 76 |
</programlisting> |
76 |
</programlisting> |
| 77 |
|
77 |
|
| 78 |
<para>in the XF86Config file in the <literal>InputDevice</literal> section (for XFree86 |
78 |
<para>in the XF86Config file in the <literal>InputDevice</literal> |
| 79 |
version 4; for version 3, put just the line <literal>Emulate3Buttons</literal>, |
79 |
section (for XFree86 version 4; for version 3, put just the line |
| 80 |
without the quotes, in the <literal>Pointer</literal> section.)</para> |
80 |
<literal>Emulate3Buttons</literal>, without the quotes, in the |
| 81 |
</sect1> |
81 |
<literal>Pointer</literal> section.)</para> |
| 82 |
|
82 |
</sect1> |
| 83 |
<sect1> |
83 |
|
| 84 |
<title>Modems</title> |
84 |
<sect1> |
| 85 |
<para> |
85 |
<title>Modems</title> |
| 86 |
Laptops usually come with internal (on-board) modems. |
86 |
<para> |
| 87 |
Unfortunately, this almost always means they are <quote>winmodems</quote> whose |
87 |
Laptops usually come with internal (on-board) modems. |
| 88 |
functionality is implemented in software, for which only windows |
88 |
Unfortunately, this almost always means they are |
| 89 |
drivers are normally available (though a few drivers are beginning |
89 |
<quote>winmodems</quote> whose |
| 90 |
to show up for other operating systems). Otherwise, you |
90 |
functionality is implemented in software, for which only windows |
| 91 |
need to buy an external modem: the most compact option is |
91 |
drivers are normally available (though a few drivers are beginning |
| 92 |
probably a PC-Card (PCMCIA) modem, discussed below, but |
92 |
to show up for other operating systems). Otherwise, you |
| 93 |
serial or USB modems may be cheaper. Generally, regular |
93 |
need to buy an external modem: the most compact option is |
| 94 |
modems (non-winmodems) should work fine. |
94 |
probably a PC-Card (PCMCIA) modem, discussed below, but |
| 95 |
</para> |
95 |
serial or USB modems may be cheaper. Generally, regular |
| 96 |
|
96 |
modems (non-winmodems) should work fine. |
| 97 |
</sect1> |
97 |
</para> |
| 98 |
|
98 |
|
| 99 |
<sect1> |
99 |
</sect1> |
| 100 |
<title>PCMCIA (PC-card) devices</title> |
100 |
|
| 101 |
|
101 |
<sect1> |
| 102 |
<para> Most laptops come with PCMCIA (also called PC-card) |
102 |
<title>PCMCIA (PC-card) devices</title> |
| 103 |
slots; these are supported fine under FreeBSD. Look through |
103 |
|
| 104 |
your boot-up messages (using dmesg) and see whether these were |
104 |
<para> Most laptops come with PCMCIA (also called PC-card) |
| 105 |
detected correctly (they should appear as |
105 |
slots; these are supported fine under FreeBSD. Look through |
| 106 |
<devicename>pccard0</devicename>, |
106 |
your boot-up messages (using dmesg) and see whether these were |
| 107 |
<devicename>pccard1</devicename> etc on devices like |
107 |
detected correctly (they should appear as |
| 108 |
<devicename>pcic0</devicename>).</para> |
108 |
<devicename>pccard0</devicename>, |
| 109 |
|
109 |
<devicename>pccard1</devicename> etc on devices like |
| 110 |
<para>FreeBSD currently supports 16-bit PCMCIA cards, but not |
110 |
<devicename>pcic0</devicename>).</para> |
| 111 |
32-bit (<quote>CardBus</quote>) cards. A database of supported cards is in |
111 |
|
| 112 |
the file <filename>/etc/defaults/pccard.conf</filename>. Look |
112 |
<para>FreeBSD currently supports 16-bit PCMCIA cards, but not |
| 113 |
through it, and preferably buy cards listed there. Cards not |
113 |
32-bit (<quote>CardBus</quote>) cards. A database of supported |
| 114 |
listed may also work as <quote>generic</quote> devices: in particular most |
114 |
cards is in the file <filename>/etc/defaults/pccard.conf</filename>. |
| 115 |
modems (16-bit) should work fine, provided they are not |
115 |
Look through it, and preferably buy cards listed there. Cards not |
| 116 |
winmodems (these do exist even as PC-cards, so watch out). If |
116 |
listed may also work as <quote>generic</quote> devices: in |
| 117 |
your card is recognised as a generic modem, note that the |
117 |
particular most modems (16-bit) should work fine, provided they |
| 118 |
default pccard.conf file specifies a delay time of 10 seconds |
118 |
are not winmodems (these do exist even as PC-cards, so watch out). |
| 119 |
(to avoid freezes on certain modems); this may well be |
119 |
If your card is recognised as a generic modem, note that the |
| 120 |
over-cautious for your modem, so you may want to play with it, |
120 |
default pccard.conf file specifies a delay time of 10 seconds |
| 121 |
reducing it or removing it totally.</para> |
121 |
(to avoid freezes on certain modems); this may well be |
| 122 |
|
122 |
over-cautious for your modem, so you may want to play with it, |
| 123 |
<para>Some parts of <filename>pccard.conf</filename> may need editing. Check the irq |
123 |
reducing it or removing it totally.</para> |
| 124 |
line, and be sure to remove any number already being used: in |
124 |
|
| 125 |
particular, if you have an on board sound card, remove irq 5 |
125 |
<para>Some parts of <filename>pccard.conf</filename> may need |
| 126 |
(otherwise you may experience hangs when you insert a card). |
126 |
editing. Check the irq line, and be sure to remove any number |
| 127 |
Check also the available memory slots; if your card is not |
127 |
already being used: in particular, if you have an on board sound |
| 128 |
being detected, try changing it to one of the other allowed |
128 |
card, remove irq 5 (otherwise you may experience hangs when you |
| 129 |
values (listed in the man page &man.pccardc.8;). |
129 |
insert a card). Check also the available memory slots; if your |
| 130 |
</para> |
130 |
card is not being detected, try changing it to one of the other |
| 131 |
|
131 |
allowed values (listed in the man page &man.pccardc.8;). |
| 132 |
<para>If it is not running already, start the pccardd daemon. |
132 |
</para> |
| 133 |
(To enable it at boot time, add |
133 |
|
| 134 |
<programlisting>pccard_enable="YES"</programlisting> to |
134 |
<para>If it is not running already, start the pccardd daemon. |
| 135 |
<filename>/etc/rc.conf</filename>). Now your cards should be |
135 |
(To enable it at boot time, add |
| 136 |
detected when you insert and remove them, and you should get |
136 |
<programlisting>pccard_enable="YES"</programlisting> to |
| 137 |
log messages about new devices being enabled.</para> |
137 |
<filename>/etc/rc.conf</filename>). Now your cards should be |
| 138 |
|
138 |
detected when you insert and remove them, and you should get |
| 139 |
<para>There have been major changes to the pccard code |
139 |
log messages about new devices being enabled.</para> |
| 140 |
(including ISA routing of interrupts, for machines whose |
140 |
|
| 141 |
PCIBIOS FreeBSD can not seem to use) before the FreeBSD 4.4 |
141 |
<para>There have been major changes to the pccard code |
| 142 |
release. If you have problems, try upgrading your system.</para> |
142 |
(including ISA routing of interrupts, for machines whose |
|
|
143 |
PCIBIOS FreeBSD can not seem to use) before the FreeBSD 4.4 |
| 144 |
release. If you have problems, try upgrading your system.</para> |
| 143 |
|
145 |
|
| 144 |
</sect1> |
146 |
</sect1> |
| 145 |
|
147 |
|
| 146 |
<sect1> |
148 |
<sect1> |
| 147 |
|
149 |
|
| 148 |
<title>Power management</title> |
150 |
<title>Power management</title> |
| 149 |
|
151 |
|
| 150 |
<para>Unfortunately, this is not very reliably supported under |
152 |
<para>Unfortunately, this is not very reliably supported under |
| 151 |
FreeBSD. If you are lucky, some functions may work reliably; |
153 |
FreeBSD. If you are lucky, some functions may work reliably; |
| 152 |
or they may not work at all.</para> |
154 |
or they may not work at all.</para> |
| 153 |
|
155 |
|
| 154 |
<para>To enable this, you may need to compile a kernel with |
156 |
<para>To enable this, you may need to compile a kernel with |
| 155 |
power management support (<literal>device apm0</literal>) or |
157 |
power management support (<literal>device apm0</literal>) or |
| 156 |
add the option <literal>enable apm0</literal> to <filename>/boot/loader.conf</filename>, and |
158 |
add the option <literal>enable apm0</literal> to |
| 157 |
also enable the apm daemon at boot time (line |
159 |
<filename>/boot/loader.conf</filename>, and |
| 158 |
<literal>apm_enable="YES"</literal> in |
160 |
also enable the apm daemon at boot time (line |
| 159 |
<filename>/etc/rc.conf</filename>). The apm commands are |
161 |
<literal>apm_enable="YES"</literal> in |
| 160 |
listed in the &man.apm.8; manpage. For instance, |
162 |
<filename>/etc/rc.conf</filename>). The apm commands are |
| 161 |
<command>apm -b</command> gives you battery status (or 255 if |
163 |
listed in the &man.apm.8; manpage. For instance, |
| 162 |
not supported), <command>apm -Z</command> puts the laptop on |
164 |
<command>apm -b</command> gives you battery status (or 255 if |
| 163 |
standby, <command>apm -z</command> (or zzz) suspends it. To |
165 |
not supported), <command>apm -Z</command> puts the laptop on |
| 164 |
shutdown and power off the machine, use <command>shutdown -p</command>. |
166 |
standby, <command>apm -z</command> (or zzz) suspends it. To |
| 165 |
Again, some or all of these functions may not work very well |
167 |
shutdown and power off the machine, use <command>shutdown -p</command>. |
| 166 |
or at all. You may find that laptop suspension/standby works |
168 |
Again, some or all of these functions may not work very well |
| 167 |
in console mode but not under X (that is, the screen does not |
169 |
or at all. You may find that laptop suspension/standby works |
| 168 |
come on again; in that case, switch to a virtual console |
170 |
in console mode but not under X (that is, the screen does not |
| 169 |
(using Ctrl-Alt-F1 or another function key) and then execute |
171 |
come on again; in that case, switch to a virtual console |
| 170 |
the apm command. |
172 |
(using Ctrl-Alt-F1 or another function key) and then execute |
| 171 |
</para> |
173 |
the apm command. |
| 172 |
|
174 |
</para> |
| 173 |
<para>The X window system (XFree86) also includes display power |
175 |
|
| 174 |
management (look at the &man.xset.1; man page, and search for |
176 |
<para>The X window system (XFree86) also includes display power |
| 175 |
dpms there). You may want to investigate this. However, this, |
177 |
management (look at the &man.xset.1; man page, and search for |
| 176 |
too, works inconsistently on laptops: it |
178 |
dpms there). You may want to investigate this. However, this, |
| 177 |
often turns off the display but does not turn off the |
179 |
too, works inconsistently on laptops: it |
| 178 |
backlight.</para> |
180 |
often turns off the display but does not turn off the |
|
|
181 |
backlight.</para> |
| 179 |
|
182 |
|
| 180 |
</sect1> |
183 |
</sect1> |
| 181 |
</article> |
184 |
</article> |