From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; T312461)
Description of problem:
I can not install or upgrade a server with ICP Raid Adapter (GDT6517RP). The
setup finds the adapter, but then it is over.
After a long time there are timeout messages. Here is the output of the install
<4> Configure GDT-PCI HA at 0/16 IRQ11
<6> scsi0: GDT6517RP
<4> Vendor: ICP Model: Host Drive #00 Rev:
<4> Type: Direct-Access ANSI SCSI revision02
pause (after a long time there a the following messages)
<6> scsi: device set offline- - not ready for ... host:0 channe 1 id0 lun 0
I have tried to install RH6.2: everything works fine!!!
Is there a similar problem like #39078?
Who can help?
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Alwayy the same:
- Try to install RH 7.2
- Try to upgrade from RH 6.2 to RH 7.2
- Try to use Driver Disk
Actual Results: Machine (gdth module) give timeout Messages (see above)
Expected Results: correct initialisation (find the Raid5-Hostdrive)
PII 400 with 512 MB RAM
Maxdata Platinum Delphi
ICP GDT6517RP (Raid 5 chip present)
4x 18,4 GB HDDs (Raid 5: 3+1 hot spare)
Is this a 440GX chipset machine ?
Server chipset: Intel 440 BX (dual processor board)
The problem is similar to the Intel gx chipset problem. I can install RH7.2 if
I use the "apic" option on lilo prompt. Then the installation goes on.
After installation there is another problem. We use only one cpu, so RH7.2
installs the single cpu kernel. This kernel do not recognize the boot
option "apic" on linux prompt. If we install (manually aktivate the kernel-smp
package at installation) the smp-kernel everthing works. After installation you
can make your own single cpu kernel, but aktivate APIC support!
This bug has been inappropriately marked MODIFIED. Please review the bug life
cycle information at
Changing bug status to ASSIGNED.
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases,
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/