Hey all I have tried unplugging the network cable from the back of the machine and re-plugging it in, I have used a different port on my switch, which I have previously used and know it works well. Firts thing i did was ping 192.168.0.1 (my internet sharing machine), and was told that the network was unreachable. I have tried using a fixed ip address (192.168.0.5 and 255.255.255.0 subnet mask), still no joy. Network is unreachable. So, after this, I tried with the command sudo ethtool eth0, which returned with the output: glenn(a)glenn-amd1: [sudo] password for glenn: sudo:ethtool:command not found. glenn(a)glenn-amd1: This is the directory /etc/network glenn(a)glenn-amd1:~$ cd /etc glenn(a)glenn-amd1:/etc$ cd network glenn(a)glenn-amd1:/etc/network$ ls if-down.d if-post-down.d if-pre-up.d if-up.d interfaces glenn(a)glenn-amd1:/etc/network$ cat interfaces auto lo iface lo inet loopback I then tried removing the interfaces file, in the event that I could start over, but still no luck. when I run dhclient I get: glenn(a)glenn-amd1:/etc/network$ sudo dhclient Internet Systems Consortium DHCP Client V3.1.1 Copyright 2004-2008 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Listening on LPF/pan0/92:93:61:a0:d3:80 Sending on LPF/pan0/92:93:61:a0:d3:80 Listening on LPF/eth0/00:0d:87:35:aa:32 Sending on LPF/eth0/00:0d:87:35:aa:32 Sending on Socket/fallback DHCPDISCOVER on pan0 to 255.255.255.255 port 67 interval 8 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 DHCPDISCOVER on pan0 to 255.255.255.255 port 67 interval 7 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19 DHCPDISCOVER on pan0 to 255.255.255.255 port 67 interval 17 DHCPDISCOVER on pan0 to 255.255.255.255 port 67 interval 9 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 DHCPDISCOVER on pan0 to 255.255.255.255 port 67 interval 9 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14 DHCPDISCOVER on pan0 to 255.255.255.255 port 67 interval 11 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 No DHCPOFFERS received. No working leases in persistent database - sleeping. glenn(a)glenn-amd1:/etc/network$ Maybe I just have a faulty network adaptor on the motherboard. But if that was the case, wouldn't it NOT be displayed with lspci? Glenn.
Glenn Stuart Morrissey wrote:
So, after this, I tried with the command
sudo ethtool eth0, which returned with the output:
glenn(a)glenn-amd1: [sudo] password for glenn: sudo:ethtool:command not found. glenn(a)glenn-amd1:
you need to install ethtool, run the command again and post the output: sudo apt-get install ethtool Happy new year to you all, Roger
Hey all
you need to install ethtool, run the command again and post the output:
sudo apt-get install ethtool Is there a way that I can remotly download a package for a machine, since I can't browse the web with my amd machine, since the ethernet connection is down?
Glenn.
On 1/Jan/09 22:58 , "Glenn Stuart Morrissey" <gmorrissey(a)kol.co.nz> wrote:
Hey all
you need to install ethtool, run the command again and post the output:
sudo apt-get install ethtool Is there a way that I can remotly download a package for a machine, since I can't browse the web with my amd machine, since the ethernet connection is down?
You certainly can - use "-d"/"--download-only" as an argument for apt-get ... Of course, that assumes that you have a machine that is running the same release that you are trying to get going. (Failing that it is possible to download the deb files and then transport them, use dpkg to install the deb packages) As an aside - do you have any way of verifying that the link is being detected ie. Check the link light on the switch / on board NIC is working. This didn't occur to me until after Daniels email. Cheers, Wazzä
Hey Wazza on my switch, my 10/100 light is on, as is link/active and half/full duplex lights. I managed to get the ethtool package from: http://debian.mirror.inra.fr/debian/pool/main/e/ethtool/ and installed it successfully. Glenn.
Maybe I just have a faulty network adaptor on the motherboard. But if that was the case, wouldn't it NOT be displayed with lspci?
Only if it was totally dead. If you've got a spare PCI nic, try plugging that one in. It'll almost definitely appear as eth1, NOT eth0[1], so bear that in mind when testing it [1] Debian and Ubuntu create udev rules to automatically map a specific MAC address to the eth* number it was first seen with. If you remove the network card, the mapping still remains. This can be fixed, but the exact fix is distro dependant. On my Ubuntu 8.10 box, I would remove /etc/udev/rules.d/70-persistent-net.rules and reboot the system. The exact filename is different on Debian (has a different number, I think 25 from memory)
participants (4)
-
Daniel Lawson -
Glenn Stuart Morrissey -
Roger Searle -
Warren Boyd