Mageia forum

I have just installed Mageia 8 on a new computer that I built from a box of relatively modern parts. Here is the inxi info.

Code: Select all

[poobah@linux8core ~]$ inxi -b
System:    Host: linux8core Kernel: 5.15.32-desktop-1.mga8 x86_64 bits: 64 Desktop: KDE Plasma 5.20.4
           Distro: Mageia 8 mga8
Machine:   Type: Desktop Mobo: Micro-Star model: MPG Z590 GAMING PLUS (MS-7D07) v: 2.0
           serial: <superuser required> UEFI: American Megatrends LLC. v: A.10 date: 04/09/2021
CPU:       Info: 8-Core 11th Gen Intel Core i7-11700K [MT MCP] speed: 800 MHz min/max: 800/4900 MHz
Graphics:  Device-1: NVIDIA driver: nouveau v: kernel
           Display: x11 server: Mageia X.org 1.20.14 driver: fbdev,v4l resolution: 1920x1080
           OpenGL: renderer: llvmpipe (LLVM 11.0.1 256 bits) v: 4.5 Mesa 21.3.8
Network:   Device-1: Intel Ethernet I225-V driver: igc
           Device-2: Qualcomm Atheros AR9271 802.11n type: USB driver: ath9k_htc
Drives:    Local Storage: total: 1.82 TiB used: 10.73 GiB (0.6%)
Info:      Processes: 328 Uptime: 10m Memory: 31.26 GiB used: 2.07 GiB (6.6%) Shell: Bash inxi: 3.2.01


The graphics card is an Nvidia GeForce RTX 3050. You can see that the system has recognized it only as a generic NVIDIA card. Apparently, the nvidia driver for the card is not supported by the distro.

According to Nvidia, the card requires the driver 510.60.02. The MCC repository shows only the nvidia drivers 390, 460, and 470.

The card is working OK with nouveau, but I am guessing that the generic driver is giving me only generic access to the card functions and not providing full performance from the card. For most of what I use the computer for (emails, web, document editing) the generic performance is adequate. I am not using the system for gaming, but I do use Blender, which hits pretty hard on the Open GL. It would be nice to have access to all that the card has to offer.

So my question is how to install the Nvidia driver 510 and whether or not it would be worth the effort.

Also, does anyone know whether or not Nvidia 510 is scheduled to be in Mageia 9. If that is the case, I might just wait form Mag9 to come out and then switch over.

Thanks
Banjo
(_)=='=~

banjo wrote:According to Nvidia, the card requires the driver 510.60.02. The MCC repository shows only the nvidia drivers 390, 460, and 470.

How did you check? According to the supported products tab for our 470 driver it should be supported:

https://www.nvidia.com/Download/driverR ... 6016/en-us

GeForce RTX 30 Series (Notebooks):
GeForce RTX 3080 Laptop GPU, GeForce RTX 3070 Laptop GPU, GeForce RTX 3060 Laptop GPU, GeForce RTX 3050 Ti Laptop GPU, GeForce RTX 3050 Laptop GPU

GeForce RTX 30 Series:
GeForce RTX 3090, GeForce RTX 3080 Ti, GeForce RTX 3080, GeForce RTX 3070 Ti, GeForce RTX 3070, GeForce RTX 3060 Ti, GeForce RTX 3060

Did you actually try to select the proprietary driver, and to what outcome ?

The 510 driver branch is a new feature branch (like cauldron for Mageia). Mageia provides the stable 470 branch for the RTX 3050. This graphic card is fully supported under Mageia. Go into MCC, set up your graphic card and accept to install the proprietary driver if asked for. I have a RTX 3080 Ti running under Mageia with the 470 branch. No problems here...

Thank you for the quick replies.

I looked up my card on the Nvidia driver page. That is where I found the reference to the 510 driver.

The supported card shown for the 470 driver is the GeForce RTX 3050 Laptop GPU. I do not have the laptop card; I have the desktop card, which is not included in the list for the desktop GeForce RTX 3050. That section ends with the GeForce RTX 3060.

