From owner-freebsd-firewire@FreeBSD.ORG Sun Jul 4 12:19:25 2004 Return-Path: Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3351B16A4CE for ; Sun, 4 Jul 2004 12:19:25 +0000 (GMT) Received: from tora.nunu.org (YahooBB219003182029.bbtec.net [219.3.182.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id A2F2043D41 for ; Sun, 4 Jul 2004 12:19:23 +0000 (GMT) (envelope-from simokawa@sat.t.u-tokyo.ac.jp) Received: from tora.nunu.org (unknown [192.168.1.2]) by tora.nunu.org (Postfix) with ESMTP id E95FA4B26D; Sun, 4 Jul 2004 21:19:21 +0900 (JST) Date: Sun, 04 Jul 2004 21:19:21 +0900 Message-ID: <87eknsrmly.wl@tora.nunu.org> From: Hidetoshi Shimokawa To: Buzz Slye In-Reply-To: References: User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 MULE XEmacs/21.4 (patch 14) (Reasonable Discussion) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII cc: freebsd-firewire@freebsd.org Subject: Re: Digital Cameras X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Jul 2004 12:19:25 -0000 At Thu, 1 Jul 2004 11:26:41 -0700 (PDT), Buzz Slye wrote: > > We've been using firewire digital cameras for some time now for > remote sensing and flying them on UAV's (with a pc104 data system). > We are using a Basler color camera (model A101fc), a Basler single > band camera for hyperspectral imaging, and also an Omega thermal > camera. These cameras conform to spec 1.20 (spec id 0xa02d). Check > www.uav-applications.org (Aircraft and Payload) for some background > info. > > The digital camera library and the 1394 raw library were converted > from the available Linux libraries to FreeBSD. We are still using the That's great. Are you going to make them a port or some other forms others can use it? > firewire version of last April/May (2003). When the July version came > along, it didn't work any more, so we've been stuck with the old ver- > sion. I have been trying to upgrade to the latest version (March 28). > > Async read and write commands are used to read and set the camera > registers for exposure, gain, shutter, and frame size etc. Camera > images are downloaded with iso stream transfer. I don't need to > support iso xmit, but only to iso receive from the camera. Normal > operation is to acquire single frames every few seconds for over- > lapping images of the ground. > > The latest current of fwdev.c (2004/05/23) works for me now for > async read and write. Also, my fix with uiomove for fw_read, per my > mail of 6/24 appears to work OK. A remaining problem is because I You need the uiomove patch to catch response from the camera, right? FireWire binding from userland is not usable state now, some other people who is interested in AV/C support have similar problem. We need some more work on this area. > only acquire single frames, but not continuously, I would like a way > to stop listening (or divert the output) while I go back to the camera > to tell it to stop xmitting. > > Buzz Slye > NASA / Ames I have a copy of digital camera spec. but I've not read it yet. Are frames sent with iso packets? Is it hard to close the device to stop listening? We may add a new ioctl that calls fc->irx_disable(), but we carefully handle buffer allocation/deallocation. I'm glad to hear that you are developing a serious FireWire application on FreeBSD. /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html From owner-freebsd-firewire@FreeBSD.ORG Sun Jul 4 14:00:12 2004 Return-Path: Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C058516A4CE; Sun, 4 Jul 2004 14:00:12 +0000 (GMT) Received: from tora.nunu.org (YahooBB219003182029.bbtec.net [219.3.182.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10C8443D49; Sun, 4 Jul 2004 14:00:12 +0000 (GMT) (envelope-from simokawa@sat.t.u-tokyo.ac.jp) Received: from tora.nunu.org (unknown [192.168.1.2]) by tora.nunu.org (Postfix) with ESMTP id 8BB544B24C; Sun, 4 Jul 2004 23:00:07 +0900 (JST) Date: Sun, 04 Jul 2004 23:00:07 +0900 Message-ID: <87d63bswig.wl@tora.nunu.org> From: Hidetoshi Shimokawa To: Alexander Nedotsukov In-Reply-To: <40E4C710.1040702@FreeBSD.org> References: <40E4C710.1040702@FreeBSD.org> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 MULE XEmacs/21.4 (patch 14) (Reasonable Discussion) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII cc: freebsd-firewire@FreeBSD.org Subject: Re: Block noise? when trying to send dv stream to video camera X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Jul 2004 14:00:12 -0000 At Fri, 02 Jul 2004 11:23:12 +0900, Alexander Nedotsukov wrote: > > Hi, > > I have Sony DCR-HC40 video camera and trying to use firewire link to > download->edit->upload movie form it. I used fwcontrol -R test.dv > command to download data. Whole process went just fine. I can play raw > dv data and content looks correct. But if I try to send dv video (either > unmodified) back to the camera with fwcontrol -S test.dv command picture > get corrupted quickly. Corruption looks like whole image splitted into How log does the noise-less image last? a few seconds or shorter? > square blocks and some parts of those blocks stay gray while > another contains correct image. Blocks are moving. The size of blocks > may vary. Time before video get corrupted as well from 0 to 50 sec. Do > you have any idea what it can be and what is much better how to fix the > situation? > I running one week old -CURRENT world+kernel. > > Thanks, > Alexander. Every DV frame has a timestamp on the packet. The DV specification said that the timestamp must be synced with the bus cycle timer. Some DV equipments are very sensitive to it and if it's out of sync, we often observe block noises. Current iso transmit code start transmit at specific bus cycle to ensure that the timestamp must be synced at the start. The following packets have timestamps which are calculated under the assumption that a packet is sent for each bus cycle. If the assumption is broken for some reason(bus is busy to transmit a packer, the host is too slow to feed the packet and etc.), the timestamp will be out of sync. Do you use PAL or NTSC? /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html From owner-freebsd-firewire@FreeBSD.ORG Tue Jul 6 04:07:09 2004 Return-Path: Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C80E116A4CE for ; Tue, 6 Jul 2004 04:07:09 +0000 (GMT) Received: from smtp3.jp.viruscheck.net (smtp3.jp.viruscheck.net [154.33.69.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id A053A43D1F for ; Tue, 6 Jul 2004 04:07:09 +0000 (GMT) (envelope-from bland@freebsd.org) Received: from scan1.jp.viruscheck.net ([154.33.69.36] helo=mail5.jp.viruscheck.net) by smtp3.jp.viruscheck.net with esmtp (Exim 3.36 #1) id 1BhhEa-0000Lk-00; Tue, 06 Jul 2004 13:07:08 +0900 Received: from [220.221.3.201] (helo=noc.orchid) by mail5.jp.viruscheck.net with esmtp (Exim 3.36 #2) id 1BhhEa-00023J-00; Tue, 06 Jul 2004 13:07:08 +0900 Received: from [89.60.10.11] (horse.orchid [89.60.10.11]) by noc.orchid (8.12.11/8.12.11) with ESMTP id i66477N9097472; Tue, 6 Jul 2004 13:07:07 +0900 (JST) (envelope-from bland@FreeBSD.org) Message-ID: <40EA256B.6060101@FreeBSD.org> Date: Tue, 06 Jul 2004 13:07:07 +0900 From: Alexander Nedotsukov User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a1) Gecko/20040520 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Hidetoshi Shimokawa References: <40E4C710.1040702@FreeBSD.org> <87d63bswig.wl@tora.nunu.org> In-Reply-To: <87d63bswig.wl@tora.nunu.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-firewire@FreeBSD.org Subject: Re: Block noise? when trying to send dv stream to video camera X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jul 2004 04:07:09 -0000 Hidetoshi Shimokawa wrote: >How log does the noise-less image last? a few seconds or shorter? > > > >>square blocks and some parts of those blocks stay gray while >>another contains correct image. Blocks are moving. The size of blocks >>may vary. Time before video get corrupted as well from 0 to 50 sec. Do >>you have any idea what it can be and what is much better how to fix the >>situation? >>I running one week old -CURRENT world+kernel. >> >>Thanks, >>Alexander. >> >> > >Every DV frame has a timestamp on the packet. The DV specification >said that the timestamp must be synced with the bus cycle timer. >Some DV equipments are very sensitive to it and if it's out of sync, >we often observe block noises. > >Current iso transmit code start transmit at specific bus cycle to >ensure that the timestamp must be synced at the start. >The following packets have timestamps which are calculated under >the assumption that a packet is sent for each bus cycle. >If the assumption is broken for some reason(bus is busy to transmit >a packer, the host is too slow to feed the packet and etc.), >the timestamp will be out of sync. > >Do you use PAL or NTSC? > > Well now things become a little bit clear :-) Thanks for explanation. I use NTSC and regilar 4:3 video format. The time I can see noise-less image vary. Some time it 40-50 sec before noise come and some time I see it right after start fwcontrol -S. After you explained me this timing issues I tried to start fwcontrol from system console (not from gnome-terminal window as I did before) and yahoo block noise gone. But there is still a problem. Now Video plays nicely about 5-10 mins and stops then. I can see (EAGAIN) errors reported by fwcontrol utility and this on the system console: ... fwohci0: IT DMA underrun (0x3ab08011) fwohci0: IT DMA underrun (0x3ab08011) fwohci0: IT DMA underrun (0x3ab08011) fwohci0: IT DMA underrun (0x3ab08011) ... Few notes about system performance. I have PIII 1GHz machine here with UDMA66 disk. cpu is 100% idle all the time video transmitted to the camera. All the best, Alexander. From owner-freebsd-firewire@FreeBSD.ORG Wed Jul 7 06:52:12 2004 Return-Path: Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 832DF16A4CE; Wed, 7 Jul 2004 06:52:12 +0000 (GMT) Received: from mta06-svc.ntlworld.com (mta06-svc.ntlworld.com [62.253.162.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 90B8043D46; Wed, 7 Jul 2004 06:52:11 +0000 (GMT) (envelope-from dmlb@dmlb.org) Received: from dmlb.org ([81.96.76.36]) by mta06-svc.ntlworld.com (InterMail vM.4.01.03.37 201-229-121-137-20020806) with ESMTP id <20040707065219.XASS9422.mta06-svc.ntlworld.com@dmlb.org>; Wed, 7 Jul 2004 07:52:19 +0100 Received: from orac.my.domain ([192.168.200.67] helo=orac) by dmlb.org with smtp (Exim 4.32; FreeBSD) id 1Bhxep-0005rI-K1; Tue, 06 Jul 2004 22:39:19 +0100 Message-ID: <01e201c463a1$c3d92950$43c8a8c0@orac> From: "Duncan Barclay" To: , Date: Tue, 6 Jul 2004 22:39:49 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Subject: Firewire drives, FreeBSD 4.10 and readonly errors X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jul 2004 06:52:12 -0000 Hello all I am setting up a machine (RELENG_4_10) with firewire drives (Maxtor OneTouch) to act as backup media for a customer. I have done this very succesfully with 4.9-RELEASE. My prefered partitioning is to create one MSDOS slice of 1G with a copy of a miniinst ISO, a dump of / and /usr and a README detailling how to reconstruct a server. The rest of the drive is a single UFS slice with the important user data. I do this, so that if anything happens all that needs to happen is to plug the drive into some h/w (via USB or Firewire) and burn a CD to rebuild the server. The problem that I am having is in creating the MSDOS partition under 4.10. I use fdisk to create the partitions: # fdisk /dev/da0 ******* Working on device /dev/da0 ******* parameters extracted from in-core disklabel are: cylinders=19929 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=19929 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 6,(Primary 'big' DOS (> 32MB)) start 63, size 2088387 (1019 Meg), flag 0 beg: cyl 0/ head 1/ sector 1; end: cyl 129/ head 254/ sector 63 The data for partition 2 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 2088450, size 318070935 (155308 Meg), flag 80 (active) beg: cyl 130/ head 0/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 3 is: The data for partition 4 is: Then newfs_msdos the first slice, but I get: # newfs_msdos /dev/da0s1 /dev/da0s1: 2084280 sectors in 260535 FAT32 clusters (4096 bytes/cluster) bps=512 spc=8 res=32 nft=2 mid=0xf8 spt=63 hds=255 hid=63 bsec=2088387 bspf=2036 rdcl=2 infs=1 bkbs=2 newfs_msdos: /dev/da0s1: Read-only file system As these drives come pre-formatted with a single slice I have tried: # dd if=/dev/zero of=/dev/da0s1 bs=2048 count=1024 dd: /dev/da0s1: Read-only file system 1+0 records in 0+0 records out 0 bytes transferred in 0.028599 secs (0 bytes/sec) What am I doing wrong to get the read-only errors? I have rebooted between writing a blank partition table and trying the newfs_msdos to no avail. Other than this error (that prevents a fsck_msdos -p from completing) writes are fine. BTW, I can recommend the Maxtor OneTouch products-they come in a nice chassis and are a robust product with Firewire and USB2 interfaces. As a backup (not archive) media they are ideal, far cheaper than tape. I have used them a number of times and provide my clients with a least two drives to use on rotation. This is more for disaster recovery than anything. The clients are instructed to keep at least one drive off the premesis. Duncan PS. Please CC me on replies from freebsd-firewire as I am not subscribed From owner-freebsd-firewire@FreeBSD.ORG Thu Jul 8 01:18:40 2004 Return-Path: Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 879B316A4CE; Thu, 8 Jul 2004 01:18:40 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E7DE43D5A; Thu, 8 Jul 2004 01:18:37 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id i681IFgt049630; Thu, 8 Jul 2004 10:48:15 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-stable@freebsd.org Date: Thu, 8 Jul 2004 10:48:14 +0930 User-Agent: KMail/1.6.2 References: <01e201c463a1$c3d92950$43c8a8c0@orac> In-Reply-To: <01e201c463a1$c3d92950$43c8a8c0@orac> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200407081048.14879.doconnor@gsoft.com.au> X-Spam-Score: -4.6 () CARRIAGE_RETURNS,IN_REP_TO,MIME_LONG_LINE_QP,PGP_SIGNATURE,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT,USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: freebsd-firewire@freebsd.org cc: Duncan Barclay Subject: Re: Firewire drives, FreeBSD 4.10 and readonly errors X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jul 2004 01:18:40 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 7 Jul 2004 07:09, Duncan Barclay wrote: > My prefered partitioning is to create one MSDOS slice of 1G with a copy of > a miniinst ISO, a dump of / and /usr and a README detailling how to > reconstruct a server. The rest of the drive is a single UFS slice with the > important user data. I do this, so that if anything happens all that needs > to happen is to plug the drive into some h/w (via USB or Firewire) and bu= rn > a CD to rebuild the server. Neat idea :) > Then newfs_msdos the first slice, but I get: > # newfs_msdos /dev/da0s1 > /dev/da0s1: 2084280 sectors in 260535 FAT32 clusters (4096 bytes/cluster) > bps=3D512 spc=3D8 res=3D32 nft=3D2 mid=3D0xf8 spt=3D63 hds=3D255 hid=3D63= bsec=3D2088387 > bspf=3D2036 rdcl=3D2 infs=3D1 bkbs=3D2 > newfs_msdos: /dev/da0s1: Read-only file system > > As these drives come pre-formatted with a single slice I have tried: > # dd if=3D/dev/zero of=3D/dev/da0s1 bs=3D2048 count=3D1024 > dd: /dev/da0s1: Read-only file system > 1+0 records in > 0+0 records out > 0 bytes transferred in 0.028599 secs (0 bytes/sec) > > What am I doing wrong to get the read-only errors? > > I have rebooted between writing a blank partition table and trying the > newfs_msdos to no avail. Other than this error (that prevents a > fsck_msdos -p from completing) writes are fine. Can you try=20 fdisk -I da0 disklabel -e da0s1 [ .. ] newfs /dev/da0s1a ? Also try editing the partition table and changing it to a DOS partition and= =20 seeing if newfs_msdos works? > BTW, I can recommend the Maxtor OneTouch products-they come in a nice > chassis and are a robust product with Firewire and USB2 interfaces. As a > backup (not archive) media they are ideal, far cheaper than tape. I have > used them a number of times and provide my clients with a least two drives > to use on rotation. This is more for disaster recovery than anything. The > clients are instructed to keep at least one drive off the premesis. I've used them (had to get a patch from Mr Firewire before they'd work :) I prefer Mapower aluminium cases, cheaper and you can customise the drive. (And they seem to work just as well.. probably got the same interface) =2D --=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA7KDW5ZPcIHs/zowRApZqAJ9wOyBfE5F4sHq+LyL9cXmPuhCKfgCeLKcl kYs4cEorZvMz35R9sqqxHYo=3D =3DXEpN =2D----END PGP SIGNATURE----- From owner-freebsd-firewire@FreeBSD.ORG Thu Jul 8 17:41:41 2004 Return-Path: Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3524616A4CE; Thu, 8 Jul 2004 17:41:41 +0000 (GMT) Received: from mta07-svc.ntlworld.com (mta07-svc.ntlworld.com [62.253.162.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47E7943D58; Thu, 8 Jul 2004 17:41:40 +0000 (GMT) (envelope-from dmlb@dmlb.org) Received: from dmlb.org ([81.96.76.36]) by mta07-svc.ntlworld.com (InterMail vM.4.01.03.37 201-229-121-137-20020806) with ESMTP id <20040708174156.HKAQ7085.mta07-svc.ntlworld.com@dmlb.org>; Thu, 8 Jul 2004 18:41:56 +0100 Received: from orac.my.domain ([192.168.200.67] helo=orac) by dmlb.org with smtp (Exim 4.32; FreeBSD) id 1Bictb-00094K-Uh; Thu, 08 Jul 2004 18:41:20 +0100 Message-ID: <003801c46512$dc5940b0$43c8a8c0@orac> From: "Duncan Barclay" To: "Daniel O'Connor" , References: <01e201c463a1$c3d92950$43c8a8c0@orac> <200407081048.14879.doconnor@gsoft.com.au> Date: Thu, 8 Jul 2004 18:41:55 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 cc: freebsd-firewire@freebsd.org Subject: Re: Firewire drives, FreeBSD 4.10 and readonly errors X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jul 2004 17:41:41 -0000 Problem solved: I had used the wrong FAT32 type when fdisking. It needed to be type 11 not type 6. Thanks for the suggestion anyway. Duncan From owner-freebsd-firewire@FreeBSD.ORG Fri Jul 9 00:26:44 2004 Return-Path: Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8D94B16A4CE; Fri, 9 Jul 2004 00:26:44 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84ABF43D1D; Fri, 9 Jul 2004 00:26:41 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id i690QOYr088112; Fri, 9 Jul 2004 09:56:28 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: "Duncan Barclay" Date: Fri, 9 Jul 2004 09:56:24 +0930 User-Agent: KMail/1.6.2 References: <01e201c463a1$c3d92950$43c8a8c0@orac> <200407081048.14879.doconnor@gsoft.com.au> <003801c46512$dc5940b0$43c8a8c0@orac> In-Reply-To: <003801c46512$dc5940b0$43c8a8c0@orac> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Message-Id: <200407090956.24970.doconnor@gsoft.com.au> X-Spam-Score: -2.8 () CARRIAGE_RETURNS,IN_REP_TO,PGP_SIGNATURE,REFERENCES,SPAM_PHRASE_00_01,UPPERCASE_25_50,USER_AGENT,USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: freebsd-firewire@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: Firewire drives, FreeBSD 4.10 and readonly errors X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jul 2004 00:26:44 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 9 Jul 2004 03:11, Duncan Barclay wrote: > Problem solved: I had used the wrong FAT32 type when fdisking. It needed = to > be type 11 not type 6. Ahh, really? Weird.. I have always used 6 without hassle. Hmm.. > Thanks for the suggestion anyway. NP =2D --=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA7eYw5ZPcIHs/zowRAowcAKCC4yomHVQF1RUJGQZJdnUfPFCPrQCggLQ5 bmDzWup61I+mp832ZVq0ncQ=3D =3DUNDJ =2D----END PGP SIGNATURE-----