MX-21 "ahs" (Xfce) RC3 feedback
-
- Posts: 3602
- Joined: Tue Jun 14, 2016 2:02 pm
Re: MX-21 "ahs" (Xfce) RC3 feedback
@BasicSloth when you say "SteamPlay" you're talking about playing Windows games off a remote Windows computer (asking cause you used the word "over" earlier) or that you are using Proton?
If I had to guess these games may need a specific version of Proton, if you know what you used wth MX-19, I would try that version. I don't think this a MX-21 AHS specific issue, but it would be nice to find out the issue with these games.
If I had to guess these games may need a specific version of Proton, if you know what you used wth MX-19, I would try that version. I don't think this a MX-21 AHS specific issue, but it would be nice to find out the issue with these games.
NEW USERS START HERE FAQS, MX Manual, and How to Break Your System - Don't use Ubuntu PPAs! Always post your Quick System Info (QSI) when asking for help.
-
- Posts: 3602
- Joined: Tue Jun 14, 2016 2:02 pm
Re: MX-21 "ahs" (Xfce) RC3 feedback
I saw this when you posted it, sorry for not replying right away. I need to look at the specs of the system you shared some more. I've seen the Fitlet2 before, never bought one myself though.datalus wrote: Sat Nov 06, 2021 1:55 pm I can confirm that MX 21 RC3 LiveMedium is unstable on an Intel small board computer (Atom, Goldmont) while using the modesetting driver. After a week of light testing while streaming video via web browser, Firefox would crash and/or the whole OS would crash. GLX gears looks nice though. Video is streaming real nice and smooth.
I have a Odroid H2+ that I've been doing MX-21 testing on since Alpha, not the same mind you, but I also ran MX-21 Fluxbox on a Atomic Pi for awhile. Done lots of testing on X86 SBCs without real issue.
My assumption is that your SBC should work without issue, the Xorg modesetting driver should work with this SBC, but it just might be on the cusp of the time line and the Intel driver may be better. You can use MX Tweak > Other Tab to change it, you'll need to at least log out and back in after.
The hardware shouldn't need AHS actually, can you try the standard MX-21 Xfce from a live USB at least.
I say this because the 5.14 is pretty stable but the 5.10 kernel is really stable, and the rest of the AHS bits while good.... aren't considered "stable" to Debian standards yet. There could be minor bugs affecting certain hardware like we've been experiencing with suspend issues recently with AHS RC.
Have you had this Fitlet2 long?
Temps weren't/aren't an issue?
Were using using it with Mint (some shipped with Mint) before without issue?
Old QSI just for reference from the H2 (again not the same thing as yours)
Code: Select all
System: Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A
parameters: BOOT_IMAGE=/boot/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_rc1_x64 Wildflower October 4 2021 base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Desktop Mobo: HARDKERNEL model: ODROID-H2 v: 1.0 serial: <filter>
UEFI: American Megatrends v: 5.13 date: 04/27/2020
CPU: Topology: Quad Core model: Intel Celeron J4115 bits: 64 type: MCP arch: Goldmont Plus
family: 6 model-id: 7A (122) stepping: 1 microcode: 36 L2 cache: 4096 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 14284
Speed: 2437 MHz min/max: 800/2500 MHz Core speeds (MHz): 1: 2474 2: 2277 3: 2359
4: 2369
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
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: Enhanced IBRS, IBPB: conditional, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: Intel GeminiLake [UHD Graphics 600] driver: i915 v: kernel bus ID: 00:02.0
chip ID: 8086:3185
Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel UHD Graphics 600 (GLK 2) v: 4.6 Mesa 20.3.5
direct render: Yes
Audio: Device-1: Intel Celeron/Pentium Silver Processor High Definition Audio
driver: snd_hda_intel v: kernel bus ID: 00:0e.0 chip ID: 8086:3198
Sound Server: ALSA v: k5.10.0-8-amd64
Network: Device-1: Realtek RTL8125 2.5GbE driver: r8169 v: kernel port: e000 bus ID: 02:00.0
chip ID: 10ec:8125
IF: eth0 state: down mac: <filter>
Device-2: Realtek RTL8125 2.5GbE driver: r8169 v: kernel port: d000 bus ID: 03:00.0
chip ID: 10ec:8125
IF: eth1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-3: Realtek RTL8811AU 802.11a/b/g/n/ac WLAN Adapter type: USB driver: rtl8812au
bus ID: 1-2:3 chip ID: 0bda:a811 serial: <filter>
IF: wlan0 state: down mac: <filter>
Drives: Local Storage: total: 238.47 GiB used: 5.96 GiB (2.5%)
ID-1: /dev/nvme0n1 model: Sabrent size: 238.47 GiB block size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: RKT303.3 scheme: GPT
Partition: ID-1: / raw size: 41.43 GiB size: 40.49 GiB (97.71%) used: 5.96 GiB (14.7%) fs: ext4
dev: /dev/nvme0n1p2
ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60)
cache pressure: 100 (default) dev: /dev/nvme0n1p3
Sensors: System Temperatures: cpu: 56.0 C mobo: N/A
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/mx.list
1: deb http://mxrepo.com/mx/repo/ bullseye main non-free
Info: Processes: 206 Uptime: 11m Memory: 7.60 GiB used: 832.6 MiB (10.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
NEW USERS START HERE FAQS, MX Manual, and How to Break Your System - Don't use Ubuntu PPAs! Always post your Quick System Info (QSI) when asking for help.
-
- Posts: 14
- Joined: Wed Jun 30, 2021 3:33 pm
Re: MX-21 "ahs" (Xfce) RC3 feedback
With SteamPlay i mean, i playing games over steam using proton. I don't think it's a MX-21 AHS problem either. I do think further discussions on that topic (those two games) don't belong in that thread. I will make a new one, as soon as I find a solution, which will make the games run.SwampRabbit wrote: Tue Nov 09, 2021 7:26 pm @BasicSloth when you say "SteamPlay" you're talking about playing Windows games off a remote Windows computer (asking cause you used the word "over" earlier) or that you are using Proton?
If I had to guess these games may need a specific version of Proton, if you know what you used wth MX-19, I would try that version. I don't think this a MX-21 AHS specific issue, but it would be nice to find out the issue with these games.
Re: MX-21 "ahs" (Xfce) RC3 feedback
Finally installed the MX-21 AHS RC3 over my MX-19.4 AHS, and other than new learnings on a UEFI dual-boot system with Windows 10, it was so far great. Everything seems to be working well. However, I noticed in DMESG, there were some new errors specific to Bluetooth. What used to work for my Bluetooth headset in MX-19.4 (w/ kernel 5.10), is not working in MX-21 AHS RC3 (w/ kernel 5.14).
System Info:
Ques#1 - Not sure if its caused by this --> "[ 5.112825] bluetooth hci0: firmware: failed to load intel/ibt-20-0-0.sfi (-2)". If so, how does one find this firmware?
or
Ques#2 - Is bluetooth itself broken on kernel 5.14 vs 5.10 for some bluetooth devices? If so, is there an easy way to downgrade kernel to 5.10 to check? Do I choose kernels in MX Package Installer, for Debian 64 bit (5.10)?
Thanks for any info.
System Info:
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: ROG STRIX B450-F GAMING II v: Rev 1.xx serial: <filter>
UEFI: American Megatrends v: 4602 date: 08/17/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: 115198
Speed: 3290 MHz min/max: 2200/3600 MHz boost: enabled Core speeds (MHz): 1: 2199 2: 3347 3: 2200 4: 2206 5: 2197
6: 2005 7: 2199 8: 2199 9: 2200 10: 2128 11: 2202 12: 2187 13: 2462 14: 2200 15: 2202 16: 2198
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: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: ASUSTeK driver: nvidia v: 470.63.01 bus ID: 09:00.0
chip ID: 10de:1c82
Display: x11 server: X.Org 1.20.13 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa alternate: nv
resolution: 1680x1050~60Hz, 3840x2160~60Hz
OpenGL: renderer: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 470.63.01 direct render: Yes
Audio: Device-1: NVIDIA GP107GL High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 09:00.1
chip ID: 10de:0fb9
Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
bus ID: 0c:00.4 chip ID: 1022:1487
Sound Server: ALSA v: k5.14.0-3mx-amd64
Network: Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel port: d000 bus ID: 03:00.0
chip ID: 8086:1539
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel port: d000 bus ID: 06:00.0 chip ID: 8086:2723
IF: wlan0 state: down mac: <filter>
Drives: Local Storage: total: 1.20 TiB used: 28.87 GiB (2.3%)
ID-1: /dev/nvme0n1 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 serial: <filter> rev: 2B2QEXM7 scheme: GPT
ID-2: /dev/sda vendor: Western Digital model: WD3200KS-00PFB0 size: 298.09 GiB block size: physical: 512 B
logical: 512 B speed: 1.5 Gb/s serial: <filter> rev: 0M21 scheme: MBR
Partition: ID-1: / raw size: 512.70 GiB size: 503.58 GiB (98.22%) used: 28.85 GiB (5.7%) fs: ext4 dev: /dev/nvme0n1p2
ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) cache pressure: 100 (default)
dev: /dev/nvme0n1p5
Sensors: System Temperatures: cpu: 38.9 C mobo: N/A gpu: nvidia temp: 30 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 29%
Repos: Active apt repos in: /etc/apt/sources.list
1: deb https://www.bchemnet.com/suldr/ debian extra
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/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/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
Active apt repos in: /etc/apt/sources.list.d/spotify.list
1: deb http://repository.spotify.com/ stable non-free
Active apt repos in: /etc/apt/sources.list.d/teamviewer.list
1: deb https://linux.teamviewer.com/deb/ stable main
Info: Processes: 361 Uptime: 11h 08m Memory: 62.71 GiB used: 2.95 GiB (4.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
Code: Select all
$ lsusb | grep -i bluetooth
Bus 001 Device 005: ID 8087:0029 Intel Corp. AX200 Bluetooth
Code: Select all
$ lsmod | grep -i bt
btusb 65536 0
btrtl 28672 1 btusb
btbcm 20480 1 btusb
btintel 32768 1 btusb
bluetooth 757760 44 btrtl,btintel,btbcm,bnep,btusb,rfcomm
btrfs 1654784 0
zstd_compress 196608 1 btrfs
xor 24576 2 async_xor,btrfs
raid6_pq 122880 4 async_pq,btrfs,raid456,async_raid6_recov
libcrc32c 16384 4 nf_conntrack,btrfs,nf_tables,raid456
usbcore 331776 6 gspca_main,xhci_hcd,gspca_zc3xx,usbhid,btusb,xhci_pci
Code: Select all
$ dmesg | grep -i bluetooth
[ 5.101530] Bluetooth: Core ver 2.22
[ 5.101542] NET: Registered PF_BLUETOOTH protocol family
[ 5.101542] Bluetooth: HCI device and connection manager initialized
[ 5.101544] Bluetooth: HCI socket layer initialized
[ 5.101545] Bluetooth: L2CAP socket layer initialized
[ 5.101547] Bluetooth: SCO socket layer initialized
[ 5.107531] Bluetooth: hci0: Firmware revision 0.0 build 206 week 30 2021
[ 5.112825] bluetooth hci0: firmware: failed to load intel/ibt-20-0-0.sfi (-2)
[ 8.098833] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 8.098836] Bluetooth: BNEP filters: protocol multicast
[ 8.098839] Bluetooth: BNEP socket layer initialized
[ 10.985605] Bluetooth: RFCOMM TTY layer initialized
[ 10.985612] Bluetooth: RFCOMM socket layer initialized
[ 10.985616] Bluetooth: RFCOMM ver 1.11
[28545.815544] Bluetooth: hci0: urb 0000000070f46ba0 submission failed (90)
[28545.815552] Bluetooth: hci0: sending frame failed (-90)
[28545.828652] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828659] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828662] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828672] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828674] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828676] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828678] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828680] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828682] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828684] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828686] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828687] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828688] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828690] Bluetooth: hci0: SCO packet for unknown connection handle 48
[28545.828692] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828693] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828695] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828696] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828698] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828699] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828701] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828702] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828703] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828705] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828706] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828708] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828709] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828711] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828712] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828714] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828715] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828717] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828718] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828720] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828721] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828723] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828724] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828725] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.828727] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.838653] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.838657] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.838659] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.838661] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.838663] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28545.838671] Bluetooth: hci0: SCO packet for unknown connection handle 0
[28550.835717] Bluetooth: hci0: SCO packet for unknown connection handle 257
[28550.835724] Bluetooth: hci0: SCO packet for unknown connection handle 257
or
Ques#2 - Is bluetooth itself broken on kernel 5.14 vs 5.10 for some bluetooth devices? If so, is there an easy way to downgrade kernel to 5.10 to check? Do I choose kernels in MX Package Installer, for Debian 64 bit (5.10)?
Thanks for any info.
Mixed of desktops and laptops, I have a Gravis Ultrasound Classic card (unfortunately its ISA-slot based) ... - I must be a dino. 
Running on my DesktopPC - MX-23.4 AHS with latest Kernel: 6.12.17-1-liquorix-amd64