GeForce RTX 30 Series (Notebooks):
GeForce RTX 3080 Laptop GPU, GeForce RTX 3070 Laptop GPU, GeForce RTX 3060 Laptop GPU, GeForce RTX 3050 Ti Laptop GPU, GeForce RTX 3050 Laptop GPU

GeForce RTX 30 Series:
GeForce RTX 3090, GeForce RTX 3080 Ti, GeForce RTX 3080, GeForce RTX 3070 Ti, GeForce RTX 3070, GeForce RTX 3060 Ti, GeForce RTX 3060

I did attempt to install the card in the MCC, but it is not recognized by the system.



When I select Custom, the list of Nvidia cards does not appear to include my card or the 30 series.



So I am at a loss on how to go ahead and install the driver. What am I missing?

In the last screenshot you have to choose "Geforce 635 series and later"

OK. That is not at all obvious.

I will give that a try and see what happens.

Well, you could complain to nvidia how they name their models. But "Geforce 635 series and later" is for the most recent cards.

I chose the "Geforce 635 series and later" and it installed 470. I rebooted and the graphics are totally gone.

When it boots, it displays the Grub menu, which is text based, then it shows the Plymouth screen, and then the screen goes black.

I cannot get it to show anything at all. Ctl-Alt-F<n> does not post a console where I can log in and fix it. All I get is a blank screen.

I am not sure how to rescue this without any graphics at all.

I have a thumb drive with the Mag8 classic installer on it. Can I use that to rescue? I also have a Mag8 live thumb drive.

I booted to single user and used XFdrake to set the driver to nouveau. I rebooted and got a black screen again, but I could get a console.

I ran startx and it errored out with a failure to connect to the x server.

So I ran XFdrake again and set it to use vesa and rebooted. I got a black screen. I ran startx, and it errored out with a failure to connect to the x server.

Maybe I will try uninstalling the nvidia driver and try again. I am grasping at straws.

I will look at the grub settings to see if nokms is set.

I edited /etc/default/grub and removed the nokmsboot flag. Then I ran update-grub and rebooted.

I got the usual blank screen after the Plymouth screen.

I ran startx and got the error "unable to connect to X server: Connection refused"

I checked /etc/X11/xorg.conf and the driver for device1 is set to vesa.

banjo wrote:I booted to single user and used XFdrake to set the driver to nouveau. I rebooted and got a black screen again, but I could get a console.

did you *test* the new driver before you rebooted?

I did not push the test button. I have been told in the past that the test button does not work and will mess things up. So I avoid using it.

I made the change and then rebooted.

With the vesa driver in xorg.conf, the system will now boot to a blank screen that allows me to open a tty anyway. When I log in and run startx it throws an error

xauth: file /root/.serverauth.893 does not exist.

That one rings a bell, but I don't remember if it is relevant or not.

There are a bunch of other errors and then it fails to connect to the X server. I don't have the text of the traceback or any way to copy the log file off the system.

I did confirm that /boot/grub2/grub.cfg no longer contains the nokmsboot flag in the linux parameters.

I was just checking

banjo wrote:I checked /etc/X11/xorg.conf and the driver for device1 is set to vesa.

how many display ports?
are any other display ports active?

I'm not sure I understand the question. I don't know what you mean by "active".

The card has one HDMI output and three DP outputs. I currently have only one monitor, which has a DVI input. I have connected one DP output on the card to the DVI input on the monitor using a passive converter. As it boots, it displays the splash screen on the monitor full screen in living color, so at some level the card works. After it switches over to X, it goes blank.

Maybe now that it is completely hosed I should download the 510 driver and see if I can install it manually. What am I going to do.... break it?

I have no idea how to even begin doing that, so that would take a while.

It is late here in New England, so I am going to bed to sleep on it.

Thanks for all the help.

banjo wrote:The card has one HDMI output and three DP outputs

*active* would mean having graphics data and sync signals available to a cable to be connected to a port.

Hypothesis:
when the login greeter would normally be displayed, the graphics card may be switching signal to the *HDMI* output, but still sending a non-graphics (ie text only) signal to the DP outputs. the monitor is detecting this so does not go to sleep (or complain about no signal)

