Bug 59628
Summary: | (SCSI GDTH)Installation/Update with ICP Raid Adapter failed | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Dirk Czirpka <dirk> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 7.2 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-30 15:39:22 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Dirk Czirpka
2002-02-11 14:30:00 UTC
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! Dirk This bug has been inappropriately marked MODIFIED. Please review the bug life cycle information at http://bugzilla.redhat.com/bugzilla/bug_status.cgi 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 persists. 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/ |