MX-21 "ahs" (Xfce) RC3 feedback

[davemx]

we have one report that intel graphics users may have some success switching to the "intel" xorg driver rather than using the default modesetting driver. there is an option in mx-tweak for that. we also have at least one report that it doesn't help, so YMMV.

I did try that with RC1 but it made no difference.

[spsf64]

@spsf64 is this samba issue localized to MX-21 AHS?
I don’t recall anyone mentioning this for standard MX-21.

I don’t believe that Warpinator (even though I package it for MX) is proper to be included in AHS. AHS is meant to be on par with standard MX-21 Xfce EXCEPT ONLY for the hardware and graphical packages. Also, Warpinator is not cross platform, it is limited to Linux and an unofficial Android app. Samba/SMB is a much more wide spread standard and provides much more interoperability.

I’m not understanding the LibreOffice template thing, can you expand on it more in a separate thread? If it’s some MX default you’re recommending, it should not be specific to AHS either, again not the point of AHS.

Hi @SwampRabbit , thanks for replying
I just tested the samba thing with Std MX21 and have same results, however as I said, it is in live Mode, not installed, but it used to work fine with 19.4 with old samba-system-config (not sure of the name); did you try to create new files the way I mentioned? I agree about warpinator, not on par with samba...

About the "Templates" I will try to open a new thread by the weekend, don´t have too much time now.
If you throw a "blank" .ods, odt, etc... file into "templates" folder, it will be displayed in the "create new document" menu; I will leave a photo so you can see what I mean...
Thanks again!

[SwampRabbit]

I see what you mean about the templates, I think I understand. Should be pretty easy to do, but probably won’t show up unless you update prior to installing as those defaults would be created at install so an update to MX defaults wouldn’t be on the original ISO since it would be added after the fact. If that makes sense.

What are the permissions on the public folder and that sub folder? Are they set recursively?

[Paul..]

Fresh install to metal...testing against War Thunder game (good for stressing graphics)...tried two different kernels.

EDIT: This game runs fine on stock MX-21 with
- Kernel: 5.10.0-9-amd64 x86_64
- Graphics renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.40.0 5.10.0-9-amd64 LLVM 11.0.1)
v: 4.6 Mesa 20.3.5 direct render: Yes

So it looks like there may be a problem with Mesa...


First Test
- Kernel: 5.14.0-3mx-amd64 x86_64

- Graphics: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.42.0 5.14.0-3mx-amd64 LLVM 12.0.1) v: 4.6
Mesa 21.2.3 direct render: Yes

Resulted in consistent and immediate crash of War Thunder..."vulkan error waiting for GPU - timeout"

Code: Select all

System:    Host: <filter> Kernel: 5.14.0-3mx-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.14.0-3mx-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_ahs_rc3_x64 Wildflower October 25  2021 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop Mobo: ASUSTeK model: PRIME X570-PRO v: Rev X.0x serial: <filter> 
           UEFI: American Megatrends v: 2606 date: 08/13/2020 
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: 114980 
           Speed: 2195 MHz min/max: 2200/3600 MHz boost: enabled Core speeds (MHz): 1: 2196 
           2: 2196 3: 2191 4: 2202 5: 1862 6: 1863 7: 2785 8: 2196 9: 2195 10: 2196 11: 2200 
           12: 2195 13: 2670 14: 2196 15: 2195 16: 2196 
           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 Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] vendor: ASUSTeK 
           driver: amdgpu v: kernel bus ID: 09:00.0 chip ID: 1002:731f 
           Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati 
           unloaded: fbdev,modesetting,radeon,vesa resolution: 2560x1440~144Hz 
           OpenGL: 
           renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.42.0 5.14.0-3mx-amd64 LLVM 12.0.1) 
           v: 4.6 Mesa 21.2.3 direct render: Yes 
Audio:     Device-1: AMD Navi 10 HDMI Audio driver: snd_hda_intel v: kernel bus ID: 09:00.1 
           chip ID: 1002:ab38 
           Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel 
           v: kernel bus ID: 0b:00.4 chip ID: 1022:1487 
           Device-3: Logitech Logitech Webcam C925e type: USB driver: snd-usb-audio,uvcvideo 
           bus ID: 1-2:3 chip ID: 046d:085b serial: <filter> 
           Sound Server: ALSA v: k5.14.0-3mx-amd64 
