-&t=57730, for the enhanced MX17+1 version
-&t=55077, for the proprietary version from an Nvidia .run file
For MX-21, the second approach is described herein because it was the easier one to adapt.
*************************************************************************
Again, 3 basic steps are involved, but a 4th intermediate step is required:
1) Reverting to xorg-server (1.19.2).
It requires the forced installation (dpkg --install *.deb)
of 22 MX18.3 debian-stretch-based packages
rather than 21 :
Code: Select all
xserver-xorg-core_1.19.2-1+deb9u5_i386.deb
xserver-xorg-video-amdgpu_18.1.0-1~mx17+1_i386.deb
xserver-xorg-video-ati_1%3a18.1.0-1~mx17+1_i386.deb
xserver-xorg-video-cirrus_1.5.3-1+b2_i386.deb
xserver-xorg-video-fbdev_0.4.4-1+b5_i386.deb
xserver-xorg-video-intel_2%3a2.99.917+git20180925-2~mx17+1_i386.deb
libxcb-util0_0.3.8-3+b2_i386.deb
xserver-xorg-video-mach64_6.9.5-1+b2_i386.deb
xserver-xorg-video-mga_1.6.5-1_i386.deb
xserver-xorg-video-neomagic_1.2.9-1+b2_i386.deb
xserver-xorg-video-nouveau_1%3a1.0.15-3~mx17+1_i386.deb
xserver-xorg-video-openchrome_0.5.0-3_i386.deb
xserver-xorg-video-qxl_0.1.4+20161126git4d7160c-1_i386.deb
xserver-xorg-video-r128_6.10.2-1_i386.deb
xserver-xorg-video-radeon_1%3a18.1.0-1~mx17+1_i386.deb
xserver-xorg-video-savage_2.3.9-1_i386.deb
xserver-xorg-video-siliconmotion_1.7.9-2_i386.deb
xserver-xorg-video-sisusb_0.9.7-1_i386.deb
xserver-xorg-video-tdfx_1.4.7-1_i386.deb
xserver-xorg-video-trident_1.3.8-1_i386.deb
xserver-xorg-video-vesa_2.3.4-1+b2_i386.deb
xserver-xorg-video-vmware_13.2.1-1+b1_i386.deb
The intel video module has a dependency on libxcb-util0:
Stretch and Buster use the same version of it, but Bullseye
doesn’t have it.
2) For kernel replacement, the linux-headers-4.9.0-279-antix.1-686-smp-pae
and linux-image-4.9.0-279-antix.1-686-smp-pae .deb files are used.
(These are the latest versions, available from the just-released antiX-21).
The MX-21_fluxbox_386.iso has linux-headers-5.10.0-9-686-pae,
linux-headers-5.10.0-9-common, and linux-headers-686-pae installed.
It has the image packages, linux-image-5.10.0-9-686-pae and linux-image-686-pae
installed. All can be removed.
Intermediate Step
It was discovered that an anomaly is caused by MX-Snapshot when trying
to install a customized version of MX19 on another machine requiring the
subject driver. On the .iso produced by MX-Snapshot, the disable-nouveau.conf
file created in the /etc/modprobe.d directory is deleted. (This problem would
be the same for MX21).
This characteristic is of no consequence if the target machine for
the MX-Snapshot .iso uses a graphics card other than NVIDIA, but
for a machine that does have the card, when boot-up is attempted
with the MX-Snapshot live dvd, failure inevitably occurs with a
heavily pixillated screen.
The workaround is can be done in at least 2 different ways:
-after completion of Step 2, suspend the graphics installation entirely,
and complete the installation of all additional application software that is desired;
or alternately,
complete Step 3 up to and including the sudo ./NVIDIA-Linux-x86-304.137.run -x
command and then install all additional application software.
NB: the Step 3 procedure as described below utilizes a /home subdirectory
for locating the NVIDIA*.run and nvidia*.patch files. As the /home
subdirectories can be omitted when running MX-Snapshot, a directory
that is sure to be retained should be used for these 2 files, and for
saving disable-nouveau.conf, e.g. /usr/share/Nvidia.
-run MX-Snapshot to create the customized .iso
-install the customized .iso in the target NVIDIA machine
-complete the graphics installation with the restoration of the
disable-nouveau.conf file to /etc/modprobe.d and the
installation of the nvidia-legacy-304xx-driver as the last 2 sub-steps.
3) Except for the directory change prescribed in the Intermediate Step above, and
omission of the patch, follow EXACTLY the July 17, 2018 steps in the “nvidia-304 won’t install” post, https://ubuntuforums.org/showthread.php?t=2396263.
Len E.