MX-21 "ahs" (Xfce) RC3 feedback

[dolphin_oracle]

I see quite a few posts about this same issue with ubuntu and steam out on the interwebs.

[danielson]

Wanting to change keyboard settings:

Hit super key "keyboard" to change layout but still must go to MX Tools "system keyboard" to add that same language desired.

Noticed same thing on stable.

Sorry if this isn't a bug, but just curious why the apparent duplicate settings?

[fehlix]

Wanting to change keyboard settings:

Hit super key "keyboard" to change layout but still must go to MX Tools "system keyboard" to add that same language desired.

Noticed same thing on stable.

Sorry if this isn't a bug, but just curious why the apparent duplicate settings?

It's by design. Either use session keyboard or change to "Use system defaults" under Keyboard->Layouts.
Rational: Different user might prefer different layouts.

[davemx]

For me, this RC3 is running OK with the kernel downgraded to 5.10.0-9, but I will test any proposed ahs kernel to see if suspend will work without systemd on my system.

[davemx]

Total double whammy! Not only does the RC3 produce exactly the same error on Suspend, (I should have expected that, as I had already tried the 5.14.0-3 kernel previously). Then after I finished looking at it, then tried to run my MX21-KDE partition, that wouldn't run, part way through the plymouth screen, it suddenly dropped to a text screen with the error:

[drm] <<ERROR>> failed to enable link training

I can log in as root (text) from there, and run the display manager, but all attempts to log in fail, they just come back to the DM.

OK I have worked out what caused the error above...

First to explain that I have 6 20Gb root partitions. I mount them as /mnt/Distro1 to /mnt/Distro6 (obviously with the exception that the actual root partition I have logged into is mounted at / ). Under MX19, and also with MX21 up to RC1, when I made a fresh install on one of the partitions, and the UUID changed, all that would happen is that the partition with the wrong info in /etc/fstab didn't mount, so then I would correct /etc/fstab.

From MX21 RC3 and final, this caused the error I described above. All I had to do was to run the new install, go into /mnt/DistroN/etc/fstab and correct it, and now the supposedly "broken" install boots as well. It only seems to affect MX-Linux not other distros I have installed which behave like MX19 did, and I can sort out their /etc/fstab entries when I get around to running them.

So it wasn't a bug, and it won't affect anyone who just installs a single instance of Linux on their computer. And I'll know what to do next time!

[dolphin_oracle]

Total double whammy! Not only does the RC3 produce exactly the same error on Suspend, (I should have expected that, as I had already tried the 5.14.0-3 kernel previously). Then after I finished looking at it, then tried to run my MX21-KDE partition, that wouldn't run, part way through the plymouth screen, it suddenly dropped to a text screen with the error:

[drm] <<ERROR>> failed to enable link training

I can log in as root (text) from there, and run the display manager, but all attempts to log in fail, they just come back to the DM.

OK I have worked out what caused the error above...

First to explain that I have 6 20Gb root partitions. I mount them as /mnt/Distro1 to /mnt/Distro6 (obviously with the exception that the actual root partition I have logged into is mounted at / ). Under MX19, and also with MX21 up to RC1, when I made a fresh install on one of the partitions, and the UUID changed, all that would happen is that the partition with the wrong info in /etc/fstab didn't mount, so then I would correct /etc/fstab.

From MX21 RC3 and final, this caused the error I described above. All I had to do was to run the new install, go into /mnt/DistroN/etc/fstab and correct it, and now the supposedly "broken" install boots as well. It only seems to affect MX-Linux not other distros I have installed which behave like MX19 did, and I can sort out their /etc/fstab entries when I get around to running them.

So it wasn't a bug, and it won't affect anyone who just installs a single instance of Linux on their computer. And I'll know what to do next time!

a systemd distro may not need the fstab entry.

[danielson]

@fehlix - can dig that.

For the record, even if my DELL is unable to handle AHS to the fullest, did work quite well for me today.
One problem though.
Even if system was set to sleep mode instead of hibernate (power button), it could never wake up after "sleeping" for a while (fuzzy screen).
Had to shutdown and reboot (tried this procedure twice).
Someone else have this issue?

