MX-19: FEEDBACK of latest GRUB 2.04-9~mx19+5 update

[SwampRabbit]

A new version of GRUB (GRUB 2.04-9~mx19+5) is in the MX Test Repo for those willing to test.
ABOVE INFORMATION IS OLD, THIS IS NOW IN THE STABLE REPO

Again please do NOT test this on production machines unless you can recover from a back up.

If you are going to test, please use the MX Test Repo tab in MX Package Installer (the packages will show as up-gradable there), please do NOT enable the MX Test Repo manually.

It has been reviewed and tested - Note we are going from a +1 at the end of the file to a +5 thanks to all the hard work by fehlix over the last few days.
Right now we don't know if there is a small chance of this breaking anything or not, but its good to play it safe until some more users can report they don't have issues.

IF you are willing to test, please post your QSI.

Thanks!

[dolphin_oracle]

installed and running. no questions during startup.

my sda and sdb designations switched AFTER the grub updated. don't know what that's about but I had to run a second update-grub to correct the issue.

output from the update:

Code: Select all

2020-08-05 21:19:01.552 DBG default: "The following packages will be upgraded:\n  grub-common grub-efi-amd64-bin grub-efi-ia32-bin grub-pc grub-pc-bin grub2"
2020-08-05 21:19:01.556 DBG default: "grub2-common"
2020-08-05 21:19:01.868 DBG default: "7 upgraded, 0 newly installed, 0 to remove and 113 not upgraded.\nNeed to get 5,651 kB of archives.\nAfter this operation, 1,024 B of additional disk space will be used.\nGet:1 http://mxrepo.com/mx/testrepo buster/test amd64 grub-efi-amd64-bin amd64 2.04-9~mx19+5 [696 kB]"
2020-08-05 21:19:02.502 DBG default: "Get:2 http://mxrepo.com/mx/testrepo buster/test amd64 grub2 amd64 2.04-9~mx19+5 [2,580 B]"
2020-08-05 21:19:02.523 DBG default: "Get:3 http://mxrepo.com/mx/testrepo buster/test amd64 grub2-common amd64 2.04-9~mx19+5 [586 kB]"
2020-08-05 21:19:02.884 DBG default: "Get:4 http://mxrepo.com/mx/testrepo buster/test amd64 grub-pc amd64 2.04-9~mx19+5 [131 kB]"
2020-08-05 21:19:02.975 DBG default: "Get:5 http://mxrepo.com/mx/testrepo buster/test amd64 grub-pc-bin amd64 2.04-9~mx19+5 [966 kB]"
2020-08-05 21:19:03.689 DBG default: "Get:6 http://mxrepo.com/mx/testrepo buster/test amd64 grub-efi-ia32-bin amd64 2.04-9~mx19+5 [658 kB]"
2020-08-05 21:19:04.183 DBG default: "Get:7 http://mxrepo.com/mx/testrepo buster/test amd64 grub-common amd64 2.04-9~mx19+5 [2,612 kB]"
2020-08-05 21:19:07.019 DBG default: "Preconfiguring packages ..."
2020-08-05 21:19:07.239 DBG default: "Fetched 5,651 kB in 4s (1,280 kB/s)"
2020-08-05 21:19:08.242 DBG default: "(Reading database ... 486234 files and directories currently installed.)"
2020-08-05 21:19:08.281 DBG default: "Preparing to unpack .../0-grub-efi-amd64-bin_2.04-9~mx19+5_amd64.deb ..."
2020-08-05 21:19:08.293 DBG default: "Unpacking grub-efi-amd64-bin (2.04-9~mx19+5) over (2.04-9~mx19+3) ..."
2020-08-05 21:19:08.531 DBG default: "Preparing to unpack .../1-grub2_2.04-9~mx19+5_amd64.deb ..."
2020-08-05 21:19:08.562 DBG default: "Unpacking grub2 (2.04-9~mx19+5) over (2.04-9~mx19+3) ..."
2020-08-05 21:19:08.689 DBG default: "Preparing to unpack .../2-grub2-common_2.04-9~mx19+5_amd64.deb ..."
2020-08-05 21:19:08.701 DBG default: "Unpacking grub2-common (2.04-9~mx19+5) over (2.04-9~mx19+3) ..."
2020-08-05 21:19:08.923 DBG default: "Preparing to unpack .../3-grub-pc_2.04-9~mx19+5_amd64.deb ..."
2020-08-05 21:19:08.960 DBG default: "Unpacking grub-pc (2.04-9~mx19+5) over (2.04-9~mx19+3) ..."
2020-08-05 21:19:09.088 DBG default: "Preparing to unpack .../4-grub-pc-bin_2.04-9~mx19+5_amd64.deb ..."
2020-08-05 21:19:09.100 DBG default: "Unpacking grub-pc-bin (2.04-9~mx19+5) over (2.04-9~mx19+3) ..."
2020-08-05 21:19:09.328 DBG default: "Preparing to unpack .../5-grub-efi-ia32-bin_2.04-9~mx19+5_amd64.deb ..."
2020-08-05 21:19:09.337 DBG default: "Unpacking grub-efi-ia32-bin (2.04-9~mx19+5) over (2.04-9~mx19+3) ..."
2020-08-05 21:19:09.566 DBG default: "Preparing to unpack .../6-grub-common_2.04-9~mx19+5_amd64.deb ..."
2020-08-05 21:19:09.624 DBG default: "Unpacking grub-common (2.04-9~mx19+5) over (2.04-9~mx19+3) ..."
2020-08-05 21:19:10.145 DBG default: "Setting up grub-common (2.04-9~mx19+5) ..."
2020-08-05 21:19:10.214 DBG default: "Setting up grub-efi-amd64-bin (2.04-9~mx19+5) ..."
2020-08-05 21:19:10.227 DBG default: "Setting up grub-efi-ia32-bin (2.04-9~mx19+5) ..."
2020-08-05 21:19:10.243 DBG default: "Setting up grub2-common (2.04-9~mx19+5) ..."
2020-08-05 21:19:10.256 DBG default: "Setting up grub-pc-bin (2.04-9~mx19+5) ...\nSetting up grub-pc (2.04-9~mx19+5) ..."
2020-08-05 21:19:11.180 WRN default: "Generating grub configuration file ..."
2020-08-05 21:19:11.184 WRN default: ""
2020-08-05 21:19:11.457 WRN default: "Found theme: /boot/grub/themes/mx_linux/theme.txt"
2020-08-05 21:19:12.021 WRN default: "Found linux image: /boot/vmlinuz-5.6.0-2-amd64"
2020-08-05 21:19:12.036 WRN default: "Found initrd image: /boot/initrd.img-5.6.0-2-amd64"
2020-08-05 21:19:13.227 WRN default: "Found mtest-64.efi image: /uefi-mt/mtest-64.efi"
2020-08-05 21:19:18.417 WRN default: "Found Windows Boot Manager on /dev/sda1@/EFI/Microsoft/Boot/bootmgfw.efi"
2020-08-05 21:19:20.207 WRN default: "Found MX 19.1 patito feo (19.1 ) on /dev/sda5"
2020-08-05 21:19:22.743 WRN default: "Found MX 19.2 patito feo (19.2 ) on /dev/sda7"
2020-08-05 21:19:26.172 WRN default: "Found Ubuntu 20.04 LTS (20.04) on /dev/sda8"
2020-08-05 21:19:29.561 WRN default: "Adding boot menu entry for EFI firmware configuration"
2020-08-05 21:19:29.581 WRN default: "done"
2020-08-05 21:19:29.582 WRN default: ""
2020-08-05 21:19:29.654 DBG default: "Setting up grub2 (2.04-9~mx19+5) ..."
2020-08-05 21:19:29.674 DBG default: "Processing triggers for man-db (2.8.5-2) ..."
2020-08-05 21:19:30.541 DBG default: "Processing triggers for install-info (6.5.0.dfsg.1-4+b1) ..."
2020-08-05 21:19:30.570 WRN default: "install-info: warning: no info dir entry in `/usr/share/info/gtkdialog.info.gz'"