I have a dual graphics (Intel/NVidia) laptop that behaves in this manor. if I want to use the NVidia graphics I need to connect an HDMI display to it for the GUI desktop to display (it send no display data to the laptop screen). After finishing doing the NVidia stuff (or I want to use the laptop as a laptop, no longer a desktop), I need to reboot and reset the Graphics card driver and choose the Intel only graphics for the internal display.

I see what you mean.

The monitor does have an HDMI input, so I hooked up the HDMI card output to the HDMI monitor input. Then I re-installed the Nvidia drivers and rebooted. After the splash screen, it took me back to the totally unresponsive blank screen. I can no longer open even a tty.

I will reboot in single user and see what else I can try.

Thanks for the ideas. Keep 'em coming.

I rebooted to single user mode, ran XFdrake to set the system back to vesa, changed /etc/default/grub to remove nokmsboot, ran update-grub and rebooted.

I am back to where I was last night. I get a blank screen but with the ability to open a tty.

I might try uninstalling the Nvida driver and doing it all over again to see if the Nvidia driver is absconding with something that the vesa needs.

I tried to run startx again, and it failed again. I copied the /var/log/Xorg.0.log file onto a thumb drive to take a look and see what is going on.

The Xorg.0.log

Code: Select all

[  2616.968]
X.Org X Server 1.20.14
X Protocol Version 11, Revision 0
[  2616.972] Build Operating System: ecosse 5.15.6-server-2.mga8
[  2616.973] Current Operating System: Linux linux8core 5.15.32-desktop-1.mga8 #1 SMP Mon Mar 28 08:31:19 UTC 2022 x86_64
[  2616.973] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.15.32-desktop-1.mga8 root=UUID=6678b5c7-2fb4-4884-b665-9f4d920cdf1d ro splash quiet noiswmd resume=UUID=c8f01bd7-adca-4d51-8dd5-24ba473e34b8 audit=0 vga=788
[  2616.976] Build Date: 16 December 2021  06:38:15PM
[  2616.977] Build ID: x11-server 1.20.14-1.mga8
[  2616.977] Current version of pixman: 0.40.0
[  2616.978]    Before reporting problems, check https://bugs.mageia.org
   to make sure that you have the latest version.
[  2616.978] Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  2616.980] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Apr 21 09:45:33 2022
[  2616.982] (==) Using config file: "/etc/X11/xorg.conf"
[  2616.982] (==) Using config directory: "/etc/X11/xorg.conf.d"
[  2616.982] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  2616.983] (==) ServerLayout "layout"
[  2616.983] (**) |-->Screen "screen1" (0)
[  2616.983] (**) |   |-->Monitor "monitor1"
[  2616.983] (**) |   |-->Device "device1"
[  2616.983] (**) Option "DontZap" "False"
[  2616.983] (**) Option "AllowMouseOpenFail"
[  2616.983] (==) Automatically adding devices
[  2616.983] (==) Automatically enabling devices
[  2616.983] (==) Automatically adding GPU devices
[  2616.983] (==) Automatically binding GPU devices
[  2616.984] (==) Max clients allowed: 256, resource mask: 0x1fffff
[  2616.984] (==) FontPath set to:
   catalogue:/etc/X11/fontpath.d,
   built-ins
[  2616.984] (**) ModulePath set to "/usr/lib64/xorg/extra-modules,/usr/lib64/xorg/modules,/usr/lib/xorg/extra-modules,/usr/lib/xorg/modules"
[  2616.984] (II) The server relies on udev to provide the list of input devices.
   If no devices become available, reconfigure udev or disable AutoAddDevices.
[  2616.984] (II) Loader magic: 0x61fd40
[  2616.984] (II) Module ABI versions:
[  2616.984]    X.Org ANSI C Emulation: 0.4
[  2616.984]    X.Org Video Driver: 24.1
[  2616.984]    X.Org XInput driver : 24.1
[  2616.984]    X.Org Server Extension : 10.0
[  2616.984] (++) using VT number 5

