Hawking Fast Ethernet Cardbus 10/100 Woody ?

[cls-du@truffula.sj.ca.us]

I've got a Cardbus 10/100 NIC from Hawking.

# cardctl ident
Socket 0:
product info: "3Com", "Megahertz 3CCFEM556", "LAN + 56k Modem", ""
manfid: 0x0101, 0x0556
function: 0 (multifunction)
Socket 1:
product info: "CardBus", "Fast Ethernet", "V1.0", ""
manfid: 0x13d1, 0xab02
function: 6 (network)


Woody's Card Services doesn't recognize it.

# lspci
00:00.0 Host bridge: Intel Corp. 440BX/ZX - 82443BX/ZX Host bridge (rev 03)
00:01.0 PCI bridge: Intel Corp. 440BX/ZX - 82443BX/ZX AGP bridge (rev 03)
00:06.0 Multimedia audio controller: ESS Technology ES1978 Maestro 2E (rev 10)
00:07.0 ISA bridge: Intel Corp. 82371AB PIIX4 ISA (rev 02)
00:07.1 IDE interface: Intel Corp. 82371AB PIIX4 IDE (rev 01)
00:07.2 USB Controller: Intel Corp. 82371AB PIIX4 USB (rev 01)
00:07.3 Bridge: Intel Corp. 82371AB PIIX4 ACPI (rev 02)
00:0a.0 CardBus bridge: Texas Instruments PCI1220 (rev 02)
00:0a.1 CardBus bridge: Texas Instruments PCI1220 (rev 02)
01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage LT Pro AGP-133 (rev dc)
06:00.0 Ethernet controller: Unknown device 17b3:ab08 (rev 11)

I'm having trouble finding the right documentation on how to
get this going. Don't know which chip set is in the card.
Don't know where the manufacturer and product IDs are defined
for Card Services. Seems to be a very popular product, perhaps
under another name. Google doesn't help because Hawking
doesn't have any model identification on the thing.
In fact, the markings on it are contradictory: it says
"CardBus 10/100 Fast Ethernet PC Card" on the front
and "Fast Ethernet CardBus 10/100" on the back.

(The correct terminology is "PC Card" is the ISA-like
interface, Cardbus is the PCI-like interface, and both
are standards from an organization named PCMCIA. It
doesn't make much sense for a product to say both
"PC Card" and "Cardbus" on it. The PC Card interface isn't
fast enough for full 100BASE-T throughput, but that didn't
stop companies like 3Com from selling 10/100 PC Cards
like the 3CCFEM556.)

I've tried bf24 and my own 2.4.21. Can't load any
PCI NIC modules because 17b3 and 0x13d1 are unrecognized.
Anybody got one of these things working with Woody?
How did you do it?
TIA


Cameron



--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

[cls-du@truffula.sj.ca.us]

I wrote:

>> # cardctl ident
>> Socket 1:
>> product info: "CardBus", "Fast Ethernet", "V1.0", ""
>> manfid: 0x13d1, 0xab02
>> function: 6 (network)

Jesse Meyer wrote:

>[I've got the same card,] FCC ID of "MQ4C2K5MX"
> [...] under the 2.4 debian kernel, I have
> got the card to work, but only using the 2.4 boot floppy kernel and the
> package pcmcia-modules-2.4.18-bf2.4. The driver seems to be 'tulip_cb',
> the regular 'tulip' driver in the kernel does not seem to work.

I poked around some more. I never did get the hang of building
"Debianized" kernels; I've always used the upstream kernel source.
When I installed the current upstream pcmcia-cs, and Debian's hotplug
package, the tulip.o in my /lib/modules/2.4.21 started working!

For the record, it seems there are two ways to support PCMCIA cards.
You have to choose the kernel's internal drivers -or- the ones
that come with Dennis Hinds' pcmcia-cs.
Debian uses pcmcia-cs, but packages the driver modules separately
as pcmcia-drivers.
Jesse reports tulip_cb from there works, and I can now report
success with the tulip and mii modules from the 2.4.21 kernel.

In my case, the hotplug package was the missing piece.
(Perhaps this is a packaging issue. Maybe the Cardbus drivers
should be in their own package, with hotplug a dependency.)

The Cardbus Tulip is noticeably faster than the PCcard 3CCFEM556.
3Com discontinued the 3CCFEM556. It's too bad, because that card also
contains the best modem I ever used. The 3CCFEM656B which replaced
it uses Cardbus, but it's got a friggin' winmodem!


Cameron


--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

[Jesse Meyer]

On Sat, 02 Aug 2003, [email]cls-du@truffula.sj.ca.us[/email] wrote:

> I wrote:

> >> # cardctl ident
> >> Socket 1:
> >> product info: "CardBus", "Fast Ethernet", "V1.0", ""
> >> manfid: 0x13d1, 0xab02
> >> function: 6 (network)

>
> Jesse Meyer wrote:

> >[I've got the same card,] FCC ID of "MQ4C2K5MX"
> > [...] under the 2.4 debian kernel, I have
> > got the card to work, but only using the 2.4 boot floppy kernel and the
> > package pcmcia-modules-2.4.18-bf2.4. The driver seems to be 'tulip_cb',
> > the regular 'tulip' driver in the kernel does not seem to work.

>
> I poked around some more. I never did get the hang of building
> "Debianized" kernels; I've always used the upstream kernel source.
> When I installed the current upstream pcmcia-cs, and Debian's hotplug
> package, the tulip.o in my /lib/modules/2.4.21 started working!
>
> For the record, it seems there are two ways to support PCMCIA cards.
> You have to choose the kernel's internal drivers -or- the ones
> that come with Dennis Hinds' pcmcia-cs.
> Debian uses pcmcia-cs, but packages the driver modules separately
> as pcmcia-drivers.
> Jesse reports tulip_cb from there works, and I can now report
> success with the tulip and mii modules from the 2.4.21 kernel.

Did your card have the same FCC number? Also, what sort of laptop is
it?

I think I'll try hotplug in a bit then, I'm sick of bf kernels. :)

~ Jesse Meyer

--
icq: 34583382 / msn: [email]dasunt@hotmail.com[/email] / yim: tsunad

"We are what we pretend to be, so we must be careful about what we
pretend to be." - Kurt Vonnegut Jr : Mother Night

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)

iD8DBQE/LIqpiWRyGryG0v8RAifNAJ94rVMiv25PLmsZVnuMRy74/P+C0ACffLot
1GmQbvifrY58TFkel7z5BoE=
=cftk
-----END PGP SIGNATURE-----