Re: 3C509 problems

[Clay Jackson <clayj nwlink com>]

I had the same problem on one machine; but not on another.

The only significant difference I could find was that the machine I had the
problem on had an AWARD BIOS and the other was AMI.  I suspect the root of the
problem (at least in my case) is/was the "Plug 'n Pray" initialization in the
BIOS.  To solve mine, not only did I have to do the insmod bit; but also run
the DOS 3Com configuration program.

Clay Jackson


Dave Brockman wrote:

> Art Ross wrote:
> >
> > I've been using RH Linux for a couple years now.   Now I'm beginning a
> > rollout of Linux in the physics department.  We began this process with
> > RH6.0 which has no problems recognizing the 3C509 NICs.  When we
> > conducted fresh RH6.1 and RH6.2 beta installs, these cards are not
> > recognized in the install.  Unfortunately, with my busy schedule I've
> > worked around this problem by doing RH6.0 fresh installs and then
> > upgrading to the RH6.1 or RH6.2beta versions.  The cards are recognized
> > by the RH6.0 install and continue to work after the upgrade.
> >   Could someone tell me what is happening?  Is there simply a module for
> > the RH6.0 that properly handles the 3C509 which isn't present in the
> > RH6.1 and RH6.2 beta versions?  I'm reasonably familiar with RH but
> > haven't tried kernel configurations and compilations to try and build a
> > fix.
> >   Thanks in advance,
> >   Art
> >
> > --
> > To unsubscribe: mail redhat-install-list-request redhat com with
> > "unsubscribe" as the Subject.
>
> I've got the same problem. I sent the RedHat support people an email
> about it but haven't got a reply yet. Meanwhile, I just do an insmod
> 3c509 and ifup eth0 everytime I boot. I suppose I should add those lines
> to a script somewhere but I'm not sure which one. If I get an answer
> from RedHat I'll post it.
>
> **************************
>   Dave Brockman/Portable
>  http://www.oz.net/~daveb
> **************************
>
> --
> To unsubscribe: mail redhat-install-list-request redhat com with
> "unsubscribe" as the Subject.