[formatting recovered]
On Mon, Apr 03, 2000 at 10:57:46AM +0100, Nick Hibma wrote:
> On Fri, 31 Mar 2000, Paul Haddad wrote:
> > On Wed, 22 Mar 2000, Christopher Masto wrote:
> > > I've been playing around with one of those iopener things and got
> > > myself into a state I thought I could get out of with the help of a
> > > USB Zip drive. Unfortunately, upon purchasing and connecting one,
> > > I discovered that I can't access it without a panic, which I
> > > point out here on the chance it's also related.
> >
> > Boy I wish I had read this message before I went out and bought a
> > USB zip drive... I'm in the exact same situation IOPENER with 4.0
> > installed and screwed up to a point where I can boot but not mount
> > the sandisk drive. I figured that I would get a zip drive and
> > mount it instead. Anyways if you found some way around this please
> > let me know, otherwise I've got to make another trip out and get a
> > SuperDisk instead...
> >
> > BTW What state are you in? Mine will boot, but gets to the point
> > where it tries to mount the sandisk and panics with a ffs_write
> > panic. Booting in single user doesn't help.
>
> Where are you guys now as far as USB drives are concerned? I've been
> looking a lot at the driver lately and would like to hear about any
> problems you have.
Well, as for the i-opener, I've gotten mine working. See
http://www.kenseglerdesigns.com/cgi-bin/UltraBoard/UltraBoard.pl?Action=ShowPost&Board=technical&Post=115
I did not have a problem with a panic mounting the sandisk, I just
didn't have a /boot/loader on it so I couldn't load my mfsroot.gz. I
was eventually able to find a Y-E Data floppy drive and use it as a
root filesystem by entering "ufs:/dev/da0" at the mount root prompt.
If a 4.0 kernel is on there, I don't know what to say, as I don't know
what worked at that point. SuperDisk is certainly out of the question,
since it's not there even now.
Regarding USB drives, I have been using the Orb "2.2GB" USB-SCSI
version with some success. There do seem to be some serious
filesystem corruption problems, but I haven't had time to determine
where they're coming from. I often get corruption-related panics
while trying to install packages, and fsck always finds a number of
serious problems and removes about a dozen files (from /usr/lib
mostly, so I'll eventually lose something important). When I
download something large, such as XFree86, the file's checksum
comes out wrong and gzip fails with errors.
I need to have a few hours free to try it on a different machine, with
different media, etc. to try to narrow this down. I have also been
getting kue lockups, so there are a lot of possibilities. I really
haven't played with the thing too much, partly because it's very
slow and takes a good 15 minutes to fsck every time I crash it.
--
Christopher Masto Senior Network Monkey NetMonger Communications
[EMAIL PROTECTED] [EMAIL PROTECTED] http://www.netmonger.net
Free yourself, free your machine, free the daemon -- http://www.freebsd.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
