Motherboard Network Interface?

I have a Linux box based on an Intel 82810 motherboard, that has been
doing me good service for a couple of years or so. (I 'acquired' the
box when someone else threw it out and installed RedHat 7.1 (Linux 2.4.2)
on it, so I don't have any H/W docs.)

I plugged in a couple of NICs (RTL8139s) to handle my local 'network'
and they work fine -- seen by Linux with no trouble. However, there
seems to be a network interface on the motherboard as well, and Linux
doesn't see this at all.

I've reached a point where it would be nice to have yet one more
connection, so has anyone any idea what I'd need to do for Linux
to recognize the motherboard port? Find a driver?

TIA,
-- Pete --


--
================================================== ==========================
The address in the header is a Spam Bucket -- don't bother replying to it...
(If you do need to email, replace the account name with my true name.)

On Sep 22, 2:14 pm, neverl...@jwgibbs.cchem.berkeley.edu (Pete) wrote:
> I have a Linux box based on an Intel 82810 motherboard, that has been
> ...
> connection, so has anyone any idea what I'd need to do for Linux
> to recognize the motherboard port? Find a driver?

Is it turned on in the BIOS? If it is, and is working, `lspci` will
see it even if you don't load a driver for it. Can you locate the chip
on the mobo and read the ID?

In article <(E-Mail Removed) om>,
Nexus7 <(E-Mail Removed)> wrote:
>On Sep 22, 2:14 pm, neverl...@jwgibbs.cchem.berkeley.edu (Pete) wrote:
>> I have a Linux box based on an Intel 82810 motherboard, that has been
>> ...
>> connection, so has anyone any idea what I'd need to do for Linux
>> to recognize the motherboard port? Find a driver?
>
>Is it turned on in the BIOS? If it is, and is working, `lspci` will
>see it even if you don't load a driver for it. Can you locate the chip
>on the mobo and read the ID?

Ackk -- you got in before I could post my retraction... (:-/)
I immediately remembered that I had intended to check the BIOS, but
had forgotten to do so before posting! Of course, you're right --
it was simply disabled.

It is now visible to the OS, but still inactive. I'll have to
set up another ethn.

Thanks,
-- Pete --

>
>


--
================================================== ==========================
The address in the header is a Spam Bucket -- don't bother replying to it...
(If you do need to email, replace the account name with my true name.)

Pete wrote:
> I have a Linux box based on an Intel 82810 motherboard, that has been
> doing me good service for a couple of years or so. (I 'acquired' the
> box when someone else threw it out and installed RedHat 7.1 (Linux 2.4.2)
> on it, so I don't have any H/W docs.)
>
> [snip]


Of course, if the hardware is newer than RH7.1, then enabling the BIOS
setting isn't going to do any good, either.

If you're committed to old distros with the 2.4 kernel, you might see if
FC1 does any better.

In article <ikjJi.58$(E-Mail Removed)>,
Allen Kistler <(E-Mail Removed)> wrote:
>Pete wrote:
>> [snip]
>
>Of course, if the hardware is newer than RH7.1, then enabling the BIOS
>setting isn't going to do any good, either.
Nahh, it's fine now. [Doubt that the h/w is newer than just about
anything...!]
>
>If you're committed to old distros with the 2.4 kernel, you might see if
>FC1 does any better.
I'm more committed to avoiding updates whenever possible. (:-))

Cheers,
-- Pete --

--
================================================== ==========================
The address in the header is a Spam Bucket -- don't bother replying to it...
(If you do need to email, replace the account name with my true name.)

Pete wrote:

> In article <ikjJi.58$(E-Mail Removed)>,
> Allen Kistler <(E-Mail Removed)> wrote:
>>Pete wrote:
>>> [snip]
>>
>>Of course, if the hardware is newer than RH7.1, then enabling the BIOS
>>setting isn't going to do any good, either.
> Nahh, it's fine now. [Doubt that the h/w is newer than just about
> anything...!]
>>
>>If you're committed to old distros with the 2.4 kernel, you might see if
>>FC1 does any better.
> I'm more committed to avoiding updates whenever possible. (:-))
>
> Cheers,
> -- Pete --
>
I had a similar problem with a current distro and a very new mobo. The
onboard NIC was detected, but wouldn't work properly. I simply use my old
NICs. If you have a spare expansion slot, that may be the way to go. I
haven't needed to look for cards with two sockets, but certainly the PCB
for only one is small enough.

Doug.
--
Husbands are like the fire on the hearth - likely to go out if left
unattended.
- W.G.P.