9.1 update fails to boot LSI Megaraid
good day all ... ok, a clean install on my HDAMA dual 242 system works fine. i update to the current kernel via YOU this morning and now i have megaraid problems. boot sequence goes as: start udev creating devices loading scsi_mod.ko scsi subsystem init loading sd_mod.ko loading megaraid_mm.ko megaraid_mm: 1.0.0rc1 (release date monday may 17) loading megaraid.ko megaraid: ingnoring new style parameters ... megaraid: 2.20.0.rc1 (release date monday may 17) megaraid: probe new devices ... megaraid mailbox: status not available megaraid: inquiry3 failed megaraid: maibox adapter did not initialize ... loading reiserfs.ko then it tries to find the root filesystem on sd1 and fails because its on the raid array. is this a known lsi megaraid issuse, is there a workaround or fix? will loading one of the KOTD kernels help? -- michael
Hi suse-amd64! ok, it seems this is again the large memory issue, with some help from penguin computing, i did a clean install and a you update, with the addition of adding 1. Edit the grub boot entry and add an *additional* line that says: uppermem 3000000 2. Add to the kernel command line: mem=3000000k to the grub config. the kernel update boots fine with that. penguin is exploring fixes to this bug. -- michael On Tue, 22 Jun 2004, Michael Galloway wrote:
On Wed, Jun 23, 2004 at 10:35:08AM -0400, Michael Galloway wrote:
Prime suspect would be the firmware of your Megaraid. They had bugs with addressing high memory addresses in the past. Perhaps you can get an upgrade for that from somewhere? -Andi
Hi suse-amd64! ok, it seems this is again the large memory issue, with some help from penguin computing, i did a clean install and a you update, with the addition of adding 1. Edit the grub boot entry and add an *additional* line that says: uppermem 3000000 2. Add to the kernel command line: mem=3000000k to the grub config. the kernel update boots fine with that. penguin is exploring fixes to this bug. -- michael On Tue, 22 Jun 2004, Michael Galloway wrote:
On Wed, Jun 23, 2004 at 10:35:08AM -0400, Michael Galloway wrote:
Prime suspect would be the firmware of your Megaraid. They had bugs with addressing high memory addresses in the past. Perhaps you can get an upgrade for that from somewhere? -Andi
participants (2)
-
Andi Kleen -
Michael Galloway