Date: Mon, 14 Sep 2009 10:20:35 +0200 From: Zahemszky =?ISO-8859-2?Q?G=E1bor?= <Gabor@Zahemszky.HU> To: freebsd-firewire@freebsd.org Subject: Re: connecting FreeBSD 7 to a DVD-recorder on FW Message-ID: <20090914102035.4da8d30c@Picasso.Zahemszky.HU> In-Reply-To: <1252018236.2779.9.camel@Lappy> References: <20090903204250.765c7bca@Picasso.Zahemszky.HU> <1252018236.2779.9.camel@Lappy>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi!
Thanks for your answer.
Thu, 03 Sep 2009 15:50:36 -0700 -n
Sean Bruno <sean.bruno@dsl-only.net> =EDrta:
> On Thu, 2009-09-03 at 20:42 +0200, Zahemszky G=E1bor wrote:
> > Hi!
> >=20
> > I've got some DV files (grabbed from a Pana-camera, with iMovie -
> > from iLife - on a Mac). In my laptop I have an PCMCIA based
> > FW-card, so I'd like to transfer these files to my DVD-recorder's
> > disk, which has DV-IN connector on it. I connected my machine with
> > a DV-cable to my recorder, set up the recorder to use the DV
> > connector as a source, and tried the "fwcontrol -S myfile.dv"
> > command. fwcontrol printed numbers 1234... and so on, and after
> > about a minute, (it was the length of the DV-file) it stopped. But
> > the dvd-recorder didn't see any data on the DV-IN line.
>=20
> Can you point me to the model/make of the DVD recorder? =20
It's a German, UMax-build "Yamada DVR-9300HX HDD and DVD-recorder"
machine.
> It looks like
> you connected your DVD recorder to your FreeBSD machine. If that is
> the case, can you check your system dmesg when you plug in the DVD
> recorder?
Here you are. I plugged my PCMCIA FW-card, connected the cable,
switched on the DVR, switched off and switched on again.
=3D=3D=3D
drm0: [ITHREAD]
cardbus0: Expecting link target, got 0xff
fwohci0: <NEC uPD72873> mem
0xe4205000-0xe4205fff,0xe4206000-0xe42060ff,0xe4207000-0xe42070ff irq
18 at device 0.0 on cardbus0 fwohci0: [FILTER] fwohci0: OHCI version
1.10 (ROM=3D1) fwohci0: No. of Isochronous channels is 4.
fwohci0: EUI64 00:00:00:00:00:00:00:00
fwohci0: Phy 1394a available S400, 2 ports.
fwohci0: Link S400, max_rec 2048 bytes.
firewire0: <IEEE1394(FireWire) bus> on fwohci0
fwe0: <Ethernet over FireWire> on firewire0
if_fwe0: Fake Ethernet address: 02:00:00:00:00:00
fwe0: Ethernet address: 02:00:00:00:00:00
fwip0: <IP over FireWire> on firewire0
fwip0: Firewire address: 00:00:00:00:00:00:00:00 @ 0xfffe00000000,
S400, maxrec 2048 sbp0: <SBP-2/SCSI over FireWire> on firewire0
dcons_crom0: <dcons configuration ROM> on firewire0
dcons_crom0: bus_addr 0x7db04000
fwohci0: Initiate bus reset
fwohci0: BUS reset
fwohci0: node_id=3D0xc000ffc0, gen=3D1, CYCLEMASTER mode
firewire0: 1 nodes, maxhop <=3D 0, cable IRM =3D 0 (me)
firewire0: bus manager 0 (me)
cardbus0: Expecting link target, got 0xff
fwohci0: BUS reset
fwohci0: node_id=3D0xc000ffc1, gen=3D2, CYCLEMASTER mode
firewire0: 2 nodes, maxhop <=3D 1, cable IRM =3D 1 (me)
firewire0: bus manager 1 (me)
fwohci0: BUS reset
fwohci0: node_id=3D0x8000ffc0, gen=3D3, non CYCLEMASTER mode
firewire0: 2 nodes, maxhop <=3D 1, cable IRM =3D 1
fwohci0: BUS reset
fwohci0: node_id=3D0xc000ffc1, gen=3D4, CYCLEMASTER mode
firewire0: 2 nodes, maxhop <=3D 1, cable IRM =3D 1 (me)
firewire0: bus manager 1 (me)
Unknown service addr 0xffff:0xf0000900 RREQQ(4) src=3D0xffc0 data=3D1d051284
firewire0: New S100 device ID:000e3a0000000000
fwohci0: BUS reset
fwohci0: node_id=3D0xc000ffc1, gen=3D5, CYCLEMASTER mode
firewire0: 2 nodes, maxhop <=3D 1, cable IRM =3D 1 (me)
firewire0: bus manager 1 (me)
Unknown service addr 0xffff:0xf0000900 RREQQ(4) src=3D0xffc0 data=3Daf141284
fwohci0: BUS reset
fwohci0: node_id=3D0xc000ffc1, gen=3D6, CYCLEMASTER mode
firewire0: 2 nodes, maxhop <=3D 1, cable IRM =3D 1 (me)
firewire0: bus manager 1 (me)
Unknown service addr 0xffff:0xf0000900 RREQQ(4) src=3D0xffc0 data=3D25201284
bge0: link state changed to UP
cpu0: Cx states changed
fwohci0: BUS reset
fwohci0: node_id=3D0xc000ffc0, gen=3D7, CYCLEMASTER mode
firewire0: 1 nodes, maxhop <=3D 0, cable IRM =3D 0 (me)
firewire0: bus manager 0 (me)
acpi_tz0: _CRT value is absurd, ignored (256.0C)
acpi_tz0: _CRT value is absurd, ignored (256.0C)
fwohci0: BUS reset
fwohci0: node_id=3D0x8000ffc0, gen=3D8, non CYCLEMASTER mode
firewire0: 2 nodes, maxhop <=3D 1, cable IRM =3D 0 (me)
firewire0: root node is not cycle master capable
firewire0: bus manager 0 (me)
fwohci0: too many cycle lost, no cycle master presents?
fwohci0: BUS reset
fwohci0: node_id=3D0xc000ffc1, gen=3D9, CYCLEMASTER mode
firewire0: 2 nodes, maxhop <=3D 1, cable IRM =3D 1 (me)
firewire0: bus manager 1 (me)
fwohci0: BUS reset
fwohci0: node_id=3D0xc000ffc1, gen=3D10, CYCLEMASTER mode
firewire0: 2 nodes, maxhop <=3D 1, cable IRM =3D 1 (me)
firewire0: bus manager 1 (me)
Unknown service addr 0xffff:0xf0000900 RREQQ(4) src=3D0xffc0 data=3D63c41284
fwohci0: BUS reset
fwohci0: node_id=3D0xc000ffc1, gen=3D11, CYCLEMASTER mode
firewire0: 2 nodes, maxhop <=3D 1, cable IRM =3D 1 (me)
firewire0: bus manager 1 (me)
Unknown service addr 0xffff:0xf0000900 RREQQ(4) src=3D0xffc0 data=3Df6d31284
fwohci0: BUS reset
fwohci0: node_id=3D0xc000ffc1, gen=3D12, CYCLEMASTER mode
firewire0: 2 nodes, maxhop <=3D 1, cable IRM =3D 1 (me)
firewire0: bus manager 1 (me)
Unknown service addr 0xffff:0xf0000900 RREQQ(4) src=3D0xffc0 data=3Dacde1284
acpi_tz0: _CRT value is absurd, ignored (256.0C)
fwohci0: Initiate bus reset
fwohci0: BUS reset
fwohci0: node_id=3D0xc000ffc1, gen=3D13, CYCLEMASTER mode
firewire0: 2 nodes, maxhop <=3D 1, cable IRM =3D 1 (me)
firewire0: bus manager 1 (me)
Unknown service addr 0xffff:0xf0000900 RREQQ(4) src=3D0xffc0 data=3Dbf201284
acpi_tz0: _CRT value is absurd, ignored (256.0C)
=3D=3D=3D
And the output of fwcontrol -r -t:
$ fwcontrol -r -t
crc_len: 4 generation:17 node_count:2 sid_count:2
id link gap_cnt speed delay cIRM power port0 port1 port2 ini more
00 1 5 S100 0 1 0W - P 0 0
01 1 5 S400 0 1 -1W C - 1 0
$
=3D=3D=3D
> > - what does the information mean in an "fwcontrol -t" output? Eg,
> > like
>=20
> fwcontrol -t is the "topology map" it lists information about
> speeds(S400/S800), connections and IDs. The man page for fwcontrol
> explains a lot of this.
I have this information about it (a 7.X-machine with csup-ped and built
yesterday):
-t Show the topology map.
And no other information. So I don't know, what the flags C or P in the
port-column means, and I didn't know (now, I know it), that the ID
(with 2 numbers) are the same, that the node. It's OK. But:
> The node "name" is the "id" field from fwcontrol -t. It's a number,
> like 0, 1 or 2
My problem is: after the previous fwcontrol output (which showed me,
that I have a node with ID: 00 and another node with ID: 01, I cannot
ask anything from these nodes:
# fwcontrol -n 0
fwcontrol: no such node 0.
# fwcontrol -c 1
fwcontrol: no such node 1.
# fwcontrol -c 00
fwcontrol: no such node 0.
# fwcontrol -c 01
fwcontrol: no such node 1.
????
> I am worried about the "speed" of the unit that shows up as "S100".
> That's the minimum speed, and with modern FW components usually means
> that something failed in negotiation. =20
Can I switch on some debugging (only) about the FW?
> I know of one bug (fixed in version > 8.0) that will show up IF an
(I hope, I can switch to 8.0 in one ot two month.)
> S800 capable device is connected to a S400 device via one of it's
> S800 ports. If you can connect both ends to S400 ports, it would work
> around that problem.
I don't think, this is my problem, as tt (the DVR) has only one
FW-connector port. (I didn't find any information about it's HW - is
it an S400- or an S800-capable machine.)
Thanks,
Zahy < Gabor at Zahemszky dot HU >
--=20
#!/bin/ksh
Z=3D'21N16I25C25E30, 40M30E33E25T15U!';
IFS=3D' ABCDEFGHIJKLMNOPQRSTUVWXYZ ';
set -- $Z;for i;{ [[ $i =3D ? ]]&&print $i&&break;
[[ $i =3D ??? ]]&&j=3D$i&&i=3D${i%?};
typeset -i40 i=3D8#$i;print -n ${i#???};
[[ "$j" =3D ??? ]]&&print -n "${j#??} "&&j=3D;typeset +i i;};
IFS=3D' 0123456789 ';set -- $Z;for i;{ [[ $i =3D , ]]&&i=3D2;
[[ $i =3D ?? ]]||typeset -l i;j=3D"$j $i";typeset +l i;};print "$j"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090914102035.4da8d30c>