[SOLVED] Install F17 in DualBoot on Samsung NP300E7A that has Win7 HP
Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Install F17 in DualBoot on Samsung NP300E7A that has Win7 HP
I've been searching a lot on this but can't find something that works.
I've been fidling with RedHat's OS's since RedHat 7 so if this works, GREAT
but if I have to go with some other OS... then so be it. (but I know ppl has got this working)
First I had had problems with partitioning and since that was due to 3 primary partitions already on
the HDD I nuked the recorvery partition and after that I could get beyond that problem.
Now I'm in trouble again
It keeps asking me to set the boot partition to GPT(or something) and I read somewhere that if I would
delete some file (can't recall the exact name) but it ended with .gpt many people got it to work.
I tried that but after that the CD wouldn't boot, I tried 4 CDs of the NetInstall(that I modified) and still
the same result.
How can I fix this "error"?
(I wanna nuke winblows but wifey won't let me.. yeah I'm a wuss)
GPT is required for disks larger than 2 terabytes. gdisk is the command to create and modify GPT tables. See this link for some insight into GPT's. http://en.wikipedia.org/wiki/GUID_Partition_Table
Does your system have a standard BIOS or is it UEFI?
man gdisk has a lot of information as well.
I don't have a 2 terabyte disk, so have not used gdisk. I have read several threads on this topic, so you may find useful information on the forum. UEFI is another bag of snakes.
The disk is just 500G and.. hmm about the BIOS and UEFI, I can't tell 'cos I have no clue what to look for
although I haven't seen anything with those letters in it.
Can't even turn OFF the stuff that let me see the boot text that usually shows (as far as I know)
Laptop: "Samsung NP300A7E-A04SE" http://www.samsung.com/se/support/mo...ownloadName=UM
New: Have no idea, as of "creation" time, but I guess new-ish.
BIOS: Yeah, have already been there and changed the bootup order. I need to try to boot on other stuff before the HDD
I am running Fedora17 dual boot with Win7 on a 320GB hard drive and had no issues during installation. Are you getting these messages from the Fedora install program? How big is your /boot partition?
In your BIOS, can you check the boot order of devices?
If you are trying to install Fedora from a DVD-ROM drive or USB drive that is booting up in UEFI mode and you are trying to install to a hard drive that is not partitioned in GPT style (i.e. it has a Master Boot Record) the installer will probably stop and give you this error. You can go into the BIOS and have the boot device boot in the normal "non UEFI" style, or you could repartition the hard drive in the GUID style.
First, how can I tell F17 to partition it using UUID? Can't think of a place where it asks for that(unless in a place by clicking a option I haven't checked out)
Oh that one, DOH! didn't think of it I just turned that off and I'll see what happens.
I Think it even was 'disabled' as default but why call it "UEFI/Legacy boot" as I've seen,
when I also saw this: "UEFI will also enable support for partitions greater than 2TB under GPT (guid partition table)."
and in here: http://en.wikipedia.org/wiki/GUID_Partition_Table
Quote:
...(Intel's proposed replacement for the PC BIOS)...
Using partitions greater then 2TB and to use GPT can't be called legacy as far as I think... or?
Ain't Win7 "new" enough to handle UEFI?
I KNOW Linux would be able to so why would there be a problem at all since 'ENABLE' will, as it says, just ENABLE it not FORCE it.
There is other reasons to have a GPT style drive than just the 2TB limit.
If the BIOS is running in UEFI mode it will not boot up a device that has a MBR. The boot drive needs to be partitioned in GPT. I guess that the installer saw this and rejected the install. Windows 8 installs are running into this issue also.
Last edited by snafflekid; 11-28-2012 at 03:10 PM.
There is other reasons to have a GPT style drive than just the 2TB limit.
If the BIOS is running in UEFI mode it will not boot up a device that has a MBR. The boot drive needs to be partitioned in GPT. I guess that the installer saw this and rejected the install. Windows 8 installs are running into this issue also.
OK, so it aint possible for BOTH MBR and UEFI at the same time, got it.
Quote:
Originally Posted by snafflekid
Windows 8 installs are running into this issue also.
and that is that it can't handle UEFI at all or...??? didn't really get that part.
Win 8 can read GPT drives, as can Win 7, Vista and later Linux distros. That is how they can access >2TB space on a drive. I am referring to data storage drives and not the boot drive.
The BIOS can be set to start up in "UEFI" or "Legacy BIOS" mode. If you try to boot from a hard drive that is MBR while your BIOS is set to UEFI, it will not work. UEFI mode booting also requires the boot drive to be GPT. I do not know how your BIOS got started in UEFI mode when you began the Fedora install. I have seen BIOS that give choices for how to boot from a USB thumb drive or optical drive in "UEFI" or "Legacy BIOS" mode.
There may be some exceptions to this rule, I am not an expert. There are some systems out there like Itanium processors that this might not apply.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.