See my edit above ..VCR58 wrote: Thu Aug 12, 2021 4:52 pmI got this as a response.fehlix wrote: Thu Aug 12, 2021 4:42 pm Try this as normal user:and reboot.Code: Select all
sudo sed -i '/SystemAccount=/s/false/true/' /var/lib/AccountsService/users/$(id -nu 998)
Code: Select all
sed: can't read /var/lib/AccountsService/users/nextpvr: No such file or directory
MX-21 beta 1 feedback thread
Re: MX-21 beta 1 feedback thread
Re: MX-21 beta 1 feedback thread
Problem: Boot flag for Windows 10 is moved to MX Linux 21.
I think that with MX21 the same problem as with MX18 is introduced again: The boot flag of a Windows 10 ntfs partition is moved by the MX21 installer to the partition with the MX21 / directory, when the partition for / , where /boot is located, is at the same sda disk.
I have an old laptop HP Pavilion dv9000. Windows 10 is at the first partition sda1 and MX21 is installed over MX19 at the second partition which is known as sda4.
A PBR is installed at sda4 (root partition). No MBR installed.
So root ( / ) is at the second partition, which is known as sda4 and the home directory is at sdb2.
Installation went fine, but the Windows boot loader (MBR) cannot find Windows 10 anymore.
The reason for this is that MX21 sets the boot flag at the / partition, so at sda4.
Windows 10 is now missing the boot flag at sda1 and The Windows 10 boot process decides to boot another system, which happens to be MX21.
The solution is very simple, using Gparted, Manage flags and set the flag at sda1 again. MX21 does not need the boot flag at the / partition or at the partition where /boot is located.
I used the EasyBCD tool to make a second entry for Linux in the bcd descriptor of Windows to point to the sda4 partition.
Windows 10 lets you choose to boot Windows 10 or Linux.
The advantage of this configuration is that updates for Windows 10 will not fail because the boot information would be missing after installing Linux.
I think that with MX21 the same problem as with MX18 is introduced again: The boot flag of a Windows 10 ntfs partition is moved by the MX21 installer to the partition with the MX21 / directory, when the partition for / , where /boot is located, is at the same sda disk.
I have an old laptop HP Pavilion dv9000. Windows 10 is at the first partition sda1 and MX21 is installed over MX19 at the second partition which is known as sda4.
A PBR is installed at sda4 (root partition). No MBR installed.
So root ( / ) is at the second partition, which is known as sda4 and the home directory is at sdb2.
Installation went fine, but the Windows boot loader (MBR) cannot find Windows 10 anymore.
The reason for this is that MX21 sets the boot flag at the / partition, so at sda4.
Windows 10 is now missing the boot flag at sda1 and The Windows 10 boot process decides to boot another system, which happens to be MX21.
The solution is very simple, using Gparted, Manage flags and set the flag at sda1 again. MX21 does not need the boot flag at the / partition or at the partition where /boot is located.
I used the EasyBCD tool to make a second entry for Linux in the bcd descriptor of Windows to point to the sda4 partition.
Windows 10 lets you choose to boot Windows 10 or Linux.
The advantage of this configuration is that updates for Windows 10 will not fail because the boot information would be missing after installing Linux.
Re: MX-21 beta 1 feedback thread
I finally got around to downloading the beta. I installed it to a USB stick and upgraded the 77 available packages, then remastered and rebooted the USB. All went well with the minor visual changes I made. So far I have not had any issues.
Forum Rules
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
Re: MX-21 beta 1 feedback thread
The command you suggested failed as shown in my post and a reboot did not help.fehlix wrote: Thu Aug 12, 2021 4:53 pmSee my edit above ..VCR58 wrote: Thu Aug 12, 2021 4:52 pmI got this as a response.fehlix wrote: Thu Aug 12, 2021 4:42 pm Try this as normal user:and reboot.Code: Select all
sudo sed -i '/SystemAccount=/s/false/true/' /var/lib/AccountsService/users/$(id -nu 998)
Code: Select all
sed: can't read /var/lib/AccountsService/users/nextpvr: No such file or directory
Re: MX-21 beta 1 feedback thread
Seen this:VCR58 wrote: Thu Aug 12, 2021 5:09 pmThe command you suggested failed as shown in my post and a reboot did not help.fehlix wrote: Thu Aug 12, 2021 4:53 pmSee my edit above ..VCR58 wrote: Thu Aug 12, 2021 4:52 pm
I got this as a response.Code: Select all
sed: can't read /var/lib/AccountsService/users/nextpvr: No such file or directory
fehlix wrote: Thu Aug 12, 2021 4:42 pm +++EDIT++ If the file /var/lib/AccountsService/users/$(id -nu 998)
was not yet created, b/c never logged in, do just create it:Code: Select all
printf "[User]\nSystemAccount=true\n" | sudo tee /var/lib/AccountsService/users/$(id -nu 998) sudo chmod 600 /var/lib/AccountsService/users/$(id -nu 998)
Re: MX-21 beta 1 feedback thread
Ok thanks, that fixed it. I didn't see the edit at first but it's there now.fehlix wrote: Thu Aug 12, 2021 5:23 pmSeen this:fehlix wrote: Thu Aug 12, 2021 4:42 pm +++EDIT++ If the file /var/lib/AccountsService/users/$(id -nu 998)
was not yet created, b/c never logged in, do just create it:Code: Select all
printf "[User]\nSystemAccount=true\n" | sudo tee /var/lib/AccountsService/users/$(id -nu 998) sudo chmod 600 /var/lib/AccountsService/users/$(id -nu 998)
Re: MX-21 beta 1 feedback thread
The Beta is so stable here that I've been running it as my working system for the past week with no issues. My applications are all installed and configured and working smoothly and I've set up and tested my backup routines. Unless something unexpected happens, I will stick with this until final. I will test the RC live for any new problems.
Here's the QSI and details of my installation routine, which may be of interest.
Here's the QSI and details of my installation routine, which may be of interest.
Code: Select all
System: Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A
parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-amd64
root=UUID=<filter> ro quiet splash
Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-21_beta1_x64 Wildflower July 27 2021 base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Desktop Mobo: ASRock model: FM2A88X-ITX+ serial: <filter>
UEFI: American Megatrends v: P2.10 date: 01/17/2014
Battery: Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard K270 serial: <filter>
charge: 100% (should be ignored) rechargeable: yes status: Discharging
Device-2: hidpp_battery_1 model: Logitech Wireless Mouse M185 serial: <filter>
charge: 55% (should be ignored) rechargeable: yes status: Discharging
CPU: Topology: Quad Core model: AMD A8-6500 APU with Radeon HD Graphics bits: 64 type: MCP
arch: Piledriver family: 15 (21) model-id: 13 (19) stepping: 1 microcode: 6001119
L2 cache: 2048 KiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 27951
Speed: 2182 MHz min/max: 1700/3500 MHz boost: enabled Core speeds (MHz): 1: 2231
2: 2096 3: 2965 4: 2375
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full AMD retpoline, STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: AMD Richland [Radeon HD 8570D] vendor: ASRock driver: radeon v: kernel
bus ID: 00:01.0 chip ID: 1002:990e
Display: x11 server: X.Org 1.20.11 driver: ati,radeon
unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: AMD ARUBA (DRM 2.50.0 / 5.10.0-8-amd64 LLVM 11.0.1)
v: 4.3 Mesa 20.3.5 compat-v: 3.1 direct render: Yes
Audio: Device-1: AMD Trinity HDMI Audio vendor: ASRock driver: snd_hda_intel v: kernel
bus ID: 00:01.1 chip ID: 1002:9902
Device-2: AMD FCH Azalia vendor: ASRock driver: snd_hda_intel v: kernel
bus ID: 00:14.2 chip ID: 1022:780d
Sound Server: ALSA v: k5.10.0-8-amd64
Network: Device-1: Qualcomm Atheros AR9462 Wireless Network Adapter vendor: AzureWave
driver: ath9k v: kernel port: f100 bus ID: 01:00.0 chip ID: 168c:0034
IF: wlan0 state: down mac: <filter>
Device-2: Qualcomm Atheros QCA8171 Gigabit Ethernet vendor: ASRock driver: alx
v: kernel port: e000 bus ID: 03:00.0 chip ID: 1969:10a1
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 2.05 TiB used: 177.55 GiB (8.5%)
ID-1: /dev/sda vendor: Samsung model: SSD 870 EVO 250GB size: 232.89 GiB block size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 1B6Q scheme: GPT
ID-2: /dev/sdb vendor: Seagate model: ST1000DM005 HD103SJ size: 931.51 GiB
block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s rotation: 7200 rpm
serial: <filter> rev: 00E5 scheme: MBR
ID-3: /dev/sdc vendor: Toshiba model: HDWD110 size: 931.51 GiB block size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter>
rev: A8J0 scheme: MBR
Partition: ID-1: / raw size: 30.00 GiB size: 29.36 GiB (97.87%) used: 8.78 GiB (29.9%) fs: ext4
dev: /dev/sda4
ID-2: swap-1 size: 7.81 GiB used: 5.5 MiB (0.1%) fs: swap swappiness: 15 (default 60)
cache pressure: 100 (default) dev: /dev/sdb11
Sensors: System Temperatures: cpu: 14.1 C mobo: N/A gpu: radeon temp: 12 C
Fan Speeds (RPM): N/A
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bullseye main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/dropbox.list
1: deb [arch=i386,amd64] http://linux.dropbox.com/debian sid main
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bullseye main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Active apt repos in: /etc/apt/sources.list.d/vivaldi.list
1: deb http://repo.vivaldi.com/stable/deb/ stable main
Info: Processes: 273 Uptime: 5d 2h 12m Memory: 6.71 GiB used: 2.38 GiB (35.4%)
Init: SysVinit v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10
Shell: quick-system-in running in: quick-system-in inxi: 3.0.36
You do not have the required permissions to view the files attached to this post.
Gigabyte B550I Aorus Pro AX, Ryzen 5 5600G, 16GB, 250GB Samsung SSD (GPT), 2x1TB HDD (MBR), MX-21-AHS
Lenovo Thinkpad X220, dual-core i5, 4MB, 120GB Samsung SSD (GPT), MX-21
- paddys-hill
- Posts: 21
- Joined: Sat Jul 31, 2021 12:45 am
Re: MX-21 beta 1 feedback thread
To the user manual writer.
On page 43 (of the MX 19 version) there is a link to the Red Hat Manual for configuring network printers. That link is no longer correct. The new link is
https://access.redhat.com/documentation ... figuration
cheers
On page 43 (of the MX 19 version) there is a link to the Red Hat Manual for configuring network printers. That link is no longer correct. The new link is
https://access.redhat.com/documentation ... figuration
cheers
Paddys-Hill Co-op co-ordinator & sysadmin
Front end: Acer Aspire A315-21G (AMD A9-9420 RADEON R5) running 5.10.0-5mx-amd64
Co-op VPN Server: HP 666161-B21 ProLiant BL460c Gen8 E5-2620 (in rebuild)
+ 6 other servers
Front end: Acer Aspire A315-21G (AMD A9-9420 RADEON R5) running 5.10.0-5mx-amd64
Co-op VPN Server: HP 666161-B21 ProLiant BL460c Gen8 E5-2620 (in rebuild)
+ 6 other servers
- PhantomTramp
- Posts: 100
- Joined: Tue Jul 10, 2007 12:53 pm
Re: MX-21 beta 1 feedback thread
I ran into the problem where Windows 10 would not update. After wasting a lot of time searching (that's a half hour I will never get back), I found that Windows would not update with a default dual boot install of MX. Microsoft's website was correct, because when I gave MX the whole drive, I did not experience the problem any more.The advantage of this configuration is that updates for Windows 10 will not fail because the boot information would be missing after installing Linux.
I am very satisfied with my laptop now.
The Tramp

- entropyfoe
- Posts: 615
- Joined: Thu Apr 19, 2007 11:42 am
Re: MX-21 beta 1 feedback thread
I have to agree with Gaer Boy. This beta1 is running smoothly, for days on end, no lockups or crashes.
Using as the daily driver like my MX 19.4 on this same hardware.
I had some small issues with getting firefox working as I like it, but the recent upgrade to 91 has solved that.
As others have noted, keep the beta up to date. Though the pace of upgrades has slowed a bit the past couple of days, earlier they were often and large.
I use synapic, every day, I accept all, so I am up to date.
In addition to testing for up time, I also like a few reboots after lots of upgrades, to get everything configured and make sure all things are still working and compatible.
Like Gaer Boy, here is my system
And a fair summary of configuration:
Using as the daily driver like my MX 19.4 on this same hardware.
I had some small issues with getting firefox working as I like it, but the recent upgrade to 91 has solved that.
As others have noted, keep the beta up to date. Though the pace of upgrades has slowed a bit the past couple of days, earlier they were often and large.
I use synapic, every day, I accept all, so I am up to date.
In addition to testing for up time, I also like a few reboots after lots of upgrades, to get everything configured and make sure all things are still working and compatible.
Like Gaer Boy, here is my system
Code: Select all
System: Host: <filter> Kernel: 5.10.0-5mx-amd64 x86_64 bits: 64 compiler: N/A
parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-5mx-amd64
root=UUID=<filter> ro quiet splash
Desktop: Xfce 4.14.2 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-19.4_x64 patito feo October 15 2019 base: Debian GNU/Linux 10 (buster)
Machine: Type: Desktop Mobo: ASUSTeK model: PRIME X470-PRO v: Rev X.0x serial: <filter>
UEFI [Legacy]: American Megatrends v: 5204 date: 07/29/2019
CPU: Topology: 6-Core model: AMD Ryzen 5 3600X bits: 64 type: MT MCP arch: Zen
family: 17 (23) model-id: 71 (113) stepping: N/A microcode: 8701013
L2 cache: 3072 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 91028
Speed: 3315 MHz min/max: 2200/3800 MHz boost: enabled Core speeds (MHz): 1: 2195
2: 2195 3: 2196 4: 2196 5: 2196 6: 2196 7: 2194 8: 2195 9: 2195 10: 2195 11: 2196
12: 2195
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2
mitigation: Full AMD retpoline, IBPB: conditional, STIBP: always-on, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: NVIDIA GK208 [GeForce GT 710B] vendor: Micro-Star MSI GK208B driver: nvidia
v: 455.45.01 bus ID: 09:00.0 chip ID: 10de:128b
Display: x11 server: X.Org 1.20.4 driver: nvidia
unloaded: fbdev,modesetting,nouveau,vesa alternate: nv resolution: 1920x1080~60Hz
OpenGL: renderer: GeForce GT 710/PCIe/SSE2 v: 4.6.0 NVIDIA 455.45.01
direct render: Yes
Audio: Device-1: NVIDIA GK208 HDMI/DP Audio vendor: Micro-Star MSI driver: snd_hda_intel
v: kernel bus ID: 09:00.1 chip ID: 10de:0e0f
Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel bus ID: 0b:00.4 chip ID: 1022:1487
Sound Server: ALSA v: k5.10.0-5mx-amd64
Network: Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel port: e000
bus ID: 07:00.0 chip ID: 8086:1539
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 1.14 TiB used: 540.69 GiB (46.4%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 250GB size: 232.89 GiB
block size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter>
rev: 2B2QEXM7 scheme: MBR
ID-2: /dev/sda vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB block size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 1B6Q scheme: MBR
Partition: ID-1: / raw size: 24.41 GiB size: 23.91 GiB (97.92%) used: 9.86 GiB (41.2%) fs: ext4
dev: /dev/nvme0n1p1
ID-2: /home raw size: 87.89 GiB size: 86.01 GiB (97.86%) used: 238.1 MiB (0.3%)
fs: ext4 dev: /dev/nvme0n1p3
ID-3: swap-1 size: 32.23 GiB used: 0 KiB (0.0%) fs: swap swappiness: 1 (default 60)
cache pressure: 100 (default) dev: /dev/nvme0n1p2
Sensors: System Temperatures: cpu: 46.5 C mobo: N/A gpu: nvidia temp: 51 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 50%
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian/ buster-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian/ buster main contrib non-free
2: deb http://deb.debian.org/debian-security/ buster/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mxrepo.com/mx/repo/ buster main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 305 Uptime: 1d 20h 33m Memory: 31.34 GiB used: 2.90 GiB (9.3%)
Init: SysVinit v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8
Shell: quick-system-in running in: quick-system-in inxi: 3.0.36
Code: Select all
Re: 10 Things to do after installing MX
#6 Post by entropyfoe » 01 Aug 2019 15:19
1. Enable my data disk in the disk manager
2. Change my wall paper
3. Fire up synaptic and load about 30 programs (adds to maybe 160 packages with all dependencies) Such as audacity, k3b, ksnip, bleachbit, ripperx, handbrake, scid, stockfish, eboard, jerry, espeak....I really should automate this with aptik !
4. Run synaptic to get all updates
5.Widen the panel and change the clock so it shows seconds
6. Install the NVidia driver with the MX Package Installer
7. Switch conky to the modified antiX conky
8. Set up a desktop short cut to the data drive
9. Run bleachbit to clear all the post install stuff out-often hundreds of MB
10. Reboot and test stability after all the up dates
11. Configure Firefox, set home page to duckduckgo, set downloads to go to a folder on the data drive, import bookmarks, add noscript
12. Disable sudo -MX Tweak > Other tab > radial button at the bottom labeled accordingly
13. set swappiness: =1
MX 23.5 on Asus PRIME X470-PRO
AMD Ryzen 3600X (12 threads @ 3.8 GHz)
32 Gig DDR4 3600 (Crucial CL 16)
Nvidia GeForce GT 710
Samsung 970 NVMe nvme0n1 P1-3=MX-23.5, P4=testing
Samsung 980 NVMe =1TB Data, plus 2TB WD =backups
on-board ethernet & sound
AMD Ryzen 3600X (12 threads @ 3.8 GHz)
32 Gig DDR4 3600 (Crucial CL 16)
Nvidia GeForce GT 710
Samsung 970 NVMe nvme0n1 P1-3=MX-23.5, P4=testing
Samsung 980 NVMe =1TB Data, plus 2TB WD =backups
on-board ethernet & sound