[  2616.985] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31
[  2616.986] (--) PCI:*(1@0:0:0) 10de:2507:1043:887c rev 161, Mem @ 0xa2000000/16777216, 0x90000000/268435456, 0xa0000000/33554432, I/O @ 0x00003000/128, BIOS @ 0x????????/131072
[  2616.986] (II) Open ACPI successful (/var/run/acpid.socket)
[  2616.986] (II) "glx" will be loaded by default.
[  2616.986] (II) LoadModule: "v4l"
[  2616.986] (II) Loading /usr/lib64/xorg/modules/drivers/v4l_drv.so
[  2616.986] (II) Module v4l: vendor="X.Org Foundation"
[  2616.986]    compiled for 1.20.7, module version = 0.1.1
[  2616.986]    ABI class: X.Org Video Driver, version 24.1
[  2616.986] (II) LoadModule: "glx"
[  2616.986] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[  2616.987] (II) Module glx: vendor="X.Org Foundation"
[  2616.987]    compiled for 1.20.14, module version = 1.0.0
[  2616.987]    ABI class: X.Org Server Extension, version 10.0
[  2616.987] (II) LoadModule: "vesa"
[  2616.987] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
[  2616.987] (II) Module vesa: vendor="X.Org Foundation"
[  2616.987]    compiled for 1.20.10, module version = 2.5.0
[  2616.987]    Module class: X.Org Video Driver
[  2616.987]    ABI class: X.Org Video Driver, version 24.1
[  2616.987] (II) v4l driver for Video4Linux overlay mode (V4L2)
[  2616.987] (II) VESA: driver for VESA chipsets: vesa
[  2616.987] (WW) Falling back to old probe method for v4l
[  2616.987] vesa: Refusing to run on UEFI
[  2616.987] (WW) Falling back to old probe method for v4l
[  2616.987] (EE) No devices detected.
[  2616.987] (EE)
Fatal server error:
[  2616.987] (EE) no screens found(EE)
[  2616.987] (EE)
Please consult the Mageia support
    at https://bugs.mageia.org
 for help.
[  2616.987] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[  2616.987] (EE)
[  2616.989] (EE) Server terminated with error (1). Closing log file.


It says, "[ 2616.987] (EE) No devices detected." which may be related to why there is no display.

The /etc/X11/xorg.conf file is showing the vesa driver for device1

Code: Select all

# File generated by XFdrake (rev 262502)

# **********************************************************************
# Refer to the xorg.conf man page for details about the format of
# this file.
# **********************************************************************

Section "ServerFlags"
    Option "DontZap" "False" # disable <Ctrl><Alt><BS> (server abort)
    AllowMouseOpenFail # allows the server to start up even if the mouse does not work
    #DontZoom # disable <Ctrl><Alt><KP_+>/<KP_-> (resolution switching)
EndSection

Section "Module"
    Load "v4l" # Video for Linux
EndSection

Section "Monitor"
    Identifier "monitor1"
    VendorName "Plug'n Play"
   
    # Apple iMac modes
    ModeLine "1024x768"   78.525 1024 1049 1145 1312   768  769  772  800 +hsync +vsync
    ModeLine "800x600"    62.357  800  821  901 1040   600  601  604  632 +hsync +vsync
    ModeLine "640x480"    49.886  640  661  725  832   480  481  484  514 +hsync +vsync
   
    # Apple monitors tend to do 832x624
    ModeLine "832x624"    57      832  876  940 1152   624  625  628  667 -hsync -vsync
   
    # Apple PowerBook G3
    ModeLine "800x600"    100     800  816  824  840   600  616  624  640 -hsync -vsync
   
    # Apple TI Powerbook
    ModeLine "1152x768"   78.741 1152 1173 1269 1440   768  769  772  800 +vsync +vsync
   
    # Pismo Firewire G3
    ModeLine "1024x768"   65     1024 1032 1176 1344   768  771  777  806 -hsync -vsync
   
    # iBook2
    ModeLine "1024x768"   65     1024 1048 1184 1344   768  771  777  806 -hsync -vsync
   
    # 17" Apple Studio Display
    ModeLine "1024x768"   112.62 1024 1076 1248 1420 768 768 780 808 +hsync +vsync
   
    # HiRes Apple Studio Display
    ModeLine "1280x1024"  135    1280 1288 1392 1664  1024 1027 1030 1064
   
    # Another variation
    ModeLine "1280x1024"  134.989 1280 1317 1429 1688  1024 1025 1028 1066 +hsync +vsync
   
    # TV fullscreen mode or DVD fullscreen output.
    # 768x576 @ 79 Hz, 50 kHz hsync
    ModeLine "768x576"     50.00  768  832  846 1000   576  590  595  630
   
    # 768x576 @ 100 Hz, 61.6 kHz hsync
    ModeLine "768x576"     63.07  768  800  960 1024   576  578  590  616
