On Wed, 2008-08-27 at 12:00 +0530, Sadaruwan Samaraweera wrote: > Hi, > > Yes I know what your saying ok! I didn't ask him any descent question > but I gave a solution based on my experience. So why hell r u guy's > coming after me and as you said in the world of IT there are lot of > perhaps OK buddy. Yeesh. Look - I'm not starting to start a flamewar here. I'm just saying that given the little information that was given, it would be prudent to have the OP give more before catch-all answers are given. I understand that your solution worked for you, but how would any of us know that they're experiencing the same problem as you did? Oh - and incidentally, the proper "Red Hat" way to do this (trust me on this one - I used to work for Red Hat, have two RHCE certs, and have been a sysadmin for over 15 years) would be to get more info before changing out network drivers. Replacing stock parts of the OS is the *FASTEST* way to have RH support say "we don't support you". Now, knowing that this is CentOS, things don't quite work that way here. But the general case still applies. Stick with stock as much as you can until you can demonstrably prove that it's broken and put in a workaround until the "correct" solution is found. That's the easiest way to get help on this list. (And, I suspect, many others...) Just look at the recent discussions on CPAN (shudder) and how it can really crap up a system based upon RPMs... -I