MX Linux Forum • MX-17 to MX-18 update testing

Page 1 of 1

MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 8:27 am

by dolphin_oracle

Since debian stretch base hasn't changed, existing MX-17 users will automatically receive packages that are currently included in the MX-18 beta 1 iso.

We would like to get some early testing and feedback on the updates. Here's how you can enable those updates early and help us out!

1. Enable the dev repo: create a file called /etc/apt/sources.list.d/devrepo.list

2. include these contents in that file

Code: Select all

deb http://mxrepo.com/mx/testrepo/  mx18  dev

3. run the following:

Code: Select all

sudo apt-get update && sudo apt-get dist-upgrade

And that's it!

Here are some other details.

1. the kernel will not auto-update. Once we near release, we will have a new kernel entry in MX-PackageInstaller->Popular Apps=>Kernels with the new kernel.

2. your home folder will not be touched during the update. No xfce settings should be changed by the update, so things like wallpapers and theme selections should not change.

3. You can use the MX-Tweak "reset defaults" options to pull in the new thunar custom right-click menu actions and the new lightdm greeter configuration, if you desire.

Those running the current MX Beta 1 can also enable the devrepo to enable installation nvidia drivers via the nvidia-driver tool.

The plan is that all packages in the devrepo will move to our main repo before final release of the MX-18 iso.

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 8:50 am

by Raitsa

All good here after the upgrade:

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 9:34 am

by richb

Upgrade from 17.1 ran smoothly, no issues with the result.

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 10:26 am

by male

Code: Select all

inxi -S
System:    Host: mx Kernel: 4.15.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3 
           Distro: MX-18_x64 Continuum March 14  2018

No problems detected so far

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 10:41 am

by Redacted

Got ton of updates, but still shows

Code: Select all

 inxi -S
System:    Host: lenovo-mx Kernel: 4.15.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3 
           Distro: MX-17.1_x64 Horizon March 14  2018

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 10:44 am

by asqwerth

Redacted wrote: Tue Dec 04, 2018 10:41 am Got ton of updates, but still shows
Code: Select all
 inxi -S
System:    Host: lenovo-mx Kernel: 4.15.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3 
           Distro: MX-17.1_x64 Horizon March 14  2018

That's strange.

Mine changed to "Continuum" after updating.

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 10:47 am

by Adrian

Things worked fine here, but I don't use Nvidia so I cannot really report on that update.

Q: After the update should people remove or keep the dev repo enabled? I don't think we'll add stuff to dev repo, right?

EDIT, the release name shows correctly for me (maybe it needs a reboot)

Code: Select all

Distro: MX-18_x64 Continuum March 14  2018

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 10:49 am

by richb

Mine shows as MX-17.b3_x64 Continuum November 29 2017. That is weird.

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 10:58 am

by Redacted

I did a sudo updatedb and rebooted.
I chose to keep something the same during the update - don't remember what it was.

That could be the reason.

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 11:00 am

by chrispop99

Update completed successfully:

Code: Select all

chris@mx17-18test:~/Desktop
$ inxi -S
System:    Host: mx17-18test Kernel: 4.15.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3 
           Distro: MX-18_x64 Continuum March 14  2018

Only anomaly is the date.

Chris

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 11:01 am

by asqwerth

Redacted wrote: Tue Dec 04, 2018 10:58 am I did a sudo updatedb and rebooted.
I chose to keep something the same during the update - don't remember what it was.
That could be the reason.

Maybe one of the version release files in /etc/ folder?

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 11:09 am

by PondLife

58 packages upgraded, 11 new install. Had some warnings about unable to delete old directory's which I assume was to do with not touching the home folder, other than that everything looks good.

Code: Select all

$ inxi -S
System:
  Host: mx Kernel: 4.18.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3 
  Distro: MX-18_x64 Continuum March 14  2018

Adrian beat me to the dev repo enabled question.

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 11:19 am

by Paul..

Fresh install of Adrian's 17.1 November snapshot, UEFI, fully upgraded, added new repo...upgrade all went fine...tested Nvidia driver installer OK.

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 11:24 am

by Adrian

I have an issue on my system not sure if caused of this or I borked the system before (which is probable) I don't see anything in Settings, no icons, nothing. Any idea how to fix this? (and just to be sure please check if that is OK for you)

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 11:28 am

by dolphin_oracle

richb wrote: Tue Dec 04, 2018 10:49 am Mine shows as MX-17.b3_x64 Continuum November 29 2017. That is weird.

a long time ago we decided to support upgrades from RC but not from beta, so betas will not be changed by the version string script.

neither is the date, so we can tell what iso a distro started from if need be.

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 11:30 am

by dolphin_oracle

Adrian wrote: Tue Dec 04, 2018 11:24 am I have an issue on my system not sure if caused of this or I borked the system before (which is probable) I don't see anything in Settings, no icons, nothing. Any idea how to fix this? (and just to be sure please check if that is OK for you)

jerry ran into something similar a while back. not sure if it was resolved.

try making a new user and see if the new user has the stuff.

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 11:33 am

by richb

dolphin_oracle wrote: Tue Dec 04, 2018 11:28 am
richb wrote: Tue Dec 04, 2018 10:49 am Mine shows as MX-17.b3_x64 Continuum November 29 2017. That is weird.
a long time ago we decided to support upgrades from RC but not from beta, so betas will not be changed by the version string script.

neither is the date, so we can tell what iso a distro started from if need be.I remember that. In any case seems that the update worked on this system, as the new stuff did come in. But maybe my reporting is not relevant.

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 11:38 am

by dolphin_oracle

Redacted wrote: Tue Dec 04, 2018 10:41 am Got ton of updates, but still shows
Code: Select all
 inxi -S
System:    Host: lenovo-mx Kernel: 4.15.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3 
           Distro: MX-17.1_x64 Horizon March 14  2018

the name change comes thru the mx-system package, so check to see if its installed on your system.

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 11:49 am

by Redacted

dolphin_oracle wrote: Tue Dec 04, 2018 11:38 am
Redacted wrote: Tue Dec 04, 2018 10:41 am Got ton of updates, but still shows
Code: Select all
 inxi -S
System:    Host: lenovo-mx Kernel: 4.15.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3 
           Distro: MX-17.1_x64 Horizon March 14  2018
the name change comes thru the mx-system package, so check to see if its installed on your system.

Thank you! That was it.

Code: Select all

inxi -S
System:    Host: lenovo-mx Kernel: 4.15.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3 
           Distro: MX-18_x64 Continuum March 14  2018

Everything is running smooth.

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 12:48 pm

by Fornhamfred

Updated here:

Code: Select all

$ inxi -S
System:    Host: mx17 Kernel: 4.15.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3 
           Distro: MX-18_x64 Continuum March 14  2018

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 1:00 pm

by Paul..

FYI...Starting with MX-18 beta 1, adding devrepo.list...and upgrading, I get:

Code: Select all

Distro: MX-18b1_x64 Continuum December 3  2018

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 1:04 pm

by dolphin_oracle

Paul.. wrote: Tue Dec 04, 2018 1:00 pm FYI...Starting with MX-18 beta 1, adding devrepo.list...and upgrading, I get:
Code: Select all
Distro: MX-18b1_x64 Continuum December 3  2018

that would be correct. and it will always say beta1 because we only change the strings on RC an up.

So if you started with 17.1, it would change to MX-18.

