Red Hat Bugzilla – Bug 133972
Installation won't recognize PERC 4e/Si RAID controller on Dell 1850
Last modified: 2015-01-04 17:10:10 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET
Description of problem:
Won't recognize the logical drive (verified the logical/physical
drive is working by installing Windows 2003 with updated driver)
Also, the megaraid driver (which is required for this RAID card) is
no longer present in the list of additional device drivers. Is this
loaded by default now?
I believe that the updated drivers have been merged into the
kernel.org stock kernel as of 2.6.8 - and I thought Fedora Core 3
Test 2 was using the 2.6.8 kernel.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Purchase a Dell Poweredge 1850
2. Try to install FC2 or FC3 Test 2
Actual Results: Says there is no hard drive
Expected Results: Should recognize the hard drive
What happens if you load megaraid_mbox?
If you mean LSI's megaraid v126.96.36.199 I am sure that would work, but I
cannot find it in the the list of additional drivers. I have even been
trying to create my own driver disk with megaraid_mm.o and
megaraid_mbox.o on it, but having problems.
How can I load megaraid_mbox?
megaraid* is missing from modules.cgz
At least on x86_64, this appears to have been fixed post-FC3t2
The 20041001 boot.iso for x86_64 just installed on the 4e/Di in a 2850
here. The PERC was autodetected and the new megaraid drivers loaded
I would think it should be working now on your 1850 as well
Note that after install you will have to create an initrd manually
(see Bug #134369).
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem. Please update to this new kernel, and
report whether or not it fixes your problem.
If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.
This bug has been automatically closed as part of a mass update.
It had been in NEEDINFO state since July 2005.
If this bug still exists in current errata kernels, please reopen this bug.
There are a large number of inactive bugs in the database, and this is the only
way to purge them.