these entries are found on sda when the update happens, but on next boot they were sdb. the only entry really adversly affected was the windows boot manager entry.

Code: Select all

"Found Windows Boot Manager on /dev/sda1@/EFI/Microsoft/Boot/bootmgfw.efi"
2020-08-05 21:19:20.207 WRN default: "Found MX 19.1 patito feo (19.1 ) on /dev/sda5"
2020-08-05 21:19:22.743 WRN default: "Found MX 19.2 patito feo (19.2 ) on /dev/sda7"
2020-08-05 21:19:26.172 WRN default: "Found Ubuntu 20.04 LTS (20.04) on /dev/sda8"

after the update-grub after the reboot, the entries were all found on sdb, and work on subsequent boots.

Now I have no idea how to deal with that, but its worth knowing in case it crops up after the update.

[fehlix]

Those messages about sda,sdb etc. are not relevant as grub.cfg is using UUID's and not (unreliable) device names like sda/sdb, if not turned off intentionally within /etc/default/grub.

[dolphin_oracle]

Those messages about sda,sdb etc. are not relevant as grub.cfg is using UUID's and not (unreliable) device names like sda/sdb, if not turned off intentionally within /etc/default/grub.

I wouldn't have thought so, but I often have to redo my grub menu when the drive letters switch. which happens when I change kernels sometimes.

