Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 22062 - no move video (black screen) after testing X configuration
no move video (black screen) after testing X configuration
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Michael Fulbright
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2000-12-11 10:55 EST by Laurent CREPET
Modified: 2007-04-18 12:30 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-12-11 11:06:04 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Laurent CREPET 2000-12-11 10:55:38 EST
I just tried to install RedHat Linux 7.0 on a clean system (no OS already
installed). First steps of installation run well.

  - PIII 800, 512 MB
  - Screen: Mitsubishi Diamond Pro 87TXM
  - Video card: Matrox G400 16 MB, dual head.

When I arrived at X configuration, I choose my screen (Mitsubishi Diamond
Pro 87TXM). Then anaconda find my video card and says that it's a Matrox
G400 Generic, with 16 MB of RAM. That's ok, and I click on "Test this

Then, "Yes", I can see the test message, and everything is well
After clicking on "Yes"... no more video, everything is dark, so dark !
- Using Ctrl+Alt+F1 to F7, I can swith consoles. F7 -> still black screen.
- [Enter] -> I can test again the X configuration, but unable to go back to
installation screen.

Then, anaconda loops on the X configuration test, always displaying the
test message, going back to black screen, again, again...
Comment 1 Michael Fulbright 2000-12-11 11:06:00 EST
Some video cards do not test correctly due to problems with the X server.
This is a known problem and we are working with the XFree86 group to resolve
these as soon as possible.

Just proceed through the install w/o testing and then when you reboot into the
system it should work fine.

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