On 03/02/2012 07:09 PM, Chris Murphy wrote:
On Mar 2, 2012, at 10:37 AM, Pádraig Brady wrote:
> Yep as expected F17 alpha is broken in the same way on my laptop.
Your laptop is what hardware? Any install media kernel parameters used? What installation
type? Can you provide both an fdisk and parted (or gdisk) listing of the post-installation
disk?
For earlier in the thread:
"Hmm, I tried that workaround I think on my Lenovo T520 with BIOS 1.29,
and it didn't help. I.E. point (1.) from the link referenced here:
https://bugzilla.redhat.com/show_bug.cgi?id=735733#c31"
You can see the boot flag is set to no avail in the disk
and parted output below:
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sda1 * 1 976773167 488386583+ ee GPT
Model: ATA ST9500420AS (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: pmbr_boot
Number Start End Size File system Name Flags
1 1049kB 2097kB 1049kB bios_grub
2 2097kB 526MB 524MB ext4 ext4 boot
3 526MB 500GB 500GB lvm
I've confirmed that installing with the "nogpt" flag is OK.
cheers,
Pádraig.