MX-21 beta 1 feedback thread

[Huckleberry Finn]

So, have you tried those mic. bars? mic boost etc.

(No PCM bar in the meantime ... )

[Buck Fankers]

I was told, to post this here. It would be easier if moderator who sent me here, would just move this post here, that was already properly formatted. Looks like copy/paste does not do this...

Title: MX21b - vulcan 32b drives - no 3d devices found

I could never get working game EverQuest TAKP emulation on MX19. Works on Manjaro. Now I'm trying with MX21. It is an old, winXP based MMOG, 32-bit.

That's why game uses 32-bit vulcan driver, so I installed this:

Code: Select all

    sudo apt install libvulkan1:i386
    sudo apt install mesa-vulkan-drivers:i386 

Manjaro equivalent:

Code: Select all

    sudo pacman -S vulkan lib32 

Then I installed wine and ran install script, just like on Manjaro. When I run game client, I get this error: (attached screenshot)

Code: Select all

No 3D Devices found

So looks like some drivers are missing. Here is my QSI:

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/vmlinuz root=/dev/sda9 
           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 System: Hewlett-Packard product: HP Compaq 6200 Pro MT PC v: N/A 
           serial: <filter> Chassis: type: 6 serial: <filter> 
           Mobo: Hewlett-Packard model: 1497 serial: <filter> UEFI: Hewlett-Packard 
           v: J01 v02.15 date: 11/10/2011 
Battery:   Device-1: hidpp_battery_0 model: Logitech Wireless Mouse B330/M330/M331 
           serial: <filter> charge: 55% (should be ignored) rechargeable: yes 
           status: Discharging 
CPU:       Topology: Quad Core model: Intel Core i7-2600 bits: 64 type: MT MCP 
           arch: Sandy Bridge family: 6 model-id: 2A (42) stepping: 7 microcode: 2F 
           L2 cache: 8192 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 54286 
           Speed: 1816 MHz min/max: 1600/3800 MHz Core speeds (MHz): 1: 1773 2: 1769 3: 1823 
           4: 1733 5: 1818 6: 1738 7: 1771 8: 1726 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           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 generic retpoline, IBPB: conditional, IBRS_FW, 
           STIBP: conditional, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: AMD Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] 
           vendor: Sapphire Limited driver: amdgpu v: kernel bus ID: 01:00.0 chip ID: 1002:699f 
           Display: x11 server: X.Org 1.20.11 driver: amdgpu,ati 
           unloaded: fbdev,modesetting,vesa resolution: 1680x1050~60Hz 
           OpenGL: 
           renderer: Radeon RX550/550 Series (POLARIS12 DRM 3.40.0 5.10.0-8-amd64 LLVM 11.0.1) 
           v: 4.6 Mesa 20.3.5 direct render: Yes 
Audio:     Device-1: Intel 6 Series/C200 Series Family High Definition Audio 
           vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
           chip ID: 8086:1c20 
           Device-2: AMD Baffin HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X] 
           vendor: Sapphire Limited driver: snd_hda_intel v: kernel bus ID: 01:00.1 
           chip ID: 1002:aae0 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Intel 82579LM Gigabit Network vendor: Hewlett-Packard driver: e1000e 
           v: kernel port: f040 bus ID: 00:19.0 chip ID: 8086:1502 
           IF: eth0 state: down mac: <filter> 
           Device-2: Intel 82540EM Gigabit Ethernet driver: e1000 v: kernel port: d000 
           bus ID: 06:00.0 chip ID: 8086:100e 
           IF: eth1 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 465.76 GiB used: 12.79 GiB (2.7%) 
           ID-1: /dev/sda vendor: Seagate model: ST500DM002-1BD142 size: 465.76 GiB block size: 
           physical: 4096 B logical: 512 B speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter> 
           rev: HP73 scheme: GPT 
Partition: ID-1: / raw size: 31.03 GiB size: 30.37 GiB (97.88%) used: 12.79 GiB (42.1%) fs: ext4 
           dev: /dev/sda9 
           ID-2: swap-1 size: 4.12 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda6 
Sensors:   System Temperatures: cpu: 36.0 C mobo: N/A gpu: amdgpu temp: 46 C 
           Fan Speeds (RPM): N/A gpu: amdgpu fan: 1081 
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
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ bullseye main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 243 Uptime: 14m Memory: 7.73 GiB used: 1.21 GiB (15.7%) 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 

When I ran vulkaninfo, I see these three errors in the terminal:

