Bug#544822: grub-pc: out of range pointer 0x8080810 with r128 graphics card
Jonathan Nieder
Version: 1.97~beta1-1
Dear GRUB team,
At the sh:grub prompt, I run:
| > insmod gfxterm
| > insmod vbe
| > videotest
This produces output:
| error: No suitable mode found.
That is not too worrying. Afterwards, I run:
| > lsmod
| > loadfont /boot/grub/unicode.pf2
This usually produces much more worrying output:
| out of range pointer 0x8080810
Sometimes that message is in response to the lsmod, sometimes the loadfont.
This series of commands was devised to try to figure out a problem booting
with GRUB_TERMINAL=console not commented. The out of range pointer was
different then, so that was probably a different bug, but this one looks
more debuggable anyway. Any tips?
Thanks,
Jonathan
Ana Guerrero
>
> This usually produces much more worrying output:
>
> | out of range pointer 0x8080810
>
For the record...
I get this same message when booting with grub2 and when accesing to the
console, no matter what command I try, this message again.
Ana
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Ana Guerrero
> On Thu, Sep 03, 2009 at 02:22:58AM -0500, Jonathan Nieder wrote:
> >
> > This usually produces much more worrying output:
> >
> > | out of range pointer 0x8080810
> >
>
> For the record...
> I get this same message when booting with grub2 and when accesing to the
> console, no matter what command I try, this message again.
I got this version of grub working using the grub.cfg generated installing the
version in lenny.
Reverting this change in /boot/grub/grub.cfg :
--- grub.testing/grub.cfg 2009-09-04 23:53:28.000000000 +0200
+++ grub.unstable/grub.cfg 2009-09-04 18:27:07.000000000 +0200
@@ -7,8 +7,20 @@
### BEGIN /etc/grub.d/00_header ###
set default=0
+insmod ext2
+set root=(hd0,1)
+search --no-floppy --fs-uuid --set 7fa532df-0147-4f83-ac28-8715c76c8c43
+if loadfont /usr/share/grub/unicode.pf2 ; then
+ set gfxmode=640x480
+ insmod gfxterm
+ insmod vbe
+ if terminal_output gfxterm ; then true ; else
+ # For backward compatibility with versions of terminal.mod that don't
+ # understand terminal_output
+ terminal gfxterm
+ fi
+fi
set timeout=5
-terminal
### END /etc/grub.d/00_header ###
the system boots without problems. Obviously I do not have the fancy graphic
terminal :)
If you use this workaround to get your system booting, remember the
/boot/grub/grub.cfg file is generated from /etc/grub.d/00_header so if you
regenerate the configuration you will lose the workaround and your system
won't boot again.
Jonathan Nieder
I noticed this bug was tagged "moreinfo". What information could I
provide to help investigate this bug? I would be glad to try various
commands, apply patches with "printf" lines, etc - just let me know
what's useful.
Thanks,
Jonathan
Robert Millan
> Hi Robert,
>
> I noticed this bug was tagged "moreinfo". What information could I
> provide to help investigate this bug? I would be glad to try various
> commands, apply patches with "printf" lines, etc - just let me know
> what's useful.
Please test the following GRUB version:
http://people.debian.org/~rmh/grub-after-fb-split/
If it fails, test this one:
http://people.debian.org/~rmh/grub-before-fb-split/
If it fails, test the one in testing (1.96+20090808-1):
http://packages.debian.org/squeeze/grub-pc
Test procedure (for all tests):
- Install the packages.
- Run grub-install
- Run update-grub
- Reboot into new GRUB. Make sure graphical mode is enabled.
If it wasn't, it means the test has failed (proceed as in with
the "out of range pointer" error).
Thanks!
--
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."