Description of Problem: Assuming bugzilla #59449 is resolved (that the kernel creates fusion.o and mptscsih.o as modules that allow booting from an MPT Fusion SCSI controller): Anaconda needs to include fusion.o and mptscsih.o as modules in its installer images to enable installation onto disks attached to MPT Fusion SCSI controllers. This controller is the primary U320 SCSI controller on the Dell PowerEdge "Discovery" platform. Ideally Pensacola, but absolutely Hampton installers need to support this. Version-Release number of selected component (if applicable): Pensacola and Hampton How Reproducible: Steps to Reproduce: 1. 2. 3. Actual Results: Expected Results: Additional Information:
Jeremy are these modules being put on the driver image currently?
Currently waiting on the drivers to be updated in the kernel per Arjan's suggestion
Katzj are these drivers going to fit?
There should be plenty of room on drvblock.img
These drivers are included in kernel 2.4.18-0.4 on Hampton Beta 3 at least. So we'd like to see them added to the installer for beta 4. Thanks, Matt
I'm adding mptscsih.o now... I'm assuming fusion.o doesn't actually exist? Also, I'll try to get a boot disk / driver disk combo a little later today to throw up so that you can test with it (it won't load the second stage, but you should at least be able to ensure the driver gets loaded properly)
Added. Images are available at http://people.redhat.com/~katzj/fusion/ that should let you see if the module properly loads. They won't, though, allow you to do an install with the beta3 tree. Please reopen if you see any problems loading the modules with these disks
*** Bug 61681 has been marked as a duplicate of this bug. ***
Thanks, Tesfamariam will test this on Monday probably. The two modules needed were mptbase.o and mptscsih.o, where mptscsih.o depends on mptbase.o. (fusion.o was an intermediate library file during the build I belive). Sorry for the confusion. -Matt
Changing this to Needinfo, as we are waiting on the results of testing from Dell.
Booting with boot.img and bootnet.img and trying to continue with the installation, the installation fails with message something like ...The second stage of the install which you selected doesn't match the boot disk which you are using...rebooting...
Allow me to quote from my initial message -- "They (these disks) won't, though, allow you to do an install with the beta3 tree." Beta4 has all of this in there, though.
Based on another bug and mail, I'm going to mark this CLOSED->RAWHIDE as it seems to be working just fine now