From nobody Thu Jul 27 10:05:39 2023 X-Original-To: questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RBRGz1fSgz4nss4 for ; Thu, 27 Jul 2023 10:05:47 +0000 (UTC) (envelope-from yuri@aetern.org) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4RBRGy5FF0z4Dqh for ; Thu, 27 Jul 2023 10:05:46 +0000 (UTC) (envelope-from yuri@aetern.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=aetern.org header.s=fm3 header.b=RNwHtzdh; dkim=pass header.d=messagingengine.com header.s=fm3 header.b="R lyhkhD"; spf=pass (mx1.freebsd.org: domain of yuri@aetern.org designates 66.111.4.26 as permitted sender) smtp.mailfrom=yuri@aetern.org Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id C132C5C012D for ; Thu, 27 Jul 2023 06:05:43 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Thu, 27 Jul 2023 06:05:43 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aetern.org; h=cc :content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm3; t= 1690452343; x=1690538743; bh=ayRqqXl7Ul9s0DFk7W0UgGvLxv677T9E3xb MDKTv7ig=; b=RNwHtzdhPSjIvJ0Qsh+q5UGfzsWeWbUd0OCJPgWWr5mjkhaGttK s5OyxWZqxY8VN7gC1yjFaSzu+r/Pvc4DzWCgiveIDmwO2jp/06VkYFviB6RNQYRG 1azTavfTKBoCz2C268DXiwSWy3osHWO4bqTX/EkV0ail+suI9CFs3unUNeqHQ1Aw 70QZ+Y+EhpLfxu5llyoiNJRkmHBIkrcLb6kxZjMfKxigC9MsTNC3xD1jqalmP//I KFC7F0TmcoS8HtSKxvBZQDaWaIPkmofFvzwG/WF0CbbspdEN4GEoppmcOT+ljn9X FCgyDxG7V8B6hrbmn2GjQ+toQY3pF3lOi7w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1690452343; x= 1690538743; bh=ayRqqXl7Ul9s0DFk7W0UgGvLxv677T9E3xbMDKTv7ig=; b=R lyhkhD+XuDskuWHUtZmz3DMgMb5Rz7hOEcxD00va1rLl2aWpzczUh4hBOkBW9x9W USw+PP7KyFBC+ART9bUSUR+obcLN76iyJqesf5PyNQbJENVhvrOBAX0tSuKaGyUC P0OsStTIkHQ6T7chvjSuLF5xzkVuGV3m8KqFhD1ivSxSDaHWEF3YfvJS71XXQiUv EKhRZAPiN3XxkLwWcZ57fjTihXQQquBZ7HqAAfAQUuj7zOLNL/DqVBRrBqnEVW51 mKRoFuvksoA89On4z0mZs3Uysw9rvAoYCu7n8jd+jzHA7OwF/gVi019zmw6Mi6aC 8W2i8Bk4J2jKefc1Puoog== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrieefgddugeelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtke ertddtvdejnecuhfhrohhmpegjuhhrihcuoeihuhhrihesrggvthgvrhhnrdhorhhgqeen ucggtffrrghtthgvrhhnpeetkeevgfefteejheeifeduiedvkedukeetudffgfejlefhtd ejkeelhedvkeduudenucffohhmrghinhepfhhrvggvsghsugdrohhrghenucevlhhushht vghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpeihuhhrihesrggvthgvrh hnrdhorhhg X-ME-Proxy: Feedback-ID: i0d79475b:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Thu, 27 Jul 2023 06:05:43 -0400 (EDT) Message-ID: <81418a25-0aaa-8578-e3c6-32f666b3ef65@aetern.org> Date: Thu, 27 Jul 2023 12:05:39 +0200 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: isp support for QLogic 2722/firmware? Content-Language: en-US To: questions@freebsd.org References: <5cf2f487-a5d2-55b7-49df-51690ac22412@aetern.org> <6on92p68-rpq2-594p-8q5s-979ns8p12653@sez2.ghz.qr> From: Yuri In-Reply-To: <6on92p68-rpq2-594p-8q5s-979ns8p12653@sez2.ghz.qr> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4RBRGy5FF0z4Dqh X-Spamd-Bar: / X-Spamd-Result: default: False [0.61 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.26]; R_DKIM_ALLOW(-0.20)[aetern.org:s=fm3,messagingengine.com:s=fm3]; XM_UA_NO_VERSION(0.01)[]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; local_wl_from(0.00)[yuri@aetern.org]; DKIM_TRACE(0.00)[aetern.org:+,messagingengine.com:+]; ASN(0.00)[asn:19151, ipnet:66.111.4.0/24, country:US] X-Rspamd-Pre-Result: action=no action; module=multimap; Matched map: local_wl_from Joerg Pulz wrote: > On Wed, 26 Jul 2023, Brian McGovern wrote: > >> >> I'm curious if anyone has this working, and if so, any chance I can >>>> obtain the firmware or process you are using? I'm hoping its something >>>> like flashing an image to the card with some other OS first. TIA >> >>> Support for this (and some other newer HBAs) was added recently to >>> 14-CURRENT, see latest commits in >>> https://cgit.freebsd.org/src/log/sys/dev/isp >> . >> >> Its getting late locally, so take this with a grain of salt... I'm pretty >> sure I grabbed the main branch from git, and effectively did a MFC >> (working >> with 13.2-RELEASE). Looking at the diffs you pointed me to vs. whats >> on the >> disk, it looks like I have the latest bits, but I'll check it again >> tomorrow to be sure. Its possible I'm missing something. >> >> The problem is consistent. When the adapters try to come up, and I'm >> using >> them as kernel modules right now just so I can cycle through testing >> faster, I continue to get >> >> "isp_2700 could not load firmware image, error 2" >> >> if I don't hack up the ispfw driver/module to have something that >> meets the >> name requirements for "isp_2700" firmware. >> >> and if I try to create a firmware module it can install with the >> bk014519.bin firmware file, it'll happily find something for firmware, >> but >> then throws a: >> isp0: Mailbox Command (0xb) Timeout (100000us) (isp_reset:373) >> isp0: Mailbox Command 'LOAD RISC RAM' failed (TIMEOUT) >> isp0: F/W download failed >> isp0: isp_reinit: cannot reset card >> device_attach: isp0 attach returned 6 >> >> So, what I think is missing is either a.) finding a good firmware image >> that I can load via the driver, or b.) figuring out how to flash firmware >> to the adapter via some other means, and figure out how to skip the load >> step when the driver starts. Hence why I'm hoping to find someone who has >> the card working, so I can clone their process. >> >> But, if anyone has other ideas, I'm all ears. >> >>     -Brian >> >> On Wed, Jul 26, 2023 at 8:55?PM Yuri wrote: >> >>> Brian McGovern wrote: >>>> Quick question about the isp and card support. I have an HPE branded >>>> Qlogic ISP 2722 that I'm trying to bring online. Following the various >>>> tutorials I loaded ispfw, then the isp driver. I got an error message >>>> "isp_2700 could not load firmware image, error 2". The boards don't >>>> come >>>> online. >>>> >>>> Looking at the man page, it appears supported on the Qlogic >>>> 2740/2742/2764 (aka 2722/2714) line, so I tried to chase down some >>>> firmware and duplicate the isp_2400 and isp_2500 functionality with the >>>> .bin file. Now, it tries to load but I get a firmware loading failure. >>>> I'm assuming that either current versions and .bin files are >>>> incompatible with the other loading processes, or I just screwed >>>> something up in all the translation (I found a bk014519.bin file). >>>> >>>> I'm curious if anyone has this working, and if so, any chance I can >>>> obtain the firmware or process you are using? I'm hoping its something >>>> like flashing an image to the card with some other OS first. TIA >>> >>> Support for this (and some other newer HBAs) was added recently to >>> 14-CURRENT, see latest commits in >>> https://cgit.freebsd.org/src/log/sys/dev/isp. > > Those HBAs are supported since 2018-02-28. > So support for them is in 13.2 - I have systems running with those: > > # uname -r > 13.2-RELEASE > > # dmesg -a |grep isp > isp0: mem > 0x93302000-0x93302fff,0x93300000-0x93301fff,0x93200000-0x932fffff at > device 0.0 on pci1 Yeah, I read the commit message wrong (2722 instead of 2772), sorry for the noise.