Hi,
Colin Watson wrote:
> > Since #550160 has been fixed, the grub menu appears, I can edit the
> > entries on the console, etc.
> >
> > But as soon as I want to boot one entry, I get the error message
> > "Memory Address not Alligned" and I'm back to the boot prompt "ok" of
> > OpenPROM/OpenBoot.
>
> Vladimir Serbinenko (upstream) told me that he believes he's fixed this:
> the problem was apparently that Open Firmware only gives us a very small
> stack, so he had to add the ability to switch the stack pointer to our
> own chunk of memory in order to have a decent stack size. Any version
> from 1.98+20100527-1 onward should have this fix. If you still have the
> affected system in operation, could you please try upgrading to the
> current version in unstable
Done today as I'm back from holidays for a few days now:
[...]
Preparing to replace grub-ieee1275 1.97+20091210-1 (using
.../grub-ieee1275_1.98+20100710-1_sparc.deb) ...
Unpacking replacement grub-ieee1275 ...
Preparing to replace grub-common 1.97+20091210-1 (using
.../grub-common_1.98+20100710-1_sparc.deb) ...
Unpacking replacement grub-common ...
[...]
grub-install /dev/hda and grub-upgrade did not throw any errors.
But /boot/grub/device.map looked funny. There was no "hd0" or similar
inside the parentheses but some binary garbage (displayed with escapes
as zile show it to me:
(\367\351[\320\367\351[\320\377\377\377\377\377\377\377\377) /dev/fd0
(\367\351]8\367\351]8) /dev/disk/by-id/ata-ST39120A_7BV080CK
I added the following line in front of this list, because those lines
above looked just too buggy:
(hd0) /dev/disk/by-id/ata-ST39120A_7BV080CK
But all I get now is:
--->8---
GRUB Loading kernel..
Welcome to GRUB!
Illegal instruction
ok
---8<---
i.e. I'm back at the openprom prompt.
Not sure if this caused by that weird looking device.map, my manual
addition to it or something else.
> and letting us know if it resolves this problem?
I can't. I seem to run in a new error before that. :-/
Since Vladimir lives in the same city as I do, he's happily invited to
have look at the issue in real life with hands-on experience on the
affected machine. ;-) Just contact me by mail.
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
`- | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
