Need an SCO 5.0.6 driver for integrated 3com 905 LAN - is there one?

[Michael Sweeden]

I have a system with an Asus A7N8X rev. 2.0 motherboard running Windows 2000
and SCO OpenServer 5.0.6. This motherboard has 2 integrated LAN ports: an
nvidia and a 3com905. I am using the 3com port under Windows 2000, but Asus
does not supply an SCO driver for it. I downloaded the 3C90X SCO driver from
3com and installed it, but I get an error when booting about "vendor ID 4318
not supported". It looks to me like I'm screwed and I'll have to install a
PCI adapter, but I wanted to check and see if anybody knew of a driver that
would work for the 3com LAN port on this motherboard. Thanks!

[Bela Lubkin]

Michael Sweeden wrote:

> I have a system with an Asus A7N8X rev. 2.0 motherboard running Windows 2000
> and SCO OpenServer 5.0.6. This motherboard has 2 integrated LAN ports: an
> nvidia and a 3com905. I am using the 3com port under Windows 2000, but Asus
> does not supply an SCO driver for it. I downloaded the 3C90X SCO driver from
> 3com and installed it, but I get an error when booting about "vendor ID 4318
> not supported". It looks to me like I'm screwed and I'll have to install a
> PCI adapter, but I wanted to check and see if anybody knew of a driver that
> would work for the 3com LAN port on this motherboard. Thanks!

That message is printed in decimal when PCI IDs are usually given in
hex. Vendor ID 4318(10) = 10DE(16) is NVidia. The driver seems to be
seeing an NVidia chip, not the 3Com chip it expects.

My guess would be that it is in fact being pointed at the wrong chip.

Run:

hw -v -r pci > /tmp/pci

Each entry in the output is 30-50 lines long. If it's true that the
motherboard has two NICs, you should see two entries that have
"ClassCode: 0x020000 Ethernet controller". One should have a VendorId
of "10be (Tsenglabs International Co.)" (which I guess has evolved into
NVidia?). The other should have a VendorId of "10b7 (3Com
Corporation)".

Pick out the DeviceNum, Function, Bus numbers from the 3Com ethernet
entry. Now run `scoadmin network` and reconfigure the 3C90X driver.
There is a way to tie it to a specific PCI bus/device/function -- I
forget if you have to go into "Advanced" setup or what. Type in the
numbers from `hw`. Now you should be able to relink, reboot, and have
the NIC recognized.

If this doesn't work, please post the `hw` output for the two NICs
(only).

>Bela<

[Michael Sweeden]

That took care of it - thank you very much!
Michael

"Bela Lubkin" <belal@sco.com> wrote in message
news:20030805184236.GG24551@sco.com...

> Michael Sweeden wrote:
>

> > I have a system with an Asus A7N8X rev. 2.0 motherboard running Windows

2000

> > and SCO OpenServer 5.0.6. This motherboard has 2 integrated LAN ports:

an

> > nvidia and a 3com905. I am using the 3com port under Windows 2000, but

Asus

> > does not supply an SCO driver for it. I downloaded the 3C90X SCO driver

from

> > 3com and installed it, but I get an error when booting about "vendor ID

4318

> > not supported". It looks to me like I'm screwed and I'll have to install

a

> > PCI adapter, but I wanted to check and see if anybody knew of a driver

that

> > would work for the 3com LAN port on this motherboard. Thanks!

>
> That message is printed in decimal when PCI IDs are usually given in
> hex. Vendor ID 4318(10) = 10DE(16) is NVidia. The driver seems to be
> seeing an NVidia chip, not the 3Com chip it expects.
>
> My guess would be that it is in fact being pointed at the wrong chip.
>
> Run:
>
> hw -v -r pci > /tmp/pci
>
> Each entry in the output is 30-50 lines long. If it's true that the
> motherboard has two NICs, you should see two entries that have
> "ClassCode: 0x020000 Ethernet controller". One should have a VendorId
> of "10be (Tsenglabs International Co.)" (which I guess has evolved into
> NVidia?). The other should have a VendorId of "10b7 (3Com
> Corporation)".
>
> Pick out the DeviceNum, Function, Bus numbers from the 3Com ethernet
> entry. Now run `scoadmin network` and reconfigure the 3C90X driver.
> There is a way to tie it to a specific PCI bus/device/function -- I
> forget if you have to go into "Advanced" setup or what. Type in the
> numbers from `hw`. Now you should be able to relink, reboot, and have
> the NIC recognized.
>