В Mon, 20 Jan 2014 10:30:33 -0500 SevenBits <[email protected]> пишет:
> On Jan 20, 2014, at 10:27 AM, Andrey Borzenkov <[email protected]> wrote: > > > В Mon, 20 Jan 2014 09:59:40 -0500 > > SevenBits <[email protected]> пишет: > > > >> On Jan 19, 2014, at 9:23 PM, Andrey Borzenkov <[email protected]> wrote: > >> > >>> В Sun, 19 Jan 2014 19:45:23 -0500 > >>> SevenBits <[email protected]> пишет: > >>> > >>>> Not sure whether to post this in this bug-grub list or here, so feel > >>>> free to correct me if perhaps this is in the wrong spot. I’m not sure if > >>>> the issue I’m having is due to a fault in setup or a bug within GRUB. > >>>> > >>>> I’m the developer of a tool called Mac Linux USB Loader, and some of my > >>>> users are reporting errors with my compiled copy of GRUB. Specifically, > >>>> after loading the kernel, GRUB spits out the following error message: > >>>> > >>>> alloc magic is broken at 0x81493ca0: 207d007d68746170 > >>>> Aborted. Press any key to exit. > >>>> > >>>> The hexadecimal values vary slightly, but generally speaking this is > >>>> what the error looks like. The kernel loading operation with GRUB’s > >>>> linux command is followed by the initrd command to load the RAM disc, > >>>> and that operation never occurs, so I know that the operation never > >>>> completes. > >>>> > >>>> This error never seems to occur with Ubuntu-based distributions. It also > >>>> seems to occur if the kernel can’t be found - but in that case, > >>>> shouldn’t the linux command fail with an error instead of something like > >>>> this? > >>>> > >>>> I can’t post my GRUB config at the moment, as I’m not on the machine > >>>> where it is stored, but any advice that you can give me without it would > >>>> be appreciated, such as under what conditions this error occurs. > >>>> > >>>> Thanks, > >>>> > >>>> — SevenBits > >>> > >>> Well, the first thing to try would be upstream HEAD to verify whether > >>> problem is still present there. > >> > >> Sorry, just realized my previous reply didn’t get posted. > >> > >> The GRUB build I’m using is compiled straight from the current git > >> repository. It might be a week or two old, but unless something really > >> changed in the last two to three weeks I don’t think it’ll differ. > >> > > > > In this case you need to post to gurb-devel. Is there any way to get > > output to serial console? > > No, I don’t think so, unless there’s some GRUB trick that I don’t know about. > Once this happens GRUB crashes to a stop and I can’t do anything. > You could change to serial console before running this command and enable debugging. > > > >> I can try an older release of GRUB, like the latest stable and see if that > >> does anything though. >
signature.asc
Description: PGP signature
_______________________________________________ Help-grub mailing list [email protected] https://lists.gnu.org/mailman/listinfo/help-grub