But don't get too worried about it, it literally just a text string for identification at this point, and the main release is still a little ways off.

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 1:31 pm

by philotux

Thanks for the upgrade path!
Upgraded from 17.1 Nov. snapshot. Here it is:

Code: Select all

$ inxi -S
System:
  Host: mx Kernel: 4.15.0-1-amd64 x86_64 bits: 64 
  Desktop: Xfce 4.12.3 Distro: MX-18_x64 Continuum March 14  2018

Apart from the wrong date, everything seems to be good so far. I will report back if I stumble upon any issues.

Thank you for you your hard work!
Greetings

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 1:46 pm

by freefreeno

Before this update I was having an issue with firmware for intel 8260 and I would just like to report that it is fixed with the package firmware-iwlwifi 20180825+dfsg-1. That is the correct firmware for intel 8260 wireless adapter and performance seems to be better also. Just wanted to let ya'll know there is no more dmesg errors about loading wireless firmware.I have to run solely off of wifi so it is a big deal to me when something funny is going on with wifi or anyhting like that. If anyone knows any good tweaks for wireless performance I am open to suggestions.Please someone tell me how to disable services with sysV because systemd is usual way of doing things.

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 1:49 pm

by Adrian

philotux wrote: Tue Dec 04, 2018 1:31 pm Apart from the wrong date, everything seems to be good so far. I will report back if I stumble upon any issues.

If I remember correctly we decided to leave the date of original installation there this way we'll know if you installed MX-17 and updated to MX-18 or you installed MX-18 directly, it might be relevant for troubleshooting.

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 1:55 pm

by fehlix

freefreeno wrote: Tue Dec 04, 2018 1:46 pm Please someone tell me how to disable services with sysV because systemd is usual way of doing thing

something like

Code: Select all

sudo service  "init-service-name" status
sudo service  "init-service-name" stop
sudo service  "init-service-name" start
sudo service  --status-all

also this comes handy to view start/stop service:

Code: Select all

sudo sysv-rc-conf

Note runlevels 2,3,4,5 are for "normal" operating in differen modes,
in most cases they are either on or off. Normal GUI runlevel is 5.

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 1:57 pm

by Stevo

Adrian wrote: Tue Dec 04, 2018 10:47 am Things worked fine here, but I don't use Nvidia so I cannot really report on that update.

Q: After the update should people remove or keep the dev repo enabled? I don't think we'll add stuff to dev repo, right?

EDIT, the release name shows correctly for me (maybe it needs a reboot)
Code: Select all
Distro: MX-18_x64 Continuum March 14  2018 

They can deactivate it unless they need some further Mesa and or -dev packages from it that have to match installed versions.

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 2:02 pm

by philotux

Adrian wrote: Tue Dec 04, 2018 1:49 pm
philotux wrote: Tue Dec 04, 2018 1:31 pm Apart from the wrong date, everything seems to be good so far. I will report back if I stumble upon any issues.
If I remember correctly we decided to leave the date of original installation there this way we'll know if you installed MX-17 and updated to MX-18 or you installed MX-18 directly, it might be relevant for troubleshooting.

Thanks for the clarification, Adrian! That makes sense.
And thanks for such a great OS! It's a joy to use!

philotux

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 2:07 pm

by loradona

Code: Select all

loradona@Tux:~
$ inxi -S
System:    Host: Tux Kernel: 4.18.0-0.bpo.1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3 
           Distro: MX-18_x64 Continuum March 14  2018

Here we go !

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 3:33 pm

by freefreeno

For some reason MX USB unmounter will not stop running. It keeps appearing at boot and I dont know why. I have no USB's even plugged in and it still shows up at boot. I can right click and hit quit and a few minutes later it comes back in the panel.

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 3:45 pm

by freefreeno

something like
CODE: SELECT ALL

sudo service "init-service-name" status
sudo service "init-service-name" stop
sudo service "init-service-name" start
sudo service --status-all
also this comes handy to view start/stop service:
CODE: SELECT ALL

sudo sysv-rc-conf
Note runlevels 2,3,4,5 are for "normal" operating in differen modes,
in most cases they are either on or off. Normal GUI runlevel is 5.

Thanks but you left off disable and thats what I need. I tried sudo service samba disable
and all it does is give me this and according to this there is no disable.
-----Usage: /etc/init.d/samba {start|stop|reload|restart|force-reload|status}---------

Apparently the menu where you can control services during install does not work because I unchecked bluetooth and I believe samba right there so that they would not run and they are running anyways. I would like to request a bigger area of things and services that we can disable right there in that same menu during install.Of course it has to work though. AS for nor I need a way to permantly disable services without causing system harm.

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 5:27 pm

by fehlix

freefreeno wrote: Tue Dec 04, 2018 3:45 pm I tried sudo service samba disable ...

When the intention is to to re-enable later you can disable as this:

Code: Select all

sudo service samba stop
sudo update-rc.d samba disable

Keeping it installed but clearing all start/stop-links would go as this:

Code: Select all

sudo service samba stop
sudo update-rc.d samba remove

If the intent is to get completely rid of samba you could now uninstall samba
(after having lateste main repo updates installed for MX17.1)

Code: Select all

sudo apt purge samba

EDIT: corrected samba removal for updated MX17.1

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 6:56 pm

by fehlix

Full upgrade success with my little play mobile "Aspire A114-31" (aka "Aspire 1")
All working fine: splash, wifi, touchpad ... fast and smooth

Code: Select all

System:    Host: mxlinux Kernel: 4.19.4-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 6.3.0 
           Desktop: Xfce 4.12.3 Distro: MX-18_x64 Continuum March 14  2018 
           base: Debian GNU/Linux 9 (stretch) 
Machine:   Type: Laptop System: Acer product: Aspire A114-31 v: V1.09 serial: <filter> 
           Mobo: APL model: Bulbasaur_AP_S v: V1.09 serial: <filter> UEFI: Insyde v: 1.09 date: 10/17/2017 
Battery:   ID-1: BAT1 charge: 34.5 Wh condition: 34.5/37.0 Wh (93%) model: PANASONIC AP16M5J status: Full 
CPU:       Topology: Quad Core model: Intel Pentium N4200 bits: 64 type: MCP arch: Goldmont rev: 9 
           L2 cache: 1024 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 8755 
           Speed: 870 MHz min/max: 800/2500 MHz Core speeds (MHz): 1: 870 2: 1399 3: 1509 4: 1409 
Graphics:  Device-1: Intel Atom/Celeron/Pentium Processor N4200/N3350/E3900 Series Integrated Graphics 
           driver: i915 v: kernel bus ID: 00:02.0 
           Display: x11 server: X.Org 1.19.2 driver: intel resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 505 (Broxton) v: 4.5 Mesa 18.2.6 direct render: Yes 
Audio:     Device-1: Intel Atom/Celeron/Pentium Processor N4200/N3350/E3900 Series Audio Cluster 
           driver: snd_hda_intel v: kernel bus ID: 00:0e.0 
           Sound Server: ALSA v: k4.19.4-antix.1-amd64-smp 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 v: kernel 
           port: 1000 bus ID: 02:00.1 
           IF: eth0 state: down mac: <filter> 
           Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter driver: ath10k_pci v: kernel 
           port: 1000 bus ID: 03:00.0 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 58.24 GiB used: 8.36 GiB (14.4%) 
           ID-1: /dev/mmcblk0 model: DF4064 size: 58.24 GiB 
