Bug 8789

Summary: FrameBuffer scrambles screen
Product: [Retired] Red Hat Linux Reporter: Frank Sweetser <fs>
Component: kernelAssignee: Michael K. Johnson <johnsonm>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-03-27 12:00:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Frank Sweetser 2000-01-24 05:02:55 UTC 
When the framebuffer devices are enabled in the kernel, the screen is
constantly "snowed" in in text mode.  X is similarly scrambled, and
essentially useless.  Recompiling the kernel without framebuffer support
fixes the problem.

relevant bit of lspci -v
01:00.0 VGA compatible controller: Nvidia Corporation Riva TNT (rev 04)
	Subsystem: Unknown device 1092:0550
	Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 11
	Memory at e1000000 (32-bit, non-prefetchable)
	Memory at e3000000 (32-bit, prefetchable)
	Capabilities: <available only to root>
Comment 1 Bill Nottingham 2000-02-05 07:05:59 UTC 
*** Bug 8500 has been marked as a duplicate of this bug. ***
Comment 2 Bill Nottingham 2000-02-06 06:02:59 UTC 
*** Bug 7549 has been marked as a duplicate of this bug. ***
Comment 3 Bill Nottingham 2000-02-06 06:05:59 UTC 
*** Bug 7597 has been marked as a duplicate of this bug. ***
Comment 4 Bill Nottingham 2000-02-06 06:24:59 UTC 
*** Bug 8287 has been marked as a duplicate of this bug. ***
Comment 5 Preston Brown 2000-02-24 01:22:59 UTC 
*** Bug 9323 has been marked as a duplicate of this bug. ***
Comment 6 Alan Cox 2000-08-22 14:53:18 UTC 
The nvidia frame buffer + X server combination isnt supported.
Either use nvidia X and text mode or frame buffer and XFree86_fb (unaccelerated)

I believe this is supposed to get fixed by 2.4