MX Linux Forum

Posted: **Sat Feb 18, 2023 3:57 pm**

Okay, so you know it's bad when I'm using Windows to report an issue I'm currently facing under MX 21.3 KDE
Here is the hardware in question:

CPU:
AMD Ryzen 5 3600

AMD X570

RAM: 16GB Dual Channel DDR4-SDRAM

GPU:
EVGA NVIDIA GeForce RTX 2070 SUPER

I would list more hardware, but again.... using windows right now, so I can write this.
I cant get MX to even get a command line session to perhaps fix this.

I installed the drivers, reinstalled drivers, uninstalled MX, reinstalled MX, clean install, but MX utterly fails here.
And yes my system was fully up-to-date BTW, no issue there.
And I'm not an idiot as I installed nvidia drivers before using MX's nvidia driver in the past, and it's not like my GPU is unsupported or anything.
Guess back to linux mint on this machine, unfortunate as that's been a pain in my ass as of late, thus why I wanted to see how MX was faring.
Mint may be bugging out on me, but at least I can get my nvidia card to work.

Posted: **Sat Feb 18, 2023 4:37 pm**

You can boot the live USB I wager?

Posted: **Sat Feb 18, 2023 4:45 pm**

We are fixing a problem with the AHS drivers right now...which KDE edition is using.

A temporary AHS workaround would be to first install nvidia-modprobe from bullseye-backports, I believe, then use the Nvidia-installer.

Posted: **Sat Feb 18, 2023 7:07 pm**

Eadwine Rose wrote: Sat Feb 18, 2023 4:37 pm You can boot the live USB I wager?

Yes the live works just fine, no issues.

Stevo wrote: Sat Feb 18, 2023 4:45 pm We are fixing a problem with the AHS drivers right now...which KDE edition is using.

A temporary AHS workaround would be to first install nvidia-modprobe from bullseye-backports, I believe, then use the Nvidia-installer.

Ah that makes sense, I was wondering why it wasn't working as MX worked with this card before.
I will try another reinstall (just in case) and see if I can get my issue resolved.
If not, I will wait out and once the AHS drivers are fixed, try it again.
Keep me informed in any case.
I am willing to keep this topic open until the issue is resolved.

Posted: **Sat Feb 18, 2023 11:52 pm**

Well I tried again and yeah something is certainly wrong.
Since I need my system to keep running, I have reinstalled mint for the time being, but will keep a close eye on this.
Honestly my mint system is okay but I do have minor gripes with it that I hoped MX could solve but since I cant get my GPU to work the way I want it mint it is for now.
I mean I could install the non AHS versions of MX but the AHS does come with its perks.

Posted: **Sun Feb 19, 2023 12:19 am**

Stevo wrote: Sat Feb 18, 2023 4:45 pm We are fixing a problem with the AHS drivers right now...which KDE edition is using.

A temporary AHS workaround would be to first install nvidia-modprobe from bullseye-backports, I believe, then use the Nvidia-installer.

Oh, good to know!

Guess I'm facing the same error.
After installing nvidia-driver system continues using nouveau-driver

Posted: **Sun Feb 19, 2023 12:46 am**

Yeah its a bit of a shame, I mean I would use nouveau, but I like to game under linux now that proton is a thing.

Posted: **Sun Feb 19, 2023 4:22 am**

Hi,

when I noted the update of nvidia-modprobe I had the hope, that the bug was resolved.
So I purged nvidia-driver and reinstalled it, but purging the driver did not remove the built kernel module, so dkms was not triggered on reinstall.

So I manually invoked

Code: Select all

/usr/lib/dkms/dkms_autoinstaller start

with this output:

Code: Select all

