From owner-freebsd-current  Thu Jul  2 00:07:14 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id AAA18427
          for freebsd-current-outgoing; Thu, 2 Jul 1998 00:07:14 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: (from sos@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id AAA18391;
          Thu, 2 Jul 1998 00:07:01 -0700 (PDT)
          (envelope-from sos)
Message-Id: <199807020707.AAA18391@hub.freebsd.org>
Subject: Re: LBA support problems
In-Reply-To: <199807012116.OAA27090@dragonfly.rain.com> from "mason@methane.dragonfly.rain.com" at "Jul 1, 98 02:16:41 pm"
To: mason@methane.dragonfly.rain.com
Date: Thu, 2 Jul 1998 00:06:58 -0700 (PDT)
Cc: freebsd-current@FreeBSD.ORG
From: sos@FreeBSD.ORG
Reply-to: sos@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In reply to mason@methane.dragonfly.rain.com who wrote:
> Hello all,
> 
> I've posted this to -current because while we're running FreeBSD
> 2.2.6-RELEASE (mostly) this really deals with the LBA support (which
> isn't a feature in a pure 2.2.6-RELEASE system).
> 
> I'm seeing some strange behaviour on our system with the LBA support
> that's been added to wd.c

[snip snap]

> Any ideas anyone?

This works fine with -current, so your patches to 2.2 has gotten
something wrong...
BTW its not nessesary to run the drive in LBA mode when you 
use it for FreeBSD only, normal CHS mode will do just
fine then...


-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Soren Schmidt             (sos@FreeBSD.org)             FreeBSD Core Team
               So much code to hack -- so little time.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message