atom feed8 messages in org.freebsd.freebsd-firewire(none) was: Re: Ext. firewire disk d...
FromSent OnAttachments
Barry BouwsmaSep 15, 2003 2:31 pm 
Hidetoshi ShimokawaSep 16, 2003 8:29 am 
Barry BouwsmaSep 17, 2003 10:09 pm 
Barry BouwsmaSep 20, 2003 6:00 am 
Hidetoshi ShimokawaSep 21, 2003 7:25 pm 
Barry BouwsmaSep 29, 2003 8:26 pm 
Hidetoshi ShimokawaSep 29, 2003 9:04 pm 
Barry BouwsmaNov 4, 2003 8:50 pm 
Subject:(none) was: Re: Ext. firewire disk disconnection and persistence of da* entry...
From:Barry Bouwsma (free@remove-NOSPAM-to-reply.NOSPAM.dyndns.dk)
Date:Nov 4, 2003 8:50:30 pm
List:org.freebsd.freebsd-firewire

[sorry for the delay; I've been away and mostly offline. Drop me from the list of recipients and I'll catch the archives Real Soon Now]

You wrote:

What I am looking for, is that the firewire drive is made available as da0 at boot, ideally with support in kernel modules instead of the

Did you chage SCSI_DELAY from the default 15sec?

Ah, very good observation. Yes, I did, when a normal SCSI drive gave me no problems with a much lower value.

Increasing the value to 8 seconds gave one time when a timeout was recorded; otherwise, the drive was mostly detected fine. I backed out the change I thought I needed to make to get things to work.

Just as a note, there was a time when I got nothing but timeouts. I then rebuilt the kernel with SCSI_DELAY increasing up to and including 15 seconds, with no change. Until I disconnected and reconnected the drive; then it worked fine, even with a 5 second SCSI_DELAY, thereafter.

I'm back down to a 5 second SCSI_DELAY, without my hacks (I think), and it works. So, sorry about the false alarm, and this for the archives, in case someone else seems to have problems, to double-check the value of SCSI_DELAY.

Thanks for the pointer, sorry for the delay in this response, and sorry for all the noise I created already.