I’ve just purchased a new PC, it had Win 8.1, which is little more use than a virus, so I obviously upgraded to Win10. It actually looks alright. Now my problems begin as I want to put OpenSUSE 13.2 onto the system. The system uses UEFI and whilst the installer is supposed to cope with that I have not had any luck.
It does not recognise the Win10 installation at all and wants to totally repartition the drive. Even when I go into expert mode I still cannot get it to behave. I found a linkthat discusses the fact that Win10 (at least the preview) does not create a GPT partition. This means nothing to me, but no doubt does to some of you. He goes on to say the Win10 preview “installer is only capable of creating partitions using an MBR partitioning scheme. And so you should be aware of that when creating partitions for installing any Linux distribution.” Again, not a lot of help to me, but it appears the released version has similar issues.
So how can I get my favourite OS installed and have a working dual boot setup?
If you by the first menu you mean when the LiveCD is booting, then yes, I am in EFI, ie. no options. I have created the partition I want to use for OpenSUSE in Win already. I previously had this working fine (on my old PC) with Win7, so the idea of setting it up is not new to me. The EFI stuff, however, is new. I’ve gone over several Youtube videos and as far as I can tell I am doing everything correctly. Despite this, I get several error/warning messages at the partition selection/setup phase. Obviously, something is still wrong. I’ll make detailed notes and post the error messages since you clearly can’t help if you don’t know what is going wrong…
You can not mix boot modes on dual boot machines and chain boot the other OS . You must turn off Fast boot in Windows. you can not mount a partition that has not been shut down correctly.and fast boot is fast because it does not bother with little details like shutting things down.
> get it to behave. I found a 'link ’ (http://tinyurl.com/q33wq2d)that
> discusses the fact that Win10 (at least the preview) does not create a
> GPT partition. This means nothing to me, but no doubt does to some of
> you. He goes on to say the Win10 preview “installer is only capable of
> creating partitions using an MBR partitioning scheme. And so you should
> be aware of that when creating partitions for installing any Linux
> distribution.”
No, that is simply not true.
I can’t currently read that link, but what you say is not possible.
> But this is how Sda is actually partitioned under Win10 Disk Management;
>
> 350 MB;NTFS;System Reserved;system, active, primary partition
> 858.20 GB;NTFS;Win10 install;boot, page file, crash dump, primary partition
> 450 MB;??;Recovery partition;Recovery partition Extended volume
> 65.83 GB;NTFS;I want to put Linux here;Logical drive
> 4.00 GB;NTFS;Want to use as swap;Logical drive
The installer should offer that 65 GB space if you erase that partition.
I’m unsure how to do that in Windows. If it sees all the space
partitioned and formatted, the installer doesn’t know what to do, and
may offer to destroy it all.
On 2015-09-19 16:46, arvidjaar wrote:
>
> robin_listas;2728953 Wrote:
>> but what you say is not possible.
> Of course it is. Windows can only be installed on MBR disk in on BIOS
> and only on GPT disk on EFI. The link describes installation on BIOS.
I understood he said that Windows 10 could not be installed on a GPT
disk, and could only be installed on an MBR disk.
What you say is that it has to be installed on MBR disk on a BIOS
machine is of course true, but that is not what he said
What I read on that link is that the writer got a test disk for BIOS
only: “For whatever reason, the ISO image I downloaded does not have a
UEFI-aware installer, so even when it’s installed on a computer with
UEFI firmware, the installer does not create GTP partitions.”
A misunderstanding, I’m sure
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Of course, because you missed where he wrote “the Win10 preview”! Like our Milestones, not the same as the release. After that, It doesn’t matter what you couldn’t “currently read that link”.
> Of course, because you missed where he wrote “the Win10 preview”!
No, I didn’t
What I said was that the OP assumption that W10 only installs on MBR
disks was wrong. He though so of the released version: “(…) but it
appears the released version has similar issues.”
To get this back on track. The original poster never actually said anything about the MBR, he (I) was quoting another site. I never suggested I fully understood what it was all about.
Anyway, I think I’ve got it worked out and I’m posting for others that may find themselves in the same situation. Over here https://bbs.archlinux.org/viewtopic.php?id=200453 there is a discussion that is of some relevance.
I also DO NOT have a EFI FAT partition on my drive, but the system does seem to be booting with EFI. I can’t be sure of this as I have no reference, but to me to it looks like it. Anyway, when I run “msinfo32” my system also has the BIOS set to Legacy. I’m assuming I can ‘blame’ the store for this, they installed Win 8.1, I merely upgraded.
So once I get Win10 installed in EFI mode I strongly suspect all will be well in the world again…
On 2015-09-20 06:16, arvidjaar wrote:
>
> robin_listas;2729014 Wrote:
>>
>> What I read on that link is that the writer got a test disk for BIOS
>> only: "For whatever reason, the ISO image I downloaded does not have a
>> UEFI-aware installer
> 32 bit Windows never supported EFI installation.
