MX-19 Beta 1 Feedback

[zebedeeboss]

Got it installed using the same method used in antiX19 :D

This works on an RTX series Card

1 Boot to live USB
2 drop to tty login as root (it will probably do this auto due to RTX issues - this is Linux wide and not anything specific to do with Antix)
3 perform a full update & upgrade
4 run nvidia cli commands as per Dolphin instructions - see below
sudo apt install --install-recommends nvidia-driver nvidia-settings nvidia-kernel-dkms libnvidia-encode1
5 run cli-installer
6 reboot

Regards Zeb...

Zeb, did that pull in nvidia-persistenced?

in our user's case here, the drivers are installed but there is an error in the nvidia-persistenced installation.

complete file here

Code: Select all

https://pastebin.com/vNiKMAHX

Hi, Yes it did, here is the end of an apt dist-upgrade

Code: Select all

Processing triggers for hicolor-icon-theme (0.17-2) ...
Errors were encountered while processing:
 nvidia-persistenced
E: Sub-process /usr/bin/dpkg returned an error code (1)
zebedee@mx-2950x:~

Regards Zeb...

[Eadwine Rose]

@ER - nvidia installer does not touch grub

Noob grub user error, have never fiddled in that section there. I had grub set to possibly save last boot option. Now I know what that means

[bigbenaugust]

I just slapped 19b1 on my Lenovo W530 and I went to set up the work VPN (openconnect) to see if I could reproduce the issue I have at home with my MX 18.3 machines, (namely that that I get a 404 and a "can't do HTTP 1.0" sort of an error from openconnect in NetworkManager, but it runs fine from the CLI).

I go to the NetworkManager applet, down to VPN Connections, click Add a VPN Connection, and see that openconnect is an option, so the bits are all installed.
But I select the Cisco OpenConnect option and the VPN tab is missing, so I can't actually configure the connection.

For comparison, my BunsenLabs Lithium box (also Deb 10 based), there is a VPN tab there and I can configure it.

I did notice that MX 19b1 is missing the network-manager-openconnect-gnome package, but BL has it installed.

[anticapitalista]

I did notice that MX 19b1 is missing the network-manager-openconnect-gnome package, but BL has it installed.

So, if you install that package, does it solve your problem? If it does, then perhaps it should be included on the iso.

[bigbenaugust]

I did notice that MX 19b1 is missing the network-manager-openconnect-gnome package, but BL has it installed.

So, if you install that package, does it solve your problem? If it does, then perhaps it should be included on the iso.

Well, you can all slap me now.
I did a

Code: Select all

sudo apt search network-manager-openconnect-gnome 

and it returned nothing at all, so I was curious if y'all were hiding the package for some reason.
But this is a fresh install and a

Code: Select all

sudo apt update

is necessary first. Oops.

So that works and it actually connects, unlike MX 18! Thanks, I'll go back to feeling silly now.

[dolphin_oracle]

I'm getting errors during codecs install, first installed nvidia driver, which worked.
Performed a reboot, installed the codecs and when it was around 99% (Fix missing dependencies), it presented me an error: Error running 'apt-get -fm install' command.

Just stating for the record that I have this happening here as well.

you nvidia users...

[dolphin_oracle]

Got it installed using the same method used in antiX19 :D

This works on an RTX series Card

1 Boot to live USB
2 drop to tty login as root (it will probably do this auto due to RTX issues - this is Linux wide and not anything specific to do with Antix)
3 perform a full update & upgrade
4 run nvidia cli commands as per Dolphin instructions - see below
sudo apt install --install-recommends nvidia-driver nvidia-settings nvidia-kernel-dkms libnvidia-encode1
5 run cli-installer
6 reboot

Regards Zeb...

Zeb, did that pull in nvidia-persistenced?

in our user's case here, the drivers are installed but there is an error in the nvidia-persistenced installation.

complete file here

Code: Select all

https://pastebin.com/vNiKMAHX

Hi, Yes it did, here is the end of an apt dist-upgrade

Code: Select all

Processing triggers for hicolor-icon-theme (0.17-2) ...
Errors were encountered while processing:
 nvidia-persistenced
E: Sub-process /usr/bin/dpkg returned an error code (1)
zebedee@mx-2950x:~

Regards Zeb...

thanks. confirms my suspicion that debian is mucking this up this morning. might be OK later today.

