Bug 4133 - Xconfigurator fails during kickstart for VGA16 card
Xconfigurator fails during kickstart for VGA16 card
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: Xconfigurator (Show other bugs)
6.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Matt Wilson
http://info.stabsoft.inf.ethz.ch/secr...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-07-21 05:58 EDT by walter
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-09-01 20:51:01 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description walter 1999-07-21 05:58:10 EDT
Kickstart installation of a Dell PowerEdge 1300 at our
site fails during X setup. When running Xconfigurator
--kickstart on the manually installed system it exits
with exit code 2.

A little debugging revealed the problem to be in the
following part of the code in Xconfigurator.c:

    if (card_selected == UNLISTED_CARD) {
        unlisted_doprobe = strcmp(state->serverbuf,"I128")
&&
            strcmp(state->serverbuf,"S3") &&
            strcmp(state->serverbuf,"S3V") &&
            strcmp(state->serverbuf,"Mach64");
    } else {

When modifying this to

    if (card_selected == UNLISTED_CARD) {
        unlisted_doprobe = strcmp(state->serverbuf,"I128")
&&
            strcmp(state->serverbuf,"S3") &&
            strcmp(state->serverbuf,"VGA16") &&
            strcmp(state->serverbuf,"S3V") &&
            strcmp(state->serverbuf,"Mach64");
    } else {

it works find. This is just an educated guess, but IMHO
a generic 16 color VGA card should not have special clock
modes detected.

The output of the "X -probeonly" that is done for
clock detection is available under the URL in the
URL: field of this bug report
Comment 1 Trond Eivind Glomsrxd 2000-07-10 14:37:17 EDT
I believe this to be fixed in 6.2 (or even 6.1)

Note You need to log in before you can comment on or make changes to this bug.