PCMCIA on PowerBook G3

I tried to get the PCMCIA stuff running on a PowerBook G3/333 (Lombard) with
Linux 2.2.14 and 2.2.15, both from the pmac-stable tree.  Using pcmcia-cs-3.0.14
plus a patch I found in the mailing list, I get kernel freezes each time I
insert a cardbus card.  With vanilla pcmcia-cs-3.1.11, the system doesn't
recognise the card correctly, e.g. (from /var/log/messages):

cardmgr[284]: initializing socket 0
cardmgr[284]: unsupported card in socket 0
kernel: cs: cb_alloc(bus 1): vendor 0xffff, device 0xffff
kernel: cs: no valid ROM images found!
cardmgr[284]:   no product info available

If I type lspci -vv, I also get messages like

01:00.0 Class ffff: Illegal Vendor ID: Unknown device ffff (rev ff) (prog-if ff)
        !!! Unknown header type 7f

Maybe some parts of the bridge were not initialized correctly?  Any ideas?

Thanks for your help, Albrecht.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Albrecht Dreß wrote:

I tried to get the PCMCIA stuff running on a PowerBook G3/333 (Lombard) with
Linux 2.2.14 and 2.2.15, both from the pmac-stable tree.  Using pcmcia-cs-3.0.14
plus a patch I found in the mailing list, I get kernel freezes each time I
insert a cardbus card.  With vanilla pcmcia-cs-3.1.11, the system doesn't
recognise the card correctly, e.g. (from /var/log/messages):

cardmgr[284]: initializing socket 0
cardmgr[284]: unsupported card in socket 0
kernel: cs: cb_alloc(bus 1): vendor 0xffff, device 0xffff
kernel: cs: no valid ROM images found!
cardmgr[284]:   no product info available

If I type lspci -vv, I also get messages like

01:00.0 Class ffff: Illegal Vendor ID: Unknown device ffff (rev ff) (prog-if ff)
        !!! Unknown header type 7f

Maybe some parts of the bridge were not initialized correctly?  Any ideas?

Thanks for your help, Albrecht.

As you've sent in an earlier message you're aware of the CardBus patch.
When you apply this patch to your kernel then the CardBus is detected.
BUT as far as my experiences goes, you must have inserted the CardBus
card before boot.

I have a ethernet/modem from Xircom working.

Andreas

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Andreas Tobler wrote:

As you've sent in an earlier message you're aware of the CardBus patch.

I know...  But in this case, I would like to use the PCMCIA package with a
Adaptec 1480 scsi card (just a test, because we need scsi for tapes, and the new
PowerBooks don't have the built-in MESH any more).  Afaik, there is only a
driver which needs all the pcmcia stuff to run.

Thanks, Albrecht.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Albrecht Dreß wrote:

Andreas Tobler wrote:

quoted

As you've sent in an earlier message you're aware of the CardBus patch.

I know...  But in this case, I would like to use the PCMCIA package with a
Adaptec 1480 scsi card (just a test, because we need scsi for tapes, and the new
PowerBooks don't have the built-in MESH any more).  Afaik, there is only a
driver which needs all the pcmcia stuff to run.

What do mean exactly 'only one driver'?

The Adaptec 1480 is a CARDBUS not a PCMCIA card. It is 32 bit. When you
apply the patch from Ryuichi Oikawa then the PCI probing should give the
information further to the cb_enabler I think.
I had the same behaviour when NOT applying this patch. Then I got also
this messages:

cardmgr[284]: unsupported card in socket 0
kernel: cs: cb_alloc(bus 1): vendor 0xffff, device 0xffff
kernel: cs: no valid ROM images found!

When you look into config from /etc/pcmcia you'll see the device:
device "apa1480_cb"
  class "scsi" module "cb_enabler", "apa1480_cb"

Here the driver is integrated after the cb_enabler which is responsible
for correct notifying the CardBus Card.

I don't have experiences with scsi, but as soon as the PCI probing
works, the cardmgr should be able to tell you at least what card you
inserted.

Andreas

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/