After an unsuccessful installation, the MX 21.0 had to return to the MX 19.4 and configure the system "from scratch".

Than MX-19.4 "patio Feo" лучше версии MX-21 "Wildflower"

1. For installation, MX 21 is not suitable for creating a bootable carrier "DD if = file.iso of =/DEV/SDD BS = 1M"
   T.K. With this option, the system with a USB disk does not load (the cursor on the black screen flashes).
   It is necessary to record an ISO file on a flash drive with formatting in NTFS in the RUFUS. utility
2. The MX 21 installation reached only 94%, The was when executing the command /bin /sync
3. MX 21 users complain about very slow work on old PCs (for which MX-19 is better suited) ..

4. Since the installation program has been processed in the MX 21, the choice of the bootloader installation is complicated - MBR, PBR, ESP. As in the MX-19, it is necessary to explain the PBR point. If UEFI in Legacy (UEFI BIOS, that is, a hard drive is broken with a type of MBR marking), then when choosing an MBR option and installation in the boot sector, when the installation program is “collapsed,” the loading of the computer (it is impossible to upload both Linux and Windows), as GRUB is faulty. Treatment leads to the "destruction" of Linux loading and Salizes the download of Windows:

   • Download from the Windows CD, the transition to the "recovery environment" and the execution of commands in it:

   bootrec /FixMbr
   
   bootrec /Fixboot
   
   bootrec /RebuildBCD

In my case, I had to additionally "sweat":

bootrec /FixMbr
bcdedit /export C:\BCD_BackUp
c:
cd boot
attrib bcd -s -h -r
ren c:\boot\bcd bcd.old
bootrec /Fixboot
bootrec /Rebuildbcd

Note: If the command is executing boorec /FixBoot выводится ошибка "Элемент не найден",
then you need to make the first Windows section ("reserved by the system") active using DISkparT :

diskpart
select disk 0
select parTition 1
active
exit

Add: if there is only one Windows section on the hard drive (which is loading and systemic, instead of EFI System partition), but the download files on it are destroyed, the following method will help: * load from the flash drive of the Windows 10 installation and enter the recovery console where to execute commands

cd /d c:\boot
bcdboot c:\Windows /L ru-ru /S c: /F all

Где /L - язык, /S - принудительное указание вместо раздела EFI диска C:, /F ALL - firmware type. Разрешенные значения UEFI, BIOS, и ALL. Очевидно, что в случае наличия EFI раздела, параметр /S C: You should not specify.

Результат: "Файлы загрузки успешно созданы".

Actions after installation MX 19.4

1. Regional settings ("Local")

1) set up the local (settings of the operating system in the national language and fonts):
Only Russia and the United States left, the UTF-8 encoding.

Program "Start" - "Settings" - "System LocaLes " can be called from the command line:

dpkg-reconfigure locaLes

2. Update

2) if the double loading system (Windows / Linux), then immediately after installing 19.4 there will be no "Windows" item in the GRUB boot menu.
You need to execute the command "UPDate-grub", которая просмотрит жёсткие диски и обнаружит установленные операционные системы (в том числе, ОС Windows), и добавит их в загрузочное меню GrUB2:

sudo update-grUB

3) Immediately completed the Internet update of packages "Debian 10 Buster":

sudo apt-get update
sudo apt-get upgrade

At the same time, the installed Intel-Fi package has been updatedrmware, amd-micrOcode and the driver for the display.
About 300 MB of packages were installed. The installation took about 30-40 minutes.
At its end, the PC reloaded to apply changes.

4) switched in the catalog /etc/apt/sources.list.d репозитории на версию "DebiaN 11 Bullseye " with all updates.

Sources.list:

Deb http: //deb.debian.org/debian bullseye main contrib non-free
Deb-Src http://deb.debian.org/debian bullseye main contrib non-free

Deb http: //deb.debian.org/debian-security/ bullseye-security main contrib non-free
Deb-Src http://deb.debian.org/debian-security/ bullseye-security main contrib non-free

Deb http: //deb.debian.org/debian bullseye-updates main contrib non-free
Deb-Src http://deb.debian.org/debian bullseye-updates main contrib non-free

Deb http: //deb.debian.org/debian bullseye-proposed-updates main contrib non-free
Deb-Src http://deb.debian.org/debian bullseye-proposed-updates main contrib non-free

Deb http: //deb.debian.org/debian bullseye-backports main contrib non-free
Deb-Src http://deb.debian.org/debian bullseye-backports main contrib non-free

Deb http: //deb.debian.org/debian bullseye-backports-sloppy main contrib non-free
Deb-Src http://deb.debian.org/debian bullseye-backports-sloppy main contrib non-free

Testing.list:

Deb http: //mirror.truenetwork.ru/mxlinux/mx/repo/ buster main non-free
Deb http: //mirror.truenetwork.ru/mxlinux/mx/repo/ buster aHS
Deb http: //mirror.truenetwork.ru/mxlinux/mx/testrepo/ buster test

Installation of new versions of packages went more than 4 hours with stops to request updating configuration files
Everywhere, in addition to setting up the GRUB-PC package, I chose the replacement of .conf with new versions.

sudo apt-get update
sudo apt-get upgrade

In the window with a request during the installation, in the GRUB settings, I indicated the installation with a checkmark for the device /dev /sda_

The MX -19.4 operating system after the update loaded without problems - in the double loading menu of both Linux and Windows.

In the programs of the LSB_ programrelease -a указан выпуск:

