From 2a9f3a7c9d1b25347d9b489e7ac22266868d481d Mon Sep 17 00:00:00 2001 From: manuel Date: Sun, 9 Jun 2024 19:03:16 +0300 Subject: [PATCH] Several updates to known_issues.md --- known_issues.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/known_issues.md b/known_issues.md index d648d0d..c71aff5 100644 --- a/known_issues.md +++ b/known_issues.md @@ -1,6 +1,6 @@ # Known issues -Last update: 2022-Mar-04. +Last update: 2024-Jun-09. Here we will list known issues of the latest EndeavourOS ISO, drivers and apps. @@ -22,6 +22,6 @@ An app behaves unexpectedly | Make sure your system is properly updated (use ter Description of the issue | Possible remedy :---- | :---- -Wired (ethernet) connection does not
work properly | If you have a Realtek `8168` ethernet card, either uninstall the `r8168` package, or reinstall it. Then reboot. -Boot failure with new Nvidia cards (30xx and 40xx) | As a temporary workaround, add kernel parameter `ibt=off`. -On nvidia system, after
system update the next boot
stops at a blank screen | Typically, on a kernel update the corresponding nvidia driver package should be updated as well.
Sometimes that doesn't happen, which can lead to this problem.
Remedy1: use the *dkms* version of the Nvidia driver (like `nvidia-dkms`). This is recommended.
Remedy2: use apps `UpdateInTerminal`, `eos-welcome` or `eos-update-notifier`
for updating the system, because they can detect such a problem and let you decide what to do.
Plain `pacman` or `yay` do not detect this. +Wired (ethernet) connection does not
work properly | If you have a Realtek `8168` ethernet card, either uninstall the `r8168` package, or reinstall it. Then reboot.
Note at 2024-Jun: package `r8168` has been moved to the AUR. +Boot failure with new Nvidia cards (30xx and 40xx) | As a temporary workaround, add kernel parameter `ibt=off`.
2024-Jan: this should no more be needed. +On nvidia system, after
system update the next boot
stops at a blank screen | Typically, on a kernel update the corresponding nvidia driver package should be updated as well.
Sometimes that doesn't happen, which can lead to this problem.
Remedy1: use the *dkms* version of the Nvidia driver (like `nvidia-dkms`). This is recommended.
Remedy2: use apps `eos-update` for updating the system, because they can detect such a problem and let you decide what to do.
Plain `pacman` or `yay` do not detect this.