Bug 49425 - default boot AND nofb boot fail on RIVA TNT2
default boot AND nofb boot fail on RIVA TNT2
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
7.3
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Brent Fox
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-07-19 10:41 EDT by greg hosler
Modified: 2007-04-18 12:34 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-07-19 17:11:17 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 greg hosler 2001-07-19 10:41:26 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
install.

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
monitor
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)?


How reproducible:
Always

Steps to Reproduce:
1. Boot with the following video card: nVidia Riva TnT2, 3D Blaster AGX,
32MB

	

Actual Results:  screen flickers, constantly. unreadable.

Expected Results:  no flicker.

Additional info:

Work around is to boot "lowres", but that's not as documented as well as it
could be.
Comment 1 Glen Foster 2001-07-19 17:11:13 EDT
This defect considered SHOULD-FIX for Fairfax.
Comment 2 Michael Fulbright 2001-07-19 21:46:14 EDT
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
running.

You did the proper thing and tried lowres mode, which is what it exists for.

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