DISTributor ID: Debian
debian GNU/Linux 11 (Bullseye) .
Release: 11
codenamE: Bullseye

The only drawback is the core 4.19.0-16-amD64, which is outdated.

5) Data is not necessarily performed. Bullseye-b repository updateackporTS

Install the core of 5.10 and the other newer from the debi repositoryan Backports (назначение ясно из перевода слов back и porTS - adaptation of more new software for old versions of the OS).

sudo apt -t bullseye-backports upgrade

228 MB of archives were loaded. The installation began, which went for 50 minutes.
It can be seen that the package manager pulled a new core 5.14.0.
When requests for updating configuration files, the “Y” responded everywhere positively.

Now the core is according to the conclusion of the team uname -r следующее:

5.14.0-0.bpo.2-amD64

The network via Wi-Fi works, everything is fine.

6) Addition: The next day completed the installation of packages - command "apt dist-upgrade" - интеллектуальную систему для установки новейших версий пакетов программ, которые доступны из репозиториев, указанных через /etc/apt/sources.list.d/*.
Unlike simple apt upgrade, команда apt dist-upgrade производит удаление и добавление пакетов согласно зависимостям, с целью получить самую новую версию установленных пакетов данного дистрибутива.

sudo apt dist-upgrade

Update using Dist-UPG commandraDe "downloaded 500 MB of packages.

During the withdrawal of information, the installation of packages skipped reports about the temporary removal of a slight number of packages:

• Python (because Python2 is not needed, everywhere replaced with Python3)
• python-minimal (из старой версии python, пакет устарел, недоступен из источников sources.list)
• GIMP-Python (has unsatisfied dependences of Python2)
• LibGCC8-DEV (package on the new version of the distribution from Sources.list)
• Libstdc ++-8-DEV (package on the new version of the distribution from Sources.list)
• Fuse (since replaced with Fuse3)
• DISk-manager (пакет на найден в новой версии дистрибутива из sources.list)
• Libreoffice-draw (переустановлен новой версией в ходе выполнения apt-get dist-upgrade)
• Libreoffice-base (переустановлен новой версией в ходе выполнения apt-get dist-upgrade)
• Libreoffice-impress (переустановлен новой версией в ходе выполнения apt-get dist-upgrade)
• Libreoffice-writer (переустановлен новой версией в ходе выполнения apt-get dist-upgrade)
• Libreoffice-common (переустановлен новой версией в ходе выполнения apt-get dist-upgrade)

ОднAko later, during the execution of the same command apt-get dist-upgrade, данные пакеты были установлены заново, точнее, переустановлены с новыми версиями. Например, для языка python 3 установлен пакет python 3.9.2-3. Таким образом, команда apt-get dist-upgrade затрагивает систему более существенно.

The situation with the package "Disk-manager"

• This package was not found in the DEBI distributionan 11 "Bullseye". Видимо, он входил в MX19 на основе "Buster", but do not enter the newer OS:
  https: // packages.debian.org/search?keywords=disk-manager

There are no problems with other packages. For example, a package compton 0.1.beta был заменён на 1.1, flatpak с версии 1.2.5 сразу на версию 1.10.5, менеджер пакетов synaptic с версии 0.90+mX19 on 0.90.2.

This update does not lead to an increase in the version of Debian 11, only versions of packages are changing.

7) cleaning (removal from the system of unnecessary packages)

sudo apt autoremOve
sudo apt autoclean

8) rebooting and evaluating available resources.

sudo reboot

After rebooting, a window appeared with a message about replacing Cliit with Diodon:

"Clipit has been deprecated and is no longer supported in DebiaN "
Diodon,a supported replacement for ClipIt, has been automatically installed for your convenience.
OK

The system is completely loaded, there are almost no errors. ;-)
"Network manager не запущен".

sudo service network-manager start

"Network-manager": unrecognized service

For this you need:

• or manually choose in the G menurub пункт загрузки (вариант запуска) "...SystemD ".
• or add to the parameters of the nucleus to the file /etc /default/grub в строку GRUB_CMDLINE_LINUX_DEFAULT (затем выполнить команду sudo update-grub)
• or in the graphic application "MX Boot Options" configure and apply the nucleus parameter: "Start" -> "Settings" -> "MX tools" ->

  "MX Boot Options" -> "Nuclear Parameters" ->
  quiet splash init=/lib/systemd/systemd

3. Screen

6) Setting the scale of the screen. Since the resolution of the netbook screen is only 1024x600 pixels, part of the user interface (lists, buttons in the lower part of the window) in many programs go beyond the boundaries of the screen. Web pages may also look too large. To eliminate this problem, you need to change the scale of information on the screen in the operating system:

Start - Settings - MX TWEak - Экран

Piring xrandr - 0,90

Apply - close.

Comparison of real consumption of RAM:

MX -19 Core 5.14 - uses 475 MB,
MX -21 (Live USB) Nuclear 5.14 - uses 547 MB.

That is, the MX-21 OS consumes more RAM than the MX-19.

Related publications

Troubleshooting L2TP/IPsec connection errors "Could not add IPsec connection" and "no acceptable traffic selectors found"

Разбивка жесткого диска для установки Linux Mint на старый ПК с BIOS в режиме GPT

Обновление Linux Mint 21.3 Virginia до Linux Mint 22.3 Zena

Removing the Xanmod kernel from a Linux operating system

Устранение отклонений при установке драйвера видеокарты nVidia