EndSection

Section "Device"
    Identifier "device1"
    BoardName "VESA driver (generic)"
    Driver "vesa"
    Option "DPMS"
EndSection

Section "Screen"
    Identifier "screen1"
    Device "device1"
    Monitor "monitor1"
EndSection

Section "ServerLayout"
    Identifier "layout1"
    Screen "screen1"
EndSection


A progress, or more correctly lack of progress, update. I booted the computer from my Mageia8 Live USB drive. It is odd that the Live system also boots to a blank screen. But, I logged in as root and ran startx and it displayed the graphical interface using the nouveau driver. So I am assuming that the graphics card is still working.

I shut down and restarted from the hard disk, resulting in the usual blank screen and a command line tty. I uninstalled every package that had the word "nvidia" in it.

Code: Select all

nvidia-current-doc-html-470.94-1.mga8.nonfree
nvidia-current-cuda-opencl-470.94-1.mga8.nonfree
lib64nvidia-egl-wayland1-1.1.5-3.mga8
nvidia-current-utils-470.94-1.mga8.nonfree
dkms-nvidia-current-470.94-1.mga8.nonfree
x11-driver-video-nvidia-current-470.94-1.mga8.nonfree


I ran XFdrake and reset the system to use the vesa driver and rebooted.

The result was the same blank screen. Startx resulted in the same error.

Xorg.0.log

Code: Select all

[    70.948]
X.Org X Server 1.20.14
X Protocol Version 11, Revision 0
[    70.948] Build Operating System: ecosse 5.15.6-server-2.mga8
[    70.948] Current Operating System: Linux linux8core 5.15.32-desktop-1.mga8 #1 SMP Mon Mar 28 08:31:19 UTC 2022 x86_64
[    70.948] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.15.32-desktop-1.mga8 root=UUID=6678b5c7-2fb4-4884-b665-9f4d920cdf1d ro splash quiet noiswmd nokmsboot resume=UUID=c8f01bd7-adca-4d51-8dd5-24ba473e34b8 audit=0 vga=788
[    70.948] Build Date: 16 December 2021  06:38:15PM
[    70.948] Build ID: x11-server 1.20.14-1.mga8
[    70.949] Current version of pixman: 0.40.0
[    70.949]    Before reporting problems, check https://bugs.mageia.org
   to make sure that you have the latest version.
[    70.949] Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    70.949] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Apr 22 10:31:57 2022
[    70.949] (==) Using config file: "/etc/X11/xorg.conf"
[    70.949] (==) Using config directory: "/etc/X11/xorg.conf.d"
[    70.949] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    70.949] (==) ServerLayout "layout1"
[    70.949] (**) |-->Screen "screen1" (0)
[    70.949] (**) |   |-->Monitor "monitor1"
[    70.949] (**) |   |-->Device "device1"
[    70.949] (**) Option "DontZap" "False"
[    70.949] (**) Option "AllowMouseOpenFail"
[    70.949] (==) Automatically adding devices
[    70.949] (==) Automatically enabling devices
[    70.949] (==) Automatically adding GPU devices
[    70.949] (==) Automatically binding GPU devices
[    70.949] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    70.949] (==) FontPath set to:
   catalogue:/etc/X11/fontpath.d,
   built-ins
