From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510
Description of problem:
The kernel module "advansys.ko" is no longer found amongst the
prebuilt kernel modules. (Previously it could be found in
installation of new kernel via "rpm -ivh
kernel-2.6.7-1.494.2.2.i686.rpm", mkinitrd fails since it cannot find
the necessary module. If I attempt to boot into my new kernel I will
not have access to any of my SCSI devices.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install kernel-2.6.7-1.494.2.2.i686.rpm
2. Try to build a new kernel that requires the advansys module
Actual Results: mkinitrd cannot build initrd for the kernel version.
Expected Results: New initrd should have been produced.
advansys.c and advansys.h can be found in the kernel source for kernel
2.6.7-1.494.2.2 - I don't understand why the module wasn't built.
FYI, I'm seeing this too (Athlon UP).
This has got me too... Is there a reason it isnt in the UP & SMP kernels?
The upstream maintainer of the advansys module has marked it BROKEN
(which means you can't select it in the kernel config basically) due
to datacorruption issues he's chasing out.
Okay... this brings up a general problem when modules go missing in
What should installation of the kernel rpm do in this situation?
Right now people who were using the advansys module end up installing
the update kernel package and mkinitrd may fail leaving them with no
initrd and no grub entry. Is this the best way to handle this
situation or should the rpm package installation do something more?
On top of that people using up2date who use this module don't see an
error message at all with regard to mkinitrd failing during the
postinstall of the kernel rpm. From an average user point of view,
there is precious little information being reported back telling them
a problem occured. Should mkinitrd fail? Should there be more reporint
back to the user?
reenabled in current errata kernels