Have gone back to MX21 XFCE (non AHS) which is super (strong words for a KDE fan)!
Just love the way MX-combort-dark mode blends in so well with Firefox, LibreOffice etc. on XFCE.

- - - - -

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_x64 Wildflower October 20  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: Dell product: Latitude E5430 non-vPro v: 01 serial: <filter> 
           Chassis: type: 9 serial: <filter> 
           Mobo: Dell model: 0MYF02 v: A00 serial: <filter> UEFI: Dell v: A21 date: 11/30/2018 
Battery:   ID-1: BAT0 charge: 1.6 Wh condition: 1.6/99.9 Wh (2%) volts: 12.6/11.1 
           model: SMP DELL P6YD624 type: Li-ion serial: <filter> status: Full 
           Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M280/320/275 
           serial: <filter> charge: 55% (should be ignored) rechargeable: yes 
           status: Discharging 
CPU:       Topology: Dual Core model: Intel Core i5-3210M bits: 64 type: MT MCP arch: Ivy Bridge 
           family: 6 model-id: 3A (58) stepping: 9 microcode: 21 L2 cache: 3072 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19933 
           Speed: 1504 MHz min/max: 1200/3100 MHz Core speeds (MHz): 1: 1317 2: 1386 3: 1514 
           4: 1404 
           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: Vulnerable: No microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel 3rd Gen Core processor Graphics vendor: Dell driver: i915 v: kernel 
           bus ID: 00:02.0 chip ID: 8086:0166 
           Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1600x900~60Hz, 1440x900~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 4000 (IVB GT2) v: 4.2 Mesa 20.3.5 
           compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Dell 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:1e20 
           Device-2: Logitech Logitech USB Headset type: USB 
           driver: hid-generic,snd-usb-audio,usbhid bus ID: 3-3:2 chip ID: 046d:0a8f 
           Sound Server: ALSA v: k5.10.0-9-amd64 
Network:   Device-1: Broadcom and subsidiaries BCM4313 802.11bgn Wireless Network Adapter 
           vendor: Dell driver: wl v: kernel port: f040 bus ID: 02:00.0 chip ID: 14e4:4727 
           IF: wlan0 state: dormant mac: <filter> 
           Device-2: Broadcom and subsidiaries NetXtreme BCM5761 Gigabit Ethernet PCIe 
           vendor: Dell driver: tg3 v: kernel port: f040 bus ID: 0c:00.0 chip ID: 14e4:1681 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 223.57 GiB used: 12.09 GiB (5.4%) 
           ID-1: /dev/sda vendor: Kingston model: SA400S37240G size: 223.57 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 0102 scheme: GPT 
RAID:      Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci v: 3.0 
           port: f060 bus ID: 00:1f.2 chip ID: 8086.282a rev: 04 
Partition: ID-1: / raw size: 54.58 GiB size: 53.42 GiB (97.88%) used: 12.04 GiB (22.5%) fs: ext4 
           dev: /dev/sda5 
Sensors:   System Temperatures: cpu: 75.0 C mobo: 47.0 C sodimm: 45.0 C 
           Fan Speeds (RPM): cpu: 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/mx.list 
           1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye main non-free
           Active apt repos in: /etc/apt/sources.list.d/vivaldi.list 
           1: deb http://repo.vivaldi.com/stable/deb/ stable main
Info:      Processes: 230 Uptime: 3h 00m Memory: 7.68 GiB used: 1.94 GiB (25.2%) 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 

[dolphin_oracle]

@fehlix - can dig that.

For the record, even if my DELL is unable to handle AHS to the fullest, did work quite well for me today.
One problem though.
Even if system was set to sleep mode instead of hibernate (power button), it could never wake up after "sleeping" for a while (fuzzy screen).
Had to shutdown and reboot (tried this procedure twice).
Someone else have this issue?

Have gone back to MX21 XFCE (non AHS) which is super (strong words for a KDE fan)!
Just love the way MX-combort-dark mode blends in so well with Firefox, LibreOffice etc. on XFCE.

