Bug 8500 - Framebuffer support in 6.2 kernel
Summary: Framebuffer support in 6.2 kernel
Status: CLOSED DUPLICATE of bug 8789
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 6.2
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Michael K. Johnson
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2000-01-15 20:02 UTC by Bernhard Rosenkraenzer
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2000-02-05 07:05:32 UTC

Attachments (Terms of Use)

Description Bernhard Rosenkraenzer 2000-01-15 20:02:02 UTC
Including framebuffer support in the 6.2 kernel was IMO a very bad idea.
First of all, it causes garbled text mode on some chipsets occasionally (my notebook, using an ATI Rage LT Pro chipset, for example, will occasionally display VERY odd stuff).
Second, it breaks switching between X and console on various chipsets.
Third, you're NEVER supposed to run a normal X server on a kernel with framebuffer support. (See /usr/src/linux/Documentation/fb/vesafb.txt). It'll also very probably break some older graphics cards (did anyone try to boot this kernel with an EGA card?).
Actually, the fact that they did this before was one of the reasons I used to tell people to use Red Hat Linux instead of Caldera OpenLinux.
Please at least turn if OFF by default. (Yes, I know the penguin at bootup looks nice, but it's not enough of a reason to mess up the system).

Comment 1 Bernhard Rosenkraenzer 2000-01-16 11:10:59 UTC
Just seen the first really major breakage caused by framebuffers:
On a Gericom 3xC notebook (ATI Rage LT Pro chipset, some Mach64), with
the stock 6.2b1 kernel, you can't start X (unless you use the framebuffer server); it just turns the screen black.
Also, when using "d$" in vi, the line being edited gets garbled.
We really really need to remove fb (at least atyfb, haven't tried the others)

Comment 2 Bill Nottingham 2000-02-05 07:05:59 UTC
*** This bug has been marked as a duplicate of 8789 ***

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