Red Hat Bugzilla – Bug 136868
AMI MegaRAID worked under FC2, but not FC3 test3
Last modified: 2015-01-04 17:11:03 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Description of problem:
Under FC1 and FC2, the MegaRAID module worked for my American
Megatrends card. Under FC3, it just won't load the devices. I'm not
sure if it's a kernel or udev problem.
Here is what `lspci -vv` yields for this card:
00:0b.0 RAID bus controller: American Megatrends Inc. MegaRAID (rev 02)
Subsystem: American Megatrends Inc. MegaRAID 475 Express
500/500LC RAID Controller
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort+ >SERR- <PERR-
Latency: 32, Cache Line Size 08
Interrupt: pin A routed to IRQ 137
Region 0: Memory at d7000000 (32-bit, prefetchable) [size=64K]
Capabilities:  Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Get a working FC2 system with an AMI MegaRAID 475 card.
2. Upgrade to FC3.
What happens when the module is loaded?
Possibly closely related to
I had much the same happen to me, except it wouldn't even show the
devices in installation. Have you checked to make sure you are at the
latest firmware level? My card wouldn't update, but yours might.
Bill - Even if I manually load megaraid_mm/megaraid_mbox, I don't see
the array. It used to show up as sdc. (I also have an Adaptec card
with 2 drives attached to it.) Did something change with the kernel,
or is this an udev problem? It used to work with the old kernel/devfs
Brian - My card isn't listed on the Manufacturer's site anymore. Given
it's excellent history, I am less likely to believe it is a firmware
problem with the card than a problem introduced by kernel/udev/devfs
changes in FC3.
Pete - OK, just thought I'd check. I show the MegaRAID 475 to be the
direct transfer to the LSI Logic MegaRAID Express 500. (LSI bought
all of AMI's RAID card business, as far as I can tell). Here's the
downloads page for that card, but you'll be able to narrow down
whether or not it is the same card far better than I.
Good luck! I think whatever fixes your problems will likely fix mine,
Brian - Thanks for the link. It looks like it's for my card, but I got
nervous while going through the readme.txt. The part about "MAKE SURE
TO FLASH THIS FIRMWARE ONLY WHEN USING A MEGARAID 475/493/471/494/503
CONTROLLER FROM LSI LOGIC CORPORATION" will probably stop me from
updating. Color me cautious on flashing my BIOS. =/
After a little more digging, I think it's a udev problem. `lspci -vv`
lists that the card is at address 00:0b.0 on the PCI bus. udevinfo for
this device reveals this:
# udevinfo -a -p /sys/devices/pci0000\:00/0000\:00\:0b.0/
udevinfo starts with the device the node belongs to and then walks up the
device chain, to print for every device found, all possibly useful
in the udev key format.
Only attributes within one device section may be used together in one
to match the device for which the node will be created.
looking at class device '/sys/devices/pci0000:00/0000:00:0b.0':
It looks like the card is attached and responding, but the system
doesn't know what to do with it. I'm just starting to learn about
udev, however, so I may be completely off-base.
Upgrading the firmware to the latest version does not resolve this
issue. The driver used for FC3 will not recognise any partitions on
the MegaRAID Express 500 controller - regardless of firmware.
Amazingly this made it out of test into the released version this week.
I have yet to find a way to get the correct megaraid driver to load
sinc e obviously the one included is defective and the old driver was
excluded from the FC3 installer.
I just upgraded to the full FC3 (from FC3-test2) and applied all of
the released updates. Still no dice. Upgrading the kernel also gave
warnings about no modules for megaraid or megaraid2. Has anyone had
any luck with this?
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.