Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Using a HP ML110 server with SATA Raid (Promise S150 SX4
controller) and Raid 5 (with 3 harddisks)
2. Using Fedora Core 3 (or 2)
3. Doesn't work - finds drivers but freezes.
4. Core 2 and Core 3 uses different drivers (name of the driver) but
the result is the same
HP have drivers for Redhat 9.0 (and SuSE 9) - shouldn't they work on
FC3 chokes on install with a Promise FastTrack 378 RAID 1 config.
Interrupt #11 errors and eventual lockup.
I also have install lockup on a HP ML110 SATA, I'm not attempting to
use any of it's hardware (well kind of) raid features. The Kernel
pickes up the controller and one the disks, then the install locks and
goes no further.
Have attempted to use an Adaptec 1210SA in the ML110 and that lockup a
the same point in the boot sequernce during install (just after the
driver has detected the first disk). How ever turn off acpi "append
acpi=off" and it works. I will re-test with the ogrinal controler.
have attempt to disable acpi mode, and try to install fc3 on HP ML110
No more succes than John apparently. My promise is a S150 SX4.
Nobody found a solution ?
Have tried with both Fedora Core 4 test 1 with the same result. I have the
sourcecodes for the promise drivers but dont know how to use them.
This sounds suspiciously familiar to bug #128180. Same lost interupt symtpom
and results (hang). Sounds like the problem may be outside the specific card
chipset drivers. These cards reportedly work fine on other OS's.
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'.
Installation of FC4 still freezes...
Mass update to all FC4 bugs:
An update has been released (2.6.13-1.1526_FC4) which rebases to a new upstream
kernel (220.127.116.11). As there were ~3500 changes upstream between this and the
previous kernel, it's possible your bug has been fixed already.
Please retest with this update, and update this bug if necessary.
To test with the last kernel update is a bit hard since the problem occures on
installation. I tried the UNOFFICIAL Fedora Core 4.1 from
http://fedora.isphuset.no/ but the kernel used there is 2.6.12-1.1447_FC4 which
didn't work. Any ideas how I can try to install the server with the current
http://fedora.isphuset.no/ contains an unofficial Fedora 4.1, which may get you
up and running, as it has a install kernel based on one of the errata kernels.
I tried this as stated in my last comment.
2.6.14-1.1637_FC4 has been released as an update for FC4.
Please retest with this update, as a large amount of code has been changed in
this release, which may have fixed your problem.
I will check this as soon as you lead me to a guide how to create ISOs with the
latest kernel in it. I found several How-tos for FC2 and FC3 but it seems these
don't work for FC4 or the anaconda-runtime scripts for FC4 are broken. Lost
already about 5 days trying to create new ISOs.
theres an unofficial FC4.2 at http://fedora.isphuset.no
which has an updated kernel, (though not the current one), but that may be new
enough to fix your problem.
Tried with Unofficial FC4.2. Still no success...
Due to the overhead involved in creating new ISOs (which is what would be
required for fixing bugs seen at installation time that don't have workarounds),
this bug has been closed.
For more information and suggestions, please see bug 169613