Re: OT Firewire networking (was: Ethernet port dead)
On Lu, 18 oct 10, 14:06:08, Rodolfo Medina wrote: > Camaleón writes: > > > On Sun, 17 Oct 2010 15:56:08 +0200, Rodolfo Medina wrote: > > > >> Camaleón writes: > > > >>> Please, type "lspci" and put here the output, just to be sure. > >> > >> > >> I had already posted it: > >> > >> # lspci | grep -i ethernet > >> eth1394: eth0: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0) > > > > Yep, but do not "grep" it, put the full output (lspci). > > Here it is the output of `lspci': > > 00:00.0 Host bridge: Silicon Integrated Systems [SiS] 760/M760 Host (rev 03) > 00:01.0 PCI bridge: Silicon Integrated Systems [SiS] SG86C202 > 00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS963 [MuTIOL Media IO] > (rev 25) > 00:02.1 SMBus: Silicon Integrated Systems [SiS] SiS961/2 SMBus Controller > 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] > 00:02.6 Modem: Silicon Integrated Systems [SiS] AC'97 Modem Controller (rev > a0) > 00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] AC'97 > Sound Controller (rev a0) > 00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller > (rev 0f) > 00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller > (rev 0f) > 00:03.3 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller > 00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast > Ethernet (rev 91) Here's your network card. Very interesting that it didn't show up in the grep... are you aware of any differences (for example booting with a different kernel)? Could you please let us see the full output of 'dmesg'. If you are worried about the size you can use paste.debian.net Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: OT Firewire networking (was: Ethernet port dead)
Camaleón writes: > On Sun, 17 Oct 2010 15:56:08 +0200, Rodolfo Medina wrote: > >> Camaleón writes: > >>> Please, type "lspci" and put here the output, just to be sure. >> >> >> I had already posted it: >> >> # lspci | grep -i ethernet >> eth1394: eth0: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0) > > Yep, but do not "grep" it, put the full output (lspci). Here it is the output of `lspci': 00:00.0 Host bridge: Silicon Integrated Systems [SiS] 760/M760 Host (rev 03) 00:01.0 PCI bridge: Silicon Integrated Systems [SiS] SG86C202 00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS963 [MuTIOL Media IO] (rev 25) 00:02.1 SMBus: Silicon Integrated Systems [SiS] SiS961/2 SMBus Controller 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] 00:02.6 Modem: Silicon Integrated Systems [SiS] AC'97 Modem Controller (rev a0) 00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] AC'97 Sound Controller (rev a0) 00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) 00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) 00:03.3 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller 00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 91) 00:06.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) 00:09.0 CardBus bridge: O2 Micro, Inc. OZ711M1/MC1 4-in-1 MemoryCardBus Controller (rev 20) 00:09.1 CardBus bridge: O2 Micro, Inc. OZ711M1/MC1 4-in-1 MemoryCardBus Controller (rev 20) 00:09.2 System peripheral: O2 Micro, Inc. OZ711Mx 4-in-1 MemoryCardBus Accelerator 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 661/741/760/761 PCI/AGP VGA Display Adapter Thanks Rodolfo -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/878w1vpuxb@gmail.com
Re: OT Firewire networking (was: Ethernet port dead)
On Sun, 17 Oct 2010 15:56:08 +0200, Rodolfo Medina wrote: > Camaleón writes: >> Please, type "lspci" and put here the output, just to be sure. > > > I had already posted it: > > # lspci | grep -i ethernet > eth1394: eth0: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0) Yep, but do not "grep" it, put the full output (lspci). Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2010.10.17.14.00...@gmail.com
Re: OT Firewire networking (was: Ethernet port dead)
Camaleón writes: > On Sun, 17 Oct 2010 13:47:22 +0200, Rodolfo Medina wrote: > >> , so eth0 has always been a firewire device. But the device I'm using >> as an ethernet port is eth1, which now is not detected by the command >> ifconfig, nor dmesg, nor lspci. > > Please, type "lspci" and put here the output, just to be sure. I had already posted it: # lspci | grep -i ethernet eth1394: eth0: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0) Bye Rodolfo -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87iq10ly87@gmail.com
Re: OT Firewire networking (was: Ethernet port dead)
On Sun, 17 Oct 2010 13:47:22 +0200, Rodolfo Medina wrote: > , so eth0 has always been a firewire device. But the device I'm using > as an ethernet port is eth1, which now is not detected by the command > ifconfig, nor dmesg, nor lspci. Please, type "lspci" and put here the output, just to be sure. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2010.10.17.12.37...@gmail.com
Re: OT Firewire networking (was: Ethernet port dead)
Camaleón writes:
>>> But... what kind of device is that? Are you using an adapter (firewire
>>> to ethernet)? :-?
> It's like Rodolfo's ethernet device got messed in some way and the system
> now detects his ethernet connection as Firewire.
Well, 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
, so eth0 has always been a firewire device. But the device I'm using as an
ethernet port is eth1, which now is not detected by the command ifconfig, nor
dmesg, nor lspci.
Rodolfo
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87r5fp3ut1@gmail.com
Re: OT Firewire networking (was: Ethernet port dead)
On Sat, 16 Oct 2010 12:25:40 -0600, Morgan Gangwere wrote: > On Sat, 16 Oct 2010 16:15:12 + (UTC) Camaleón <> wrote: > >> But... what kind of device is that? Are you using an adapter (firewire >> to ethernet)? :-? > > the 1394 standard says that a computer which supports 1394 must also > support "1394 networking". Short end of it, if you need to move some > data between two 1394 capable computers, you use that. They act like > normal, everyday, nondescript ether ports in software, no less. I don't have it :-) Look, I have 2 firewire controllers: s...@stt008:~$ lspci | grep 1394 06:07.0 FireWire (IEEE 1394): Texas Instruments TSB82AA2 IEEE-1394b Link Layer Controller (rev 01) 11:03.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) But not their ethernet counterpart (just the "real" devices): s...@stt008:~$ dmesg | grep -i eth [6.296132] Driver 'sd' needs updating - please use bus_type methods [8.835653] Driver 'sr' needs updating - please use bus_type methods [8.939032] eth0: (PCI Express:2.5GB/s:Width x1) 00:30:48:d9:08:27 [8.971270] eth0: Intel(R) PRO/1000 Network Connection [8.989936] eth0: MAC: 7, PHY: 6, PBA No: ff-0ff [ 12.105820] r8169 Gigabit Ethernet driver 2.2LK-NAPI loaded [ 12.263452] eth1: RTL8169sb/8110sb at 0xc20002894000, 00:1d:0f:be:b6:ad, XID 1000 IRQ 20 [ 40.041511] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 40.928617] eth0: Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX [ 40.952349] eth0: 10/100 speed: disabling TSO [ 40.974738] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 47.063355] r8169: eth1: link down [ 47.086842] ADDRCONF(NETDEV_UP): eth1: link is not ready [ 53.459758] eth0: no IPv6 routers present It's like Rodolfo's ethernet device got messed in some way and the system now detects his ethernet connection as Firewire. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2010.10.17.09.57...@gmail.com
Re: OT Firewire networking (was: Ethernet port dead)
On Saturday 16 October 2010 10:57:30 Rodolfo Medina wrote: > Morgan Gangwere <0.fracta...@gmail.com> writes: > > "dmesg | grep eth" gives the folloing output: > > > > eth1394: eth0: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0) > > > > On Sat, 16 Oct 2010 16:15:12 + (UTC) Camaleón <> wrote: > >> But... what kind of device is that? Are you using an adapter > >> (firewire to ethernet)? :-? > > > > the 1394 standard says that a computer which supports 1394 must also > > support "1394 networking". Short end of it, if you need to move some > > data between two 1394 capable computers, you use that. They act like > > normal, everyday, nondescript ether ports in software, no less. > > But eth0 is not the device I'm using: the device I'm using as an ethernet > port is eth1, but it doesn't appear in dmesg nor in lspci output: this is > /etc/network/interfaces: > > 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 > > > Rodolfo If lspci does't find your ethernet controller it probably died, that happens. AFAIK lspci finds functioning hardware on the pci bus whether or not modules for devices are installed. On a laptop, options are usb>ethernet or a pcmcia card if available. -- Peace, Greg -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201010161130.05041.gomadtr...@gci.net
Re: OT Firewire networking (was: Ethernet port dead)
Morgan Gangwere <0.fracta...@gmail.com> writes: > "dmesg | grep eth" gives the folloing output: > > eth1394: eth0: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0) > On Sat, 16 Oct 2010 16:15:12 + (UTC) Camaleón <> wrote: > >> But... what kind of device is that? Are you using an adapter >> (firewire to ethernet)? :-? > > the 1394 standard says that a computer which supports 1394 must also > support "1394 networking". Short end of it, if you need to move some > data between two 1394 capable computers, you use that. They act like > normal, everyday, nondescript ether ports in software, no less. But eth0 is not the device I'm using: the device I'm using as an ethernet port is eth1, but it doesn't appear in dmesg nor in lspci output: this is /etc/network/interfaces: 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 Rodolfo -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8762x2rmn9@gmail.com
OT Firewire networking (was: Ethernet port dead)
On Sat, 16 Oct 2010 16:15:12 + (UTC) Camaleón <> wrote: > But... what kind of device is that? Are you using an adapter > (firewire to ethernet)? :-? the 1394 standard says that a computer which supports 1394 must also support "1394 networking". Short end of it, if you need to move some data between two 1394 capable computers, you use that. They act like normal, everyday, nondescript ether ports in software, no less. -- Morgan Gangwere PGP Key at http://indrora.homelinux.org/gpg_key.asc BOFH Excuse #32: Solar flares causing disk errors. signature.asc Description: PGP signature
