Re: framebuffer broken in 2.6.16.x and 2.6.17-rc3 ?

Giuseppe Bilotta
2006-05-04T21:29:37Z

On Fri, 05 May 2006 04:48:44 +0800, Antonino A. Daplas wrote:

> Giuseppe Bilotta wrote:
>> On Tue, 2 May 2006 21:51:13 +0200, Olivier Fourdan wrote:
>>
>>> I'm surprised noone has raised that issue yet, so I'm wondering if I'm
>>> missing something obvious :) When using the fb in 2.6.16.x and
>>> 2.6.17-rc3, the screen stays just black, nothing is displayed... I'm
>>> using the regular unaccelerated vesa framebuffer.
>>
>> It may sound silly and it's probably not relevant to your case, but I
>> had this kind of result during a kernel upgrade some versions ago when
>> I forgot the fbcon module.
>
> Not silly because that is exactly what happened. He sent me his config in a
> private mail.

Oh.

> I don't know what method he used to upgrade his kernel, but the setting
> changed from 'y' to 'm', and I've received quite a few reports from
> different users on this lately...

Well, when it happened to me it was because I switched from a distro
kernel to a custom build and so the error was entirely on my part. I
still think that some kind of warning in the dmesg or appropriate
wording in the help for the framebuffer devices or for fbcon would
help sort this FAQ out.

OTOH, if the OP made oldconfig it would be interesting to see what
caused the change in configuration ...

--
Giuseppe "Oblomov" Bilotta

"E la storia dell'umanità, babbo?"
"Ma niente: prima si fanno delle cazzate,
poi si studia che cazzate si sono fatte"
(Altan)
("And what about the history of the human race, dad?"
"Oh, nothing special: first they make some foolish things,
then you study what foolish things have been made")