The thing is though, if I revert back to 2.2.17 kernel, everything works fine...so its not cabling, and its not the other computers...
I will tcpdump and see if the packets are actually leaving the interface... btw when I said I can ping my IP address and my loopback address, I meant I was able to do it from the same machine as the problem...if that changes anything... James Gregory wrote: > It looks like the driver has loaded fine and that ifconfig has > attached eth0 to that driver. If you can ping the ethernet address > then the problem is quite likely not actually in your computer. Bring > the interface down and up, check cables, check other machines can ping > other machines. Try a broadcast ping and see what you can see and > maybe try tcpdump to see if the interface can see anything at all. > > HTH, > > James. > > Adam Hewitt wrote: > >> I have managed to modprobe the e100 module and that hasn helped at >> all....and I also tried the 2.4.16 kernel and I am getting the same >> error... >> >> I have attached some outputs for you to look at...if you want to see >> anything else please ask me... > -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
