Portege 650ct Pcmcia - yenta vs i82365 - Portable

This is a discussion on Portege 650ct Pcmcia - yenta vs i82365 - Portable ; Right, this is a bit of a wierd one. I have two cards: * One, no-name usb hub : cardbus * One, smc wlan card : 16 bit My trusty 650ct's bois is set to its PCIC/Cardbus setting. They both ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Portege 650ct Pcmcia - yenta vs i82365

  1. Portege 650ct Pcmcia - yenta vs i82365

    Right, this is a bit of a wierd one.

    I have two cards:

    * One, no-name usb hub : cardbus
    * One, smc wlan card : 16 bit

    My trusty 650ct's bois is set to its PCIC/Cardbus setting.

    They both work... ...but not together, which is what I'm trying to
    achieve.

    ==Scenario #1 - Yenta ==
    The usb hub pcmcia card works well. The Wlan card doesn't
    I'm using a 2.4.17 kernel with kernel pcmcia drivers; cardmgr 3.2.5.

    At boot time, we have:

    ....
    Yenta IRQ list 0000, PCI irq11
    Socket status: 30000006
    Yenta IRQ list 0000, PCI irq11
    Socket status: 30000006
    ....

    {Stick in my USB card, and I get:}

    PCI: Enabling device 15:00.0 (0000 -> 0002)
    PCI: Enabling device 15:00.1 (0000 -> 0002)
    PCI: Enabling device 15:00.2 (0000 -> 0002)

    {Modprobe usb-ohci, and we have}

    ....
    usb-ohci.c: USB OHCI at membase 0xc4043000, IRQ 11
    usb-ohci.c: usb-15:00.0, PCI device 1033:0035
    ....

    {Great! Now insert my SMC EZ wlan card + two unhopeful beeps later,
    syslog shows}

    cs: unable to map card memory!
    cs: unable to map card memory!
    cs: IO port probe 0x0c00-0xcff: clean.
    cs: IO port probe 0x0800-0x8ff: clean.
    cs: IO port probe 0x0100-0x4ff: clean. excluding 0x120-0x127
    0x220-0x22f 0x388 - 0x38f 0x480-0x48f 0x4d0-0x4d7

    {bummer :-(. I tried changing the memory window as per 3.4 of PCMCIA
    HOWTO to no avail. Cardctl config/status shows:}

    Socket 0: {Wlan card}
    Vcc 3.3V Vpp1 3.3V Vpp2 3.3v
    Socket 1: {USB}
    Vcc 3.3v Vpp1 3.3V Vpp2 3.3v
    interface type is "cardbus"
    irq 11 [exclusive] [level]
    function 0:
    function 1:
    function 2:


    Socket 0:
    3.3v 16-bit PC Card
    function 0: [ready], [wp], [bat dead]
    Socket 1:
    3.3v CardBus Card
    function 0: [ready]
    function 1: [ready]
    function 2: [ready]

    ==Scenario #2 - i82365==
    The wlan card works well. The pcmcia USB card doesn't
    I'm using a 2.4.17 kernel with pcmcia 3.2.5 module drivers; cardmgr
    3.2.5.

    At boot time, we have:

    Linux PCMCIA card services 3.2.5
    kernel build: 2.4.17 unknown
    options: [pci] [cardbus] [apm] [pnp]
    PnP: PNP BIOS installation structure at 0xc00f8dd0
    PnP: PNP BIOS version 1.0, entry at f0000:9d02, dseg at 0
    Intel ISA/PCI/Cardbus PCIC Probe:
    Toshiba ToPIC95-B rev 07 PCI-to-CardBus at slot 00:02, mem
    0xffeff000
    host opts [0]: [slot 0xd0] [ccr 0x15] [cdr 0x86] [rcr 0x00] [pci
    irq 11] [lat 168/176] [bus 20/20]
    host opts [0]: [slot 0xd0] [ccr 0x25] [cdr 0x86] [rcr 0x00] [pci
    irq 11] [lat 168/176] [bus 21/21]
    ISA irqs (default) = 3,4,5,7,10,15 PCI status changes
    cs: memory probe 0x0d0000-0x0dffff: clean.

    {then stick in my wlan card, and it works perfectly}

    init_module: prism2_cs.o: 0.2.0 Loaded
    init_module: dev_info is: prism2_cs
    prism2_cs: index 0x01: Vcc 3.3, irq 3, io 0x0140-0x017f
    indent ... {etc etc}

    {Meanwhile if I insert the pcmcia USB, and modprobe usb-ohci}

    usb.c: registered new driver usbdevfs
    usb.c: registered new driver hub
    PCI: No IRQ known for interrupt pin A of device. Please try using
    pci=biosirq.
    usb-ohci.c: found OHCI device with no IRQ assigned. check BIOS
    settings!
    PCI: No IRQ known for interrupt pin B of device. Please try using
    pci=biosirq.
    usb-ohci.c: found OHCI device with no IRQ assigned. check BIOS
    settings!

    {Trying pci=biosirq at boot time, causes a kernel panic. Meanwhile,
    running lspci -vvH 1}

    00:00.0 Host bridge: Toshiba America Info Systems 601 (rev 11)
    Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
    ParErr- Stepping- SERR- FastB2B-
    Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium
    >TAbort- SERR-
    Latency: 0, cache line size 08

    00:02.0 CardBus bridge: Toshiba America Info Systems ToPIC95 (rev 07)
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
    ParErr- Stepping- SERR- FastB2B-
    Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=slow >TAbort-
    SERR- Latency: 0
    Interrupt: pin A routed to IRQ 11
    Region 0: Memory at ffeff000 (32-bit, non-prefetchable)
    Bus: primary=00, secondary=14, subordinate=14, sec-latency=0
    Memory window 1: 10400000-107ff000
    I/O window 0: 00004000-000040ff
    I/O window 1: 00004400-000044ff
    BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset- 16bInt+
    PostWrite+

    00:02.1 CardBus bridge: Toshiba America Info Systems ToPIC95 (rev 07)
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
    ParErr- Stepping- SERR- FastB2B-
    Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=slow >TAbort-
    SERR- Latency: 0
    Interrupt: pin B routed to IRQ 11
    Region 0: Memory at ffdff000 (32-bit, non-prefetchable)
    Bus: primary=00, secondary=15, subordinate=15, sec-latency=0
    Memory window 1: 10c00000-10fff000
    I/O window 0: 00004800-000048ff
    I/O window 1: 00004c00-00004cff
    BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset- 16bInt+
    PostWrite+

    00:04.0 VGA compatible controller: Chips and Technologies F65550 (rev
    05) (prog-if 00 [VGA])
    Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop-
    ParErr- Stepping+ SERR- FastB2B-
    Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium
    >TAbort- SERR-
    Region 0: Memory at fe000000 (32-bit, non-prefetchable)

    15:00.0 USB Controller: NEC Corporation USB (rev 41) (prog-if 10
    [OHCI])
    Subsystem: NEC Corporation: Unknown device 1735
    Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
    ParErr- Stepping- SERR- FastB2B-
    Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium
    >TAbort- SERR-
    Interrupt: pin A routed to IRQ 0
    Capabilities: [40] Power Management version 2
    Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
    PME(D0+,D1+,D2+,D3hot+,D3cold-)
    Status: D0 PME-Enable- DSel=0 DScale=0 PME-

    15:00.1 USB Controller: NEC Corporation USB (rev 41) (prog-if 10
    [OHCI])
    Subsystem: NEC Corporation: Unknown device 1033
    Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
    ParErr- Stepping- SERR- FastB2B-
    Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium
    >TAbort- SERR-
    Interrupt: pin B routed to IRQ 0
    Capabilities: [40] Power Management version 2
    Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
    PME(D0+,D1+,D2+,D3hot+,D3cold-)
    Status: D0 PME-Enable- DSel=0 DScale=0 PME-

    15:00.2 USB Controller: NEC Corporation: Unknown device 00e0 (rev 02)
    (prog-if 20)
    Subsystem: Unknown device 1735:00e0
    Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
    ParErr- Stepping- SERR- FastB2B-
    Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium
    >TAbort- SERR-
    Interrupt: pin C routed to IRQ 0
    Capabilities: [40] Power Management version 2
    Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
    PME(D0+,D1+,D2+,D3hot+,D3cold-)
    Status: D0 PME-Enable- DSel=0 DScale=0 PME-

    {with scenrio #1, each of the usb hub interrupt pins are routed to IRQ
    11}

    == Conclusion/Comments ==

    So, I'm a little lost - they both work, but not together? I've tried
    everything I can think of.

    I would greatly appreciate any suggestions!

    Many thanks,

    Tom.

  2. Re: Portege 650ct Pcmcia - yenta vs i82365

    tja105 wrote:
    > Right, this is a bit of a wierd one.


    > I have two cards:


    > * One, no-name usb hub : cardbus
    > * One, smc wlan card : 16 bit


    > My trusty 650ct's bois is set to its PCIC/Cardbus setting.


    > They both work... ...but not together, which is what I'm trying to
    > achieve.


    > ==Scenario #1 - Yenta ==
    > The usb hub pcmcia card works well. The Wlan card doesn't
    > I'm using a 2.4.17 kernel with kernel pcmcia drivers; cardmgr 3.2.5.


    > At boot time, we have:


    > Yenta IRQ list 0000, PCI irq11
    > Socket status: 30000006
    > Yenta IRQ list 0000, PCI irq11
    > Socket status: 30000006


    I am afraid that the yenta driver may not be super smart about dealing
    with the Toshiba bridges.

    > ==Scenario #2 - i82365==
    > The wlan card works well. The pcmcia USB card doesn't
    > I'm using a 2.4.17 kernel with pcmcia 3.2.5 module drivers; cardmgr
    > 3.2.5.


    > {Meanwhile if I insert the pcmcia USB, and modprobe usb-ohci}


    > usb.c: registered new driver usbdevfs
    > usb.c: registered new driver hub
    > PCI: No IRQ known for interrupt pin A of device. Please try using
    > pci=biosirq.


    There's a way around this one, I think. If you get the latest beta
    from http://pcmcia-cs.sourceforge.net/ftp/NEW, there is a new driver
    called "dummy_cb". See "man dummy_cb" for instructions for how to set
    it up.

    -- Dave