Page 1 of 1

MX23 AHS freezes keyboard and mouse while MX23 doesn't

Posted: Sat Aug 12, 2023 1:07 pm
by yann
Hello,

I've been wanting to install XFCE MX23 AHS, and in the USB live, the keyboard and mouse don't respond while the Wacom tablet does. The regular XFCE MX23 USB live has no problem whatsoever. I tried several times but I always get the same issue in AHS.
Also related to the problem, AHS refers to modern hardware but without specifying what is considered as recent. For MX21, my hardware was AHS, but how do I know for MX23 ?

The system info is the one I currently have in MX21 but it's the same PC

Thanks in advance for your help.

Code: Select all

System:    Kernel: 6.0.0-6mx-amd64 [6.0.12-1~mx21+1] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-6.0.0-6mx-amd64 root=UUID=<filter> ro quiet 
           Desktop: Xfce 4.18.1 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.18.0 vt: 7 
           dm: LightDM 1.26.0 Distro: MX-21.3_ahs_x64 Wildflower November 22  2021 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop Mobo: ASRock model: B450M Pro4-F serial: <filter> 
           BIOS: American Megatrends v: P7.40 date: 10/26/2022 
CPU:       Info: Quad Core model: AMD Ryzen 3 3200G with Radeon Vega Graphics bits: 64 type: MCP 
           arch: Zen family: 17 (23) model-id: 18 (24) stepping: 1 microcode: 8108109 cache: 
           L2: 2 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 28801 
           Speed: 1398 MHz min/max: 1400/3600 MHz boost: enabled Core speeds (MHz): 1: 1398 
           2: 1400 3: 1400 4: 1400 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: mmio_stale_data status: Not affected 
           Type: retbleed mitigation: untrained return thunk; SMT disabled 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, STIBP: disabled, RSB 
           filling, PBRSB-eIBRS: Not affected 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: AMD Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] 
           driver: amdgpu v: kernel bus-ID: 07:00.0 chip-ID: 1002:15d8 class-ID: 0300 
           Device-2: KYE Systems (Mouse Systems) Genius FaceCam 320 type: USB 
           driver: snd-usb-audio,uvcvideo bus-ID: 1-5:2 chip-ID: 0458:7089 class-ID: 0102 
           Display: x11 server: X.Org 1.20.14 compositor: xfwm4 v: 4.18.0 driver: 
           loaded: amdgpu,ati unloaded: fbdev,modesetting,vesa display-ID: :0.0 screens: 1 
           Screen-1: 0 s-res: 2944x1280 s-dpi: 96 s-size: 779x339mm (30.7x13.3") 
           s-diag: 850mm (33.4") 
           Monitor-1: HDMI-A-0 res: 1024x1280 hz: 60 
           Monitor-2: HDMI-A-1 res: 1920x1080 hz: 60 dpi: 102 size: 480x270mm (18.9x10.6") 
           diag: 551mm (21.7") 
           OpenGL: 
           renderer: AMD Radeon Vega 8 Graphics (raven LLVM 14.0.5 DRM 3.48 6.0.0-6mx-amd64) 
           v: 4.6 Mesa 22.0.5 direct render: Yes 
Audio:     Device-1: AMD Raven/Raven2/Fenghuang HDMI/DP Audio driver: snd_hda_intel v: kernel 
           bus-ID: 07:00.1 chip-ID: 1002:15de class-ID: 0403 
           Device-2: AMD Family 17h/19h HD Audio vendor: ASRock driver: snd_hda_intel v: kernel 
           bus-ID: 07:00.6 chip-ID: 1022:15e3 class-ID: 0403 
           Device-3: KYE Systems (Mouse Systems) Genius FaceCam 320 type: USB 
           driver: snd-usb-audio,uvcvideo bus-ID: 1-5:2 chip-ID: 0458:7089 class-ID: 0102 
           Sound Server-1: ALSA v: k6.0.0-6mx-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASRock 
           driver: r8169 v: kernel port: f000 bus-ID: 04:00.0 chip-ID: 10ec:8168 class-ID: 0200 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 1.82 TiB used: 1.05 TiB (57.7%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 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: 2B4QFXO7 temp: 38.9 C scheme: MBR 
           ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 EVO 1TB size: 931.51 GiB 
           block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> 
           rev: 3B6Q scheme: MBR 
Partition: ID-1: / raw-size: 96.17 GiB size: 94.35 GiB (98.11%) used: 20.75 GiB (22.0%) fs: ext4 
           dev: /dev/nvme0n1p1 maj-min: 259:1 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 15.62 GiB used: 0 KiB (0.0%) priority: -2 
           dev: /dev/nvme0n1p2 maj-min: 259:2 
Sensors:   Message: No sensor data found. Is lm-sensors configured? 
Repos:     Packages: note: see --pkg apt: 2446 lib: 1350 flatpak: 0 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list 
           1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ bullseye main
           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://ftp.osuosl.org/pub/mxlinux/mx/repo/ bullseye main non-free
           2: deb http://ftp.osuosl.org/pub/mxlinux/mx/repo/ bullseye ahs
Info:      Processes: 251 Uptime: 22m wakeups: 1 Memory: 13.58 GiB used: 1.96 GiB (14.4%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 10.2.1 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: BIOS (legacy, CSM, MBR)

Re: MX23 AHS freezes keyboard and mouse while MX23 doesn't

Posted: Sat Aug 12, 2023 1:22 pm
by CharlesV
I actually saw something REALLY close to this on mx21. The ahs version was not smooth on several machines and the regular version was amazing.

What I found really interesting was that once I was all installed... I added the ahs repos and updated / upgraded... and didnt see ANY of the issues that I saw when I booted the live ahs.

Additionally, I tried to install on a couple of machines that showed this issue and I had the same exact results. I have no clue why this is like this, but there is a difference on how things setup from the AHS and non AHS liveusb's and installs.

Re: MX23 AHS freezes keyboard and mouse while MX23 doesn't  [Solved]

Posted: Sat Aug 12, 2023 1:29 pm
by j2mcgreg
@yann
Your CPU and chipset is just over 4 years old so there's no need for you to be running the AHS version. Back when MX 21 was released, your laptop would have been new enough to warrant using the AHS version. Generally the AHS version is aimed at machines that are <= eighteen months old.

Your QSI shows that you are running the 6.0.xxx kernel which is known to be buggy. You should use MXPI to install the Debian 6.1.xxx kernel, reboot, and at the Grub screen choose Advanced Options to select the new kernel as your boot choice. If this upgrade works without issues, you can make the switch permanent with the Boot Options utility in MX Tools.

Re: MX23 AHS freezes keyboard and mouse while MX23 doesn't

Posted: Sat Aug 12, 2023 5:15 pm
by yann
@CharlesV Thanks a lot. I installed XFCE MX23 standard edition and it worked almost flawlessly. Just a weird behaviour probably due to Ventoy that I used to install it.

@j2mcgreg As you said that AHS is not needed for my PC, I stuck to the standard version and it seems to work fine, thanks a lot. Still I think this issue should be solved for new users, as @CharlesV also had a similar issue.