Running on my DesktopPC - MX-23.4 AHS with latest Kernel: 6.12.17-1-liquorix-amd64
Re: MX-21 "ahs" (Xfce) RC3 feedback
Ok, I think I found the repository --> kernel/git/firmware/linux-firmware.git, and its not there (from the latest?). And I think its not due to the act its missing in Ques#1. I think its more related to Ques#2, a possible 5.14.x kernel issue. Hopefully, there is a newer patched kernel soon.
Mixed of desktops and laptops, I have a Gravis Ultrasound Classic card (unfortunately its ISA-slot based) ... - I must be a dino. 
Running on my DesktopPC - MX-23.4 AHS with latest Kernel: 6.12.17-1-liquorix-amd64

Running on my DesktopPC - MX-23.4 AHS with latest Kernel: 6.12.17-1-liquorix-amd64
-
- Posts: 3602
- Joined: Tue Jun 14, 2016 2:02 pm
Re: MX-21 "ahs" (Xfce) RC3 feedback
@razor2021 the firmware for the AX200 series has been in firmware-nonfree for quite a while now and seems to be updated with each release.
https://metadata.ftp-master.debian.org/ ... _changelog
Is the AX200 device a PCIe device, is it built into the motherboard, is it M.2?
I believe we had someone using a AX200 series from the AHS Beta or other RC threads. Have to go back and see those posts.
Hunting around a bit, I've found similar errors reported for both 5.14 kernel and btusb, some old and some new, might take a bit to narrow it down.
https://patches.linaro.org/project/linu ... gmail.com/
https://www.mail-archive.com/debian-bug ... 22096.html
We have recently updated the 5.14 kernel in MX Test Repo, you might want to look in MX Package Installer to make sure you have the latest in the mean time.
https://metadata.ftp-master.debian.org/ ... _changelog
Is the AX200 device a PCIe device, is it built into the motherboard, is it M.2?
I believe we had someone using a AX200 series from the AHS Beta or other RC threads. Have to go back and see those posts.
Hunting around a bit, I've found similar errors reported for both 5.14 kernel and btusb, some old and some new, might take a bit to narrow it down.
https://patches.linaro.org/project/linu ... gmail.com/
https://www.mail-archive.com/debian-bug ... 22096.html
We have recently updated the 5.14 kernel in MX Test Repo, you might want to look in MX Package Installer to make sure you have the latest in the mean time.
NEW USERS START HERE FAQS, MX Manual, and How to Break Your System - Don't use Ubuntu PPAs! Always post your Quick System Info (QSI) when asking for help.
Re: MX-21 "ahs" (Xfce) RC3 feedback
@SwampRabbit The AX200 is a PCIe device and takes a PCIe slot. I'll take a look into MX Test Repo. What should I be looking for in MX Test Repo? If I search for 'kernel', I am not sure which package I might be looking for, or am I looking at the wrong packages i.e. linux-config-5.14?
Mixed of desktops and laptops, I have a Gravis Ultrasound Classic card (unfortunately its ISA-slot based) ... - I must be a dino. 
Running on my DesktopPC - MX-23.4 AHS with latest Kernel: 6.12.17-1-liquorix-amd64

