MX-23 beta 2 feedback thread

[baldyeti]

Yep, I got everything on that list plus some extras. Even the versions are exact.

Was worth checking; I am on oldish gen4 intel HD, perhaps someone on nvidia like you could try a wayland session ?

[Arnox]

Yep, I got everything on that list plus some extras. Even the versions are exact.

Was worth checking; I am on oldish gen4 intel HD, perhaps someone on nvidia like you could try a wayland session ?

Ok, I think I've isolated the problem further. Wayland seems to work fine on nouveau (though it was a very quick test) but the proprietary Nvidia drivers make Wayland instantly crash on session start. I wonder if the Nvidia Driver Installer isn't set to properly configure the system for Wayland operation yet maybe?

[dolphin_oracle]

Yep, I got everything on that list plus some extras. Even the versions are exact.

Was worth checking; I am on oldish gen4 intel HD, perhaps someone on nvidia like you could try a wayland session ?

Ok, I think I've isolated the problem further. Wayland seems to work fine on nouveau (though it was a very quick test) but the proprietary Nvidia drivers make Wayland instantly crash on session start. I wonder if the Nvidia Driver Installer isn't set to properly configure the system for Wayland operation yet maybe?

someone tells me what that is and maybe we can fix that.

[Arnox]

Was worth checking; I am on oldish gen4 intel HD, perhaps someone on nvidia like you could try a wayland session ?

Ok, I think I've isolated the problem further. Wayland seems to work fine on nouveau (though it was a very quick test) but the proprietary Nvidia drivers make Wayland instantly crash on session start. I wonder if the Nvidia Driver Installer isn't set to properly configure the system for Wayland operation yet maybe?

someone tells me what that is and maybe we can fix that.

Doing some super quick looking online, it looks like Wayland with Nvidia proprietary drivers may still just be flat out non-functional in general right now. I'm gonna download Debian 12 and install it and see if I get the same issue.

[Arnox]

Was worth checking; I am on oldish gen4 intel HD, perhaps someone on nvidia like you could try a wayland session ?

Ok, I think I've isolated the problem further. Wayland seems to work fine on nouveau (though it was a very quick test) but the proprietary Nvidia drivers make Wayland instantly crash on session start. I wonder if the Nvidia Driver Installer isn't set to properly configure the system for Wayland operation yet maybe?

someone tells me what that is and maybe we can fix that.

UPDATE: Yep, Debian 12 has the exact same behavior. Nvidia drivers are installed along with the appropriate Xorg config generated, then Wayland just refuses to open a session after that.

I did find this: https://wiki.debian.org/NvidiaGraphicsDrivers#Wayland

In Debian 12 (currently Debian Testing), almost all issues should be resolved and most Wayland sessions should "just work" with the 495-series driver, however some major issues remain with KDE Plasma. These will require merging KDE's Qt 5 patch collection to fix: https://salsa.debian.org/qt-kde-team/qt ... requests/5

[jacklarge]

Forgive me if this isn't anything to worry about!
I have been pretty impressed with the Beta as I tried it on a new home-built PC and not only did the PC run without issues but the Beta software also installed and found everything without complaint or the need to edit config files. However I did notice that after a couple of updates apt gave warnings about amdgpu (I am using AMD Ryzen 7 5700G without a dedicated Graphic Card currently). This is a screen shot of the latest one:
https://flic.kr/p/2oMzVcD

As requested here is my Quick System Info:

Code: Select all

System:
  Kernel: 6.1.0-9-amd64 [6.1.27-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-9-amd64 root=UUID=<filter> ro quiet splash
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23_beta2_x64 Libretto June 15  2023 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Desktop Mobo: Micro-Star model: MAG B550 TOMAHAWK MAX WIFI (MS-7C91) v: 1.0
    serial: <superuser required> UEFI: American Megatrends LLC. v: 2.20 date: 08/30/2022
CPU:
  Info: model: AMD Ryzen 7 5700G with Radeon Graphics bits: 64 type: MT MCP arch: Zen 3 gen: 4
    level: v3 note: check built: 2021-22 process: TSMC n7 (7nm) family: 0x19 (25) model-id: 0x50 (80)
    stepping: 0 microcode: 0xA50000D
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache: L1: 512 KiB
    desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB L3: 16 MiB desc: 1x16 MiB
  Speed (MHz): avg: 1507 high: 1696 min/max: 1400/4672 boost: enabled scaling:
    driver: acpi-cpufreq governor: ondemand cores: 1: 1400 2: 1695 3: 1696 4: 1414 5: 1519 6: 1687
    7: 1400 8: 1414 9: 1400 10: 1696 11: 1688 12: 1451 13: 1437 14: 1400 15: 1414 16: 1414
    bogomips: 121366
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series] driver: amdgpu v: kernel
    arch: GCN-5 code: Vega process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s ports: active: DP-1 empty: DP-2,HDMI-A-1 bus-ID: 30:00.0
    chip-ID: 1002:1638 class-ID: 0300 temp: 25.0 C
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: amdgpu
    unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.65x15.00") s-diag: 777mm (30.58")
  Monitor-1: DP-1 mapped: DisplayPort-0 model: Dell U2719DC serial: <filter> built: 2020
    res: 2560x1440 hz: 60 dpi: 109 gamma: 1.2 size: 597x336mm (23.5x13.23") diag: 685mm (27")
    ratio: 16:9 modes: max: 2560x1440 min: 720x400
  API: OpenGL v: 4.6 Mesa 22.3.6 renderer: AMD Radeon Graphics (renoir LLVM 15.0.6 DRM 3.49
    6.1.0-9-amd64) direct-render: Yes
