PCMCIA: unable to map memory

From: Ulrich Hansen (uhansen_at_mainz-online.de)
Date: 11/07/03

  • Next message: dhinds_at_sonic.net: "Re: PCMCIA: unable to map memory" 
    Date: Fri, 07 Nov 2003 19:04:15 +0100

    Hi,

    after a four day procedure of trial and error I am
    hoping that you could perhaps help me.

    Since nearly one year I run a Redhat 7.0 system on
    a compaq contura aero laptop. (486SLC33, 20 MB RAM
    10 GB hdd, one 16bit PCMCIA-Slot, kernel
    2.2.19ext3) Thanks to the pcmcia-package it works
    since then well as web/file/mailserver.

    Now I got a identical machine and installed
    successfully Redhat 9a on it. Runs nearly the same
    speed (slow but OK for its purpose).

    But I can't convince pcmcia to run with the kernel
    2.4.20-20.9.

    The problem:
    All aeros have naturally a defect in their RAM if
    this is upgraded to the max of 20MB (which I did,
    as you can imagine). The source of this problem is
    told to be a strange behaviour of the
    pcmcia-controller. Because of this, there is a
    32kb part of RAM that must be excluded for linux,
    otherwise the system freezes some time after
    start. For this purpose people use the BadRAM or
    BadMEM-patch provided by the linux-community and
    they append badram=0x010b0000,0xffff8000 at start
    or in lilo.conf.

    Further the pcmcia-cardmanager has to be told to
    only use the ram-adresses 0xb0000-0xb7fff which is
    done in /etc/pcmcia/config.opts (and all the other
    include commands are outcommented).

    As I told all this works rock-stable on the RedHat
    7 machine since nearly one year.

    With RedHat 9 and my 2.4 kernel this dosn't seem
    to work any more.

    If I start pcmcia, it says "unable to map memory"
    and dmesg tells me:

    -----
    Linux PCMCIA Card Services 3.2.5
       kernel build: 2.4.20-20.9-badram #1 Mon Nov 3
    03:22:06 CET 2003
       options: [pci] [apm]
    Intel ISA/PCI/CardBus PCIC probe:
       VLSI 82C146 rev 00 ISA-to-PCMCIA at port 0x3e0
    ofs 0x00
         host opts [0]: none
         ISA irqs (scanned) = 3,4,5,7,9,10,11,12,15
    status change on irq 15
    cs: memory probe 0x0b0000-0x0b7fff: excluding
    0xb0000-0xb7fff
    cs: unable to map card memory!
    cs: unable to map card memory!
    cs: unable to map card memory!
    cs: unable to map card memory!
    cs: unable to map card memory!
    cs: unable to map card memory!
    cs: unable to map card memory!
    cs: unable to map card memory!
    memory_cs: RequestWindow: Resource in use
    -----

    If I use the other RAM-addresses in config.opts,
    pcmcia starts and detects my 3Com574-NIC but the
    system freezes after some time as expected.

    Debugging
    I use the newest pcmcia-cs 3.2.5 (I also tried out
    3.2.3). Kernel pcmcia is disabled, modules and
    network are enabled. I also recompiled the kernel
    with enabled kernel-pcmcia and reinstalled
    pcmcia-cs - same result.

    I then copied the kernel 2.2.19ext3 over from my
    other aero, copied a 2.2.19 kernel tree into
    /usr/src (unfortunately I am not able to build a
    new 2.2 kernel on the redhat 9 system, must have
    something to do with the compilers). Then I
    reinstalled pcmcia-cs.
    The result: PCMCIA is working! on the RedHat 9
    system (but only with that specific kernel :-( )

    So it must have to do with the 2.4 kernel. As the
    only main difference to the 2.4-kernel, the
    2.2.19-kernel is compiled without pci-support. I
    had no success in compiling the 2.4-kernel without
    pci (compilation failed), don't know if this is
    important. The aero has of course no pci, it was
    manufactured 1994 - with ISA.

    If I append all my configuration files this will
    get too long. So please look at them: I copied
    them to:
    http://ulihansen.kicks-ass.net/aero/pcmcia-problem

    There you find:
    config.opts /etc/pcmcia/config.opts
    dmesg-2.2.19 dmesg after boot with kernel 2.2.19
    dmesg-2.4.20-20.9 dmesg after boot with 2.4.20
    kernel-config-2.2.19 .config of kernel 2.2.19
    kernel-config-2.4.20-20.9 .config of 2.4.20
    lilo.conf /etc/lilo.conf
    rc.d-init.d-pcmcia /etc/rc.d/init.d/pcmcia
    rc.d-rc.pcmcia /etc/rc.pcmcia
                              Same as /etc/rc.pcmcia.N
    sysconfig-pcmcia /etc/sysconfig/pcmcia

    Thank you very much for reading. I hope you have
    an idea.

    Thanks
    Uli

  • Next message: dhinds_at_sonic.net: "Re: PCMCIA: unable to map memory"

    Relevant Pages

    • Re: Contents of redhat-list digest...
      ... limiting CPU access per user ... Old Version of kermit Source Code ... handle kernel NULL pointer ... barcode reader, from TRU-64 to Redhat. ...
      (RedHat)
    • Re: RedHat 10 wishlist
      ... But performance is not everything SATA ... the smaller form factor drives. ... > kernel, ... >> REdhat is to wrap more stuff into its coming workstation release that I ...
      (alt.os.linux.redhat)
    • Re: APM (or ACPI) on an Acer TravelMate 280 (RH9)
      ... Red Hat Linux does not seem to like your laptop's BIOS and PCMCIA ... compile your own kernel in order to get ACPI and PCMCIA working. ... This will open a new window, in this window type in something like the ...
      (comp.os.linux.portable)
    • Re: pcmcia not working
      ... > I've just installed RH9 on my laptop, but I can't get pcmcia to work. ... You need the kernel-source RPM package for your current kernel installed ... To install the RPM package first mount the CDROM as root, ...
      (linux.redhat.misc)
    • Re: difficulty recompiling RHEL 4.2 kernel
      ... RHEL 4.2 specialized for scientific apps by Fermilab, CERN, and several ... Linux managers at Fermilab say my earlier problems were in parts of the ... You would hardly expect RedHat to do something about a rewritten version. ... You recompile your kernel only if you have narrowed down the error to the ...
      (comp.os.linux.setup)