Rodolfo Medina <[email protected]> writes: > The ethernet port of my Hyundai laptop, that used to work fine, seems to be > dead. At boot, I get the following message: > > Setting up networking.... > Configuring network interfaces...SIOCSIFADDR: No such device > eth1: ERROR while getting interface flags: No such device > SIOCSIFNETMASK: No such device > eth1: ERROR while getting interface flags: No such device > Failed to bring up eth1. > > Do you think it's a hardware problem? > > The file /etc/udev/rules.d/z25_persistent-net.rules is the following: > > > # Firewire device 00030d53255c8616 (ohci1394) > SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:03:0d:53:25:5c:86:16", > NAME="eth0" > > # PCI device 0x1039:0x0900 (sis900) > SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:03:0d:33:02:17", > NAME="eth1 > > > The command `ifconfig -a' gives the following output: > > > # ifconfig -a > eth0 Link encap:UNSPEC HWaddr > 00-03-0D-53-25-5C-86-16-00-00-00-00-00-00-00-00 > inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > lo Link encap:Local Loopback > LOOPBACK MTU:16436 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > [...] > > > , whereas it used to have also eth1: > > eth1 Link encap:Ethernet HWaddr 00:03:0D:33:02:17 > BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > Interrupt:201 Base address:0xd800 > > > > /etc/network/interfaces is the following: > > # This file describes the network interfaces available on your system > # and how to activate them. For more information, see interfaces(5). > > # The loopback network interface > auto lo > iface lo inet loopback > > auto eth1 > allow-hotplug eth1 > iface eth1 inet static > address 192.168.0.1 > netmask 255.255.255.0 > > > Please help with this issue, I need to know if the machine hardware needs to > be repaired or it is only a configuration problem.
Umarzuki Mochlis <[email protected]> writes: > you could try using any live cd (e.g. debian live cd) to see if it is the > software/hardware that are problematic Camaleón <[email protected]> writes: > (please, open a new thread if you change the thematic of the e-mail) > Review your logs. Run: "dmesg | grep eth" I was using the old thread because it's also about ethernet. Anyway, now I've started a new one as you say. With Knoppix 6.0, I ran `ifconfig -a' and got the following output: lo Link encap:Local Loopback LOOPBACK MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) "dmesg | grep eth" gives the folloing output: eth1394: eth0: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0) What should we conclude? Rodolfo -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