Network:   Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel port: f000 
           bus ID: 03:00.0 chip ID: 8086:1539 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 975.96 GiB used: 252.52 GiB (25.9%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 4B6Q scheme: GPT 
           ID-2: /dev/sdb vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 1B6Q scheme: GPT 
           ID-3: /dev/sdc type: USB vendor: SanDisk model: Cruzer Blade size: 14.56 GiB 
           block size: physical: 512 B logical: 512 B serial: <filter> rev: 1.27 scheme: MBR 
           ID-4: /dev/sdd type: USB vendor: Samsung model: Flash Drive FIT size: 29.88 GiB 
           block size: physical: 512 B logical: 512 B serial: <filter> rev: 1100 scheme: MBR 
Partition: ID-1: / raw size: 218.97 GiB size: 214.48 GiB (97.95%) used: 7.02 GiB (3.3%) fs: ext4 
           dev: /dev/sda3 
           ID-2: swap-1 size: 16.60 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda4 
Sensors:   System Temperatures: cpu: 53.5 C mobo: N/A gpu: amdgpu temp: 56 C 
           Fan Speeds (RPM): N/A gpu: amdgpu fan: 0 
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-chrome.list 
           1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye main non-free
           2: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye ahs
Info:      Processes: 368 Uptime: 34m Memory: 15.54 GiB used: 1.46 GiB (9.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 

Second Test
- Kernel: 5.10.0-9-amd64 x86_64

- Graphics renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.40.0 5.10.0-9-amd64 LLVM 12.0.1)
v: 4.6 Mesa 21.2.3 direct render: Yes

Note: Earlier version of AMD driver was loaded...but same version of Mesa...Same result with War Thunder crash "vulkan error waiting for GPU - timeout"

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-9-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-9-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_ahs_rc3_x64 Wildflower October 25  2021 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop Mobo: ASUSTeK model: PRIME X570-PRO v: Rev X.0x serial: <filter> 
           UEFI: American Megatrends v: 2606 date: 08/13/2020 
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: 114978 
           Speed: 2040 MHz min/max: 2200/3600 MHz boost: enabled Core speeds (MHz): 1: 1892 
           2: 1984 3: 2539 4: 1868 5: 2196 6: 2194 7: 2196 8: 2196 9: 2739 10: 2007 11: 2196 
           12: 2196 13: 2195 14: 2194 15: 1863 16: 1929 
           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 Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] vendor: ASUSTeK 
           driver: amdgpu v: kernel bus ID: 09:00.0 chip ID: 1002:731f 
           Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati 
           unloaded: fbdev,modesetting,radeon,vesa resolution: 2560x1440~144Hz 
           OpenGL: 
           renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.40.0 5.10.0-9-amd64 LLVM 12.0.1) 
           v: 4.6 Mesa 21.2.3 direct render: Yes 
Audio:     Device-1: AMD Navi 10 HDMI Audio driver: snd_hda_intel v: kernel bus ID: 09:00.1 
           chip ID: 1002:ab38 
           Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel 
           v: kernel bus ID: 0b:00.4 chip ID: 1022:1487 
           Device-3: Logitech Logitech Webcam C925e type: USB driver: snd-usb-audio,uvcvideo 
           bus ID: 1-2:3 chip ID: 046d:085b serial: <filter> 
           Sound Server: ALSA v: k5.10.0-9-amd64 
