Re: Can't activate network device (NIC)
From: Nico Kadel-Garcia (nkadel_at_verizon.net)
Date: 09/02/03
- Next message: Alan Connor: "Re: Spammers LUV SpamAssassin"
- Previous message: Alan Connor: "Re: Spammers LUV SpamAssassin"
- In reply to: cdstrand: "Re: Can't activate network device (NIC)"
- Next in thread: /dev/rob0: "Re: Can't activate network device (NIC)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 02 Sep 2003 03:37:23 GMT
cdstrand wrote:
> "bowmma" <msbowman@sympatico.ca> wrote in message news:<RLN3b.15915$Cg2.1295462@news20.bellglobal.com>...
>
>
>>I'm a Linux newbie and am trying to configure my Dell I4100 notebook (which
>>is dualbooted for W2000 and RHL9) to connect Linux with my DSL provider,
>>Sympatico. My NIC (3Com 3C905C-TX) is compatible with RHL9 but when I try
>>to activate the device I get the error message "Determining IP info for eth0
>>....failed" after about a minute. The NIC wasn't accepted when I first
>>installed RHL and delayed bootup while it diagnosed the interface. Is this
>>a PnP issue?
>
>
> Redhat states, as you say, on their web site this device is
> "supported". That does not mean, evidently, that they have a driver
> for it on the cd's, or, if they do, it will work with your network
> card. That is not their problem. The type problem you describe is
> well known to them as you can see by doing a search on "3Com
> 3c905c-tx" on their website as user after user has sought help for
> this and, instead of simply getting together some drivers that work,
> or telling the truth which is that 3com nic cards just don't work very
> well with linux and ought to be avoided by the user without a detailed
> technical education, they have, over the years, and have not, so far
> as I have ever been able to find, provided even simple instructions
> how to solve this problem.
3com doesn't work very well *period*. I keep seeing hardware failures
with them, find that various models refuse to release their DHCP
settings without a full power cycle under Windows as well as Linux, and
find their naming scheme for drivers to have absolutely nothing to do
with the model number of the card and they're inconsistent naming
schemes from Windows version to Windows version.
> As you may have noticed when your system was trying to load your nic
> card, Redhat thoughtfully pointed you to:
>
> http://www.scyld.com/network/vortex.html where you can begin your
> education learning how to configure the source code for a driver,
> compile it, and manually load it into your kernel. Good luck.
>
> You, or anyone else, who uses Redhat's site to determine what hardware
> to buy because Redhat "supports" it, is wasting their time, as the url
> cited above makes abundantly clear without saying so in so many words.
I've found RedHat to be pretty helpful in listing only hardware that
they *know* works, rather than oddball hand-built combinations that only
work on alternate Tuesdays if you squint really hard and beep your nose.
(I've been doing a lot of laptop installations of stuff that "someone
found a webpage that said you could install Linux" lately, for laptops
of a different model number and graphics chipsets....)
- Next message: Alan Connor: "Re: Spammers LUV SpamAssassin"
- Previous message: Alan Connor: "Re: Spammers LUV SpamAssassin"
- In reply to: cdstrand: "Re: Can't activate network device (NIC)"
- Next in thread: /dev/rob0: "Re: Can't activate network device (NIC)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
