Bug 4222 - Perceptive Solution's 3rd party SCSI drivers
Summary: Perceptive Solution's 3rd party SCSI drivers
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 6.0
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Cristian Gafton
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1999-07-27 14:13 UTC by psitech
Modified: 2008-08-01 16:22 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed:

Attachments (Terms of Use)

Description psitech 1999-07-27 14:13:02 UTC
I have submitted this report before to a
dledford.  I have recieved no response on this
matter at all.  I have e-mailed several times with no
response.  We have many customers who want to use Red Hat.
Please, whoever gets this bug it is very important that we
get some insight on this problem.

My name Oswaldo Rodriguez, I work for a company called
PSI (Perceptive Solutions, Inc.)  There are problems with
the installation of our third party SCSI drivers on your
Redhat 6.0 distribution diskette. Our drivers are in the
sources on the Redhat 6.0 distribution CD, but are not
included in the built kernel. While they should be included
as SCSI modules some of them were not marked as such in the
default kernel configuration.  Similar problems appear to
also affect other third party SCSI providers.

The script for driver selection lists only one of the three
drivers we furnished (and that are included in the
During Installation, messaging appears that indicates two
the three drivers (including the only one selectable during
installation) were not configured as modules. This prevents
generation of the target system.

Another problem is that any kernel built using the sources
supplied fails with a version mismatch during the "boot
loader installation" step. Manually running insmod reports
that loop.0 was built with version 2.2.5-14BOOT while the
generated kernel is reported as version 2.2.5-15.

This problem prevents the installation of the boot loader
an otherwise fully functional (although manually generated)
working system.

With these problems, there is NO practical mechanism for a
normal user to install our drivers using the Redhat 6.0.
While our drivers have no problems running in 6.0, getting
them installed with the scripts Redhat has generated is a

Correcting the configuration (M for module instead of NO)
should address one of the immediate problems problems with
the 6.0 as distributed.  The problem of upgrades (or field
addition of SCSI drivers) however, will remain until the
version mismatch problem is addressed.

We would like to work with Redhat to eliminate these
problems so the full value of 6.x can be accessible. Please
feel free to contact us for hardware or any other support
can offer. We hope that these problems can be addressed in
the near term.

On a separate matter, we would like to suggest that the
default for SCSI generic support (in the kernel) be set to
ON (currently it is off). This fairly small module provides
some powerful support. For us, it is a standard mechanism
for an application to obtain RAID status information and
manage hot swap and reconstruct. Currently it is necessary
to build the kernel in order to utilize this feature.

Thank you....

P.S.  Once we get this resolved we need to also be placed
your hardware compatabilty list.

Note You need to log in before you can comment on or make changes to this bug.