framebuffer broken in 2.6.16.x and 2.6.17-rc3 ?

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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: framebuffer broken in 2.6.16.x and 2.6.17-rc3 ?
    • From: Giuseppe Bilotta <[email protected]>
  • Re: framebuffer broken in 2.6.16.x and 2.6.17-rc3 ?
    • From: "Antonino A. Daplas" <[email protected]>

• Prev by Date: Re: assert/crash in __rmqueue() when enabling CONFIG_NUMA
• Next by Date: [RFC, PATCH] cond_resched() added to close_files()
• Previous by thread: Question about cmpxchg()
• Next by thread: Re: framebuffer broken in 2.6.16.x and 2.6.17-rc3 ?
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]