• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

The "Linux questions (and other stuff)" thread

Dngrsone said:
Damn!

I downloaded the .iso, verified the md5 hash, and tried burning the image to DVD.

Three times-- twice using Brasero (hangs up trying to verify the burned disc), once (theoretically successfully) with Win 8.1.

The laptop fails to recognize any of the discs as having any data on them.

I am going to have to use Dngrswife's machine, I guess.
Click to expand...

What distro?
 
Not sure it matters that it is efi most distros have efi support. I would try the usb really shouldn't be any difference From installing from cd or usb
 
As ridiculous (-ly awesome?) as it sounds, I've lately been using a single DVD-RW disc to burn my isos, linux or otherwise, onto. Just format > start burning. UEFI or non-UEFI, 32 or 64 bit, its all worked well.

Dngrsone, you could always use imgburn to burn your dvd isos -- the program in my exprience is intelligent enough to predict and avoid burning errors and has NEVER produced a coaster. :D
 
I'll keep that in mind, Joel. The USB Image writer did the job right the first time, though.

I just have to figure out the best way to go about this so I don't break my existing installs...
 
Hmmm.....perhaps my UEFI linux dualboot how-to could be of some use here? :D

What other installs are you putting this one alongside? If they're modern enough (Win8.x) I'd say you could ignore the parts about turning secureboot off as ubuntu 14.04 should fully support it. I know mint 17 does.

Just remember, though, if you are doing a manual partion setup and have other existing OSes, you'll need to drop the bootloader into the ESP partition, not the beginning of the drive. In my case its /dev/sda2 as opposed to straight /dev/sda.
 
Joelgp83 said:
Hmmm.....perhaps my UEFI linux dualboot how-to could be of some use here? :D

What other installs are you putting this one alongside? If they're modern enough (Win8.x) I'd say you could ignore the parts about turning secureboot off as ubuntu 14.04 should fully support it. I know mint 17 does.

Just remember, though, if you are doing a manual partion setup and have other existing OSes, you'll need to drop the bootloader into the ESP partition, not the beginning of the drive. In my case its /dev/sda2 as opposed to straight /dev/sda.
Click to expand...

I have Win 8.1 and Mint 15 with rEFInd as my boot manager.
 
Then (if I read your other post right in moody's other thread), you'll still need to drop grub into /dev/sda2 and rEFInd should handle the rest, if it's designed to take a roll call of what's in your /EFI/boot/ directory at boot time.

If not, you need to go through whatever manual update process rEFInd has to get it to show up.

-edit-
Crap, hold up, just remembered. Both mint versions set their EFI files in /EFI/boot/Ubuntu/.

Are you just upgrading, or are mint 15 and 17 gonna be alongside? If doing a side by side, you're gonna have to rename the current Ubuntu folder to something else, pre-install, then let the mint 17 installer make a new one, then configure rEFInd with everybody's new locations.

And try not to let it chainload to grub. It has a bug where it won't find any mint bootloaders that aren't in a folder named ubuntu. Stupid, I know, but as far as I know they haven't fixed it yet.
 
They are going to be side-by-side for now-- I like to have a known-working one while I mess around with a new one.

I normally have my computer in Secure Boot, so in order to have Mint running I had to certify my mint installer. That bypasses the boot chain.

I am thinking that what will happen after the install is that the machine will default boot to Win, and I will be able to tell Windows 8.1 to use the rEFInd boot manager again.

I just hope I will not have to do some juggling in the CLI mode after that.
 
I take it you're not using the standard shim that mint 17 comes packaged with? I am using secureboot, too, and the installer was able to pass all the cryptographic key checks without me needing to fiddle with it in the first place....
 
From experience, you'll need to run the installer iso with secure boot on, so that it boots using the shim and then, when it comes to installing the kernel and grub2, it knows to put the shim there too.

Downside is that if you ever look at your UEFI boot menu, you may have two ubuntu boot entries. One is shim'd, the other is not, and won't work with secure boot. This is apparently intentional on the part of the installer designers.
 
Joelgp83 said:
From experience, you'll need to run the installer iso with secure boot on, so that it boots using the shim and then, when it comes to installing the kernel and grub2, it knows to put the shim there too.

Downside is that if you ever look at your UEFI boot menu, you may have two ubuntu boot entries. One is shim'd, the other is not, and won't work with secure boot. This is apparently intentional on the part of the installer designers.
Click to expand...

I find all this fascinating and informative, as I've not had the occasion to deal with it myself. Love seeing this kind of helpful info posted and shared. :)
 
Dngrsone said:
Hmm... Didn't work that way last time. I guess I will turn Secure Boot back on and see what happens.
Click to expand...

Not surprised. Mint 15 is based on what, 13.04? I had secure boot problems with 13.04 but not 13.10 and onward.

Prinny said:
Weird. On my one laptop with secure boot..I disabled it and poof...was done. O.o huh...
Click to expand...

I, uh,, .....wha?! I think your subject-verb agreement in that sentence is missing. :p I also like a little more "story" with my story, thank you. ;)
 
Ha! I had to get some coffee. All is well now.

What I meant by that is I have a satellite C855D laptop, came with Windows 8, secure boot and such. I went into the BIOS, disabled said option, and was able to install a new OS without an issue. Never has to run an installer with secure boot on.
 
Meh, spoke too early. The new Grub installed (which does work in Secure Boot) has taken over as boot loader, so now I have to figure out how to restore rEFInd. I may have to reinstall it from within Mint 17...
 
Okay, fixed it with:

Code: 
sudo efibootmgr -o 0005
where hex 0005 is the ident for the rEFInd bootloader.

I have to weed out some of the useless kernels...
 
It's at 0.5, dude. I have trouble enough with 'finished' DEs like Unity when they first come out.


... oh, BTW I will have to certificate that new install, probably because I am using a different bootloader. Not too big a deal, just have to relearn how to do it.

Unfortunately, I may have to send my laptop back out to Toshiba again, because it seems they broke my optical changing my battery. :(
 
You must log in or register to reply here.
Back
Top Bottom