MAY
9
2013
|
The Breakouts: UEFIMe and Rohan and Harald spent the day playing with the cheapo Sony Vaio laptop I got with Windows 8 and UEFI firmware. This laptop has many partitions: I've no idea why there are two efi partitions We installed Kubuntu but it didn't set up Grub and we couldn't do much useful at the Grub command line. So we installed Ubuntu Unity 13.04 and it successfully set up Grub so we could boot from Grub into Ubuntu. Grub also listed Windows 8 but it gives an error on trying to boot "error: can't find command drivemap error: invalid EFI file path". Grub also listed windows recovery and this does boot and lets us boot into Windows 8 but that then stops Grub being loaded so there's no way to reboot into Ubuntu. see log. Then we tried to install Kubuntu again and it give an error during install about the grub setup package not configuring right see bug for log. If you go to ubuntu.com to download it points Windows 8 users to this scary UEFI wiki page with scary headings like "Installing Ubuntu Quickly and Easily via Trial and Error". Conclusion: UEFI is a giant MS conspiracy to make installing Linux more faffy than it already is. Kubuntu is slightly more broken then Ubuntu but not much. Only silver lining is that Windows 8 is rubbish and when we tried it there genuinely was a notification saying "Warning: your children might not be protected". Think of the children and don't use Windows 8! Oh well, here's some pretty pictures to keep you amused. |
![]() |
Comments
Ignoring The Doctor?
VHanda, that needs an explanation, a good one, and fast!
Currently the best approach
Currently the best approach is to simply register the EFI partitions in the BIOS and then dual boot using the BIOS boot menu. That works on all systems I have encountered so far.
But yeah EFI is a huge pain. Try installing EFI with software RAID, that's so much fun. Took me 3 work days.
giving MSFT too much credit; Apple started the conspiracy
When I first joined my current job I had the pleasure to use a Mac pro for a few weeks. No BIOS in sight.
Quite a pain, though I didn't have it as bad as you all since I had no interest in dual booting. You would have been better off wiping all those confusing partitions.
It's a kernel problem
Jonathan, a commit added to kernel 3.8 is the cause of this problem. See LP bug 1167622 (and duplicates 1167567, 1168659). This is supposed to be fixed eventually.