Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 94628 - Legacy megaraid driver missing on 2005.0 LiveCD
Summary: Legacy megaraid driver missing on 2005.0 LiveCD
Status: RESOLVED DUPLICATE of bug 62508
Alias: None
Product: Gentoo Release Media
Classification: Unclassified
Component: Everything (show other bugs)
Hardware: x86 Other
: High normal (vote)
Assignee: Gentoo Release Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-31 08:13 UTC by Angela Williams
Modified: 2005-06-20 06:46 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Angela Williams 2005-05-31 08:13:15 UTC
The current LiveCD 2005.0 only has driver support for the newer LSI megaraid
controller.
The older/legacy driver needed for the megaraid 4ch  controller supplied by Dell
for standard
ide disks is not in the kernel source tree used to create both 2005.0 and 2004.3
Live CD's  

Reproducible: Always
Steps to Reproduce:
1.Any smaller Dell server with a 'cerc' 4ch megaraid controller
2.Boot either 2005.0 or 2004.3 LiveCD's
3.Not raid controller is found and megaraid.ko driver is no existant within
/lib/modules 

Actual Results:  
Unable to access raid disks configured on Megaraid controller

Expected Results:  
Found the controller or provided the legacy megaraid drivers to manually load!

I have found a possible way to circumvent the problem!
I have done a minimal load of FC3 with a manual install of the megaraid driver -
"linux dd"
I created a 6G partion for FC3 to use plus my normal boot, swap,  root, and lvm2
partions
to be used later by Gentoo.
I followed the steps in "The Gentoo Linux alternative installation method HOWTO"
Comment 1 Daniel Drake (RETIRED) gentoo-dev 2005-06-19 04:15:09 UTC
dup/related to 62508
Comment 2 Chris Gianelloni (RETIRED) gentoo-dev 2005-06-20 06:46:17 UTC
Right... even though this isn't exactly a duplicate, I'll mark it as such
anyway, since fixing the one will fix the other.

*** This bug has been marked as a duplicate of 62508 ***