Bug#535026: patch, please test

[Robert Millan]

On Fri, Jul 03, 2009 at 06:10:01PM +0200, Luca Tettamanti wrote:
> The last update to grub didn't fix the bug for me, I still have a blank FB.
> vesafb still reports bogus information:
> 
> vesafb: framebuffer at 0xe0000000, mapped to 0xffffc90010100000, using
> 768k, total 768k
> vesafb: mode is 1024x768x8, linelength=1024, pages=0
> vesafb: scrolling: redraw
> vesafb: Pseudocolor: size=0:0:0:0, shift=0:0:0:0

Please tell me the output of:

  A) A *patched* Linux being loaded by "linux16" command, using the
     patch in:
     http://lists.gnu.org/archive/html/grub-devel/2009-06/txteL9T65YdVL.txt

     This could be what you already provided in
     http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=535026#43
     except your followup comment "vesafb is not picking up the right options"
     contradicts that (linux16 *is* the old loader, and it is supposed to
     work.  If linux16 doesn't work, we have an entirely different problem).

  B) Linux (patched or not), being loaded by "linux" command, using the
     GRUB patch in:
     http://lists.gnu.org/archive/html/grub-devel/2009-06/txtFlQanGk4Pv.txt
     *plus* the patch I'm attaching.

In both cases, I need both the screen_info dump and (if available) vesafb
output.

Btw, you can also contact me on IRC (nyu @ irc.freenode.net / #grub).

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: capabilities.diff
Type: text/x-diff
Size: 538 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-grub-devel/attachments/20090704/f64b5a4d/attachment.diff>