Acer Aspire One ZA3 751h does not boot GRUB

[Hankyone]

Binary package hint: grub2

After a sucessful install of Maverick or Lucid on a Acer Aspire One ZA3 751h, it it appears to not be able to boot GRUB.

Holding shift at boot displays "loading grub..." and nothing else happens.

Also tried installing netbook remix (karmic) and it booted without any issues.

[Ameet Paranjape (ameetp)]

Please provide a bit more information on the release you are testing. What is the iso of the day level, x86 or x86_64, Ubuntu server or desktop, etc. Thanks.

[Hankyone (hankyone)]

All build are i386.

Just tried a Lucid Desktop install, issue did not reproduce.

I will report back with more info as I run more tests.

[Hankyone (hankyone)]

Issue reproduced on maverick desktop 20100722
Cannot test with a more recent build for the moment.

And again, pressing shift to get the grub menu displays the grub loading message then nothing.

[Hankyone (hankyone)]

If I install a working version (like karmic netbook remix) and then install maverick side by side I get the Grub menu and am able to boot in both installs.

[Ameet Paranjape (ameetp)]

Anouar,

Got a suggestion from cjwatson:

Try using the debian installer's rescue mode to give a shell in the relevant root filesystem, and run 'grub-install --debug-image=all /dev/sda' (or whatever device is appropriate)

If we can connect a serial console to this system, we might be able to save the generated output. The other option is to just video the system while it is starting...

[Hankyone (hankyone)]

I attached the output of where it freezes.

[Colin Watson (cjwatson)]

On Mon, Sep 20, 2010 at 06:12:33PM -0000, Ameet Paranjape wrote:
> *** This bug is a duplicate of bug 641259 ***
> https://bugs.launchpad.net/bugs/641259
>
> ** This bug has been marked a duplicate of bug 641259
> grub does not appear to load after maverick post-beta install

Ameet, how do you know that this is the same underlying issue?

[Ameet Paranjape (ameetp)]

>Ameet, how do you know that this is the same underlying issue?

I marked this as a duplicate because the resulting behavior and the workaround are the same as bug 641259. Also, bug 641259 affects systems from various hardware vendors so I thought it would be easier to track and debug as a whole and then we could reopen or create new bugs for separate architectures based on the debug findings.

[Marc Tardif (cr3)]

This bug could not be reproduced with the released version of Maverick, so marking as fixed.