Bug#152804: boot-floppies: framebuffer causes Mobile Radeons to lock

[Richard Hirst <rhirst@linuxcare.com>]

On Sun, Jul 14, 2002 at 01:13:20AM +0100, Philip Blundell wrote:
> On Sat, 2002-07-13 at 17:21, Chris Tillman wrote:
> > It was already documented by Richard. But, I added some more details about
> > what the problems look like and what machines have reported problems.
> 
> Okay, cool.  I wonder if's worth explaining the distinction between
> problems caused by framebuffer itself and problems caused by bogl /
> LANG_CHOOSER lossage.  In the former case, using "nolangchooser" won't
> help.  Equally, "video=vga16:off" is hardware specific, so that isn't
> ideal either, sigh.

Actually, I came across code in drivers/video/fbmem.c (2.4 kernel) the
other day, which indicates video= works for all frame buffers.  It
supports the 'off' parameter itself, and for any other parameters it
calls the framebuffer specific code if that code has a setup function.
So, for the atari, for example, you might use "video=atafb:off", or for
hppa "video=stifb:off".  I havn't tested this, and don't know if it
applies to 2.2. kernels.  Where 'nolangchooser' just stops bterm
running, this would disable the framebuffer driver itself.  As I say,
untested.

Richard



-- 
To UNSUBSCRIBE, email to debian-boot-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org