MX-18 beta 1 feedback

[chrispop99]

Well this is fun! Just received an MSI U135 from one of our users for testing purposes, and the beta runs OK, if a bit slow. It seems that everything is functioning normally:

Code: Select all

System:    Host: mx1 Kernel: 4.19.0-1-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0 
           Desktop: Xfce 4.12.3 Distro: MX-18b1_x64 Continuum December 3  2018 
           base: Debian GNU/Linux 9 (stretch) 
Machine:   Type: Laptop System: MICRO-STAR product: MS-N014 v: REV:1.0 serial: <filter> 
           Mobo: MICRO-STAR model: MS-N014 v: REV:1.0 serial: <filter> BIOS: American Megatrends 
           v: EN014IMS.30k date: 01/08/2010 
Battery:   ID-1: BAT1 charge: 45.5 Wh condition: 48.2/48.8 Wh (99%) model: MSI Corp. MS-N014 
           status: Charging 
           Device-1: hidpp_battery_0 model: Logitech Wireless Mouse charge: Normal 
           status: Discharging 
CPU:       Topology: Single Core model: Intel Atom N450 bits: 64 type: MT arch: Bonnell rev: A 
           L2 cache: 512 KiB 
           flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 6649 
           Speed: 1599 MHz min/max: 1000/1667 MHz Core speeds (MHz): 1: 1238 2: 1233 
Graphics:  Device-1: Intel Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics driver: i915 
           v: kernel bus ID: 00:02.0 
           Display: x11 server: X.Org 1.19.2 driver: intel resolution: 1024x600~60Hz 
           OpenGL: renderer: Mesa DRI Intel Pineview M v: 1.4 Mesa 18.2.6 direct render: Yes 
Audio:     Device-1: Intel NM10/ICH7 Family High Definition Audio driver: snd_hda_intel 
           v: kernel bus ID: 00:1b.0 
           Sound Server: ALSA v: k4.19.0-1-amd64 
Network:   Device-1: Qualcomm Atheros AR9285 Wireless Network Adapter driver: ath9k v: kernel 
           port: f000 bus ID: 01:00.0 
           IF: wlan0 state: up mac: <filter> 
           Device-2: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet driver: r8169 
           v: kernel port: e000 bus ID: 02:00.0 
           IF: eth0 state: down mac: <filter> 
Drives:    Local Storage: total: 122.04 GiB used: 1.33 GiB (1.1%) 
           ID-1: /dev/sda vendor: Toshiba model: MK1032GSX size: 93.16 GiB 
           ID-2: /dev/sdb type: USB vendor: PNY model: USB 3.0 FD size: 28.88 GiB 
Partition: ID-1: / size: 1.51 GiB used: 258.9 MiB (16.7%) fs: overlay dev: ERR-102 
Sensors:   System Temperatures: cpu: 45.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb http://iso.mxrepo.com/antix/stretch stretch main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://ftp.us.debian.org/debian/ stretch-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://ftp.us.debian.org/debian/ stretch main contrib non-free
           2: deb http://security.debian.org/ stretch/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ stretch main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 172 Uptime: 9m Memory: 1.94 GiB used: 651.7 MiB (32.8%) Init: SysVinit 
           runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.25 

One of my test machines is Atom-based, and also works without issue.

Chris

[Gerson]

My report MX 18 beta after 5 days of use without problem, except that the Conky when clicking on the desktop disappears:

Code: Select all

System:    Host: Compaq 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: Laptop System: COMPAQ product: Presario 21 VerK v: N/A serial: <root required> 
           Mobo: EA model: K21 v: Type2 - Board Version serial: <root required> UEFI: COMPAQ 
           v: fd date: 02/27/2016 
Battery:   ID-1: BAT1 charge: 46.1 Wh condition: 48.1/N/A Wh 
CPU:       Topology: Dual Core model: Intel Core i3-6100U bits: 64 type: MT MCP 
           L2 cache: 3072 KiB 
           Speed: 900 MHz min/max: 400/2300 MHz Core speeds (MHz): 1: 900 2: 902 3: 900 4: 900 
Graphics:  Device-1: Intel HD Graphics 520 driver: i915 v: kernel 
           Display: x11 server: X.Org 1.19.2 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2) v: 4.5 Mesa 18.2.6 
Audio:     Device-1: Intel Sunrise Point-LP HD Audio 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: up speed: 100 Mbps duplex: full mac: 00:e0:4c:69:89:db 
           Device-2: Intel Wireless 3160 driver: iwlwifi 
           IF: wlan0 state: up mac: 78:0c:b8:f4:da:30 
