A bit more success with FireWire I think

Booting, installing, newbie
Post Reply
Message
Author
User avatar
Béèm
Posts: 513
Joined: Sun 16 Apr 2006, 16:18
Location: Brussels

A bit more success with FireWire I think

#1 Post by Béèm »

Installed 1.0.9CE
With Nathan's testlibraw command I have now.
# testlibraw
successfully got handle
current generation number: 1
1 card(s) found
nodes on bus: 2, card name: ohci1394
using first card found: 2 nodes on bus, local ID is 0, IRM is 1

doing transactions with custom tag handler
trying to send read request to node 0... completed with value 0xd21bb098
trying to send read request to node 1... completed with value 0x1425b098

using standard tag handler and synchronous calls
trying to read from node 0... completed with value 0x2533b098
trying to read from node 1... completed with value 0x4737b098

testing FCP monitoring on local node
got fcp command from node 0 of 8 bytes: 01 23 45 67 89 ab cd ef
got fcp response from node 0 of 8 bytes: 01 23 45 67 89 ab cd ef
testing config rom stuff
get_config_rom returned 0, romsize 64, rom_version 3
here are the first 10 quadlets:
0. quadlet: 0xc8fa0404
1. quadlet: 0x34393331
2. quadlet: 0x02a200e0
3. quadlet: 0x00634000
4. quadlet: 0x5f1302b0
5. quadlet: 0x80840300
6. quadlet: 0x63400003
7. quadlet: 0x02000081
8. quadlet: 0xc083000c
9. quadlet: 0xab030600
update_config_rom returned 0

polling for leftover messages

Another machine is connected with a working 1394 interface (PCLinuxOS)

If I disconnect the cable, nothing is reported fore node 1, so I am sure through the cable both machines see each other to a certain extend.

The PCLinuxOS machine sees the 1394 device as eth2: IEEE1394 IPv4 driver (IPv4 over 1394 as per rfc 2734)

So my problem is still, that I can't attach an IP adress on the 1394 device.
The ethernet wizard doesn't see the IEEE1394 as an ethx device
The ethernet port is seen as eth0 and used to do the connection with the internet.

So if someone has a clue, it's welcome.

Post Reply