lkml.org 
[lkml]   [2003]   [Jun]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: FRAMEBUFFER (and console)
On 17 Jun 03 at 21:03, James Simmons wrote:
> > My framebuffer (and therefore system console, by definition) come up
> > rather late.
> >
> > It seems the console doesnt care to check for drivers comming up after a
> > certain time, and thus I get no output despite the driver working.
>
> The reason for this is because the framebuffers most often depend on the
> bus being set up. Usually this happening later in the boot process. What
> are trying to do? Retrieve the earlier printk messages. Do you have
> DUMMY_CONSOLE set to Y. I believe the data is transfered from dummycon to
> fbcon after fbcon is initialized. If you having problems with that try
> increasing the size of dummycon's "screen". See dummycon.c for more
> details.

Maybe he just enabled vga16 + XXXfb. First vga16 comes up, and start
painting characters. Few microseconds after that XXXfb (for example
matroxfb) comes up, registers itself as /dev/fb1 and reprograms hardware
to non-VGA mode.

From that point on vga16fb paints characters to unmapped memory, and
there is only black on screen.
Petr Vandrovec
vandrove@vc.cvut.cz


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:36    [W:0.030 / U:1.012 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site