MX-21 fluxbox beta 1 feedback thread.

[siamhie]

Installed my rtl8814 drivers and connected to the 5G Netgear. Been playing around for about two hours and love the speed. Now I remember what I loved about Fluxbox in the first place.

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 
           init=/lib/systemd/systemd 
           Desktop: Fluxbox 1.3.5 info: tint2 dm: LightDM 1.26.0 
           Distro: MX-21_fluxbox_beta1_x64 Wildflower August 20  2021 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop System: ASUSTeK product: K30BF_M32BF_A_F_K31BF_6 v: N/A 
           serial: <filter> 
           Mobo: ASUSTeK model: K30BF_M32BF_A_F_K31BF_6 v: Rev X.0x serial: <filter> 
           UEFI [Legacy]: American Megatrends v: 0401 date: 04/29/2015 
Battery:   Device-1: hidpp_battery_0 model: Logitech Wireless Mouse serial: <filter> 
           charge: 55% (should be ignored) rechargeable: yes status: Discharging 
           Device-2: hidpp_battery_1 model: Logitech Wireless Keyboard K360 serial: <filter> 
           charge: 100% (should be ignored) rechargeable: yes status: Discharging 
CPU:       Topology: Quad Core model: AMD A10-7800 Radeon R7 12 Compute Cores 4C+8G bits: 64 
           type: MCP arch: Steamroller family: 15 (21) model-id: 30 (48) stepping: 1 
           microcode: 6003106 L2 cache: 2048 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 27930 
           Speed: 1394 MHz min/max: 1400/3500 MHz boost: enabled Core speeds (MHz): 1: 1392 
           2: 1395 3: 1396 4: 1394 
           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 Kaveri [Radeon R7 Graphics] vendor: ASUSTeK driver: radeon v: kernel 
           bus ID: 00:01.0 chip ID: 1002:130f 
           Device-2: AMD Oland PRO [Radeon R7 240/340] vendor: ASUSTeK driver: radeon v: kernel 
           bus ID: 01:00.0 chip ID: 1002:6613 
           Display: x11 server: X.Org 1.20.11 driver: ati,radeon 
           unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz 
           OpenGL: renderer: AMD OLAND (DRM 2.50.0 5.10.0-8-amd64 LLVM 11.0.1) 
           v: 4.5 Mesa 20.3.5 direct render: Yes 
Audio:     Device-1: AMD Kaveri HDMI/DP Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus ID: 00:01.1 chip ID: 1002:1308 
           Device-2: AMD FCH Azalia vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus ID: 00:14.2 chip ID: 1022:780d 
           Device-3: AMD Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000 Series] 
           vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 1002:aab0 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Realtek RTL8821AE 802.11ac PCIe Wireless Network Adapter vendor: AzureWave 
           driver: rtl8821ae v: kernel port: d000 bus ID: 04:00.0 chip ID: 10ec:8821 
           IF: wlan0 state: down mac: <filter> 
           Device-2: NetGear Nighthawk A7000 802.11ac Wireless Adapter AC1900 [Realtek 8814AU] 
           type: USB driver: 8814au bus ID: 2-2:2 chip ID: 0846:9054 serial: <filter> 
           IF: wlan1 state: up mac: <filter> 
Drives:    Local Storage: total: 1.82 TiB used: 4.93 GiB (0.3%) 
           ID-1: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB block size: 
           physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> 
           rev: A7L0 scheme: GPT 
           ID-2: /dev/sdb vendor: Seagate model: ST1000DM003-1ER162 size: 931.51 GiB block size: 
           physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> 
           rev: CC43 scheme: MBR 
Partition: ID-1: / raw size: 461.62 GiB size: 453.30 GiB (98.20%) used: 4.73 GiB (1.0%) fs: ext4 
           dev: /dev/sda2 
           ID-2: /home raw size: 461.62 GiB size: 453.30 GiB (98.20%) used: 207.3 MiB (0.0%) 
           fs: ext4 dev: /dev/sda4 
           ID-3: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda3 
Sensors:   System Temperatures: cpu: 1.8 C mobo: N/A 
           Fan Speeds (RPM): N/A 
           GPU: device: radeon temp: 2 C device: radeon temp: 37 C 
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
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://la.mxrepo.com/mx/repo/ bullseye main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 195 Uptime: 10m Memory: 14.60 GiB used: 825.8 MiB (5.5%) Init: systemd 
           v: 247 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 

