From owner-freebsd-questions Wed Sep 15 6:54:25 1999 Delivered-To: freebsd-questions@freebsd.org Received: from crash.videotron.ab.ca (crash.videotron.ab.ca [206.75.216.220]) by hub.freebsd.org (Postfix) with ESMTP id 22F5915231 for ; Wed, 15 Sep 1999 06:54:18 -0700 (PDT) (envelope-from cwasser@v-wave.com) Received: from area51 (area51.v-wave.com [24.108.26.39]) by crash.videotron.ab.ca (8.9.2/8.9.2) with SMTP id HAA17885 for ; Wed, 15 Sep 1999 07:54:17 -0600 (MDT) Message-ID: <000701beff81$bf9f3a20$271a6c18@vwave.com> From: "Chris Wasser" To: Subject: HPT366 controller Date: Wed, 15 Sep 1999 07:53:54 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-Mimeole: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone had any success (hope this is the right area) on getting FreeBSD 3.2 (or any 3.x) working with the Highpoint-Technologies UDMA66 controller? I recently switched mobo's here, tried booting the GENERIC kernel on 3.2 (I knew I was gonna have an issue before hand, I recall reading something about "secondary" controllers in LINT) crossing my fingers it'd come up so I could mod it. It's on a ABIT BE6 motherboard, running the HPT366 controller as primary, rather then the Intel BX PCI-IDE controller (which I have disabled)... winsux sees it as a SCSI controller as do the system BIOS (PCI listing shows it as a PCI mass storage controller) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message