MX-23 beta 2 feedback thread

[siamhie]

maybe but its also possible its just loading very very fast on that machine. I see the animation on my core i7, but its very fast.

@dolphin_oracle It is fast but I was able to see both lines create the X portion of the logo. I saw it during beta 1 and initially beta 2.

I'll boot to Sys-V to see if there is any difference. (possible I have a service taking it's time to load)

the revised theme is faster than the original. not saying that its so fast you aren't seeing it, but it is much quicker.

@dolphin_oracle I just see a static image (probably loaded by the time the image appears on my screen) when booting to either Sys V or SystemD. Shame because I really liked that animation at boot.

[Senpai]

UPDATE
Also errors with RTL8812AU (search github for updated drivers of your device - mine is RTL8821CE - for kernel 6x and read the docs)

Code: Select all

Loading new rtl8821cu-5.12.0 DKMS files...
/usr/sbin/dkms: line 2497: echo: write error: Broken pipe

were removed:

although because of a warning from using build and installed different modules after retries I ended up using:

Code: Select all

~$  dkms status
~$  rtl8812au/5.13.6, 6.1.0-9-amd64, x86_64: (different modules warning here!!!)
~$ sudo dkms remove rtl8812au/5.13.6 -k <kernel from dkms status here>
~$ sudo dkms install rtl8812au/5.13.6 -k <kernel from dkms status here>
~$  dkms status
~$  rtl8812au/5.13.6, 6.1.0-9-amd64, x86_64: installed

There maybe typos here... I'm using also a dozen kernels for testing future nvidia modules from v5 to v6 also ahs...
Hope it helps!

Hi:
This solution has helped me to uninstall the 8812au module that in my PC with MX21.3 was giving me kernel panic in Kernels 6.1 and 5.19, I have uninstalled it and both are booting... as it is a PC without wiffi, it seems that it does not need it... although I do not know the reason why in the kernel 6.0 of the same machine it does not give error...
Thanks

[gRegNfo]

UPDATE
Also errors with RTL8812AU (search github for updated drivers of your device - mine is RTL8821CE - for kernel 6x and read the docs)

Code: Select all

Loading new rtl8821cu-5.12.0 DKMS files...
/usr/sbin/dkms: line 2497: echo: write error: Broken pipe

were removed:

although because of a warning from using build and installed different modules after retries I ended up using:

Code: Select all

~$  dkms status
~$  rtl8812au/5.13.6, 6.1.0-9-amd64, x86_64: (different modules warning here!!!)
~$ sudo dkms remove rtl8812au/5.13.6 -k <kernel from dkms status here>
~$ sudo dkms install rtl8812au/5.13.6 -k <kernel from dkms status here>
~$  dkms status
~$  rtl8812au/5.13.6, 6.1.0-9-amd64, x86_64: installed

There maybe typos here... I'm using also a dozen kernels for testing future nvidia modules from v5 to v6 also ahs...
Hope it helps!

Hi:
This solution has helped me to uninstall the 8812au module that in my PC with MX21.3 was giving me kernel panic in Kernels 6.1 and 5.19, I have uninstalled it and both are booting... as it is a PC without wiffi, it seems that it does not need it... although I do not know the reason why in the kernel 6.0 of the same machine it does not give error...
Thanks

Hi Senpai, really glad it was useful...
Though that driver is also used for Bluetooth connectivity and I can't tell if anything else.
But go on like that and check if everything is working as the beta is being trialed.

[dolphin_oracle]

@dolphin_oracle It is fast but I was able to see both lines create the X portion of the logo. I saw it during beta 1 and initially beta 2.

I'll boot to Sys-V to see if there is any difference. (possible I have a service taking it's time to load)

the revised theme is faster than the original. not saying that its so fast you aren't seeing it, but it is much quicker.

@dolphin_oracle I just see a static image (probably loaded by the time the image appears on my screen) when booting to either Sys V or SystemD. Shame because I really liked that animation at boot.

you could try updating the initramfs again. it should have been done automatically.

Code: Select all

sudo update-initramfs -u -k all

[Danathar]

I believe I've discovered a bug in the live-USB storage creation process. I created a persistent, fully-featured, encrypted drive using the "Clone Live Running System" option in the USB Creator while running off a non-persistent beta USB stick. However, the resulting USB stick did not have the live-usb-storage folder or the file system for the rest of the stick.

As an experiment, I created a 21.3 stick and performed the same process. This time, I made the resulting USB stick from an image I downloaded (beta), and the resulting USB image did have the live-usb-storage folder.

[gRegNfo]

I just ran

Code: Select all

ddm-mx nvidia-tesla-470-driver

yesterday for my laptop MX23b2.

I don't know if I had to make something by the end of it... But booting, it completely ruined all my Kernels.
None would boot up! It broke the wlan first and next usb3... and stalled there probing a lot of Genius inputs until I Ctrl-Alt-Del and re-installed my Snapshot.

