pcmcia bridge problem - Portable

This is a discussion on pcmcia bridge problem - Portable ; I have problems with a Samsung MagicLan 2100P PCI card. This card uses a Cirrus Logic CL 6729 PCMCIA bridge. So it's not really a portable device, but PCMCIA people directed me here. On my former motherboard (asus a7v266) it ...

+ Reply to Thread
Results 1 to 9 of 9

Thread: pcmcia bridge problem

  1. pcmcia bridge problem

    I have problems with a Samsung MagicLan 2100P PCI card.
    This card uses a Cirrus Logic CL 6729 PCMCIA bridge.
    So it's not really a portable device, but PCMCIA people
    directed me here.

    On my former motherboard (asus a7v266) it could be
    accessed trouble-free.

    Now I installed it on a asus a7n8x deluxe board and
    it ceased to work. PCMCIA modules load correctly but
    it does not recognize the wlan 'socket'. cardctl tells:

    # cardctl ident
    Socket 0:
    no product info available
    function: 136 ((null))
    Socket 1:
    no product info available

    The Anonymous Memory in socket 0 seems correct only the
    wlan (socket 1) part is missing.

    If I recall correctly the card was on PCI bus 0 with
    the old card, while it is on bus 1 now (from lspci).

    I use pcmcia-cs and -modules version 3.2.2, kernel
    version is 2.4.32pre8. The only no-std configuration is:

    PCIC=i82365
    PCIC_OPTS="irq_mode=1 fast_pci=1 cmd_time=16"

    irq_mode=0 would freeze the machine.

    Any ideas who to bring up this card?

    Thanks,
    tobias


  2. Re: pcmcia bridge problem

    Tobias Richter wrote:

    > If I recall correctly the card was on PCI bus 0 with
    > the old card, while it is on bus 1 now (from lspci).


    It may be that the memory windows in /etc/pcmcia/config.opts are not
    being passed through to PCI bus 1. Check 'lspci -v' for the PCI bus
    bridge that reports subordinate PCI bus 1, and see what memory and IO
    port ranges it specifies. And then try putting those in config.opts
    in place of the default ranges.

    -- Dave

  3. Re: pcmcia bridge problem

    dhinds@sonic.net wrote:
    > Tobias Richter wrote:
    >> If I recall correctly the card was on PCI bus 0 with
    >> the old card, while it is on bus 1 now (from lspci).

    >
    > It may be that the memory windows in /etc/pcmcia/config.opts are not
    > being passed through to PCI bus 1. Check 'lspci -v' for the PCI bus
    > bridge that reports subordinate PCI bus 1, and see what memory and IO
    > port ranges it specifies. And then try putting those in config.opts
    > in place of the default ranges.


    Using that instead of the original values it does no longer configure
    the anonymous memory. If used additional to the original values that again
    works, but nothing further. So still no wlan interface is found.

    Thanks anyway,
    tobias

  4. Re: pcmcia bridge problem

    Tobias Richter wrote:
    > dhinds@sonic.net wrote:
    >> Tobias Richter wrote:
    >>> If I recall correctly the card was on PCI bus 0 with
    >>> the old card, while it is on bus 1 now (from lspci).

    >>
    >> It may be that the memory windows in /etc/pcmcia/config.opts are not
    >> being passed through to PCI bus 1. Check 'lspci -v' for the PCI bus
    >> bridge that reports subordinate PCI bus 1, and see what memory and IO
    >> port ranges it specifies. And then try putting those in config.opts
    >> in place of the default ranges.


    > Using that instead of the original values it does no longer configure
    > the anonymous memory. If used additional to the original values that again
    > works, but nothing further. So still no wlan interface is found.


    Well you are going to have to try to be a little bit more descriptive
    if you want a solution to your problem.

    If it no longer configures the card as anonymous memory, and doesn't
    configure it as a wireless device, how exactly is it configured?

    System log messages would be helpful.

    -- Dave

  5. Re: pcmcia bridge problem

    dhinds@sonic.net wrote:
    > Tobias Richter wrote:
    >> Using that instead of the original values it does no longer configure
    >> the anonymous memory. If used additional to the original values that again
    >> works, but nothing further. So still no wlan interface is found.

    >
    > Well you are going to have to try to be a little bit more descriptive
    > if you want a solution to your problem.
    >
    > If it no longer configures the card as anonymous memory, and doesn't
    > configure it as a wireless device, how exactly is it configured?
    >
    > System log messages would be helpful.


    Well, I still don't think it'll help much, but here we are.
    This is a log entry with _only_ memory stettings of pci brigde 1:

    Oct 28 21:37:01 host cardmgr[26736]: watching 2 sockets
    Oct 28 21:37:01 host cardmgr[26737]: starting, version is 3.2.2
    Oct 28 21:37:01 host cardmgr[26737]: socket 0: Anonymous Memory
    Oct 28 21:37:01 host cardmgr[26737]: executing: 'modprobe memory_cs'
    Oct 28 21:37:01 host cardmgr[26737]: get dev info on socket 0 failed: No such device

    This is the one with the additional default settings for memory and
    ioports:

    Oct 28 21:37:16 host cardmgr[26784]: watching 2 sockets
    Oct 28 21:37:16 host cardmgr[26785]: starting, version is 3.2.2
    Oct 28 21:37:16 host cardmgr[26785]: socket 0: Anonymous Memory
    Oct 28 21:37:16 host cardmgr[26785]: executing: 'modprobe sram_mtd'
    Oct 28 21:37:16 host cardmgr[26785]: Common memory region at 0x86000: Generic or SRAM
    Oct 28 21:37:16 host cardmgr[26785]: Common memory region at 0x7e000: Generic or SRAM
    Oct 28 21:37:16 host cardmgr[26785]: Common memory region at 0x3e000: Generic or SRAM
    Oct 28 21:37:16 host cardmgr[26785]: Common memory region at 0x0: Generic or SRAM
    Oct 28 21:37:16 host cardmgr[26785]: executing: 'modprobe memory_cs'
    Oct 28 21:37:16 host cardmgr[26785]: executing: './memory start mem0'

    Thanks so far,
    tobias

  6. Re: pcmcia bridge problem

    Tobias Richter wrote:
    >>
    >> System log messages would be helpful.


    > Well, I still don't think it'll help much, but here we are.
    > This is a log entry with _only_ memory stettings of pci brigde 1:


    > Oct 28 21:37:01 host cardmgr[26736]: watching 2 sockets
    > Oct 28 21:37:01 host cardmgr[26737]: starting, version is 3.2.2
    > Oct 28 21:37:01 host cardmgr[26737]: socket 0: Anonymous Memory
    > Oct 28 21:37:01 host cardmgr[26737]: executing: 'modprobe memory_cs'
    > Oct 28 21:37:01 host cardmgr[26737]: get dev info on socket 0 failed: No such device


    There should be more messages, from the kernel PCMCIA drivers, in
    addition to the cardmgr messages?

    -- Dave

  7. Re: pcmcia bridge problem

    dhinds@sonic.net wrote:
    > Tobias Richter wrote:
    >> Well, I still don't think it'll help much, but here we are.
    >> This is a log entry with _only_ memory stettings of pci brigde 1:

    >
    >> Oct 28 21:37:01 host cardmgr[26736]: watching 2 sockets
    >> Oct 28 21:37:01 host cardmgr[26737]: starting, version is 3.2.2
    >> Oct 28 21:37:01 host cardmgr[26737]: socket 0: Anonymous Memory
    >> Oct 28 21:37:01 host cardmgr[26737]: executing: 'modprobe memory_cs'
    >> Oct 28 21:37:01 host cardmgr[26737]: get dev info on socket 0 failed: No such device

    >
    > There should be more messages, from the kernel PCMCIA drivers, in
    > addition to the cardmgr messages?


    Doh! Sorry, I thought that was all there was.

    Oct 28 21:37:01 host kernel: Linux PCMCIA Card Services 3.2.2
    Oct 28 21:37:01 host kernel: kernel build: 2.4.23-pre8 unknown
    Oct 28 21:37:01 host kernel: options: [pci] [cardbus]
    Oct 28 21:37:01 host kernel: Intel ISA/PCI/CardBus PCIC probe:
    Oct 28 21:37:01 host kernel: Cirrus PD6729 rev 00 PCI-to-PCMCIA at slot 01:0a, port 0xa000
    Oct 28 21:37:01 host kernel: host opts [0]: [ring] [pci irq 11] [1/16/0] [1/36/0]
    Oct 28 21:37:01 host kernel: host opts [1]: [ring] [pci irq 11] [1/16/0] [1/36/0]
    Oct 28 21:37:01 host kernel: PCI card interrupts, PCI status changes
    Oct 28 21:37:01 host kernel: cs: unable to map card memory!
    Oct 28 21:37:01 host last message repeated 7 times
    Oct 28 21:37:01 host kernel: memory_cs: RequestWindow: Resource in use

    I still see no point in restricting memory ranges until error
    messages are seen. Why should that improve the situation?
    Here's the error free but still unsuccessful other test:

    Oct 28 21:37:15 host kernel: Linux PCMCIA Card Services 3.2.2
    Oct 28 21:37:15 host kernel: kernel build: 2.4.23-pre8 unknown
    Oct 28 21:37:15 host kernel: options: [pci] [cardbus]
    Oct 28 21:37:15 host kernel: Intel ISA/PCI/CardBus PCIC probe:
    Oct 28 21:37:15 host kernel: Cirrus PD6729 rev 00 PCI-to-PCMCIA at slot 01:0a, port 0xa000
    Oct 28 21:37:15 host kernel: host opts [0]: [ring] [pci irq 11] [1/16/0] [1/36/0]
    Oct 28 21:37:15 host kernel: host opts [1]: [ring] [pci irq 11] [1/16/0] [1/36/0]
    Oct 28 21:37:15 host kernel: PCI card interrupts, PCI status changes
    Oct 28 21:37:16 host kernel: cs: memory probe 0x0d0000-0x0dffff: excluding 0xd0000-0xdffff
    Oct 28 21:37:16 host kernel: cs: memory probe 0x0c0000-0x0cffff: excluding 0xc0000-0xcffff
    Oct 28 21:37:16 host kernel: sram_mtd: common at 0x86000, 192 kb, 100 ns
    Oct 28 21:37:16 host kernel: memory_cs: mem0: common 192 kb 32 kb 256 kb 248 kb

    My config.opts now looks like this:

    include port 0x100-0x4ff, port 0x800-0x8ff, port 0xc00-0xcff
    include memory 0xc0000-0xfffff
    include memory 0xa0000000-0xa0ffffff, memory 0x60000000-0x60ffffff
    include port 0x9000-0xbfff
    include memory 0xeb000000-0xecffffff
    exclude irq 4
    exclude irq 3
    exclude irq 7

    The last port/memory pair was commented out in the first
    syslog example.

    Thanks for still being helpful in spite of my poor reporting,
    tobias

  8. Re: pcmcia bridge problem

    Tobias Richter wrote:

    > Oct 28 21:37:01 host kernel: Linux PCMCIA Card Services 3.2.2
    > Oct 28 21:37:01 host kernel: kernel build: 2.4.23-pre8 unknown
    > Oct 28 21:37:01 host kernel: options: [pci] [cardbus]
    > Oct 28 21:37:01 host kernel: Intel ISA/PCI/CardBus PCIC probe:
    > Oct 28 21:37:01 host kernel: Cirrus PD6729 rev 00 PCI-to-PCMCIA at slot 01:0a, port 0xa000
    > Oct 28 21:37:01 host kernel: host opts [0]: [ring] [pci irq 11] [1/16/0] [1/36/0]
    > Oct 28 21:37:01 host kernel: host opts [1]: [ring] [pci irq 11] [1/16/0] [1/36/0]
    > Oct 28 21:37:01 host kernel: PCI card interrupts, PCI status changes
    > Oct 28 21:37:01 host kernel: cs: unable to map card memory!
    > Oct 28 21:37:01 host last message repeated 7 times
    > Oct 28 21:37:01 host kernel: memory_cs: RequestWindow: Resource in use


    Hmmm. Can you show 'lspci -v' output? (all of it)

    > I still see no point in restricting memory ranges until error
    > messages are seen. Why should that improve the situation?
    >
    > Here's the error free but still unsuccessful other test:


    This was error free due to a bug in pcmcia-cs that was fixed in 3.2.5.

    -- Dave

  9. Re: pcmcia bridge problem

    dhinds@sonic.net wrote:
    > Hmmm. Can you show 'lspci -v' output? (all of it)


    Sure. Follows below.

    >> Here's the error free but still unsuccessful other test:

    >
    > This was error free due to a bug in pcmcia-cs that was fixed in 3.2.5.


    Oops, that's strange.

    Again, thank you,
    tobias

    lspci -v:

    00:00.0 Host bridge: nVidia Corporation: Unknown device 01e0 (rev c1)
    Subsystem: Asustek Computer, Inc.: Unknown device 80ac
    Flags: bus master, 66Mhz, fast devsel, latency 0
    Memory at e0000000 (32-bit, prefetchable) [size=64M]
    Capabilities: [40] AGP version 2.0
    Capabilities: [60] #08 [2001]

    00:00.1 RAM memory: nVidia Corporation: Unknown device 01eb (rev c1)
    Subsystem: nVidia Corporation: Unknown device 0c17
    Flags: 66Mhz, fast devsel

    00:00.2 RAM memory: nVidia Corporation: Unknown device 01ee (rev c1)
    Subsystem: nVidia Corporation: Unknown device 0c17
    Flags: 66Mhz, fast devsel

    00:00.3 RAM memory: nVidia Corporation: Unknown device 01ed (rev c1)
    Subsystem: nVidia Corporation: Unknown device 0c17
    Flags: 66Mhz, fast devsel

    00:00.4 RAM memory: nVidia Corporation: Unknown device 01ec (rev c1)
    Subsystem: nVidia Corporation: Unknown device 0c17
    Flags: 66Mhz, fast devsel

    00:00.5 RAM memory: nVidia Corporation: Unknown device 01ef (rev c1)
    Subsystem: nVidia Corporation: Unknown device 0c17
    Flags: 66Mhz, fast devsel

    00:01.0 ISA bridge: nVidia Corporation: Unknown device 0060 (rev a4)
    Subsystem: Asustek Computer, Inc.: Unknown device 80ad
    Flags: bus master, 66Mhz, fast devsel, latency 0
    Capabilities: [48] #08 [01e1]

    00:01.1 SMBus: nVidia Corporation: Unknown device 0064 (rev a2)
    Subsystem: Asustek Computer, Inc.: Unknown device 0c11
    Flags: 66Mhz, fast devsel, IRQ 5
    I/O ports at e000 [size=32]
    Capabilities: [44] Power Management version 2

    00:02.0 USB Controller: nVidia Corporation: Unknown device 0067 (rev a4) (prog-if 10 [OHCI])
    Subsystem: Asustek Computer, Inc.: Unknown device 0c11
    Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 5
    Memory at ed087000 (32-bit, non-prefetchable) [size=4K]
    Capabilities: [44] Power Management version 2

    00:02.1 USB Controller: nVidia Corporation: Unknown device 0067 (rev a4) (prog-if 10 [OHCI])
    Subsystem: Asustek Computer, Inc.: Unknown device 0c11
    Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 11
    Memory at ed082000 (32-bit, non-prefetchable) [size=4K]
    Capabilities: [44] Power Management version 2

    00:02.2 USB Controller: nVidia Corporation: Unknown device 0068 (rev a4) (prog-if 20)
    Subsystem: Asustek Computer, Inc.: Unknown device 0c11
    Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 5
    Memory at ed083000 (32-bit, non-prefetchable) [size=256]
    Capabilities: [44] #0a [2080]
    Capabilities: [80] Power Management version 2

    00:04.0 Ethernet controller: nVidia Corporation: Unknown device 0066 (rev a1)
    Subsystem: Asustek Computer, Inc.: Unknown device 80a7
    Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 5
    Memory at ed086000 (32-bit, non-prefetchable) [size=4K]
    I/O ports at e400 [size=8]
    Capabilities: [44] Power Management version 2

    00:05.0 Multimedia audio controller: nVidia Corporation: Unknown device 006b (rev a2)
    Subsystem: Asustek Computer, Inc.: Unknown device 0c11
    Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 11
    Memory at ed000000 (32-bit, non-prefetchable) [size=512K]
    Capabilities: [44] Power Management version 2

    00:06.0 Multimedia audio controller: nVidia Corporation: Unknown device 006a (rev a1)
    Subsystem: Asustek Computer, Inc.: Unknown device 8095
    Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 5
    I/O ports at d000 [size=256]
    I/O ports at d400 [size=128]
    Memory at ed080000 (32-bit, non-prefetchable) [size=4K]
    Capabilities: [44] Power Management version 2

    00:08.0 PCI bridge: nVidia Corporation: Unknown device 006c (rev a3) (prog-if 00 [Normal decode])
    Flags: bus master, 66Mhz, fast devsel, latency 0
    Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
    I/O behind bridge: 00009000-0000bfff
    Memory behind bridge: eb000000-ecffffff

    00:09.0 IDE interface: nVidia Corporation: Unknown device 0065 (rev a2) (prog-if 8a [Master SecP PriP])
    Subsystem: Asustek Computer, Inc.: Unknown device 0c11
    Flags: bus master, 66Mhz, fast devsel, latency 0
    I/O ports at f000 [size=16]
    Capabilities: [44] Power Management version 2

    00:0c.0 PCI bridge: nVidia Corporation: Unknown device 006d (rev a3) (prog-if 00 [Normal decode])
    Flags: bus master, 66Mhz, fast devsel, latency 0
    Bus: primary=00, secondary=02, subordinate=02, sec-latency=32
    I/O behind bridge: 0000c000-0000cfff
    Memory behind bridge: e6000000-e7ffffff

    00:0d.0 FireWire (IEEE 1394): nVidia Corporation: Unknown device 006e (rev a3) (prog-if 10 [OHCI])
    Subsystem: Asustek Computer, Inc.: Unknown device 809a
    Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 11
    Memory at ed084000 (32-bit, non-prefetchable) [size=2K]
    Memory at ed085000 (32-bit, non-prefetchable) [size=64]
    Capabilities: [44] Power Management version 2

    00:1e.0 PCI bridge: nVidia Corporation: Unknown device 01e8 (rev c1) (prog-if 00 [Normal decode])
    Flags: bus master, 66Mhz, medium devsel, latency 32
    Bus: primary=00, secondary=03, subordinate=03, sec-latency=32
    Memory behind bridge: e8000000-eaffffff
    Prefetchable memory behind bridge: e4000000-e5ffffff

    01:06.0 Network controller: Elsa AG QuickStep 1000 (rev 01)
    Subsystem: Elsa AG QuickStep 1000
    Flags: medium devsel, IRQ 11
    Memory at ec000000 (32-bit, non-prefetchable) [size=128]
    I/O ports at 9000 [size=128]
    I/O ports at 9400 [size=4]

    01:08.0 SCSI storage controller: LSI Logic / Symbios Logic (formerly NCR) 53c875 (rev 26)
    Subsystem: LSI Logic / Symbios Logic (formerly NCR): Unknown device 1000
    Flags: bus master, medium devsel, latency 134, IRQ 11
    I/O ports at 9800 [size=256]
    Memory at ec001000 (32-bit, non-prefetchable) [size=256]
    Memory at ec002000 (32-bit, non-prefetchable) [size=4K]
    Expansion ROM at [disabled] [size=64K]
    Capabilities: [40] Power Management version 1

    01:09.0 Ethernet controller: Lite-On Communications Inc LNE100TX (rev 20)
    Subsystem: Kingston Technologies: Unknown device f002
    Flags: bus master, medium devsel, latency 32, IRQ 11
    I/O ports at 9c00 [size=256]
    Memory at ec003000 (32-bit, non-prefetchable) [size=256]
    Expansion ROM at [disabled] [size=256K]

    01:0a.0 PCMCIA bridge: Cirrus Logic CL 6729 (rev 07)
    Flags: stepping, slow devsel, IRQ 11
    I/O ports at a000 [size=4]

    01:0b.0 RAID bus controller: CMD Technology Inc: Unknown device 3112 (rev 01)
    Subsystem: CMD Technology Inc: Unknown device 6112
    Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 11
    I/O ports at a400 [size=8]
    I/O ports at a800 [size=4]
    I/O ports at ac00 [size=8]
    I/O ports at b000 [size=4]
    I/O ports at b400 [size=16]
    Memory at ec004000 (32-bit, non-prefetchable) [size=512]
    Expansion ROM at [disabled] [size=512K]
    Capabilities: [60] Power Management version 2

    02:01.0 Ethernet controller: 3Com Corporation: Unknown device 9201 (rev 40)
    Subsystem: Asustek Computer, Inc.: Unknown device 80ab
    Flags: bus master, medium devsel, latency 32, IRQ 5
    I/O ports at c000 [size=128]
    Memory at e7000000 (32-bit, non-prefetchable) [size=128]
    Expansion ROM at [disabled] [size=128K]
    Capabilities: [dc] Power Management version 2

    03:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G550 AGP (rev 01) (prog-if 00 [VGA])
    Subsystem: Matrox Graphics, Inc. Millennium G550 Dual Head DDR 32Mb
    Flags: bus master, medium devsel, latency 32, IRQ 5
    Memory at e4000000 (32-bit, prefetchable) [size=32M]
    Memory at e8000000 (32-bit, non-prefetchable) [size=16K]
    Memory at e9000000 (32-bit, non-prefetchable) [size=8M]
    Expansion ROM at [disabled] [size=128K]
    Capabilities: [dc] Power Management version 2
    Capabilities: [f0] AGP version 2.0


+ Reply to Thread