grub failure with gpt formatted disk

On such a partition table, what are you supposed to use for the boot loader instead of grub?

This isn't particularly a mythbuntu specific issue, but will need to be properly addressed generally in ubiquity. I'm going to add ubiquity to the list of affects.

Hi Mario,

In my scenario, I'm installing mythbuntu on my appletv. The appletv has
its own bootloader, so grub isn't needed. I have worked around it by
commenting out the bootloader configuration in the install scripts so
that the installation completes.

Myself and others who run mythbuntu on their appletvs would like to see
an option to skip the bootloader. Another option would be to have the
installer ask if you would like to finish the installation if the
bootloader config fails (regular ubuntu installs do this).

Thanks for your time,
Derek

Mario Limonciello wrote:
> On such a partition table, what are you supposed to use for the boot
> loader instead of grub?
>
> This isn't particularly a mythbuntu specific issue, but will need to be
> properly addressed generally in ubiquity. I'm going to add ubiquity to
> the list of affects.
>
> ** Also affects: ubiquity (Ubuntu)
> Importance: Undecided
> Status: New
>
> ** Changed in: ubiquity (Ubuntu)
> Status: New => Incomplete
>
>

Hi Mario,

I have been playing around with the install scripts to skip installing
the bootloader. I found 3 scripts that seem to install the bootloader:

1. /usr/share/ubuquity/install.py
2. /usr/share/ubiquity/mythbuntu_install.py
3. /usr/share/ubiquity/mythbuntu/mythbuntu_install.py

2 and 3 are the same. I have commented out the
.self_configure_bootloader() line in all three files. My question is,
do I have to? Do I only need to comment it out in 1 or two of the
install scripts? I haven't tried all of the different combinations
because it would be fairly time consuming.

Thanks again for your time,
Derek

ubiquity (1.5.8) gutsy; urgency=low

  [ Mario Limonciello ]
  * Fix mythbuntu lircd.conf generation.
  * Update lircd gui to fit better.
  * Clean up mythbuntu summary text. Remove all passwords that are
    shown.
  * Activate mythweb security.
  * Add lirc to mythbuntu depends.
  * In postinstall mythbuntu-setup, change xhost behavior.
  * Add lirc.hwdb population to mythbuntu lirc steps
  * Make all "yes"/"no"'s True/False
  * Add support to enable/disable boot loader installation in GTK,
    KDE, and Mythbuntu frontends (LP: #130445)

  [ Evan Dandrea ]
  * Don't dump debug information to the console when using --automatic.
  * Get the user password straight from debconf in noninteractive mode.

  [ Colin Watson ]
  * Add partman-auto-loop.
  * Move oem-config post-user-creation hacks to the end of install_extras,
    when oem-config-gtk/kde will have been installed in /target
    (LP: #131250).
  * Reimplement more of oem-config-udeb (ugh): disable the hwdb-client
    notification for the created user; set up autologin for the oem user via
    gdm/kdm.
  * Disable migration-assistant if oem-config/enable=true.
  * Adjust apport hook to attach /var/log/installer/debug too if available.

 -- Colin Watson <email address hidden> Thu, 09 Aug 2007 19:57:31 +0100

On dell m1330 laptops, it would be really helpful if the system would try hard to convince the user to overwrite the MBR. The default Dell MBR responds to the 'media direct' button trashing the partition table.