Audio:
  Device-1: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel v: kernel pcie: gen: 3
    speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 30:00.1 chip-ID: 1002:1637
    class-ID: 0403
  Device-2: AMD Family 17h/19h HD Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
    pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 30:00.6
    chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.1.0-9-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: MEDIATEK MT7921K Wi-Fi 6E 80MHz driver: mt7921e v: kernel modules: wl pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 29:00.0 chip-ID: 14c3:0608 class-ID: 0280
  IF: wlan0 state: down mac: <filter>
  Device-2: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169 v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 port: f000 bus-ID: 2a:00.0 chip-ID: 10ec:8125 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: MediaTek Wireless_Device type: USB driver: btusb v: 0.8 bus-ID: 1-9:6
    chip-ID: 0e8d:0608 class-ID: e001 serial: <filter>
  Report: hciconfig ID: hci0 rfk-id: 5 state: down bt-service: N/A rfk-block: hardware: no
    software: yes address: <filter>
  Info: acl-mtu: 1021:6 sco-mtu: 240:8 link-policy: rswitch sniff link-mode: peripheral accept
Drives:
  Local Storage: total: 1.82 TiB used: 23.37 GiB (1.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:1 vendor: Samsung model: SSD 970 EVO Plus 1TB size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 4B2QEXM7 temp: 28.9 C scheme: MBR
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 1TB size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 5B2QGXA7 temp: 28.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 931.25 GiB size: 915.56 GiB (98.31%) used: 23.37 GiB (2.6%) fs: ext4
    dev: /dev/nvme1n1p2 maj-min: 259:4
  ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
    dev: /dev/nvme1n1p1 maj-min: 259:3
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 8 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
Sensors:
  System Temperatures: cpu: 30.6 C mobo: N/A gpu: amdgpu temp: 25.0 C
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 2152 libs: 1116 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  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 bookworm-updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bookworm main non-free
Info:
  Processes: 393 Uptime: 3d 7m wakeups: 11 Memory: 58.75 GiB used: 5.87 GiB (10.0%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12 Client: shell wrapper
  v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

[Wallon]

Dear Developers,

I can confirm Debian 12 with Gnome and a Nvidia graphics card.
Wayland is not compatible with the proprietary Nvidia driver.

I have 2 USB keys with 2 installations.
a) A Debian 12 Gnome USB key with the « nouveau » driver and Wayland.
b) A Debian 12 Gnome USB key with the proprietary Nvidia driver - X display server, so without Wayland.

In Debian 12, you need to start the session with the X display server and install the proprietary Nvidia driver.
When you restart, Wayland is automatically deleted.

Please note;
1) I don't know if KDE Plasma is still able to work with the X display server. I haven't tested it under Debian 12.
2) Gnome does not work in the same way with the « nouveau » driver as with the proprietary Nvidia driver. For example: when you click on the Gnome dock icon, you no longer have focus on the window that opens with the proprietary Nvidia driver. So there could also be differences for KDE Plasma with the 2 drivers.

My Nvidia GTX960 graphics card is able to decode YouTube VP9.
With the « nouveau » driver, I get a lot of « dropped frames » in YouTube's « Nerd Stats », especially if I move the mouse to my second screen.
The proprietary Nvidia driver makes much better use of my graphics card and I get almost no dropped frames with 60 fps (full HD 1080p).

It's not easy to choose between the 2 drivers. Each has its advantages.

Best regards,
Wallon

[Wallon]

Dear Developers,

Localization
Debian 11 and Debian 12 automatically configure the "papersize" file.
In my case, Debian 12 puts "a4" in the file.
MX Linux never localizes this file.
Why doesn't MX Linux do the same as Debian?
This is an important variable for configuring certain software.

Best regards,
Wallon

[Wallon]

Dear Developers,

When installing Debian 12, LibreOffice and Firefox are directly localized in the installation language.
Why doesn't MX Linux set the installation language directly for the software?
It would be easier for new users.

Best regards,
Wallon

[hurricane74]

- Sorry, I discovered something dumb I was doing right after posting this. Therefore I deleted it. -