Page 1 of 1
testing for MX 18.3
Posted: Sat May 11, 2019 7:13 pm
by dolphin_oracle
in lieu of a snapshot in may, we plan to produce a new iso, MX-18.3
It has been proposed to use kernel package 4.19.0-5 from the test repository.
While this should be a simple upgrade, we could use some quick testing.
If folks could test this package (easiest from MX-Packageinstaller-> Test Repo) that would really help.
64bit
linux-image-4.19.0-5-amd64-unsigned
linux-headers-4.19.0-5-amd64
32 bit
linux-image-4.19.0-5-686-pae-unsigned
linux-headers-4.19.0-5-686-pae
Thank you in advance. Post comments here.
Re: testing for MX 18.3
Posted: Sat May 11, 2019 7:42 pm
by fehlix
dolphin_oracle wrote: Sat May 11, 2019 7:13 pm
64bit
linux-image-4.19.0-5-amd64-unsigned
linux-headers-4.19.0-5-amd64
Installs and boot fine running MX 18.2 in VirtualBox and also in real hardware with nvidia 390.116.
Re: testing for MX 18.3
Posted: Sat May 11, 2019 7:57 pm
by oops
here, with: linux-headers-4.19.0-5-common ... &. ... linux-image-4.19.0-5-amd64-unsigned
Code: Select all
cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.19.0-5-amd64 ..... quiet
Every things are ok here, I have the same warnings as usual due to a buggy bios:
Code: Select all
dmesg -k -l emerg,alert,crit,err,warn
[ 0.000000] secureboot: Secure boot could not be determined (mode 0)
[ 0.176121] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[ 0.176121] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
[ 0.189946] pmd_set_huge: Cannot satisfy [mem 0xf8000000-0xf8200000] with a huge-page mapping due to MTRR override.
[ 1.269301] r8169 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 1.295584] resource sanity check: requesting [mem 0x000c0000-0x000dffff], which spans more than PCI Bus 0000:00 [mem 0x000d0000-0x000d3fff window]
[ 1.295588] caller pci_map_rom+0x6a/0x1d0 mapping multiple BARs
[ 1.606245] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
[ 1.606254] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT0._GTF, AE_NOT_FOUND (20180810/psparse-516)
[ 1.607576] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
[ 1.607583] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT0._GTF, AE_NOT_FOUND (20180810/psparse-516)
[ 1.608922] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT3._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
[ 1.608929] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT3._GTF, AE_NOT_FOUND (20180810/psparse-516)
[ 1.613841] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT3._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
[ 1.613849] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT3._GTF, AE_NOT_FOUND (20180810/psparse-516)
[ 5.786040] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20180810/utaddress-213)
[ 5.786047] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20180810/utaddress-213)
[ 5.786050] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20180810/utaddress-213)
[ 5.786053] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20180810/utaddress-213)
[ 5.786056] lpc_ich: Resource conflict(s) found affecting gpio_ich
....
Edit: But why using the linux-headers-4.19.0-5-amd64 , instead the the linux-headers-4.19.0-5-common ?
Re: testing for MX 18.3
Posted: Sat May 11, 2019 8:17 pm
by dolphin_oracle
oops wrote: Sat May 11, 2019 7:57 pm
here, with: linux-headers-4.19.0-5-common ... &. ... linux-image-4.19.0-5-amd64-unsigned
Code: Select all
cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.19.0-5-amd64 ..... quiet
Every things are ok here, I have the same warnings as usual due to a buggy bios:
Code: Select all
dmesg -k -l emerg,alert,crit,err,warn
[ 0.000000] secureboot: Secure boot could not be determined (mode 0)
[ 0.176121] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[ 0.176121] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
[ 0.189946] pmd_set_huge: Cannot satisfy [mem 0xf8000000-0xf8200000] with a huge-page mapping due to MTRR override.
[ 1.269301] r8169 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 1.295584] resource sanity check: requesting [mem 0x000c0000-0x000dffff], which spans more than PCI Bus 0000:00 [mem 0x000d0000-0x000d3fff window]
[ 1.295588] caller pci_map_rom+0x6a/0x1d0 mapping multiple BARs
[ 1.606245] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
[ 1.606254] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT0._GTF, AE_NOT_FOUND (20180810/psparse-516)
[ 1.607576] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
[ 1.607583] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT0._GTF, AE_NOT_FOUND (20180810/psparse-516)
[ 1.608922] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT3._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
[ 1.608929] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT3._GTF, AE_NOT_FOUND (20180810/psparse-516)
[ 1.613841] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT3._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
[ 1.613849] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT3._GTF, AE_NOT_FOUND (20180810/psparse-516)
[ 5.786040] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20180810/utaddress-213)
[ 5.786047] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20180810/utaddress-213)
[ 5.786050] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20180810/utaddress-213)
[ 5.786053] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20180810/utaddress-213)
[ 5.786056] lpc_ich: Resource conflict(s) found affecting gpio_ich
....
Edit: But why using the linux-headers-4.19.0-5-amd64 , instead the the linux-headers-4.19.0-5-common ?
--common is a depend of --amd64 and --i386, so you should have them both.
Re: testing for MX 18.3
Posted: Sat May 11, 2019 8:19 pm
by fehlix
oops wrote: Sat May 11, 2019 7:57 pm
But why using the linux-headers-4.19.0-5-amd64 , instead the the linux-headers-4.19.0-5-common ?
Because your need them both:
Code: Select all
LANG=fr_FR.UTF-8 apt search 'linux-(image|headers)-4.19.0-5'
En train de trier... Fait
Recherche en texte intégral... Fait
linux-headers-4.19.0-5-amd64/now 4.19.37-1~mx17+1 amd64 [installé, local]
Header files for Linux 4.19.0-5-amd64
linux-headers-4.19.0-5-common/now 4.19.37-1~mx17+1 all [installé, local]
Common header files for Linux 4.19.0-5
linux-image-4.19.0-5-amd64-unsigned/now 4.19.37-1~mx17+1 amd64 [installé, local]
Linux 4.19 for 64-bit PCs
Re: testing for MX 18.3
Posted: Sat May 11, 2019 8:28 pm
by dolphin_oracle
everything appears to be working for me as well. can't see anything going odd. this is on a system that's been updated since mx-18
Re: testing for MX 18.3
Posted: Sat May 11, 2019 8:29 pm
by oops
... Ah OK, thank you for the info. Everything appears to working fine here too.
Re: testing for MX 18.3
Posted: Sat May 11, 2019 8:34 pm
by richb
OK for me as well.
Re: testing for MX 18.3
Posted: Sat May 11, 2019 9:54 pm
by Stevo
Running fine for me since I built the packages, too. For those interested, the MX 18 kernel is 4.19.0-1, based on 4.19.5, while 4.19.0-5 is backported from the latest 4.19 LTS release to make it into Debian Sid, 4.19.37, so should have a load of bugfixes.You can look at the Debian changelog it installs on your system in /usr/share/doc--Debian lists every bugfix in it. It will probably make it into Buster soon.
Re: testing for MX 18.3
Posted: Sat May 11, 2019 10:14 pm
by i_ri
hello dolphin_oracle and everyone
remove 4.19.0-1amd64
replace 4.19.0-5amd64 [4.19.37]
on the installed system. _x64
all works as previous about one degree warmer overall.
Will check live usb after making some updates for that.
okay back with edit: about live .
usb live MX 18.2 GENERAL live-kernel-updater to 4.19.0-5amd64.
Fired up live on three varied machines pc successfully.
A fourth machine, hp a1410y desktop, trial default=no, trial safe video = no, trial failsafe = success with everything working; amd ATI RC410; though running the llvmpipe. posting from machine number four here now.
Re: testing for MX 18.3
Posted: Sun May 12, 2019 3:50 am
by Richard
On T430 as in Sig & Quick Info,
Installed kernel 4.19.0-5-amd64 via MXPI:
Virtualbox boots Win7 after reboot.
[These temps normal for this laptop.]
Snapshot temps about same as Liquorix-5.0.0-8.1
Avg. 86°C with Max peaks to 90°C, 4 proc ,
35 to 40 min to complete.
15 min. Idle Temps:. CORRECTED
MX-4.19.0-5:......... 50′C 44′C. Fan 3792 rpm
....after properly config intel_pstate for 4.19.0-5
Liquorix-5.0.0-8.1: 58′C 53′C. Fan 3978 rpm
Output from install with MXPI:
Code: Select all
Selecting previously unselected package linux-headers-4.19.0-5-common.
(Reading database ... 298373 files and directories currently installed.)
Preparing to unpack .../0-linux-headers-4.19.0-5-common_4.19.37-1~mx17+1_all.deb ...
Unpacking linux-headers-4.19.0-5-common (4.19.37-1~mx17+1) ...
Selecting previously unselected package linux-headers-4.19.0-5-amd64.
Preparing to unpack .../1-linux-headers-4.19.0-5-amd64_4.19.37-1~mx17+1_amd64.deb ...
Unpacking linux-headers-4.19.0-5-amd64 (4.19.37-1~mx17+1) ...
Selecting previously unselected package linux-headers-4.19.0-5-cloud-amd64.
Preparing to unpack .../2-linux-headers-4.19.0-5-cloud-amd64_4.19.37-1~mx17+1_amd64.deb ...
Unpacking linux-headers-4.19.0-5-cloud-amd64 (4.19.37-1~mx17+1) ...
Selecting previously unselected package linux-headers-4.19.0-5-common-rt.
Preparing to unpack .../3-linux-headers-4.19.0-5-common-rt_4.19.37-1~mx17+1_all.deb ...
Unpacking linux-headers-4.19.0-5-common-rt (4.19.37-1~mx17+1) ...
Selecting previously unselected package linux-headers-4.19.0-5-rt-amd64.
Preparing to unpack .../4-linux-headers-4.19.0-5-rt-amd64_4.19.37-1~mx17+1_amd64.deb ...
Unpacking linux-headers-4.19.0-5-rt-amd64 (4.19.37-1~mx17+1) ...
Selecting previously unselected package linux-headers-4.19.0-5-all-amd64.
Preparing to unpack .../5-linux-headers-4.19.0-5-all-amd64_4.19.37-1~mx17+1_amd64.deb ...
Unpacking linux-headers-4.19.0-5-all-amd64 (4.19.37-1~mx17+1) ...
Selecting previously unselected package linux-image-4.19.0-5-amd64-unsigned.
Preparing to unpack .../6-linux-image-4.19.0-5-amd64-unsigned_4.19.37-1~mx17+1_amd64.deb ...
Unpacking linux-image-4.19.0-5-amd64-unsigned (4.19.37-1~mx17+1) ...
Setting up linux-headers-4.19.0-5-common-rt (4.19.37-1~mx17+1) ...
Setting up linux-headers-4.19.0-5-common (4.19.37-1~mx17+1) ...
Setting up linux-headers-4.19.0-5-cloud-amd64 (4.19.37-1~mx17+1) ...
/etc/kernel/header_postinst.d/dkms:
Warning: Unable to find an initial ram disk that I know how to handle.
Will not try to make an initrd.
Setting up linux-headers-4.19.0-5-rt-amd64 (4.19.37-1~mx17+1) ...
/etc/kernel/header_postinst.d/dkms:
Warning: Unable to find an initial ram disk that I know how to handle.
Will not try to make an initrd.
Error! Bad return status for module build on kernel: 4.19.0-5-rt-amd64 (x86_64)
Consult /var/lib/dkms/ndiswrapper/1.61/build/make.log for more information.
Setting up linux-headers-4.19.0-5-amd64 (4.19.37-1~mx17+1) ...
/etc/kernel/header_postinst.d/dkms:
Warning: Unable to find an initial ram disk that I know how to handle.
Will not try to make an initrd.
Error! Module version 6.0.4_Debian for vboxvideo.ko
is not newer than what is already found in kernel 4.19.0-5-amd64 (6.0.4_Debian).
You may override by specifying --force.
Setting up linux-image-4.19.0-5-amd64-unsigned (4.19.37-1~mx17+1) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-5.0.0-8.1-liquorix-amd64
I: /initrd.img.old is now a symlink to boot/initrd.img-5.0.0-8.1-liquorix-amd64
I: /vmlinuz is now a symlink to boot/vmlinuz-4.19.0-5-amd64
I: /initrd.img is now a symlink to boot/initrd.img-4.19.0-5-amd64
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.19.0-5-amd64
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
using custom appearance settings
Found linux image: /boot/vmlinuz-5.0.0-8.1-liquorix-amd64
Found initrd image: /boot/initrd.img-5.0.0-8.1-liquorix-amd64
Found linux image: /boot/vmlinuz-4.19.0-5-amd64
Found initrd image: /boot/initrd.img-4.19.0-5-amd64
Found linux image: /boot/vmlinuz-4.19.0-1-amd64
Found initrd image: /boot/initrd.img-4.19.0-1-amd64
Found memtest86+ image: /boot/memtest86+.bin
done
Setting up linux-headers-4.19.0-5-all-amd64 (4.19.37-1~mx17+1) ...
Successfully applied all changes. You can close the window now.
On T430 laptop:
Code: Select all
System: Host: MX18x64 Kernel: 5.0.0-8.1-liquorix-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0
Desktop: Xfce 4.12.3 Distro: MX-18.2_x64 Continuum December 17 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: 24.9 Wh condition: 25.8/56.2 Wh (46%) model: SANYO 45N1001
status: Unknown
CPU: Topology: Dual Core model: Intel Core i5-3320M bits: 64 type: MT MCP arch: Ivy Bridge
rev: 9 L2 cache: 3072 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 20752
Speed: 1297 MHz min/max: 1200/3300 MHz Core speeds (MHz): 1: 1297 2: 1495 3: 1539
4: 1489
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: k5.0.0-8.1-liquorix-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: down 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: 96.09 GiB (64.8%)
ID-1: /dev/mmcblk0 model: SA32G size: 29.05 GiB
ID-2: /dev/sda vendor: Samsung model: SSD 840 PRO Series size: 119.24 GiB
Partition: ID-1: / size: 20.54 GiB used: 9.86 GiB (48.0%) fs: ext4 dev: /dev/sda2
Sensors: System Temperatures: cpu: 78.0 C mobo: N/A
Fan Speeds (RPM): cpu: 4115
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://mirror.cedia.org.ec/mx-workspace/antix/stretch/ stretch main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://ftp.br.debian.org/debian/ stretch-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://ftp.br.debian.org/debian/ stretch non-free contrib main
2: deb http://security.debian.org/ stretch/updates non-free contrib main
Active apt repos in: /etc/apt/sources.list.d/home_Alexx2000.list
1: deb http://download.opensuse.org/repositories/home:/Alexx2000/Debian_9.0/ /
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mirror.cedia.org.ec/mx-workspace/mx/repo/ stretch non-free main
Info: Processes: 254 Uptime: 1h 40m Memory: 7.48 GiB used: 1.47 GiB (19.6%) Init: SysVinit
runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.33
Re: testing for MX 18.3
Posted: Sun May 12, 2019 6:43 pm
by teddyk67
Hello everyone.
On 32-bit, the upgraded kernel works for me as well.
Re: testing for MX 18.3
Posted: Sun May 12, 2019 9:25 pm
by JeffA
dolphin_oracle wrote: Sat May 11, 2019 7:13 pm
If folks could test this package (easiest from MX-Packageinstaller-> Test Repo) that would really help.
64bit
linux-image-4.19.0-5-amd64-unsigned
linux-headers-4.19.0-5-amd64
Installed and booted into it now.
Will report if any problems.
Just to note I installed it from the Stable Repo, which may explain why I didn't see it in the Test Repo when I first saw this thread yesterday.
Re: testing for MX 18.3
Posted: Sun May 12, 2019 9:58 pm
by dolphin_oracle
Good to know.
And thanks.everyone
Re: testing for MX 18.3
Posted: Sun May 12, 2019 10:40 pm
by figueroa
Upgraded using Synaptic in an up-to-date and well used VirtualBox 64 bit virtual machine. Now:
Code: Select all
uname -a
Linux mxvb 4.19.0-5-amd64 #1 SMP Debian 4.19.37-1~mx17+1 (2019-05-09) x86_64 GNU/Linux
Booted cleanly. During upgrade, there were some errors in the console output, but they appear to have resolved themsleves.
From Apt history.log:
Code: Select all
Install: linux-image-4.19.0-5-amd64-unsigned:amd64 (4.19.37-1~mx17+1), linux-headers-4.19.0-5-amd64:amd64 (4.19.37-1~mx17+1), linux-headers-4.19.0-5-common:amd64 (4.19.37-1~mx17+1, automatic)
Upgrade: linux-kbuild-4.19:amd64 (4.19.5-2~mx17+1, 4.19.37-1~mx17+1)
From Apt term.log follows:
Code: Select all
Log started: 2019-05-12 22:26:36
Selecting previously unselected package linux-headers-4.19.0-5-common.
(Reading database ... 345021 files and directories currently installed.)
Preparing to unpack .../linux-headers-4.19.0-5-common_4.19.37-1~mx17+1_all.deb ...
Unpacking linux-headers-4.19.0-5-common (4.19.37-1~mx17+1) ...
Preparing to unpack .../linux-kbuild-4.19_4.19.37-1~mx17+1_amd64.deb ...
Unpacking linux-kbuild-4.19 (4.19.37-1~mx17+1) over (4.19.5-2~mx17+1) ...
Selecting previously unselected package linux-headers-4.19.0-5-amd64.
Preparing to unpack .../linux-headers-4.19.0-5-amd64_4.19.37-1~mx17+1_amd64.deb ...
Unpacking linux-headers-4.19.0-5-amd64 (4.19.37-1~mx17+1) ...
Selecting previously unselected package linux-image-4.19.0-5-amd64-unsigned.
Preparing to unpack .../linux-image-4.19.0-5-amd64-unsigned_4.19.37-1~mx17+1_amd64.deb ...
Unpacking linux-image-4.19.0-5-amd64-unsigned (4.19.37-1~mx17+1) ...
Setting up linux-headers-4.19.0-5-common (4.19.37-1~mx17+1) ...
Setting up linux-kbuild-4.19 (4.19.37-1~mx17+1) ...
Setting up linux-headers-4.19.0-5-amd64 (4.19.37-1~mx17+1) ...
/etc/kernel/header_postinst.d/dkms:
Error! Could not locate dkms.conf file.
File: does not exist.
Warning: Unable to find an initial ram disk that I know how to handle.
Will not try to make an initrd.
Setting up linux-image-4.19.0-5-amd64-unsigned (4.19.37-1~mx17+1) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-4.19.0-1-amd64
I: /initrd.img.old is now a symlink to boot/initrd.img-4.19.0-1-amd64
I: /vmlinuz is now a symlink to boot/vmlinuz-4.19.0-5-amd64
I: /initrd.img is now a symlink to boot/initrd.img-4.19.0-5-amd64
/etc/kernel/postinst.d/dkms:
Error! Could not locate dkms.conf file.
File: does not exist.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.19.0-5-amd64
I: The initramfs will attempt to resume from /dev/sda2
I: (UUID=79d2e9a0-df0f-467e-8668-5aa3cc9c2e76)
I: Set the RESUME variable to override this.
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
using custom appearance settings
Found background image: /usr/share/backgrounds/MXLinux/grub/mxreflection_by_ant_ony.png
Found linux image: /boot/vmlinuz-4.19.0-5-amd64
Found initrd image: /boot/initrd.img-4.19.0-5-amd64
Found linux image: /boot/vmlinuz-4.19.0-1-amd64
Found initrd image: /boot/initrd.img-4.19.0-1-amd64
Found linux image: /boot/vmlinuz-4.13.0-1-amd64
Found initrd image: /boot/initrd.img-4.13.0-1-amd64
Found memtest86+ image: /boot/memtest86+.bin
done
Log ended: 2019-05-12 22:28:16
Re: testing for MX 18.3
Posted: Mon May 13, 2019 9:06 am
by manyroads
I received the same messages as @Richard but the upgrade went well. My niggling VirtualBox even worked with this kernel (which is the first kernel beyond 4.19.0-1 that worked. :)
Re: testing for MX 18.3
Posted: Mon May 13, 2019 10:11 am
by beardedragon
Well, as you can see below this kernel works on a fully installed MX 18.2. A few questions if you don't mind, like, when is this MX 18.3 coming out and is it going to have the new version of Xfce?
$ inxi -Fxzc0
System: Host: MX Kernel: 4.19.0-5-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0
Desktop: Xfce 4.12.3 Distro: MX-18.2_x64 Continuum Apr 7 2019
base: Debian GNU/Linux 9 (stretch)
Graphics: Device-1: NVIDIA GK208 [GeForce GT 720] vendor: Micro-Star MSI driver: nvidia
v: 410.104 bus ID: 01:00.0
Display: x11 server: X.Org 1.19.2 driver: nvidia resolution: 1920x1080~60Hz
OpenGL: renderer: GeForce GT 720/PCIe/SSE2 v: 4.6.0 NVIDIA 410.104 direct render: Yes
Re: testing for MX 18.3
Posted: Mon May 13, 2019 10:39 am
by Adrian
when is this MX 18.3 coming out and is it going to have the new version of Xfce
No, that's not the purpose of 18.3, it's mostly a ISO refresh, with a fixed and improved installer, and a updated kernel.
Re: testing for MX 18.3
Posted: Mon May 13, 2019 10:42 am
by beardedragon
Adrian wrote: Mon May 13, 2019 10:39 am
when is this MX 18.3 coming out and is it going to have the new version of Xfce
No, that's not the purpose of 18.3, it's mostly a ISO refresh, with a fixed and improved installer, and a updated kernel.
The first question is "When?"
Re: testing for MX 18.3
Posted: Mon May 13, 2019 10:51 am
by manyroads
beardedragon wrote: Mon May 13, 2019 10:42 am
Adrian wrote: Mon May 13, 2019 10:39 am
when is this MX 18.3 coming out and is it going to have the new version of Xfce
No, that's not the purpose of 18.3, it's mostly a ISO refresh, with a fixed and improved installer, and a updated kernel.
The first question is "When?"
What I saw from @Dolphin_Oracle in a thread here was an estimate for MX with Buster sometime in late summer-early fall (Northern Hemisphere). That's half of your question...
Re: testing for MX 18.3
Posted: Mon May 13, 2019 11:25 am
by beardedragon
What I saw from @Dolphin_Oracle in a thread here was an estimate for MX with Buster sometime in late summer-early fall (Northern Hemisphere). That's half of your question...
[/quote]
Thanks!
Re: testing for MX 18.3
Posted: Mon May 13, 2019 11:41 am
by asqwerth
MX18.3 won't be Buster. This is supposed to be an updated version of MX18 with bug fixes.
Re: testing for MX 18.3
Posted: Mon May 13, 2019 11:43 am
by beardedragon
asqwerth wrote: Mon May 13, 2019 11:41 am
MX18.3 won't be Buster. This is supposed to be an updated version of MX18 with bug fixes.
Ahah, so will it be available as a normal upgrade?
Re: testing for MX 18.3
Posted: Mon May 13, 2019 11:48 am
by Paul..
Correct
Re: testing for MX 18.3
Posted: Mon May 13, 2019 12:14 pm
by dolphin_oracle
18.3 will be approximately released when its ready. but May. Maybe an RC this week. Stay tuned.
Re: testing for MX 18.3
Posted: Mon May 13, 2019 12:16 pm
by dolphin_oracle
beardedragon wrote: Mon May 13, 2019 11:25 am
What I saw from @Dolphin_Oracle in a thread here was an estimate for MX with Buster sometime in late summer-early fall (Northern Hemisphere). That's half of your question...
Thanks!
[/quote]
yeah, 19 will be buster. and despite buster's "feature freeze", its still a moving target. I'm not even joking a little. If we did a buster release a month ago, recent updates would have broken it. They keep shifting dependencies definitions on certain key packages.
but if you want to get in on the early buster goodness, check out antiX 19 alpha. its rough but alphas are supposed to be
Re: testing for MX 18.3
Posted: Mon May 13, 2019 1:22 pm
by manyroads
dolphin_oracle wrote: Mon May 13, 2019 12:16 pm
[...]
but if you want to get in on the early buster goodness, check out antiX 19 alpha. its rough but alphas are supposed to be
Sorry for being off topic but...
I have to say I like the antiX19 alpha. I have been trying really hard to tweak every knob I know and a many that I don't; it runs like the Eveready bunny and just keeps on ticking.
Re: testing for MX 18.3
Posted: Mon May 13, 2019 1:37 pm
by figueroa
dolphin_oracle wrote: Sat May 11, 2019 7:13 pm
64bit
linux-image-4.19.0-5-amd64-unsigned
linux-headers-4.19.0-5-amd64
32 bit
linux-image-4.19.0-5-686-pae-unsigned
linux-headers-4.19.0-5-686-pae
Upgraded both on identical older hardware using Synamptic. Works fine as intended.
Code: Select all
Type: Desktop Mobo: PCCHIPS model: A15G serial: <root required>
BIOS: American Megatrends v: 080015 date: 08/13/2009
CPU: Dual Core: AMD Athlon 7850 type: MCP speed: 1400 MHz min/max: 1400/2800 MHz
Graphics: Device-1: NVIDIA C61 [GeForce 6150SE nForce 430] driver: nouveau v: kernel
The 32 bit machine had been running 4.15.0-1 and also has VirtualBox installed.
The 64 bit machine had been running 4.19.0-1 with no VirtualBox installed.
Re: testing for MX 18.3
Posted: Mon May 13, 2019 2:45 pm
by beardedragon
manyroads wrote: Mon May 13, 2019 1:22 pm
dolphin_oracle wrote: Mon May 13, 2019 12:16 pm
[...]
but if you want to get in on the early buster goodness, check out antiX 19 alpha. its rough but alphas are supposed to be
Sorry for being off topic but...
I have to say I like the antiX19 alpha. I have been trying really hard to tweak every knob I know and a many that I don't; it runs like the Eveready bunny and just keeps on ticking.
I hopped over here:
System:
Host: debian Kernel: 4.19.0-4-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
Desktop: Xfce 4.12.4 Distro: Debian GNU/Linux buster/sid
Just testing.
Re: testing for MX 18.3
Posted: Mon May 13, 2019 2:53 pm
by mx-2018
dolphin_oracle wrote: Mon May 13, 2019 12:16 pm
...
yeah, 19 will be buster. and despite buster's "feature freeze", its still a moving target. I'm not even joking a little. If we did a buster release a month ago, recent updates would have broken it. They keep shifting dependencies definitions on certain key packages....
And despite the challenge, the MX team have been able to keep the MX Linux stable?
RESPECT!
Re: testing for MX 18.3
Posted: Mon May 13, 2019 9:09 pm
by Stevo
mx-2018 wrote: Mon May 13, 2019 2:53 pm
dolphin_oracle wrote: Mon May 13, 2019 12:16 pm
...
yeah, 19 will be buster. and despite buster's "feature freeze", its still a moving target. I'm not even joking a little. If we did a buster release a month ago, recent updates would have broken it. They keep shifting dependencies definitions on certain key packages....
And despite the challenge, the MX team have been able to keep the MX Linux stable?
RESPECT!
There hasn't been a Buster edition of MX yet, so...no challenge yet.
Re: testing for MX 18.3
Posted: Mon May 13, 2019 9:50 pm
by Richard
New Kernel Question? Never mind.
Found the answer on D_O's original post.
The 4.19.0-5-amd64 is working very well, plus it is normally some 8 to 10°C cooler. than with the Liquorix-5.0.0-8.1-amd64; once I got intel_pstate & thermald properly configured.
Re: testing for MX 18.3
Posted: Tue May 14, 2019 11:11 pm
by Sanji
Hi
I tested the
linux-image-4.19.0-5-amd64-unsigned
kernel just now.
For me it has the same problem which the previous 4.19 kernel had where the system can freeze up. I can confirm that this is still an issue for me on the newer updated 4.19 kernel.
I will go back to using the 4.20 antiX kernel which works fine for me.
Re: testing for MX 18.3
Posted: Mon May 20, 2019 9:06 am
by i_ri
hello dolphin_oracle and Steveo
Coming back to this topic This is where it started for this machine upgraded to the 4.19.0-5 when it was presented here.
MX-18.2_x64 today looked at update packages. On the listing there is a update for the 4.19.37-1 [disguised as 4.19.0-5] update to 4.19.37-2.
There became available a 4.19.43 yesterday so selcted to upgrade to that instead. Now machine is running 4.19.43 But the 4.19.37-2 is still on the update list. upgrading would install 4.19.37-2. (It has the kbuild too.)
What direction to take to iron out this wrinkle? 4.19.37-2 or 4.19.43?
Re: testing for MX 18.3
Posted: Mon May 20, 2019 9:23 am
by dolphin_oracle
I don't know where your 43 is coming from, but we are looking at 37-2 for the 18.3 iso.
Re: testing for MX 18.3
Posted: Mon May 20, 2019 9:42 am
by AK-47
i_ri wrote: Mon May 20, 2019 9:06 am4.19.37-1 [disguised as 4.19.0-5]
I can easily see why that convention is confusing. Is that something out of Debian or is that an MX/antiX convention?
Re: testing for MX 18.3
Posted: Mon May 20, 2019 10:16 am
by kmathern
dolphin_oracle wrote: Mon May 20, 2019 9:23 am
I don't know where your 43 is coming from, but we are looking at 37-2 for the 18.3 iso.
It looks like it's up to a -3 (4.19.37-3) now in buster & stretch-backports:
https://packages.debian.org/source/buster/linux
edit: nevermind, -3 was just to fix a fail to build problem for powerpc, so -2 is probably still okay to use:
https://metadata.ftp-master.debian.org/ ... _changelog
43 is a antiX kernel
Code: Select all
linux-image-4.19.43-antix.1-amd64-smp 4.19.43-antix.1-amd64-smp-1 http://la.mxrepo.com/antix/stretch/
linux-image-4.19.0-5-rt-amd64-unsigned 4.19.37-2~mx17+1 http://la.mxrepo.com/mx/repo/
linux-image-4.19.0-5-cloud-amd64-unsigned 4.19.37-2~mx17+1 http://la.mxrepo.com/mx/repo/
linux-image-4.19.0-5-amd64-unsigned 4.19.37-2~mx17+1 http://la.mxrepo.com/mx/repo/
Re: testing for MX 18.3
Posted: Mon May 20, 2019 11:55 am
by figueroa
Debian renumbers the kernels released by upstream (kernel.org) according to its own convention. Its always been a little confusing. MX sticks with the Debian number. You can see exactly which kernel you are running on the first line of dmesg output:
Code: Select all
$ dmesg | head -1
[ 0.000000] Linux version 4.19.0-5-amd64 (stevep@mxlinux.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 SMP Debian 4.19.37-2~mx17+1 (2019-05-15)
Re: testing for MX 18.3
Posted: Mon May 20, 2019 12:14 pm
by dolphin_oracle
Re: testing for MX 18.3
Posted: Mon May 20, 2019 9:52 pm
by i_ri
hello dolphin_oracle and SteveO
uname -a? not when I can have a chuckle with any chance to type inxi -bs.
machine allowed the upgrade of 4.19.37. It boots to the 4.19.43.
I think that is the first time a update to a previous kernel has been encountered here. Now I know the outcome.
Re: testing for MX 18.3
Posted: Tue May 21, 2019 2:55 am
by watsoccurring
18.3-rc1 out in Distrowatch
Re: testing for MX 18.3
Posted: Tue May 21, 2019 3:39 am
by jackdanielsesq
URL?
Cannot see it anywhere
Jack
watsoccurring wrote: Tue May 21, 2019 2:55 am
18.3-rc1 out in Distrowatch
Re: testing for MX 18.3
Posted: Tue May 21, 2019 4:05 am
by watsoccurring
It is at the moment at the top of the latest releases:
https://sourceforge.net/projects/mx-lin ... rror=netix
Re: testing for MX 18.3
Posted: Tue May 21, 2019 7:52 am
by JayM
I installed it on my old 32-bit netbook and will experiment with it tomorrow or so, when I have time. It was extremely slow booting from the live USB with perst_static enabled, with lots of 100% CPU utilization per the conky, which I was going to complain about but then I remembered that all of the other times I'd used a persistent USB on that machine I'd selected perst_all which uses the RAM. It seems OK speed-wide after having been installed, at least no worse that MX 18.2 on the same machine. (I love the new installer!)
Re: testing for MX 18.3
Posted: Tue May 21, 2019 7:58 am
by dolphin_oracle
FYI, there was a problem with those isos, so they have been removed. Probably be back up later today.
Re: testing for MX 18.3
Posted: Tue May 21, 2019 8:09 am
by JayM
dolphin_oracle wrote: Tue May 21, 2019 7:58 am
FYI, there was a problem with those isos, so they have been removed. Probably be back up later today.
That would be tonight where I live.
Thanks for the heads-up. Will I need to redownload/reburn/reinstall?
Re: testing for MX 18.3
Posted: Tue May 21, 2019 8:17 am
by dolphin_oracle
JayM wrote: Tue May 21, 2019 8:09 am
dolphin_oracle wrote: Tue May 21, 2019 7:58 am
FYI, there was a problem with those isos, so they have been removed. Probably be back up later today.
That would be tonight where I live.
Thanks for the heads-up. Will I need to redownload/reburn/reinstall?
no. if you already installed, then you will get fix in regular updates. had to do with mmcblk devices.
Re: testing for MX 18.3
Posted: Mon May 27, 2019 4:37 pm
by beardedragon
With the final release of MX 18.3 :
Been running it for a couple days, seems it had a bug in it with nvidia, but, that has since cleared up. It changed display settings to 1280x960, don't know why? I could not get 1920x1080. I reinstalled MX18.3 and I guess the change in kernels made a difference. The first time I ran Antix 5.1.2-64 and this time I used Liquorix 5.0.0-18.1.
Code: Select all
bob@MX18.3:~
$ inxi -Fxzc0
System: Host: MX18.3 Kernel: 5.0.0-18.1-liquorix-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0
Desktop: Xfce 4.12.3 Distro: MX-18.3_x64 Continuum May 26 2019
base: Debian GNU/Linux 9 (stretch)
Machine: Type: Desktop System: LENOVO product: 10181 v: Lenovo K450e serial: <filter>
Mobo: LENOVO model: N/A v: 31900058 STD serial: <filter> BIOS: LENOVO v: I1KT38AUS
date: 06/10/2014
Battery: Device-1: hidpp_battery_0 model: Logitech M570 charge: 85% status: Discharging
CPU: Topology: Quad Core model: Intel Core i5-4460 bits: 64 type: MCP arch: Haswell rev: 3
L2 cache: 6144 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 25541
Speed: 938 MHz min/max: 800/3400 MHz Core speeds (MHz): 1: 885 2: 877 3: 859 4: 865
Graphics: Device-1: NVIDIA GK208 [GeForce GT 720] vendor: Micro-Star MSI driver: nvidia
v: 418.74 bus ID: 01:00.0
Display: x11 server: X.Org 1.19.2 driver: nvidia resolution: 1920x1080~60Hz
OpenGL: renderer: GeForce GT 720/PCIe/SSE2 v: 4.6.0 NVIDIA 418.74 direct render: Yes
Audio: Device-1: Intel 8 Series/C220 Series High Definition Audio vendor: Lenovo
driver: snd_hda_intel v: kernel bus ID: 00:1b.0
Device-2: NVIDIA GK208 HDMI/DP Audio vendor: Micro-Star MSI driver: snd_hda_intel
v: kernel bus ID: 01:00.1
Sound Server: ALSA v: k5.0.0-18.1-liquorix-amd64
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Lenovo
driver: r8169 v: kernel port: d000 bus ID: 03:00.0
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Realtek RTL8821AE 802.11ac PCIe Wireless Network Adapter vendor: Lenovo
driver: rtl8821ae v: kernel port: c000 bus ID: 04:00.0
IF: wlan0 state: down mac: <filter>
Drives: Local Storage: total: 1.82 TiB used: 81.01 GiB (4.3%)
ID-1: /dev/sda vendor: Western Digital model: WD10EZEX-08M2NA0 size: 931.51 GiB
ID-2: /dev/sdd type: USB vendor: Western Digital model: WD Elements 25A2
size: 931.48 GiB
Partition: ID-1: / size: 913.89 GiB used: 25.45 GiB (2.8%) fs: ext4 dev: /dev/sda1
ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2
Sensors: System Temperatures: cpu: 44.0 C mobo: N/A gpu: nvidia temp: 51 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 28%
Info: Processes: 244 Uptime: 3h 59m Memory: 7.72 GiB used: 1.13 GiB (14.7%) Init: SysVinit
runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.33
Re: testing for MX 18.3
Posted: Mon May 27, 2019 4:58 pm
by Jerry3904
Thanks everybody, I'm closing this thread now that it's been released.