[m_pav]

I seem to have a few hardware issues compared to my current install
- I can only select a maximum screen resolution of 1280x1024. (graphic card not supported by new nouveau driver?)
- CPU identified as single core instead of dual core
- Shutdown hangs and doesn't complete

It may be that your machine has a similar issue to one of mine re: the shutdown.

Have a look at the file in /etc/modprobe.d/hang-on-shutdown.conf and you'll see it's fully commented out. If you've got any recent version of MX installed, check out the file on your own machine because it should be there. You only need to uncomment the last 2 lines in the file to try it, but one way or another, to test it, you'll have to boot either live or installed with the changed file.

Another thing to look at for such a system as yours is it may only be happy to run a 4.xx series kernel, which should be fully possible, though I have not tested on MX-21 yet.

You can either try an install if this is a spare machine, or you can try remastering the Live USB to incorporate a change to test. Remastering a single time is fully reversible, it can get trickier if you do it more than once. Let us know if you need help remastering the Live USB.

[Adrian]

Some packages that can be removed: exfat-fuse (it's now in kernel), gcc-9-base, gcc-10-base:i386 (in 64bit, and the rest of i386 stuff, do we need i386 for anything in 64bit?), mx19-archive-keyring.

[wdscharff]

After yesterday's announcement still quickly installed on the laptop, that the laptop does not accept every USB stick on every port as a boot device, has nothing to do with MX, he also did with opensuse and mint.
Laptop was still set to legacy, ran through without problems.

But it should be tested UEFI. This morning switched to UEFI (secure boot:off), disks on GPT with FAT32 ESP partition, the "rest" left unformatted.
And then times the first menu item taken, the system automatically set up (I have never done before). The only thing I had to do manually was to select as boot device and for Grub/ESP the NVME, because he wanted to take me every time the SSD. There probably everyone uses the same installer, somehow, opensuse and mint did the same :)

First impression: Great, super, impressive
Only the current RAM requirement with something around 750MB (the xfce beta is not better) is still suboptimal. I hope this will improve until the final release.

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: Fluxbox 1.3.5 info: tint2 dm: LightDM 1.26.0 
           Distro: MX-21_fluxbox_beta1_x64 Wildflower August 20  2021 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: Acer product: Aspire A717-71G v: V1.10 serial: <filter> 
           Mobo: KBL model: Charizard_KLS v: V1.10 serial: <filter> UEFI: Insyde v: 1.10 
           date: 08/22/2017 
Battery:   ID-1: BAT1 charge: 45.1 Wh condition: 45.1/48.9 Wh (92%) volts: 15.9/15.2 
           model: COMPAL PABAS0241231 type: Li-ion serial: <filter> status: Full 
CPU:       Topology: Quad Core model: Intel Core i5-7300HQ bits: 64 type: MCP arch: Kaby Lake 
           family: 6 model-id: 9E (158) stepping: 9 microcode: EA L2 cache: 6144 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19999 
           Speed: 2924 MHz min/max: 800/3500 MHz Core speeds (MHz): 1: 2396 2: 2308 3: 2338 
           4: 2391 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled 
           Type: mds mitigation: Clear CPU buffers; SMT disabled 
           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: disabled, RSB filling 
           Type: srbds mitigation: Microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel HD Graphics 630 vendor: Acer Incorporated ALI driver: i915 v: kernel 
           bus ID: 00:02.0 chip ID: 8086:591b 
           Device-2: NVIDIA GP107M [GeForce GTX 1050 Mobile] vendor: Acer Incorporated ALI 
           driver: N/A bus ID: 01:00.0 chip ID: 10de:1c8d 
           Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.3.5 
           direct render: Yes 
Audio:     Device-1: Intel CM238 HD Audio vendor: Acer Incorporated ALI driver: snd_hda_intel 
           v: kernel bus ID: 00:1f.3 chip ID: 8086:a171 
           Device-2: NVIDIA GP107GL High Definition Audio vendor: Acer Incorporated ALI 
           driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:0fb9 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter vendor: Lite-On 
           driver: ath10k_pci v: kernel port: 4000 bus ID: 02:00.0 chip ID: 168c:003e 
           IF: wlan0 state: down mac: <filter> 
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: Acer Incorporated ALI driver: r8169 v: kernel port: 3000 bus ID: 03:00.1 
           chip ID: 10ec:8168 
           IF: eth0 state: down mac: <filter> 
