From owner-freebsd-hardware@FreeBSD.ORG Sat May 3 16:05:17 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E1A5D1065670 for ; Sat, 3 May 2008 16:05:17 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from parsely.rain.com (parsely.rain.com [199.26.172.196]) by mx1.freebsd.org (Postfix) with ESMTP id 608C18FC18 for ; Sat, 3 May 2008 16:05:17 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from sopwith.solgatos.com (uucp@localhost) by parsely.rain.com (8.11.4/8.11.4) with UUCP id m43G5Bv77252; Sat, 3 May 2008 09:05:11 -0700 (PDT) (envelope-from freebsd@sopwith.solgatos.com) Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id QAA03668; Sat, 3 May 2008 16:03:45 GMT Message-Id: <200805031603.QAA03668@sopwith.solgatos.com> To: "Shaun Sabo" In-reply-to: Your message of "Sat, 03 May 2008 10:46:11 EDT." Date: Sat, 03 May 2008 09:03:45 +0100 From: Dieter Cc: freebsd-hardware@freebsd.org Subject: Re: FreeBSD 7.0 SATA Controller X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 May 2008 16:05:18 -0000 > Im really not too concerned about the bios bug. i just figured it might be a > side effect of freebsd not being able access the disks. just out of > curiosity though, before i upgrade 6.2 to 7.0 again, what is the atpic > device supposed to do? My understanding is that atpic is the old way of mapping interrupts, and apic is the new way. If apic doesn't work for whatever reason, you need atpic. I was was getting lots of errors like Could not allocate irq attach returned 6 no driver attached Can't map interrupt -> can't attach driver -> can't talk to disks -> can't mount root