Yes it really works now like a charm, doesn't stall at 11% and Ventoy already fixed the code!

By now I use Time-Shift too and will report next time I ruin my system

I ended up after the snapshot, installing the driver and modules (Tesla 470) by hand on Synaptic... It works when rebooted right away.
After I did DKMS and UPDATE-INITRAMFS to specific kernels, and it works! None broken.

I even got the NVIDIA X Server settings module working at last!!!! It displays all info! I'm quite amazed!

I'll try in the future to run specific 3D rendered stuff to check it out.
Not sure yet how to work the changing of GPU but I'll get it (bumblebee is broken, or deprecated? We'll see)

Primus Optimus and Vulkan drivers are still buzzwords to check too. It's too much for now!

[dolphin_oracle]

I just ran

Code: Select all

ddm-mx nvidia-tesla-470-driver

yesterday for my laptop MX23b2.

I don't know if I had to make something by the end of it... But booting, it completely ruined all my Kernels.
None would boot up! It broke the wlan first and next usb3... and stalled there probing a lot of Genius inputs until I Ctrl-Alt-Del and re-installed my Snapshot.

Yes it really works now like a charm, doesn't stall at 11% and Ventoy already fixed the code!

By now I use Time-Shift too and will report next time I ruin my system

I ended up after the snapshot, installing the driver and modules (Tesla 470) by hand on Synaptic... It works when rebooted right away.
After I did DKMS and UPDATE-INITRAMFS to specific kernels, and it works! None broken.

I even got the NVIDIA X Server settings module working at last!!!! It displays all info! I'm quite amazed!

I'll try in the future to run specific 3D rendered stuff to check it out.
Not sure yet how to work the changing of GPU but I'll get it (bumblebee is broken, or deprecated? We'll see)

Primus Optimus and Vulkan drivers are still buzzwords to check too. It's too much for now!

running that "command" as written wouldn't do anything. please update to indicate what you actually ran, or provide the /var/log/ddm.log file.

[gRegNfo]

I just ran

Code: Select all

ddm-mx nvidia-tesla-470-driver

yesterday for my laptop MX23b2.

I don't know if I had to make something by the end of it... But booting, it completely ruined all my Kernels.
None would boot up! It broke the wlan first and next usb3... and stalled there probing a lot of Genius inputs until I Ctrl-Alt-Del and re-installed my Snapshot.

Yes it really works now like a charm, doesn't stall at 11% and Ventoy already fixed the code!

By now I use Time-Shift too and will report next time I ruin my system

I ended up after the snapshot, installing the driver and modules (Tesla 470) by hand on Synaptic... It works when rebooted right away.
After I did DKMS and UPDATE-INITRAMFS to specific kernels, and it works! None broken.

I even got the NVIDIA X Server settings module working at last!!!! It displays all info! I'm quite amazed!

I'll try in the future to run specific 3D rendered stuff to check it out.
Not sure yet how to work the changing of GPU but I'll get it (bumblebee is broken, or deprecated? We'll see)

Primus Optimus and Vulkan drivers are still buzzwords to check too. It's too much for now!

running that "command" as written wouldn't do anything. please update to indicate what you actually ran, or provide the /var/log/ddm.log file.

I Was very distracted sorry, you're very right... it was actually:

Code: Select all

sudo ddm-mx -i nvidia -f nvidia-tesla-470-driver

I don't know what this installer runs after but it broke everything.
Am I supposed to run dkms or initramfs as I did later after ddm-mx? Or is it self sufficient ?

I can assure the synaptic installation was a success though. I even tried checking a lot of the 470 modules just to try it all.

As I reversed it installing the snapshot I don't have a valid DDM.LOG file anymore, but I can sacrifice my system and redo it if you want. ( I have snapshot and timeshift, and am willing to give it a go as a good beta :) )
It takes me just a bit my system is quite fast!

[dolphin_oracle]

I just ran

Code: Select all

ddm-mx nvidia-tesla-470-driver

yesterday for my laptop MX23b2.

I don't know if I had to make something by the end of it... But booting, it completely ruined all my Kernels.
None would boot up! It broke the wlan first and next usb3... and stalled there probing a lot of Genius inputs until I Ctrl-Alt-Del and re-installed my Snapshot.

Yes it really works now like a charm, doesn't stall at 11% and Ventoy already fixed the code!

By now I use Time-Shift too and will report next time I ruin my system

I ended up after the snapshot, installing the driver and modules (Tesla 470) by hand on Synaptic... It works when rebooted right away.
After I did DKMS and UPDATE-INITRAMFS to specific kernels, and it works! None broken.

I even got the NVIDIA X Server settings module working at last!!!! It displays all info! I'm quite amazed!

I'll try in the future to run specific 3D rendered stuff to check it out.
Not sure yet how to work the changing of GPU but I'll get it (bumblebee is broken, or deprecated? We'll see)

