hi all,
Sorry if this has been already covered recently, but it seems that the
framebuffer doesn't work anymore in 2.6.16.9 and 2.6.17-rc3, while it
worked in 2.6.16 at least.
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.
I'm wondering if this could related to the fb changes that occured
after 2.6.16 initial release and if other people are experiencing
issues with frame buffer recently.
Cheers,
Olivier.
Olivier Fourdan wrote:
> hi all,
>
> Sorry if this has been already covered recently, but it seems that the
> framebuffer doesn't work anymore in 2.6.16.9 and 2.6.17-rc3, while it
> worked in 2.6.16 at least.
>
> 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.
>
> I'm wondering if this could related to the fb changes that occured
> after 2.6.16 initial release and if other people are experiencing
> issues with frame buffer recently.
There should be no issues, especially with the vesa framebuffer. Can you
post your dmesg and config?
Tony
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.
--
Giuseppe "Oblomov" Bilotta
"Da grande lotter? per la pace"
"A me me la compra il mio babbo"
(Altan)
("When I grow up, I will fight for peace"
"I'll have my daddy buy it for me")
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.
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...
Tony
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")
Giuseppe Bilotta wrote:
> 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 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.
This is already documented in Documentation/fb/fbcon.txt. Although a
warning in the help text of vesafb might help.
Tony