My experiments with installing Ubuntu 13.04 (pre-release) with UEFI Boot
Summary: The Live image is Secure Boot compatible, but the installed system is not?
Image 13 of 13

(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.
Seriously.
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.
Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.
Talkback
Is it stable?
Clarify
is 13.04 full of bugs on the pre released version?
Thanks.
Not qualified to answer
jw
Why do you think you did something wrong?
Maybe Ubuntu has serious bugs in it and isn't ready for release? Why do you automatically assume you did something wrong? Since this works with the Live desktop and it works with SuSE, this clearly isn't an issue with Secure Boot, it is an issue with Ubuntu.
Don't give Ubuntu a pass on this one. There is clearly a very serious bug in the installer. You aren't to blame for this one.
Kudos on an otherwise fantastic blog post, again. You are up in Ed Bott and MJF territory with your posts and that is much appreciated. ZDNet needs more bloggers like you.
Others say it works
Thanks for reading and commenting.
jw
Have you submitted a bug report to Launchpad?
https://help.ubuntu.com/community/ReportingBugs
In addition, I didn't find a related bug described for Ubuntu 13.04 here:
https://launchpad.net/ubuntu/+milestone/ubuntu-13.04
Here is how that plays out
So no, thanks, I have not submitted a bug report. If I am right about this, then there are thousands of other people having the same problem, including plenty at Canonical, and they don't need me to add to the chorus. If I am wrong, then all is well with the world, I will never use Ubuntu anyway, and the world is a wonderful place.
Thanks for reading and commenting.
jw
Why is does the release contain mainly blank screens? Simple:
“The first screen in the installer has the language select, and a whole lot of empty space. I find this a bit baffling, why not fill that space with something, even if it is only Ubuntu propaganda? Seems like a waste to me, but perhaps there is a reason for it.”
There IS a reason for it: Shuttleworth has run out of time, people who believe in him, and people WHO BELIEVE HIM. He has few developers, no partners, no one to do the heavy lifting, and the press is turning against him; he has for too long found it more fun to generate promises of FUTURE product than real product (“...our VISION is clear...").
Shuttleworth doesn’t have the resources to finalise a major Ubuntu release; then again, one is hard-pressed to remember a release after 9.04 which was ready for prime time.
The answer is obvious: the screen is not filled up because of a lack of commitment and dedication on Shuttleworth’s part. Oh, and complete and total disdain of his users hasn’t hurt his rush to self-destruction, either.
@JAW--
You continue to amaze the REAL Linux community with your hard work and clear, concise writing. Your ability simplify and explain is among the best. Thank you from all of us.
Warmest regards...
Ubuntu review from an experienced Windows gamer...
"Last week Valve released Steam for Linux, the open-source, free-range operating system and liberating alternative to the increasingly walled-gardens of Windows and Macintosh. Hooray for that! To celebrate the launch, Valve are offering a free Team Fortress 2 penguin to anybody who follows them into Linux-town by installing the free OS...
...So here, in just seven easy steps, is how to easily install UBUNTU in order to win a TF2 penguin and then get back out again as quickly as possible...
...STEP THREE: Everything crashes all the time and nothing works
The borders around this error window [screenshot here] will disappear and, if you've followed the steps correctly, something called 'Compiz' will stop working. You can send an error report to help fix the problem. Alternatively you can shout an error report out of your bedroom window with much the same effect...
...MISTAKE TWO: I used the latest release of Ubuntu...
...MISTAKE THREE: I even used Ubuntu in the first place...”.
No comment. None needed.
Warmest regards...
Boot-repair to enable dual-booting
https://help.ubuntu.com/community/Boot-Repair
Tried that...
Again, if there is anyone who can say with authority "I installed Ubuntu 13.04 with UEFI Secure Boot ENABLED", please speak up, and hopefully share how you did it.
Thanks for reading and commenting.
jw