From owner-freebsd-multimedia  Sat Feb 22 13:32:24 1997
Return-Path: <owner-multimedia>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA20218
          for multimedia-outgoing; Sat, 22 Feb 1997 13:32:24 -0800 (PST)
Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA20211
          for <multimedia@FreeBSD.org>; Sat, 22 Feb 1997 13:32:20 -0800 (PST)
Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.7.3) with ESMTP id NAA09286; Sat, 22 Feb 1997 13:32:20 -0800 (PST)
Message-Id: <199702222132.NAA09286@rah.star-gate.com>
X-Mailer: exmh version 1.6.9 8/22/96
To: Randall Hopper <rhh@ct.picker.com>
cc: multimedia@FreeBSD.org
Subject: Re: New BT848 driver 0.2 
In-reply-to: Your message of "Sat, 22 Feb 1997 16:19:52 EST."
             <19970222161952.45511@ct.picker.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 22 Feb 1997 13:32:19 -0800
From: Amancio Hasty <hasty@rah.star-gate.com>
Sender: owner-multimedia@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

Sorry about that , I am going over the driver right now attempting to
find out what can cause the problem that you are seeing in your
system. So far no luck over here. About the wd driver well I think
that that  driver also needs work. My P100 has IDE drives and I must 
say that with my PPRO 200, adaptec  + SCSI disk drives seems to be more
stable with or without the Bt848 driver.

	Amancio

>From The Desk Of Randall Hopper :
> Well, I've fscked my root disk so many times today it went belly-up.  (From
> the fixit disk:
> 
>      > mount /dev/wd1a /mnt
>      /dev/wd1a on /mnt: Incorrect superblock
> 
>      > fsck /dev/rwd1a
>      Can't open /dev/rwd1a: Invalid argument
> 
>      > disklabel wd1
>      DIOCGDINFO: Invalid argument
> 
>      > fdisk wd1 
>      ...(correct partition info)...
> 
> Having never had disk problems with FreeBSD before, I guess I'll need to
> dig in and figure out the safest way to go about diagnosing and repairing
> the damage (boot block, disklabel, or something) before I can continue
> working with the Bt driver.
> 
> All tips welcome.
> 
> Randall
> 
>