13 of 13Image
(Image: Screenshot by JA Watson/ZDNet)
Installation complete, reboot
When the installation is complete, I am prompted to reboot (or continue working with the Live system).
On both of my UEFI systems, I got the same surprise with Ubuntu that I had already gotten with openSuSE and Fedora — reboot didn't bring up Ubuntu, it still brought up whatever was booted before I did any of this (in most cases, this will be Windows 8).
Now, there may be other systems, from other manufacturers that do in fact get UEFI boot parameters set, stored and stable properly so that they boot Ubuntu, but that hasn't been my experience. Oh, and there is another even bigger problem...
If you still have Secure Boot enabled, which was the purpose of this exercise, then when you finally do try to boot Ubuntu (probably by pressing Boot Select), you are going to be very surprised to find that it doesn't boot.
At least, it didn't for me, on either one of my systems. What the heck is that about?
The Live image on a USB stick worked just fine with Secure Boot enabled, but the installed system won't? Really? I must be wrong about this. I must be confused. I must be doing something wrong. But I can't figure out what, and I have installed Ubuntu 13.04 quite a few times now over the past six weeks or so.
I keep thinking this is some kind of pre-release problem, and they will get it sorted out before the final release, but time is running out.
Anyway, although I hope that they get this working, if they don't then you will have to disable Secure Boot for Ubuntu. Note that this means only secure boot, it works just fine with UEFI Boot then, you don't have to go all the way back to Legacy Boot.
Oh, and one last note for others who might have a system with the same Ralink 3290 wi-fi adapter my HP has. Although it doesn't work with Ubuntu 13.04 out of the box (at this stage), it actually has the correct kernal and drivers, all that is missing is the firmware file. I was able to "cheat" and copy the file /lib/firmware/rt3290.bin from either openSuSE 12.3 or Fedora 18, and then after rebooting, it works just fine. If you don't have one of those distributions, I believe that you can pick up the firmware file from the Rallink web page.