|
| 1 | +--- |
| 2 | +title: "Low screen resolution after reboot" |
| 3 | +date: 2026-04-03T19:31:29+02:00 |
| 4 | +author: "Techassi" |
| 5 | +tags: ["linux", "gpu driver", "nvidia", "dkms"] |
| 6 | +description: | |
| 7 | + Sometimes your system decides to be stuck at a super low screen resolution. These tips hopefully |
| 8 | + help you to troubleshoot and fix such issues. |
| 9 | +draft: true |
| 10 | +--- |
| 11 | + |
| 12 | +Sometimes your system decides to be stuck at a super low screen resolution (usually also only on a |
| 13 | +single monitor), for example 1024 x 764. These tricks should help to resolve these kind of issues |
| 14 | +(at least they got me out of a pickle twice already). |
| 15 | + |
| 16 | +## Tips which saved my butt in the past |
| 17 | + |
| 18 | +1. Make sure the correct GPU drivers are installed. For example, the NVIDIA GTX 970 graphics card |
| 19 | + only supports the `nvidia-580xx-dkms` drivers. The latest driver shipped by default on Arch (and |
| 20 | + possibly other distributions) is too new and will result in a low resolution after the system was |
| 21 | + updated and rebooted. Checking `dmesg` after the reboot helps to spot any driver-related |
| 22 | + messages/errors. So check if the currently installed driver supports your graphics card. |
| 23 | +2. Add `nvidia_drm.modeset=1` to the boot options by appending it to the `GRUB_CMDLINE_LINUX_DEFAULT` |
| 24 | + parameter in `/etc/default/grub`. Then proceed to re-generate GRUB's live boot config by executing |
| 25 | + |
| 26 | + ```shell |
| 27 | + grub-mkconfig -o /boot/grub/grub.cfg |
| 28 | + ``` |
| 29 | + |
| 30 | + This one was really hard to spot, because the switch to a low resolution was silent after a |
| 31 | + system update reboot. All utilities I ran basically reported that everything was fine. The list |
| 32 | + below mentions a few useful tools - even though they didn't help me in this case. |
| 33 | +3. Try to install a newer kernel, but that could also potentially backfire. Try other potential |
| 34 | + fixes first, before resorting to this. |
| 35 | + |
| 36 | +## Generally useful tools to know in these situations |
| 37 | + |
| 38 | +- `nvidia-smi` prints out information about the installed graphics card and driver. |
| 39 | +- `inxi -Fzxx` prints out various system-level information. |
| 40 | +- `xrandr` prints out information about monitors, their resolution and refresh rate. |
| 41 | +- `dkms status` prints out the status of kernel modules, which the driver is one of. |
| 42 | +- `nvidia-settings` launches the NVIDIA settings application, but this will display fairly limited |
| 43 | + information when you run into GPU (driver) related issues. |
| 44 | +- The internet and their Linux-focused forums, like the Arch forum and wiki, the Manjaro forum, or |
| 45 | + other forums for various other distributions (like Debian, Ubuntu, CachyOS, EndeavourOS). |
0 commit comments