Bug 8043 - Upgrade selects wrong SCSI module - after restart, kernel panic
Upgrade selects wrong SCSI module - after restart, kernel panic
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Michael Fulbright
Depends On:
  Show dependency treegraph
Reported: 1999-12-29 09:23 EST by jkarun
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-06-12 14:05:01 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description jkarun 1999-12-29 09:23:36 EST
While upgrading from version 5.2 to 6.1 I experienced the following bug:

I have an Adaptec 2920 scsi card which, of course, requires aic7xxx.o to
run.  The install/upgrade program detects the right board and loads the
driver appropriately.  However, for some reason, the install program places
the aic151 module in conf.modules and consequently gets the wrong driver
built into the ramsdisk.  When my server restarted I could see the scsi
driver failing to load and, of course, kernel panic.  I have been able to
work around this problem by putting the right entry in conf.modules during
the install program (escaping to console, copying file to another machine
and editing - a long process, especially if the local filesystems are not

Thanks - I hope I provided you with good information
Comment 1 Derek Tattersall 2000-04-25 14:21:59 EDT
Unfortunately, we don't have a 2920.  Itried with a 2940 which uses the same
aic7xxx driver.  I installed 5.2, then upgraded to 6.1 and had no problems.  I
also installed 5.2 and upgraded to 6.2 and had no problems.  conf.modules was
correct each time.

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