Maximus VII Ranger
Bios version 3003
Build date 10/28/2015
intel i5-4460 @ 3.20GHz
FOG version 1.5.5
Chainloader = undionly.kpxe
I have a dual-boot Windows 10/Linux (Zorin 12.4) installation.
Windows 10 is installed on a NVMe 250GB SSD.
Zorin was installed on a Western Digital hard drive.
Both operating systems were installed BIOS legacy mode.
I had Network Booting set up and FOG was working fine.
Then the Western Digital hard drive failed so I replaced it with hardware raid using a StarTech 4 port PCIe SATA III 6Gbps RAID Controller Card with two 2TB Western Digital hard drives.
I had to re-install Zorin so I did so in UEFI mode. Then I had problems dual booting as BIOS legacy and UEFI are not compatable so I converted my Windows 10 installation from Bios Legacy to UEFI by following the instructions here:
Current BIOS settings:
Advanced --> Network Stack Configuration --> Network Stack [Enabled]
Ipv4 PXE Support [Enabled]
Ipv6 PXE Support [Enabled]
CSM(Compatibilty Support Module)
Launch CSM [Enabled]
Boot Device Control [UEFI and Legacy OPROM]
Boot from Network Devices [Legacy OPROM first]
Boot from Storage Devices [Both, UEFI first]
Boot from PCI-E/PCI Expansion Devices [UEFI driver first]
Advanced --> Onboard Devices Configuration --> Intel LAN Controller --> Intel LAN PXE Option ROM [Enabled]
My current Boot Options (in order) are:
IBA GE Slot 00C8 v1547
MARVELL Raid VD (1907649MB)
Windows Boot Manager (Samsung SSD 970 EVO 250GB)
P2: Asus DRW-24BSST
After the FOG splash screen I now get a blank screen with a blinking cursor in the top right hand corner. I also get this outcome if I make “MARVELL Raid VD (1907649)” the second boot option (after “IBA GE Slot 00C8 v1547”). I also get this outcome if I choose “MARVELL Raid VD (1907649)” as the “Boot Overide” in the BIOS.
If I go into the BIOS and chose “ubuntu” as the Boot Overide, or make “ubuntu” as the first boot option, bypassing network booting entirely, the Grub menu appears and I can boot into either Zorin or Windows no problem.
If I remove “MARVELL Raid VD (1907649MB)” as a Boot Option entirely once I get to the FOG splash screen it counts down from 3 with the “Boot from hard disk” option selected then the screen refreshes and it starts the count again. Over and over. That’s as far as it gets. For some reason FOG does not want to pass the boot control over to “ubuntu”?
As I am able to continue the boot process by choosing “ubuntu” from the BIOS I am thinking there is a setting in FOG somewhere I need to tweak to resolve this?
Have pressed the CLR_CMOS button to reset the BIOS and repeated the entire process. No change.