From owner-freebsd-questions  Thu May 11 07:32:33 1995
Return-Path: questions-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id HAA01360
          for questions-outgoing; Thu, 11 May 1995 07:32:33 -0700
Received: from gateway.uwohali.com (gateway.uwohali.com [198.79.105.253])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id HAA01354
          for <questions@freebsd.org>; Thu, 11 May 1995 07:32:29 -0700
Received: from Uwohali1.Uwohali.Com (uwohali1.uwohali.com [198.79.105.1]) by gateway.uwohali.com (8.6.9/8.6.9) with SMTP id JAA23798; Thu, 11 May 1995 09:36:07 -0500
Received: from UWOHALI1/MAILQ by Uwohali1.Uwohali.Com (Mercury 1.13);
    Thu, 11 May 95 9:30:18 -0600
Received: from MAILQ by UWOHALI1 (Mercury 1.13); Thu, 11 May 95 9:30:14 -0600
From: "Walter Huff" <WHUFF@uwohali.com>
Organization:  Uwohali, Incorporated
To: Ivan Lima <ivan@nauplius.rsmas.miami.edu>
Date:          Thu, 11 May 1995 09:30:09 CST
Subject:       Re: Colorado tape drive
Reply-to: whuff@uwohali.com
CC: questions@FreeBSD.org
Priority: normal
X-mailer: Pegasus Mail/Windows (v1.22)
Message-ID: <11BC7D7A6A@Uwohali1.Uwohali.Com>
Sender: questions-owner@FreeBSD.org
Precedence: bulk

> From:          Ivan Lima <ivan@nauplius.rsmas.miami.edu>
> Subject:       Colorado tape drive
> To:            whuff@uwohali.com
> Date:          Thu, 11 May 1995 10:09:59 -0400 (EDT)

> 	Sorry to e-mail directly to you instead of posting in the news
> group (my news reader is not posting for some reason). 
> 	I read your posting on comp.os.386bsd.misc about the problems
> you were having with your Colorado Jumbo 250. I'm also having problems
> with my Colorado Jumbo 250, but not the same you had. In my case I
> can't get the kernel to probe the tape drive at boot-up. And I noticed
> that in your case it saw the tape drive and that you have the same
> version of FreeBSD that I do (2.0). So, I'd greatly appreciate if you
> sent me a copy of the configuration file you used to build the kernel
> or just told me what you did. I've rebuilded my kernel several times
> trying different options (flags 0x1, flags1) and nothing worked.

Actually, I didn't re-build the kernel!  I used the stock 2.0R kernel 
as provided in the distribution, unmodified and un-rebuilt.  The 
machine is extremely stock, and all the devices in it were correctly 
recognized and operational (except for the tape drive), so I didn't 
re-build it.

As an update I have swapped in the cable with which the tape drive is 
supposed to hook up, and the result is now the kernel doesn't even 
see the tape drive!  The floppy drive still appears to be working 
however

> 	Thanks in advance,
> 
> -ivan-
> ivan@nauplius.rsmas.miami.edu
> 
> 

Anybody out there have any further insight on this wonderous set of 
occurances?

- Walter Huff