From owner-freebsd-firewire@FreeBSD.ORG Mon Sep 14 08:20:38 2009 Return-Path: Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ACE931065705 for ; Mon, 14 Sep 2009 08:20:38 +0000 (UTC) (envelope-from Gabor@Zahemszky.HU) Received: from relay02.digicable.hu (relay02.digicable.hu [92.249.128.188]) by mx1.freebsd.org (Postfix) with ESMTP id 235458FC1D for ; Mon, 14 Sep 2009 08:20:37 +0000 (UTC) Received: from [94.21.14.106] (helo=Picasso.Zahemszky.HU) by relay02.digicable.hu with esmtpa id 1Mn6nb-0003wu-L3 for ; Mon, 14 Sep 2009 10:20:35 +0200 Date: Mon, 14 Sep 2009 10:20:35 +0200 From: Zahemszky =?ISO-8859-2?Q?G=E1bor?= To: freebsd-firewire@freebsd.org 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> Organization: Zahemszky Bt. X-Mailer: Claws Mail 3.7.2 (GTK+ 2.16.6; i386-portbld-freebsd7.2) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: quoted-printable X-Original: 94.21.14.106 Subject: Re: connecting FreeBSD 7 to a DVD-recorder on FW X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Sep 2009 08:20:38 -0000 Hi! Thanks for your answer. Thu, 03 Sep 2009 15:50:36 -0700 -n Sean Bruno =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: 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: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:00:00:00:00:00 fwe0: Ethernet address: 02:00:00:00:00:00 fwip0: on firewire0 fwip0: Firewire address: 00:00:00:00:00:00:00:00 @ 0xfffe00000000, S400, maxrec 2048 sbp0: on firewire0 dcons_crom0: 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" From owner-freebsd-firewire@FreeBSD.ORG Mon Sep 14 11:06:58 2009 Return-Path: Delivered-To: freebsd-firewire@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5A0F01065694 for ; Mon, 14 Sep 2009 11:06:58 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 482F28FC14 for ; Mon, 14 Sep 2009 11:06:58 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n8EB6wOc072301 for ; Mon, 14 Sep 2009 11:06:58 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n8EB6vlJ072297 for freebsd-firewire@FreeBSD.org; Mon, 14 Sep 2009 11:06:57 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 14 Sep 2009 11:06:57 GMT Message-Id: <200909141106.n8EB6vlJ072297@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-firewire@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-firewire@FreeBSD.org X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Sep 2009 11:06:58 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/136946 firewire [fwohci] fwohci throws an"unrecoverable error" upon re o kern/136652 firewire [firewire] Firewire-attached "WD My Book 1028" does no p kern/125673 firewire [firewire] [panic] FreeBSD7 panics when kldunloading f o kern/122951 firewire [firewire] video-transfer via fwcontrol triggers a pan o kern/118093 firewire [firewire] firewire bus reset hogs CPU, causing data t p kern/114646 firewire [firewire] [patch] firewire fails after suspend/resume o kern/113785 firewire [firewire] dropouts when playing DV on firewire o kern/97208 firewire [firewire] System hangs / locks up when a firewire dis o kern/74238 firewire [firewire] fw_rcv: unknown response; firewire ad-hoc w 9 problems total.