Code: Select all

    $ vulkaninfo >> vulkan.txt
    ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so: wrong ELF class: ELFCLASS32
    ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_lvp.so: wrong ELF class: ELFCLASS32
    ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so: wrong ELF class: ELFCLASS32
    WARNING: lavapipe is not a conformant vulkan implementation, testing use only. 

Here is complete, huge output, in case it is of any help, I didn't see any errors in it:
Edit, can't post, msg has too many characters:

Code: Select all

    Your message contains 68303 characters.
    The maximum number of allowed characters is 60000. 

I'm attaching it to the post as 'vulkan.txt'

Looks like someone has similar error:
https://www.linuxquestions.org/question ... 175686371/

As solutions was posted this:

Code: Select all

I downgraded to mesa 20.2.3 and that fixed it.

More info:

Code: Select all

$ glxinfo | grep OpenGL
OpenGL vendor string: AMD
OpenGL renderer string: Radeon RX550/550 Series (POLARIS12, DRM 3.40.0, 5.10.0-8-amd64, LLVM 11.0.1)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 20.3.5
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.6 (Compatibility Profile) Mesa 20.3.5
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 20.3.5
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:

Should I do this?
If yes, how exactly and how would I lock this version: 20.2.3 (should I?) so it does not get updated after next system update.

If I get this game to work on MX21, I will use this installation just for this game, and for nothing else

More info: vulkaninfo --summary

Code: Select all

$ vulkaninfo --summary
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so: wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_lvp.so: wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so: wrong ELF class: ELFCLASS32
WARNING: lavapipe is not a conformant vulkan implementation, testing use only.
==========
VULKANINFO
==========

Vulkan Instance Version: 1.2.162


Instance Extensions: count = 18
-------------------------------
VK_EXT_acquire_xlib_display            : extension revision 1
VK_EXT_debug_report                    : extension revision 8
VK_EXT_debug_utils                     : extension revision 2
VK_EXT_direct_mode_display             : extension revision 1
VK_EXT_display_surface_counter         : extension revision 1
VK_KHR_device_group_creation           : extension revision 1
VK_KHR_display                         : extension revision 23
VK_KHR_external_fence_capabilities     : extension revision 1
VK_KHR_external_memory_capabilities    : extension revision 1
VK_KHR_external_semaphore_capabilities : extension revision 1
VK_KHR_get_display_properties2         : extension revision 1
VK_KHR_get_physical_device_properties2 : extension revision 1
VK_KHR_get_surface_capabilities2       : extension revision 1
VK_KHR_surface                         : extension revision 25
VK_KHR_surface_protected_capabilities  : extension revision 1
VK_KHR_wayland_surface                 : extension revision 6
VK_KHR_xcb_surface                     : extension revision 6
VK_KHR_xlib_surface                    : extension revision 6

Instance Layers: count = 2
--------------------------
VK_LAYER_MESA_device_select Linux device selection layer 1.2.73  version 1
VK_LAYER_MESA_overlay       Mesa Overlay layer           1.1.73  version 1

Devices:
========
GPU0:
	apiVersion         = 4202641 (1.2.145)
	driverVersion      = 83898373 (0x5003005)
	vendorID           = 0x1002
	deviceID           = 0x699f
	deviceType         = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
	deviceName         = AMD RADV POLARIS12 (ACO)
	driverID           = DRIVER_ID_MESA_RADV
	driverName         = radv
	driverInfo         = Mesa 20.3.5 (ACO)
	conformanceVersion = 1.2.3.0
GPU1:
	apiVersion         = 4194306 (1.0.2)
	driverVersion      = 1 (0x0001)
	vendorID           = 0x10005
	deviceID           = 0x0000
	deviceType         = PHYSICAL_DEVICE_TYPE_CPU
	deviceName         = llvmpipe (LLVM 11.0.1, 256 bits)
	driverID           = DRIVER_ID_MESA_LLVMPIPE
	driverName         = llvmpipe
	driverInfo         = Mesa 20.3.5 (LLVM 11.0.1)
	conformanceVersion = 1.0.0.0

[Andrii]

@SwampRabbit

@dolphin_oracle


After installing alsa-topology-conf and alsa-ucm-conf and rebooting the system, the digital microphone worked and the configuration of the sound mixer was completely changed. Sorry for the delay, but I had to install MXLinux again for testing.

[SwampRabbit]

After installing alsa-topology-conf and alsa-ucm-conf and rebooting the system, the digital microphone worked and the configuration of the sound mixer was completely changed.

