MX Linux Forum

You're welcome. Now I have another thing to go check out, thanks for letting me know!

the xfce-superkey app is how we are able to have whisker menu on the super key and allow other common super+key entries to work.

Just loaded MX-21b2 on a spare system and it's great so far! Thunar seems snappier and this system has a spinning disk. Can't wait to put it on a system with an SSD.

One thing I'm seeing is that after I wake it up when it goes into power saver, after I enter my password I get a dialog box that says "Authentication is required to suspend the system."
Details are:
Action: org.freedesktop.login1.suspend
Vendor: The systemd Project (sorry, I like systemd!)

Any ideas?

Which password did you use? The root or the user pass? I fell for that in other spots, and needed the user pass instead of root.

If that happens to be the cause, you can change that back to root if you want to, in MX Tweak - Other.

@Eadwine Rose The root and user passwords are the same. I don't want to have to enter a password to allow the system to suspend.

@BasicSloth just in case I missed it, but have you tried with acpi=off on the MX-21 Beta 2?

I still haven't gotten to go back through your posts, my apologies for that, its been a busy day.

Hi - 21 is real nice - loving the new look! Evaluated a bunch of distro's before settling on MX since 19 and absolutely love it.

So recently I decided to ditch NVIDIA for AMD - just got a Radeon 6600XT but am having no luck with the driver.

Have tried to run the AMD Radeon software for Linux but seems like 21's kernel is a newer version?

This is the error I get at the end of the amdgpu-insall script.

Processing triggers for libc-bin (2.31-13) ...
Errors were encountered while processing:
amdgpu-dkms
amdgpu
E: Sub-process /usr/bin/dpkg returned an error code (1)

tekxy wrote: Sat Sep 11, 2021 5:09 am Hi - 21 is real nice - loving the new look! Evaluated a bunch of distro's before settling on MX since 19 and absolutely love it.

So recently I decided to ditch NVIDIA for AMD - just got a Radeon 6600XT but am having no luck with the driver.

Have tried to run the AMD Radeon software for Linux but seems like 21's kernel is a newer version?

This is the error I get at the end of the amdgpu-insall script.

Processing triggers for libc-bin (2.31-13) ...
Errors were encountered while processing:
amdgpu-dkms
amdgpu
E: Sub-process /usr/bin/dpkg returned an error code (1)

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/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) 
Graphics:  Device-1: AMD Navi 23 vendor: ASRock driver: N/A bus ID: 09:00.0 chip ID: 1002:73ff 
           Display: x11 server: X.Org 1.20.11 driver: none unloaded: fbdev 
           resolution: 3840x2160~88Hz 
           OpenGL: renderer: llvmpipe (LLVM 11.0.1 256 bits) v: 4.5 Mesa 21.1.5 compat-v: 3.1 
           direct render: Yes 
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
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           3: deb-src http://deb.debian.org/debian bullseye main contrib non-free
           4: deb http://deb.debian.org/debian bullseye-backports main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/home:manuelschneid3r.list 
           1: deb http://download.opensuse.org/repositories/home:/manuelschneid3r/xUbuntu_20.04/ /
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mx.debian.nz/mx/repo/ bullseye main non-free
           2: deb http://mx.debian.nz/mx/repo/ bullseye ahs
           Active apt repos in: /etc/apt/sources.list.d/sublime-text.list 
           1: deb https://download.sublimetext.com/ apt/stable/
           Active apt repos in: /etc/apt/sources.list.d/various.list 
           1: deb http://download.virtualbox.org/virtualbox/debian bullseye contrib

I don't know if this is to blame, but what is that Ubuntu repo you added? MX is not Ubuntu and adding such repos could cause conflicts.

Thanks, yeah the AMD drivers are Ubuntu and CentOs only .. I thought maybe if those sources were available to download it'd find them and add since it's mostly Debian based. I'll try removing that from source to see if it helps.

@AK-47

I found a usability/clarity issue (IMO) in the Installer if one uses the in-built partition maker instead of Gparted. I didn't notice it before because in the alpha and beta1, I either let the installer install on the whole disk (VM) or I created the partitions manually with Gparted from within the Installer.

What happened:

1. My VM is 26GB. When I used the "+" button to create the root and swap partitions, I didn't notice that the default size is measured in MB, not GB. That doesn't seem intuitive. As a result, I made a root partition of 20MB and swap of 6MB.
Only in later installation attempts did I finally notice partition size was in MB. You can't change the MB/GB unit in the installer dropdown menu nor delete the "MB" text in the text field. You will have to manually enter say, "20000", if you want to make a root partition of 20GB.

2. when I entered NEXT after configuring the root and swap partitions, the popup window warning that formatting was going to commence didn't set out the sizes of the proposed sda1 and sda2 partitions to be created. It just recapped that the formatting would make sda1 root and sda2 swap. If the popup window had listed the sizes, this would have been another chance for the user to realise they had made partitions that were way too small. There was no warning about this, and installation just commenced.

3. I entered my user name and password, and chose to create root password as well.

4. When I clicked on Next, I received a popup warning window that simply said that I had failed to set user account passwords.
5. I was puzzled, clicked on BACK button, checked and confirmed all the passwords were set. Anyway, I redid the passwords, clicked NEXT, to see if it would proceed. This time, there was no warning popup. I waited a long time and installation never concluded. I tried to abort, and the installer window never closed. I had to press the CLOSE button at the bottom of installer to close it. There was never any warning window that installation had stopped because the root partition was too small for installation of all the packages. The warning about no user passwords being set was a red herring and sent me down the wrong path checking on wrong things.


6. I tried redoing the installation but encountered the same problem because I just didn't notice the partition size unit was MB and not GB.

5. only on my 4 try did I notice it and of course it finally went through.

Suggestions:
1. Either make it possible to toggle between MB or GB, or add a line in the explanatory notes in the left pane of installer that all partition sizes are measured in MB if one uses the in-built partition maker.
2. when you click NEXT from this window, maybe have the popup window also recap the sizes of all the partitions (or at least root) to be formatted. If root is smaller than 10GB, perhaps a warning can be triggered.
3. if in the midst of installation, there is no longer any space to complete the installation of all the packages, could the popup window inform the user?