Partition: ID-1: / size: 20.41 GiB used: 8.31 GiB (40.7%) fs: ext4 dev: /dev/mmcblk0p5 
           ID-2: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/mmcblk0p6 
Sensors:   System Temperatures: cpu: 43.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb https://ftp.nluug.nl/os/Linux/distr/mxlinux/antix/stretch/ stretch main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://ftp2.de.debian.org/debian/ stretch-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://ftp2.de.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/devrepo.list 
           1: deb http://mxrepo.com/mx/testrepo/ mx18 dev
           Active apt repos in: /etc/apt/sources.list.d/local-apt-repository.list 
           1: deb [trusted=yes] file:///var/lib/local-apt-repository/ ./
           2: deb-src [trusted=yes] file:///var/lib/local-apt-repository/ ./
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb https://ftp.nluug.nl/os/Linux/distr/mxlinux/mx/repo/ stretch main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
           Active apt repos in: /etc/apt/sources.list.d/vivaldi.list 
           1: deb http://repo.vivaldi.com/stable/deb/ stable main
Info:      Processes: 210 Uptime: 7m Memory: 3.70 GiB used: 505.4 MiB (13.4%) Init: SysVinit runlevel: 5 
           Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.25

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 6:57 pm

by dolphin_oracle

fehlix wrote: Tue Dec 04, 2018 6:56 pm Full upgrade success with my little play mobile "Aspire A114-31" (aka "Aspire 1")
All working fine: splash, wifi, touchpad ... fast and smooth

Code: Select all

System:    Host: mxlinux Kernel: 4.19.4-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 6.3.0 
           Desktop: Xfce 4.12.3 Distro: MX-18_x64 Continuum March 14  2018 
           base: Debian GNU/Linux 9 (stretch) 
Machine:   Type: Laptop System: Acer product: Aspire A114-31 v: V1.09 serial: <filter> 
           Mobo: APL model: Bulbasaur_AP_S v: V1.09 serial: <filter> UEFI: Insyde v: 1.09 date: 10/17/2017 
Battery:   ID-1: BAT1 charge: 34.5 Wh condition: 34.5/37.0 Wh (93%) model: PANASONIC AP16M5J status: Full 
CPU:       Topology: Quad Core model: Intel Pentium N4200 bits: 64 type: MCP arch: Goldmont rev: 9 
           L2 cache: 1024 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 8755 
           Speed: 870 MHz min/max: 800/2500 MHz Core speeds (MHz): 1: 870 2: 1399 3: 1509 4: 1409 
Graphics:  Device-1: Intel Atom/Celeron/Pentium Processor N4200/N3350/E3900 Series Integrated Graphics 
           driver: i915 v: kernel bus ID: 00:02.0 
           Display: x11 server: X.Org 1.19.2 driver: intel resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 505 (Broxton) v: 4.5 Mesa 18.2.6 direct render: Yes 
Audio:     Device-1: Intel Atom/Celeron/Pentium Processor N4200/N3350/E3900 Series Audio Cluster 
           driver: snd_hda_intel v: kernel bus ID: 00:0e.0 
           Sound Server: ALSA v: k4.19.4-antix.1-amd64-smp 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 v: kernel 
           port: 1000 bus ID: 02:00.1 
           IF: eth0 state: down mac: <filter> 
           Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter driver: ath10k_pci v: kernel 
           port: 1000 bus ID: 03:00.0 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 58.24 GiB used: 8.36 GiB (14.4%) 
           ID-1: /dev/mmcblk0 model: DF4064 size: 58.24 GiB 
Partition: ID-1: / size: 20.41 GiB used: 8.31 GiB (40.7%) fs: ext4 dev: /dev/mmcblk0p5 
           ID-2: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/mmcblk0p6 
Sensors:   System Temperatures: cpu: 43.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb https://ftp.nluug.nl/os/Linux/distr/mxlinux/antix/stretch/ stretch main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://ftp2.de.debian.org/debian/ stretch-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://ftp2.de.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/devrepo.list 
           1: deb http://mxrepo.com/mx/testrepo/ mx18 dev
           Active apt repos in: /etc/apt/sources.list.d/local-apt-repository.list 
           1: deb [trusted=yes] file:///var/lib/local-apt-repository/ ./
           2: deb-src [trusted=yes] file:///var/lib/local-apt-repository/ ./
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb https://ftp.nluug.nl/os/Linux/distr/mxlinux/mx/repo/ stretch main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
           Active apt repos in: /etc/apt/sources.list.d/vivaldi.list 
           1: deb http://repo.vivaldi.com/stable/deb/ stable main
Info:      Processes: 210 Uptime: 7m Memory: 3.70 GiB used: 505.4 MiB (13.4%) Init: SysVinit runlevel: 5 
           Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.25

how do the font descriptions look on your updated system?

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 7:12 pm

by fehlix

dolphin_oracle wrote: Tue Dec 04, 2018 6:57 pm how do the font descriptions look on your updated system?

only those mscorefonts still in czech-like descriptions
EDIT:
Update: Just gone through the whole list:
only "Arial" and "Courier New" shows this "czech"-symptom on the style-selections even the othes from mscorefonts are translated.
Let's see what the diff from our sourcce and the one available on sf.

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 7:12 pm

by dolphin_oracle

fehlix wrote: Tue Dec 04, 2018 7:12 pm
dolphin_oracle wrote: Tue Dec 04, 2018 6:57 pm how do the font descriptions look on your updated system?
only those mscorefonts still in czech-like descriptions

same here. weird.

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 04, 2018 7:35 pm

by fehlix

dolphin_oracle wrote: Tue Dec 04, 2018 7:12 pm
fehlix wrote: Tue Dec 04, 2018 7:12 pm
dolphin_oracle wrote: Tue Dec 04, 2018 6:57 pm how do the font descriptions look on your updated system?
only those mscorefonts still in czech-like descriptions
same here. weird.

need to check the source of those ... and compare
Note: those fonts normaly are even not needed on linux as we have for most of them good alteranatives available.
Surely understand the user does only know Arial and most have no idea of the identical looking
fonts linux like "Nimbus Sans L" or "Liberation Sans" for Arial
or "Nimbus Mono L" for "Courier New" ...

Re: MX-17 to MX-18 update testing

Posted: Wed Dec 05, 2018 7:47 am

by NGIB

Have updated my 3 main laptops and all is well. I'm glad this method is available as I run a highly modified version of MX and I hate doing all the work again...

Re: MX-17 to MX-18 update testing

Posted: Thu Dec 06, 2018 6:48 am

by oops

No big problems detected so far, except a systemd-logind failed warning below:

Code: Select all

$ inxi -S
System:    Host: XEON Kernel: 4.18.9-localmodconfig-01.efi x86_64 bits: 64 Desktop: Xfce 4.12.3 
           Distro: MX-18_x64 Continuum March 14  2018 

$ # dmesg -k -l emerg,alert,crit,err,warn
dmesg | egrep -i --color 'error|critical|failed|warn'
...
[   27.108802] systemd-logind[3002]: Failed to start user service, ignoring: Unknown unit: user@115.service
[   67.951081] systemd-logind[3002]: Failed to start user service, ignoring: Unknown unit: user@1002.service

Re: MX-17 to MX-18 update testing

Posted: Thu Dec 06, 2018 6:07 pm

