Bug 4730 - aic7xxx.o out of date after upgrade to 6.0
aic7xxx.o out of date after upgrade to 6.0
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
6.0
All Linux
medium Severity high
: ---
: ---
Assigned To: David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-08-26 16:50 EDT by peterf
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-08-27 15:58:12 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description peterf 1999-08-26 16:50:29 EDT
After upgrading Redhat 5.1 to 6.0, booting from harddrive
fails with message:

/lib/aic7xx.o kernel-module version mismatch compiled with
2.0.35 while we are 2.2.5-15

Then the root filesystem fails to mount, etc.

The system boots fine from the boot diskette made during
the upgrade to 6.0 and finds the SCSI drives, etc.

How can I get a aic7xx.o built for 2.2.5-15?  I didn't see
the sources anywhere in the distribution...
Comment 1 peterf 1999-08-26 16:55:59 EDT
changed architecture to i386
Comment 2 Bill Nottingham 1999-08-27 10:34:59 EDT
Take the aic7xxx.o out of your /lib directory - chances are
that it  doesn't belong to any RPM that's installed in 6.0
Comment 3 peterf 1999-08-27 10:52:59 EDT
Actually the aic7xxx.o doesn't exist in /lib.  The boot message right
before the kernel version mismatch message says "Loading aic7xxx
module".  What does this mean?
Comment 4 peterf 1999-08-27 11:09:59 EDT
I just noticed that in /boot I have a initrd-2.0.35-1.img but no
initrd-2.2.5-15.img.  My lilo.conf is pointing to the initrd-2.0.35-
1.img.  Could this be the problem?
Comment 5 Bill Nottingham 1999-08-27 12:13:59 EDT
Yes.

Make sure you have a line in your /etc/conf.modules that says:
alias scsi_hostadapter aic7xxx


and then try running
'mkinitrd /boot/initrd-2.2.5-15 2.2.5-15`
and editing your lilo.conf appropriately.
Comment 6 peterf 1999-08-27 12:48:59 EDT
That worked.  The entry in /etc/conf.modules was already there so all
I had to do was run mkinitrd and fix /etc/lilo.conf.

Thanks for your quick reply.

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