Red Hat Bugzilla – Bug 49425
default boot AND nofb boot fail on RIVA TNT2
Last modified: 2007-04-18 12:34:53 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.4.3-2.9.2smp i686)
Description of problem:
Video card: nVidia Corporation Riva TnT2, 3D Blaster AGX, 32MB
Monitor: HP A4033A
problem, default boot uses a frame buffer that causes the screen to flicker
so bad that reading the screen is out of the question, much less doing an
reboot, select "nofb" - slightly better. The initial boot gote ok, then X
starts, and the flickering is again terrible.
reboot, select lowres - this time everything is ok.
In all 3 cases, the video card is properly identified as RIVA TNT2, and the
is misidentified as UNIDENTIFIED MONITOR
I'm wondering out loud here, is there some way to drop into lowres mode
without rebooting, if the installer can tell that the user can't read
the screen (such as by a timeout, or something)?
Steps to Reproduce:
1. Boot with the following video card: nVidia Riva TnT2, 3D Blaster AGX,
Actual Results: screen flickers, constantly. unreadable.
Expected Results: no flicker.
Work around is to boot "lowres", but that's not as documented as well as it
This defect considered SHOULD-FIX for Fairfax.
The monitor settings we have selected in the case of a undetected monitor are
extremely conservative (equivalent to an IBM XGA display in 1989). It is rare
(first report I've heard actually) for it to cause problems.
There is no easy way to make X and anaconda switch to a lower resolution once
You did the proper thing and tried lowres mode, which is what it exists for.