Skip to content

Commit

Permalink
Several updates to known_issues.md
Browse files Browse the repository at this point in the history
  • Loading branch information
manuel-192 committed Jun 9, 2024
1 parent d298c9c commit 2a9f3a7
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions known_issues.md
Original file line number Diff line number Diff line change
@@ -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.

Expand All @@ -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<br>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<br>system update the next boot<br>stops at a blank screen | Typically, on a kernel update the corresponding nvidia driver package should be updated as well.<br>Sometimes that doesn't happen, which can lead to this problem.<br>Remedy1: use the *dkms* version of the Nvidia driver (like `nvidia-dkms`). This is recommended.<br>Remedy2: use apps `UpdateInTerminal`, `eos-welcome` or `eos-update-notifier`<br>for updating the system, because they can detect such a problem and let you decide what to do.<br>Plain `pacman` or `yay` do not detect this.
Wired (ethernet) connection does not<br>work properly | If you have a Realtek `8168` ethernet card, either uninstall the `r8168` package, or reinstall it. Then reboot.<br>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`.<br>2024-Jan: this should no more be needed.
On nvidia system, after<br>system update the next boot<br>stops at a blank screen | Typically, on a kernel update the corresponding nvidia driver package should be updated as well.<br>Sometimes that doesn't happen, which can lead to this problem.<br>Remedy1: use the *dkms* version of the Nvidia driver (like `nvidia-dkms`). This is recommended.<br>Remedy2: use apps `eos-update` for updating the system, because they can detect such a problem and let you decide what to do.<br>Plain `pacman` or `yay` do not detect this.

0 comments on commit 2a9f3a7

Please sign in to comment.