Michael Rothwell wrote:
>
> RH6.1 almost gets it...
>
> When I tell it to load the tulip driver, I get "Lite-On 83c168 PNIC at
> 0xee00, 00a0cc282e3d, IRQ 11." This is the correct hardware address,
> according to the stickers on the thing. I cannot send or recieve data,
> however. It seems odd that it gets recognized well enough that its
> hardware address can be read, but not well enough that it can use it to
> transmit and recieve data.
This seems remarkably unlikely - perhaps coincidental. Do you have a
network card installed? Perhaps it is finding your PCI network card?
What does /proc/pci say?
What does /proc/interrupts say?
What does /proc/bus/usb/devices say?
>From the FreeBSD supported devices list:
"ADMtek Inc. AN986-based USB ethernet NICs including the following:
LinkSys USB100TX
Billionton USB100
Melco Inc. LU-ATX
D-Link DSB-650TX
SMC 2202USB
CATC USB-EL1210A-based USB ethernet NICs including the following:
CATC Netmate
CATC Netmate II
Belkin F5U111
Kawasaki LSI KU5KUSB101B-based USB ethernet NICs including the
following:
LinkSys USB10T
Entrega NET-USB-E45
Peracom USB Ethernet Adapter
3Com 3c19250
ADS Technologies USB-10BT
ATen UC10T
Netgear EA101
D-Link DSB-650
SMC 2102USB
SMC 2104USB
Corega USB-T"
So it is not tulip based at all. The AMDtek device is supported (driver
"pegasus") and an alternative pegasus driver and a CATC driver is
available from Donald Becker's site (http://blueraja.scyld.com/usb/). He
has some wierd licensing on the catc.c code.
I think someone was working on the driver for the KLSI device (maybe
even Donald), although it has become very quiet lately. But there is
enough data available to support a driver development, given the
website, the FreeBSD implementation and the pegasus.c example.
Brad
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
