From 74955e0a0ee0d62119df6be1d85a93fe0d484f5c Mon Sep 17 00:00:00 2001 From: AJ Jordan Date: Mon, 12 Nov 2018 13:17:23 -0500 Subject: [PATCH 1/4] Document troubleshooting with `kernel-next` --- doc.md | 1 + .../newer-hardware-troubleshooting.md | 24 +++++++++++++++++++ 2 files changed, 25 insertions(+) create mode 100644 troubleshooting/newer-hardware-troubleshooting.md diff --git a/doc.md b/doc.md index dec7b8ac..d8673876 100644 --- a/doc.md +++ b/doc.md @@ -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/) diff --git a/troubleshooting/newer-hardware-troubleshooting.md b/troubleshooting/newer-hardware-troubleshooting.md new file mode 100644 index 00000000..b4fba217 --- /dev/null +++ b/troubleshooting/newer-hardware-troubleshooting.md @@ -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`. From 0cb389694062a8f53aa0899f749d6d32bbdba568 Mon Sep 17 00:00:00 2001 From: AJ Jordan Date: Mon, 12 Nov 2018 22:07:05 -0500 Subject: [PATCH 2/4] Fix statement about `kernel` being from Fedora 25 While we're at it, make the documentation version-independent. --- troubleshooting/newer-hardware-troubleshooting.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/troubleshooting/newer-hardware-troubleshooting.md b/troubleshooting/newer-hardware-troubleshooting.md index b4fba217..7ef65925 100644 --- a/troubleshooting/newer-hardware-troubleshooting.md +++ b/troubleshooting/newer-hardware-troubleshooting.md @@ -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`. From c4573610f7e0a109f5cc830164b96870c399d176 Mon Sep 17 00:00:00 2001 From: AJ Jordan Date: Sun, 18 Nov 2018 19:23:07 -0500 Subject: [PATCH 3/4] Clarify who backports LTS kernel fixes --- troubleshooting/newer-hardware-troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/troubleshooting/newer-hardware-troubleshooting.md b/troubleshooting/newer-hardware-troubleshooting.md index 7ef65925..21361b3c 100644 --- a/troubleshooting/newer-hardware-troubleshooting.md +++ b/troubleshooting/newer-hardware-troubleshooting.md @@ -8,7 +8,7 @@ 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 Qubes OS developers backport fixes to this kernel, but for some newer hardware, you may run into issues. +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! From 231cd82b1b98814f8cb857730d04910154559a8d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marek=20Marczykowski-G=C3=B3recki?= Date: Sun, 18 Nov 2018 19:25:21 -0500 Subject: [PATCH 4/4] Simplify kernel version rpm command Co-Authored-By: strugee --- troubleshooting/newer-hardware-troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/troubleshooting/newer-hardware-troubleshooting.md b/troubleshooting/newer-hardware-troubleshooting.md index 21361b3c..23bd35d4 100644 --- a/troubleshooting/newer-hardware-troubleshooting.md +++ b/troubleshooting/newer-hardware-troubleshooting.md @@ -20,6 +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. -Compare this with the output of `rpm -qi kernel | grep Version`. +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`.