Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2024-12-26 07:49:34 -05:00
Code Issues Packages Projects Releases Wiki Activity

Document troubleshooting with kernel-next

Browse Source
This commit is contained in:
AJ Jordan 2018-11-12 13:17:23 -05:00
parent 0907ce5f4d
commit 74955e0a0e
No known key found for this signature in database
GPG Key ID: A4FDB7BE12F63EC3
2 changed files with 25 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
doc.md
View File

@ -163,6 +163,7 @@ Customization Guides
Troubleshooting
---------------
* [Home directory is out of disk space error](/doc/out-of-memory/)
* [Newer hardware doesn't work](/doc/newer-hardware-troubleshooting/)
* [Installing on system with new AMD GPU (missing firmware problem)](https://groups.google.com/group/qubes-devel/browse_thread/thread/e27a57b0eda62f76)
* [How to install an Nvidia driver in dom0](/doc/install-nvidia-driver/)
* [Nvidia troubleshooting guide](/doc/nvidia-troubleshooting/)

24
troubleshooting/newer-hardware-troubleshooting.md Normal file
View File

@ -0,0 +1,24 @@
---
layout: doc
title: Troubleshooting newer hardware
permalink: /doc/newer-hardware-troubleshooting/
---
Troubleshooting newer hardware
==============================
By default, the kernel that is installed in dom0 is the kernel shipped by Fedora 25.
For most cases this works fine since the Qubes OS developers backport fixes to this kernel, but for some newer hardware, you may run into issues.
For example, the audio might not work if the sound card is too new for the Fedora 25 kernel.
To fix this, you can try the `kernel-latest` package - though be aware that it's less tested!
In dom0:
~~~
sudo qubes-dom0-update kernel-latest
~~~
Reboot when it's done installing.
You can double-check that the boot used the newer kernel with `uname -r`, which prints the version of the currently-running kernel.
If it says `4.14` at the beginning, then you're still using the Fedora 25 kernel, and you'll probably need to manually fix your boot settings.
If it reports a higher version number, then you've successfully booted with the kernel shipped by `kernel-latest`.