PCMCIA: Bad bridge mapping at ...

Support knowledgebase (pcmcia_dell-mem_72)
Applies to

SuSE Linux: Versions since 7.1
Kernel: Versions since 2.4.0
PCMCIA: Version 3.1.22-

Symptom

The PCMCIA system does not start; when you attempt to load the module i82365, you find an error message similar to the following in /var/log/messages:
Jun 10 14:50:58 linux kernel:   Bad bridge mapping at 0x13ff0000!
This can happen with notebooks (or computers with PCMCIA card reader/adapter) with more than 256 MB of main memory.

Cause

Kernel 2.4.x and large RAM: 'Bad bridge mapping' sometimes results if the kernel does not detect the memory size correctly and subsequently maps PCI to ranges that cause RAM conflicts. (according to D. Hinds, http://sourceforge.net/forum/forum.php?thread_id=96476&forum_id=7049)

Solution

Define the memory size with the kernel parameter 'mem' at the boot prompt:
boot: linux mem=xxxM
"xxx" being the size of the notebook's memory. If this works, enter the parameter permanently in /etc/lilo.conf (or follow the corresponding procedure for other boot loaders):
append="mem=xxxM"
Restart lilo:
lilo
We experienced one case where the IRQ list for PCMCIA had to be limited and IRQ 3 (used by von IrDA) had to be excluded. Therefore, if the error message 'Bad bridge mapping' persists despite 'mem=', try to exclude all IRQs used by ISA devices by means of an entry similar to the following in /etc/rc.config:
PCMCIA_PCIC_OPTS="irq_list=9,10,11"
Then start PCMCIA with:
rcpcmcia start
Keywords: PCMCIA, NOTEBOOK, LAPTOP, DELL, BADBRIDGEMAPPING, MEM, RAM, CARDREADER

Feedback welcome: Send Mail to cdb@suse.de (Please give the following subject: SDB-pcmcia_dell-mem_72)
SDB-pcmcia_dell-mem_72, Copyright SuSE Linux AG, Nürnberg, Germany - Version: 01. Feb 2002
SuSE Linux AG - Last generated: 01. Feb 2002 by tino (sdb_gen 1.40.0)