From owner-freebsd-hardware@freebsd.org Sat Sep 8 21:22:19 2018 Return-Path: Delivered-To: freebsd-hardware@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A4A85FFE9F9 for ; Sat, 8 Sep 2018 21:22:19 +0000 (UTC) (envelope-from josh@tcbug.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 44DD8790E2 for ; Sat, 8 Sep 2018 21:22:19 +0000 (UTC) (envelope-from josh@tcbug.org) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id B406420F02 for ; Sat, 8 Sep 2018 17:22:18 -0400 (EDT) Received: from web2 ([10.202.2.212]) by compute1.internal (MEProxy); Sat, 08 Sep 2018 17:22:18 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=5otw7q RxkIUtHbP2Tpo29H0K1FHqD+lDJyuUB0iCZUo=; b=af921jjxYsk3qWbqW3B+7I 5BGFSbTAxEzwXLKhsCZcS5USFMDSDcPA/LvqwEB55KGlvvUGApT1DWf9WsJbwiv+ 50zwCyYh41eTiL2eTEifKvxaHsJTypQcv8ly6ibkOF/Ufpy8Fu8uF4pwFHcp1mte DnFmhTFLEOxID82nG9K/6pmf/dVclSPZv/0ZGp5aeu2LOU7imBO8KDFrrFZw1fEC a3ioz1eJsS2G4ClU+GcXB5jxRxRACFCbwl9z2JH1lfqkpr8k36FVnOt6k5fnv9NN BWCNqx/5wMkZcD7xiQ1KJOJroxHPEB4mrRHOIOVHf3+uC269/q7ijLyzE7ROUfOw == X-ME-Proxy: X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 2CE1762673; Sat, 8 Sep 2018 17:22:18 -0400 (EDT) Message-Id: <1536441738.3021216.1501446976.64CAD235@webmail.messagingengine.com> From: Josh Paetzel To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-1234af23 In-Reply-To: Subject: Re: Problem with FreeBSD 11.2 and LSI 9341-8i Date: Sat, 08 Sep 2018 16:22:18 -0500 References: X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Sep 2018 21:22:20 -0000 On Sat, Sep 8, 2018, at 1:07 PM, Josh Endries wrote: > I just got an LSI 9341-8i card and I'm having some trouble getting it to > work in a new install of 11.2-RELEASE. I'm trying to replace an old 9.x > FreeNAS box with a new machine. I have one drive connected for testing. I > haven't set anything up, it's just JBOD (which is what I want anyway). The > BIOS seems to see the drive and controller, and in FreeBSD when I boot I > see this: > > AVAGO MegaRAID SAS FreeBSD mrsas driver version: 06.712.04.00-fbsd > mfi0: port 0xd000-0xd0ff mem > 0xfe720000-0xfe72ffff,0xfe600000-0xfe6fffff irq 19 at device 0.0 on pci2 > mfi0: Using MSI > mfi0: Megaraid SAS driver Ver 4.23 > mfi0: FW MaxCmds = 240, limiting to 128 > mfi0: MaxCmd = 240, Drv MaxCmd = 128, MaxSgl = 70, state = 0xbf3c00f0 > mfi0: Init command Failed 0x3 > mfi0: TB Init has failed with error 3 > device_attach: mfi0 attach returned 3 > > I haven't found anything on Google. I read on the mfi man page (I think) > that I should enable mrsas for these cards, so I added > hwmfi.mrsas_enable="1" to /boot/device.hints, but that didn't help. I have > nothing related in /dev, no disk or even a controller node, so I can't > update the firmware or do anything else... I'm not sure what else to try. > > For now I'm going to try 10.x instead and see if that works, though I would > of course rather use the latest version. > > Josh > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" mfi(4) doesn't support the 9341, however mrsas(4) does. Is the snippet of dmesg you pasted after you added hwmfi.mrsas_enable="1" to /boot/device.hints? If so perhaps that isn't just a typo in your email, but rather a typo in your device.hints The correct line is hw.mfi.mrsas_enable="1" If after activating the mrsas driver it's still not working please attach your dmesg and output of pciconf -lv -- Thanks, Josh Paetzel