[    70.949] (**) ModulePath set to "/usr/lib64/xorg/extra-modules,/usr/lib64/xorg/modules,/usr/lib/xorg/extra-modules,/usr/lib/xorg/modules"
[    70.949] (II) The server relies on udev to provide the list of input devices.
   If no devices become available, reconfigure udev or disable AutoAddDevices.
[    70.949] (II) Loader magic: 0x61fd40
[    70.949] (II) Module ABI versions:
[    70.949]    X.Org ANSI C Emulation: 0.4
[    70.949]    X.Org Video Driver: 24.1
[    70.949]    X.Org XInput driver : 24.1
[    70.949]    X.Org Server Extension : 10.0
[    70.949] (++) using VT number 5

[    70.950] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31
[    70.950] (--) PCI:*(1@0:0:0) 10de:2507:1043:887c rev 161, Mem @ 0xa2000000/16777216, 0x90000000/268435456, 0xa0000000/33554432, I/O @ 0x00003000/128, BIOS @ 0x????????/131072
[    70.950] (II) Open ACPI successful (/var/run/acpid.socket)
[    70.950] (II) "glx" will be loaded by default.
[    70.950] (II) LoadModule: "v4l"
[    70.950] (II) Loading /usr/lib64/xorg/modules/drivers/v4l_drv.so
[    70.950] (II) Module v4l: vendor="X.Org Foundation"
[    70.950]    compiled for 1.20.7, module version = 0.1.1
[    70.950]    ABI class: X.Org Video Driver, version 24.1
[    70.950] (II) LoadModule: "glx"
[    70.951] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[    70.951] (II) Module glx: vendor="X.Org Foundation"
[    70.951]    compiled for 1.20.14, module version = 1.0.0
[    70.951]    ABI class: X.Org Server Extension, version 10.0
[    70.951] (II) LoadModule: "vesa"
[    70.951] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
[    70.951] (II) Module vesa: vendor="X.Org Foundation"
[    70.951]    compiled for 1.20.10, module version = 2.5.0
[    70.951]    Module class: X.Org Video Driver
[    70.951]    ABI class: X.Org Video Driver, version 24.1
[    70.951] (II) v4l driver for Video4Linux overlay mode (V4L2)
[    70.951] (II) VESA: driver for VESA chipsets: vesa
[    70.951] (WW) Falling back to old probe method for v4l
[    70.951] vesa: Refusing to run on UEFI
[    70.951] (WW) Falling back to old probe method for v4l
[    70.951] (EE) No devices detected.
[    70.951] (EE)
Fatal server error:
[    70.951] (EE) no screens found(EE)
[    70.951] (EE)
Please consult the Mageia support
    at https://bugs.mageia.org
 for help.
[    70.951] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[    70.951] (EE)
[    70.953] (EE) Server terminated with error (1). Closing log file.


I cannot think of anything else to try other than re-installing the OS. I hate to do that since I have some hours invested in setting up the computer, and it is such a Windoze way to fix things. But I cannot think of anything else to try at this point.

If re-installing the OS does not fix it, then I will have a brand new, unusable boat anchor.

Anybody have any ideas before I nuke the system?

FWIW, you should never run startx as root, only as your regular user ( if at all - ususally you would want to switch to what was earlier runlevel 5 by systemctl isolate graphical.target or by (re-)starting your display manager by e.g. systemctl restart sddm.service if you were already at graphical.target )

Apart from that, I recently needed to switch from proprietary nvidia driver to nouveau, and it was as simple as running drakx11, selecting nouveau and rebooting. No manual fiddling needed with grub config or anything else.
Please check if you have any ~/.Xauthority* files in your home directory and remove them, then try again. IF that does not help, please create a log after a fresh boot as root by

Code: Select all

journalctl -ab > /tmp/journal.log

and attach journal.log here later.

All the .Xauthority files in all the /home directories were empty, but I removed them anyway. That made no difference.

I used drakx11 (looks just like XFdrake) to set up the nouveau driver. I had been using vesa since that is what was set up during the installation and was working for a while. The reboot resulted in the same blank screen, but with an interesting Xorg.0.log file.

Code: Select all

