From owner-freebsd-hardware Fri Jan 12 12:59:43 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from accord.grasslake.net (accord.grasslake.net [206.11.249.240]) by hub.freebsd.org (Postfix) with ESMTP id 6CD3437B402; Fri, 12 Jan 2001 12:59:25 -0800 (PST) Received: from marlowe (accord.grasslake.net [206.11.249.240]) by accord.grasslake.net (8.11.1/8.11.1) with SMTP id f0CKupE36866; Fri, 12 Jan 2001 14:56:51 -0600 (CST) (envelope-from swb@grasslake.net) Message-ID: <000401c07cda$ad575370$b8209fc0@marlowe> From: "Shawn Barnhart" To: "Mike Smith" Cc: References: <200101120158.f0C1wT201615@mass.osd.bsdi.com> Subject: Re: Doing an install with the aac driver Date: Fri, 12 Jan 2001 15:00:21 -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.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From: "Mike Smith" > Er, I thought that scottl merged it back. He must have forgotten to > update GENERIC. Use a -current install floppy set then. 8) He should also merge in some changes to MAKEDEV so devices can be built, but that's another story. Last I looked MAKEDEV didn't support the aacd devices, except in CURRENT. I did get a 4.2-RELEASE install going on it, but things got kind of weird. I did the install with a 5.0-snap install floppies and a 4.2-RELEASE CD. Install went OK, and I was able to get it running with a 4.2-STABLE kernel (built elsewhere) with the aac driver. I rebuilt world and I noticed that periodically during the installworld that the process would just kind of stop -- switching vtys to a vmstat screen would show the disk drive @ 100%. Then it would take off again like everything was normal. After buildworld, buildkernel, installkernel and installworld I rebooted. During the reboot process the kernel "gave up" on 7 buffers, and on reboot my / is dirty, except I get nothing but "command timed out..", even after power cycling the host (HP LC2000, Dual 866 CPUs, 1GB RAM) and the array cabinet (HP Rackstorage 12 w/6 disks). Any ideas? Did I oops by running a 4.2-STABLE kernel with 4.2-RELEASE binaries and libs? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message