Networking Forums

Networking Forums > Computer Networking > Linux Networking > ΙΕΕΕ1394 networking TCP/IP

Reply
Thread Tools Display Modes

ΙΕΕΕ1394 networking TCP/IP

 
 
tkonto@gmail.com
Guest
Posts: n/a

 
      10-24-2007, 12:28 PM
Hi,

I have AMDX2 on a Gigabyte M/B, Centos5, Kernel 2.6.18-8.1.14-
el5.centos.plus and on board Firewire

with modprobe I load ieee1394, ohci1394 and raw1394 modules.

I also try to load "modprobe eth1394 eth1" but nothing happens.

The kernel reports that the IEEE1394 modules are loaded and the kernel
reports that the root node has been added.

How can I use firewire as ethernet?

Thank you.

 
Reply With Quote
 
 
 
 
tkonto@gmail.com
Guest
Posts: n/a

 
      10-24-2007, 06:18 PM
On Oct 24, 3:28 pm, tko...@gmail.com wrote:
> Hi,
>
> I have AMDX2 on a Gigabyte M/B, Centos5, Kernel 2.6.18-8.1.14-
> el5.centos.plus and on board Firewire
>
> with modprobe I load ieee1394, ohci1394 and raw1394 modules.
>
> I also try to load "modprobe eth1394 eth1" but nothing happens.
>
> The kernel reports that the IEEE1394 modules are loaded and the kernel
> reports that the root node has been added.
>
> How can I use firewire as ethernet?
>
> Thank you.


Some more info:

dmesg:
ieee1394: Node added: ID:BUS[0-00:1023] GUID[001a4d0000e0733c]
ieee1394: Node changed: 0-00:1023 -> 0-01:1023
ieee1394: Node changed: 0-01:1023 -> 0-00:1023
ieee1394: Node suspended: ID:BUS[0-00:1023] GUID[001a4d0000e0733c]
ieee1394: Node changed: 0-00:1023 -> 0-01:1023
ieee1394: Node changed: 0-01:1023 -> 0-00:1023
ieee1394: The root node is not cycle master capable; selecting a new
root node and resetting...

[root@tweety1 ~]# lsmod | grep 1394
raw1394 60785 0
ohci1394 67865 0
ieee1394 394041 2 raw1394,ohci1394

[root@tweety1 ~]# lspci -vv
..........................
01:0e.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23
IEEE-1394a-2000 Controller (PHY/Link) (prog-if 10 [OHCI])
Subsystem: Giga-byte Technology Unknown device 1000
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR-

Latency: 32 (500ns min, 1000ns max), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 201
Region 0: Memory at f5004000 (32-bit, non-prefetchable)
[size=2K]
Region 1: Memory at f5000000 (32-bit, non-prefetchable)
[size=16K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME+



 
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
1394 connection Mike Wireless Networks 5 10-30-2006 02:43 AM
1394 connection Andy Home Networking 1 06-01-2006 05:58 PM
1394 to USB Fuzzy Wuzzy Network Routers 3 03-01-2005 01:39 PM
IEEE 1394 Larry Thompson Windows Networking 4 01-04-2004 04:34 AM
IEEE 1394 Firewire Heather Windows Networking 0 11-12-2003 08:34 PM



1 2 3 4 5 6 7 8 9 10 11