Changing BIOS (latest, 1.31) settings BIOS Startup->UEFI/Legacy Boot from "Both" to "Legacy only" has no effect. As FreeBSD AFAIK doesn't support UEFI boot, legacy boot should work picking up and starting pmbr (protected MBR record), but it doesn't.

However, FreeBSD 9 UFS-on-MBR installation (with mbr boot record and FreeBSD slice in MBR partition instead of GPT) works fine.

It seems to me that UEFI/Legacy Boot "Legacy" setting actually has no effect if 0xEE type Primary partition entry is present on disk.

First of all, has anyone installed Linux or FreeBSD with GPT partitioning scheme on latest Thinkpads?

And the second one, as I've saw similar problem on FreeBSD forum thread about T420s laptopI believethat this maybe a bugin the BIOS. How can I fill the bugreport or send an e-mail to support or developers, as, obvious, phone support can consult only about Windows OS.

I've got similar problems on my W520, it doesn't even attempt to boot from my GPT disk. Really it should be possible to boot GPT disks both in BIOS and UEFI mode, both Linux and FreeBSD support this (though as usual, Windows can't). I've got a suspicion that the Thinkpad bios/efi is not simply executing the first stage bootloader, but looking around on the GPT disk and then crapping its pants when it doesn't find Windows.

Right now I have a MBR-formatted harddisk in the ultrabay with the bootloader in the MBR. Once I get the bootloader off the MBR disk, I can easily continue to boot from my GPT-formatted SSD.

I asked an "expert" on the site and they said call a number for support. I called and there is only one option, for service requests and they said they do not support this issue. How are we suppoed to get this issue realized and find out how to get it fixed?

Hi fellow-sufferers! Same problem here on an E520 thinkpad. Legacy can't boot from an "ee" Protective MBR / GPT partitioned disk. Latest BIOS 1.23 for this model is installed. It' s a shame that lenovo only supports windows and ignores linux problems. Above problem should be easy to fix! Has anyone made direct contact to the devs of this BIOS series? Regards, Martin