On Thu, 2011-06-16 at 16:10 +0200, Cahn Roger wrote: > > Apologies if I missed someone already asking these: > > No problem! Thanks to try to help me. > > > 1. are the lights on or flashing with a cable plugged in and pinging > > something valid? > > No. They are stable >
That indicates a problem - if a packet is going out/in, the lights shouls flash > > 2. can you ping yourself (both 127.0.0.1 and the nic IP) - cable plugged > > in > > They work both (127.0.0.1 and 192.168.1.20 my desktop IP) > that would indicate the software (protocol stack) is ok > > 3. do you have IP tables installed - "iptables -vnL" and check you have > > not firewalled yourself off from the world somehow. > > Not iptables installed. ok > > > 4. set up a ping and check "dmesg" and terminal 12 (<ctrl-alt-F12>) for > > anything meaningful. > > ping to my laptop which works (192.168.0.22) fails. > In dmesg (very very long!) I didn't find anything > I could understand but this: > [ 11.002756] sky2 0000:02:00.0: eth0: enabling interface > [ 11.003194] ADDRCONF(NETDEV_UP): eth0: link is not ready > [ 11.113427] Adding 2048280k swap on /dev/sdb2. Priority:-1 extents:1 > across:2048280k > [ 14.025657] sky2 0000:02:00.0: eth0: Link is up at 100 Mbps, full > duplex, flow control rx > [ 14.026096] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready > [ 24.386040] eth0: no IPv6 routers present > normal, seeing the cable and a valid line discipline the other end > With ctrl+alt+F12 i canread this (interesting?) > Bureau ntpd_intres[3301] host name not found: 0.gentoo.pool.ntp.org > (3 other lines like this with number 2, 3, 4) > ntpd is the network time protocol daemon - its basicly complaining about no network. > > 5. as an outside chance, run "modinfo [eth_module]" - get the right > > module name from "lsmod" > > in lsmod I don't have a module eth_module > > in this comntext [ ] normally means optional or "replace this" so you need to do an lsmod, identify the module for your ethernet card (sky2?) and rum "modinfo eth_module" replacing eth_module with the real module name. > > > Next I would remove the switch and use a crossover cable to another machine and use ethtool on each end to go deeper into what the hardware/cable is doing. You can still get problems with one end being say 10Mb/s and the other running a different speed/duplex etc. I am finding that 1Ghz chips seem less than reliable in this regard to older switches that way! I also have some 4 port sun 100mhz cards that need the other end always up before powering the machine they are in on as nothing I can do once up will get the ends in sync. also try "cat /proc/net/dev" and see if that shows anything useful BillK -- William Kenworthy <bi...@iinet.net.au> Home in Perth!
