From bugmaster at FreeBSD.org Mon Jun 1 11:06:52 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jun 1 11:07:54 2009 Subject: Current problem reports assigned to freebsd-firewire@FreeBSD.org Message-ID: <200906011106.n51B6nP8021038@freefall.freebsd.org> 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 -------------------------------------------------------------------------------- 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 7 problems total. From freebsd at chthonic.com Mon Jun 8 01:41:40 2009 From: freebsd at chthonic.com (Joe A.) Date: Mon Jun 8 01:42:12 2009 Subject: Failure to pull DV from Panasonic PV-GS320 Message-ID: <20090608012539.GA1964@panix.com> [NB: I am not subscribed to the list; please Cc: me. Thanks] Greetings... In September 2008, I was able to do this on FreeBSD 7.0: fwcontrol -R mini.dv I'd see this: Detected DV format on input. (EAGAIN) - push 'Play'? (EAGAIN) - push 'Play'? NTSC 012345678901234567890123456789 and eventually obtain a dv file named mini.dv. At that time, and now, I used a VIA VT6306. However, it now fails: fwcontrol -R mini.dv fwcontrol: detect_recv_fn: ioctl FW_SSTBUF: Bad file descriptor And I am unable to retrieve the DV from the tape. Grasping at straws, I tried this: sysctl hw.firewire.try_bmr=0 fwcontrol -r No joy; failures continued. As far as I know, the only thing different is the upgrade to 7.1 that I had to undertake, due to EOL of 7.0. Is this a problem, known or new, or PEBKAC? I have this on the motherboard; but it also fails: fwohci0@pci0:2:1:0: class=0x0c0010 card=0x2a36103c chip=0x581111c1 rev=0x70 hdr=0x00 vendor = 'Lucent/Agere Systems (Was: AT&T MicroElectronics)' device = 'FW322 1394A PCI PHY/Link Open Host Ctrlr I/F' class = serial bus subclass = FireWire As of June 7, I see these: fwcontrol -t crc_len: 4 generation:5 node_count:2 sid_count:2 id link gap_cnt speed delay cIRM power port0 port1 port2 ini more 00 1 44 S400 0 1 0W P - 0 0 01 1 44 S100 0 1 0W C 1 0 fwcontrol -c 0 first quad: 0x04327a95 info_len=4 crc_len=50 crc=0x7a95(OK) bus_name: 0x31333934 irmc:1 cmc:1 isc:1 bmc:1 pmc:0 cyc_clk_acc:100 max_rec:10 max_rom:0 generation:3 link_spd:2 EUI64: 00-11-d8-00-00-e9-3b-e5 root_directory: len=0x0006(6) crc=0x8a3e(OK) 0c(I:0c) 0083c0 node_capabilities: 03(I:03) acde48 module_vendor_ID: 81(L:01) 000004 text_leaf: len=7 crc=0x82ed(OK) FreeBSD Project 04(I:04) 0ab248 hardware_version: 81(L:01) 00000a text_leaf: len=9 crc=0xd5f4(OK) d1(D:11) 000013 unit_directory: len=8 crc=0x83a4(OK) 12(I:12) acde48 unit_spec_ID: 81(L:01) 000007 text_leaf: len=5 crc=0xec03(OK) FreeBSD 13(I:13) 64636f unit_sw_version: 81(L:01) 00000b text_leaf: len=5 crc=0xc6ec(OK) dcons 3a(I:3a) 000001 unit_characteristics: 3b(I:3b) 264000 command_set_revision: 3c(I:3c) 000000 firmware_revision: 3d(I:3d) 8cf740 reconnect_timeout: fwcontrol -c 1 first quad: 0x0404d64e info_len=4 crc_len=4 crc=0xd64e(OK) bus_name: 0x31333934 irmc:1 cmc:1 isc:1 bmc:0 pmc:0 cyc_clk_acc:100 max_rec:4 max_rom:0 generation:0 link_spd:0 EUI64: 00-80-45-80-11-94-f5-f6 root_directory: len=0x0007(7) crc=0x0270(OK) 03(I:03) 008045 module_vendor_ID: 81(L:01) 00000b text_leaf: len=5 crc=0x508c(OK) Panasonic 17(I:17) 803337 model_ID: 81(L:01) 000012 text_leaf: len=5 crc=0x483a(OK) PV-GS320 0c(I:0c) 0083c0 node_capabilities: 8d(L:0d) 00000d unknown: len=2 crc=0x0a3f(OK) d1(D:11) 000001 unit_directory: len=4 crc=0x1f4e(OK) 12(I:12) 00a02d unit_spec_ID: 13(I:13) 010001 unit_sw_version: AV/C 17(I:17) 803337 model_ID: 81(L:01) 00000a text_leaf: len=5 crc=0x483a(OK) PV-GS320 >From pre-September 2008, as I was learning to manipulate the DV camera: fwcontrol -t crc_len: 3 generation:1 node_count:1 sid_count:1 id link gap_cnt speed delay cIRM power port0 port1 port2 ini more 00 1 63 S400 0 1 15W - - - 1 0 fwcontrol -c 0 first quad: 0x04167e69 info_len=4 crc_len=22 crc=0x7e69(OK) bus_name: 0x31333934 irmc:1 cmc:1 isc:1 bmc:1 pmc:0 cyc_clk_acc:100 max_rec:10 max_rom:0 generation:2 link_spd:2 EUI64: 00-11-06-66-00-00-03-12 root_directory: len=0x0005(5) crc=0xf64b(OK) 0c(I:0c) 0083c0 node_capabilities: 03(I:03) acde48 module_vendor_ID: 81(L:01) 000003 text_leaf: len=7 crc=0x82ed(OK) FreeBSD Project 04(I:04) 093378 hardware_version: 81(L:01) 000009 text_leaf: len=3 crc=0x0000(OK) >From dmesg about the firewire card: fwohci0: port 0xa000-0xa07f mem 0xfa010000-0xfa0107ff irq 7 at device 2.0 on pci2 fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:11:06:66:00:00:03:12 fwohci0: Phy 1394a available S400, 3 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 From bugmaster at FreeBSD.org Mon Jun 8 11:06:52 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jun 8 11:08:01 2009 Subject: Current problem reports assigned to freebsd-firewire@FreeBSD.org Message-ID: <200906081106.n58B6psE020605@freefall.freebsd.org> 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 -------------------------------------------------------------------------------- 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 7 problems total. From sean.bruno at dsl-only.net Mon Jun 8 21:36:24 2009 From: sean.bruno at dsl-only.net (Sean Bruno) Date: Mon Jun 8 21:36:30 2009 Subject: Failure to pull DV from Panasonic PV-GS320 In-Reply-To: <20090608012539.GA1964@panix.com> References: <20090608012539.GA1964@panix.com> Message-ID: <1244496981.6095.8.camel@localhost.localdomain> On Sun, 2009-06-07 at 21:25 -0400, Joe A. wrote: > [NB: I am not subscribed to the list; please Cc: me. Thanks] > > > Greetings... > > In September 2008, I was able to do this on FreeBSD 7.0: > > fwcontrol -R mini.dv > > I'd see this: > > Detected DV format on input. > (EAGAIN) - push 'Play'? > (EAGAIN) - push 'Play'? > NTSC > 012345678901234567890123456789 > > > and eventually obtain a dv file named mini.dv. > > At that time, and now, I used a VIA VT6306. However, it now fails: > > fwcontrol -R mini.dv > fwcontrol: detect_recv_fn: ioctl FW_SSTBUF: Bad file descriptor > > And I am unable to retrieve the DV from the tape. > > Grasping at straws, I tried this: > sysctl hw.firewire.try_bmr=0 > fwcontrol -r Ok, my first guess is that fwcontrol did not get rebuilt in your upgrade? I modified fwcontrol to be a bit smarter a while ago. However this did require a rebuild of /usr/sbin/fwcontrol from source. You may want to try "fwcontrol -u 1 -R mini.dv" Since the device list NOW includes the firewire controller in your PC, and that controller is now device "0", you will have to specify the device number with the -u switch. Sean From fj at panix.com Tue Jun 9 14:56:25 2009 From: fj at panix.com (Joe A.) Date: Tue Jun 9 14:56:32 2009 Subject: Failure to pull DV from Panasonic PV-GS320 In-Reply-To: <20090608012539.GA1964@panix.com> References: <20090608012539.GA1964@panix.com> Message-ID: <20090609143958.GA10414@panix.com> Sean... I read your mail, and ended up doing this: fwcontrol -u 0 -M dv -R mini.dv Using the onboard firewire chip. When I combine the part about the '-M' flag: -M mode Explicitly specify either dv or mpeg mode for the incoming stream. Only meaningful in case of and must precede the -R option. If not specified, the program will try to guess. with the example: EXAMPLES fwcontrol -R original.dv Receive a DV stream with DV camera attached. To my eyes, it looked (and looks) as if the '-M' flag was optional; and for whatever reason, I did not have to specify '-M dv' prior to this instance; so fwcontrol guessed correctly for all previous instances. Anyway, problem solved; thanks for your help. Also, I apologize for the bounce; my alias was broken. From bugmaster at FreeBSD.org Mon Jun 15 11:06:53 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jun 15 11:07:51 2009 Subject: Current problem reports assigned to freebsd-firewire@FreeBSD.org Message-ID: <200906151106.n5FB6qbW076878@freefall.freebsd.org> 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 -------------------------------------------------------------------------------- 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 7 problems total. From bugmaster at FreeBSD.org Mon Jun 22 11:06:54 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jun 22 11:07:51 2009 Subject: Current problem reports assigned to freebsd-firewire@FreeBSD.org Message-ID: <200906221106.n5MB6rYL017989@freefall.freebsd.org> 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 -------------------------------------------------------------------------------- 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 7 problems total. From chippy at snnonline.nl Wed Jun 24 19:39:16 2009 From: chippy at snnonline.nl (ovalizes) Date: Wed Jun 24 19:39:26 2009 Subject: 7 Tips Ftor Women to Bring aBck the Prom Night Romance Message-ID: <4A428065-6144339@ir-tech.com> 7 Tips For Women to Bring Back the Prgom Night Romaance www . shop57 . net From bugmaster at FreeBSD.org Mon Jun 29 11:06:57 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jun 29 11:07:51 2009 Subject: Current problem reports assigned to freebsd-firewire@FreeBSD.org Message-ID: <200906291106.n5TB6uPO046296@freefall.freebsd.org> 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 -------------------------------------------------------------------------------- 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 7 problems total. From faust64 at gmail.com Mon Jun 29 14:20:24 2009 From: faust64 at gmail.com (=?ISO-8859-1?Q?Samuel_Mart=EDn_Moro?=) Date: Mon Jun 29 14:20:30 2009 Subject: can't read from two cameras Message-ID: Hi I've got a problem, trying to read streams from 2 firewire DV cameras. When I plug the second camera in, the first one disapear from my /dev, and is replaced by the new one. So I just get /dev/fw0 (-> /dev/fw0.0) and /dev/fwmem0 (-> /dev/fwmem0.0) How can I get more than one device in my /dev ? Thanks! Samuel Mart?n Moro CamTrace {EPITECH.} tek3 From sean.bruno at dsl-only.net Mon Jun 29 15:38:18 2009 From: sean.bruno at dsl-only.net (Sean Bruno) Date: Mon Jun 29 15:38:25 2009 Subject: can't read from two cameras In-Reply-To: References: Message-ID: <1246289897.3981.3.camel@Lappy> On Mon, 2009-06-29 at 15:50 +0200, Samuel Mart?n Moro wrote: > Hi > > I've got a problem, trying to read streams from 2 firewire DV cameras. > When I plug the second camera in, the first one disapear from my /dev, and > is replaced by the new one. > > So I just get /dev/fw0 (-> /dev/fw0.0) and /dev/fwmem0 (-> /dev/fwmem0.0) > > How can I get more than one device in my /dev ? > > > > Thanks! > > > Samuel Mart?n Moro > CamTrace > {EPITECH.} tek3 > _______________________________________________ > freebsd-firewire@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-firewire > To unsubscribe, send any mail to "freebsd-firewire-unsubscribe@freebsd.org" Ouch. Really? What FreeBSD version is this? Sean From faust64 at gmail.com Mon Jun 29 15:47:41 2009 From: faust64 at gmail.com (=?ISO-8859-1?Q?Samuel_Mart=EDn_Moro?=) Date: Mon Jun 29 15:47:47 2009 Subject: can't read from two cameras In-Reply-To: <1246289897.3981.3.camel@Lappy> References: <1246289897.3981.3.camel@Lappy> Message-ID: sry, I forget: *uname -a* FreeBSD h2g2.axis.fr 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Fri May 1 08:49:13 UTC 2009 root@walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 *sysctl -a | grep firewire* debug.firewire_debug: 0 hw.firewire.hold_count: 3 hw.firewire.try_bmr: 1 hw.firewire.fwmem.speed: 2 hw.firewire.fwmem.eui64_lo: 0 hw.firewire.fwmem.eui64_hi: 0 hw.firewire.phydma_enable: 1 hw.firewire.nocyclemaster: 0 hw.firewire.fwe.rx_queue_len: 128 hw.firewire.fwe.tx_speed: 2 hw.firewire.fwe.stream_ch: 2 hw.firewire.fwip.rx_queue_len: 128 hw.firewire.sbp.tags: 0 hw.firewire.sbp.use_doorbell: 0 hw.firewire.sbp.scan_delay: 500 hw.firewire.sbp.login_delay: 1000 hw.firewire.sbp.exclusive_login: 1 hw.firewire.sbp.max_speed: 2 hw.firewire.sbp.auto_login: 1 dev.firewire.0.%desc: IEEE1394(FireWire) bus dev.firewire.0.%driver: firewire dev.firewire.0.%parent: fwohci0 dev.fwe.0.%parent: firewire0 dev.fwip.0.%parent: firewire0 dev.sbp.0.%parent: firewire0 dev.dcons_crom.0.%parent: firewire0 if one need something else... ;) thanks ! Samuel Mart?n Moro CamTrace {EPITECH.} tek3 On Mon, Jun 29, 2009 at 5:38 PM, Sean Bruno wrote: > On Mon, 2009-06-29 at 15:50 +0200, Samuel Mart?n Moro wrote: > > Hi > > > > I've got a problem, trying to read streams from 2 firewire DV cameras. > > When I plug the second camera in, the first one disapear from my /dev, > and > > is replaced by the new one. > > > > So I just get /dev/fw0 (-> /dev/fw0.0) and /dev/fwmem0 (-> /dev/fwmem0.0) > > > > How can I get more than one device in my /dev ? > > > > > > > > Thanks! > > > > > > Samuel Mart?n Moro > > CamTrace > > {EPITECH.} tek3 > > _______________________________________________ > > freebsd-firewire@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-firewire > > To unsubscribe, send any mail to " > freebsd-firewire-unsubscribe@freebsd.org" > > Ouch. Really? > > What FreeBSD version is this? > > Sean > > From gary.jennejohn at freenet.de Tue Jun 30 12:32:11 2009 From: gary.jennejohn at freenet.de (Gary Jennejohn) Date: Tue Jun 30 12:32:18 2009 Subject: 8-CURRENT Firewire In-Reply-To: <1246316092.3981.11.camel@Lappy> References: <1246316092.3981.11.camel@Lappy> Message-ID: <20090630143205.02283be5@ernst.jennejohn.org> On Mon, 29 Jun 2009 15:54:52 -0700 Sean Bruno wrote: > -CURRENT has some slightly different Firewire code in it than 6/7. If > you have an opportunity to test it with your Firewire hard drives and > cameras I'd really appreciate it. > > Stuff that's changed: > multi-speed compatible devices will acutally work. > a 400/800 device is connected to a 400/800 compatible > firewire card via a 400 connection will work at 400 > fwcontrol understands multiple firewire cards as multiple > buses now. most commands now take a -u argument to > indicate the bus. > > Please report to the -firewire if you get a chance to test. It would > be great to get positive as well as negative results. > I plugged in an enclosure with a laptop HDD in it. I couldn't do much with it because it has openSUSE on it and I don't have any Linux file system support in my kernel. But dd works ok: root:ernst:~:bash:10> dd if=/dev/da0 of=/dev/null bs=64k count=10000 10000+0 records in 10000+0 records out 655360000 bytes transferred in 26.577845 secs (24658132 bytes/sec) Here's the kernel output: Jun 30 14:21:12 ernst kernel: fwohci0: fwohci_intr_core: BUS reset Jun 30 14:21:12 ernst kernel: fwohci0: fwohci_intr_core: node_id=0x00000000, SelfID Count=3, non CYCLEMASTER mode Jun 30 14:21:12 ernst kernel: firewire0: 2 nodes, maxhop <= 1 cable IRM irm(1) Jun 30 14:21:12 ernst kernel: fwohci0: too many cycle lost, no cycle master presents? Jun 30 14:21:13 ernst kernel: fwohci0: fwohci_intr_core: BUS reset Jun 30 14:21:13 ernst kernel: fwohci0: fwohci_intr_core: node_id=0x00000000, SelfID Count=4, non CYCLEMASTER mode Jun 30 14:21:13 ernst kernel: firewire0: 2 nodes, maxhop <= 1 cable IRM irm(1) Jun 30 14:21:13 ernst kernel: fwohci0: too many cycle lost, no cycle master presents? Jun 30 14:21:13 ernst kernel: firewire0: New S400 device ID:0030e004e0454649 Jun 30 14:21:13 ernst kernel: sbp0: sbp_show_sdev_info: sbp0:0:0: ordered:1 type:14 EUI:0030e004e0454649 node:1 speed:2 maxrec:8 Jun 30 14:21:13 ernst kernel: sbp0: sbp_show_sdev_info: sbp0:0:0 'ROCSTOR' 'ROC PORT' '000101' Jun 30 14:21:14 ernst kernel: da0 at sbp0 bus 0 target 0 lun 0 Jun 30 14:21:14 ernst kernel: da0: Fixed Simplified Direct Access SCSI-4 device Jun 30 14:21:14 ernst kernel: da0: 50.000MB/s transfers Jun 30 14:21:14 ernst kernel: da0: 76351MB (156368016 512 byte sectors: 255H 63S/T 9733C) Jun 30 14:24:39 ernst kernel: fwohci0: fwohci_intr_core: BUS reset Jun 30 14:24:39 ernst kernel: fwohci0: fwohci_intr_core: node_id=0x00000000, SelfID Count=5, CYCLEMASTER mode Jun 30 14:24:39 ernst kernel: firewire0: 1 nodes, maxhop <= 0 cable IRM irm(0) (me) Jun 30 14:24:39 ernst kernel: firewire0: bus manager 0 Jun 30 14:24:39 ernst kernel: firewire0: fw_attach_dev:Removing missing device ID:0030e004e0454649 Jun 30 14:24:39 ernst kernel: (da0:sbp0:0:0:0): lost device Jun 30 14:24:39 ernst kernel: (da0:sbp0:0:0:0): removing device entry --- Gary Jennejohn From shuvaev at physik.uni-wuerzburg.de Tue Jun 30 15:43:10 2009 From: shuvaev at physik.uni-wuerzburg.de (Alexey Shuvaev) Date: Tue Jun 30 15:43:16 2009 Subject: 8-CURRENT Firewire In-Reply-To: <1246316092.3981.11.camel@Lappy> References: <1246316092.3981.11.camel@Lappy> Message-ID: <20090630152149.GA74145@wep4035.physik.uni-wuerzburg.de> On Mon, Jun 29, 2009 at 03:54:52PM -0700, Sean Bruno wrote: > -CURRENT has some slightly different Firewire code in it than 6/7. If > you have an opportunity to test it with your Firewire hard drives and > cameras I'd really appreciate it. > > Stuff that's changed: > multi-speed compatible devices will acutally work. > a 400/800 device is connected to a 400/800 compatible > firewire card via a 400 connection will work at 400 > fwcontrol understands multiple firewire cards as multiple > buses now. most commands now take a -u argument to > indicate the bus. > > Please report to the -firewire if you get a chance to test. It would > be great to get positive as well as negative results. > > Sean > Seems to work for me. This is not mine drive with "Apple Extended (journaled)" filesystem, so read-only tests only :( ~> uname -a FreeBSD wep4035 8.0-CURRENT FreeBSD 8.0-CURRENT #0 r195053: Fri Jun 26 16:57:21 CEST 2009 root@wep4035:/usr/obj/usr/src/sys/GENERIC amd64 dmesg output due to pluggin-in, -out, -in and -out again: fwohci0: fwohci_intr_core: BUS reset fwohci0: fwohci_intr_core: node_id=0x00000001, SelfID Count=2, CYCLEMASTER mode firewire0: 2 nodes, maxhop <= 1 cable IRM irm(1) (me) firewire0: bus manager 1 firewire0: New S800 device ID:00303c02e013fe3a sbp0: sbp_show_sdev_info: sbp0:0:0: ordered:1 type:14 EUI:00303c02e013fe3a node:0 speed:3 maxrec:8 sbp0: sbp_show_sdev_info: sbp0:0:0 'Iomega' 'HDD' '000110' da0 at sbp0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-4 device da0: 50.000MB/s transfers da0: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C) fwohci0: fwohci_intr_core: BUS reset fwohci0: fwohci_intr_core: node_id=0x00000000, SelfID Count=3, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0 cable IRM irm(0) (me) firewire0: bus manager 0 firewire0: fw_attach_dev:Removing missing device ID:00303c02e013fe3a (da0:sbp0:0:0:0): lost device (da0:sbp0:0:0:0): removing device entry fwohci0: fwohci_intr_core: BUS reset fwohci0: fwohci_intr_core: node_id=0x00000000, SelfID Count=4, non CYCLEMASTER mode firewire0: 2 nodes, maxhop <= 1 cable IRM irm(0) (me) firewire0: root node is not cycle master capable firewire0: bus manager 0 fwohci0: too many cycle lost, no cycle master presents? firewire0: New S800 device ID:00303c02e013fe3a sbp0: sbp_show_sdev_info: sbp0:0:0: ordered:1 type:14 EUI:00303c02e013fe3a node:1 speed:3 maxrec:8 sbp0: sbp_show_sdev_info: sbp0:0:0 'Iomega' 'HDD' '000110' da0 at sbp0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-4 device da0: 50.000MB/s transfers da0: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C) fwohci0: fwohci_intr_core: BUS reset fwohci0: fwohci_intr_core: node_id=0x00000000, SelfID Count=5, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0 cable IRM irm(0) (me) firewire0: bus manager 0 firewire0: fw_attach_dev:Removing missing device ID:00303c02e013fe3a (da0:sbp0:0:0:0): lost device (da0:sbp0:0:0:0): removing device entry dd tests: # dd if=/dev/da0 of=/dev/null bs=1m count=1024 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 26.945771 secs (39848250 bytes/sec) # dd if=/dev/da0 of=/dev/null skip=250000 bs=1m count=1024 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 27.018072 secs (39741615 bytes/sec) # dd if=/dev/da0 of=/dev/null skip=400000 bs=1m count=1024 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 26.958295 secs (39829738 bytes/sec) HTH, Alexey.