by philotux

Hi all,

Just wondered if I need to disable the devrepo now after the upgrade from 17.1 to 18 beta. Sorry if it has been asked and answered already.

cheers
philotux

Re: MX-17 to MX-18 update testing

Posted: Thu Dec 06, 2018 8:23 pm

by dolphin_oracle

philotux wrote: Thu Dec 06, 2018 6:07 pm Hi all,

Just wondered if I need to disable the devrepo now after the upgrade from 17.1 to 18 beta. Sorry if it has been asked and answered already.

cheers
philotux

we are still pushing updates, but you can disable if you want. everything will eventually hit main.

Re: MX-17 to MX-18 update testing

Posted: Thu Dec 06, 2018 8:34 pm

by philotux

dolphin_oracle wrote: Thu Dec 06, 2018 8:23 pm
philotux wrote: Thu Dec 06, 2018 6:07 pm Hi all,

Just wondered if I need to disable the devrepo now after the upgrade from 17.1 to 18 beta. Sorry if it has been asked and answered already.

cheers
philotux
we are still pushing updates, but you can disable if you want. everything will eventually hit main.

I guess I will leave it enabled then for the time being.
Thak you so much for your reply and all the hard work.
Cheers

Re: MX-17 to MX-18 update testing

Posted: Thu Dec 06, 2018 10:04 pm

by mx-ian

Successful upgrade from 17.1 on a 32-bit laptop.

Happy to accept more updates.

Code: Select all

System: Host: MX Kernel: 4.15.0-1-686-pae i686 bits: 32 compiler: gcc v: 6.3.0 
           Desktop: Xfce 4.12.3 Distro: MX-18_386 Continuum March 12 2017 
           base: Debian GNU/Linux 9 (stretch) 
Machine: Type: Laptop System: SAMSUNG product: N310 v: N/A serial: <filter> 
           Mobo: SAMSUNG model: N310 serial: <filter> BIOS: Phoenix v: 06BA.M042.20100113.CYH 
           date: 01/13/2010 
Battery: ID-1: BAT1 charge: 19.1 Wh condition: 56.2/66.4 Wh (85%) model: SAMSUNG Electronics 
           status: Discharging 
CPU: Topology: Single Core model: Intel Atom N270 bits: 32 type: MT arch: Bonnell rev: 2 
           L2 cache: 512 KiB 
           flags: nx pae sse sse2 sse3 ssse3 bogomips: 6383 
           Speed: 1553 MHz min/max: 800/1600 MHz Core speeds (MHz): 1: 856 2: 945 
Graphics: Device-1: Intel Mobile 945GSE Express Integrated Graphics driver: i915 v: kernel 
           bus ID: 00:02.0 
           Display: x11 server: X.Org 1.19.2 driver: intel unloaded: fbdev,modesetting,vesa 
           resolution: 1024x600~60Hz 
           OpenGL: renderer: Mesa DRI Intel 945GME x86/MMX/SSE2 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.15.0-1-686-pae 
Network: Device-1: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter driver: ath5k 
           v: kernel port: 18a0 bus ID: 02:00.0 
           IF: wlan0 state: up mac: <filter> 
           Device-2: Marvell 88E8040 PCI-E Fast Ethernet driver: sky2 v: 1.30 port: 2000 
           bus ID: 03:00.0 
           IF: eth0 state: down mac: <filter> 
Drives: Local Storage: total: 232.89 GiB used: 18.93 GiB (8.1%) 
           ID-1: /dev/sda vendor: Crucial model: CT250MX500SSD1 size: 232.89 GiB 
Partition: ID-1: / size: 9.95 GiB used: 7.50 GiB (75.3%) fs: ext4 dev: /dev/sda2 
           ID-2: /home size: 215.26 GiB used: 11.43 GiB (5.3%) fs: ext4 dev: /dev/sda3 
           ID-3: swap-1 size: 3.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda1 
Sensors: System Temperatures: cpu: 54.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://ftp.yzu.edu.tw/Linux/mx-workspace/antix/stretch stretch main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://ftp.jp.debian.org/debian/ stretch-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://ftp.jp.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/devrepro.list 
           1: deb http://mxrepo.com/mx/testrepo/ mx18 dev
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://ftp.yzu.edu.tw/Linux/mx-workspace/mx/repo/ stretch main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info: Processes: 177 Uptime: 1m Memory: 1.96 GiB used: 391.4 MiB (19.5%) Init: SysVinit 
           runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.25

Re: MX-17 to MX-18 update testing

Posted: Fri Dec 07, 2018 1:12 pm

by Siles

Upgraded my Dell Precision M6400. Everything works so far. I will keep repository open for now for kernel update.
Did not lose anything.

Re: MX-17 to MX-18 update testing

Posted: Fri Dec 07, 2018 2:03 pm

by Richard

Prior to migrate, made snapshot of uptodate
MX171-Horizon-x32, just in case.

Have achieved similar results with
/etc/apt/sources.list.d/devrepo.list
on Acer Aspire One, AOAZG5, netbook
with 150 GB HDD (see hardware in Sig).
Installed the Debian backport 4.9.0-8-686
kernel. Configured MX18b1x32p
for myself, then made a snapshot.

Installed snapshot onto EeePC-1005HA
(see hardware in Sig) Only slight differences
to adjust. Both working as expected.

Looking forward to MX18 release.
Thanks.

Re: MX-17 to MX-18 update testing

Posted: Fri Dec 07, 2018 4:42 pm

by Stevo

mx-ian wrote: Thu Dec 06, 2018 10:04 pm Successful upgrade from 17.1 on a 32-bit laptop.

Happy to accept more updates.

...

If you want to test the 4.19 kernel, it's available if you search in Synaptic for "4.19.0-1" and install the linux-image.

Re: MX-17 to MX-18 update testing

Posted: Fri Dec 07, 2018 6:43 pm

by rasat

Thanks Stevo.... upgrade and 4.19 work fine.

$ inxi -S
System: Host: AMURT Kernel: 4.19.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
Distro: MX-18_x64 Continuum March 14 2018

Re: MX-17 to MX-18 update testing

Posted: Fri Dec 07, 2018 7:16 pm

by Richard

Thanks Stevo. I'll go look for the 4.19 kernel.

I just applied the "/etc/apt/sources.list.d/devrepo.list" migration to the T430. Made an uptodate MX171-Horizon-x64 before. :)
And now, running MX18b1-Continuum-x64 with very few tweaks required, mostly cosmetic [Notes below]:
Most things in the Notification bar were set back to defaults, dates, colors, temps, etc. Usually change them anyway. :)
Oddly enough, it feels like a new install. Seems quicker, but probably just me.

Code: Select all

System:    Host: mx171 Kernel: 4.18.0-0.bpo.1-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0 Desktop: Xfce 4.12.3 
           Distro: MX-18_x64 Continuum March 14  2018 base: Debian GNU/Linux 9 (stretch) 
           
--> and now...

System:    Host: mx171 Kernel: 4.19.0-1-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0 Desktop: Xfce 4.12.3 
           Distro: MX-18_x64 Continuum March 14  2018 base: Debian GNU/Linux 9 (stretch) 
Machine:   Type: Laptop System: LENOVO product: 2347AY1 v: ThinkPad T430 serial: <filter> 
           Mobo: LENOVO model: 2347AY1 v: NO DPK serial: <filter> UEFI [Legacy]: LENOVO v: G1ET73WW (2.09 ) 
           date: 10/19/2012 
