From owner-freebsd-hardware@freebsd.org Sun Apr 29 14:28:18 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 865E9FAE2C3; Sun, 29 Apr 2018 14:28:18 +0000 (UTC) (envelope-from freebsd@disroot.org) Received: from knopi.disroot.org (knopi.disroot.org [178.21.23.139]) (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 215C27DD49; Sun, 29 Apr 2018 14:28:17 +0000 (UTC) (envelope-from freebsd@disroot.org) Received: from localhost (localhost [127.0.0.1]) by disroot.org (Postfix) with ESMTP id 1FD0629661; Sun, 29 Apr 2018 16:28:10 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1525012090; bh=3da/vyZVt3DoKosDOv8yNZ6N2ytCYsoGiadblrQPqhM=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=i18h2DNm4PMch6WX8jyjHltzhOLrVSMsmvkjM0wzWb5OiBLHwVDCnsA6YEy32mHJf oYraOcjoSVsaFkXcHFP97P0i5M1sSN8F1tW50U8fumRE9dsG3maEwHas3TAemmh4Bu +DOBnrCbL0+lUyKEgeksNfAt48DST/MEqY1IGQ+YgoDx9vfdThxeKSCW2JNmhlqT6T EKi4DdqFXDT5H13FP+gynguHOXjV9MNt+eM4yUAe261Tp4CxdsyyG7l2Nw0Wq7Cc78 PVnM7FBgGwEYAQ3rcyeexKMy5tODqvQMLNJaE/nNLZ6AhGsjRN8A8+q6ThL+8tXlKs LAq4FrDzFKcJw== X-Virus-Scanned: Debian amavisd-new at disroot.org Received: from knopi.disroot.org ([127.0.0.1]) by localhost (mail01.disroot.lan [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F5xE5zeMqGGP; Sun, 29 Apr 2018 16:28:08 +0200 (CEST) Subject: Re: Can we please finally solve Dell's racadm for FreeBSD? Advice needed DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1525012088; bh=3da/vyZVt3DoKosDOv8yNZ6N2ytCYsoGiadblrQPqhM=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=GMexQlyDWAW7/Etoi0xRaOF/O2uTgBmQEqwCbZvR2qG5Ub5J3aJjC1A4D9T08Lr8Z v2hEqLgeoe9I7mPNLwHiCbRvmmzpOiJP3dqU3Cb83DK1zxXLUa25UNBW+YNH7je4k1 w8GED1FLBt3r5inWfl12mHzyfzBLEre5YvLFf/OYl/Vq4yEXz8OYF6C9gaqDlEucj5 RZWs9Ny7Plu7zqUOOy6avq8XQy30WPlskmo7l2aYkCrW54OhJFopPPqbzM9Q0aBgQ6 NJLQGqVKhjdbFgE8C3sxomWOQIAqC4n/EQLOSQ2JTef2bG/2poOzIAXFGowZwQvivX uqwggiOrBTHtg== To: xxjack12xx@gmail.com Cc: freebsd-hackers@freebsd.org, freebsd-amd64@freebsd.org, freebsd-hardware@freebsd.org References: <5eca3020-4b9c-dd43-8cf0-066d63a92521@disroot.org> From: "Peter G." Message-ID: Date: Sun, 29 Apr 2018 16:28:06 +0200 Mime-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Apr 2018 14:28:18 -0000 On 29/04/2018 05:08, Jack L. wrote: > I manage a variety of Dell servers running FreeBSD, only 610 and 1950s > work with racadm but everything that can be done with racadm can also > be done with ipmitool. I just use ipmitool to get around instead of > their proprietary racadm stuff. What functionality do you need from > racadm and maybe I can give you an ipmitool equivalent? It seems I may missed the ipmi angle altogether assuming it was only remote. Only now following Dan's comments I am realizing how racadm works talking to local hardware. You mean using this impi(4) as a local device and talking to it via local tool allowing coms with the device? Oh, that would do nicely. I need this for scripting mostly, e.g. monitoring what the intrusion sensor shows. Can you please describe your setup? What other kernel modules and 3rd party software do you employ? Any tricks with device.hints are needed? I have a small R220 at hand for testing, but it's lacking impi(4) altogether. Will have to rebuild. -- PG