Drives:    Local Storage: total: 484.44 GiB used: 4.36 GiB (0.9%) 
           ID-1: /dev/nvme0n1 vendor: Intel model: SSDPEKKW256G7 size: 238.47 GiB block size: 
           physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter> 
           rev: PSF109C scheme: GPT 
           ID-2: /dev/sda vendor: Crucial model: CT256MX100SSD1 size: 238.47 GiB block size: 
           physical: 4096 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: MU01 
           scheme: GPT 
           ID-3: /dev/sdb type: USB vendor: SanDisk model: Cruzer size: 7.49 GiB block size: 
           physical: 512 B logical: 512 B serial: <filter> rev: 8.01 scheme: MBR 
Partition: ID-1: / raw size: 230.19 GiB size: 225.52 GiB (97.97%) used: 4.36 GiB (1.9%) 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: 43.5 C mobo: 29.8 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
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bullseye main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 200 Uptime: 6m Memory: 7.66 GiB used: 742.7 MiB (9.5%) 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 

Der Bericht wurde in die Zwischenablage des Systems kopiert
Der Bericht ist bereits für das Forum formatiert.
Direkt in den Forumsbeitrag einfügen

https://web57.ws/test/W-1_001.png

[chrispop99]

Just to clarify - the low battery alert only appears with desktop machines. It does not happen with laptops.

Chris

[kobaian]

Tested on live USB.
1. Very impressive look at the first glance.
2. "Low-battery" alert on a desktop PC is a little bit annoying.
3. There's a bug in "nobattery-tint2rc" - no "exit-options", browser icon instead. Probably there is one "P" missing in the config file.
4. I like simplicity, but the screenshoter is too simple for me, and makes posting screenshots much more complicated.
5. I think it would be useful adding GTK-greeter preferences to MX-Fluxbox-Settings.
6. On Polish translation there's a bug in RootMenu - an empty entry without any text leading to MX-Fluxbox-Settings. I haven't seen the problem in English default version.

[m_pav]

Some packages that can be removed: exfat-fuse (it's now in kernel), gcc-9-base, gcc-10-base:i386 (in 64bit, and the rest of i386 stuff, do we need i386 for anything in 64bit?), mx19-archive-keyring.

Thanks Adrian, I've removed exfat-fuse and mx19-archive-keyring from the build package list.

As for the three i386 packages in the 64-bit build listed below, they are connected with our disk/partition encryption and earlier releases like MX-19_AHS have the same 3 Debian Buster equivalents of the i386 packages installed.

The i386 packages are not in any of the 64-bit package lists so they're automatically installed and I think removing them would break disk/partition encryption. When I tested this in a VM, apt gave me it's most dire warnings

Code: Select all

This should NOT be done unless you know exactly what you are doing

Code: Select all

You are about to do something potentially harmful 

and would not proceed unless I typed the venerable

Code: Select all

Yes, do as I say!

When that message comes up, you can be sure something's going to break.

gcc-10-base:i386
libc6:i386
libgcc-s1:i386

[Jerry3904]

Just to clarify - the low battery alert only appears with desktop machines. It does not happen with laptops.

Chris

Big clarification, thanks. That's on the top of my list for today.

[Jerry3904]

On the low battery message: this band-aid should work (on my laptop early in the morning, can't test).

1) open /.config/tint2/tint2rc in geany or featherpad
2) search for

Code: Select all

battery_low_cmd = xmessage 'tint2: Battery low!'

3) delete the message so it looks like this

Code: Select all

battery_low_cmd = 

4) save and close

Still looking for the desktop low message problem itself...

[Jerry3904]

There's a bug in "nobattery-tint2rc" - no "exit-options", browser icon instead. Probably there is one "P" missing in the config file.

I'll have to wait to see if anyone else reports this b/c the icon link is correct and I've not had a problem on the various machines I've tested on so far.

5. I think it would be useful adding GTK-greeter preferences to MX-Fluxbox-Settings.

It should show up in MX Tools, where it belongs IMO as an advanced tool. But it's not there so will have to look at the desktop file.