Re: lenovo s205 installation problems
On Tue, Feb 7, 2012 at 9:18 AM, Tom H <tomh0665@gmail.com> wrote:
> On Tue, Feb 7, 2012 at 9:07 AM, Tom H <tomh0665@gmail.com> wrote:
>> On Tue, Feb 7, 2012 at 8:05 AM, Russell L. Harris
>> <rlharris@broadcaster.org> wrote:
>>> * Tom H <tomh0665@gmail.com> [120207 12:12]:
>>>> On Mon, Feb 6, 2012 at 6:12 AM, Russell L. Harris
>>>> <rlharris@broadcaster.org> wrote:
>>>>
>>> So I plan to reboot the GParted-Live flash USB (now upgraded to
>>> 0.11.0) and experiment.
>>>>
>>>> "bios_grub"/"bios_boot" is a type/flag like "boot", "lvm", "raid". In
>>>> fdisk/gdisk, you use "t" to set them and in parted you use "set".
>>>
>>> Using GParted to partition the drive just prior to this installation
>>> attempt, I created a separate /boot partition as the first partition.
>>> I then used the "manage flags" menu of GParted to set the boot flag.
>>> In addition to the "boot" flag, the menu offered also the "bios-grub"
>>> flag. Should I have set both the "boot" and the "bios-grub" flag for
>>> the partition "/boot"?
>>
>> I wouldn't worry about the "boot" flag; I don't have it set on any
>> partition on my netbook and it boots fine. If you do want to use it,
>> set it to "/boot" or to "/" if you don't have a separate "/boot".
>>
>> The "bios_grub" flag shouldn't be applied to "/boot" or any other
>> partition with a filesystem.
>>
>> if you want to install grub to the MBR, create a 1MB partition as the
>> first partition of your GPT disk and flag it as "bios_grub" and then
>> create "/boot', etc.
>
> FORGOT!
>
> In your case, make sure that you also apply the "boot" flag to the
> "bios_grub" partition, as this might be a solution to your grub boot
> problem.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=696482
>
> https://bugzilla.redhat.com/show_bug.cgi?id=754850
>
> There's a third bug report with more info (IIRC, mentioning Lenovo)
> but it's now been marked "private"...
I've found another Lenovo mention (the last para's about the Fedora
installer's kernel command line!):
http://lists.fedoraproject.org/pipermail/test/2012-February/105441.html
In Fedora 16 we changed to using GPT as the default disklabel for new
installs. In a few cases, mostly limited to Lenovo hardware, we found
that some BIOS's would not boot from GPT. We blacklisted Lenovo, falling
back to msdos labels in order to solve this.
Thanks to Matthew Garrett we found that switching on the boot flag of
the GPT's protective MBR these BIOS's would then boot from GPT. Matthew
wrote a patch for parted to allow controlling this flag using the
disk_set pmbr_boot command in parted. This is in parted-3.0-7
In anaconda-17.6 I have reverted the Lenovo blacklist and changed things
so that pmbr_boot is always set on GPT labeled installs. This should
ensure that thing boot correctly.
If this still causes problems the symptom will be that grub never starts
and the bios may complain about not being able to find an OS. If you
have problems with this please open a bug with the output from dmidecode.
You can still force usage of msdos partitions by passing nogpt on the
kernel cmdline.
Reply to: