Mike,
I can get FC2 to install if I replace the default kernel in the install image with one I've built myself.
I'm 95% sure now that the problem I'm having with booting the default kernel (pre/post install) is that the driver for the embedded Smart Array controller is never being loaded. In fact, if I boot the install on ANY Compaq with a Smart Array (whether embedded or on-a-card), the install fails to boot.
If I boot my custom kernel, I see the kernel detect the array and load the cpqarray driver, but I don't see this happen with the kernel that is shipped with Fedora (1, 2, 3T1).
-David
On Aug 11, 2004, at 16:28, Michael E. Webster wrote:
David,
I have core1 and core2 running on over 30 HP servers right now. I only had problems with one DL360-G3 in particular. All of my others have had no problems. My problem ended up being the cdrom drive itself. Pull one from another DL360-G3 and try that. If that doesn't work, try linux allowcddma. That might work.
Hope this helps, Mike.
On Wed, 2004-08-11 at 15:48, Kevin Wang wrote:On Wed, 11 Aug 2004 15:45:19 -0400, David Nedrow <listbox@xxxxxxxxxx> wrote:No other theories out there?
Note that even though I didn't specifically mention it, I have tried the uniprocessor kernels with no change.
Also tried ide=nodma with no change.
-David
On Aug 9, 2004, at 15:04, David Nedrow wrote:
I have been unable to install or boot FC2, FC3T1, or devel using the
default kernels on ANY Compaq system that I have access to. The
Compaqs are DL360s, 1850's, and 4500s with SMART array controllers and
896 meg of RAM.
Scenario 1:
Simply booting the install loads anaconda, which then complains there
is not enough memory.
Scenario 2:
mem=896M
Supplying the simplified mem parameter never makes it to anaconda, and
errors out with the following:
md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. VFS: Cannot open root device "LABEL=/" or unknown-block(8,3) Please append a correct "root=" boot option Kernel panic: VFS: Unable to mount root fs on unknown-block(8,3)
Scenario 3:
map=exactmap map=640K@0 map=895M@1M
Now, the system simply stops after displaying "Uncompressing Linux...
OK, booting the kernel."
Note also that regardless of what root= options I've tried, I still get a kernel panic in scenario 2.
I've also tried nousb, nopcmcia, noprobe, acpi=off, skipddc, in multiple combinations without any benefit or difference in errors.
Strangely, if I replace the kernel on the install disk with one I've
built myself, I can get through the installation fine, but then cannot
boot the kernel that is actually installed by anaconda. Presumably, if
I were to boot via rescue and replace the installed kernel with mine,
I would be able to boot the system OK.
This has me flummoxed. If you need more info from the boot process,
let me know what items. Obviously, I'm not making it far enough in the
kernel panic scenarios to switch consoles to get the output of the
boot processes.
This is with the following kernels: kernel-smp-2.6.5-1.358 kernel-smp-2.6.7-1.478 kernel-smp-2.6.7-1.509
David
-- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
-- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
-- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