[Dede]

Root Terminal disappeared?

Please elaborate. Your comment as it appears is not helpful to developers without more details.

It's not in the system, I can't find it anywhere...

[entropyfoe]

Here is the tail of that ddm.log for the nvidia-persistenced error. I am not sure how big a deal this is, nvidia is loaded, working, and video with comptom compositing is working fine.

Code: Select all

Setting up nvidia-persistenced (418.56-1) ...
Warning: The home dir /var/run/nvpd/ you specified can't be accessed: No such file or directory
Adding system user `nvpd' (UID 119) ...
Adding new group `nvpd' (GID 129) ...
Adding new user `nvpd' (UID 119) with group `nvpd' ...
Not creating home directory `/var/run/nvpd/'.
Starting NVIDIA Persistence Daemon
nvidia-persistenced failed to initialize. Check syslog for more details.
invoke-rc.d: initscript nvidia-persistenced, action "start" failed.
dpkg: error processing package nvidia-persistenced (--configure):
 installed nvidia-persistenced package post-installation script subprocess returned error exit status 1
Setting up nvidia-egl-icd:amd64 (418.74-1) ...
Setting up nvidia-egl-icd:i386 (418.74-1) ...
Setting up libnvidia-encode1:amd64 (418.74-1) ...
Setting up nvidia-driver-libs:amd64 (418.74-1) ...
Setting up nvidia-driver-libs:i386 (418.74-1) ...
Setting up nvidia-driver-libs-i386:i386 (418.74-1) ...
Processing triggers for nvidia-alternative (418.74-1) ...
update-alternatives: updating alternative /usr/lib/nvidia/current because link group nvidia has changed slave links
Setting up nvidia-kernel-dkms (418.74-1) ...
Loading new nvidia-current-418.74 DKMS files...
Building for 4.19.0-5-amd64
Building initial module for 4.19.0-5-amd64
Done.

nvidia-current.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.19.0-5-amd64/updates/dkms/

nvidia-current-modeset.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.19.0-5-amd64/updates/dkms/

nvidia-current-drm.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.19.0-5-amd64/updates/dkms/

nvidia-current-uvm.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.19.0-5-amd64/updates/dkms/

depmod...
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down

DKMS: install completed.
Setting up nvidia-driver (418.74-1) ...
Processing triggers for libc-bin (2.28-10) ...
Processing triggers for initramfs-tools (0.133) ...
update-initramfs: Generating /boot/initrd.img-4.19.0-5-amd64
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries 
    nor crypto modules. If that's on purpose, you may want to uninstall the 
    'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs 
    integration and avoid this warning.
W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_load.bin for module nouveau
I: The initramfs will attempt to resume from /dev/nvme0n1p2
I: (UUID=4ce88423-c5cf-4a69-b6d4-1d9fcafa7353)
I: Set the RESUME variable to override this.
Processing triggers for update-glx (1.0.0) ...
Processing triggers for glx-alternative-nvidia (1.0.0) ...
update-alternatives: using /usr/lib/nvidia to provide /usr/lib/glx (glx) in auto mode
Processing triggers for glx-alternative-mesa (1.0.0) ...
Processing triggers for systemd (1:241-5+mx19+2) ...
Processing triggers for libc-bin (2.28-10) ...
Processing triggers for initramfs-tools (0.133) ...
update-initramfs: Generating /boot/initrd.img-4.19.0-5-amd64
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries 
    nor crypto modules. If that's on purpose, you may want to uninstall the 
    'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs 
    integration and avoid this warning.
W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_load.bin for module nouveau
I: The initramfs will attempt to resume from /dev/nvme0n1p2
I: (UUID=4ce88423-c5cf-4a69-b6d4-1d9fcafa7353)
I: Set the RESUME variable to override this.
Errors were encountered while processing:
 nvidia-persistenced
E: Sub-process /usr/bin/dpkg returned an error code (1)
Finished

[Eadwine Rose]

I'm getting errors during codecs install, first installed nvidia driver, which worked.
Performed a reboot, installed the codecs and when it was around 99% (Fix missing dependencies), it presented me an error: Error running 'apt-get -fm install' command.

Just stating for the record that I have this happening here as well.

you nvidia users...

Yeah.. I know.. we're an annoying lot huh.