Bug 160287 - fc4 graphic install for cyberblade/i1 does not work
fc4 graphic install for cyberblade/i1 does not work
Status: CLOSED DUPLICATE of bug 161242
Product: Fedora
Classification: Fedora
Component: xorg-x11 (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: X/OpenGL Maintenance List
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2005-06-14 03:32 EDT by Paul Coleman
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-07-05 19:37:17 EDT
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 Paul Coleman 2005-06-14 03:32:07 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4

Description of problem:
The graphics for cyberblade/i1 (Via C3) and some cirrus chips does not work on fc4 as has been reported since fc4t1. I bring this to the attention of kernel since it has not been addressed in X (bugs have been filed and commented) and it maybe a kernel shared memory problem (or not). My post on this issue was for what ever reason was sensored on test-list. I really tried to bring attention to this issue before fc4 release. After a text install startx results in white screen. Dropping to a terminal the text screen is corrupt with a blue character wide blue border.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Insert fc4 install disk
2.Graphical install results in white screen
3.After text install gdm? is white screen

Actual Results:  Anything except a white screen or corrupt text screen is not possible.

Expected Results:  A normal fc4 install

Additional info:
Comment 1 Mike A. Harris 2005-07-05 19:37:17 EDT

*** This bug has been marked as a duplicate of 161242 ***

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