Running on my DesktopPC - MX-23.4 AHS with latest Kernel: 6.12.17-1-liquorix-amd64
Re: MX-21 "ahs" (Xfce) RC3 feedback
I'm not testing this any more. I've removed the ahs-RC3 and installed the "vanilla" XFCE version and I can see no practical reason now to use the ahs, even though with the 19.x versions I could. Obviously, in both cases, that's perception rather than any measurable difference.
Desktop: Mini-Box M350 with Asus H110i-plus motherboard, Pentium G4600 processor, 2TB SSD and 16Gb RAM DDR4-2133
Printer/Scanner: Brother MFC-J5335W
Laptop: Lenovo V15 ADA
Media Centre: Lenovo Q190
Printer/Scanner: Brother MFC-J5335W
Laptop: Lenovo V15 ADA
Media Centre: Lenovo Q190
Re: MX-21 "ahs" (Xfce) RC3 feedback
Installed RC3 over RC1 yesterday and repeated the install today because of a couple of issues which didn't occur on RC1.
I've rebooted about 20 times (because of problems with disk manager, now resolved I think) and three times the boot has failed at about 4 secs leaving a Busybox prompt. The first error message is
and errors cascade from there. The next boot has been successful each time.
[EDIT] Realised I didn't post QSI
I've rebooted about 20 times (because of problems with disk manager, now resolved I think) and three times the boot has failed at about 4 secs leaving a Busybox prompt. The first error message is
Code: Select all
Begin: Running /scripts/init-bottom... mount: mounting /dev on /root/dev failed: no such file or directory
[EDIT] Realised I didn't post QSI
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=/dev/sda5
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: ASRock model: FM2A88X-ITX+ serial: <filter>
UEFI: American Megatrends v: P2.10 date: 01/17/2014
Battery: Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard K270 serial: <filter>
charge: 50% (should be ignored) rechargeable: yes status: N/A
Device-2: hidpp_battery_1 model: Logitech Wireless Mouse M185 serial: <filter>
charge: 55% (should be ignored) rechargeable: yes status: Discharging
CPU: Topology: Quad Core model: AMD A8-6500 APU with Radeon HD Graphics bits: 64 type: MCP
arch: Piledriver family: 15 (21) model-id: 13 (19) stepping: 1 microcode: 6001119
L2 cache: 2048 KiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 27948
Speed: 1827 MHz min/max: 1700/3500 MHz boost: enabled Core speeds (MHz): 1: 1956
2: 2148 3: 1717 4: 1696
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, STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: AMD Richland [Radeon HD 8570D] vendor: ASRock driver: radeon v: kernel
bus ID: 00:01.0 chip ID: 1002:990e
Display: x11 server: X.Org 1.20.13 driver: ati,radeon
unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: AMD ARUBA (DRM 2.50.0 / 5.14.0-3mx-amd64 LLVM 12.0.1)
v: 4.3 Mesa 21.2.5 compat-v: 3.1 direct render: Yes
Audio: Device-1: AMD Trinity HDMI Audio vendor: ASRock driver: snd_hda_intel v: kernel
bus ID: 00:01.1 chip ID: 1002:9902
Device-2: AMD FCH Azalia vendor: ASRock driver: snd_hda_intel v: kernel
bus ID: 00:14.2 chip ID: 1022:780d
Sound Server: ALSA v: k5.14.0-3mx-amd64
Network: Device-1: Qualcomm Atheros AR9462 Wireless Network Adapter vendor: AzureWave
driver: ath9k v: kernel port: f100 bus ID: 01:00.0 chip ID: 168c:0034
IF: wlan0 state: down mac: <filter>
Device-2: Qualcomm Atheros QCA8171 Gigabit Ethernet vendor: ASRock driver: alx
v: kernel port: e000 bus ID: 03:00.0 chip ID: 1969:10a1
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 2.05 TiB used: 179.37 GiB (8.6%)
ID-1: /dev/sda vendor: Samsung model: SSD 870 EVO 250GB size: 232.89 GiB block size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 1B6Q scheme: GPT
ID-2: /dev/sdb vendor: Seagate model: ST1000DM005 HD103SJ size: 931.51 GiB
block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s rotation: 7200 rpm
serial: <filter> rev: 00E5 scheme: MBR
ID-3: /dev/sdc vendor: Toshiba model: HDWD110 size: 931.51 GiB block size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter>
rev: A8J0 scheme: MBR
Partition: ID-1: / raw size: 30.00 GiB size: 29.36 GiB (97.87%) used: 7.00 GiB (23.9%) fs: ext4
dev: /dev/sda5
ID-2: swap-1 size: 7.81 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60)
cache pressure: 100 (default) dev: /dev/sdb11
Sensors: System Temperatures: cpu: 17.5 C mobo: N/A gpu: radeon temp: 10 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/mx.list
1: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bullseye main non-free
2: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bullseye ahs
Active apt repos in: /etc/apt/sources.list.d/vivaldi.list
1: deb [arch=amd64] http://repo.vivaldi.com/stable/deb/ stable main
Info: Processes: 237 Uptime: 23m Memory: 6.71 GiB used: 1.05 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
Gigabyte B550I Aorus Pro AX, Ryzen 5 5600G, 16GB, 250GB Samsung SSD (GPT), 2x1TB HDD (MBR), MX-21-AHS
Lenovo Thinkpad X220, dual-core i5, 4MB, 120GB Samsung SSD (GPT), MX-21
- Eadwine Rose
- Administrator
- Posts: 14804
- Joined: Wed Jul 12, 2006 2:10 am
Re: MX-21 "ahs" (Xfce) RC3 feedback
MX-23.6_x64 July 31 2023 * 6.1.0-37amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030