Thank for narrowing that down, looks like we should start including those in the ISO maybe.

[Andrii]

@SwampRabbit
@dolphin_oracle

You also need to add firmware-sof-signed_1.7-1 to the ISO image.
Thanks for the help.

[dolphin_oracle]

@SwampRabbit
@dolphin_oracle

You also need to add firmware-sof-signed_1.7-1 to the ISO image.
Thanks for the help.

thanks for the troubleshooting!

[JayM]

1. I installed Mirage picture viewer from the Stable Repo and told Thunar to open image files with mirage as the default. Whenever I open pictures mirage always opens in a larger resolution than my 1920x1080 monitor (2376x1724 per the miragerc file in ~/.config/mirage) causing the upper-right control buttons (minimize, maximize, close) to be off-screen. I deleted the ~/.config/mirage directory and let mirage recreate it, I changed my GTK theme to Arc Dark, I disabled CSD in MX Tweak, i adjusted the size of apps to trigger smart placement in Window Manager Tweaks to no avail. There's nothing in mirage's preferences to tell it to open maximized so it always opens in a larger than life window. It didn't do this in MX-19.4 AHS. Buster has version 0.9.5.2, Bullseye and Sid have 0.11.1. (This may be just a user training issue: telling apps to remember their window sizes, or else I could use devilspie as a work-around but I'd rather not have to: besides, the GUI interface for devilspie that made it way easier to configure in MX-19 is missing from the MX-21 repos.)

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) 
Machine:   Type: Desktop Mobo: ASUSTeK model: TUF B450M-PRO GAMING v: Rev X.0x serial: <filter> 
           UEFI: American Megatrends v: 3202 date: 06/16/2021 
CPU:       Topology: 8-Core model: AMD Ryzen 7 3700X bits: 64 type: MT MCP arch: Zen 
           family: 17 (23) model-id: 71 (113) stepping: N/A microcode: 8701021 
           L2 cache: 4096 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
           bogomips: 114985 
           Speed: 2361 MHz min/max: 2200/3600 MHz boost: enabled Core speeds (MHz): 1: 2361 
           2: 2227 3: 2154 4: 2112 5: 2197 6: 2151 7: 2177 8: 2196 9: 2168 10: 2119 11: 2187 
           12: 2175 13: 2170 14: 2201 15: 2307 16: 2300 
           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: conditional, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: AMD Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] 
           driver: amdgpu v: kernel bus ID: 07:00.0 chip ID: 1002:67ef 
           Display: x11 server: X.Org 1.20.11 driver: amdgpu,ati 
           unloaded: fbdev,modesetting,vesa tty: N/A 
           OpenGL: 
           renderer: Radeon RX 560 Series (POLARIS11 DRM 3.40.0 5.10.0-8-amd64 LLVM 11.0.1) 
           v: 4.6 Mesa 20.3.5 direct render: Yes 
Audio:     Device-1: AMD Baffin HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X] 
           driver: snd_hda_intel v: kernel bus ID: 07:00.1 chip ID: 1002:aae0 
           Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel 
           v: kernel bus ID: 09:00.4 chip ID: 1022:1487 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: ASUSTeK PRIME B450M-A driver: r8169 v: kernel port: f000 bus ID: 04:00.0 
           chip ID: 10ec:8168 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 4.20 TiB used: 85.15 GiB (2.0%) 
           ID-1: /dev/nvme0n1 vendor: PNY model: CS3030 500GB SSD size: 465.76 GiB block size: 
           physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter> 
           rev: CS303321 scheme: GPT 
           ID-2: /dev/sda vendor: Gigabyte model: GP-GSTFS31120GNTD size: 111.79 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 61.3 scheme: GPT 
           ID-3: /dev/sdb vendor: Seagate model: ST4000DM004-2CV104 size: 3.64 TiB block size: 
           physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 5425 rpm serial: <filter> 
           rev: 0001 
Partition: ID-1: / raw size: 105.37 GiB size: 103.16 GiB (97.90%) used: 85.05 GiB (82.4%) 
           fs: ext4 dev: /dev/dm-0 
           ID-2: /boot raw size: 512.0 MiB size: 487.2 MiB (95.16%) used: 104.4 MiB (21.4%) 
           fs: ext4 dev: /dev/sda2 
           ID-3: swap-1 size: 5.61 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/dm-1 
