Networking issue with latest kernel

[scalvert]

Hi All,
Installed FC2 with 2.6.5-1-358 kernel as per the oringal release of FC2 and all was ok. That is, the network connection to my cable modem on eth0 and the connection to my windows box on eth1 worked fine. Upgraded the kernel to 2.6.6-1-435 using the Red Hat update tool and suddenly I can´t ping the windows box. The eth0 connection to the cable modem still works ok though. When I revert to the 2.6.5-1-358 kernel the eth1 connection to the windows box is then ok. No other settings are changed, it simply works with the earlier kernel but not the later one. Any ideas??

:) :)

[Jman]

What network cards do you have? Perhaps you have a driver issue.

[robsummitt]

I have the same problem. I lost my network connectivity/card function after I upgraded the kernal.

I'm using onboard nVIdia NForce2 card. I tried installing the drivers from nVidia's website, but still no luck.

[robsummitt]

I'm having the same problem. I updated ther kernel and then lost my network connectivity.

I'm using an nForce2 motherboard with onboard nic.

[Cr0n_J0b]

I've had a ton of issues with FC2 and networking...I finally got things workign by moving cards around, but I'm still getting lots of errors...I think there is something hosed in the network code.

I'm running a Tulip card and 2 boomerang (3Com cards)

[Picomp314]

if you would compile your own kernel instead of relying upon Fedora , you would get the benefits of faster, and more personalized hardware drivers, it may seem daunting but the benefits are enormous

[Cr0n_J0b]

I tried that route, but got more confused than ever. what tools do you use to compile new kernels? I hear there are some slick GUI tools for doing it now...

I alway get confused at the end...make dep....make clean....make coffee...

[crackers]

if you would compile your own kernel instead of relying upon Fedora , you would get the benefits of faster, and more personalized hardware drivers, it may seem daunting but the benefits are enormous
Dude - recompiling the kernel is not the answer to all questions. Most folks don't want to do that, okay? The point is to diagnose the problem and find out why it's not working - typically it's a configuration issue, not the kernel.

scalvert and/or robsummitt: what does the output of /sbin/ifconfig look like? Have you tried /usr/sbin/service network restart to see if you just need to hit it again?

[robsummitt]

Dude - recompiling the kernel is not the answer to all questions. Most folks don't want to do that, okay? The point is to diagnose the problem and find out why it's not working - typically it's a configuration issue, not the kernel.

scalvert and/or robsummitt: what does the output of /sbin/ifconfig look like? Have you tried /usr/sbin/service network restart to see if you just need to hit it again?
I'm unable to run ipconfig or network restart. Both are returning a "not found error. ".

execuse my ignorance, I'm still in learning mode.

[jeru]

If it's nforce like robsummitt said.... Don't you guys have to re-install the nvidia nforce drivers with every kernel upgrade (compiled by *you* or compiled by fedora)

robsummitt, the command isn't found because /sbin is not in your (or normal users) path. You can see what is in your path by typing 'echo $PATH'. Anyways, run ifconfig and whatnot by telling it where to get it. You can also add /sbin to your path if you don't like typing all that. (or just 'su -' to get the root enviroment.... which isn't the same thing as 'su')

/sbin/ifconfig

[robsummitt]

thanks go the ifconfig working fine.

can you point me to somewhere (link) that explains compiling the nForce drivers.

Thanks

[jeru]

http://download.nvidia.com/XFree86/nforce/1.0-0274/ReleaseNotes.html

[robsummitt]

I assigned the card a static ip, restarted the network service with no problems
BUT I cannot ping the other computers on the network.

[Cr0n_J0b]

Can you post some of the output from the following commands:

/sbin/ifconfig
/sbin/route -e

that will give us a start...

[robsummitt]

Here is the output from ifconfig:

eth0 link encap: Ethernet hwaddr: 00:E0:46:C5:79:2A
inet addr: 192.168.71.105 BCAST:192.168.71.255 MASK 255.255.255.0
inet6 addr: fe80::2e0:4cff:fec5:792a/64 Scope:Link
UP BROADCAST Running MULTICAST MTU: 150 Metric: 1
Rx packets: 0 errors:0 dropped:0 overruns:0 frame:0
Tx packets: 180 errors: 0 dropped: 5 overruns: 0 carrier:0
Collisions: 0 txqueuelen: 1000

lo: Link encap: Local Loopback
inet addr: 127.0.0.1 Mask: 255.0.0.0
inet6 addr: ::1/128 SCOPE HOST
UP LOOPBACK RUNNING MTU: 16436 Metric: 1
Rx packets: 2515 errors:0 dropped: 0 overruns:0 frame:0
Tx packets: 2515 erros: 0 dropped: 0 overruns:0 carrier: 0
Collisions: 0 txqueuelen: 0
Rx bytes: 2827152 (2.6M) Tx bytes: 2827152 (2.6M)


Output from "route -e"

Dest Gateway GenMask Flags Metric Ref Use
192.168.71.0 * 255.255.255.0 U 0 0 0 eth0
169.254.0.0 * 255.255.0.0 U 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo

Thanks for all the help...

[robsummitt]

Got it working!

In my system bios I had to change the USB setting from v2.0-1.1 to only 1.1. Seems this is a bug, I did some reading and found something similar on redhat's support forums/bugzilla

Thanks for everyones help!!