- - - - -

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_x64 Wildflower October 20  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: Dell product: Latitude E5430 non-vPro v: 01 serial: <filter> 
           Chassis: type: 9 serial: <filter> 
           Mobo: Dell model: 0MYF02 v: A00 serial: <filter> UEFI: Dell v: A21 date: 11/30/2018 
Battery:   ID-1: BAT0 charge: 1.6 Wh condition: 1.6/99.9 Wh (2%) volts: 12.6/11.1 
           model: SMP DELL P6YD624 type: Li-ion serial: <filter> status: Full 
           Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M280/320/275 
           serial: <filter> charge: 55% (should be ignored) rechargeable: yes 
           status: Discharging 
CPU:       Topology: Dual Core model: Intel Core i5-3210M bits: 64 type: MT MCP arch: Ivy Bridge 
           family: 6 model-id: 3A (58) stepping: 9 microcode: 21 L2 cache: 3072 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19933 
           Speed: 1504 MHz min/max: 1200/3100 MHz Core speeds (MHz): 1: 1317 2: 1386 3: 1514 
           4: 1404 
           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: Vulnerable: No microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel 3rd Gen Core processor Graphics vendor: Dell driver: i915 v: kernel 
           bus ID: 00:02.0 chip ID: 8086:0166 
           Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1600x900~60Hz, 1440x900~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 4000 (IVB GT2) v: 4.2 Mesa 20.3.5 
           compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Dell 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:1e20 
           Device-2: Logitech Logitech USB Headset type: USB 
           driver: hid-generic,snd-usb-audio,usbhid bus ID: 3-3:2 chip ID: 046d:0a8f 
           Sound Server: ALSA v: k5.10.0-9-amd64 
Network:   Device-1: Broadcom and subsidiaries BCM4313 802.11bgn Wireless Network Adapter 
           vendor: Dell driver: wl v: kernel port: f040 bus ID: 02:00.0 chip ID: 14e4:4727 
           IF: wlan0 state: dormant mac: <filter> 
           Device-2: Broadcom and subsidiaries NetXtreme BCM5761 Gigabit Ethernet PCIe 
           vendor: Dell driver: tg3 v: kernel port: f040 bus ID: 0c:00.0 chip ID: 14e4:1681 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 223.57 GiB used: 12.09 GiB (5.4%) 
           ID-1: /dev/sda vendor: Kingston model: SA400S37240G size: 223.57 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 0102 scheme: GPT 
RAID:      Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci v: 3.0 
           port: f060 bus ID: 00:1f.2 chip ID: 8086.282a rev: 04 
Partition: ID-1: / raw size: 54.58 GiB size: 53.42 GiB (97.88%) used: 12.04 GiB (22.5%) fs: ext4 
           dev: /dev/sda5 
Sensors:   System Temperatures: cpu: 75.0 C mobo: 47.0 C sodimm: 45.0 C 
           Fan Speeds (RPM): cpu: 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/mx.list 
           1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye main non-free
           Active apt repos in: /etc/apt/sources.list.d/vivaldi.list 
           1: deb http://repo.vivaldi.com/stable/deb/ stable main
Info:      Processes: 230 Uptime: 3h 00m Memory: 7.68 GiB used: 1.94 GiB (25.2%) 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 

I have an ivy bridge like yours and yes suspend is a mess on it. but my newer, less capable, intel-based netbooks suspend pretty well with the 5.14.0-3 kernel. and they all suspend well with the 5.10.

[davemx]

a systemd distro may not need the fstab entry.

The other Distro is not systemd, and booting into MX with systemd before I corrected fstab didn't work either. It also doesn't have a problem with suspend, but I guess that having a kernel designed to work with both init systems adds extra complication. You could have two optimised kernels though, as the choice of init systems is made at bootup via grub.

[danielson]

@dolphin_oracle - suspenders work better for some than others eh!

Rather than tinkering with downgrading/upgrading kernel, will stick with MX21 "normal" for now since its "suspender" works fine here.
(never cared for suspenders - don't know how men could ever wear those things).