testing for MX 18.3

Forum rules
Locked
Message
Author
User avatar
dolphin_oracle
Developer
Posts: 22248
Joined: Sun Dec 16, 2007 12:17 pm

testing for MX 18.3

#1 Post 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.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
Top
User avatar
fehlix
Developer
Posts: 12700
Joined: Wed Apr 11, 2018 5:09 pm

Re: testing for MX 18.3

#2 Post 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.
Top
User avatar
oops
Posts: 1913
Joined: Tue Apr 10, 2018 5:07 pm

Re: testing for MX 18.3

#3 Post 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 ?
Pour les nouveaux utilisateurs: Alt+F1 pour le manuel, ou FAQS, MX MANUEL, et Conseils Debian - Info. système “quick-system-info-mx” (QSI) ... Ici: System: MX-19_x64 & antiX19_x32
Top
User avatar
dolphin_oracle
Developer
Posts: 22248
Joined: Sun Dec 16, 2007 12:17 pm

Re: testing for MX 18.3

#4 Post 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.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
Top
User avatar
fehlix
Developer
Posts: 12700
Joined: Wed Apr 11, 2018 5:09 pm

Re: testing for MX 18.3

#5 Post 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
:puppy:
Top
User avatar
dolphin_oracle
Developer
Posts: 22248
Joined: Sun Dec 16, 2007 12:17 pm

Re: testing for MX 18.3

#6 Post 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
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
Top
User avatar
oops
Posts: 1913
Joined: Tue Apr 10, 2018 5:07 pm

Re: testing for MX 18.3

#7 Post by oops »

... Ah OK, thank you for the info. Everything appears to working fine here too.
Pour les nouveaux utilisateurs: Alt+F1 pour le manuel, ou FAQS, MX MANUEL, et Conseils Debian - Info. système “quick-system-info-mx” (QSI) ... Ici: System: MX-19_x64 & antiX19_x32
Top
User avatar
richb
Administrator
Posts: 10890
Joined: Wed Jul 12, 2006 2:17 pm

Re: testing for MX 18.3

#8 Post by richb »

OK for me as well.
Forum Rules
Guide - How to Ask for Help

richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
Top
User avatar
Stevo
Developer
Posts: 14565
Joined: Fri Dec 15, 2006 7:07 pm

Re: testing for MX 18.3

#9 Post 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.
Top
User avatar
i_ri
Posts: 1098
Joined: Tue Jun 30, 2015 12:26 am

Re: testing for MX 18.3

#10 Post 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.
Top
Locked

Return to “General”