leetNightshade
/
help-center-docs
Archived
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
This repository has been archived on 2024-04-14. You can view files and clone it, but cannot push or open issues or pull requests.
help-center-docs/troubleshooting/installation-issues/en.md

26 lines
2.1 KiB
Markdown
Raw Permalink Normal View History

Add metadata to troubleshooting docs, moved Boot Rescue to it. Renamed doc for Printer Compat, added some spacing.
2017-09-22 17:13:43 +00:00
+++
title = "Installation Issues"
lastmod = "2017-09-22T20:13:14+03:00"
+++
Provide some generic troubleshooting information Experience on the forums and IRC has led to many questions cropping up over again. This commit begins trying to document common solutions for multiple reasons. - Allow users to find answers to issues themselves through help center search. Hopefully this can avoid users making support queries. - Allow other users to provide support to others backed by the help center. We aren't around all the time to answer questions. - Document some parts that aren't well known and differ a lot on Solus. Particularly adding kernel parameters on boot. Signed-off-by: Peter O'Connor <peter@solus-project.com>
2017-09-22 04:27:34 +00:00
# Installation Issues
Add some article summaries / descriptions for the Help Center.
2017-09-22 17:22:49 +00:00
This article covers various issues that you may come across during installation of Solus.
Provide some generic troubleshooting information Experience on the forums and IRC has led to many questions cropping up over again. This commit begins trying to document common solutions for multiple reasons. - Allow users to find answers to issues themselves through help center search. Hopefully this can avoid users making support queries. - Allow other users to provide support to others backed by the help center. We aren't around all the time to answer questions. - Document some parts that aren't well known and differ a lot on Solus. Particularly adding kernel parameters on boot. Signed-off-by: Peter O'Connor <peter@solus-project.com>
2017-09-22 04:27:34 +00:00
## Can't install in EFI mode
Add metadata to troubleshooting docs, moved Boot Rescue to it. Renamed doc for Printer Compat, added some spacing.
2017-09-22 17:13:43 +00:00
The live ISO will attempt to install Solus by the same method it was booted. If it is unable to install the boot loader to the ESP, then it is likely booted in legacy mode. Ensure that the ISO has been created via a [supported method](/articles/installation/preparing-to-install/en/) and that an EFI boot is selected from the boot options.
Provide some generic troubleshooting information Experience on the forums and IRC has led to many questions cropping up over again. This commit begins trying to document common solutions for multiple reasons. - Allow users to find answers to issues themselves through help center search. Hopefully this can avoid users making support queries. - Allow other users to provide support to others backed by the help center. We aren't around all the time to answer questions. - Document some parts that aren't well known and differ a lot on Solus. Particularly adding kernel parameters on boot. Signed-off-by: Peter O'Connor <peter@solus-project.com>
2017-09-22 04:27:34 +00:00
You can check whether the Solus ISO has booted in EFI mode by checking the for the existence of `ls /sys/firmware/efi` (if it's not found, then it's booted in legacy mode).
## I can't boot into Solus after installation!
There are some misunderstandings with how legacy and EFI boot works (usually implemented as UEFI). These sections cover the common misconceptions.
### Legacy/BIOS installation
Legacy installations on Solus use the Grub boot loader on an MBR disk. Only one boot loader can be used on an MBR disk, so if you haven't installed the Solus boot loader on the MBR, you will need to boot into the other OS and update grub prior to being able to boot Solus. This will also be required on each update of the kernel to ensure you're booting in the latest release.
### EFI
Fix a couple of hyperlinks in troubleshooting docs Signed-off-by: Peter O'Connor <peter@solus-project.com>
2017-09-23 12:38:01 +00:00
EFI allows for multiple boot loaders to be installed, which means you can boot the Solus boot loader directly. To ensure you are booting Solus you need to boot `Linux Boot Manager` from the EFI options. Common keys for bringing up a boot menu or the options during boot are hitting `Esc/F2/F9/F10/F11/F12` during boot (this differs per motherboard). If a boot loader for another OS is not listed in the menu, then it is not correctly registered (and therefore not installed correctly). You can make the Solus boot menu appear via [Displaying the Solus boot menu on boot](/articles/troubleshooting/boot-management/en/#displaying-the-solus-boot-menu-by-default-on-boot) which should be able to boot windows (as it's registered with UEFI properly) as well as Solus, but not other systems.