~# /usr/lib/dkms/dkms_autoinstaller start
dkms: running auto installation service for kernel 6.1.0-4mx-amd64:Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20221215/source/dkms.conf)
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20221215/source/dkms.conf)
...
'make' all KVER=6.1.0-4mx-amd64.........(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.1.0-4mx-amd64 (x86_64)
Consult /var/lib/dkms/rtl8821cu/5.12.0/build/make.log for more information.

logfile is this:

Code: Select all

$ cat /var/lib/dkms/rtl8821cu/5.12.0/build/make.log 
DKMS make.log for rtl8821cu-5.12.0 for kernel 6.1.0-4mx-amd64 (x86_64)
So 19. Feb 10:08:34 CET 2023
make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/6.1.0-4mx-amd64/build M=/var/lib/dkms/rtl8821cu/5.12.0/build  modules
make[1]: Verzeichnis „/usr/src/linux-headers-6.1.0-4mx-amd64“ wird betreten
...
  CC [M]  /var/lib/dkms/rtl8821cu/5.12.0/build/os_dep/osdep_service.o
/var/lib/dkms/rtl8821cu/5.12.0/build/os_dep/osdep_service.c: In function ‘rtw_random32’:
/var/lib/dkms/rtl8821cu/5.12.0/build/os_dep/osdep_service.c:2918:9: error: implicit declaration of function ‘prandom_u32’; did you mean ‘prandom_u32_max’? [-Werror=implicit-function-declaration]
 2918 |  return prandom_u32();
      |         ^~~~~~~~~~~
      |         prandom_u32_max
cc1: some warnings being treated as errors
make[2]: *** [/usr/src/linux-headers-6.1.0-4mx-common/scripts/Makefile.build:255: /var/lib/dkms/rtl8821cu/5.12.0/build/os_dep/osdep_service.o] Fehler 1
make[1]: *** [/usr/src/linux-headers-6.1.0-4mx-common/Makefile:2030: /var/lib/dkms/rtl8821cu/5.12.0/build] Fehler 2
make[1]: Verzeichnis „/usr/src/linux-headers-6.1.0-4mx-amd64“ wird verlassen
make: *** [Makefile:2498: modules] Fehler 2

Posted: **Sun Feb 19, 2023 6:59 pm**

If you don't have a wireless card with the Realtek 8821CU card, just remove rtl8821cu-dkms.

Actually, save time doing rebuilds by removing any dkms drivers packages you don't use, since they will get rebuilt with all kernel updates, and some of those take some time.

If you do need that driver, try this new one: https://mxrepo.com/mx/repo/pool/ahs-sta ... 21cu-dkms/

Support for that chipset is supposed to be built into Linux kernels starting with 6.2, though.

Posted: **Sun Feb 19, 2023 9:44 pm**

Stevo wrote: Sun Feb 19, 2023 6:59 pm
Support for that chipset is supposed to be built into Linux kernels starting with 6.2, though.

Sweet! There's one less thing to worry about

Honestly this is why I dont use certain distros with my old lappy as it uses that chipset, very nice to see it integrated into the kernel making my linux options become wider.

Posted: **Sun Feb 19, 2023 10:38 pm**

Hi,

Stevo wrote: Sun Feb 19, 2023 6:59 pm If you don't have a wireless card with the Realtek 8821CU card, just remove rtl8821cu-dkms.

The board already has wireless support, but I don't use it. So removed the drivers and dkms building succeeded.

But - how can I tell the kernel to use the nvidia driver?

I tried to blacklist nouveau by adding a file to /etc/modprobe.d with this content:

Code: Select all

blacklist amdgpu
blacklist nouveau
install amdgpu /bin/false
install nouveau /bin/false

but it is silently ignored

The cpu has integrated gpu, which is amdgpu - so xserver starts by loading amdgpu
... but my monitors are connected to nvidia gpu.

Its the first time in my years with linux, that kernel does not use an installed nvidia-driver and I have no idea how to solve it

Posted: **Sun Feb 19, 2023 10:47 pm**

You might try the boot code

Code: Select all

amdgpu.dc=0

which theoretically should keep amdgpu from loading. No guarantee it won't load radeon instead but it's worth a try.

Posted: **Mon Feb 20, 2023 3:58 pm**

Is the machine a desktop or an Optimus laptop with hybrid graphics? That makes a big difference.

Posted: **Mon Feb 20, 2023 10:52 pm**

Hi,

... which theoretically should keep amdgpu from loading.

keeps being a theory

No change at all.

Is the machine a desktop or an Optimus laptop ...

its a desktop machine. QIS of most recent installation:
(3. line shows kernel parameters)

Code: Select all

System:    Kernel: 6.0.0-6mx-amd64 [6.0.12-1~mx21+1] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-6.0.0-6mx-amd64 
           root=UUID=<filter> ro quiet splash amdgpu.dc=0 
           Desktop: KDE Plasma 5.20.5 wm: kwin_x11 vt: 7 dm: SDDM 
           Distro: MX-21.3_KDE_x64 Wildflower January 15  2023 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop Mobo: ASRock model: X670E Steel Legend serial: <filter> 
           UEFI: American Megatrends LLC. v: 1.07 date: 09/23/2022 
CPU:       Info: 6-Core model: AMD Ryzen 5 7600X bits: 64 type: MT MCP arch: Zen 3 family: 19 (25) 
           model-id: 61 (97) stepping: 2 microcode: A601203 cache: L2: 6 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 112595 
           Speed: 400 MHz min/max: 400/5453 MHz boost: enabled Core speeds (MHz): 1: 400 2: 400 
           3: 501 4: 400 5: 699 6: 1057 7: 400 8: 400 9: 451 10: 501 11: 400 12: 400 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: mmio_stale_data status: Not affected 
           Type: retbleed status: Not affected 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW, STIBP: always-on, 
           RSB filling, PBRSB-eIBRS: Not affected 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA TU116 [GeForce GTX 1660 SUPER] vendor: Micro-Star MSI driver: nouveau 
           v: kernel alternate: nvidia_current_drm,nvidia_current bus-ID: 01:00.0 
           chip-ID: 10de:21c4 class-ID: 0300 
           Device-2: AMD driver: amdgpu v: kernel bus-ID: 16:00.0 chip-ID: 1002:164e 
           class-ID: 0300 
           Display: x11 server: X.Org 1.20.14 compositor: kwin_x11 driver: 
           loaded: amdgpu,ati,modesetting unloaded: fbdev,vesa display-ID: :0 screens: 1 
           Screen-1: 0 s-res: 3600x1920 s-dpi: 96 s-size: 951x507mm (37.4x20.0") 
           s-diag: 1078mm (42.4") 
           Monitor-1: DP-1 res: 1200x1920 hz: 60 
           Monitor-2: DP-2 res: 1200x1920 hz: 60 
           Monitor-3: DP-3 res: 1200x1920 hz: 60 
           OpenGL: renderer: NV168 v: 4.3 Mesa 22.0.5 direct render: Yes 
Audio:     Device-1: NVIDIA TU116 High Definition Audio vendor: Micro-Star MSI 
           driver: snd_hda_intel v: kernel bus-ID: 01:00.1 chip-ID: 10de:1aeb class-ID: 0403 
           Device-2: AMD Rembrandt Radeon High Definition Audio driver: snd_hda_intel v: kernel 
           bus-ID: 16:00.1 chip-ID: 1002:1640 class-ID: 0403 
           Device-3: AMD Family 17h/19h HD Audio vendor: ASRock driver: snd_hda_intel v: kernel 
           bus-ID: 16:00.6 chip-ID: 1022:15e3 class-ID: 0403 
           Sound Server-1: ALSA v: k6.0.0-6mx-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASRock 
           driver: r8169 v: kernel port: d000 bus-ID: 05:00.0 chip-ID: 10ec:8168 class-ID: 0200 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter driver: mt7921e 
           v: kernel modules: wl port: d000 bus-ID: 07:00.0 chip-ID: 14c3:0616 class-ID: 0280 
           IF: wlan0 state: down mac: <filter> 
           Device-3: Realtek RTL8125 2.5GbE vendor: ASRock driver: r8169 v: kernel port: c000 
           bus-ID: 08:00.0 chip-ID: 10ec:8125 class-ID: 0200 
           IF: eth1 state: down mac: <filter> 
Bluetooth: Device-1: MediaTek Wireless_Device type: USB driver: btusb v: 0.8 bus-ID: 5-12:2 
           chip-ID: 0e8d:0616 class-ID: e001 serial: <filter> 
           Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2 
           sub-v: 2209 hci-v: 5.2 rev: 820 
           Info: acl-mtu: 1021:6 sco-mtu: 240:8 link-policy: rswitch sniff link-mode: slave accept 
           service-classes: rendering, capturing, object transfer, audio 
Drives:    Local Storage: total: 8.93 TiB used: 1.42 TiB (15.9%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: SKC3000D2048G size: 1.86 TiB 
           block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD 
           serial: <filter> rev: EIFK31.6 temp: 19.9 C scheme: GPT 
           ID-2: /dev/nvme1n1 maj-min: 259:6 vendor: Kingston model: SKC3000D2048G size: 1.86 TiB 
           block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD 
           serial: <filter> rev: EIFK31.6 temp: 19.9 C 
           ID-3: /dev/nvme2n1 maj-min: 259:8 vendor: Kingston model: SKC3000D2048G size: 1.86 TiB 
           block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD 
           serial: <filter> rev: EIFK31.6 temp: 20.9 C scheme: GPT 
           ID-4: /dev/nvme3n1 maj-min: 259:7 vendor: Kingston model: SKC3000D2048G size: 1.86 TiB 
           block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD 
           serial: <filter> rev: EIFK31.6 temp: 23.9 C scheme: GPT 
           ID-5: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB 
           block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> 
           rev: 2B6Q scheme: MBR 
           ID-6: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 840 PRO Series size: 119.24 GiB 
           block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> 
           rev: 5B0Q scheme: MBR 
           ID-7: /dev/sdc maj-min: 8:32 vendor: HP model: SSD S700 500GB size: 465.76 GiB 
           block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> 
           rev: 4A1 scheme: MBR 
Partition: ID-1: / raw-size: 931.17 GiB size: 915.48 GiB (98.31%) used: 8.65 GiB (0.9%) fs: ext4 
           dev: /dev/nvme0n1p5 maj-min: 259:5 
           ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%) used: 25.2 MiB (26.3%) fs: vfat 
           dev: /dev/nvme0n1p1 maj-min: 259:1 
Swap:      Alert: No swap data was found. 
Sensors:   Message: No sensor data found. Is lm-sensors configured? 
Repos:     Packages: note: see --pkg apt: 2351 lib: 1297 flatpak: 0 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bullseye main non-free
           2: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bullseye ahs
Info:      Processes: 321 Uptime: 34m wakeups: 1 Memory: 30.49 GiB used: 1.97 GiB (6.5%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: N/A 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: UEFI

configuration on MX seems to work different.
On debian, even on debian bullseye I could change /etc/X11/xorg.conf and the changes had been recognized and applied.
Sadly that's not true on MX linux.

The only way I didn't try yet is move the nouveau driver out of the way ...

Posted: **Mon Feb 20, 2023 11:04 pm**

Using the MX Nvidia Installer, if it succeeeds in building a driver on your kernel (even a buggy one), will pop up a dialog box informing you that it has blacklisted nouveau on your machine, and the simplest way for this to take effect is a reboot. So I'm wondering how Nvidia drivers were installed on your desktop.

Is there an option to disable the integrated AMD GPU in your desktop's setup "BIOS"?

Posted: **Mon Feb 20, 2023 11:56 pm**

Hi,

Stevo wrote: Mon Feb 20, 2023 11:04 pm Using the MX Nvidia Installer, if it succeeeds in building a driver on your kernel (even a buggy one), will pop up a dialog box informing you that it has blacklisted nouveau on your machine, and the simplest way for this to take effect is a reboot. So I'm wondering how Nvidia drivers were installed on your desktop.

Well, I tried MX NVidia installer several times and it made no difference at all.
Recent installation I installed nvidia-driver by calling "apt install nvidia-driver" - the way I was used from debian systems.
And that installation tells about driver conflicts too, which should be resolved by next reboot.
... obviously something works different at MX

Stevo wrote: Mon Feb 20, 2023 11:04 pm Is there an option to disable the integrated AMD GPU in your desktop's setup "BIOS"?

No. I can only choose the preferred gpu for startup

I tried to move all nouveau-, amd- and radeon-drivers out of their default location with the result, that the system is unable to start x-server. System boots until starting x - and then waits forever. So to me it looks like nvidia-driver installation is incomplete.
Sadly I don't have any log from that failed boot ...

by the way:
I added a file '00-nvidia.conf' to /etc/X11/xorg.conf.d:

Code: Select all

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 1660 Super (MSI)"
EndSection

but that didn't help neither.

If you have any ideas about some additional tests - I'm willing to do any tests.

Posted: **Wed Feb 22, 2023 8:33 am**

Just for feedback purpose:

I got it working (according to this post.

So to summarize the tested steps:

installing the driver by mx-tools or apt makes no difference (nouveau stil active)
blacklisting nouveau - does not work
kernel parameters - don't work

the working steps:

Code: Select all

echo -e 'nvidia\nnvidia-drm\nnvidia-modeset\n\nloop' | sudo tee /etc/modules

Code: Select all

sudo tee /etc/X11/xorg.conf.d/90-nvidia.conf <<!
Section "Device"
     Identifier "Nvidia Card"
     Driver "nvidia"
     VendorName "NVIDIA Corporation"
     Option "RegistryDwords" "EnableBrightnessControl=1
EndSection
!

Code: Select all

sudo update-initramfs -uk all

After these changes original nvidia driver finally takes over control and I could turn on xinerama and add my monitor setup by adding a 99-screen.conf to /etc/X11/xorg.conf.d :

Code: Select all

# nvidia rotated multi-monitor setup
Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    Option         "Xinerama" "1"
EndSection

Section "Module"
    Load           "dbe"
    Load           "extmod"
    Load           "type1"
    Load           "freetype"
    Load           "glx"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device"
    DefaultDepth    24
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "DFP-6"
    Option         "metamodes" "DP-5: nvidia-auto-select +2400+0 {rotation=left}, DP-0: nvidia-auto-select +1200+0 {rotation=left}, DP-2: nvidia-auto-select +0+0 {rotation=left}"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Opposed to the experience using kde-sysconfig xrandr settings I now have a correct oriented desktop spanning all 3 monitors at boot stage (before login).

I'm happy!

Thank you to all

Posted: **Wed Feb 22, 2023 10:00 am**

django013 wrote: Wed Feb 22, 2023 8:33 am Just for feedback purpose:

I got it working (according to this post.

So glad to hear that and thank you for the feedback :)

In fact, you were very close to the solution 2 times. Just an update-initramfs after creating the conf files could've done it.

Posted: **Wed Feb 22, 2023 10:26 pm**

Hi,

Just an update-initramfs after creating the conf files could've done it.

Thought about it, but on searching for the right command syntax I found the wrong pages, so I didn't know how to do it.
MX-tools does not contain such an entry.
So I had to wait until I could read your post :)

Interestingly: MX linux works out of the box - so far the only linux (I tried) that works on my AM5 box.
An USB-stick prepared with bookworm-alpha2 installer is not even recognized as bootable media :(

So you MX guys did a pretty good job! Thank you!

Posted: **Sun Mar 19, 2023 10:51 pm**

Hey I would like to report that as of my recent try of MX linux MX 21.3 that the NVIDIA driver now installs properly! Time to test out some games and see how I fare!

Edit: okay, so far so good, but I will not mark this as solved. Never know if this topic will come in handy for someone else.

Posted: **Mon Mar 20, 2023 12:42 am**

MadmanRB wrote: Sun Mar 19, 2023 10:51 pm Hey I would like to report that as of my recent try of MX linux MX 21.3 that the NVIDIA driver now installs properly! Time to test out some games and see how I fare!

Glad to hear of your success. You're clearly a 'power user' of Linux (unlike myself), so I won't offer any technical advice.

But as a long time MX user, I suggest that you take on-board the following article (which rambles a bit) which also mentions: init as well as: Systemd-shim towards the bottom.

Why MX Linux Uses SysVinit Instead Of Systemd

Over the years on this forum, I have seen folks have 'issues' with downloaded Debian software, and it often revolves around this packaging difference. This is one of the main differences between Ubuntu, Mint, et al, and MX. In this article, there is a linked YouTube video included from the man himself: MX's own Dolphin Oracle, where apparently you can Boot up in Systemd, although what benefits this entails is lost on me!

Personally, I don't understand it AT ALL (!), so I just stick with the MX Package Installer (MXPI), where the Developers have taken lots of Systemd programs and modified them to install under SysVinit protocols.

Folks like you who understand Debian can work-around this, make adjustment to many Systemd programs, play with 'tarballs', etc. and get most everything that they want to run in MX, but you need to have it in the back of your mind when you are out exploring the Internet and downloading stuff to try out! Anything you don't understand, if you search the Forum, you can probably find an answer. If not, start a new thread! Also, if you find something really neat, you can: "make a case for the software" by posting on the Board here for the Dev's to look at and maybe they will do the SysVinit 'thing' and port it into the MXPI for all to use. (Of course, if you know how to 'fix' it yourself, try it and it works, you can upload it to the Dev's, and they can then add it to the MXPI.)

P.S. If your issue here about the Nvidia drivers is still a work-in-progress, fine. But if you think it is now solved, then hit one of the Check-mark Boxes in the top right of a post, and it will label this Thread as "Solved" on the Forum. (Only the original poster can do this!)

Posted: **Mon Mar 20, 2023 10:46 am**

Yeah, well as I said even though my particular issue is solved I am keeping this open just in case someone wants to use it as a reference or if I have more issues down the road.

As for the systemd debate, honestly, if sysinit is causing so many issues for us end users, then maybe the MX developers should drop the BS and use systemd already.
I know the issues that systemd has like memory management and such, but that matters not when doing tasks like installing drivers and such becomes an issue.
And look I understand the hate systemd gets, but still since more and more things are using systemd as a dependency it's becoming a necessary evil.
Personally I think the best compromise is to keep sysinit for the main XFCE non AHS edition and use systemd for the others, I know that would mean issues but if systemd is such a major issue I don't see much choice TBH.

Posted: **Mon Mar 20, 2023 10:53 am**

@Solon Please only use different colors unless absolutely needed, this keeps the forum better readable for all, thanks.

Posted: **Mon Mar 20, 2023 10:53 am**

MadmanRB wrote: Sun Mar 19, 2023 10:51 pm Hey I would like to report that as of my recent try of MX linux MX 21.3 that the NVIDIA driver now installs properly!

Because the Nvidia Driver Installer has been updated to include the above steps (after they worked for different users in different threads). Thank you for the feedback :)

MX Linux Forum

MX 21.3 KDE Nvidia driver installation frustration

MX 21.3 KDE Nvidia driver installation frustration

Re: MX 21.3 KDE Nvidia driver installation frustration

Re: MX 21.3 KDE Nvidia driver installation frustration

Re: MX 21.3 KDE Nvidia driver installation frustration

Re: MX 21.3 KDE Nvidia driver installation frustration

Re: MX 21.3 KDE Nvidia driver installation frustration

Re: MX 21.3 KDE Nvidia driver installation frustration

Re: MX 21.3 KDE Nvidia driver installation frustration

Re: MX 21.3 KDE Nvidia driver installation frustration

Re: MX 21.3 KDE Nvidia driver installation frustration

Re: MX 21.3 KDE Nvidia driver installation frustration

Re: MX 21.3 KDE Nvidia driver installation frustration

Re: MX 21.3 KDE Nvidia driver installation frustration

Re: MX 21.3 KDE Nvidia driver installation frustration

Re: MX 21.3 KDE Nvidia driver installation frustration

Re: MX 21.3 KDE Nvidia driver installation frustration

Re: MX 21.3 KDE Nvidia driver installation frustration

Re: MX 21.3 KDE Nvidia driver installation frustration

Re: MX 21.3 KDE Nvidia driver installation frustration

Re: MX 21.3 KDE Nvidia driver installation frustration

Re: MX 21.3 KDE Nvidia driver installation frustration

Re: MX 21.3 KDE Nvidia driver installation frustration

Re: MX 21.3 KDE Nvidia driver installation frustration

Re: MX 21.3 KDE Nvidia driver installation frustration