MX-18 beta 1 feedback

[Paul..]

Asus motherboard + AMD Ryzen crash testing with various kernels --

Base Test System
OS: MX-18b1_x64 (Upgraded from devrepo)
Motherboard: Asus Prime X470-Pro
CPU: AMD Ryzen 5 1400
UEFI option: Advanced->AMD CBS ->Power Supply Idle Control->Typical Current Idle
Kernel option: Not using "rcu_nocbs..."

Kernels that tested stable so far (5+ hours)
- 4.15.5-antix.1-amd64-smp
- 4.19.0-1-amd64
- 4.19.4-antix.1-amd64-smp
- 4.19.7-antix.1-amd64-smp
EDIT: 4.19.8-antix.1-amd64-smp

Conclusion: Best avenue appears to be using "Typical Current Idle" setting available via upgraded UEFI firmware

[Gerson]

Suggestion to translate into Spanish: "Cento Multimedia" (Multimedia center) no "Centro de medias"; (medias = socks)

[anticapitalista]

Used live-usb-maker to make an encrypted live stick (32 bit version), but on first boot on this T60, I get this error.

Failed to set up dm-crypt key mapping for device /dev/sdb2
Check that kernel supports aes-xts-plin64 cipher

Using live-ub-maker without encryption and the stick boots fine and beta1 works well even live (usb2)

[richb]

Used live-usb-maker to make an encrypted live stick (32 bit version), but on first boot on this T60, I get this error.

Failed to set up dm-crypt key mapping for device /dev/sdb2
Check that kernel supports aes-xts-plin64 cipher

Using live-ub-maker without encryption and the stick boots fine and beta1 works well even live (usb2)

Made an encrypted live stick (64 bit version), first boot on AMD desktop booted to desktop after asking to set encryption password and asking for same password to continue.. Posted this for another data point.

Code: Select all

System:    Host: mx Kernel: 4.19.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3 
           Distro: MX-18b1_x64 Continuum December 3  2018 
Machine:   Type: Desktop System: Gigabyte product: N/A v: N/A serial: <root required> 
           Mobo: Gigabyte model: F2A68HM-H v: x.x serial: <root required> UEFI: American Megatrends v: FB 
           date: 04/22/2015 
CPU:       Topology: Quad Core model: AMD A8-7600 Radeon R7 10 Compute Cores 4C+6G bits: 64 type: MCP 
           L2 cache: 2048 KiB 
           Speed: 1828 MHz min/max: 1400/3100 MHz Core speeds (MHz): 1: 1821 2: 1811 3: 1523 4: 1471 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Kaveri [Radeon R7 Graphics] driver: radeon v: kernel 
           Display: x11 server: X.Org 1.19.2 driver: ati,radeon unloaded: fbdev,modesetting,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: AMD KAVERI (DRM 2.50.0 4.19.0-1-amd64 LLVM 7.0.0) v: 4.5 Mesa 18.2.6 
Audio:     Device-1: Advanced Micro Devices [AMD/ATI] Kaveri HDMI/DP Audio driver: snd_hda_intel 
           Device-2: Advanced Micro Devices [AMD] FCH Azalia driver: snd_hda_intel 
           Sound Server: ALSA v: k4.19.0-1-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 
           IF: eth0 state: down mac: 40:8d:5c:0d:62:1b 
           Device-2: Qualcomm Atheros AR93xx Wireless Network Adapter driver: ath9k 
           IF: wlan0 state: up mac: 60:e3:27:08:b6:6c 
Drives:    Local Storage: total: 757.78 GiB used: 116.94 GiB (15.4%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB 
           ID-2: /dev/sdb vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB 
           ID-3: /dev/sdc vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB 
           ID-4: /dev/sdd type: USB vendor: PNY model: USB 3.0 FD size: 59.12 GiB 
Partition: ID-1: / size: 225.02 GiB used: 14.97 GiB (6.7%) fs: ext4 dev: /dev/sda2 
           ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda3 
Sensors:   System Temperatures: cpu: 10.1 C mobo: N/A gpu: radeon temp: 12 C 
           Fan Speeds (RPM): N/A 
Info:      Processes: 238 Uptime: 5m Memory: 14.69 GiB used: 1.16 GiB (7.9%) Shell: bash inxi: 3.0.25

[chrispop99]

Used live-usb-maker to make an encrypted live stick (32 bit version), but on first boot on this T60, I get this error.

Failed to set up dm-crypt key mapping for device /dev/sdb2
Check that kernel supports aes-xts-plin64 cipher

Using live-ub-maker without encryption and the stick boots fine and beta1 works well even live (usb2)

Problem confirmed with Dell D610.

Chris

[manyroads]

Just a quick update on my three MX18 pcs. All are working exceptionally well with only tiny items / errors noted.

• I had one Dell Latitude lose both its mouse and trackpad. I can not get the error to repeat. A shutdown/ reboot fixed things, I think.

• I experience a usability issue writing a Personal backup to USB. My USB was too small and the dd (LiveUSB creation function) abended (old geek's term) without a helpful error message. Replacing the USB with a larger capacity USB allowed the USB to write successfully. A pre-test for USB size appropriateness test would be helpful. Minimally a better error message would help.

Otherwise, the system seems exceptionally 'smooth' and polished, to me and my little user community of three test users/machines.

[entropyfoe]

Paul,

So you have total >25 hours with the idle current typical setting with different kernels, and no rcu_nocbs.
That is encouraging.


I crashed with the antix kernel AND rcu_nocbs, so....
Last night I installed the latest BIOS (4024) and rebooted with the idle current set to typical (default was AUTO).

SO far 16 hours, but it will take a few days to be sure.

Other than the Ryzen specific problem, the beta1 is running smoothly.
The crashes were only at idle, when running actively, never a problem.

[Paul..]

Paul,

So you have total >25 hours with the idle current typical setting with different kernels, and no rcu_nocbs.
That is encouraging.


I crashed with the antix kernel AND rcu_nocbs, so....
Last night I installed the latest BIOS (4024) and rebooted with the idle current set to typical (default was AUTO).

SO far 16 hours, but it will take a few days to be sure.

Other than the Ryzen specific problem, the beta1 is running smoothly.
The crashes were only at idle, when running actively, never a problem.

4024 is the same version as I installed...looking good!

[dolphin_oracle]

Used live-usb-maker to make an encrypted live stick (32 bit version), but on first boot on this T60, I get this error.

Failed to set up dm-crypt key mapping for device /dev/sdb2
Check that kernel supports aes-xts-plin64 cipher

Using live-ub-maker without encryption and the stick boots fine and beta1 works well even live (usb2)

I'm looking at the kernel configs for hte 64bit vs. the 32 bit and I'm not seeing a big difference. these are the items with aes in them.

Code: Select all

CONFIG_CRYPTO_AES=y
# CONFIG_CRYPTO_AES_TI is not set
CONFIG_CRYPTO_AES_586=m
CONFIG_CRYPTO_AES_NI_INTEL=m

and

Code: Select all

CONFIG_CRYPTO_DEV_PADLOCK_AES=m

they appear to be the same in both kernels.

any other ideas where to look?

[Old Giza]

Suggestion to translate into Spanish: "Cento Multimedia" (Multimedia center) no "Centro de medias"; (medias = socks)

Done. Changed to "Centro multimedia" as per screenshot. (It will come through normal updates, not necessarily with MX-18 release.)