From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Moger, Babu" <Babu.Moger@lsi.com>
Cc: Seokmann Ju <seokmann.ju@qlogic.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
device-mapper development <dm-devel@redhat.com>
Subject: RE: qla2xxx 0000:03:0c.0: Firmware image unavailable
Date: Thu, 22 Jan 2009 08:56:05 -0600 [thread overview]
Message-ID: <1232636165.3569.0.camel@localhost.localdomain> (raw)
In-Reply-To: <E463DF2B2E584B4A82673F53D62C2EF45CEAB550@cosmail01.lsi.com>
On Thu, 2009-01-22 at 07:14 -0700, Moger, Babu wrote:
> Yes, the naming conventions look good. Here is the output of ls
>
> -rw-r--r-- 1 root root 76802 Jan 21 16:41 ql2100_fw.bin
> -rw-r--r-- 1 root root 84566 Jan 21 16:41 ql2200_fw.bin
> -rw-r--r-- 1 root root 125088 Jan 21 16:41 ql2300_fw.bin
> -rw-r--r-- 1 root root 135896 Jan 21 16:41 ql2322_fw.bin
> -rw-r--r-- 1 root root 228056 Jan 21 16:41 ql2400_fw.bin
> -rw-r--r-- 1 root root 239052 Jan 21 16:41 ql2400_fw.bin_mid
> -rw-r--r-- 1 root root 200064 Jan 21 16:41 ql2500_fw.bin
> -rw-r--r-- 1 root root 219924 Jan 21 16:41 ql2500_fw.bin_mid
OK, so logical choice number 2 is that udev, which feeds the firmware
into the kernel, isn't working for you. This is really a distribution
problem.
James
prev parent reply other threads:[~2009-01-22 14:56 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 4:05 [PATCH] Make sure the state of a path is set properly when controller is swapped from passive to active Chandra Seetharaman
2008-11-10 23:17 ` [PATCH] scsi_dh: Adding LSI vendor and product ids in rdac device list Moger, Babu
2008-11-24 0:04 ` James Bottomley
2008-11-24 15:06 ` Moger, Babu
2008-11-11 0:45 ` DM does not activate the paths if there are more than one path in path group during failover Moger, Babu
2008-11-11 0:59 ` Alasdair G Kergon
2008-11-11 17:13 ` Moger, Babu
2008-11-11 21:00 ` Chandra Seetharaman
2008-11-13 23:48 ` [RFC][PATCH] Handle multipath paths in a path group properly during pg_init (was "RE: [dm-devel] DM does not activate the paths if there are more than one path in path group during failover") Chandra Seetharaman
2008-11-14 0:12 ` [RFC][PATCH] Handle multipath paths in a path group properly during pg_init (was "RE: " Alasdair G Kergon
2008-11-14 19:08 ` [RFC][PATCH] Handle multipath paths in a path group properly during pg_init (was "RE: [dm-devel] " Chandra Seetharaman
2008-11-14 19:34 ` [RFC][PATCH] Handle multipath paths in a path group properly during pg_init (was "RE: " Alasdair G Kergon
2008-11-14 20:24 ` [RFC][PATCH] Handle multipath paths in a path group properly during pg_init (was "RE: [dm-devel] " Chandra Seetharaman
2008-11-11 2:06 ` DM does not activate the paths if there are more than one path in path group during failover Chandra Seetharaman
2008-11-11 17:07 ` Moger, Babu
2008-11-11 17:10 ` Chandra Seetharaman
2008-11-11 17:28 ` Moger, Babu
2009-01-22 0:00 ` qla2xxx 0000:03:0c.0: Firmware image unavailable Moger, Babu
2009-01-22 0:26 ` Seokmann Ju
2009-01-22 14:14 ` Moger, Babu
2009-01-22 14:39 ` Sudhakar Pannerselvam
2009-01-22 15:20 ` Moger, Babu
2009-01-22 16:46 ` Dave Holland
2009-01-23 0:15 ` [dm-devel] " Moger, Babu
2009-01-23 6:22 ` Sudhakar Pannerselvam
2009-01-23 15:04 ` James Bottomley
2009-01-25 4:22 ` Mike Snitzer
2009-01-22 14:56 ` James Bottomley [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1232636165.3569.0.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=Babu.Moger@lsi.com \
--cc=dm-devel@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=seokmann.ju@qlogic.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox