Reputation
18,838
Top tag
Next privilege 20,000 Rep.
Access 'trusted user' tools
Badges
1 14 37
Newest
 Nice Answer
Impact
~2.6m people reached

14h
comment Ubuntu 15.10 won't show up
Secure Boot is most likely not the problem; if it were, the installer would not have booted. My first guess is that Sylhfer accidentally installed Ubuntu in BIOS/CSM/legacy mode, with Windows already booting in EFI/UEFI mode; however, there could be another cause. Boot Repair might work, but if you don't want to roll the dice without knowing the odds of winning, first run Boot Info Script. This will create a file called RESULTS.txt. Post it to a pastebin site and post the URL to the document here.
16h
answered Still cannot load windows 10 even after using boot-repair
16h
comment ASUS N550JK - Ubuntu 15.10 install
The single most common cause of USB flash drives not booting is that they were prepared incorrectly. You didn't mention what tool you used to prepare the disk, or what options you selected. You may need to try another tool and/or change options. Some people need to try three or four tools before they find one that works. Rufus (Windows) and Unetbootin (cross-platform) are the most likely to work, but even they aren't guaranteed to work.
16h
comment Dual booting Windows 10/Ubuntu on a windows 8 pre-loaded machine
STOP! If the partitioning screen is showing no partitions, and if you want to dual-boot with a Windows that's already installed, proceeding will TRASH your system! The problem is likely caused by a damaged partition table, as described on this page of mine. Fix this problem before proceeding!
20h
comment Remove GRUB and keep a Linux system
A boot loader is required with either BIOS-mode or EFI-mode booting. EFI provides its own boot manager, which enables selecting what to boot; but a boot loader (which transfers control to the kernel) is still required. Where it gets a little dicey is that the EFI stub loader turn the kernel into its own EFI-mode boot loader, but technically it's still a boot loader. GRUB 2 is just one of several boot loaders available, but it is the default used by Ubuntu.
1d
comment Remove GRUB and keep a Linux system
You're right, underscore_d, but it goes even further than that. If the machine is booting in BIOS/CSM/legacy mode, alternatives to the default GRUB 2 include LILO, SYSLINUX, and GRUB Legacy; and if it's booting in EFI mode, alternatives include ELILO, SYSLINUX, GRUB Legacy, and the EFI stub loader, with the last of these being selectable via the firmware's built-in boot manager, gummiboot/systemd-boot, rEFInd, or even (awkwardly) rEFIt. In sum, the number of boot loader (and boot manager) options is pretty large. Switching from GRUB 2 may not be Magix's best option, but alternatives do exist.
1d
answered Ubuntu 14.04.3 live USB not booting in pre-installed Windows 10 machine
1d
answered Attempting to install Mint alongside Ubuntu, cannot add Mint to GRUB
1d
answered Dual booting Windows 10 and Ubuntu (UEFI mode) on a blank HDD.
2d
answered Resize efi partition on Ubuntu / Mac system on Mac Air
2d
comment Windows not loading after Dual Booting windows 10 & ubuntu 15
You may have a cross-mode installation (Windows in EFI/UEFI mode and Ubuntu in BIOS/CSM/legacy mode, or vice-versa), but I can't be sure of that. Please run the Boot Info Script in Ubuntu. This will generate a file called RESULTS.txt. Post that file to a pastebin site and post the URL to your document here. That will give us detailed information we need to make a diagnosis rather than a guess.
2d
answered boot Ubuntu 14.04.3 problem from grub2
2d
comment I can't install Ubuntu in my laptop
"Doesn't want to detect the usb" is a rather vague problem report. Please clarify -- WHAT is not detecting the USB drive? How was it prepared? What steps have you taken to get it to work? That said, my suspicion is that you prepared it incorrectly or with a broken tool. Rufus generally works well from Windows, but not always.
2d
answered Cannot Change the boot order in bios or F9 Anymore after installing Ubuntu
2d
comment How to dual boot Ubuntu with Windows 10?
Also note that how you prepare your installation media can be important; some tools omit the EFI-mode boot loader, or set it up in such a way that it doesn't work with some computers. If you can't get it to boot in EFI mode, try another tool. Rufus generally works well from Windows (you may need to fiddle with some of its options), and Unetbootin generally works from a variety of OSes. Even these may fail with some systems, though.
Feb
5
comment Dual boot Ubuntu and Windows 8: UEFI vs Legacy mode
Please see this question and my answer to it. Incidentally, you almost certainly can boot in EFI mode -- just not with the boot media you prepared.
Feb
5
comment efibootmgr creates an entry in which DevPath is set to Venhw istead of PciRoot
refind.conf does not take Linux device identifiers such as /dev/nvme0n1p6, so if you've used that identifier in refind.conf, it's not doing what you think it's doing. Chances are it's just not doing anything. If you can post the exact line on which you've used it (or the entire manual boot stanza, if it's in one of them), I could say more. (Please edit your original question and then add a comment here so I'll notice; do not put the refind.conf entries in a comment, since they'll be mangled.)
Feb
4
comment Can't mount or fix corrupt NTFS partition on working HDD
This is a problem with an NTFS volume. NTFS is a Windows filesystem, and repairing it is a Windows issue. Note that the Linux ntfsfix utility does only the most minimal checks and then flags the filesystem as needing attention in Windows. You should ask about this problem on a Windows forum. In a worst-case scenario, you may be able to recover individual files with PhotoRec, but proprietary Windows tools may do a better job of that, too. (Sorry, I have no links to what tools may do better; I've just heard that such tools exist.)
Feb
4
answered efibootmgr creates an entry in which DevPath is set to Venhw istead of PciRoot
Feb
4
comment efibootmgr creates an entry in which DevPath is set to Venhw istead of PciRoot
refind.conf will not normally include anything with a PciRoot specification; that's something you'll see in efibootmgr output -- but you won't even use that sort of specification in efibootmgr input..