MX Linux Forum

Hello, first of all congratulations on this new MX version, we all hope for an RC soon.
Two remarks only:
- Firstly, the installation of the tool with personal partitions is less clear than it was with the previous version of MX: it is not clear whether /home will not be formatted. That's why I finally gave up on doing this installation. Please keep in mind that most of all users want to be sure that they don't lose their data. It is already a weakness of MX that a new install is needed at each new Debian stable, so the installation tool must be completely clear, and I must say that a net-install of Debian stable, certainly less sexy, seems nevertheless more secure for me.
- Second, clearly the wallpaper is nice but not adapted to this configuration of the conky by default: we do not see the details of informations.
Hope this helps.
Best wishes,
Jo.

joseph.vidal-rosset wrote: Fri Sep 03, 2021 2:58 am Hello, first of all congratulations on this new MX version, we all hope for an RC soon.
Two remarks only:
- Firstly, the installation of the tool with personal partitions is less clear than it was with the previous version of MX: it is not clear whether /home will not be formatted. That's why I finally gave up on doing this installation. Please keep in mind that most of all users want to be sure that they don't lose their data. It is already a weakness of MX that a new install is needed at each new Debian stable, so the installation tool must be completely clear, and I must say that a net-install of Debian stable, certainly less sexy, seems nevertheless more secure for me. ...

Please let us know which items/parts/descriptions in the installer you felt were not clear. It would help us in assessing the current installer.

I noticed this as well, the text in the drop-down ("/home without reformatting" or some such) is too wide to be clearly readable, perhaps the control could be made wider or the fulll text displayed as a tooltip ?

Hello. First what is confusing is that we clearly see a box to encryption, but no box to format. Second, to preserve /home from formatting we see (in French) /Présev that's it.
In my opinion, It would be clearer to see a empty box to check for formatting the partition or to leave blank to avoid it.

Will probably affect all MX betas ... but I currently have only the Fluxbox (and the beta thread is locked).

What I was annoyed about before because the distances are so long and I (I think) did not have the problem with the 19_ahs and I have to google for it every time anew :)
on my laptop i have to use bluetooth, the built in speakers are an insult to the ears, at best you can listen to news with them, they sound even worse than they already are anyway.
I use a small Marshall Killburn for this.
Bluetooth error message:
Bluetooth: "protocol not available"

It's no real consolation now, that this occurs with many other distributions too, that's why you can find the solution in google right away, but w*f, why isn't the "pulseaudio-bluetooth" installed at the same time. Most will probably use Bluetooth like me to operate speakers / headphones.
Whereby a timid beginner can of course still fail because the driver under Debian/MX is called "pulseaudio-module-bluetooth" :)

I am not able to boot any usb with MX-21_beta1_x64 on my old hp laptop model dv6-7210us. Upon powering up the boot just hangs with a dark screen (not even displaying the boot grub menu).

I've tried without success:

- using different bootable usb creators to create the live usb: balena etcher, rufus, unetbootin, win32diskimager

- using other usb sticks

- turning off secure boot on the hp dv6 laptop

The same mxlinux usb stick unbootable on the dv6 would boot fine on my other laptops (acer, toshiba) -- so there is no integrity issue with the usb stick or the software image.

The hp dv6 laptop can boot the same usb stick when it contains MX-19 or another linux distro (such as mint, arcolinux, skylinux, etc.) -- hence it seems there is some incompatibility between the MX-21 build and the dv6 hardware.

Info on the laptop (reported while running Mint):

digixmax wrote: Sat Sep 04, 2021 3:57 pm I am not able to boot any usb with MX-21_beta1_x64 on my old hp laptop model dv6-7210us. Upon powering up the boot just hangs with a dark screen (not even displaying the boot grub menu).

I've tried without success:

- using different bootable usb creators to create the live usb: balena etcher, rufus, unetbootin, win32diskimager

- using other usb sticks

- turning off secure boot on the hp dv6 laptop

The same mxlinux usb stick unbootable on the dv6 would boot fine on my other laptops (acer, toshiba) -- so there is no integrity issue with the usb stick or the software image.

The hp dv6 laptop can boot the same usb stick when it contains MX-19 or another linux distro (such as mint, arcolinux, skylinux, etc.) -- hence it seems there is some incompatibility between the MX-21 build and the dv6 hardware.

Info on the laptop (reported while running Mint):

Code: Select all

System:    Kernel: 5.4.0-81-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Xfce 4.16.0
           tk: Gtk 3.24.20 wm: xfwm4 dm: LightDM Distro: Linux Mint 20.2 Uma
           base: Ubuntu 20.04 focal