[    18.564] (--) Log file renamed from "/var/log/Xorg.pid-3696.log" to "/var/log/Xorg.0.log"
[    18.565]
X.Org X Server 1.20.14
X Protocol Version 11, Revision 0
[    18.565] Build Operating System: ecosse 5.15.6-server-2.mga8
[    18.565] Current Operating System: Linux linux8core 5.15.32-desktop-1.mga8 #1 SMP Mon Mar 28 08:31:19 UTC 2022 x86_64
[    18.565] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.15.32-desktop-1.mga8 root=UUID=6678b5c7-2fb4-4884-b665-9f4d920cdf1d ro splash quiet noiswmd resume=UUID=c8f01bd7-adca-4d51-8dd5-24ba473e34b8 audit=0 vga=788
[    18.565] Build Date: 16 December 2021  06:38:15PM
[    18.565] Build ID: x11-server 1.20.14-1.mga8
[    18.565] Current version of pixman: 0.40.0
[    18.565]    Before reporting problems, check https://bugs.mageia.org
   to make sure that you have the latest version.
[    18.565] Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    18.565] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Apr 22 12:59:18 2022
[    18.565] (==) Using config file: "/etc/X11/xorg.conf"
[    18.565] (==) Using config directory: "/etc/X11/xorg.conf.d"
[    18.565] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    18.565] (==) ServerLayout "layout1"
[    18.565] (**) |-->Screen "screen1" (0)
[    18.565] (**) |   |-->Monitor "monitor1"
[    18.565] (**) |   |-->Device "device1"
[    18.565] (**) Option "DontZap" "False"
[    18.565] (**) Option "AllowMouseOpenFail"
[    18.565] (==) Automatically adding devices
[    18.565] (==) Automatically enabling devices
[    18.565] (==) Automatically adding GPU devices
[    18.565] (==) Automatically binding GPU devices
[    18.565] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    18.565] (==) FontPath set to:
   catalogue:/etc/X11/fontpath.d,
   built-ins
[    18.565] (**) ModulePath set to "/usr/lib64/xorg/extra-modules,/usr/lib64/xorg/modules,/usr/lib/xorg/extra-modules,/usr/lib/xorg/modules"
[    18.565] (II) The server relies on udev to provide the list of input devices.
   If no devices become available, reconfigure udev or disable AutoAddDevices.
[    18.565] (II) Loader magic: 0x61fd40
[    18.565] (II) Module ABI versions:
[    18.565]    X.Org ANSI C Emulation: 0.4
[    18.565]    X.Org Video Driver: 24.1
[    18.565]    X.Org XInput driver : 24.1
[    18.565]    X.Org Server Extension : 10.0
[    18.565] (++) using VT number 1

