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

Fix statement about kernel being from Fedora 25

Browse Source 
While we're at it, make the documentation version-independent.
This commit is contained in:
AJ Jordan 2018-11-12 22:07:05 -05:00
parent 74955e0a0e
commit 0cb3896940
No known key found for this signature in database
GPG Key ID: A4FDB7BE12F63EC3
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
troubleshooting/newer-hardware-troubleshooting.md
View File

@ -7,9 +7,9 @@ permalink: /doc/newer-hardware-troubleshooting/
Troubleshooting newer hardware
==============================
By default, the kernel that is installed in dom0 is the kernel shipped by Fedora 25.
By default, the kernel that is installed in dom0 comes from the `kernel` package, which is an older Linux LTS kernel.
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.
For example, the audio might not work if the sound card is too new for the LTS kernel.
To fix this, you can try the `kernel-latest` package - though be aware that it's less tested!
In dom0:
@ -20,5 +20,6 @@ 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`.
Compare this with the output of `rpm -qi kernel | grep Version`.
If the start of `uname -r` matches one of the versions printed by `rpm`, then you're still using the Linux LTS kernel, and you'll probably need to manually fix your boot settings.
If `uname -r` reports a higher version number, then you've successfully booted with the kernel shipped by `kernel-latest`.