On Thu, 7 Dec 2000, Janet Sullivan wrote:
> Christopher Shumway wrote:
>
> > The Intelligent Server Adapter has a PCI ID of 0x5201. The driver code,
> > /usr/src/sys/pci/if_fxpreg.h defines the device ID for the i82557 as
> > 0x1030, which is of course not what this partitular card is.
> >
> > One idea would be to edit if_fxpreg.h and replace this line:
> >
> > #define FXP_DEVICEID_i82559 0x1030 /* New 82559 device id.. */
> >
> > With this line:
> >
> > #define FXP_DEVICEID_i82559 0x5201 /* New 82559 device id.. */
> >
> > and then recompile a kernel.
> >
> > It *may* Just Work[tm].
>
> Unfortunately, it didn't. As soon as I tried to use ifconfig to give
> the card an ip address, it locked the machine up solid. Upon reboot,
> here is what ifconfig -a reports (fxp0 is the Intelligent Server
> Adapter, fxp1 is an i82558).
>
> ifconfig snippit:
>
> fxp0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
> ether 00:00:00:00:00:00
> media: manual
> supported media: manual
Ick. It appears this card is just diffrent enough that the fxp driver
doesn't understand it.
> fxp1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> inet 192.168.23.4 netmask 0xfffffff8 broadcast 192.168.23.7
> ether 00:a0:c9:a0:ff:a4
> media: 100baseTX <full-duplex> status: active
> supported media: autoselect 100baseTX <full-duplex> 100baseTX
> 10baseT/UTP <full-duplex> 10baseT/UTP
>
>
> dmesg snippit:
>
> fxp0: <Intel InBusiness 10/100 Ethernet> mem 0xe1000000-0xe11fffff irq 9
> at devi
> ce 18.1 on pci0
> fxp0: Ethernet address 00:00:00:00:00:00
> fxp1: <Intel Pro 10/100B/100+ Ethernet> port 0xe800-0xe81f mem
> 0xe1200000-0xe12f
> ffff,0xe1300000-0xe1300fff irq 3 at device 19.0 on pci0
> fxp1: Ethernet address 00:a0:c9:a0:ff:a4
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-stable" in the body of the message
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