Primus Optimus and Vulkan drivers are still buzzwords to check too. It's too much for now!

running that "command" as written wouldn't do anything. please update to indicate what you actually ran, or provide the /var/log/ddm.log file.

I Was very distracted sorry, you're very right... it was actually:

Code: Select all

sudo ddm-mx -i nvidia -f nvidia-tesla-470-driver

I don't know what this installer runs after but it broke everything.
Am I supposed to run dkms or initramfs as I did later after ddm-mx? Or is it self sufficient ?

I can assure the synaptic installation was a success though. I even tried checking a lot of the 470 modules just to try it all.

As I reversed it installing the snapshot I don't have a valid DDM.LOG file anymore, but I can sacrifice my system and redo it if you want. ( I have snapshot and timeshift, and am willing to give it a go as a good beta :) )
It takes me just a bit my system is quite fast!

provide the output of this:

Code: Select all

nvidia-detect-mx

please.

make sure the latest ddm-mx is installed first though. there have been updates since beta2 launch.

[gRegNfo]

provide the output of this:

Code: Select all

nvidia-detect-mx

please.
make sure the latest ddm-mx is installed first though. there have been updates since beta2 launch.

First, I think looking at my own logs (snippets) that I messed up using

Code: Select all

ddm-mx -t

option! It's meant for devs only...
It was a typo, I then corrected it to use

Code: Select all

-i -f 

options!!!
(maybe it did something wrong and messed the DD-MX installer?) I'll try to replicate the next time I have a chance to backup all.

DDM-MX v.23.06.01
The Tesla v.470 drivers and kernel related files I LOCKED on synaptic so they won't upgrade to v.520 for now... until I test it and know they are fully supported.

So, here is what you asked, and a little more to add more insight:

Code: Select all

$ nvidia-detect-mx

Distribution:   MX

Latest  = 525.105.17
Detected NVIDIA GPUs:
01:00.0 3D controller [0302]: NVIDIA Corporation GK107M [GeForce GT 740M] [10de:0fdf] (rev a1)

Checking card:  NVIDIA Corporation GK107M [GeForce GT 740M] (rev a1)
Your card is supported by the nvidia 340 drivers series. nvidia-legacy-340xx-driver
Your card is supported by the nvidia 390 drivers series. nvidia-legacy-390xx-driver
Your card is supported by the nvidia tesla 418 drivers series. nvidia-tesla-418-driver
Your card is supported by the nvidia tesla 470 drivers series. nvidia-tesla-470-driver

It is recommended to install the following:
INSTALL:  nvidia-tesla-470-driver

To install alternate driver packages, use sudo ddm-mx -i nvidia -f [driver package name]

Code: Select all

$ inxi -G
Graphics:
  Device-1: Intel 3rd Gen Core processor Graphics driver: i915 v: kernel
  Device-2: NVIDIA GK107M [GeForce GT 740M] driver: nvidia v: 470.182.03
  Device-3: Chicony UVC 1.00 device HD WebCam type: USB driver: uvcvideo
  Display: x11 server: X.Org v: 1.21.1.7 driver: X:
    loaded: modesetting,nvidia unloaded: fbdev,vesa dri: crocus gpu: i915
    resolution: 1920x1080~60Hz
  API: OpenGL v: 4.2 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 4000 (IVB
    GT2)

Code: Select all

$ nvidia-smi
Tue Jun 27 21:51:58 2023       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 470.182.03   Driver Version: 470.182.03   CUDA Version: 11.4     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA GeForce ...  Off  | 00000000:01:00.0 N/A |                  N/A |
| N/A   48C    P8    N/A /  N/A |      3MiB /  4039MiB |     N/A      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
                                                                               
+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|  No running processes found                                                 |
+-----------------------------------------------------------------------------+

Code: Select all

$ cat /proc/driver/nvidia/version
NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.182.03  Fri Feb 24 03:29:56 UTC 2023
GCC version:  gcc version 12.2.0 (Debian 12.2.0-14) 

Code: Select all

$ cat /sys/module/nvidia/version
470.182.03

Code: Select all

$ grep "X Driver" /var/log/Xorg.0.log
[    10.715] (II) NVIDIA dlloader X Driver  470.182.03  Fri Feb 24 03:24:48 UTC 2023

Code: Select all

$ cat /proc/driver/nvidia/gpus/0000:01:00.0/information
Model: 		 Unknown
IRQ:   		 36
GPU UUID: 	 GPU-dd0cd3d3-dd92-bf7b-a5c7-0529b6d4097d
Video BIOS: 	 80.07.95.00.07
Bus Type: 	 PCIe
DMA Size: 	 40 bits
DMA Mask: 	 0xffffffffff
Bus Location: 	 0000:01:00.0
Device Minor: 	 0
GPU Excluded:	 No

Sorry I spamed here, just threw all I had in my notes here...
I hope it's enough