Drives:    Local Storage: total: 931.51 GiB used: 367.59 GiB (39.5%) 
           ID-1: /dev/sda vendor: HGST (Hitachi) model: HTS541010A7E630 size: 931.51 GiB 
Partition: ID-1: / size: 22.57 GiB used: 6.07 GiB (26.9%) fs: ext4 dev: /dev/sda2 
           ID-2: /home size: 95.62 GiB used: 29.19 GiB (30.5%) fs: ext4 dev: /dev/sda3 
           ID-3: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda4 
Sensors:   System Temperatures: cpu: 36.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Info:      Processes: 210 Uptime: 16m Memory: 3.77 GiB used: 1.13 GiB (30.1%) Shell: bash 
           inxi: 3.0.25

[asqwerth]

A lot depends on the way a particular conky config was written, and its interaction with your desktop, what compositing and window manager you use, etc.

You could probably ask in the conky thread, male might be able to solve the issue if you provide your conky config in your post there.

If it's solved, let us know . But it may not be a solution that requires changing the beta packages. Others may or may not have the same issue. Let's see .

[Ghost67]

No problems to report back here as yet, aside from Steam not installing due to certain 32bit packages being held back. Not a problem for daily use though.
Possibly I can fix by using another repo but I'm not prepared to change defaults, regardless of the OS. I'm a stickler like that :)

[Paul..]

Ryzen crash update -- This looks like a keeper

Asus Prime X470-Pro motherboard w/Ryzen 5 1400 CPU...stable for 5 hours...and will keep it running overnight

- OS version: MX-18b1_x64 Continuum December 3 2018
- Kernel: 4.15.5-antix.1-amd64-smp
- UEFI setup: Advanced->AMD CBS ->Power Supply Idle Control->Typical Current Idle
- Boot option: Not using "rcu_nocbs=0-7"

@entropyfoe Kernel: 4.19.0-1-amd64 is good with config above (this kernel does not support "rcu_nocbs" option) ...Uptime: 12h 30m
will test 4.15.5-antix.1-amd64-smp (which does support "rcu_nocbs option) all day today

@caprea...many thanks for pointing us all to the UEFI setup for these Asus Motherboards

[Richard]

MX Boot Options changes not sticking...
moved to ... viewtopic.php?f=108&t=47262#p470901

[anticapitalista]

Paul, How is that typical idle current stetting working? With or without the rcu_nocbs?

I was able to use the MX Package installer to get the 4.19-antix kernel, which I have installed. All went smoothly, updated the grubs, and am posting from MX18 b1 with the 4.19.4-antix.1 kernel.
I think the LTS support of this kernel will make it useful to us and attractive to the potential users. This should be stressed in the PR and distrowatch pronouncements !

The hypothesis is, the antix kernels have some rcu option set that makes the rcu_ncbs=0-11 effective. For me this was certainly true with the 4.15 antix kernel.
So now I will test for stability, before it was three crashes in two days.

Depending on what Paul finds, I may update the BIOS. This idle current setting, most say it fixes it, though a minority on the amd boards say they still get crashes.

antiX now has 4.19.7-antix.1 kernel

[Paul..]

Thanks, anti. I will add that to the list to test.

[entropyfoe]

Thanks anti, what is the advantage of running the 4.19.7 over the 4.19.4?
More security patches?

So far the antix kernel has remained up for >12 hours, encouraging, but too early to claim stability. I should be more confident by say Sunday night.
Paul, the MX kernel, as you wrote does not support the rcu_nocbs, so that explains why we had the crashes.

I will test this kernel for a few days. I downloaded the latest BIOS and have it ready for testing after I see that the kernel approach is stable.
It makes sense that the motherboard manufacturers would figure a way to fix this with a BIOS change. I hope that works of you, and then me !

[Paul..]

Thanks anti, what is the advantage of running the 4.19.7 over the 4.19.4?
More security patches?

So far the antix kernel has remained up for >12 hours, encouraging, but too early to claim stability. I should be more confident by say Sunday night.
Paul, the MX kernel, as you wrote does not support the rcu_nocbs, so that explains why we had the crashes.

I will test this kernel for a few days. I downloaded the latest BIOS and have it ready for testing after I see that the kernel approach is stable.
It makes sense that the motherboard manufacturers would figure a way to fix this with a BIOS change. I hope that works of you, and then me !

Looks like one difference is:
4.19.7-antix.1-amd64-smp (does not support rcu_nocbs)
4.19.4-antix.1-amd64-smp (does support rcu_nocbs)