Sensors:   System Temperatures: cpu: 46.4 C mobo: N/A gpu: amdgpu temp: 48 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
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/google-earth-pro.list 
           1: deb [arch=amd64] http://dl.google.com/linux/earth/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/mono-official-stable.list 
           1: deb https://download.mono-project.com/repo/debian stable-buster main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ bullseye main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 347 Uptime: 18m Memory: 31.33 GiB used: 2.01 GiB (6.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 

2. I installed VirtualBox from MXPI Pop Apps/Misc and even VirtualBox Manager's icon becomes the generic "gear" icon in Docklike Taskbar. When VB Manager first starts launching I see the same icon that's in the Whisker menu for a second, then when the app opens it reverts to the gear. Right-clicking on the gear doesn't show the normal context menu either, just the name of the app with an X to close it. It works with some apps as expected, doesn't work properly with many others. I suggest you rethink deploying this buggy program on the release version of MX-21 and go back to traditional panel launchers and window buttons for now until Docklike is fixed. Otherwise there will be a LOT of help requests and complaints about it in the forum. Maybe you can change to Docklike again later in a dot release of MX-21 once Docklike's working as expected. (I did post this on the current maintainer's github page. That's another thing: the original author seems to have jumped ship earlier this year and someone else is trying to pick up where he left off, but he seems to be relatively new. IMO that doesn't bode well for the stability of this utility, particularly on production systems.)

Edit: I see that @SwampRabbit posted this to the new dev on github already and it's supposed to have been fixed since then, but I don't know if MX-21's version has been repackaged such that it contains the commit that fixed it. If so, it's still not working.

[chrispop99]

I'm posting this here on the basis that it might need to be mentioned as a known issue for future releases.

I've tested the problem I reported earlier, with resumption after screen blanking failing, on three machines of different makes/models. They all show the same problem, and they all have Intel Mobile GM965/GL960 integrated graphics. It does not happen with either KDE or Fluxbox, only Xfce.

Unless display power management is turned off completely in System Settings, after the screen blanks, pressing a key or moving the mouse will not restore power to the screen. The user is essentially locked out. Recovery from this situation is possible without a forced shutdown by pressing Ctrl-Alt-F1, followed by Ctrl-Alt-F7.

It is possible to prevent this situation by using MX Tweak>Other tab to set the driver to Intel, then rebooting.

Chris

[j.kemp]

@j.kemp is it possible for you to try with an "untouched" MX 21 (other than just updating). Before & After Nvidia installation.

(You have many repos added )

I added those repos after installing. It was not updated from 19.4. So I did make another fresh install, and it froze even before I could get the Nvidia driver installed. Once I did get it installed, I could not change the resolution beyond 1024x768*. The Nvidia installer from mx-tools installed the 460 driver. I had to remove to get any decent resolution. System still freezes. I renamed a folder in Thunar, and it will happen. The mouse moves around but can't log out, shutdown, or switch to TTY terminal. Only hard booting gets me out. Static, toram, nothing stops it from happening.

[SwampRabbit]

2. I installed VirtualBox from MXPI Pop Apps/Misc and even VirtualBox Manager's icon becomes the generic "gear" icon in Docklike Taskbar. When VB Manager first starts launching I see the same icon that's in the Whisker menu for a second, then when the app opens it reverts to the gear. Right-clicking on the gear doesn't show the normal context menu either, just the name of the app with an X to close it. It works with some apps as expected, doesn't work properly with many others. I suggest you rethink deploying this buggy program on the release version of MX-21 and go back to traditional panel launchers and window buttons for now until Docklike is fixed. Otherwise there will be a LOT of help requests and complaints about it in the forum. Maybe you can change to Docklike again later in a dot release of MX-21 once Docklike's working as expected. (I did post this on the current maintainer's github page. That's another thing: the original author seems to have jumped ship earlier this year and someone else is trying to pick up where he left off, but he seems to be relatively new. IMO that doesn't bode well for the stability of this utility, particularly on production systems.)

Edit: I see that @SwampRabbit posted this to the new dev on github already and it's supposed to have been fixed since then, but I don't know if MX-21's version has been repackaged such that it contains the commit that fixed it. If so, it's still not working.

I have not packaged the updated version because I was working on Xfce updates and prepping for MX-21 AHS.

As far as the fork we are using, the current developer is the reason it is as good as it is, and he is the reason it made it into the official Xfce GitLab. So I think those comments are a little harsh assumptions.

I will package the latest version probably in the next day or two and hopefully it meets everyone’s demands before final release.