All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rajat Jain <rajat.noida.india@gmail.com>
To: Andrew Vasquez <andrew.vasquez@qlogic.com>
Cc: Greg KH <greg@kroah.com>,
	kernelnewbies@nl.linux.org, linux-scsi@vger.kernel.org,
	linux-newbie@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Incorrect driver getting loaded for Qlogic FC-HBA
Date: Thu, 28 Jul 2005 19:36:15 +0900	[thread overview]
Message-ID: <b115cb5f050728033662fb288a@mail.gmail.com> (raw)
In-Reply-To: <20050727181135.GI7114@plap.qlogic.org>

> > > A similar problem was noted with RHEL4, it seems the modules.pcimap
> > > and pci.ids file were correct, but the pcitable file contained entries
> > > for all ql[ae]23xx based HBAs to load qla2300.ko.
> > >
> > > It's my understanding that this was fixed for RHEL4 U1.  Which distro
> > > are you using?  If you are using RHEL, and are still having problems,
> > > I'd suggest you file a report with Redhat.
> > >
> > > Regards,
> > > Andrew Vasquez
> > >
> >
> > BINGO! I AM using RHEL 4. So does that mean I can rectify the problem
> > by making appropriate changes to "pcitable" file?
> 
> I'm trying to get a firm answer from the folks who originally
> discvoered the problem some time back, it seems you have two options:

Hey Thanks. I would really appreciate if you could update list/me on
it IF you get any updates (I know its too much pain).


>  - (post installation) modify the /etc/modprobe.conf to and rename the
>   qla2300 entry to qla2322 (i.e.):
> 
>        alias scsi_hostadapter1 qla2322
> 
>   modify the modules.pcimap table to load qla2322 for the 2322
>   device-id:
> 
>        qla2300         0x00001077      0x00002322      ...
> 
>   to:
> 
>        qla2322         0x00001077      0x00002322      ...
> 
> 
> Beyond that, I'd suggest you log a report with Redhat, as that's the
> extent of the workaround knowledge without going to RHEL4U1.
> 
> Hope this helps,
> Andrew Vasquez
> 

THANKS. It worked for me, for time being. 
In the mean time, I plan to file  report with RedHat and will update
list as and when I get any response.

regards,

Rajat
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

WARNING: multiple messages have this Message-ID (diff)
From: Rajat Jain <rajat.noida.india@gmail.com>
To: Andrew Vasquez <andrew.vasquez@qlogic.com>
Cc: Greg KH <greg@kroah.com>,
	kernelnewbies@nl.linux.org, linux-scsi@vger.kernel.org,
	linux-newbie@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Incorrect driver getting loaded for Qlogic FC-HBA
Date: Thu, 28 Jul 2005 19:36:15 +0900	[thread overview]
Message-ID: <b115cb5f050728033662fb288a@mail.gmail.com> (raw)
In-Reply-To: <20050727181135.GI7114@plap.qlogic.org>

> > > A similar problem was noted with RHEL4, it seems the modules.pcimap
> > > and pci.ids file were correct, but the pcitable file contained entries
> > > for all ql[ae]23xx based HBAs to load qla2300.ko.
> > >
> > > It's my understanding that this was fixed for RHEL4 U1.  Which distro
> > > are you using?  If you are using RHEL, and are still having problems,
> > > I'd suggest you file a report with Redhat.
> > >
> > > Regards,
> > > Andrew Vasquez
> > >
> >
> > BINGO! I AM using RHEL 4. So does that mean I can rectify the problem
> > by making appropriate changes to "pcitable" file?
> 
> I'm trying to get a firm answer from the folks who originally
> discvoered the problem some time back, it seems you have two options:

Hey Thanks. I would really appreciate if you could update list/me on
it IF you get any updates (I know its too much pain).


>  - (post installation) modify the /etc/modprobe.conf to and rename the
>   qla2300 entry to qla2322 (i.e.):
> 
>        alias scsi_hostadapter1 qla2322
> 
>   modify the modules.pcimap table to load qla2322 for the 2322
>   device-id:
> 
>        qla2300         0x00001077      0x00002322      ...
> 
>   to:
> 
>        qla2322         0x00001077      0x00002322      ...
> 
> 
> Beyond that, I'd suggest you log a report with Redhat, as that's the
> extent of the workaround knowledge without going to RHEL4U1.
> 
> Hope this helps,
> Andrew Vasquez
> 

THANKS. It worked for me, for time being. 
In the mean time, I plan to file  report with RedHat and will update
list as and when I get any response.

regards,

Rajat

  reply	other threads:[~2005-07-28 10:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-25  2:02 Incorrect driver getting loaded for Qlogic FC-HBA Rajat Jain
2005-07-25  2:02 ` Rajat Jain
2005-07-26  0:06 ` Greg KH
2005-07-26  0:06   ` Greg KH
2005-07-26  4:16   ` Rajat Jain
2005-07-26 15:52     ` Andrew Vasquez
2005-07-27  6:01       ` Rajat Jain
2005-07-27 18:11         ` Andrew Vasquez
2005-07-27 18:11           ` Andrew Vasquez
2005-07-28 10:36           ` Rajat Jain [this message]
2005-07-28 10:36             ` Rajat Jain

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=b115cb5f050728033662fb288a@mail.gmail.com \
    --to=rajat.noida.india@gmail.com \
    --cc=andrew.vasquez@qlogic.com \
    --cc=greg@kroah.com \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-newbie@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.