Battery:   ID-1: BAT0 charge: 17.4 Wh condition: 17.4/56.2 Wh (31%) model: SANYO 45N1001 status: Full 
CPU:       Topology: Dual Core model: Intel Core i5-3320M bits: 64 type: MT MCP arch: Ivy Bridge family: 6 
           model-id: 3A (58) stepping: 9 microcode: 20 L2 cache: 3072 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 20751 
           Speed: 1230 MHz min/max: 1200/3300 MHz Core speeds (MHz): 1: 1197 2: 1210 3: 1201 4: 1197 
           Vulnerabilities: Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB, IBRS_FW 
Graphics:  Device-1: Intel 3rd Gen Core processor Graphics vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 
           Display: x11 server: X.Org 1.19.2 driver: intel resolution: 1600x900~60Hz 
           OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile v: 4.2 Mesa 18.2.6 direct render: Yes 
Audio:     Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Lenovo driver: snd_hda_intel v: kernel 
           bus ID: 00:1b.0 
           Sound Server: ALSA v: k4.19.0-1-amd64 
Network:   Device-1: Intel 82579LM Gigabit Network vendor: Lenovo driver: e1000e v: 3.2.6-k port: 5080 bus ID: 00:19.0 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
           Device-2: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi v: kernel port: efa0 bus ID: 03:00.0 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 148.30 GiB used: 110.94 GiB (74.8%) 
           ID-1: /dev/mmcblk0 model: SA32G size: 29.05 GiB block size: physical: 512 B logical: 512 B 
           ID-2: /dev/sda vendor: Samsung model: SSD 840 PRO Series size: 119.24 GiB block size: physical: 512 B 
           logical: 512 B 
           Optical-1: /dev/sr0 vendor: Optiarc model: DVD RW AD-7740H rev: 1.S1 dev-links: cdrom,cdrw,dvd,dvdrw 
           Features: speed: 24 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram state: running 
Partition: ID-1: / raw size: 21.00 GiB size: 20.54 GiB (97.83%) used: 11.30 GiB (55.0%) fs: ext4 dev: /dev/sda2 
           label: MX171 
           ID-2: /media/DATA raw size: 98.25 GiB size: 96.20 GiB (97.92%) used: 81.60 GiB (84.8%) fs: ext4 dev: /dev/sda1 
           label: DATA 
           ID-3: /media/SD-NTFS raw size: 29.05 GiB size: 29.05 GiB (100.00%) used: 18.05 GiB (62.1%) fs: ntfs 
           dev: /dev/mmcblk0p1 label: SD-NTFS 
Unmounted: Message: No unmounted partitions found. 
Sensors:   System Temperatures: cpu: 63.0 C mobo: N/A 
           Fan Speeds (RPM): cpu: 3973 
Info:      Processes: 208 Uptime: 4m Memory: 7.02 GiB used: 632.5 MiB (8.8%) Init: SysVinit runlevel: 5 Compilers: 
           gcc: 6.3.0 Shell: xfce4-terminal v: 0.8.3 pinxi: 3.0.27-11

Re: MX-17 to MX-18 update testing

Posted: Fri Dec 07, 2018 8:40 pm

by Siles

I upgraded the kernel per instructions and everything is still working. The only non-working item is Plymouth customization on boot, I expected that as it is a combination of two images.

I agree with Richard, MX18 seems a little faster to me but I have no objective measurements. Great job by the Devs. THANK YOU

Re: MX-17 to MX-18 update testing

Posted: Fri Dec 07, 2018 8:42 pm

by Richard

Great work guys 'n gals!
Waiting for the eye candy...

Re: MX-17 to MX-18 update testing

Posted: Sat Dec 08, 2018 4:11 am

by mx-ian

Stevo wrote: Fri Dec 07, 2018 4:42 pm
mx-ian wrote: Thu Dec 06, 2018 10:04 pm Successful upgrade from 17.1 on a 32-bit laptop.

Happy to accept more updates.

...
If you want to test the 4.19 kernel, it's available if you search in Synaptic for "4.19.0-1" and install the linux-image.

Installed the 4.19 kernel.
The more I update it, the more I like it.

Code: Select all

inxi -S
System:
  Host: MX Kernel: 4.19.0-1-686-pae i686 bits: 32 Desktop: Xfce 4.12.3 
  Distro: MX-18_386 Continuum March 12  2017

Re: MX-17 to MX-18 update testing

Posted: Sat Dec 08, 2018 3:20 pm

by zorzi

Everything went fine.

Just have a font problem with Thunderbird. "g" letter now blinks in messages subjects when I move my mouse cursor. Did someone experience that ?

This can be "solved" by changing fonts or tweaking noto sans fonts to a bigger bigger size.

I suspect the fontconfig & fontconfig-config packages updates.

Re: MX-17 to MX-18 update testing

Posted: Sat Dec 08, 2018 3:25 pm

by Stevo

Can anyone running the 4.19 32-bit kernel install spectre-meltdown-checker and see if it now supports the PTI Meltdown hardening, as was advertised?

Steve (too dang lazy to upgrade in a virtual machine and check for himself)

Re: MX-17 to MX-18 update testing

Posted: Sat Dec 08, 2018 3:48 pm

by anticapitalista

Stevo wrote: Sat Dec 08, 2018 3:25 pm Can anyone running the 4.19 32-bit kernel install spectre-meltdown-checker and see if it now supports the PTI Meltdown hardening, as was advertised?

Steve (too dang lazy to upgrade in a virtual machine and check for himself)

In VBox

Code: Select all

spectre-meltdown-checker 
Spectre and Meltdown mitigation detection tool v0.40

Checking for vulnerabilities on current system
Kernel is Linux 4.19.0-1-686-pae #1 SMP Debian 4.19.5-1~mx17+1 (2018-11-28) i686
CPU is Intel(R) Core(TM) i5 CPU       M 520  @ 2.40GHz

Hardware check
* Hardware support (CPU microcode) for mitigation techniques
  * Indirect Branch Restricted Speculation (IBRS)
    * SPEC_CTRL MSR is available:  NO 
    * CPU indicates IBRS capability:  NO 
  * Indirect Branch Prediction Barrier (IBPB)
    * PRED_CMD MSR is available:  NO 
    * CPU indicates IBPB capability:  NO 
  * Single Thread Indirect Branch Predictors (STIBP)
    * SPEC_CTRL MSR is available:  NO 
    * CPU indicates STIBP capability:  NO 
  * Speculative Store Bypass Disable (SSBD)
    * CPU indicates SSBD capability:  NO 
  * L1 data cache invalidation
    * FLUSH_CMD MSR is available:  YES 
    * CPU indicates L1D flush capability:  YES  (L1D flush feature bit)
  * Enhanced IBRS (IBRS_ALL)
    * CPU indicates ARCH_CAPABILITIES MSR availability:  NO 
    * ARCH_CAPABILITIES MSR advertises IBRS_ALL capability:  NO 
  * CPU explicitly indicates not being vulnerable to Meltdown (RDCL_NO):  NO 
  * CPU explicitly indicates not being vulnerable to Variant 4 (SSB_NO):  NO 
  * CPU/Hypervisor indicates L1D flushing is not necessary on this system:  NO 
  * Hypervisor indicates host CPU might be vulnerable to RSB underflow (RSBA):  NO 
  * CPU supports Software Guard Extensions (SGX):  NO 
  * CPU microcode is known to cause stability problems:  NO  (model 0x25 family 0x6 stepping 0x2 ucode 0x616 cpuid 0x20652)
  * CPU microcode is the latest known available version:  YES  (latest version is 0x11 dated 2018/05/08 according to builtin MCExtractor DB v84 - 2018/09/27)
