2

I have Dell 5110n laptop that belongs to 2011 so it won't support UEFI at all. Now I just wanna know how can I:

  1. Make bootable USB flash for JUST Legacy mode
  2. Force Ubuntu to install only in Legacy mode

I want install Ubuntu dual boot with Windows 10 (Version 1709 build 16299.461).

I read this question and also deleted EFI directory but the Ubuntu still doesn't show Keyboard icon that shows it loaded in UEFI mode.

and if I don't make EFI partition it gives me the below error: Force Ubuntu to boot just in Legacy

also when I make an EFI partition it will gives me this error at the end and will fail the installation process:

Install Ubuntu Dell 5110n Legacy mode

P.S: I know I should boot my USB in just Legacy mode because my Windows installed in Legacy mode too. But I don't know how should I do that. Either make bootable USB (with Rufus or Universal USB installer) or just force Ubuntu to boot in Legacy. P.S: My bios doesn't have any "Fast boot" or "Secure boot" option or any way to boot in UEFI.

so can you please give me a hand? Thanks in advance

2 Answers2

1

I have the same issue on a pre-uefi GA-EX58-UD4P mb with award bios. I get the fatal error installing ubuntu 20.04 on a new SSD. A live boot-repair usb also fails to install boot loader due to the session having booted in "compatibility" mode. I did find a work around by shutting down after a "fatal error" install, then plugging in and booted an old ubuntu hdd. Then did "sudo update-grub". Shut down + unplugged the old hdd. Booted the new install and the link to it appeared in the grub bootloader screen. I suspect using a live usb session to mount the disk the failed install is located on then using "sudo update-grub" might have worked too.

Nankeen
  • 11
  • 3
1

The problem has been solved. Here is the solution for those have same problem like me:

The reason of getting error was having two HDD. The old HDD, and new one is SSD. So the Bootloader was stored on old HDD meanwhile the Ubuntu installed on SSD and when I was trying to fix grub, it was trying to fix old HDD. So my friend fixed Bootloader with EasyBCD app and then problem solved because he set Bootloader to loading from SSD.

Hope this help many people.