Re: [DNG] Strange behaviour with last version of grub
On 3/9/21 9:22 AM, David Kuehling via Dng wrote: > I think we were bitten by this known Debian Bug: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925309 > > "Wrong prefix directory hardcoded in signed GRUB image" > > Signed grub assumes that the initial grub.cfg is in EFI/debian/grub.cfg > and not in wherever grub-install put it (usually EFI/devuan/grub.cfg or > EFI/BOOT/grub.cfg). > > You can verify this by entering "set" on the grub command line and > checking the default value of the "prefix" and "root" variables. > > Workaround for me is to manually enter > > configfile (hd2,gpt1)/EFI/devuan/grub.cfg > > every time I boot my machine. > > cheers, > > David I worked with fsmithred a year or so ago on this issue. I think the consensus was to make the system variable debian instead of devuan to fix this issue. I've been removing the signed image lately in order to keep my efi systems booting. Shouldn't grub be forked in order to fix this? Or perhaps remove grub-efi-amd64-signed from merged? Chris ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Strange behaviour with last version of grub
In der Nachricht vom Tuesday, 9 March 2021 18:40:22 CET schrieb Adrian Zaugg: > In der Nachricht vom Saturday, 6 March 2021 19:16:13 CET schrieb fsmithred > via > Dng: > > I could not reproduce the problem on a system that boots legacy bios and > > uses grub-pc. > > ...my machine where it happened is a Legacy-BIOS-MBR-Installation. The problem I encountered was something different, but maybe related. My machine booted into the grub menu, loaded initrd, stayed blank, changed screen resolution and still did not show any boot message. It did answer pings but sshd did not come up, keyboard strokes ignored. Inspecting the machine with a live distro I found the linux image installed is from the package linux-image-4.19.0-14-amd64, which is ...signed. I never realized before this image to be signed. I installed linux-image-4.19.0-14- amd64-unsigned and the machine came back up as usual. Since when is the standard stock kernel signed? Regards, Adrian. signature.asc Description: This is a digitally signed message part. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Strange behaviour with last version of grub
In der Nachricht vom Saturday, 6 March 2021 19:16:13 CET schrieb fsmithred via Dng: > I could not reproduce the problem on a system that boots legacy bios and > uses grub-pc. ...my machine where it happened is a Legacy-BIOS-MBR-Installation. signature.asc Description: This is a digitally signed message part. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Strange behaviour with last version of grub
> On 3/4/21 11:08 PM, wirelessduck--- via Dng wrote: >>> >>> And now the question. Has anyone reported the error in Devuan? Has >>> anyone haved this problem? >> >> Seems to be a bit of news about the latest update. >> https://9to5linux.com/patches-for-multiple-new-grub2-security-flaws-start-rolling-out-to-linux-distros-update-now >> >> The changelog mentions changes to secure boot. Could that be related >> to the issue? Same problem here. I think we were bitten by this known Debian Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925309 "Wrong prefix directory hardcoded in signed GRUB image" Signed grub assumes that the initial grub.cfg is in EFI/debian/grub.cfg and not in wherever grub-install put it (usually EFI/devuan/grub.cfg or EFI/BOOT/grub.cfg). You can verify this by entering "set" on the grub command line and checking the default value of the "prefix" and "root" variables. Workaround for me is to manually enter configfile (hd2,gpt1)/EFI/devuan/grub.cfg every time I boot my machine. cheers, David ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Strange behaviour with last version of grub
My system76 laptop got the grub updates this morning, and I installed (suspiciously) after running a meeting first. Yup, the system did not boot, giving a grub prompt. I booted with a refind USB stick, and then rolled back the grub-efi stuff to the previous version using synaptic. That worked. That laptop does *not* have the grub-efi-amd64-signed version installed, just the unsigned. FYI --Tim On Saturday, March 6, 2021, 1:27:12 PM EST, fsmithred via Dng wrote: On 3/4/21 11:08 PM, wirelessduck--- via Dng wrote: > > >> On 5 Mar 2021, at 03:23, viverna wrote: >> >> Yesterday I updated one of my computers with apt-get upgrade. This packages >> are upgraded: >> >> grub-common grub-pc grub-pc-bin grub2-common >> >> dpkg install from version 2.02+dfsg1-20+deb10u3 to version >> 2.02+dfsg1-20+deb10u4 >> >> >> And now the question. Has anyone reported the error in Devuan? Has anyone >> haved this problem? > > Seems to be a bit of news about the latest update. > https://9to5linux.com/patches-for-multiple-new-grub2-security-flaws-start-rolling-out-to-linux-distros-update-now > > The changelog mentions changes to secure boot. Could that be related to the > issue? > > https://metadata.ftp-master.debian.org/changelogs//main/g/grub2/grub2_2.02+dfsg1-20+deb10u4_changelog > > I've been able to reproduce the problem in two systems that boot uefi, (one beowulf, one chimaera) but only after I installed grub-efi-amd64-signed. It's not necessary to have secure boot enabled; you just need the signed package. I've been avoiding that package for over a year because it has caused this problem in the past. If you don't need secure boot, just use grub-efi-amd64. I could not reproduce the problem on a system that boots legacy bios and uses grub-pc. fsmithred ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Strange behaviour with last version of grub
On 3/4/21 11:08 PM, wirelessduck--- via Dng wrote: > > >> On 5 Mar 2021, at 03:23, viverna wrote: >> >> Yesterday I updated one of my computers with apt-get upgrade. This packages >> are upgraded: >> >> grub-common grub-pc grub-pc-bin grub2-common >> >> dpkg install from version 2.02+dfsg1-20+deb10u3 to version >> 2.02+dfsg1-20+deb10u4 >> >> >> And now the question. Has anyone reported the error in Devuan? Has anyone >> haved this problem? > > Seems to be a bit of news about the latest update. > https://9to5linux.com/patches-for-multiple-new-grub2-security-flaws-start-rolling-out-to-linux-distros-update-now > > The changelog mentions changes to secure boot. Could that be related to the > issue? > > https://metadata.ftp-master.debian.org/changelogs//main/g/grub2/grub2_2.02+dfsg1-20+deb10u4_changelog > > I've been able to reproduce the problem in two systems that boot uefi, (one beowulf, one chimaera) but only after I installed grub-efi-amd64-signed. It's not necessary to have secure boot enabled; you just need the signed package. I've been avoiding that package for over a year because it has caused this problem in the past. If you don't need secure boot, just use grub-efi-amd64. I could not reproduce the problem on a system that boots legacy bios and uses grub-pc. fsmithred ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Strange behaviour with last version of grub
il devuanizzato viverna il 04-03-21 17:22:42 ha scritto:
I am currently reluctant to upgrade again.
And now the question. Has anyone reported the error in Devuan? Has
anyone haved this problem?
I tried with various pc without errors, but this behavior was generated
in a pc booted in UEFI mode.
In fact the pc booted in UEFI mode and grub-pc are installed. I removed
grub-pc and I installed grub-efi.
I reapplied the procedure again and I have not received any errors.
I am surprised though precedent grub version works.
For me it's solved.
Thank you all.
--
_
< Viverna >
-
\^/^
\ / \ // \
\ |\___/| / \// .\
\ /0 0 \__ /// | \ \ **
/ / \/_/// | \ \ \ |
@_^_@`/ \/_ //| \ \ \/\ \
//_^_/ \/_ // |\\ \ \
( //) |\/// | \ \ | |
( / /) | // | \ _\ | /
( // /) | ; -.|_ _\.-~ / /
(( / / )) |_ *-.|.-~-. .~~
(( // / ))\ / ~-. _ .-~ /
(( /// )) `. }{ /
(( / )) .~-.\\-` .~
///...<\ _ -~
///-._ _ _ _ _ _ _{^ - - - - ~
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Strange behaviour with last version of grub
On Fri, 5 Mar 2021 11:36:52 +0100 Adrian Zaugg wrote: > Does anyone see this problem on Debian too (non-bootable after GRUB update)? Well, it happened to me few days ago, tough the usual tricks did the job (setting root at grub prompt, booting the /vmlinux and issuing update-grub and grub-install). I did the upgrade from jessie to ascii and then to beowulf. Luciano. -- /"\ /Via A. Salaino, 7 - 20144 Milano (Italy) \ / ASCII RIBBON CAMPAIGN / PHONE : +39 02485781 FAX: +39 0248028247 X AGAINST HTML MAIL/ E-MAIL: posthams...@sublink.sublink.org / \ AND POSTINGS/ WWW: http://www.lesassaie.IT/ ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Strange behaviour with last version of grub
‐‐‐ Original Message ‐‐‐ On Friday, March 5, 2021 10:36 AM, Adrian Zaugg wrote: > On 05.03.21 05:08, wirelessduck--- via Dng wrote: > > > The changelog mentions changes to secure boot. Could that be related to > > the issue? > > No, not in my case, secure boot is not in use on the concerned system. > > Does anyone see this problem on Debian too (non-bootable after GRUB update)? > > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ~# dpkg -l grub-pc Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--== ii grub-pc2.02+dfsg1-20+deb10u4 amd64 No issues. NOTE: 1) MSDOS partition not GPT 2) EFI is disabled on this system publickey - g4sra@protonmail.com - 0x42E94623.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Strange behaviour with last version of grub
On 05.03.21 05:08, wirelessduck--- via Dng wrote: > The changelog mentions changes to secure boot. Could that be related to > the issue? No, not in my case, secure boot is not in use on the concerned system. Does anyone see this problem on Debian too (non-bootable after GRUB update)? ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Strange behaviour with last version of grub
> On 5 Mar 2021, at 15:08, wirelessd...@gmail.com wrote: > > > > >>> On 5 Mar 2021, at 03:23, viverna wrote: >>> >> Yesterday I updated one of my computers with apt-get upgrade. This packages >> are upgraded: >> >> grub-common grub-pc grub-pc-bin grub2-common >> >> dpkg install from version 2.02+dfsg1-20+deb10u3 to version >> 2.02+dfsg1-20+deb10u4 >> >> 2.02+dfsg1-20+deb10u4 seems came from to: >> http://deb.devuan.org/merged beowulf-security/main >> >> 2.02+dfsg1-20+deb10u3 is in: >> http://deb.devuan.org/merged beowulf/main >> >> Upgrading system does not produce or show any problems and then I halt the >> system. >> >> I use Devuan Beowulf for all my pc. In this computer there is only 1 hd, >> partition type gpt, 3 partitions: >> >> /dev/sda1 EFI System >> /dev/sda2 Linux filesystem >> /dev/sda3 Linux swap >> >> I switched on the pc later and grub rescue appears. WTF? >> >> I solved (temporarily) the problems with: >> >> set prefix=(hd0,gpt2)/boot/grub >> set root=(hd0,gpt2) >> insmod normal >> normal >> >> and grub menù appears. >> >> Login with root, and then update-grub... grub-install... and so on... >> >> Restart the system. Grub rescue. Then login with root. New tests. Grub >> rescue again. [N times?] >> >> At the end I downgrade from 2.02+dfsg1-20+deb10u4 to 2.02+dfsg1-20+deb10u3 >> the upgraded package. >> >> update-grub and grub-install. Reboot. Grub works! >> >> I am currently reluctant to upgrade again. >> >> And now the question. Has anyone reported the error in Devuan? Has anyone >> haved this problem? > > Seems to be a bit of news about the latest update. > https://9to5linux.com/patches-for-multiple-new-grub2-security-flaws-start-rolling-out-to-linux-distros-update-now > > The changelog mentions changes to secure boot. Could that be related to the > issue? > > https://metadata.ftp-master.debian.org/changelogs//main/g/grub2/grub2_2.02+dfsg1-20+deb10u4_changelog And there is also a debian security advisory related to this update. https://www.debian.org/security/2021/dsa-4867___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Strange behaviour with last version of grub
> On 5 Mar 2021, at 03:23, viverna wrote: > > Yesterday I updated one of my computers with apt-get upgrade. This packages > are upgraded: > > grub-common grub-pc grub-pc-bin grub2-common > > dpkg install from version 2.02+dfsg1-20+deb10u3 to version > 2.02+dfsg1-20+deb10u4 > > 2.02+dfsg1-20+deb10u4 seems came from to: > http://deb.devuan.org/merged beowulf-security/main > > 2.02+dfsg1-20+deb10u3 is in: > http://deb.devuan.org/merged beowulf/main > > Upgrading system does not produce or show any problems and then I halt the > system. > > I use Devuan Beowulf for all my pc. In this computer there is only 1 hd, > partition type gpt, 3 partitions: > > /dev/sda1 EFI System > /dev/sda2 Linux filesystem > /dev/sda3 Linux swap > > I switched on the pc later and grub rescue appears. WTF? > > I solved (temporarily) the problems with: > > set prefix=(hd0,gpt2)/boot/grub > set root=(hd0,gpt2) > insmod normal > normal > > and grub menù appears. > > Login with root, and then update-grub... grub-install... and so on... > > Restart the system. Grub rescue. Then login with root. New tests. Grub rescue > again. [N times?] > > At the end I downgrade from 2.02+dfsg1-20+deb10u4 to 2.02+dfsg1-20+deb10u3 > the upgraded package. > > update-grub and grub-install. Reboot. Grub works! > > I am currently reluctant to upgrade again. > > And now the question. Has anyone reported the error in Devuan? Has anyone > haved this problem? Seems to be a bit of news about the latest update. https://9to5linux.com/patches-for-multiple-new-grub2-security-flaws-start-rolling-out-to-linux-distros-update-now The changelog mentions changes to secure boot. Could that be related to the issue? https://metadata.ftp-master.debian.org/changelogs//main/g/grub2/grub2_2.02+dfsg1-20+deb10u4_changelog___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Strange behaviour with last version of grub
Hi Viverna In der Nachricht vom Thursday, 4 March 2021 17:22:42 CET schrieb viverna: > And now the question. Has anyone reported the error in Devuan? Has > anyone haved this problem? Yes, it happened on one of my machines too. I did not yet check what really happened and did not try to solve it yet. It started with an unattended- upgrade: ... Setting up grub-pc (2.02+dfsg1-20+deb10u4) ... /dev/disk/by-id/ata-TS64GMTS400S_F673990758 does not exist, so cannot grub- install to it! I did rerun apt upgrade manually and did not see an error, it asked to install in /dev/sda, of course it's the only disk in the system, I wondered why it asked and rebooted after successful installation, but the machine did not come back up. Regards, Adrian. signature.asc Description: This is a digitally signed message part. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Strange behaviour with last version of grub
‐‐‐ Original Message ‐‐‐ On Thursday, March 4, 2021 8:10 PM, tito via Dng wrote: > On Thu, 4 Mar 2021 17:22:42 +0100 > viverna vive...@inventati.org wrote: > > > Yesterday I updated one of my computers with apt-get upgrade. This > > packages are upgraded: > > grub-common grub-pc grub-pc-bin grub2-common > > dpkg install from version 2.02+dfsg1-20+deb10u3 to version > > 2.02+dfsg1-20+deb10u4 > > 2.02+dfsg1-20+deb10u4 seems came from to: > > http://deb.devuan.org/merged beowulf-security/main > > 2.02+dfsg1-20+deb10u3 is in: > > http://deb.devuan.org/merged beowulf/main > > Upgrading system does not produce or show any problems and then I > > halt the system. > > I use Devuan Beowulf for all my pc. In this computer there is only 1 > > hd, partition type gpt, 3 partitions: > > /dev/sda1 EFI System > > /dev/sda2 Linux filesystem > > /dev/sda3 Linux swap > > I switched on the pc later and grub rescue appears. WTF? > > I solved (temporarily) the problems with: > > set prefix=(hd0,gpt2)/boot/grub > > set root=(hd0,gpt2) > > insmod normal > > normal > > and grub menù appears. > > Login with root, and then update-grub... grub-install... and so on... > > Restart the system. Grub rescue. Then login with root. New tests. > > Grub rescue again. [N times?] > > At the end I downgrade from 2.02+dfsg1-20+deb10u4 to > > 2.02+dfsg1-20+deb10u3 the upgraded package. > > update-grub and grub-install. Reboot. Grub works! > > I am currently reluctant to upgrade again. > > And now the question. Has anyone reported the error in Devuan? Has > > anyone haved this problem? > > Hi, > I updated all my boxes and rebooted them without problems (still have > to reboot the routers, now that you tell I will do it when I'm there > physically). > > Ciao, > Tito > > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng I bet this is an EFI issue, start by looking there. publickey - g4sra@protonmail.com - 0x42E94623.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Strange behaviour with last version of grub
On Thu, 4 Mar 2021 17:22:42 +0100 viverna wrote: > Yesterday I updated one of my computers with apt-get upgrade. This > packages are upgraded: > > grub-common grub-pc grub-pc-bin grub2-common > > dpkg install from version 2.02+dfsg1-20+deb10u3 to version > 2.02+dfsg1-20+deb10u4 > > 2.02+dfsg1-20+deb10u4 seems came from to: > http://deb.devuan.org/merged beowulf-security/main > > 2.02+dfsg1-20+deb10u3 is in: > http://deb.devuan.org/merged beowulf/main > > Upgrading system does not produce or show any problems and then I > halt the system. > > I use Devuan Beowulf for all my pc. In this computer there is only 1 > hd, partition type gpt, 3 partitions: > > /dev/sda1 EFI System > /dev/sda2 Linux filesystem > /dev/sda3 Linux swap > > I switched on the pc later and grub rescue appears. WTF? > > I solved (temporarily) the problems with: > > set prefix=(hd0,gpt2)/boot/grub > set root=(hd0,gpt2) > insmod normal > normal > > and grub menù appears. > > Login with root, and then update-grub... grub-install... and so on... > > Restart the system. Grub rescue. Then login with root. New tests. > Grub rescue again. [N times?] > > At the end I downgrade from 2.02+dfsg1-20+deb10u4 to > 2.02+dfsg1-20+deb10u3 the upgraded package. > > update-grub and grub-install. Reboot. Grub works! > > I am currently reluctant to upgrade again. > > And now the question. Has anyone reported the error in Devuan? Has > anyone haved this problem? > Hi, I updated all my boxes and rebooted them without problems (still have to reboot the routers, now that you tell I will do it when I'm there physically). Ciao, Tito ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Strange behaviour with last version of grub
Yesterday I updated one of my computers with apt-get upgrade. This
packages are upgraded:
grub-common grub-pc grub-pc-bin grub2-common
dpkg install from version 2.02+dfsg1-20+deb10u3 to version
2.02+dfsg1-20+deb10u4
2.02+dfsg1-20+deb10u4 seems came from to:
http://deb.devuan.org/merged beowulf-security/main
2.02+dfsg1-20+deb10u3 is in:
http://deb.devuan.org/merged beowulf/main
Upgrading system does not produce or show any problems and then I halt
the system.
I use Devuan Beowulf for all my pc. In this computer there is only 1 hd,
partition type gpt, 3 partitions:
/dev/sda1 EFI System
/dev/sda2 Linux filesystem
/dev/sda3 Linux swap
I switched on the pc later and grub rescue appears. WTF?
I solved (temporarily) the problems with:
set prefix=(hd0,gpt2)/boot/grub
set root=(hd0,gpt2)
insmod normal
normal
and grub menù appears.
Login with root, and then update-grub... grub-install... and so on...
Restart the system. Grub rescue. Then login with root. New tests. Grub
rescue again. [N times?]
At the end I downgrade from 2.02+dfsg1-20+deb10u4 to
2.02+dfsg1-20+deb10u3 the upgraded package.
update-grub and grub-install. Reboot. Grub works!
I am currently reluctant to upgrade again.
And now the question. Has anyone reported the error in Devuan? Has
anyone haved this problem?
--
_
< Viverna >
-
\^/^
\ / \ // \
\ |\___/| / \// .\
\ /0 0 \__ /// | \ \ **
/ / \/_/// | \ \ \ |
@_^_@`/ \/_ //| \ \ \/\ \
//_^_/ \/_ // |\\ \ \
( //) |\/// | \ \ | |
( / /) | // | \ _\ | /
( // /) | ; -.|_ _\.-~ / /
(( / / )) |_ *-.|.-~-. .~~
(( // / ))\ / ~-. _ .-~ /
(( /// )) `. }{ /
(( / )) .~-.\\-` .~
///...<\ _ -~
///-._ _ _ _ _ _ _{^ - - - - ~
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