* CPU vulnerability to the speculative execution attack variants
  * Vulnerable to CVE-2017-5753 (Spectre Variant 1, bounds check bypass):  YES 
  * Vulnerable to CVE-2017-5715 (Spectre Variant 2, branch target injection):  YES 
  * Vulnerable to CVE-2017-5754 (Variant 3, Meltdown, rogue data cache load):  YES 
  * Vulnerable to CVE-2018-3640 (Variant 3a, rogue system register read):  YES 
  * Vulnerable to CVE-2018-3639 (Variant 4, speculative store bypass):  YES 
  * Vulnerable to CVE-2018-3615 (Foreshadow (SGX), L1 terminal fault):  NO 
  * Vulnerable to CVE-2018-3620 (Foreshadow-NG (OS), L1 terminal fault):  YES 
  * Vulnerable to CVE-2018-3646 (Foreshadow-NG (VMM), L1 terminal fault):  YES 

CVE-2017-5753 aka 'Spectre Variant 1, bounds check bypass'
* Mitigated according to the /sys interface:  YES  (Mitigation: __user pointer sanitization)
* Kernel has array_index_mask_nospec:  YES  (1 occurrence(s) found of x86 32 bits array_index_mask_nospec())
* Kernel has the Red Hat/Ubuntu patch:  NO 
* Kernel has mask_nospec64 (arm64):  NO 
> STATUS:  NOT VULNERABLE  (Mitigation: __user pointer sanitization)

CVE-2017-5715 aka 'Spectre Variant 2, branch target injection'
* Mitigated according to the /sys interface:  YES  (Mitigation: Full generic retpoline)
* Mitigation 1
  * Kernel is compiled with IBRS support:  YES 
    * IBRS enabled and active:  NO 
  * Kernel is compiled with IBPB support:  YES 
    * IBPB enabled and active:  NO 
* Mitigation 2
  * Kernel has branch predictor hardening (arm):  NO 
  * Kernel compiled with retpoline option:  YES 
    * Kernel compiled with a retpoline-aware compiler:  YES  (kernel reports full retpoline compilation)
> STATUS:  NOT VULNERABLE  (Full retpoline is mitigating the vulnerability)
IBPB is considered as a good addition to retpoline for Variant 2 mitigation, but your CPU microcode doesn't support it

CVE-2017-5754 aka 'Variant 3, Meltdown, rogue data cache load'
* Mitigated according to the /sys interface:  YES  (Mitigation: PTI)
* Kernel supports Page Table Isolation (PTI):  YES 
  * PTI enabled and active:  YES 
  * Reduced performance impact of PTI:  NO  (PCID/INVPCID not supported, performance impact of PTI will be significant)
* Running as a Xen PV DomU:  NO 
> STATUS:  NOT VULNERABLE  (Mitigation: PTI)

CVE-2018-3640 aka 'Variant 3a, rogue system register read'
* CPU microcode mitigates the vulnerability:  NO 
> STATUS:  VULNERABLE  (an up-to-date CPU microcode is needed to mitigate this vulnerability)

