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

Interrupt starvation often indicates a problem with the interrupt probe (see Interrupt scan failures). In some

cases, the probe will seem to work, but only report one or two available interrupts. Check your system log to

see if the scan results look sensible. Disabling the probe and selecting interrupts manually should help.

If the interrupt probe is not working properly, the socket driver may allocate an interrupt for monitoring card

insertions, even when interrupts are too scarce for this to be a good idea. In that case, you can switch the

controller to polled mode by setting PCIC_OPTS to ``poll_interval=100'. Or, if you have a CardBus

controller, try ``pci_csc=1'', which selects a PCI interrupt (if available) for card status changes.

IO port starvation is fairly uncommon, but sometimes happens with cards that require large, contiguous,

aligned regions of IO port space, or that only recognize a few specific IO port positions. The default IO port

ranges in /etc/pcmcia/config.opts are normally sufficient, but may be extended. In rare cases,

starvation may indicate that the IO port probe failed (see IO port scan failures).

Memory starvation is also uncommon with the default memory window settings in config.opts. CardBus

cards may require larger memory regions than typical 16−bit cards. Since CardBus memory windows can be

mapped anywhere in the host's PCI address space (rather than just in the 640K−1MB ``hole'' in PC systems),

it is helpful to specify large memory windows in high memory, such as 0xa0000000−0xa0ffffff.

3.8 Resource conflict only with two cards inserted

Symptoms:

• Two cards each work fine when used separately.

• When both cards are inserted, only one works.

This usually indicates a resource conflict with a system device that Linux does not know about. PCMCIA

devices are dynamically configured, so, for example, interrupts are allocated as needed, rather than

specifically assigned to particular cards or sockets. Given a list of resources that appear to be available, cards

are assigned resources in the order they are configured. In this case, the card configured last is being assigned

a resource that in fact is not free.

Check the system log to see what resources are used by the non−working card. Exclude these in

/etc/pcmcia/config.opts, and restart the cardmgr daemon to reload the resource database.

3.9 Device configuration does not complete

Symptoms:

• When a card is inserted, exactly one high beep is heard.

• Subsequent card insertions and removals may be ignored.

This indicates that the card was identified successfully, however, cardmgr has been unable to complete the

configuration process for some reason. The most likely reason is that a step in the card setup script has

blocked. A good example would be the network script blocking if a network card is inserted with no actual

Linux PCMCIA HOWTO

3.8 Resource conflict only with two cards inserted 19

1 2 ... 17 18 19 20 21 22 23 24 25 26 27 ... 55 56

Sin comentarios

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