Uniden Data 2000 Wireless CDPD PC Card Guía de usuario descargar pdf (Pagina 20)

probe is read−only, but in rare cases, reading from a device may interfere with an important system function,

resulting in a lock−up.

Your system user's guide may include a map of system devices, showing their IO and memory ranges. These

can be explicitly excluded in config.opts.

Alternatively, if the probe is unreliable on your system, it can be disabled by setting CORE_OPTS to

``probe_io=0''. In this case, you should be very careful to specify only genuinely available ranges of ports

in config.opts, instead of using the default settings.

3.5 Memory probe failures

Symptoms:

• The core drivers load correctly when no cards are present, with no errors in the system log.

• The system freezes and/or reboots as soon as any card is inserted, before any beeps are heard.

Or alternately:

• All card insertions generate a high beep followed by a low beep.

• All cards are identified as ``anonymous memory cards''.

• The system log reports that various memory ranges have been excluded.

The core modules perform a memory scan at the time of first 16−bit card insertion. This scan can potentially

interfere with other memory mapped devices. Also, pre−3.0.0 driver packages perform a more aggressive

scan than more recent drivers. The memory window is defined in /etc/pcmcia/config.opts. The

default window is large, so it may help to restrict the scan to a narrower range. Reasonable ranges to try

include 0xd0000−0xdffff, 0xc0000−0xcffff, 0xc8000−0xcffff, or 0xd8000−0xdffff.

If you have DOS or Windows PCMCIA drivers, you may be able to deduce what memory region those

drivers use. Note that DOS memory addresses are often specified in ``segment'' form, which leaves off the

final hex digit (so an absolute address of 0xd0000 might be given as 0xd000). Be sure to add the extra digit

back when making changes to config.opts.

In unusual cases, a memory probe failure can indicate a timing register setup problem with the host

controller. See the Startup options section for information about dealing with common timing problems.

• cs: warning: no high memory space available!

CardBus bridges can allocate memory windows outside of the 640KB−1MB ``memory hole'' in the ISA bus

architecture. It is generally a good idea to configure CardBus bridges to use high memory windows, because

these are unlikely to conflict with other devices. Also, CardBus cards may require large memory windows,

which may be difficult or impossible to fit into low memory. Card Services will preferentially allocate

windows in high memory for CardBus bridges, if both low and high memory windows are defined in

config.opts. The default config.opts now includes a high memory window of

0xa0000000−0xa0ffffff. If you have a CardBus bridge and have upgraded from an older PCMCIA driver

release, add this memory window if it is not already defined.

Linux PCMCIA HOWTO

3.5 Memory probe failures 17

1 2 ... 15 16 17 18 19 20 21 22 23 24 25 ... 55 56

Sin comentarios

Uniden Data 2000 Wireless CDPD PC Card Guía de usuario Pagina 20