---
title: 'Setting up MX Linux after a clean install: locale, updates, screen scale'
url: 'https://ra1ahq.blog/en/nastroika-mx-linux-posle-chistoi-ustanovki-lokal-obnovleniya-masshtab-ekrana'
markdown: 'https://ra1ahq.blog/en/nastroika-mx-linux-posle-chistoi-ustanovki-lokal-obnovleniya-masshtab-ekrana.md'
lang: en
date: '2021-12-16'
description: 'After an unsuccessful installation of MX 21.0, I had to return to MX 19.4 and configure the system from scratch. Why is'
taxonomy:
category:
- blog
tag:
- Linux
archives_month:
- dec_2021
archives_year:
- '2021'
---
# Setting up MX Linux after a clean install: locale, updates, screen scale
16
December
2021
16:02
### Setting up MX Linux after a clean install: locale, updates, screen scale
[Linux](https://ra1ahq.blog/en/tag:Linux)
16 December 2021 16:02
After an unsuccessful installation of MX 21.0, I had to return to MX 19.4 and configure the system from scratch.
### Why is the MX-19.4 "Patio Feo" better than the MX-21 "Wildflower" version?
1. The standard method of creating bootable media "dd if=file.iso of=/dev/sdd bs=1M" is not suitable for installing MX 21
because with this option, the system does not boot from the USB drive (the cursor blinks on a black screen).
*You need to write an ISO file to a flash drive formatted in NTFS using the RuFus utility.*
2. The installation of MX 21 only reached 94%, *stopped when executing the command /bin/sync*
3. MX 21 users have complained about very slow performance on older PCs (for which the MX-19 is better suited).
4. Since the installation program has been redesigned in MX 21, the choice of installing the bootloader is more complicated - MBR, PBR, ESP. As with the MX-19, the PBR clause needs an explanation. If the UEFI is in Legacy mode (UEFI BIOS, that is, the hard drive is partitioned with the MBR partition type), then when you select the MBR option and install it in the boot sector, if the installation program crashes or freezes, the computer will boot (it is impossible to boot both Linux and Windows), since GRUB is faulty. The treatment "destroys" the Linux boot and *restores the Windows boot*:
- Boot from the Windows CD, go to the "Recovery Environment" and run the commands in it:
`bootrec /FixMbr
bootrec /FixBoot
bootrec /RebuildBCD
`
In my case I had to work extra hard:
```
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 when executing the command `boorec /FixBoot` the error "*Element not found*" is displayed,
then you need to make the first Windows partition (“Reserved by the system”) *active* using **diskpart**:
```
diskpart
select disk 0
select partition 1
active
exit
```
Addition: if there is only one Windows partition on the hard drive (which is boot and system partition, instead of the EFI system partition), but the boot files on it are destroyed, the following method will help: \* boot from the Windows 10 installation flash drive and enter the recovery console, where run the commands
```
cd /d c:\boot
bcdboot c:\Windows /L ru-ru /S c: /F ALL
```
Where /L is the language, /S is the forced indication of the C: drive instead of the EFI partition, /F ALL is the firmware type. Allowed values are UEFI, BIOS, and ALL. Obviously, if there is an EFI partition, the /S c: parameter should not be specified.
Result:**"Download files created successfully"**.
Thus, the Windows boot loader has been restored after an unsuccessful installation of Linux MX 21 and the Windows OS is loaded when the computer is turned on.
---
### Steps after installing MX 19.4
#### 1. Regional settings (“locale”)
1\) Configured the locale (operating system settings for the national language and fonts):
I left only Russia and the USA, UTF-8 encoding.
program **"Start" - "Settings" - "System Locales"** can be called from the command line:
```
dpkg-reconfigure locales
```
#### 2. Update
2\) If the system is dual boot (Windows / Linux), then immediately after installing 19.4 there will be no “Windows” item in the Grub boot menu.
You need to run the "update-grub" command, which will scan the hard drives and detect installed operating systems (including Windows OS), and add them to the Grub2 boot menu:
```
sudo update-grub
```
3\) Immediately updated the "Debian 10 Buster" packages over the Internet:
```
sudo apt-get update
sudo apt-get upgrade
```
At the same time, the installed intel-firmware package, amd-microcode and the display driver were updated.
About 300 MB of packages were installed. Installation took about 30-40 minutes.
Upon completion, I rebooted the PC to apply the changes.
4\) Switched in the directory **/etc/apt/sources.list.d** repositories for version "**Debian 11 Bullseye**" with all updates.
This time I **didn't set myself** the task of switching to Debian 12 Bookworm/sid, as written [in the article - about updating Debian](https://ra1ahq.blog/en/pro-obnovlenie-debian-10-buster-do-11-bullseye) because the current version of Debian at the time of writing is Debian 11 "Bullseye".
*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 took more than 4 hours with stops for requests to update configuration files
Everywhere, except for setting up the package, grub-pc chose to replace .conf with new versions.
```
sudo apt-get update
sudo apt-get upgrade
```
In the window with the request during installation, in the GRUB settings, I checked the installation *only on the /dev/sda* device
After the update, the MX-19.4 operating system booted without problems - into the dual boot menu of both Linux and Windows.
lsb\_release -a program messages indicate the release:
***Distributor ID: Debian***
***Debian GNU/Linux 11 (bullseye).***
***Release: 11***
***Codename: bullseye***
The only drawback is kernel 4.19.0-16-amd64, which is outdated.
5\) *This point is not necessary*. Update from the bullseye-backports repository
Let's install kernel 5.10 and other newer ones from the Debian Backports repository (the purpose is clear from the translation of the words back and ports - adaptation of newer software for older OS versions).
```
sudo apt -t bullseye-backports upgrade
```
228 MB of archives were downloaded. The installation began and took 50 minutes.
It can be seen that the package manager has pulled up a new kernel **5.14.0.**
When asked to update configuration files, the answer was positive everywhere - “Y”.
Now the kernel according to the command output `uname -r` the following:
*5.14.0-0.bpo.2-amd64*
The network via Wi-Fi works, everything is fine.
6)**Update: next day** completed package installation - command **"apt dist-upgrade"**- an intelligent system for installing the latest versions of software packages that are available from repositories specified through /etc/apt/sources.list.d/\*.
Unlike a simple `apt upgrade`, the `apt dist-upgrade` command removes and adds packages based on dependencies in order to obtain the latest versions of the installed packages for the given distribution.
```
sudo apt dist-upgrade
```
Updating using the "dist-upgrade" command downloaded 500 MB of packages.
During the display of package installation information, messages appeared about the temporary removal of a small number of packages:
- python (because python2 is not needed, it has been replaced by python3 everywhere)
- python-minimal (from an old version of python, the package is deprecated, not available from sources.list)
- gimp-python (has unmet python2 dependencies)
- libgcc8-dev (package not found in the new version of the distribution from sources.list)
- libstdc++-8-dev (package not found in the new version of the distribution from sources.list)
- fuse (since replaced by fuse3)
- disk-manager (package not found in the new version of the distribution from sources.list)
- libreoffice-draw (reinstalled with new version during apt-get dist-upgrade)
- libreoffice-base (reinstalled with new version during apt-get dist-upgrade)
- libreoffice-impress (reinstalled with new version during apt-get dist-upgrade)
- libreoffice-writer (reinstalled with new version during apt-get dist-upgrade)
- libreoffice-common (reinstalled with new version during apt-get dist-upgrade)
However, later on—during the execution of that same `apt-get dist-upgrade` command—these packages were installed again; or rather, they were reinstalled with newer versions. For instance, the `python3.9.2-3` package was installed for Python 3. Thus, the `apt-get dist-upgrade` command has a more significant impact on the system.
The situation with the *"disk-manager"* package is unclear
- this package was not found in the Debian 11 "Bullseye" distribution. Apparently it was included in MX19 based on "Buster", but not included in newer OSs:
There are no problems with other packages. For example, the *compton* 0.1.beta package was replaced by 1.1, *flatpak* from version 1.2.5 immediately to version 1.10.5, the *synaptic* package manager from version 0.90+mx19 to 0.90.2.
This update does not upgrade Debian 11, only package versions are changed.
7\) Cleaning (removing unnecessary packages from the system)
```
sudo apt autoremove
sudo apt autoclean
```
8\) Reboot and evaluate available resources.
```
sudo reboot
```
After the reboot, 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 fully loaded, there are almost no errors. ;-)
*"network manager is not running."*
```
sudo service network-manager start
```
*"network-manager": unrecognized service*
!**Solution**: I independently found out that Network Manager, which manages network connections, works fine in SystemD service startup control mode.
**To do this, you need to:**
- either manually select the "...SystemD" boot option from the GRUB menu;
- or add the parameter to the `GRUB_CMDLINE_LINUX_DEFAULT` line in the `/etc/default/grub` file (then run the `sudo update-grub` command);
- or configure and apply the kernel parameter using the "MX Boot Options" graphical application: "Start" -> "Settings" -> "MX Tools" -> "MX Boot Options" → "Kernel parameters" →
**`quiet splash init=/lib/systemd/systemd`**
A nice feature of **systemd** is the availability of the `sudo journalctl -xe` command and the `systemctl` service management tool. For example, the command `sudo systemctl status NetworkManager` displays the service's status, its RAM usage, and recent service events.
#### 3. Screen
6\) Setting the screen scale. Since the netbook screen resolution is only 1024x600 pixels, part of the user interface (lists, buttons at the bottom of the window) for many programs extends beyond the screen. Web pages may also appear too large. To fix this problem, you need to change the scale of display of information on the screen in the operating system:
**Start - Settings - MX Tweak - Screen**
*xrandr scaling - 0.90*
Apply - Close.
**Comparison of real RAM consumption:**
MX-19 kernel 5.14 - uses 475 MB,
MX-21 (Live USB) kernel 5.14 - uses 547 MB.
That is, the MX-21 OS consumes more RAM than the MX-19.
### Related publications
[  Установка драйвера ядра для Wi-Fi адаптера TP-Link после обновления ОС Debian ](https://ra1ahq.blog/en/ustanovka-draivera-yadra-dlya-wi-fi-adaptera-tp-link-posle-obnovleniya-os-debian)
[  Linux Cinnamon Desktop Applets for Listening to Internet Radio Stations ](https://ra1ahq.blog/en/applety-dlya-rabochego-stola-linux-cinnamon-dlya-proslushivaniya-internet-radiostancii)
[  Passing a parameter to a Linux module/driver ](https://ra1ahq.blog/en/peredacha-parametra-modulyu-draiveru-linux)
[  Installing the TP-Link Archer T600U Nano Wi-Fi adapter driver in Debian 13 "Trixie" ](https://ra1ahq.blog/en/ustanovka-draivera-wi-fi-adaptera-tp-link-archer-t600u-nano-v-debian-13-trixie)
[  Installing the audio equalizer pulseaudio-equalizer-ladspa on Linux ](https://ra1ahq.blog/en/ustanovka-v-linux-ekvalaizera-zvuka-pulseaudio-equalizer-ladspa)
[ Backward](https://ra1ahq.blog/en/like-fm-novaya-radiostanciya-na-104-8-mgc "Previuous page")
[ Forward ](https://ra1ahq.blog/en/nastroika-mx-linux-posle-chistoi-ustanovki-uluchshennyi-sposob "Next page")
## Languages
- [Русский](https://ra1ahq.blog/posts/nastroika-mx-linux-posle-chistoi-ustanovki-lokal-obnovleniya-masshtab-ekrana)
- [English](https://ra1ahq.blog/en/nastroika-mx-linux-posle-chistoi-ustanovki-lokal-obnovleniya-masshtab-ekrana)
- [Deutsch](https://ra1ahq.blog/de/posts/nastroika-mx-linux-posle-chistoi-ustanovki-lokal-obnovleniya-masshtab-ekrana)
- [Français](https://ra1ahq.blog/fr/posts/nastroika-mx-linux-posle-chistoi-ustanovki-lokal-obnovleniya-masshtab-ekrana)
- [中文 (简体) (cn)](https://ra1ahq.blog/zh-cn/posts/nastroika-mx-linux-posle-chistoi-ustanovki-lokal-obnovleniya-masshtab-ekrana)
## Theme
## RSS feeds
[ Atom 1.0](https://ra1ahq.blog/en/.atom) [ RSS](https://ra1ahq.blog/en/.rss)
## Popular tags
[APRS](https://ra1ahq.blog/en/tag:APRS) [CW](https://ra1ahq.blog/en/tag:CW) [DX](https://ra1ahq.blog/en/tag:DX) [FM](https://ra1ahq.blog/en/tag:FM) [Linux](https://ra1ahq.blog/en/tag:Linux) [VHF](https://ra1ahq.blog/en/tag:VHF) [antennas](https://ra1ahq.blog/en/tag:antennas) [firefox](https://ra1ahq.blog/en/tag:firefox) [morse](https://ra1ahq.blog/en/tag:morse) [soundtrack](https://ra1ahq.blog/en/tag:soundtrack) [video](https://ra1ahq.blog/en/tag:video) [windows](https://ra1ahq.blog/en/tag:windows) [youtube](https://ra1ahq.blog/en/tag:youtube) [КВ](https://ra1ahq.blog/en/tag:%D0%9A%D0%92) [ТВ](https://ra1ahq.blog/en/tag:%D0%A2%D0%92) [УКВ](https://ra1ahq.blog/en/tag:%D0%A3%D0%9A%D0%92) [антенны](https://ra1ahq.blog/en/tag:%D0%B0%D0%BD%D1%82%D0%B5%D0%BD%D0%BD%D1%8B) [безопасность](https://ra1ahq.blog/en/tag:%D0%B1%D0%B5%D0%B7%D0%BE%D0%BF%D0%B0%D1%81%D0%BD%D0%BE%D1%81%D1%82%D1%8C) [длинные волны](https://ra1ahq.blog/en/tag:%D0%B4%D0%BB%D0%B8%D0%BD%D0%BD%D1%8B%D0%B5%20%D0%B2%D0%BE%D0%BB%D0%BD%D1%8B) [путешествия](https://ra1ahq.blog/en/tag:%D0%BF%D1%83%D1%82%D0%B5%D1%88%D0%B5%D1%81%D1%82%D0%B2%D0%B8%D1%8F) [религия](https://ra1ahq.blog/en/tag:%D1%80%D0%B5%D0%BB%D0%B8%D0%B3%D0%B8%D1%8F) [соревнования](https://ra1ahq.blog/en/tag:%D1%81%D0%BE%D1%80%D0%B5%D0%B2%D0%BD%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D1%8F) [спутники](https://ra1ahq.blog/en/tag:%D1%81%D0%BF%D1%83%D1%82%D0%BD%D0%B8%D0%BA%D0%B8) [средние волны](https://ra1ahq.blog/en/tag:%D1%81%D1%80%D0%B5%D0%B4%D0%BD%D0%B8%D0%B5%20%D0%B2%D0%BE%D0%BB%D0%BD%D1%8B) [схемы](https://ra1ahq.blog/en/tag:%D1%81%D1%85%D0%B5%D0%BC%D1%8B) [тесты](https://ra1ahq.blog/en/tag:%D1%82%D0%B5%D1%81%D1%82%D1%8B) [трансивер](https://ra1ahq.blog/en/tag:%D1%82%D1%80%D0%B0%D0%BD%D1%81%D0%B8%D0%B2%D0%B5%D1%80) [управление](https://ra1ahq.blog/en/tag:%D1%83%D0%BF%D1%80%D0%B0%D0%B2%D0%BB%D0%B5%D0%BD%D0%B8%D0%B5) [фотографии](https://ra1ahq.blog/en/tag:%D1%84%D0%BE%D1%82%D0%BE%D0%B3%D1%80%D0%B0%D1%84%D0%B8%D0%B8)
## Random post
[ I'll be lucky!](https://ra1ahq.blog/en/random)
## Archive of posts
- [ October 2026 ✒ 4 ](https://ra1ahq.blog/en/archives_month:oct_2026)
- [ September 2026 ✒ 9 ](https://ra1ahq.blog/en/archives_month:sep_2026)
- [ August 2026 ✒ 6 ](https://ra1ahq.blog/en/archives_month:aug_2026)
- [ July 2026 ✒ 13 ](https://ra1ahq.blog/en/archives_month:jul_2026)
- [ June 2026 ✒ 8 ](https://ra1ahq.blog/en/archives_month:jun_2026)
- [ May 2026 ✒ 2 ](https://ra1ahq.blog/en/archives_month:may_2026)
- [ April 2026 ✒ 6 ](https://ra1ahq.blog/en/archives_month:apr_2026)
- [ March 2026 ✒ 3 ](https://ra1ahq.blog/en/archives_month:mar_2026)
- [ February 2026 ✒ 7 ](https://ra1ahq.blog/en/archives_month:feb_2026)
- [ January 2026 ✒ 8 ](https://ra1ahq.blog/en/archives_month:jan_2026)
- [ December 2025 ✒ 12 ](https://ra1ahq.blog/en/archives_month:dec_2025)
- [ November 2025 ✒ 9 ](https://ra1ahq.blog/en/archives_month:nov_2025)
- [ October 2025 ✒ 8 ](https://ra1ahq.blog/en/archives_month:oct_2025)
- [ September 2025 ✒ 5 ](https://ra1ahq.blog/en/archives_month:sep_2025)
- [ August 2025 ✒ 8 ](https://ra1ahq.blog/en/archives_month:aug_2025)
- [ July 2025 ✒ 6 ](https://ra1ahq.blog/en/archives_month:jul_2025)
- [ June 2025 ✒ 10 ](https://ra1ahq.blog/en/archives_month:jun_2025)
- [ May 2025 ✒ 4 ](https://ra1ahq.blog/en/archives_month:may_2025)
- [ April 2025 ✒ 4 ](https://ra1ahq.blog/en/archives_month:apr_2025)
- [ March 2025 ✒ 4 ](https://ra1ahq.blog/en/archives_month:mar_2025)
- [ February 2025 ✒ 11 ](https://ra1ahq.blog/en/archives_month:feb_2025)
- [ December 2024 ✒ 8 ](https://ra1ahq.blog/en/archives_month:dec_2024)
- [ November 2024 ✒ 2 ](https://ra1ahq.blog/en/archives_month:nov_2024)
- [ October 2024 ✒ 8 ](https://ra1ahq.blog/en/archives_month:oct_2024)
- [ September 2024 ✒ 3 ](https://ra1ahq.blog/en/archives_month:sep_2024)
- [ August 2024 ✒ 5 ](https://ra1ahq.blog/en/archives_month:aug_2024)
- [ July 2024 ✒ 9 ](https://ra1ahq.blog/en/archives_month:jul_2024)
- [ June 2024 ✒ 6 ](https://ra1ahq.blog/en/archives_month:jun_2024)
- [ May 2024 ✒ 7 ](https://ra1ahq.blog/en/archives_month:may_2024)
- [ April 2024 ✒ 5 ](https://ra1ahq.blog/en/archives_month:apr_2024)
- [ March 2024 ✒ 5 ](https://ra1ahq.blog/en/archives_month:mar_2024)
- [ February 2024 ✒ 5 ](https://ra1ahq.blog/en/archives_month:feb_2024)
- [ January 2024 ✒ 6 ](https://ra1ahq.blog/en/archives_month:jan_2024)
- [ December 2023 ✒ 7 ](https://ra1ahq.blog/en/archives_month:dec_2023)
- [ November 2023 ✒ 4 ](https://ra1ahq.blog/en/archives_month:nov_2023)
- [ October 2023 ✒ 8 ](https://ra1ahq.blog/en/archives_month:oct_2023)
- [ September 2023 ✒ 7 ](https://ra1ahq.blog/en/archives_month:sep_2023)
- [ August 2023 ✒ 4 ](https://ra1ahq.blog/en/archives_month:aug_2023)
- [ July 2023 ✒ 7 ](https://ra1ahq.blog/en/archives_month:jul_2023)
- [ June 2023 ✒ 7 ](https://ra1ahq.blog/en/archives_month:jun_2023)
- [ May 2023 ✒ 5 ](https://ra1ahq.blog/en/archives_month:may_2023)
- [ April 2023 ✒ 6 ](https://ra1ahq.blog/en/archives_month:apr_2023)
- [ March 2023 ✒ 5 ](https://ra1ahq.blog/en/archives_month:mar_2023)
- [ February 2023 ✒ 2 ](https://ra1ahq.blog/en/archives_month:feb_2023)
- [ January 2023 ✒ 5 ](https://ra1ahq.blog/en/archives_month:jan_2023)
- [ December 2022 ✒ 7 ](https://ra1ahq.blog/en/archives_month:dec_2022)
- [ November 2022 ✒ 8 ](https://ra1ahq.blog/en/archives_month:nov_2022)
- [ October 2022 ✒ 6 ](https://ra1ahq.blog/en/archives_month:oct_2022)
- [ September 2022 ✒ 9 ](https://ra1ahq.blog/en/archives_month:sep_2022)
- [ August 2022 ✒ 8 ](https://ra1ahq.blog/en/archives_month:aug_2022)
- [ July 2022 ✒ 4 ](https://ra1ahq.blog/en/archives_month:jul_2022)
- [ June 2022 ✒ 9 ](https://ra1ahq.blog/en/archives_month:jun_2022)
- [ May 2022 ✒ 7 ](https://ra1ahq.blog/en/archives_month:may_2022)
- [ April 2022 ✒ 3 ](https://ra1ahq.blog/en/archives_month:apr_2022)
- [ March 2022 ✒ 4 ](https://ra1ahq.blog/en/archives_month:mar_2022)
- [ February 2022 ✒ 6 ](https://ra1ahq.blog/en/archives_month:feb_2022)
- [ January 2022 ✒ 7 ](https://ra1ahq.blog/en/archives_month:jan_2022)
- [ December 2021 ✒ 7 ](https://ra1ahq.blog/en/archives_month:dec_2021)
- [ November 2021 ✒ 7 ](https://ra1ahq.blog/en/archives_month:nov_2021)
- [ October 2021 ✒ 7 ](https://ra1ahq.blog/en/archives_month:oct_2021)
- [ September 2021 ✒ 10 ](https://ra1ahq.blog/en/archives_month:sep_2021)
- [ August 2021 ✒ 6 ](https://ra1ahq.blog/en/archives_month:aug_2021)
- [ July 2021 ✒ 7 ](https://ra1ahq.blog/en/archives_month:jul_2021)
- [ June 2021 ✒ 7 ](https://ra1ahq.blog/en/archives_month:jun_2021)
- [ May 2021 ✒ 7 ](https://ra1ahq.blog/en/archives_month:may_2021)
- [ April 2021 ✒ 4 ](https://ra1ahq.blog/en/archives_month:apr_2021)
- [ March 2021 ✒ 4 ](https://ra1ahq.blog/en/archives_month:mar_2021)
- [ February 2021 ✒ 3 ](https://ra1ahq.blog/en/archives_month:feb_2021)
- [ January 2021 ✒ 4 ](https://ra1ahq.blog/en/archives_month:jan_2021)
- [ December 2020 ✒ 8 ](https://ra1ahq.blog/en/archives_month:dec_2020)
- [ November 2020 ✒ 2 ](https://ra1ahq.blog/en/archives_month:nov_2020)
- [ October 2020 ✒ 3 ](https://ra1ahq.blog/en/archives_month:oct_2020)
- [ September 2020 ✒ 3 ](https://ra1ahq.blog/en/archives_month:sep_2020)
- [ August 2020 ✒ 5 ](https://ra1ahq.blog/en/archives_month:aug_2020)
- [ July 2020 ✒ 5 ](https://ra1ahq.blog/en/archives_month:jul_2020)
- [ June 2020 ✒ 8 ](https://ra1ahq.blog/en/archives_month:jun_2020)
- [ May 2020 ✒ 10 ](https://ra1ahq.blog/en/archives_month:may_2020)
- [ April 2020 ✒ 4 ](https://ra1ahq.blog/en/archives_month:apr_2020)
- [ March 2020 ✒ 2 ](https://ra1ahq.blog/en/archives_month:mar_2020)
- [ January 2020 ✒ 1 ](https://ra1ahq.blog/en/archives_month:jan_2020)
- [ December 2019 ✒ 2 ](https://ra1ahq.blog/en/archives_month:dec_2019)
## Search
## Weather forecast
[На 14 дней](https://world-weather.ru/pogoda/russia/saint_petersburg/14days/)
[world-weather.ru](https://world-weather.ru/)
---
## Navigation
- Parent: [RA1AHQ](https://ra1ahq.blog/en/index.md)
- Previous: [Setting up MX Linux after a clean install: a better way](https://ra1ahq.blog/en/nastroika-mx-linux-posle-chistoi-ustanovki-uluchshennyi-sposob.md)
- Next: ["Like FM" - new radio station on 104.8 MHz](https://ra1ahq.blog/en/like-fm-novaya-radiostanciya-na-104-8-mgc.md)