TW Feature Request: X11 Fallback Driver
This isn't the right place but it would be really nice if X11 could use a secondary driver if the primary driver fails. This would help new users when the kernel is updated and the binary NV driver needs to be rebuilt.
On Tuesday, 11 April 2023 6:50:54 PM ACST Reid Sutherland wrote:
This isn't the right place but it would be really nice if X11 could use a secondary driver if the primary driver fails. This would help new users when the kernel is updated and the binary NV driver needs to be rebuilt.
Have you tried using dkms? That will automatically take care of building the kernel module for you when you boot the new kernel and the module does not exist (but you have to have dkms installed and have installed the nvidia driver from the nvidia installer, not the openSUSE packages). I've been doing it that way for years. You can also tell dkms to build the module for the new kernel prior to rebooting. If you include the nvidia fb and drm modules in initrd, you also need to run dracut to add the newly build modules prior to rebooting. Cheers, Rodney. -- ================================================================================================================== Rodney Baker rodney.baker@iinet.net.au ==================================================================================================================
On 4/11/23 05:56, Rodney Baker wrote:
On Tuesday, 11 April 2023 6:50:54 PM ACST Reid Sutherland wrote:
This isn't the right place but it would be really nice if X11 could use a secondary driver if the primary driver fails. This would help new users when the kernel is updated and the binary NV driver needs to be rebuilt.
Have you tried using dkms? That will automatically take care of building the kernel module for you when you boot the new kernel and the module does not exist (but you have to have dkms installed and have installed the nvidia driver from the nvidia installer, not the openSUSE packages).
I've been doing it that way for years. You can also tell dkms to build the module for the new kernel prior to rebooting. If you include the nvidia fb and drm modules in initrd, you also need to run dracut to add the newly build modules prior to rebooting.
That's a good idea, I've been just running ./NV.. -K and restarting sddm. I was thinking on behalf of new users, having a fallback driver is ideal compared hitting a text-only login prompt or trying to figure out what you mentioned.
On 4/11/23 09:06, Andrei Borzenkov wrote:
On Tue, Apr 11, 2023 at 3:59 PM Reid Sutherland <reid@thirddimension.net> wrote:
I was thinking on behalf of new users, having a fallback driver is ideal
That is exactly what Xorg does - it tries different drivers in (built-in) order of preference and uses the first one that works.
Thanks, will test it out for next time.
Am 11.04.23 um 15:14 schrieb Reid Sutherland:
On 4/11/23 09:06, Andrei Borzenkov wrote:
On Tue, Apr 11, 2023 at 3:59 PM Reid Sutherland <reid@thirddimension.net> wrote:
I was thinking on behalf of new users, having a fallback driver is ideal
That is exactly what Xorg does - it tries different drivers in (built-in) order of preference and uses the first one that works.
with the open-source drivers shipped with opensuse (or maybe other distros). if you use proprietary nvidia driver this will not work in most cases. simoN
Thanks, will test it out for next time.
-- www.becherer.de
Reid Sutherland composed on 2023-04-11 09:14 (UTC-0400):
Andrei Borzenkov wrote:
Reid Sutherland wrote:
I was thinking on behalf of new users, having a fallback driver is ideal
That is exactly what Xorg does - it tries different drivers in (built-in) order of preference and uses the first one that works.
Thanks, will test it out for next time.
When NVidia's proprietary driver is installed, an environment is created such that either: 1-no FOSS driver will load, resulting in no running Xorg (most likely); or 2-a crude, low priority driver will load, usually resulting in no better than 800x600 or 1024x768 resolution. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 4/11/23 10:06, Felix Miata wrote:
When NVidia's proprietary driver is installed, an environment is created such that either: 1-no FOSS driver will load, resulting in no running Xorg (most likely); or 2-a crude, low priority driver will load, usually resulting in no better than 800x600 or 1024x768 resolution.
Crude VESA driver is better than nothing. If the user is unprepared, they're basically hard down unless they have another device.
On 2023-04-11 16:11, Reid Sutherland wrote:
On 4/11/23 10:06, Felix Miata wrote:
When NVidia's proprietary driver is installed, an environment is created such that either: 1-no FOSS driver will load, resulting in no running Xorg (most likely); or 2-a crude, low priority driver will load, usually resulting in no better than 800x600 or 1024x768 resolution.
Crude VESA driver is better than nothing. If the user is unprepared, they're basically hard down unless they have another device.
With a low resolution display you are also stuck. You can not browse internet to ask questions, it is barely usable. Several tools you need are bigger than the display and you can not press the buttons at the bottom. Unless somebody designs an alternate X system that ignores all configuration systems and proprietary drivers, which tries to start on failure of X. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 4/14/23 05:32, Carlos E. R. wrote:
On 2023-04-11 16:11, Reid Sutherland wrote:
On 4/11/23 10:06, Felix Miata wrote:
When NVidia's proprietary driver is installed, an environment is created such that either: 1-no FOSS driver will load, resulting in no running Xorg (most likely); or 2-a crude, low priority driver will load, usually resulting in no better than 800x600 or 1024x768 resolution.
Crude VESA driver is better than nothing. If the user is unprepared, they're basically hard down unless they have another device.
With a low resolution display you are also stuck. You can not browse internet to ask questions, it is barely usable. Several tools you need are bigger than the display and you can not press the buttons at the bottom.
Unless somebody designs an alternate X system that ignores all configuration systems and proprietary drivers, which tries to start on failure of X.
Nothing wrong with 1024, Windows does the same thing but they have better drivers. No idea how you think a text prompt is better for someone who has no knowledge of what to enter into it. The issue is the kernel driver isn't loaded at boot, so X should be able to move on to the next driver without issue. Can safely put this issue to rest unless someone with direct knowledge wants to help correct it (Nvidia).
On 2023-04-14 11:36, Reid Sutherland wrote:
On 4/14/23 05:32, Carlos E. R. wrote:
On 2023-04-11 16:11, Reid Sutherland wrote:
On 4/11/23 10:06, Felix Miata wrote:
When NVidia's proprietary driver is installed, an environment is created such that either: 1-no FOSS driver will load, resulting in no running Xorg (most likely); or 2-a crude, low priority driver will load, usually resulting in no better than 800x600 or 1024x768 resolution.
Crude VESA driver is better than nothing. If the user is unprepared, they're basically hard down unless they have another device.
With a low resolution display you are also stuck. You can not browse internet to ask questions, it is barely usable. Several tools you need are bigger than the display and you can not press the buttons at the bottom.
Unless somebody designs an alternate X system that ignores all configuration systems and proprietary drivers, which tries to start on failure of X.
Nothing wrong with 1024, Windows does the same thing but they have better drivers. No idea how you think a text prompt is better for someone who has no knowledge of what to enter into it.
We are not saying it is better. Would you prefer a cute empty blue screen instead? I guess it is better than that.
The issue is the kernel driver isn't loaded at boot, so X should be able to move on to the next driver without issue.
It does move to the next driver.
Can safely put this issue to rest unless someone with direct knowledge wants to help correct it (Nvidia).
If the nvidia proprietary driver is enabled, they do it in such a way that X11 can not try another driver. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
participants (6)
-
Andrei Borzenkov -
Carlos E. R. -
Felix Miata -
Reid Sutherland -
Rodney Baker -
Simon Becherer