From owner-freebsd-amd64@freebsd.org Sun Apr 22 02:00:52 2018 Return-Path: Delivered-To: freebsd-amd64@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 30757FB657B for ; Sun, 22 Apr 2018 02:00:52 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic307-12.consmr.mail.ne1.yahoo.com (sonic307-12.consmr.mail.ne1.yahoo.com [66.163.190.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B828C74ED3 for ; Sun, 22 Apr 2018 02:00:51 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: 3HDaIXQVM1nIH8ytBfWnxZ1qAFHfkB8uOr5oqC5mW_wMMLu1tRv3rVAj97gD5nf Cey_bq2COOL2K8Ph6kl6.3yLdccL4.onUtPPQjN79rDml0RetJPJnAZ.IuJ8f6FpuLNMlnXbM180 kGgHVM0LYNdkYZgj0p9qEQl8ZZjvVYFsJ3Qr1aGawlt3tiwvPUrLYzhuB6axlsoO4MQ2FskjUBv9 .7DviAcbZRVDj3kQd_5nnkRM074CjQik_o5dnk3vZQd0FDDcQ1QxHXDo2li5VMOo_7sBuBV6zgtE qw0ovgZSLVgV37_SWCcZRSucxDKAOeg7s3gdmQRkuYOyCj6VhthrdxDjRmpasjWPcaG1KmGc2CRh XKwQm25aSAaW9aev9s8o9o3_6WS58Ih_QN7lf8uAh112v3k9EKv9z3EmO4bbcwTNQpWz.rpyQSf6 WwFoYdqmgsrc77GDz98tFxIXnEL5g5hf_qJa4MHPVAaqWMKE.cePO8LjsyMqK1F_uEy41z40P_ap cQpep0YGpgrspAGhCp4OWHZ4K.zNmCe528sTpjRPRtn0JXgwUjptT12CsEiJTeaEG79UND2gLmTX q5yj2w7M- Received: from sonic.gate.mail.ne1.yahoo.com by sonic307.consmr.mail.ne1.yahoo.com with HTTP; Sun, 22 Apr 2018 02:00:45 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp409.mail.ne1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID bd7ba04b5069c7487a7c8a06959d2076; Sun, 22 Apr 2018 02:00:41 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Why https://ci.freebsd.org/job/FreeBSD-head-amd64-gcc builds are failing . . . Message-Id: <570A6CA9-6DBD-4F5C-BA3E-8ABE953B8A79@yahoo.com> Date: Sat, 21 Apr 2018 19:00:40 -0700 To: freebsd-toolchain@freebsd.org, freebsd-amd64@freebsd.org X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Apr 2018 02:00:52 -0000 /usr/local/bin/x86_64-freebsd-ld: unrecognized option '--no-rosegment' is the message that reports what stops the build. I think this traces back to: /usr/src/share/mk/bsd.sys.mk:LDFLAGS+=3D ${LDFLAGS.${LINKER_TYPE}} being incorrect for an amd64-gcc / x86_64-freebsd-ld based build. The details for how I got to that follow. Looking around . . . # grep -r rosegment /usr/src/* | more /usr/src/contrib/llvm/tools/lld/ELF/Writer.cpp: // -no-rosegment = option is used. /usr/src/contrib/llvm/tools/lld/ELF/Options.td:def no_rosegment: = F<"no-rosegment">, /usr/src/contrib/llvm/tools/lld/ELF/ScriptParser.cpp: // -no-rosegment = is used to avoid placing read only non-executable sections in /usr/src/contrib/llvm/tools/lld/ELF/SyntheticSections.cpp: // for that = case, which happens only when -no-rosegment is given. /usr/src/contrib/llvm/tools/lld/ELF/Driver.cpp: Config->SingleRoRx =3D = Args.hasArg(OPT_no_rosegment); /usr/src/stand/i386/Makefile.inc:LDFLAGS.lld+=3D -Wl,--no-rosegment /usr/src/usr.bin/clang/lld/ld.lld.1:.It Fl -no-rosegment Note the line: /usr/src/stand/i386/Makefile.inc:LDFLAGS.lld+=3D = -Wl,--no-rosegment which seems to be the only place that the --no-rosegment could be from. The error report detail is: =3D=3D=3D> stand/i386/mbr (all) --- machine --- machine -> /workspace/src/sys/i386/include --- x86 --- x86 -> /workspace/src/sys/x86/include --- mbr.o --- as --defsym FLAGS=3D0x80 --32 -o mbr.o = /workspace/src/stand/i386/mbr/mbr.s --- mbr --- /usr/local/bin/x86_64-unknown-freebsd11.1-gcc -isystem = /workspace/obj/workspace/src/amd64.amd64/tmp/usr/include = -L/workspace/obj/workspace/src/amd64.amd64/tmp/usr/lib = -B/workspace/obj/workspace/src/amd64.amd64/tmp/usr/lib = --sysroot=3D/workspace/obj/workspace/src/amd64.amd64/tmp = -B/workspace/obj/workspace/src/amd64.amd64/tmp/usr/bin -O2 -pipe = -I/workspace/src/stand/i386/btx/lib -nostdinc = -I/workspace/obj/workspace/src/amd64.amd64/stand/libsa32 = -I/workspace/src/stand/libsa -D_STANDALONE -I/workspace/src/sys = -Ddouble=3Djagged-little-pill -Dfloat=3Dfloaty-mcfloatface = -DLOADER_DISK_SUPPORT -m32 -mcpu=3Di386 -ffreestanding -mno-mmx -mno-sse = -msoft-float -march=3Di386 -I. -std=3Dgnu99 -Wsystem-headers -Werror = -Wno-pointer-sign -Wno-error=3Daddress -Wno-error=3Darray-bounds = -Wno-error=3Dattributes -Wno-error=3Dbool-compare -Wno-error=3Dcast-align = -Wno-error=3Dclobbered -Wno-error=3Denum-compare -Wno-error=3Dextra = -Wno-error=3Dinline -Wno-error=3Dlogical-not-parentheses = -Wno-error=3Dstrict-aliasing -Wno-error=3Duninitialized = -Wno-error=3Dunused-but-set-variable -Wno-error=3Dunused-function = -Wno-error=3Dunused-value -Wno-error=3Dmisleading-indentation = -Wno-error=3Dnonnull-compare -Wno-error=3Dshift-negative-value = -Wno-error=3Dtautological-compare -Wno-error=3Dunused-const-variable = -mpreferred-stack-boundary=3D2 -e start -Ttext 0x600 = -Wl,-N,-S,--oformat,binary -nostdlib -Wl,--no-rosegment -o mbr mbr.o =20 x86_64-unknown-freebsd11.1-gcc: warning: '-mcpu=3D' is deprecated; use = '-mtune=3D' or '-march=3D' instead /usr/local/bin/x86_64-freebsd-ld: unrecognized option '--no-rosegment' /usr/local/bin/x86_64-freebsd-ld: use the --help option for usage = information collect2: error: ld returned 1 exit status *** [mbr] Error code 1 It appears that, for a amd64-gcc build that is using = /usr/local/bin/x86_64-freebsd-ld via x86_64-unknown-freebsd11.1-gcc , for some reason LDFLAGS.lld content = is using used. This suggests that in: /usr/src/share/mk/bsd.sys.mk:LDFLAGS+=3D ${LDFLAGS.${LINKER_TYPE}} LINKER_TYPE is "lld". In turn that would seem to be from: /usr/src/share/mk/bsd.linker.mk:${X_}LINKER_TYPE=3D lld Or with more context and indented but inside a ".for ld X_ in LD $${_empty_var_} XLD X_": .if ${ld} =3D=3D "LD" || (${ld} =3D=3D "XLD" && ${XLD} !=3D ${LD}) .if !defined(${X_}LINKER_TYPE) || !defined(${X_}LINKER_VERSION) _ld_version!=3D (${${ld}} --version || echo none) | head -n 1 . . . .elif ${_ld_version:[1]} =3D=3D "LLD" ${X_}LINKER_TYPE=3D lld _v=3D ${_ld_version:[2]} .else . . . .endif .else . . . .endif # ${ld} =3D=3D "LD" || (${ld} =3D=3D "XLD" && ${XLD} !=3D ${LD}) So it seems that ${${ld}} picked out lld for assigning _ld_version . In turn, the following what apparently executed: .elif ${_ld_version:[1]} =3D=3D "LLD" ${X_}LINKER_TYPE=3D lld _v=3D ${_ld_version:[2]} But for (again): /usr/src/share/mk/bsd.sys.mk:LDFLAGS+=3D ${LDFLAGS.${LINKER_TYPE}} that implies that the case involved is: ld X_ in LD $${_empty_var_} It looks like the LDFLAGS+=3D should not be using that for this type of build. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-amd64@freebsd.org Sun Apr 22 16:12:59 2018 Return-Path: Delivered-To: freebsd-amd64@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 C26BEFAB6EF for ; Sun, 22 Apr 2018 16:12:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 5DD2A78F90 for ; Sun, 22 Apr 2018 16:12:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 1D1BAFAB6EA; Sun, 22 Apr 2018 16:12:59 +0000 (UTC) Delivered-To: amd64@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 0A97AFAB6E4 for ; Sun, 22 Apr 2018 16:12:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 96C4E78F8C for ; Sun, 22 Apr 2018 16:12:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id D687620EAA for ; Sun, 22 Apr 2018 16:12:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w3MGCv9q030360 for ; Sun, 22 Apr 2018 16:12:57 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w3MGCvrM030358 for amd64@FreeBSD.org; Sun, 22 Apr 2018 16:12:57 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: amd64@FreeBSD.org Subject: [Bug 211001] HP Proliant: BIOS problem with 3TB+ disks Date: Sun, 22 Apr 2018 16:12:58 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: eugen@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc bug_status bug_file_loc resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Apr 2018 16:12:59 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211001 Eugene Grosbein changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eugen@freebsd.org Status|New |Closed URL| |https://wiki.freebsd.org/HP | |BIOS3TBHDD Resolution|--- |FIXED --- Comment #4 from Eugene Grosbein --- The patch has been committed to head as r331718 and has been MFC'd to stabl= e/11 as r332056, prior to the release of 11.2. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-amd64@freebsd.org Sat Apr 28 13:39:54 2018 Return-Path: Delivered-To: freebsd-amd64@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 61807FAF713; Sat, 28 Apr 2018 13:39:54 +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 E7CBD877CA; Sat, 28 Apr 2018 13:39:53 +0000 (UTC) (envelope-from freebsd@disroot.org) Received: from localhost (localhost [127.0.0.1]) by disroot.org (Postfix) with ESMTP id 390422E0EB; Sat, 28 Apr 2018 15:39:52 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1524922792; bh=iATcv+amWP0kdwBGj+iD29ylM0yfx14bRWMceIm2QPE=; h=To:From:Subject:Date; b=jv9zCI6oHJ5lI9XvR2mVKzFlgp/VXroeit/DvwgELOY/GkvfVs0aCVrdBkz/aqBMc FrLoe9ho4+Iw2DWS2QShMLad5vRxnKz668radXAUsi+b6u48mpyW56Svc7YtNBQldY J8eEDRD/ZTfduuWWKYJLdm/HM+T2PibhVciJonVpG3lB7C19etG4JOPpMG9basUAfr XcPOMXxF7Tl+eUnlKkzV9zDFSi3wHUHk39lnVotB+W+V3i0r03QdhnDVd9gJ3A8flk c9rdEJk3sVC3girhOSiHdYiOQd/l0FufedG53Vd4ldFr/v9EuiSg/nH2kr0SkesL56 ikx0eVlfcHG/A== 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 7kitWTG6r0Qm; Sat, 28 Apr 2018 15:39:50 +0200 (CEST) To: freebsd-amd64@freebsd.org, freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1524922790; bh=iATcv+amWP0kdwBGj+iD29ylM0yfx14bRWMceIm2QPE=; h=To:From:Subject:Date; b=RUamFca7khtnVqIsxqDWP7pZFXxDgKxtj/PZ+c1mMeky2hMSV4rIxbT9hFjAdt1ZV C9WDICeFrSum27b5rQa+MhruDhfXQ29XLEUxpClvxUY+YHPeqLvs3ei/Is8Hrs+QVk AGG0gTz08pdh6VA45vMzyBiEpneNZDcwirT4KXrS9QgzBy3asCIaEPXI5CLimnKCQw 9ZWzxLU8a9QJAx92YxmYzCZzpaMqR7poVV8ccSzmRZzmPuiMdk+nea7xs5x6zbekBE PAPYna9Bc5bt6qiFcc4fQP7MiYlG9f4CQ3PykEeyVWakDrebxIdT5/cnsM/vrFXzv8 oNJv98aKl4vgQ== From: "Peter G." Subject: Can we please finally solve Dell's racadm for FreeBSD? Advice needed Message-ID: <5eca3020-4b9c-dd43-8cf0-066d63a92521@disroot.org> Date: Sat, 28 Apr 2018 15:39:39 +0200 Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Apr 2018 13:39:54 -0000 Dear everybody, regarding: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201799 would somebody knowledgeable be kind enough to advice and/or help with bringing Dell racadm client/tools to FreeBSD? What is the problem with ipmi enumeration Dan mentioned on his commit? What is in the first place desired is local access to local hardware via standard racadm client. Local management is the "big kahuna" here. There were several attempts over the years, yet everything waned away without any solid results. Dell hardware is constantly mentioned on the lists or in the forums, so clearly many of us use it. I myself manage several Dell servers. The lack of local racadm for FreeBSD is daring. On my own and out of my pocket I will offer 50 EUR in Bitcoin to anybody who will solve the problem, i.e. provide a working racadm client which can access and manage local hardware. Of course anybody else is welcome to chime in. I am willing to put that in escrow with a trusted member of the community. Please let me know what to do. Many thanks! -- PG From owner-freebsd-amd64@freebsd.org Sat Apr 28 14:13:24 2018 Return-Path: Delivered-To: freebsd-amd64@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 AD0DCFB0692; Sat, 28 Apr 2018 14:13:24 +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 2EFC48D9E5; Sat, 28 Apr 2018 14:13:23 +0000 (UTC) (envelope-from freebsd@disroot.org) Received: from localhost (localhost [127.0.0.1]) by disroot.org (Postfix) with ESMTP id 201EF2E075; Sat, 28 Apr 2018 16:13:22 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1524924802; bh=GM7lVvArRv/I63Q4hw5aY0MHRfhsKmN460ejXCBTqqk=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=JJFloeGIwFEqpgjRdI0zi6+4mj+OAg1f1ahmqLW2vTKDAffJGuE63fXVP8hsnr1Cm 7lsiVMELO5raXZbq3oa0/dFUWv0tGiZ2+ciKEzF7pkrf303FcfkNlkNx0acj4gFIuJ TUv/cztBwO2zbyfTpnHAlE9JWHdgcuyhvd6tzYJmGS8wzlp0h/lzr8/on6wyMYbXx2 ogRgO5U5EDfX5dUJvtzzCzWk1jliu6PpNOCBvvxx54eLFOATJoVgujWjeVCwyZCoFU xuhwl63yCc4Y1kMqiiykQVo8kmkV3E5BXqI3p7xKiokTbuDqthaRb8594M74izdk1Z SHps6YMn9/btw== 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 X1424zeqgOKI; Sat, 28 Apr 2018 16:13:20 +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=1524924800; bh=GM7lVvArRv/I63Q4hw5aY0MHRfhsKmN460ejXCBTqqk=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=ldkJC4l7zs2yM2elkfm27NzXxlxTu5Bi0sJFza0rH5tcqfZZ4xN2jDpOYkGZjwrG9 oxvOQY9ooC33X+yTobsMbzWVGow060CRiei2iYJw5E+aoXm8nyIqSvzIkiPfo019I+ nKs7BW0ebv0PnqJhvEXk4KXXpybjfjKRP2yB20vVBr6N1im7TW+/8uU/F54msMqfEC Ri8To82M6sRTyAAEoV7/7Zvjh3r+XDRo2ycmyObDbKy7wkquF/JArjlZiBqZhD8hx0 Qf4wn/j4b3hPHU0qhmEijbV0cD61QKwQwHgR9yxb6dE0ZLbhBF6D8sdJD1fzNJr9Ng iLzeYmexUdkzw== To: mark@exonetric.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: <1c82e4d6-8fb6-3191-9e2f-ff7478c1284e@disroot.org> Date: Sat, 28 Apr 2018 16:13:09 +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-amd64@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Apr 2018 14:13:24 -0000 On 28/04/2018 15:56, Mark Blackman wrote: >> On my own and out of my pocket I will offer 50 EUR in Bitcoin to anybody >> who will solve the problem, i.e. provide a working racadm client which >> can access and manage local hardware. Of course anybody else is welcome >> to chime in. I am willing to put that in escrow with a trusted member of >> the community. Please let me know what to do. > > A kind offer, and much better than nothing. I think more like Nx1000 Euros > cash would be a more realistic offer. Maybe a kickstarter campaign or similar > to fund it? If all the Dell server managers clubbed together, I bet they could > easily find that much. Alternately persuade the FreeBSD foundation to put their > focus behind it. I don't think this much exposure and/or funds is/are really needed here. The proposed port, especially after Dan's commits, is already functional. The local access is missing. I bet if anybody with knowledge what to do offers a bit of advice how to solve it, it will be solved in no time. I'd say this is more about know-how than funds. -- PG From owner-freebsd-amd64@freebsd.org Sat Apr 28 13:54:35 2018 Return-Path: Delivered-To: freebsd-amd64@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 57DA1FAFCEF for ; Sat, 28 Apr 2018 13:54:35 +0000 (UTC) (envelope-from nbari@codigo.io) Received: from mail-wr0-x232.google.com (mail-wr0-x232.google.com [IPv6:2a00:1450:400c:c0c::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AB64F8A70F for ; Sat, 28 Apr 2018 13:54:34 +0000 (UTC) (envelope-from nbari@codigo.io) Received: by mail-wr0-x232.google.com with SMTP id u18-v6so4192840wrg.3 for ; Sat, 28 Apr 2018 06:54:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=codigo.io; s=google; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=nuO8UwLub9DgmZv+m8er805wrQ2RUCZzFYAe+TiChwA=; b=LVNqyNNWrHkE7g22+b+pgaWh4+fqgt7J/voia+FwHBJMrCl/NYOSGkbmE/LmdmIx+0 e26UsnrdlVmjfOSswzwEIwCDvNx1fkdJzySjoLexfO0y9/Bf0c4adyU32/3gO2pOpZQc D+Nh5jksxnJ6K88W5toW4y6rLtrFqYR/Dnjg7wKhlJYMThf5h87QMI/s0x1NOHoZlwcF hIoDzYlsxIS/UAJYCX3niSUbZPjGVFdaFNhEE05Q+Qc1ob5fMniPQZ6e4p6mkmZECbHX mg3PJzimRhxZ1qPFG33Tu6yuLDMiojqbpAlHJLz8dutwxrsFCfEm3v0Yn9W0tDy0CzfS irYg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tequila.io; s=google; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=nuO8UwLub9DgmZv+m8er805wrQ2RUCZzFYAe+TiChwA=; b=DzIjkrp295IJmKrP250mZdRUy0l2ARuUc/O8UdvhWpj8QRjIaiUIz+ntFJWR3tVToX D09kXiLesskZLy3FUmC8OKrzXWbUMkMCEiDrGQPpXjc1PjkWOXUY8VkizHt3zSAKa5SL MAaWV+3o0dkNiTO3Er4L/UHTyvE1E6kkjtga/3eD+L+qwLjvTLxOMQxNqdZ/EIztU0Yd P5692+KlXNVTkMSS44EP7zEYjunVDFioxEsa9NuHq4PeQ1Y//57FnWEnfyeMxRCoWDO4 N10zxWSdE22gd/9UksIDaCgEbWoWTc+qNGbuApoy7xnuvsVUbFv8Xf28TO8/8vBzZXp1 WtUA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=nuO8UwLub9DgmZv+m8er805wrQ2RUCZzFYAe+TiChwA=; b=f5ERDjGbjUMJaU8NObhuAPb2Zf0ndBpCTTbHFFLnR+J5jwGY0FPVInFP+rsPjVNzv/ ahCknlBQtKtGE9eGapkWbbhPoYrdk3oW2kWV+E0L2nqT9P0iU/K3v5gTk1noZZEQzfkq yJtaLqzap2dKlVoXwmW6Dw2/l0CLxiqlGIhsIrfI6A/wknX/YBSDKAQBW+zfrTtkeMP8 6gc2QNEefx0YFr3naqvyu98TrarDERmNitnLvcslSodavXezM5iTHkKe6POJBiXXvMd0 3tJSTB6+T0QI3mDwF+0HurT9w/GCCwJjyU2DInBzAhPURpO4nOdC+pRpJJyMcBsqowmu znQA== X-Gm-Message-State: ALQs6tA8DsmYSnGN0zOeyQWIEvuR8s4nwLAg9YU1eFboZYtUqzV5ro5Q Bouj59c0N5xfQDblJ2Vb20h/OsUpf7Js25yXvL2HcQ== X-Google-Smtp-Source: AB8JxZr6hxhOoEeqIWPYcipfGkLjeF31Er4GAYTNdSc3mVsG1BvOJB7t+G1eRgkrX2bhAIQPvosU76rSfUOQMbvkL/I= X-Received: by 2002:adf:a3d7:: with SMTP id m23-v6mr4703136wrb.209.1524923673588; Sat, 28 Apr 2018 06:54:33 -0700 (PDT) MIME-Version: 1.0 Sender: nbari@codigo.io Received: by 10.223.176.5 with HTTP; Sat, 28 Apr 2018 06:54:33 -0700 (PDT) X-Originating-IP: [82.197.160.85] In-Reply-To: <5eca3020-4b9c-dd43-8cf0-066d63a92521@disroot.org> References: <5eca3020-4b9c-dd43-8cf0-066d63a92521@disroot.org> From: Nicolas Embriz Date: Sat, 28 Apr 2018 15:54:33 +0200 X-Google-Sender-Auth: j3spVbarGUQd5ZY_OwUZr4-qumo Message-ID: Subject: Re: Can we please finally solve Dell's racadm for FreeBSD? Advice needed To: "Peter G." Cc: freebsd-amd64@freebsd.org, FreeBSD Hackers , freebsd-hardware@freebsd.org X-Mailman-Approved-At: Sat, 28 Apr 2018 14:52:05 +0000 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Apr 2018 13:54:35 -0000 Regarding this topic I have a Dell Power 2900 that I could donate for testing more in detail this issues. If interested please PM. Regards. On Sat, Apr 28, 2018 at 3:39 PM, Peter G. wrote: > Dear everybody, > > regarding: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201799 > > would somebody knowledgeable be kind enough to advice and/or help with > bringing Dell racadm client/tools to FreeBSD? What is the problem with > ipmi enumeration Dan mentioned on his commit? What is in the first place > desired is local access to local hardware via standard racadm client. > Local management is the "big kahuna" here. > > There were several attempts over the years, yet everything waned away > without any solid results. Dell hardware is constantly mentioned on the > lists or in the forums, so clearly many of us use it. I myself manage > several Dell servers. The lack of local racadm for FreeBSD is daring. > > On my own and out of my pocket I will offer 50 EUR in Bitcoin to anybody > who will solve the problem, i.e. provide a working racadm client which > can access and manage local hardware. Of course anybody else is welcome > to chime in. I am willing to put that in escrow with a trusted member of > the community. Please let me know what to do. > > Many thanks! > -- > PG > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-amd64@freebsd.org Sat Apr 28 14:05:21 2018 Return-Path: Delivered-To: freebsd-amd64@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 B1666FB01B8; Sat, 28 Apr 2018 14:05:21 +0000 (UTC) (envelope-from mark@exonetric.com) Received: from relay.exonetric.net (relay0.exonetric.net [178.250.72.161]) by mx1.freebsd.org (Postfix) with ESMTP id 581068AD21; Sat, 28 Apr 2018 14:05:20 +0000 (UTC) (envelope-from mark@exonetric.com) Received: from [192.168.10.198] (90.69.187.81.in-addr.arpa [81.187.69.90]) by relay.exonetric.net (Postfix) with ESMTPSA id 7F2E42B10B; Sat, 28 Apr 2018 14:56:16 +0100 (BST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: Can we please finally solve Dell's racadm for FreeBSD? Advice needed From: Mark Blackman In-Reply-To: <5eca3020-4b9c-dd43-8cf0-066d63a92521@disroot.org> Date: Sat, 28 Apr 2018 14:56:14 +0100 Cc: freebsd-amd64@freebsd.org, freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <5eca3020-4b9c-dd43-8cf0-066d63a92521@disroot.org> To: "Peter G." X-Mailer: Apple Mail (2.3445.6.18) X-Mailman-Approved-At: Sat, 28 Apr 2018 15:57:22 +0000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Apr 2018 14:05:21 -0000 > On 28 Apr 2018, at 14:39, Peter G. wrote: >=20 > Dear everybody, >=20 > regarding: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D201799 >=20 > would somebody knowledgeable be kind enough to advice and/or help with > bringing Dell racadm client/tools to FreeBSD? What is the problem with > ipmi enumeration Dan mentioned on his commit? What is in the first = place > desired is local access to local hardware via standard racadm client. > Local management is the "big kahuna" here. >=20 > There were several attempts over the years, yet everything waned away > without any solid results. Dell hardware is constantly mentioned on = the > lists or in the forums, so clearly many of us use it. I myself manage > several Dell servers. The lack of local racadm for FreeBSD is daring. >=20 > On my own and out of my pocket I will offer 50 EUR in Bitcoin to = anybody > who will solve the problem, i.e. provide a working racadm client which > can access and manage local hardware. Of course anybody else is = welcome > to chime in. I am willing to put that in escrow with a trusted member = of > the community. Please let me know what to do. A kind offer, and much better than nothing. I think more like Nx1000 = Euros=20 cash would be a more realistic offer. Maybe a kickstarter campaign or = similar to fund it? If all the Dell server managers clubbed together, I bet they = could easily find that much. Alternately persuade the FreeBSD foundation to = put their focus behind it. - Mark=