AFAICT, its just the windows boot loader with issues.. this probalby happened the other day to when I though installing the extra ia32 bin file would fixed things. It was probably just the extra update-grub.

[fehlix]

Those messages about sda,sdb etc. are not relevant as grub.cfg is using UUID's and not (unreliable) device names like sda/sdb, if not turned off intentionally within /etc/default/grub.

I wouldn't have thought so, but I often have to redo my grub menu when the drive letters switch. which happens when I change kernels sometimes.

check for the line in /etc/default/grub:
GRUB_DISABLE_LINUX_UUID=true
The gnerate grub.cfg does not need any device name/drive letter if GRUB_DISABLE_LINUX_UUID is not set to true.
The default is to have this line commented out:
#GRUB_DISABLE_LINUX_UUID=true

[i_ri]

grub-pc:
Installed: 2.04-9~mx19+5
Candidate: 2.04-9~mx19+5
Version table:
*** 2.04-9~mx19+5 100
100 /var/lib/dpkg/status
2.04-3mx19+3 500
500 http://la.mxrepo.com/mx/repo buster/main i386 Packages
2.02+dfsg1-20+deb10u2 500
500 http://deb.debian.org/debian buster/main i386 Packages
500 http://deb.debian.org/debian-security buster/updates/main i386 Packages
demo@mx1:~/Desktop

Hello SwampRabbit
On a mx1 live
MX-19_386 patito feo October 21 2019
4.19.0-6-686-pae i686
persist static root
from grub 2.04-3mx19+3
to grub 2.04-9~mx19+5[_i386]
It starts. (live on a machine with MX-16 installed.)

[fehlix]

grub-pc:
Installed: 2.04-9~mx19+5
Candidate: 2.04-9~mx19+5
Version table:
*** 2.04-9~mx19+5 100
100 /var/lib/dpkg/status
2.04-3mx19+3 500
500 http://la.mxrepo.com/mx/repo buster/main i386 Packages
2.02+dfsg1-20+deb10u2 500
500 http://deb.debian.org/debian buster/main i386 Packages
500 http://deb.debian.org/debian-security buster/updates/main i386 Packages
demo@mx1:~/Desktop

Hello SwampRabbit
On a mx1 live
MX-19_386 patito feo October 21 2019
4.19.0-6-686-pae i686
persist static root
from grub 2.04-3mx19+3
to grub 2.04-9~mx19+5[_i386]
It starts. (live on a machine with MX-16 installed.)

The grub installation/upgrade is not used within the a LiveUSB/ Live installed system,
The GRUB upgrade is only relevant/used within an installed (non-live) system .
The Live-System does use it's own (Live-)Grub, which cannot be updated through a grub-package upgrade.

[i_ri]

Hello SwampRabbit and fehlix and … everyone . Do you wish the live post deleted?
.+5 , using , MX 19.2_64,
starts. Normal

Code: Select all

grub-common:
  Installed: 2.04-9~mx19+5
  Candidate: 2.04-9~mx19+5
  Version table:
 *** 2.04-9~mx19+5 100
        100 /var/lib/dpkg/status
     2.04-3mx19+3 500
        500 http://mxrepo.com/mx/repo buster/main amd64 Packages
     2.02+dfsg1-20+deb10u2 500
        500 http://deb.debian.org/debian-security buster/updates/main amd64 Packages
     2.02+dfsg1-20 500
        500 http://deb.debian.org/debian buster/main amd64 Packages
grub2-common:
  Installed: 2.04-9~mx19+5
  Candidate: 2.04-9~mx19+5
  Version table:
 *** 2.04-9~mx19+5 100
        100 /var/lib/dpkg/status
     2.04-3mx19+3 500
        500 http://mxrepo.com/mx/repo buster/main amd64 Packages
     2.02+dfsg1-20+deb10u2 500
        500 http://deb.debian.org/debian-security buster/updates/main amd64 Packages
     2.02+dfsg1-20 500
        500 http://deb.debian.org/debian buster/main amd64 Packages
