Looking for advice - dualbooting ;)

[SwoRNLeaDejZ]

Could be the placement of the partitions. My setup is recovery, EFI, C:\ (Win8 partition), Ubuntu partition, Ubuntu swap, recovery. Try it that way.

If you still can't get the "install alongside" option, try going back one screen, press Ctrl+Alt+T to open a terminal window, and then go

sudo modprobe efivars

then exit the terminal window, and continue on. If it still doesn't work, then you may not truely be running in UEFI mode. The lack of an EFI partition on your layout is concerning. Can we get a pic of Disk Management's output?



I've never got Secure Boot support working on 13.04, but I've got someone's else's system to actually do it. Not sure why it worked on hers but not mine.....

Going to take my laptop with me to work tomorrow and I'll toss up some screen shots then. Had to take a break it was driving me insane

One interesting fact, windows doesn't recognize the Ubuntu partition (lists as unknown) and gparted reacts the same way to my recovery partitions.

 

[Joelgp83]

One interesting fact, windows doesn't recognize the Ubuntu partition (lists as unknown) and gparted reacts the same way to my recovery partitions.

This is normal. Linux installs typically use the EXT2, EXT3, or EXT4 disk format. Windows does not know how to read it (possibly because Microsoft doesn't want to condone the use of Linux), so it simply lists it as unknown.

On the other hand, I've no idea why gparted can't recognize the recovery partitions. They are typically FAT32, and usually have a drive label called "Recovery". Either way, don't touch them. Better to not play with fire in case something completely hoses both your Linux AND Win8 installs.

 

[SwoRNLeaDejZ]

This is normal. Linux installs typically use the EXT2, EXT3, or EXT4 disk format. Windows does not know how to read it (possibly because Microsoft doesn't want to condone the use of Linux), so it simply lists it as unknown.

On the other hand, I've no idea why gparted can't recognize the recovery partitions. They are typically FAT32, and usually have a drive label called "Recovery". Either way, don't touch them. Better to not play with fire in case something completely hoses both your Linux AND Win8 installs.

Dude, you truly are a godsend and a genius.

I formatted the partitions and started over. This time I did 198GB for the install and a 2GB swap. Installation finished perfectly and i rebooted... Went straight to Windows

Rebooted into the LiveCD.. Ran boot repair and this time I chose yes to backup and replace the windows UEFI files and reinstall grub, fixing what boot repair called a buggy kernel. Rebooted, this time it wouldn't boot windows at all

I used a repair disc to get into bios settings, I noticed an option that I hadn't seen before: Enable F12 to open boot menu. I enabled it. Now, when the Gateway logo displays, I press F12 and get 3 options, the top one Windows Boot Utility takes me to Windows, either of the other options opens grub, and allows me to either boot into windows or ubuntu. Problem solved.

One thing i did have to do, after I ran boot repair the first time, I booted back to ubuntu and chose advanced options in boot repair and set an option called 'OS to boot by default' to Windows.

Either way, it's working now, and if i had listened to you from the beginning, I would have ended this headache three days ago

 

[MoodyBlues]

Problem solved.

Awesome!

 

[Dngrsone]

Sorry I am coming late into this thread... because life.

Anyway, from what I understand, Ubuntu 13.04 has a unique way of dealing with UEFI, and from what I understand from someone who is currently playing with 13.10beta that the upcoming version will be much better at handling UEFI and secure boot.

I went with rEFInd for dual-booting my Toshiba Satellite S55t, and after a few days of work managed to get the laptop to work with Secure Boot enabled for both Win 8 and Mint 15.

The key was digitally signing the kernel manually.

 

[SwoRNLeaDejZ]

Sorry I am coming late into this thread... because life.

Anyway, from what I understand, Ubuntu 13.04 has a unique way of dealing with UEFI, and from what I understand from someone who is currently playing with 13.10beta that the upcoming version will be much better at handling UEFI and secure boot.

I went with rEFInd for dual-booting my Toshiba Satellite S55t, and after a few days of work managed to get the laptop to work with Secure Boot enabled for both Win 8 and Mint 15.

The key was digitally signing the kernel manually.

Sounds like a fun process (kidding)

I couldn't have possibly installed it with Secure Boot enabled, as Windows blocks the disc every single time. I don't understand how Microsoft including the Secure Boot feature doesn't equal some type of violation of monopoly laws in this country, and worldwide. It's total BS.. Microsoft didn't make my computer, Gateway did, why does Microsoft even get a partial say in what I can and can't install on it? If i owned a TV company, and sold the most powerful amazing TVs, and then included a feature that made it so you could only watch NBC, people would have a meltdown and sue the living hell out of me, and i would deserve it. Or if Dunkin Donuts made travel mugs where the bottom fell out if you filed them with Starbucks Coffee.. People would have a lot to say about that... Such crap.

 

[Dngrsone]

Well, I did have Secure Boot disabled to install Mint and for the first week while trying to get rEFInd working correctly and everything.

But once I understood the steps required to get the kernel signed, I got Secure Boot re-enabled; if only because it removes a superfluous error page during boot-up (I seriously doubt any malware is gong to show up trying to hijack my EFI boot, which is theoretically what MS is trying to 'prevent').

 

[Joelgp83]

Joelgp83, after SwoRNLeaDejZ gets his situation resolved, if there are any other changes you want to make to your instruction post, please do--and then I'll replace the copy in the Linux thread with the updated version. If there won't be any additional changes, then I'll replace it with the version in this thread as it stands now.

I don't have a lot of time right now (gotta go to bed), but I just want to say that last Thursday we had a modern UEFI Gateway desktop come into my school and stumped everyone else who was trying to get it reset to get win7 on it. cguru:

I got to futz with it and upon reviewing my notes of that encounter I can confirm that many of the UEFI BIOS issues SwoRNLeaDejZ had were also seen in that desktop (POST Boot device selection hotkey disabled by default, which keys you need to press, wording of options in the BIOS, etc), and that they are altogether different than the multiple UEFI HP systems I've worked on.

For that matter, the Dell Optiplexi we use in school (UEI College's CST training program :rock also use an entirely different POST hotkey scheme than either Gateway or HP. :banghead:

It seems each manufacturer, while keeping to the Win8/UEFI spec, has their own interpretation of how to implement the BIOS/POST environment settings. I may need to greatly modify my instructions to be per-manufacturer, which would mean multiple posts.....

 

[SwoRNLeaDejZ]

I don't have a lot of time right now (gotta go to bed), but I just want to say that last Thursday we had a modern UEFI Gateway desktop come into my school and stumped everyone else who was trying to get it reset to get win7 on it. cguru:

I got to futz with it and upon reviewing my notes of that encounter I can confirm that many of the UEFI BIOS issues SwoRNLeaDejZ had were also seen in that desktop (POST Boot device selection hotkey disabled by default, which keys you need to press, wording of options in the BIOS, etc), and that they are altogether different than the multiple UEFI HP systems I've worked on.

For that matter, the Dell Optiplexi we use in school (UEI College's CST training program :rock also use an entirely different POST hotkey scheme than either Gateway or HP. :banghead:

It seems each manufacturer, while keeping to the Win8/UEFI spec, has their own interpretation of how to implement the BIOS/POST environment settings. I may need to greatly modify my instructions to be per-manufacturer, which would mean multiple posts.....

Dude, you know what the worst part is? There is an option to enable the BOOT MENU but there is no option to enable a bios hot key combo during post. The only way I can get into bios is to SHIFT + RESTART windows 8,and then choose troubleshoot, advanced options, UEFI firmware settings. It's almost like they try as hard as they possibly can to make it as hard as possible, for you to use anything other than a Microsoft product. Something needs to be done in an anti monopoly sense to end this.

 

[MoodyBlues]

I don't have a lot of time right now (gotta go to bed), but I just want to say that last Thursday we had a modern UEFI Gateway desktop come into my school and stumped everyone else who was trying to get it reset to get win7 on it. cguru:

I got to futz with it and upon reviewing my notes of that encounter I can confirm that many of the UEFI BIOS issues SwoRNLeaDejZ had were also seen in that desktop (POST Boot device selection hotkey disabled by default, which keys you need to press, wording of options in the BIOS, etc), and that they are altogether different than the multiple UEFI HP systems I've worked on.

For that matter, the Dell Optiplexi we use in school (UEI College's CST training program :rock also use an entirely different POST hotkey scheme than either Gateway or HP. :banghead:

It seems each manufacturer, while keeping to the Win8/UEFI spec, has their own interpretation of how to implement the BIOS/POST environment settings.

Thanks for that info.

Wow...that's really crazy.

I may need to greatly modify my instructions to be per-manufacturer, which would mean multiple posts.....

Whew! That could turn into a Herculean task. Is there enough commonality that generic instructions for that part of the process could suffice? And/or let people ask for help with their specific manufacturer? Somehow keeping it to one main post...

 

[SwoRNLeaDejZ]

Thanks for that info.

Wow...that's really crazy.


Whew! That could turn into a Herculean task. Is there enough commonality that generic instructions for that part of the process could suffice? And/or let people ask for help with their specific manufacturer? Somehow keeping it to one main post...

In speaking with other people and looking at a variety of the laptops at work, I think the majority of the process is the same, with tweaks and edits depending on manufacturer.

The problem seems worst on any HP machines.

 

[Davdi]

Just turn Secure boot off and use legacy boot. Then it works just like pre-secure boot. I wouldn't trust secure boot anyway, not while Microsoft is responsible for signing. They can revoke a certificate at any time, then you're up the proverbial creek, as the Linux shim (or whatever other device is used to enable secure booting with Linux) won't be trusted or able to boot. Not that I'm being cynical or anything.

 

[Dngrsone]

Actually, you can self-sign... it's just Ubuntu's shim that is wrong.

Look here for more information.

 

[Joelgp83]

Whew....lotta questions to answer.

Dude, you know what the worst part is? There is an option to enable the BOOT MENU but there is no option to enable a bios hot key combo during post. The only way I can get into bios is to SHIFT + RESTART windows 8,and then choose troubleshoot, advanced options, UEFI firmware settings. It's almost like they try as hard as they possibly can to make it as hard as possible, for you to use anything other than a Microsoft product. Something needs to be done in an anti monopoly sense to end this.

We encountered the same thing on the UEFI gateway machine at school. Sadly, I was the only one who knew Win8 well enough to pull that trick to get into the BIOS. Saved my instructor and everyone else a whole weekend of head scratching.

Whew! That could turn into a Herculean task. Is there enough commonality that generic instructions for that part of the process could suffice? And/or let people ask for help with their specific manufacturer? Somehow keeping it to one main post...

The differences mainly concern which buttons to push, whether you can directly access the BIOS or have to go thru Win8 to do it, and what you need to enable in the BIOS to get there. Once the install disc gets booted, its generally going to be the same.

In speaking with other people and looking at a variety of the laptops at work, I think the majority of the process is the same, with tweaks and edits depending on manufacturer.

The problem seems worst on any HP machines.

Actually, I've found the best ones are HP machines. They're up-front and consistant about what buttons to push across their models (F2 to access UEFI diagnostics, F9 to select Boot device, and F10 to directly access BIOS options)

Just turn Secure boot off and use legacy boot. Then it works just like pre-secure boot. I wouldn't trust secure boot anyway, not while Microsoft is responsible for signing. They can revoke a certificate at any time, then you're up the proverbial creek, as the Linux shim (or whatever other device is used to enable secure booting with Linux) won't be trusted or able to boot. Not that I'm being cynical or anything.

IMO, if you've got the ability to run your OS in UEFI mode you should. What with the faster handoff/bootup times and simpler boot device selection (in Legacy mode, all your drives show up twice -- one for Legacy and one for UEFI).

Furthermore, running in UEFI mode and keeping legacy mode off is a more resilient setup if, say, either the Win8 bootmgr or GRUB get corrupted. Since they don't overwrite each other but have their own separate side-by-side EFI Partition entries, the utter destruction of one won't require a boot/repair disc to get into the other. :thumbup: