Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

MX-18 beta 1 feedback

Message
Author
User avatar
Paul..
Forum Guide
Forum Guide
Posts: 2306
Joined: Sun Mar 18, 2007 6:34 pm

Re: MX-18 beta 1 feedback

#251 Post by Paul.. » Sat Dec 08, 2018 9:17 pm

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

Asus Prime X470-Pro
AMD Ryzen 5 1400 (8 threads)
16 Gig DDR4 3000
Nvidia - GeForce GTX 750 Ti
Samsung 970 NVMe SSD nvme0n1P2=MX-18
500GB SSD sda1= Data

User avatar
Gerson
Forum Regular
Forum Regular
Posts: 360
Joined: Sun Nov 12, 2017 10:58 am

Re: MX-18 beta 1 feedback

#252 Post by Gerson » Sun Dec 09, 2018 7:29 am

Suggestion to translate into Spanish: "Cento Multimedia" (Multimedia center) no "Centro de medias"; (medias = socks)
You do not have the required permissions to view the files attached to this post.
No todos ignoramos las mismas cosas. :confused:

User avatar
anticapitalista
Forum Veteran
Forum Veteran
Posts: 5827
Joined: Sat Jul 15, 2006 10:40 am

Re: MX-18 beta 1 feedback

#253 Post by anticapitalista » Sun Dec 09, 2018 8:07 am

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)
anticapitalista
Reg. linux user #395339.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX-17 "Heather Heyer" - lean and mean.
https://antixlinux.com

User avatar
richb
Administrator
Posts: 17490
Joined: Wed Jul 12, 2006 2:17 pm

Re: MX-18 beta 1 feedback

#254 Post by richb » Sun Dec 09, 2018 8:39 am

anticapitalista wrote:
Sun Dec 09, 2018 8:07 am
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
Forum Rules
Guide - How to Ask for Help

Rich
SSD Production: MX 17.1
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB, 350 GB HD

User avatar
chrispop99
Forum Guide
Forum Guide
Posts: 2497
Joined: Tue Jan 27, 2009 3:07 pm

Re: MX-18 beta 1 feedback

#255 Post by chrispop99 » Sun Dec 09, 2018 10:24 am

anticapitalista wrote:
Sun Dec 09, 2018 8:07 am
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
Test machines:
32-bit non-PAE - Thinkpad T41, 1.6GHz Pentium M, 1GB RAM.
32-bit PAE - DELL Latitude D610, 1.73GHz Pentium M, 2GB RAM.
64-bit - Lenovo T61, 2GHz Core 2 Duo, 2GB RAM
64-bit - Gigabyte Z77P-D3, Intel i3-3220, GeForce 8400 GS, 4GB PC3-12800.

User avatar
manyroads
Forum Regular
Forum Regular
Posts: 206
Joined: Sat Jun 30, 2018 6:33 pm

Re: MX-18 beta 1 feedback

#256 Post by manyroads » Sun Dec 09, 2018 10:41 am

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. :happy:
Pax vobiscum,
ManyRoads (Mark Rabideau)
http://many-roads.com
MX-18b1_x64 Continuum
Platform: Dell Latitude E5470
CPU: Dual Core Intel i5-6300U (-MT MCP-)
Mem: 8GB SSD: 978.09 GiB
Reg. Linux User #449130
:bagoverhead:

User avatar
entropyfoe
Forum Regular
Forum Regular
Posts: 848
Joined: Thu Apr 19, 2007 11:42 am

Re: MX-18 beta 1 feedback

#257 Post by entropyfoe » Sun Dec 09, 2018 10:58 am

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.
Asus Prime 370X-Pro
AMD Ryzen 1600X (12 threads @ 3.6 GHz)
16 Gig DDR4 3200 (G Skill)
Nvidia -MSI GeForce GT 710 fanless
Samsung 960 NVMe SSD nvme0n1 P1-3=MX-17.1, P4=MX 18 betas
1TB SSD sda1= Data, 2TB WD =backups
on-board ethernet & sound

User avatar
Paul..
Forum Guide
Forum Guide
Posts: 2306
Joined: Sun Mar 18, 2007 6:34 pm

Re: MX-18 beta 1 feedback

#258 Post by Paul.. » Sun Dec 09, 2018 11:24 am

entropyfoe wrote:
Sun Dec 09, 2018 10:58 am
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!

Asus Prime X470-Pro
AMD Ryzen 5 1400 (8 threads)
16 Gig DDR4 3000
Nvidia - GeForce GTX 750 Ti
Samsung 970 NVMe SSD nvme0n1P2=MX-18
500GB SSD sda1= Data

User avatar
dolphin_oracle
Forum Veteran
Forum Veteran
Posts: 10052
Joined: Sun Dec 16, 2007 1:17 pm

Re: MX-18 beta 1 feedback

#259 Post by dolphin_oracle » Sun Dec 09, 2018 11:25 am

anticapitalista wrote:
Sun Dec 09, 2018 8:07 am
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?
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad T530 - MX-17
lenovo s21e & 100s - antiX-17, MX17(live-usb)
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
Old Giza
Forum Regular
Forum Regular
Posts: 380
Joined: Wed Apr 16, 2014 10:31 pm

Re: MX-18 beta 1 feedback

#260 Post by Old Giza » Sun Dec 09, 2018 12:11 pm

Gerson wrote:
Sun Dec 09, 2018 7:29 am
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.)

Post Reply

Return to “General”