From owner-freebsd-bugs@FreeBSD.ORG Sun Jan 29 09:10:15 2012 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 924C9106566C for ; Sun, 29 Jan 2012 09:10:15 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 77D4A8FC0A for ; Sun, 29 Jan 2012 09:10:15 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0T9AFAF015073 for ; Sun, 29 Jan 2012 09:10:15 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0T9AFL6015072; Sun, 29 Jan 2012 09:10:15 GMT (envelope-from gnats) Date: Sun, 29 Jan 2012 09:10:15 GMT Message-Id: <201201290910.q0T9AFL6015072@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: James Mansion Cc: Subject: Re: kern/164258: [mfi] mfi does not work with PERC5/i in AMD M350 motherboard X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: James Mansion List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jan 2012 09:10:15 -0000 The following reply was made to PR kern/164258; it has been noted by GNATS. From: James Mansion To: bug-followup@FreeBSD.org, james@mansionfamily.plus.com Cc: Subject: Re: kern/164258: [mfi] mfi does not work with PERC5/i in AMD M350 motherboard Date: Sun, 29 Jan 2012 08:55:20 +0000 The machine doesn't have a serial port. Oddly, the BIOS goes through PERC BIOS setup and then sits and doesn't autoboot: F7 to get the boot list gives me a sane list and then I can just pres return to boot from sata0 (which happens to be an SSD). Then the Beastie menu starts up etc - but at this point the USB keyboard ISN'T working. The countdown timeout triggers OK, and then we boot up OK from the SATA drives. Can I get the boot -v dmesg captured by editing loader.4th (or similar)? James