[    18.565] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[    18.566] (II) xfree86: Adding drm device (/dev/dri/card0)
[    18.566] (--) PCI:*(1@0:0:0) 10de:2507:1043:887c rev 161, Mem @ 0xa2000000/16777216, 0x90000000/268435456, 0xa0000000/33554432, I/O @ 0x00003000/128, BIOS @ 0x????????/131072
[    18.566] (II) Open ACPI successful (/var/run/acpid.socket)
[    18.566] (II) "glx" will be loaded by default.
[    18.566] (II) LoadModule: "v4l"
[    18.566] (II) Loading /usr/lib64/xorg/modules/drivers/v4l_drv.so
[    18.566] (II) Module v4l: vendor="X.Org Foundation"
[    18.566]    compiled for 1.20.7, module version = 0.1.1
[    18.566]    ABI class: X.Org Video Driver, version 24.1
[    18.566] (II) LoadModule: "glx"
[    18.566] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[    18.567] (II) Module glx: vendor="X.Org Foundation"
[    18.567]    compiled for 1.20.14, module version = 1.0.0
[    18.567]    ABI class: X.Org Server Extension, version 10.0
[    18.567] (II) LoadModule: "nouveau"
[    18.567] (II) Loading /usr/lib64/xorg/modules/drivers/nouveau_drv.so
[    18.567] (II) Module nouveau: vendor="X.Org Foundation"
[    18.567]    compiled for 1.20.10, module version = 1.0.17
[    18.567]    Module class: X.Org Video Driver
[    18.567]    ABI class: X.Org Video Driver, version 24.1
[    18.567] (II) v4l driver for Video4Linux overlay mode (V4L2)
[    18.567] (II) NOUVEAU driver
[    18.567] (II) NOUVEAU driver for NVIDIA chipset families :
[    18.567]    RIVA TNT            (NV04)
[    18.567]    RIVA TNT2           (NV05)
[    18.567]    GeForce 256         (NV10)
[    18.567]    GeForce 2           (NV11, NV15)
[    18.567]    GeForce 4MX         (NV17, NV18)
[    18.567]    GeForce 3           (NV20)
[    18.567]    GeForce 4Ti         (NV25, NV28)
[    18.567]    GeForce FX          (NV3x)
[    18.567]    GeForce 6           (NV4x)
[    18.567]    GeForce 7           (G7x)
[    18.567]    GeForce 8           (G8x)
[    18.567]    GeForce 9           (G9x)
[    18.567]    GeForce GTX 2xx/3xx (GT2xx)
[    18.567]    GeForce GTX 4xx/5xx (GFxxx)
[    18.567]    GeForce GTX 6xx/7xx (GKxxx)
[    18.567]    GeForce GTX 9xx     (GMxxx)
[    18.567]    GeForce GTX 10xx    (GPxxx)
[    18.567] (WW) Falling back to old probe method for v4l
[    18.567] (II) [drm] nouveau interface version: 1.3.1
[    18.567] (EE) Unknown chipset: NV176
[    18.567] (II) [drm] nouveau interface version: 1.3.1
[    18.567] (EE) Unknown chipset: NV176
[    18.567] (WW) Falling back to old probe method for v4l
[    18.567] (II) [drm] nouveau interface version: 1.3.1
[    18.567] (EE) Unknown chipset: NV176
[    18.567] (II) [drm] nouveau interface version: 1.3.1
[    18.567] (EE) Unknown chipset: NV176
[    18.567] (EE) No devices detected.
[    18.567] (EE)
Fatal server error:
[    18.567] (EE) no screens found(EE)
[    18.567] (EE)
Please consult the Mageia support
    at https://bugs.mageia.org
 for help.
[    18.567] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[    18.567] (EE)
[    18.572] (EE) Server terminated with error (1). Closing log file.


Apparently, nouveau does not recognize chipset: NV176, and it failed out.

I am starting to believe that I have an oddball unsupported card somehow. It isn't supported by the Nvidia driver, and it isn't supported by nouveau. It was working for a while with vesa, but now that errors out as well. Ii is not a no-name card. The product is ASUS Dual GeForce RTX 3050 8GB GDDR6 PCI Express 4.0 Video Card DUAL-RTX3050-O8G

Yep you were right. The desktop RTX 3050 is only supported from 510 driver upwards. We have the 510 drivers in cauldron. You could open a bugreport and request to backport the 510 driver from cauldron to MGA8. https://madb.mageia.org/package/show/name/x11-driver-video-nvidia-current/release/cauldron/arch/x86_64

Or you could try to install the driver manually from the Nvidia site:
http://us.download.nvidia.com/XFree86/Linux-x86_64/510.47.03/README/index.html
(The last time i did a manual Nvidia driver install was at Mandrake times...so i don't know if it still works. But the mentioned installation instruction is way better nowadays...)

I wondered why the 3050 was "in stock" at Newegg, while the upper level cards were always "out of stock".

Thanks for the info on Cauldron. I don't really need the new computer right away, so I might take a deep dive into installing the 510 manually. I went to the Nvidia site, and they recommend registering the driver with DKMS so that it will build when the kernel updates. I am not sure how to do that, so I will need to go do some research. But what the heck. What am I going to do ...... break it?

I will look into filing the backport request.

Stay tuned. This could get interesting.

banjo wrote: and they recommend registering the driver with DKMS so that it will build when the kernel updates. I am not sure how to do that,

You only need to install the package "dkms". The Nvidia installer will search for it and when it's found, it will register the module itself.