|
Lines 203-210
Link Here
|
| 203 |
from working.</para> |
203 |
from working.</para> |
| 204 |
</question> |
204 |
</question> |
| 205 |
<answer> |
205 |
<answer> |
| 206 |
<para>Use the UserConfig utility (see |
206 |
<para>Set the hints |
| 207 |
<filename>HARDWARE.TXT</filename>) and disable the probing |
207 |
<quote>hint.mcd.0.disabled="1"</quote> and |
|
|
208 |
<quote>hint.mcd.1.disabled="1"</quote> |
| 209 |
in the third stage boot loader to disable the probing |
| 208 |
of the <devicename>mcd0</devicename> and |
210 |
of the <devicename>mcd0</devicename> and |
| 209 |
<devicename>mcd1</devicename> devices. Generally speaking, |
211 |
<devicename>mcd1</devicename> devices. Generally speaking, |
| 210 |
you should only leave the devices that you will be using |
212 |
you should only leave the devices that you will be using |
|
Lines 218-233
Link Here
|
| 218 |
</question> |
220 |
</question> |
| 219 |
<answer> |
221 |
<answer> |
| 220 |
<para>Your card is probably on a different IRQ from what is |
222 |
<para>Your card is probably on a different IRQ from what is |
| 221 |
specified in the kernel configuration. The ed driver does |
223 |
specified in the <filename>/boot/device.hints</filename> file. The ed driver does |
| 222 |
not use the `soft' configuration by default (values entered |
224 |
not use the `soft' configuration by default (values entered |
| 223 |
using EZSETUP in DOS), but it will use the software |
225 |
using EZSETUP in DOS), but it will use the software |
| 224 |
configuration if you specify <literal>?</literal> in the IRQ field of your |
226 |
configuration if you specify <literal>-1</literal> in the hints |
| 225 |
kernel config file.</para> |
227 |
for the interface.</para> |
| 226 |
|
228 |
|
| 227 |
<para>Either move the jumper on the card to a hard |
229 |
<para>Either move the jumper on the card to a hard |
| 228 |
configuration setting (altering the kernel settings if |
230 |
configuration setting (altering the kernel settings if |
| 229 |
necessary), or specify the IRQ as <literal>-1</literal> in UserConfig or <literal>?</literal> |
231 |
necessary), or specify the IRQ as <literal>-1</literal> |
| 230 |
in your kernel config file. This will tell the kernel to |
232 |
by setting the hint <quote>hint.ed.0.irq="-1"</quote> |
|
|
233 |
This will tell the kernel to |
| 231 |
use the soft configuration.</para> |
234 |
use the soft configuration.</para> |
| 232 |
|
235 |
|
| 233 |
<para>Another possibility is that your card is at IRQ 9, |
236 |
<para>Another possibility is that your card is at IRQ 9, |
|
Lines 244-252
Link Here
|
| 244 |
<answer> |
247 |
<answer> |
| 245 |
<para>Older IBM laptops use a non-standard keyboard |
248 |
<para>Older IBM laptops use a non-standard keyboard |
| 246 |
controller, so you must tell the keyboard driver (atkbd0) to |
249 |
controller, so you must tell the keyboard driver (atkbd0) to |
| 247 |
go into a special mode which works on the ThinkPads. Change |
250 |
go into a special mode which works on the ThinkPads. Set the |
| 248 |
the atkbd0 'Flags' to 0x4 in UserConfig and it should work |
251 |
hint <quote>hint.atkbd.0.flags="4"</quote> and it should work |
| 249 |
fine. (Look in the Input Menu for 'Keyboard'.)</para> |
252 |
fine.</para> |
| 250 |
</answer> |
253 |
</answer> |
| 251 |
</qandaentry> |
254 |
</qandaentry> |
| 252 |
<qandaentry> |
255 |
<qandaentry> |
|
Lines 268-290
Link Here
|
| 268 |
<answer> |
271 |
<answer> |
| 269 |
<para>This is a known problem, and will hopefully be fixed |
272 |
<para>This is a known problem, and will hopefully be fixed |
| 270 |
in the future. In order to get your system installed at |
273 |
in the future. In order to get your system installed at |
| 271 |
all, boot with the <option>-c</option> option into |
274 |
all, set the hint <quote>hw.eisa_slots="12"</quote> in the |
| 272 |
UserConfig, but <emphasis>don't</emphasis> use the pretty |
275 |
third stage loader.</para> |
| 273 |
visual mode but the plain old CLI mode. Type:</para> |
|
|
| 274 |
|
| 275 |
<screen><userinput>eisa 12</userinput> |
| 276 |
<userinput>quit</userinput></screen> |
| 277 |
|
| 278 |
<para>at the prompt. (Instead of `quit', you might also |
| 279 |
type `visual', and continue the rest of the configuration |
| 280 |
session in visual mode.) While it's recommended to compile |
| 281 |
a custom kernel, dset now also understands to save |
| 282 |
this value.</para> |
| 283 |
|
| 284 |
<para>Refer to the FAQ topic 3.16 for an explanation of the |
| 285 |
problem, and for how to continue. Remember that you can |
| 286 |
find the FAQ on your local system in /usr/share/doc/FAQ, |
| 287 |
provided you have installed the `doc' distribution.</para> |
| 288 |
</answer> |
276 |
</answer> |
| 289 |
</qandaentry> |
277 |
</qandaentry> |
| 290 |
<qandaentry> |
278 |
<qandaentry> |
|
Lines 297-312
Link Here
|
| 297 |
<para>Your machine doesn't like the new |
285 |
<para>Your machine doesn't like the new |
| 298 |
<literal>i586_copyout</literal> and |
286 |
<literal>i586_copyout</literal> and |
| 299 |
<literal>i586_copyin</literal> code for some reason. To |
287 |
<literal>i586_copyin</literal> code for some reason. To |
| 300 |
disable this, boot the installation boot floppy and when it |
288 |
disable this, set the hint <quote>hint.npx.0.flags="1"</quote></para> |
| 301 |
comes to the very first menu (the choice to drop into kernel |
|
|
| 302 |
UserConfig mode or not) choose the command-line interface |
| 303 |
(<quote>expert mode</quote>) version and type the following |
| 304 |
at it:</para> |
| 305 |
|
| 306 |
<screen><userinput>flags npx0 1</userinput></screen> |
| 307 |
|
| 308 |
<para>Then proceed normally to boot. This will be saved |
| 309 |
into your kernel, so you only need to do it once.</para> |
| 310 |
</answer> |
289 |
</answer> |
| 311 |
</qandaentry> |
290 |
</qandaentry> |
| 312 |
<qandaentry> |
291 |
<qandaentry> |
|
Lines 328-335
Link Here
|
| 328 |
<para>With Compaq being always a little different from other |
307 |
<para>With Compaq being always a little different from other |
| 329 |
systems, they do not announce their floppy drive in the CMOS |
308 |
systems, they do not announce their floppy drive in the CMOS |
| 330 |
RAM of an Aero notebook. Therefore, the floppy disk driver |
309 |
RAM of an Aero notebook. Therefore, the floppy disk driver |
| 331 |
assumes there is no drive configured. Go to the UserConfig |
310 |
assumes there is no drive configured. Set the hint |
| 332 |
screen, and set the Flags value of the fdc0 device to 0x1. |
311 |
<quote>hint.fdc.0.flags="1"</quote> |
| 333 |
This pretends the existence of the first floppy drive (as a |
312 |
This pretends the existence of the first floppy drive (as a |
| 334 |
1.44 MB drive) to the driver without asking the CMOS at |
313 |
1.44 MB drive) to the driver without asking the CMOS at |
| 335 |
all.</para> |
314 |
all.</para> |