SOLVED nvidia errors using X11 after uprading kernel & nvidia driver

timminybo · 2025-12-23 19:08:47

I have combined both services into a single service file and changed the type to oneshot without restart as follows:

# /etc/systemd/system/monitor-settings-at-boot.service
# bb 2025.12.22
# https://bbs.archlinux.org/viewtopic.php?id=278369&p=2
# https://bbs.archlinux.org/viewtopic.php?id=311099

[Unit]
Description=console monitor and font settings at boot
After=multi-user.target

[Service]
Type=oneshot
User=root
ExecStart=fbset -xres 1920 -yres 1080
ExecStart=setfont ter-u32n
Restart=no

vvv2542 · 2025-12-23 20:07:18

timminybo wrote:

I have combined both services into a single service file and changed the type to oneshot without restart

Another way to do this: create file /etc/modprobe.d/monitor-settings-at-boot.conf:

install nvidia_drm /sbin/modprobe --ignore-install nvidia_drm; /bin/fbset -xres 1920 -yres 1080; /bin/setfont ter-u32n

fbset and setfont will run just after nvidia_drm module which changes resolution and font.

I use Fedora 43 and there is no fbset. Can't find alternative way to change VT resolution after nvidia_drm.

timminybo · 2025-12-23 21:37:23

vvv2542,

That's interesting.

Maybe you can install fbset from source from github or maybe find a COPR for it or an .rpm somewhere.

A quick search found this: https://fedora.pkgs.org/42/rpm-sphere-x … 4.rpm.html

It is for Fedora 42 but might work. There are instructions on the page for installing it. Use at your own risk just like the AUR.

vvv2542 · 2025-12-23 21:57:34

Thanks. I prefer to leave nvidia_drm.fbdev=0 and add BusID in xorg.conf as described in #20.

seth · 2025-12-23 22:16:18

Does it help if you add "initcall_blacklist=simpledrm_platform_driver_init" to the https://wiki.archlinux.org/title/Kernel_parameters ?

vvv2542 · 2025-12-23 23:49:11

seth wrote:

Does it help if you add "initcall_blacklist=simpledrm_platform_driver_init" to the https://wiki.archlinux.org/title/Kernel_parameters ?

Partially. The font stops changing to default 16x8. But the screen resolution changes as well as without this parameter.

timminybo · Yesterday 00:26:28

I tried it temporarily as well (I use systemd-boot) after disabling the systemd service. Immediate result was a black screen. Entered my encrypted volume password anyway. Login screen (on both monitors) look normal. As soon as I log in, back to black border around larger (primary) monitor but text size is correct.

seth · Yesterday 09:14:37

black border around larger (primary) monitor but text size is correct.

If you've outputs w/ different resolutions and one cannot/does not scale up lower resolution feeds (ie. how the monitor handles this, they typically have OSD features for that), doesn't "fbset -xres 1920 -yres 1080" just end up cutting off the lower and right section of the smaller monitor??

timminybo · Yesterday 20:16:44

Yes it does. For the console.

My wording was imprecise. I should have said "black border along bottom and right side of larger (primary) monitor."

When I set the resolution with fbset, the cutting off only occurs on the console and for the smaller monitor. I don't really care because I spend little time in a console and don't need two consoles displaying the same information. I often don't even have the secondary monitor turned on at boot. I just look at the boot messages, login, and then startx to get into the X11 environment where I then use the i3 window manager. Once X11 starts, I don't have the black borders on the larger higher resolution (1920x1080) primary monitor or the cutting off on the physcially smaller monitor (1680x1050).

My limited understanding (I could cetainly be wrong) is that the framebuffer affects the console graphics, that is, prior to the X11 starting. I have assumed that X11 and the graphics card driver take over and control monitor resolution and positioning, etc. once X11 starts (after executing startx).

Auto-login might be another way to avoid the console as much as possible. I haven't played with that yet. I also haven't tried vvv2542's suggestion.

Seth, you solved the main problem back on post #11. I mentioned the console oddities to be complete, because they weren't present before the driver/kernel change, and in case anyone else had them. There seem to be two or three ways to work around them. I will happily try out any suggestions you have and post the results. But I don't want to take your attention from more important matters. From my perusal of the Arch forums, you are a very busy individual.

Thank you and all the other Arch folks who tirelessly answer our questions and create, package, and maintain all this software. Happy Holidays!

Arch Linux

#26 2025-12-23 19:08:47

Re: SOLVED nvidia errors using X11 after uprading kernel & nvidia driver

#27 2025-12-23 20:07:18

Re: SOLVED nvidia errors using X11 after uprading kernel & nvidia driver

#28 2025-12-23 21:37:23

Re: SOLVED nvidia errors using X11 after uprading kernel & nvidia driver

#29 2025-12-23 21:57:34

Re: SOLVED nvidia errors using X11 after uprading kernel & nvidia driver

#30 2025-12-23 22:16:18

Re: SOLVED nvidia errors using X11 after uprading kernel & nvidia driver

#31 2025-12-23 23:49:11

Re: SOLVED nvidia errors using X11 after uprading kernel & nvidia driver

#32 Yesterday 00:26:28

Re: SOLVED nvidia errors using X11 after uprading kernel & nvidia driver

#33 Yesterday 09:14:37

Re: SOLVED nvidia errors using X11 after uprading kernel & nvidia driver

#34 Yesterday 20:16:44

Re: SOLVED nvidia errors using X11 after uprading kernel & nvidia driver

Board footer