Machine:   Type: Laptop System: Hewlett-Packard product: HP ENVY dv6 Notebook PC
           v: 088B110000305910000620100 serial: <filter> Chassis: type: 10 serial: <filter>
           Mobo: Hewlett-Packard model: 182D v: 55.25 serial: <filter> UEFI: Insyde v: F.25
           date: 08/04/2014
Battery:   ID-1: BAT0 charge: 21.0 Wh condition: 21.0/21.0 Wh (100%) volts: 12.5/10.8
           model: 11-85 MO06047 serial: <filter> status: Full
CPU:       Topology: Quad Core model: AMD A8-4500M APU with Radeon HD Graphics bits: 64 type: MCP
           arch: Piledriver rev: 1 L2 cache: 2048 KiB
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 15170
           Speed: 1242 MHz min/max: 1400/1900 MHz Core speeds (MHz): 1: 1600 2: 1619 3: 1348
           4: 1375
Graphics:  Device-1: AMD Trinity [Radeon HD 7640G] vendor: Hewlett-Packard driver: radeon
           v: kernel bus ID: 00:01.0 chip ID: 1002:9903
           Display: x11 server: X.Org 1.20.11 driver: ati,radeon unloaded: fbdev,modesetting,vesa
           resolution: 1366x768~60Hz
           OpenGL: renderer: AMD ARUBA (DRM 2.50.0 / 5.4.0-81-generic LLVM 12.0.0)
           v: 4.3 Mesa 21.0.3 compat-v: 3.1 direct render: Yes
Audio:     Device-1: AMD Trinity HDMI Audio vendor: Hewlett-Packard driver: snd_hda_intel
           v: kernel bus ID: 00:01.1 chip ID: 1002:9902
           Device-2: AMD FCH Azalia vendor: Hewlett-Packard driver: snd_hda_intel v: kernel
           bus ID: 00:14.2 chip ID: 1022:780d
           Sound Server: ALSA v: k5.4.0-81-generic
Network:   Device-1: Qualcomm Atheros AR9485 Wireless Network Adapter
           vendor: Hewlett-Packard AR9485/HB125 802.11bgn 1×1 Wi-Fi driver: ath9k v: kernel
           port: 3100 bus ID: 02:00.0 chip ID: 168c:0032
           IF: wlo1 state: up mac: <filter>
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
           vendor: Hewlett-Packard driver: r8169 v: kernel port: 2000 bus ID: 04:00.0
           chip ID: 10ec:8168
           IF: eno1 state: down mac: <filter>
Drives:    Local Storage: total: 698.64 GiB used: 10.26 GiB (1.5%)
           ID-1: /dev/sda vendor: Hitachi model: HTS547575A9E384 size: 698.64 GiB speed: 3.0 Gb/s
           serial: <filter>
Partition: ID-1: / size: 686.18 GiB used: 10.25 GiB (1.5%) fs: ext4 dev: /dev/sda2
USB:       Hub: 1-0:1 info: Full speed (or root) Hub ports: 5 rev: 2.0 chip ID: 1d6b:0002
           Device-1: 1-4:3 info: Chicony HP Truevision HD type: Video driver: uvcvideo rev: 2.0
           chip ID: 04f2:b2f8
           Hub: 2-0:1 info: Full speed (or root) Hub ports: 5 rev: 1.1 chip ID: 1d6b:0001
           Device-2: 2-3:2 info: Validity Sensors Fingerprint scanner type: <vendor specific>
           driver: N/A rev: 1.1 chip ID: 138a:0018
           Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 chip ID: 1d6b:0002
           Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.0 chip ID: 1d6b:0003
           Hub: 5-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 chip ID: 1d6b:0002
           Hub: 6-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.0 chip ID: 1d6b:0003
Sensors:   System Temperatures: cpu: 59.2 C mobo: N/A gpu: radeon temp: 30 C
           Fan Speeds (RPM): N/A

Suggest to create a LiveUSB using MX Live USB Maker, e.g. running on another PC.
Try to plugin the LiveUSB directly into an USB-port on the laptop incase it fails to boot from a USB-HUB.
Also do make sure you have verified the downloade ISO-file. Even if it successfully boots on one PC,
on another PC some other modules are probably needed to read from the USB, which might
be corrupted on the downloaded ISO-files already.

I'd like to add that on some of the HPs from that era, the only working option is to boot from a DVD and on some others, you have to enter the bios and set all the boot options to usb in order to get it to work.

There is a beta 2 thread available, this one is now locked.