Add metadata to troubleshooting docs, moved Boot Rescue to it. Renamed doc for Printer Compat, added some spacing.
This commit is contained in:
Joshua Strobl
parent
3fa7721461
commit
a8f51d81ca
|
|
@ -1,6 +1,6 @@
|
|||
+++
|
||||
title = "Printer Compatibility"
|
||||
lastmod = "2017-09-22T18:30:00+01:00"
|
||||
lastmod = "2017-09-22T20:09:00+03:00"
|
||||
+++
|
||||
|
||||
# Printer Compatibility
|
||||
|
|
@ -11,12 +11,16 @@ This list should not suggest that *only* such devices listed below are compatibl
|
|||
|
||||
In order to install your printer you will have to open `Printer Configuration` from Gnome Settings and click on `Add a Printer`.
|
||||
The following dialogs will guide you to choose the appropriate driver for your device
|
||||
|
||||
## Models
|
||||
|
||||
### Epson
|
||||
*Some Epson printers will only work if you install the `epson-inkjet-printer-escpr` package.*
|
||||
|
||||
**Some Epson printers will only work if you install the `epson-inkjet-printer-escpr` package.**
|
||||
|
||||
- Epson SX-125
|
||||
- Epson XP-540
|
||||
|
||||
### HP
|
||||
*If you own an HP printer you should install the `hplip` package in order to get your device working.*
|
||||
|
||||
**If you own an HP printer you should install the `hplip` package in order to get your device working.**
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
+++
|
||||
title = "VirtualBox"
|
||||
lastmod = "2017-07-22T15:17:22+03:00"
|
||||
lastmod = "2017-09-22T20:12:22+03:00"
|
||||
+++
|
||||
# VirtualBox
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,8 @@
|
|||
# Boot management
|
||||
+++
|
||||
title = "Boot Management"
|
||||
lastmod = "2017-09-22T20:12:14+03:00"
|
||||
+++
|
||||
# Boot Management
|
||||
|
||||
## Bring up the boot menu with no timeout set?
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
+++
|
||||
title = "Boot Rescue"
|
||||
lastmod = "2017-04-13T17:39:14+03:00"
|
||||
aliases = ["/articles/configuration/modifying-grub/en/"]
|
||||
lastmod = "2017-09-22T20:08:14+03:00"
|
||||
aliases = ["/articles/configuration/modifying-grub/en/", "/articles/repair-and-recovery/boot-rescue/en/"]
|
||||
+++
|
||||
# Boot Rescue
|
||||
|
||||
|
|
@ -1,10 +1,14 @@
|
|||
# General troubleshooting
|
||||
+++
|
||||
title = "General Troubleshooting"
|
||||
lastmod = "2017-09-22T20:10:14+03:00"
|
||||
+++
|
||||
# General Troubleshooting
|
||||
|
||||
This guide provides some basic troubleshooting instructions for when you have an issue in Solus. Before reporting bugs, it is important to validate your Solus installation doesn't suffer from missing files or disk corruption. Also ensuring the system is fully up to date as the bug may have already been fixed.
|
||||
|
||||
First of all performa a full system update `sudo eopkg up` (or via the Software Center). Then validate that packages are installed correctly and aren't missing files: (run this once, it will take some time and may not show much output)
|
||||
|
||||
```
|
||||
``` bash
|
||||
sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall
|
||||
```
|
||||
|
||||
|
|
@ -32,7 +36,7 @@ To run database recovery, run `sudo eopkg rdb` in the terminal and then updates
|
|||
|
||||
### Reverting updates
|
||||
|
||||
If booting into the previous kernel doesn't solve the issue, there may be an issue with the package updates. It is possible to [revert the updates](https://solus-project.com/articles/package-management/history-and-rollback/en/) (this would also confirm that the issue is in the selected updates).
|
||||
If booting into the previous kernel doesn't solve the issue, there may be an issue with the package updates. It is possible to [revert the updates](/articles/package-management/history-and-rollback/en/) (this would also confirm that the issue is in the selected updates).
|
||||
|
||||
## Boot Failure
|
||||
|
||||
|
|
@ -42,11 +46,11 @@ If Solus partially boots, you can generally get to a TTY using `Ctrl+Alt+F2` to
|
|||
|
||||
A common cause of not being able to boot is due to installing the nvidia drivers, but not booting into the latest kernel (the only kernel which has the drivers installed). Also ensure you have the correct driver version installed for your kernel. You can check if you have booted into the latest kernel by comparing the installed package with the booted kernel (instructions for both kernels)
|
||||
|
||||
```
|
||||
``` bash
|
||||
eopkg info linux-lts | head -n2; uname -a
|
||||
```
|
||||
|
||||
```
|
||||
``` bash
|
||||
eopkg info linux-current | head -n2; uname -a
|
||||
```
|
||||
|
||||
|
|
@ -56,17 +60,17 @@ If the kernel version and release don't match from lines 2 and 3 of the output,
|
|||
|
||||
- Another possibility is that the `ESP` has run out of space so the kernel cannot be copied over to it. You can debug why this isn't happening via `sudo CBM_DEBUG=1 clr-boot-manager update`. This will output all information on the process, where it may be failing, or that it is working correctly.
|
||||
|
||||
If these two steps fail, you can't revert the installation of the drivers via [History and Rollback](https://solus-project.com/articles/package-management/history-and-rollback/en/)
|
||||
If these two steps fail, you can't revert the installation of the drivers via [History and Rollback](/articles/package-management/history-and-rollback/en/)
|
||||
|
||||
### No Solus boot loader
|
||||
|
||||
If the Solus boot loader is not functioning (this has been known to be broken by the odd update of a certain OS), the boot loader can be recreated via [Boot Rescue](https://solus-project.com/articles/repair-and-recovery/boot-rescue/en/)
|
||||
If the Solus boot loader is not functioning (this has been known to be broken by the odd update of a certain OS), the boot loader can be recreated via [Boot Rescue](/articles/troubleshooting/boot-rescue/en/)
|
||||
|
||||
## Long boot time
|
||||
|
||||
There are a number of factors that can contribute to a long boot time. The boot up messages can be viewed to look for any timeouts by looking at the timestamped journal.
|
||||
|
||||
```
|
||||
``` bash
|
||||
sudo journalctl -b
|
||||
```
|
||||
|
||||
|
|
@ -78,6 +82,4 @@ If information about a device changes (UUID or mount path `/dev/sda`), this can
|
|||
|
||||
`cat /proc/cmdline` will show what parameters the kernel has booted with.
|
||||
|
||||
If the devices don't match up with what's listed in `ls /dev/disk/*/*` then it will cause a 90s timeout while it waits to see if it can be found. To fix this, you will need to remove the reference to the UUID or device path that no longer exists, or correct it to the new UUID label.
|
||||
|
||||
|
||||
If the devices don't match up with what's listed in `ls /dev/disk/*/*` then it will cause a 90s timeout while it waits to see if it can be found. To fix this, you will need to remove the reference to the UUID or device path that no longer exists, or correct it to the new UUID label.
|
||||
|
|
@ -1,8 +1,12 @@
|
|||
+++
|
||||
title = "Installation Issues"
|
||||
lastmod = "2017-09-22T20:13:14+03:00"
|
||||
+++
|
||||
# Installation Issues
|
||||
|
||||
## Can't install in EFI mode
|
||||
|
||||
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](https://solus-project.com/articles/installation/preparing-to-install/en/) and that an EFI boot is selected from the boot options.
|
||||
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.
|
||||
|
||||
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).
|
||||
|
||||
|
|
@ -16,4 +20,4 @@ Legacy installations on Solus use the Grub boot loader on an MBR disk. Only one
|
|||
|
||||
### EFI
|
||||
|
||||
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](https://solus-project.com/articles/troubleshooting/boot-management/en/) which should be able to boot windows (as it's registered with UEFI properly) as well as Solus, but not other systems.
|
||||
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/) which should be able to boot windows (as it's registered with UEFI properly) as well as Solus, but not other systems.
|
||||
|
|
|
|||
Reference in New Issue