Ext. firewire disk disconnection and persistence of da* entry...
Barry Bouwsma
freebsd-misuser at remove-NOSPAM-to-reply.NOSPAM.dyndns.dk
Wed Sep 17 22:09:34 PDT 2003
[Ooops, looks like I sent out a few mails to the lists with the wrong
address, so most of your anti-spam filters probably bitbucketed them
where they belong. That'll learn me. If you just reply to the list
and drop me, I'll catch up later from the archives... ]
> > enlighten me as to what it would be, given the alternative of hanging
> > attempts to access the device under my old RELENG_4 ?
> See manpage of sbp(4).
Hmmm, checking manpage. Nothing obvious -- Ooops, these are the man
pages from last December, on which I was doing my hacking. Reading
the latest man pages, that I haven't built yet, I see what you mean.
I need to get online more often...
> You can detach the drive after 4 or 5 'fwcontrol -r'.
Ah yes, another program that didn't exist back in December. Well, I
guess it's time for me to build the whole world, as well as just the
kernel...
> > (PS: I'll see about syncing the rest of my hacks against the latest code
> > to see what more is needed to get my drive working reliably, and sending
> Could you describe a detail of the problem?
I believe -- but I am not certain, because I've been running with my
hacked codes from half a year ago, that the drive is not reliably
recognized every time it's attached, but it is recognized every second
or third time. But I am not certain, since it has been a while since
I was using a kernel with the latest codes, and then only to see what
did and did not work perfectly.
Also, I could be confused, because the drive works both as a Firewire
peripheral, and as a USB2/1 device, and I may have seen this with the
USB1.x codes, or perhaps with the USB2 codes I've tried to extract
from 5.x and NetBSD and merge into 4_RELENG -- I needed hacks to the
USB code from last December, and I see I've changed several USB files
from last week's 4.x source.
I will let you know after some days, when I've rebooted my machine into
this year's 4.x, just what the problem was. And I'll also see if the
hacks I made could be applied to fix the problem.
Thanks, and sorry for not completely updating my system before asking
my last question...
Barry Bouwsma
More information about the freebsd-firewire
mailing list