CVE-2018-3639 aka 'Variant 4, speculative store bypass'
* Mitigated according to the /sys interface:  NO  (Vulnerable)
* Kernel supports speculation store bypass:  YES  (found in /proc/self/status)
> STATUS:  VULNERABLE  (Your CPU doesn't support SSBD)

CVE-2018-3615 aka 'Foreshadow (SGX), L1 terminal fault'
* CPU microcode mitigates the vulnerability:  N/A 
> STATUS:  NOT VULNERABLE  (your CPU vendor reported your CPU model as not vulnerable)

CVE-2018-3620 aka 'Foreshadow-NG (OS), L1 terminal fault'
* Mitigated according to the /sys interface:  YES  (Mitigation: PTE Inversion)
* Kernel supports PTE inversion:  YES  (found in kernel image)
* PTE inversion enabled and active:  YES 
> STATUS:  NOT VULNERABLE  (Mitigation: PTE Inversion)

CVE-2018-3646 aka 'Foreshadow-NG (VMM), L1 terminal fault'
* Information from the /sys interface: 
* This system is a host running an hypervisor:  NO 
* Mitigation 1 (KVM)
  * EPT is disabled:  N/A  (the kvm_intel module is not loaded)
* Mitigation 2
  * L1D flush is supported by kernel:  YES  (found flush_l1d in /proc/cpuinfo)
  * L1D flush enabled:  UNKNOWN  (unrecognized mode)
  * Hardware-backed L1D flush supported:  YES  (performance impact of the mitigation will be greatly reduced)
  * Hyper-Threading (SMT) is enabled:  NO 
> STATUS:  NOT VULNERABLE  (this system is not running an hypervisor)

> SUMMARY: CVE-2017-5753:OK CVE-2017-5715:OK CVE-2017-5754:OK CVE-2018-3640:KO CVE-2018-3639:KO CVE-2018-3615:OK CVE-2018-3620:OK CVE-2018-3646:OK

Need more detailed information about mitigation options? Use --explain
A false sense of security is worse than no security at all, see --disclaimer

Re: MX-17 to MX-18 update testing

Posted: Sat Dec 08, 2018 3:49 pm

by dolphin_oracle

Stevo wrote: Sat Dec 08, 2018 3:25 pm Can anyone running the 4.19 32-bit kernel install spectre-meltdown-checker and see if it now supports the PTI Meltdown hardening, as was advertised?

Steve (too dang lazy to upgrade in a virtual machine and check for himself)

Code: Select all

demo@mx1:~
$ sudo spectre-meltdown-checker 

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

[sudo] password for demo: 
Spectre and Meltdown mitigation detection tool v0.40

Checking for vulnerabilities on current system
Kernel is Linux 4.19.0-1-686-pae #1 SMP Debian 4.19.5-1~mx17+1 (2018-11-28) i686
CPU is Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz

Hardware check
* Hardware support (CPU microcode) for mitigation techniques
  * Indirect Branch Restricted Speculation (IBRS)
    * SPEC_CTRL MSR is available:  NO 
    * CPU indicates IBRS capability:  NO 
  * Indirect Branch Prediction Barrier (IBPB)
    * PRED_CMD MSR is available:  NO 
    * CPU indicates IBPB capability:  NO 
  * Single Thread Indirect Branch Predictors (STIBP)
    * SPEC_CTRL MSR is available:  NO 
    * CPU indicates STIBP capability:  NO 
  * Speculative Store Bypass Disable (SSBD)
    * CPU indicates SSBD capability:  NO 
  * L1 data cache invalidation
    * FLUSH_CMD MSR is available:  YES 
    * CPU indicates L1D flush capability:  YES  (L1D flush feature bit)
  * Enhanced IBRS (IBRS_ALL)
    * CPU indicates ARCH_CAPABILITIES MSR availability:  NO 
    * ARCH_CAPABILITIES MSR advertises IBRS_ALL capability:  NO 
  * CPU explicitly indicates not being vulnerable to Meltdown (RDCL_NO):  NO 
  * CPU explicitly indicates not being vulnerable to Variant 4 (SSB_NO):  NO 
  * CPU/Hypervisor indicates L1D flushing is not necessary on this system:  NO 
  * Hypervisor indicates host CPU might be vulnerable to RSB underflow (RSBA):  NO 
  * CPU supports Software Guard Extensions (SGX):  NO 
  * CPU microcode is known to cause stability problems:  NO  (model 0x3a family 0x6 stepping 0x9 ucode 0x19 cpuid 0x306a9)
  * CPU microcode is the latest known available version:  NO  (latest version is 0x20 dated 2018/04/10 according to builtin MCExtractor DB v84 - 2018/09/27)
* CPU vulnerability to the speculative execution attack variants
  * Vulnerable to CVE-2017-5753 (Spectre Variant 1, bounds check bypass):  YES 
  * Vulnerable to CVE-2017-5715 (Spectre Variant 2, branch target injection):  YES 
  * Vulnerable to CVE-2017-5754 (Variant 3, Meltdown, rogue data cache load):  YES 
  * Vulnerable to CVE-2018-3640 (Variant 3a, rogue system register read):  YES 
  * Vulnerable to CVE-2018-3639 (Variant 4, speculative store bypass):  YES 
  * Vulnerable to CVE-2018-3615 (Foreshadow (SGX), L1 terminal fault):  NO 
  * Vulnerable to CVE-2018-3620 (Foreshadow-NG (OS), L1 terminal fault):  YES 
  * Vulnerable to CVE-2018-3646 (Foreshadow-NG (VMM), L1 terminal fault):  YES 

CVE-2017-5753 aka 'Spectre Variant 1, bounds check bypass'
* Mitigated according to the /sys interface:  YES  (Mitigation: __user pointer sanitization)
* Kernel has array_index_mask_nospec:  YES  (1 occurrence(s) found of x86 32 bits array_index_mask_nospec())
* Kernel has the Red Hat/Ubuntu patch:  NO 
* Kernel has mask_nospec64 (arm64):  NO 
> STATUS:  NOT VULNERABLE  (Mitigation: __user pointer sanitization)

CVE-2017-5715 aka 'Spectre Variant 2, branch target injection'
* Mitigated according to the /sys interface:  YES  (Mitigation: Full generic retpoline)
* Mitigation 1
  * Kernel is compiled with IBRS support:  YES 
    * IBRS enabled and active:  NO 
  * Kernel is compiled with IBPB support:  YES 
    * IBPB enabled and active:  NO 
* Mitigation 2
  * Kernel has branch predictor hardening (arm):  NO 
  * Kernel compiled with retpoline option:  YES 
    * Kernel compiled with a retpoline-aware compiler:  YES  (kernel reports full retpoline compilation)
> STATUS:  NOT VULNERABLE  (Full retpoline is mitigating the vulnerability)
IBPB is considered as a good addition to retpoline for Variant 2 mitigation, but your CPU microcode doesn't support it

CVE-2017-5754 aka 'Variant 3, Meltdown, rogue data cache load'
* Mitigated according to the /sys interface:  YES  (Mitigation: PTI)
* Kernel supports Page Table Isolation (PTI):  YES 
  * PTI enabled and active:  YES 
  * Reduced performance impact of PTI:  YES  (CPU supports PCID, performance impact of PTI will be reduced)
* Running as a Xen PV DomU:  NO 
> STATUS:  NOT VULNERABLE  (Mitigation: PTI)

CVE-2018-3640 aka 'Variant 3a, rogue system register read'
* CPU microcode mitigates the vulnerability:  NO 
> STATUS:  VULNERABLE  (an up-to-date CPU microcode is needed to mitigate this vulnerability)

CVE-2018-3639 aka 'Variant 4, speculative store bypass'
* Mitigated according to the /sys interface:  NO  (Vulnerable)
* Kernel supports speculation store bypass:  YES  (found in /proc/self/status)
> STATUS:  VULNERABLE  (Your CPU doesn't support SSBD)

CVE-2018-3615 aka 'Foreshadow (SGX), L1 terminal fault'
* CPU microcode mitigates the vulnerability:  N/A 
> STATUS:  NOT VULNERABLE  (your CPU vendor reported your CPU model as not vulnerable)

CVE-2018-3620 aka 'Foreshadow-NG (OS), L1 terminal fault'
* Mitigated according to the /sys interface:  YES  (Mitigation: PTE Inversion)
* Kernel supports PTE inversion:  YES  (found in kernel image)
* PTE inversion enabled and active:  YES 
> STATUS:  NOT VULNERABLE  (Mitigation: PTE Inversion)

CVE-2018-3646 aka 'Foreshadow-NG (VMM), L1 terminal fault'
* Information from the /sys interface: 
* This system is a host running an hypervisor:  NO 
* Mitigation 1 (KVM)
  * EPT is disabled:  N/A  (the kvm_intel module is not loaded)
* Mitigation 2
  * L1D flush is supported by kernel:  YES  (found flush_l1d in /proc/cpuinfo)
  * L1D flush enabled:  UNKNOWN  (unrecognized mode)
  * Hardware-backed L1D flush supported:  YES  (performance impact of the mitigation will be greatly reduced)
  * Hyper-Threading (SMT) is enabled:  NO 
> STATUS:  NOT VULNERABLE  (this system is not running an hypervisor)

> SUMMARY: CVE-2017-5753:OK CVE-2017-5715:OK CVE-2017-5754:OK CVE-2018-3640:KO CVE-2018-3639:KO CVE-2018-3615:OK CVE-2018-3620:OK CVE-2018-3646:OK

Need more detailed information about mitigation options? Use --explain
A false sense of security is worse than no security at all, see --disclaimer
demo@mx1:~
$

Re: MX-17 to MX-18 update testing

Posted: Sat Dec 08, 2018 7:27 pm

by tek10

Code: Select all

$ inxi -S
System:    Host: fractal Kernel: 4.19.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3 
           Distro: MX-18_x64 Continuum March 14  2018

Updated 17.1 and installed the 4.19 kernel. Everything looks good so far.

Re: MX-17 to MX-18 update testing

Posted: Sat Dec 08, 2018 7:48 pm

by Stevo

Thanks! So the 32-bit 4.19 kernel now does have the PTI Meltdown mitigations working. That's another improvement bullet point on the release notes.

Re: MX-17 to MX-18 update testing

Posted: Sat Dec 08, 2018 8:52 pm

by tascoast

I seemed to have no problems updating after adding /etc/apt/sources.list.d/devrepo.list, using root Thunar, as described in OP.

This additional source does not appear in Synaptic and reading through posts regarding disabling, noting other updates may yet come through, I assume I would # (ie. comment out) the
deb http://mxrepo.com/mx/testrepo/ mx18 dev
line, or just delete the file itself at some stage?

System: Host: mx1 Kernel: 4.14.0-3-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
Distro: MX-18_x64 Continuum December 15 2017
Machine: Type: Desktop System: LENOVO product: 7522RU3 v: ThinkCentre A58

No news is good news unless something unusual crops up in operation.
Kind thanks
Mick

Re: MX-17 to MX-18 update testing

Posted: Mon Dec 10, 2018 10:06 am

by marlowe221

Just updated to MX 18 and 4.19.0-1 64 bit. Everything seems to be working well so far. The update process was smooth and seamless.

Edit - My hardware is a Lenovo Thinkpad T450, in case that information is useful.

Re: MX-17 to MX-18 update testing

Posted: Mon Dec 10, 2018 1:59 pm

by Stevo

We have a patched MyPaint in the dev repo that is now also compatible with GIMP 2.10.X, unlike the situation in upstream Debian, though I did get the patch to fix it from a Debian bug report. If anyone else wants to test and confirm that, we'd appreciate that!

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 11, 2018 3:56 pm

by darth.severus

I just want to be sure that I got it right: There will be an automatic update from MX-17.1 to MX-18? When I use the dev repo I'm just a bit ahead of what happens anyway? Or I maybe need an additional Kernel upgrade later, but that's all?

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 11, 2018 3:58 pm

by dolphin_oracle

darth.severus wrote: Tue Dec 11, 2018 3:56 pm I just want to be sure that I got it right: There will be an automatic update from MX-17.1 to MX-18? When I use the dev repo I'm just a bit ahead of what happens anyway? Or I maybe need an additional Kernel upgrade later, but that's all?

pretty much, yep

Re: MX-17 to MX-18 update testing

Posted: Tue Dec 11, 2018 4:21 pm

by Stevo

If your hardware is running just fine with the current kernel, you might want to stick with it, though the 4.19.5 kernel does offer more Spectre and Meltdown protection for 32-bit users...at the cost of a somewhat variable performance loss, unless you disable that with the "nopti" kernel boot command.

Users can install spectre-meltdown-checker and run

Code: Select all

sudo spectre-meltdown-checker

to see how vunerable they are.

Re: MX-17 to MX-18 update testing

Posted: Wed Dec 12, 2018 9:52 am

by darth.severus

Thanks for the answers. My system is 64-Bit. One CVE is open because I need a Microkernel upgrade. I'd like using the newest kernel I'm able to use.
My question has the background that MX-18 may be longer supported if there is a difference to MX-17.1, so I have to decide if I wait or not. If MX-17.1 becomes MX-18, or at least could become, then there is no reason to wait for MX-18 final. I probably don't need the system encryption installer because I do that myself, with btrfs subvolumes instead of LVM.

Re: MX-17 to MX-18 update testing

Posted: Wed Dec 12, 2018 4:56 pm

by Stevo

Yes, we already went with the same kind of transition with MX 15 to MX 16, both of which had the same Jessie base.

We're still going to label our packages as MX 17 versions, since they will be compatible with both 17 and 18, unless they are specifically for MX 18, such as artwork.

Re: MX-17 to MX-18 update testing

Posted: Wed Dec 12, 2018 5:00 pm

by dolphin_oracle

Think

"How long will the stretch based series be supported" rather than a given number series.

You could also think of the update to mx18 as part of that support.

Re: MX-17 to MX-18 update testing

Posted: Thu Dec 13, 2018 1:55 pm

by darth.severus

Okay, thanks. For me it now sounds like it will be the same. So I'll go with MX-17.1 and upgrade later.

dolphin_oracle wrote: Wed Dec 12, 2018 5:00 pm You could also think of the update to mx18 as part of that support.

My thinking was, if something is different and can't be upgraded later without a new install e.g. Kernel, it won't last as long as MX-18.

Re: MX-17 to MX-18 update testing

Posted: Fri Dec 14, 2018 6:41 am

by mx-ian

Stevo wrote: Tue Dec 11, 2018 4:21 pm If your hardware is running just fine with the current kernel, you might want to stick with it, though the 4.19.5 kernel does offer more Spectre and Meltdown protection for 32-bit users...at the cost of a somewhat variable performance loss, unless you disable that with the "nopti" kernel boot command.

Users can install spectre-meltdown-checker and run
Code: Select all
sudo spectre-meltdown-checker
to see how vunerable they are.

I ran the spectre-meltdown-checker installed from the Synaptic Package Manager. The cpu is not vulnerable.

Steps to add the "nopti" option to the kernel boot command:
1. Open the Grub Customizer application
2. Edit the first entry, in this case "MX 18 Continuum"
3. Scroll down to the line "linux /boot/vmlinuz- ..." and add "nopti" at the end of the line without quotes
4. Click the OK button
5. Clck the Save button in Grub Customizer and close the application
6. Reboot
7. Open the Xfce Terminal and type "cat /proc/cmdline" to confirm the "nopti" option

Re: MX-17 to MX-18 update testing

Posted: Mon Dec 17, 2018 3:26 am

by ChrisUK

All OK so far:

Code: Select all

System:    Host: mx1742 Kernel: 4.9.0-8-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0 
           Desktop: Xfce 4.12.3 Distro: MX-18_x64 Continuum March 14  2018 
           base: Debian GNU/Linux 9 (stretch) 
Machine:   Type: Laptop System: SAMSUNG product: RV411/RV511/E3511/S3511/RV711 v: N/A 
           serial: <filter> 
           Mobo: SAMSUNG model: RV411/RV511/E3511/S3511/RV711 serial: <filter> BIOS: Phoenix 
           v: 03PA.M001.20110312.XW date: 03/12/2011 
Battery:   ID-1: BAT1 charge: 7.6 Wh condition: 7.6/47.5 Wh (16%) model: SAMSUNG Electronics 
           status: Full 
CPU:       Topology: Dual Core model: Intel Core i3 M 380 bits: 64 type: MT MCP arch: Nehalem 
           rev: 5 L2 cache: 3072 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 20216 
           Speed: 933 MHz min/max: 933/2533 MHz Core speeds (MHz): 1: 933 2: 933 3: 933 4: 933 
Graphics:  Device-1: NVIDIA GT218M [GeForce 315M] driver: nouveau v: kernel bus ID: 02:00.0 
           Display: x11 server: X.Org 1.19.2 driver: nouveau unloaded: fbdev,modesetting,vesa 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: NVA8 v: 3.3 Mesa 18.2.6 direct render: Yes 
Audio:     Device-1: Intel 5 Series/3400 Series High Definition Audio driver: snd_hda_intel 
           v: kernel bus ID: 00:1b.0 
           Device-2: NVIDIA High Definition Audio driver: snd_hda_intel v: kernel 
           bus ID: 02:00.1 
           Sound Server: ALSA v: k4.9.0-8-amd64 
Network:   Device-1: Broadcom Limited BCM4313 802.11bgn Wireless Network Adapter 
           driver: bcma-pci-bridge v: N/A port: 2000 bus ID: 03:00.0 
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 
           v: 2.3LK-NAPI port: 4000 bus ID: 05:00.0 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
           IF-ID-1: wlan0 state: down mac: <filter> 
Drives:    Local Storage: total: 931.51 GiB used: 14.75 GiB (1.6%) 
           ID-1: /dev/sda vendor: Seagate model: ST1000LM048-2E7172 size: 931.51 GiB 
Partition: ID-1: / size: 49.26 GiB used: 14.75 GiB (29.9%) fs: ext4 dev: /dev/sda1 
Sensors:   System Temperatures: cpu: 47.0 C mobo: 47.0 C gpu: nouveau temp: 51 C 
           Fan Speeds (RPM): N/A 
Info:      Processes: 190 Uptime: 9m Memory: 5.70 GiB used: 654.1 MiB (11.2%) Init: SysVinit 
           runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.25