Network:   Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel port: f000 
           bus ID: 03:00.0 chip ID: 8086:1539 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 975.96 GiB used: 210.56 GiB (21.6%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 4B6Q scheme: GPT 
           ID-2: /dev/sdb vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 1B6Q scheme: GPT 
           ID-3: /dev/sdc type: USB vendor: SanDisk model: Cruzer Blade size: 14.56 GiB 
           block size: physical: 512 B logical: 512 B serial: <filter> rev: 1.27 scheme: MBR 
           ID-4: /dev/sdd type: USB vendor: Samsung model: Flash Drive FIT size: 29.88 GiB 
           block size: physical: 512 B logical: 512 B serial: <filter> rev: 1100 scheme: MBR 
Partition: ID-1: / raw size: 218.97 GiB size: 214.48 GiB (97.95%) used: 7.59 GiB (3.5%) fs: ext4 
           dev: /dev/sda3 
           ID-2: swap-1 size: 16.60 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda4 
Sensors:   System Temperatures: cpu: 51.0 C mobo: N/A gpu: amdgpu temp: 56 C 
           Fan Speeds (RPM): N/A gpu: amdgpu fan: 0 
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-chrome.list 
           1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye main non-free
           2: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye ahs
Info:      Processes: 344 Uptime: 20m Memory: 15.60 GiB used: 1.14 GiB (7.3%) 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 

[dr-kart]

Resulted in consistent and immediate crash of War Thunder..."vulkan error waiting for GPU - timeout"

I got similar video hardware. No issues with WT at all.

Code: Select all

Graphics:  Device-1: AMD Navi 23 [Radeon RX 6600/6600 XT/6600M] vendor: Gigabyte driver: amdgpu 
           v: kernel bus ID: 03:00.0 chip ID: 1002:73ff 
           Display: x11 server: X.Org 1.20.13 driver: amdgpu resolution: 1920x1080~60Hz 
           OpenGL: renderer: AMD DIMGREY_CAVEFISH (DRM 3.42.0 5.14.0-3mx-amd64 LLVM 12.0.1) 
           v: 4.6 Mesa 21.2.3 direct render: Yes 

Here is what I did before:
Installed both 32 and 64 bit vulkan soft:

Code: Select all

libvulkan1:i386
mesa-vulkan-drivers:i386
libvulkan1
mesa-vulkan-drivers

and here edited /etc/environment:

Code: Select all

VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.i686.json:/usr/share/vulkan/icd.d/radeon_icd.x86_64.json
LIBVA_DRIVER_NAME=radeonsi

[SwampRabbit]

@Paul.. I was just about to mention adding the i386 items ...

@dr-kart where did you get this from? Did it not work until you did that?
I would have thought this would not be good seeming that the radeonsi driver would not be even close to what you would want?

Code: Select all

VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.i686.json:/usr/share/vulkan/icd.d/radeon_icd.x86_64.json
LIBVA_DRIVER_NAME=radeonsi

I'll be messing with MX-21 AHS stuff this weekend a bit

[dr-kart]

@SwampRabbit Sure thing. radeonsi in /etc/environment is just to make sure hardware video acceleration would work as it should (mpv with hwdec=auto option)

Code: Select all

Did it not work until you did that?

WarThunder won't start without

Code: Select all

VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.i686.json:/usr/share/vulkan/icd.d/radeon_icd.x86_64.json

[SwampRabbit]

@spsf64 so looking at your suggestion about the templates, I like it, but quick question about the execution of this.

While it works to great a new document of whatever type you select and have templates for, it just creates them, it doesn't open like LibreOffice Writer, Calc, etc.

Is the expectation that LibreOffice should open the new blank document after creation?

[SwampRabbit]

@SwampRabbit Sure thing. radeonsi in /etc/environment is just to make sure hardware video acceleration would work as it should (mpv with hwdec=auto option)

Wouldn't you want amdgpu instead of radeonsi though?

I guess that is what is throwing me for a loop, plus this has never been needed in the past that I am aware of, but who knows.

[dr-kart]

Wouldn't you want amdgpu instead of radeonsi though?

From https://wiki.archlinux.org/title/Hardwa ... celeration

Code: Select all

Although the video driver should automatically enable hardware video acceleration support for both VA-API and VDPAU, it may be needed to configure VA-API/VDPAU manually

Vaapi is best option for AMD GPUs afaik. So:

Code: Select all

Configuring VA-API

You can override the driver for VA-API by using the LIBVA_DRIVER_NAME environment variable:

    Intel graphics:
        For libva-intel-driver use i965.
        For intel-media-driver use iHD.
    NVIDIA:
        For Nouveau use nouveau.
        For NVIDIA use vdpau.
    AMD:
        For AMDGPU driver use radeonsi.