grub-pc:
  Installed: 2.04-9~mx19+5
  Candidate: 2.04-9~mx19+5
  Version table:
 *** 2.04-9~mx19+5 100
        100 /var/lib/dpkg/status
     2.04-3mx19+3 500
        500 http://mxrepo.com/mx/repo buster/main amd64 Packages
     2.02+dfsg1-20+deb10u2 500
        500 http://deb.debian.org/debian-security buster/updates/main amd64 Packages
     2.02+dfsg1-20 500
        500 http://deb.debian.org/debian buster/main amd64 Packages

System:    Host: WallEp6330f Kernel: 4.19.0-9-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           Desktop: Xfce 4.14.2 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-19.2_x64 patito feo October 21  2019 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop System: HP-Pavilion product: AY022AA-ABA p6330f v: N/A 
           serial: <root required> Chassis: Hewlett-Packard type: 3 serial: <root required> 
           Mobo: MSI model: IONA v: 1.0 serial: <root required> BIOS: American Megatrends 
           v: 5.15 date: 06/25/2010 
CPU:       Topology: Dual Core model: Intel Core i3 530 bits: 64 type: MT MCP arch: Nehalem 
           rev: 2 L2 cache: 4096 KiB bogomips: 23408 
           Speed: 1437 MHz min/max: 1200/2933 MHz Core speeds (MHz): 1: 1400 2: 1378 3: 1325 
           4: 1435 
           Flags: acpi aperfmperf apic arat arch_perfmon bts clflush cmov constant_tsc cpuid 
           cx16 cx8 de ds_cpl dtes64 dtherm dts ept est flexpriority flush_l1d fpu fxsr ht ibpb 
           ibrs lahf_lm lm mca mce mmx monitor msr mtrr nonstop_tsc nopl nx pae pat pbe pdcm 
           pebs pge pni popcnt pse pse36 pti rdtscp rep_good sep ss ssbd sse sse2 sse4_1 sse4_2 
           ssse3 stibp syscall tm tm2 tpr_shadow tsc vme vmx vnmi vpid xtopology xtpr 
Graphics:  Device-1: Intel Core Processor Integrated Graphics vendor: Hewlett-Packard 
           driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0042 
           Display: x11 server: X.Org 1.20.4 driver: intel resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa DRI Intel Ironlake Desktop v: 2.1 Mesa 18.3.6 
           direct render: Yes 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: Hewlett-Packard driver: r8169 v: kernel port: d800 bus ID: 01:00.0 
           chip ID: 10ec:8168 
           Device-2: Realtek RTL8188EUS 802.11n Wireless Network Adapter type: USB 
           driver: r8188eu bus ID: 1-1.3:3 chip ID: 0bda:8179 serial: 00E04C0001 
Drives:    Local Storage: total: 1.82 TiB used: 12.27 GiB (0.7%) 
           ID-1: /dev/sda vendor: Toshiba model: DT01ACA200 size: 1.82 TiB speed: 3.0 Gb/s 
           rotation: 7200 rpm serial: 335RBPGKS rev: ABB0 scheme: MBR 
Weather:   Temperature: 25.9 C (79 F) Conditions: Overcast clouds 
           Wind: from SE at 1.8 m/s (6 km/h, 4 mph) Cloud Cover: 45% Humidity: 67% 
           Dew Point: 19.3 C (67 F) Pressure: 1013.6 mb (34 in) 
           Location: Washington, D.C., DC, US, 20500 
           Current Time: Wed 05 Aug 2020 11:50:28 PM EDT 
           Observation Time: 2020-08-05 22:44:00 (America/New_York -0400) Source: WeatherBit.io 
Info:      Processes: 199 Uptime: 12m Memory: 7.66 GiB used: 574.5 MiB (7.3%) Init: SysVinit 
           v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 
           running in: xfce4-terminal inxi: 3.0.36 
Packages: 2260 (dpkg) 
hithere@WallEp6330f:~
$ hello everyone  

Machine runs vintage* MX-19.2. pre*mxfluxbox.
Already MX 19.2 Vintage, before end of life.

[SwampRabbit]

Hello SwampRabbit and fehlix and … everyone . Do you wish the live post deleted?
.+5 , using , MX 19.2_64,

No it is ok i_ri, it may help if another user comes asking the same thing.

And thank you, We do appreciate the testing!

[baldyeti]

Tested 2nd candidate on same system as before, same OK outcome

Installed successfully to sda20 on an MBR-partitioned drive. Only to pbr, though. Chainloading from main loader (grub4dos) still works fine as previously.

This time i was not offered the choice to install to mbr/pbr/both, but the upgrade correctly installed to pbr only, so no complaint.