MX-18 beta 1 feedback

[richb]

You are not newbie

... after a week of use a newbie would ...

... probably rarely open the Welcome screen anyway, if at all. :lipsrsealed:

Me either but we are not newbies.

[dreamer]

I agree with fehlix. Windows that disappear and reappear are not good UX design. Good UX design is predictable. Like the physical world. Things don't appear and disappear without physical interaction. It's the basics of the desktop metaphor. Each window is a real world folder or document. You can put them away by minimizing them or closing them.

I respect that other people might prefer a more "slick" experience, I'm old-fashioned.

So yes, my opinion is that MX Tools window is equally annoying.

I grew up with PCs, not smartphones so the desktop metaphor is pretty strong in me and so is old-school thinking.

[Adrian]

OK, let's end this discussion about MX Welcome, the code is changed, D_O will review it later on today.

[Fornhamfred]

On my Mx17 upgraded to 18 beta the login screen is displayed momentarily during shutdown. Just tested my fresh MX18 install and that does the same.

[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"

Note: will test other kernels tomorrow.

[mmikeinsantarosa]

How can I place a screensaver? The option does not appear and neither Grub-customizer.

You may see screensavers in mxpi soon. And use mx boot options instead of grub customizer.

mike

[Jerry3904]

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 

[Gerson]

@mmikeinsantarosa
With MX boot options I can only change the background of the grub but I like to change the color of the typefaces.

[richb]

@mmikeinsantarosa
With MX boot options I can only change the background of the grub but I like to change the color of the typefaces.

You can install grub-customizer from the repos.

[entropyfoe]

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.