Nvidia network troubles (was:HELP ME!)
Kyrre Ness Sjobak
kyrre at solution-forge.net
Tue Mar 22 12:15:23 UTC 2005
tir, 22.03.2005 kl. 12.00 skrev Cimmo:
> ifconfig attached.
> PLEASE HELP!
> eth0 Link encap:Ethernet HWaddr 00:11:09:C8:ED:04
> inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0
> inet6 addr: fe80::211:9ff:fec8:ed04/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:8 errors:0 dropped:0 overruns:0 frame:0
> TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:1652 (1.6 KiB) TX bytes:3418 (3.3 KiB)
> Interrupt:193 Base address:0x9000
> 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:49 errors:0 dropped:0 overruns:0 frame:0
> TX packets:49 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:3592 (3.5 KiB) TX bytes:3592 (3.5 KiB)
> fedora-test-list mailing list
> fedora-test-list at redhat.com
> To unsubscribe:
>From what i can tell, your machine *has* network connectivety working -
you do get an ip, you do get a dns, and you are able to ping remote
adresses, get data from them, and get info from your router's dns cache.
Hmm... you are saying you are using nvidia's proprietary network driver
(WTF?!?), and their proprietary display driver (understandable). That
means you have a tainted kernel - and that most kernel guys will refuse
to help you, as they don't have access to the full sourcecode.
If you use the fedora shipped network driver (forcedeth?) - what happens
then? Try that driver, and use the built-in "nv" driver (yes, i know it
doesn't give any 3D), and if it doesn't work still, you have a kernel
bug (which should be reported at RH bugzilla). Or you could try to talk
nvidia's engineers into finding out what went wrong with *their* driver
(means their trouble).
It could be that:
- firefox is borked (try some other client such as links to rule out
- your network driver is borked, so it will fail on larger amounts of
data (would explain why ping, dig, and the *start* of pages in firefox
work, but not complete webpages etc.). Try to download something big (a
fedora ISO?) with wget, and see what happens. Do it from a *real*
console, sou you can see any error messages flying past.
And for god's sake: Use a more descriptive subject next time!!!
Kyrre Ness Sjøbæk
ps. i am going to be away for the rest of the week, so happy bughunting!
More information about the test