Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2025-08-02 03:26:38 -04:00
Code Issues Projects Releases Packages Wiki Activity

Move core docs back to core section; clean up titles

Browse source 
Requested by: https://github.com/QubesOS/qubes-doc/pull/823#issuecomment-497306277
This commit is contained in:
Andrew David Wong 2019-05-30 21:02:41 -05:00
parent 643d02da51
commit 994632280a
No known key found for this signature in database
GPG key ID: 8CE137352A019A17
5 changed files with 9 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

25
user/advanced-configuration/newer-hardware-troubleshooting.md Normal file
View file

@ -0,0 +1,25 @@
---
layout: doc
title: Troubleshooting newer hardware
permalink: /doc/newer-hardware-troubleshooting/
---
Troubleshooting newer hardware
==============================
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 Linux kernel 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 LTS 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.
Compare this with the output of `rpm -q kernel`.
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`.