two
> different nvmes)
> /dev/nvme0n1p3 = /dev/nvme1n1p3 = 7mb 8300 (Linux RAID)
lsblk gives a nice readable version of this info.
> I am currently using /dev/nvme*1*n1p2 as /boot/efi and groub-efi is
> installed there.
>
> I like to also install grub-efi on /dev/nvme*0*n1p1 t
/nvme1n1p3 = 7mb 8300 (Linux RAID)
I am currently using /dev/nvme*1*n1p2 as /boot/efi and groub-efi is
installed there.
I like to also install grub-efi on /dev/nvme*0*n1p1 to mimic RAID1. My
Google search does not give me a clear way to do it. There are a lot
explanation on how certain things
302/OvmfPkg/OvmfPkgX64.fdf -smp 2 -m 2G /dev/sda
>This will just give me a QEMU error message ("could not load PC BIOS"). Is it
>possible to boot an EFI system with QEMU without downloading a custom firmware
>file, i.e. is there a Debian package providing this functionality?
Valentin Caracalla (12023-04-25):
> thanks a lot for the tip! However, I'm a complete novice when it comes to
> running custom firmware in QEMU. I just tried the following:
>
> 1.: Download the latest EDK2 release from Github:
I could boot a VM with a UEFI bootloader using only files packaged
Hello Steve,
thanks a lot for the tip! However, I'm a complete novice when it comes to
running custom firmware in QEMU. I just tried the following:
1.: Download the latest EDK2 release from Github:
https://github.com/tianocore/edk2/archive/refs/tags/edk2-stable202302.tar.gz
2.: Extract the
mick.crane wrote:
...
> on reboot after installation of bookworm PC says no OS found.
you'd have to check the installer logs in /var/log/installer
(for that install) to see where it failed.
> Changed Dell f2/f12 menu to boot legacy CDrom and bookworm installation
> succeeds, has
On 24/04/2023 01:38, Charles Curley wrote:
On Sun, 23 Apr 2023 16:34:03 - (UTC)
Curt wrote:
Install grml-rescueboot
I just tried it. It may work with a grml CD ISO; I didn't try it. The
code builds the grub.cfg entry correctly, and that works. But grub
refused to boot the debian netinst
On 2023-04-23, Charles Curley wrote:
> On Sun, 23 Apr 2023 16:34:03 - (UTC)
> Curt wrote:
>
>> Install grml-rescueboot
>
> I just tried it. It may work with a grml CD ISO; I didn't try it. The
> code builds the grub.cfg entry correctly, and that works. But grub
> refused to boot the debian
On 2023-04-24 10:23, David Christensen wrote:
On 4/22/23 22:07, mick.crane wrote:
Dell Precision T3600
I assume this is the computer for the subject thread.
I couldn't make head nor tail of the Dell f2/f12 boot options.
installed bullseye and all was stable at 800x600 but with no options to
Name ESP
Use as EFI System Partition
Bootable flag on
-> Done setting up the partition
-> 59.0 GB FREE SPACE
-> Create a new partition
New partition
On 2023-04-23 20:56, mick.crane wrote:
Please be considerate of us oldies who struggle with the technology.
I successfully booted from the CD and reinstalled Debian.
The purpose for doing this was that I was having pixel glitches on the
monitor and some freezes.
Thinking anything I've done that
On 2023-04-23 20:21, David Christensen wrote:
On 4/23/23 12:56, mick.crane wrote:
Please be considerate of us oldies who struggle with the technology.
I successfully booted from the CD and reinstalled Debian.
The purpose for doing this was that I was having pixel glitches on the
monitor and
mick.crane composed on 2023-04-23 20:56 (UTC+0100):
> I wondered if there is some way to examine graphics card memory and mark
> as bad or something.
Marking sections of VRAM bad isn't something I've ever heard of doing. If you
have
a discrete graphics card rather than one included in
On 4/23/23 12:56, mick.crane wrote:
Please be considerate of us oldies who struggle with the technology.
I successfully booted from the CD and reinstalled Debian.
The purpose for doing this was that I was having pixel glitches on the
monitor and some freezes.
Thinking anything I've done that
On Sun, 23 Apr 2023 15:15:22 -0400
songbird wrote:
> that's my thoughts at this point. hope you will make better
> progress on this soon. :)
No worries. I have USB sticks, CD-RWs, etc. I just did the experiment
to see how well it worked. Thanks for the thoughts, though.
--
Does anybody
Please be considerate of us oldies who struggle with the technology.
I successfully booted from the CD and reinstalled Debian.
The purpose for doing this was that I was having pixel glitches on the
monitor and some freezes.
Thinking anything I've done that might be causing that will be
Charles Curley wrote:
> On Sun, 23 Apr 2023 16:34:03 - (UTC)
> Curt wrote:
>
>> Install grml-rescueboot
>
> I just tried it. It may work with a grml CD ISO; I didn't try it. The
> code builds the grub.cfg entry correctly, and that works. But grub
> refused to boot the debian netinst image I
On Sun, 23 Apr 2023 16:34:03 - (UTC)
Curt wrote:
> Install grml-rescueboot
I just tried it. It may work with a grml CD ISO; I didn't try it. The
code builds the grub.cfg entry correctly, and that works. But grub
refused to boot the debian netinst image I provided.
--
Does anybody read
On 2023-04-22, mick.crane wrote:
>> DdB
> This sounds encouraging.
> Any idea what the correct manifestation would be to get the PC to boot
> the debian installer CD?
> What as wrong with boot from CD, disk 1, disk 2, some convoluted network
> connection?
>
>
Install grml-rescueboot
sudo
>>> think.
>>> Just to see if it's maybe a driver issue.
>>> Thing is I can't get the f12 options screen of the PC to let me boot
>>> from a CD in this EFI mode what's grub done.
>>> How can I boot from CD in this EFI mode?
>>
>> what
On 23/04/2023 12:07, mick.crane wrote:
root@pumpkin:/home/mick# efibootmgr
BootCurrent: 0007
Timeout: 1 seconds
BootOrder: 0008,,000A,0003,0004,0007,0001,0002
-
Boot0007* debian
Boot0008* CD/DVD/CD-RW Drive
...
Is there some way I can say "boot Boot0008 please"?
get the f12 options screen of the PC to let me boot
from a CD in this EFI mode what's grub done.
How can I boot from CD in this EFI mode?
what does efibootmgr say when you run it from the
root prompt?
mine lists the CD drive and if i change the boot
order to put that first it will boot from
as I've got copies of everything
> > > I think.
> > > Just to see if it's maybe a driver issue.
> > > Thing is I can't get the f12 options screen of the PC to let me boot
> > > from a CD in this EFI mode what's grub done.
> > > How can I boot from CD in thi
options screen of the PC to let me boot
> from a CD in this EFI mode what's grub done.
> How can I boot from CD in this EFI mode?
what does efibootmgr say when you run it from the
root prompt?
mine lists the CD drive and if i change the boot
order to put that first it will boot fro
mick.crane composed on 2023-04-22 18:30 (UTC+0100):
> Thing is I can't get the f12 options screen of the PC to let me boot
> from a CD in this EFI mode what's grub done.
> How can I boot from CD in this EFI mode?
Are you sure it's supposed to be F12 on yours?
BBS Boot Keys (
OS as I've got copies of everything I think.
> > Just to see if it's maybe a driver issue.
> > Thing is I can't get the f12 options screen of the PC to let me boot
> > from a CD in this EFI mode what's grub done.
> > How can I boot from CD in this EFI mode?
>
> You try ot
Am 22.04.2023 um 21:01 schrieb mick.crane:
> Any idea what the correct manifestation would be to get the PC to boot
> the debian installer CD?
Without checking your CPU and general hardware, it would be dangerous to
speculate as of what you need. But to give at least one hint to you,
i'll copy
to see if it's maybe a driver issue.
Thing is I can't get the f12 options screen of the PC to let me boot
from a CD in this EFI mode what's grub done.
How can I boot from CD in this EFI mode?
mick
My neighbor has an old laptop without a CD drive. But there is a linux
running (ubuntu). So what i
.
Thing is I can't get the f12 options screen of the PC to let me boot
from a CD in this EFI mode what's grub done.
How can I boot from CD in this EFI mode?
mick
My neighbor has an old laptop without a CD drive. But there is a linux
running (ubuntu). So what i did is this:
i did download
.
Thing is I can't get the f12 options screen of the PC to let me boot
from a CD in this EFI mode what's grub done.
How can I boot from CD in this EFI mode?
mick
My neighbor has an old laptop without a CD drive. But there is a linux
running (ubuntu). So what i did is this:
i did download
> Thing is I can't get the f12 options screen of the PC to let me boot
> from a CD in this EFI mode what's grub done.
> How can I boot from CD in this EFI mode?
You try other keys besides F12. You tap them repeatedly after
turning on. You try them in combination with Escape. There
screen of the PC to let me boot
from a CD in this EFI mode what's grub done.
How can I boot from CD in this EFI mode?
mick
Without knowing the make and model of the computer, it is difficult to
offer specific advice.
When you power up the computer, there should be a hot key to enter
is I can't get the f12 options screen of the PC to let me boot
> from a CD in this EFI mode what's grub done.
> How can I boot from CD in this EFI mode?
>
> mick
>
>
My neighbor has an old laptop without a CD drive. But there is a linux
running (ubuntu). So what i did is this:
a CD in this EFI mode what's grub done.
How can I boot from CD in this EFI mode?
mick
Hey!
As kind of a network-wide fallback system (and for some diskless computers in
our network) I'd like to set up EFI PXE boot for a simple Debian system.
However, I have only been able to find very sparse and possibly outdated
information on how to actually tell the kernel/initramfs to mount
Windows-10-Jorge.xml
Description: XML document
Hi! After I upgraded to bookworm, my QEMU-KVM VM fails to boot the
guest OS; instead it drops to the EFI shell. If I boot the physical
host into bullseye's kernel (Linux 5.10) then the VM boots normally.
This VM has two virtual disks, each backed
Am 11.10.2022 11:38, schrieb Alain D D Williams:
How do I integrate the HP diagnostics into the current EFI ?
It should be fine to copy the files to the EFI partition (if not already
there) and add some boot entry via efibootmgr (if not already present).
Running efibootmgr (as root) without
these as they know more about the laptop's hardware than what is installed
from Mint -- just some generic memory test.
I did copy the EFI before it was overwritten by the Linux installation.
How do I integrate the HP diagnostics into the current EFI ?
Thanks in advance.
This is what there is now:
/boot/efi
On 9/7/2022 1:46 PM, Sven Hoexter wrote:
On Tue, Sep 06, 2022 at 07:21:59PM +0200, john doe wrote:
Debians,
I'm trying to pxe boot a client with UEFI BIOS to no avail.
Everything works with legacy BIOS but if I use those two lines in my
dnsmasq.conf:
"dhcp-boot=bootnetx64.efi
pxe-servic
On Tue, Sep 06, 2022 at 07:21:59PM +0200, john doe wrote:
> Debians,
>
> I'm trying to pxe boot a client with UEFI BIOS to no avail.
>
> Everything works with legacy BIOS but if I use those two lines in my
> dnsmasq.conf:
>
> "dhcp-boot=bootnetx64.efi
> pxe-servi
Debians,
I'm trying to pxe boot a client with UEFI BIOS to no avail.
Everything works with legacy BIOS but if I use those two lines in my
dnsmasq.conf:
"dhcp-boot=bootnetx64.efi
pxe-service=X86-64_EFI, "Boot UEFI PXE-64", bootnetx64.efi"
the client gets an IP but no
22 11:08:56 +0200 (CEST)
Objet: Pb démarrage Debian en dual boot EFI
Bonjour,
j'ai installé Debian (Bullseye) en dual boot EFI sur un PC W10.
Aucun problème, sauf que je n'arrive pas à avoir le menu Grub au
démarrage. Systématiquement le PC boote sur Windows.
J'ai essayé de modifier l'ordre de
, la présence d'une entré nommé Microsoft dans
le magasin EFI empêche l'utilisation d'un autre chargeur que celui de
Windows. Dans ce cas, j'ai dû commencer par booter Linux à la main
(menu de démarrage UEFI) puis sous Linux, sauvegarder le paragraphe de
/boot/grub/grub.cfg concernant Windows, renommer
simplement avec le BIOS.
Elilo n'est plus maintenu non plus mais avait été créé pour être
compatible avec l'UEFI (le E de Elilo pour EFI, je suppose).
Si je me souviens bien, Slackware doit proposer Grub, mais par défaut
installe Lilo pour du BIOS et Elilo pour de l'UEFI.
Ceci dit, dans le problème
elui par défaut.
> Sur certains UEFI buggés, la présence d'une entré nommé Microsoft dans
> le magasin EFI empêche l'utilisation d'un autre chargeur que celui de
> Windows. Dans ce cas, j'ai dû commencer par booter Linux à la main
> (menu de démarrage UEFI) puis sous Linux, sauvegarder le
Bonjour,
Mofifier le "BootOrder" avec l'option "-o" de efibootmgr peut-être.
Bonne journée
Le 2022-04-03 à 05 h 08, Thierry a écrit :
Bonjour,
j'ai installé Debian (Bullseye) en dual boot EFI sur un PC W10.
Aucun problème, sauf que je n'arrive pas à avoir le men
Microsoft dans
le magasin EFI empêche l'utilisation d'un autre chargeur que celui de
Windows. Dans ce cas, j'ai dû commencer par booter Linux à la main
(menu de démarrage UEFI) puis sous Linux, sauvegarder le paragraphe de
/boot/grub/grub.cfg concernant Windows, renommer
/boot/efi/EFI/Microsoft en
Le 03/04/2022 à 11:08, Thierry a écrit :
Bonjour,
j'ai installé Debian (Bullseye) en dual boot EFI sur un PC W10.
Aucun problème, sauf que je n'arrive pas à avoir le menu Grub au
démarrage. Systématiquement le PC boote sur Windows.
Je me doute que ce n'est pas un problème Debian, mais
Alors peut-être le réinstaller:
os-prober
update-grub
grub-install /dev/sda (mettre le bon disk ici…)
Le 03-04-2022, à 12:02:58 +0200, Thierry a écrit :
Merci, mais çà ne fait que modifier le menu Grub.
Encore faut-il qu'il s'affiche au boot. C'est là mon problème.
Merci, mais çà ne fait que modifier le menu Grub.
Encore faut-il qu'il s'affiche au boot. C'est là mon problème.
Le 03/04/2022 à 11:37, steve a écrit :
Salut,
As-tu lancé en root :
update-grub
Normalement ça devrait suffire.
Bon dimanche
Salut,
As-tu lancé en root :
update-grub
Normalement ça devrait suffire.
Bon dimanche
Bonjour,
j'ai installé Debian (Bullseye) en dual boot EFI sur un PC W10.
Aucun problème, sauf que je n'arrive pas à avoir le menu Grub au
démarrage. Systématiquement le PC boote sur Windows.
J'ai essayé de modifier l'ordre de démarrage sous Windows avec bcdedit
ou sous Debian avec
On Sun, Sep 05, 2021 at 09:21:38PM +0300, Gunnar Gervin wrote:
> Hi all.
> Where do I find a live Debian x86-64 iso image with EFI 'cd image' in it ?
> (My 2007 ex-Mac computer now only runs Puppy x86-64 live dvd in RAM.)
> My Macbook 64b computer won't open any iso without a cd ima
On 2021-09-05 at 14:21, Gunnar Gervin wrote:
> Hi all. Where do I find a live Debian x86-64 iso image with EFI 'cd
> image' in it ?
As far as I understand, all of the Debian install ISOs will support both
EFI and non-EFI-style boot.
(At my workplace, we have Linux-based utility CDs wh
Hi all.
Where do I find a live Debian x86-64 iso image with EFI 'cd image' in it ?
(My 2007 ex-Mac computer now only runs Puppy x86-64 live dvd in RAM.)
My Macbook 64b computer won't open any iso without a cd image named EFI.
Alt key on boot up will show distro's ISO image, on the right side I
On 2021-08-16 6:44 a.m., Andrew M.A. Cater wrote:
> On Mon, Aug 16, 2021 at 06:19:47AM -0400, Polyna-Maude Racicot-Summerside
> wrote:
>> Hi,
>>
>> On 2021-08-16 2:30 a.m., to...@tuxteam.de wrote:
>>> On Sun, Aug 15, 2021 at 05:21:41PM -0400, Polyna-Maude Racicot-Summerside
>>> wrote:
> And one of the best way of learning is by trial and error
Dear Polly, but, you are so beautiful : not only Beautiful, but,
French-Canadienne-Beautiful
thank you : bless you
.
And one of the best way of learning is by trial and error
Dear Polly, but, you are so beautiful
.
regards
.
On Sun 15 Aug 2021 at 20:31:36 +, Andrew M.A. Cater wrote:
> On Sun, Aug 15, 2021 at 10:13:07PM +0300, Gunnar Gervin wrote:
[...]
> > Debian and Devuan obviously don't mix with Mint. And vice versa. Why not,
> > really? You can learn around Efi & Grub from each oth
On Mon, Aug 16, 2021 at 06:19:47AM -0400, Polyna-Maude Racicot-Summerside wrote:
> Hi,
>
> On 2021-08-16 2:30 a.m., to...@tuxteam.de wrote:
> > On Sun, Aug 15, 2021 at 05:21:41PM -0400, Polyna-Maude Racicot-Summerside
> > wrote:
> >>
> >>
> >> On 2021-08-15 4:31 p.m., Andrew M.A. Cater wrote:
>
Hi,
On 2021-08-16 2:30 a.m., to...@tuxteam.de wrote:
> On Sun, Aug 15, 2021 at 05:21:41PM -0400, Polyna-Maude Racicot-Summerside
> wrote:
>>
>>
>> On 2021-08-15 4:31 p.m., Andrew M.A. Cater wrote:
>
> [...]
>
>>> Keep notes as you go. Try and raise single issues - it'll help.
>>>
>>> All the
On Sun, Aug 15, 2021 at 05:21:41PM -0400, Polyna-Maude Racicot-Summerside wrote:
>
>
> On 2021-08-15 4:31 p.m., Andrew M.A. Cater wrote:
[...]
> > Keep notes as you go. Try and raise single issues - it'll help.
> >
> > All the very best, as ever,
> I'd like to have as much patience you do ;-)
On 2021-08-15 3:34 p.m., Brian wrote:
> On Sun 15 Aug 2021 at 22:13:07 +0300, Gunnar Gervin wrote:
>
>> Hi.
>> After I put EFI in sda1 Refracta installer was not satisfied and told me to
>> put 'boot installer' in, and write some (unspecified) text in fst
Hi,
On 2021-08-15 3:13 p.m., Gunnar Gervin wrote:
> Hi.
> After I put EFI in sda1 Refracta installer was not satisfied and told me
> to put 'boot installer' in, and write some (unspecified) text in fstab,
> but wasn't in ETC.
>
> How and what to write in fstab?
>
>
On 2021-08-15 4:31 p.m., Andrew M.A. Cater wrote:
> On Sun, Aug 15, 2021 at 10:13:07PM +0300, Gunnar Gervin wrote:
>> Hi.
>> After I put EFI in sda1 Refracta installer was not satisfied and told me to
>> put 'boot installer' in, and write some (unspecified) text in fstab,
Hi,
On 2021-08-15 3:13 p.m., Gunnar Gervin wrote:
> Hi.
> After I put EFI in sda1 Refracta installer was not satisfied and told me
> to put 'boot installer' in, and write some (unspecified) text in fstab,
> but wasn't in ETC.
>
> How and what to write in fstab?
>
https://ww
Hi,
On 2021-08-15 3:13 p.m., Gunnar Gervin wrote:
> Hi.
> After I put EFI in sda1 Refracta installer was not satisfied and told me
> to put 'boot installer' in, and write some (unspecified) text in fstab,
> but wasn't in ETC.
>
> How and what to write in fstab?
>
>
On Sun, Aug 15, 2021 at 10:13:07PM +0300, Gunnar Gervin wrote:
> Hi.
> After I put EFI in sda1 Refracta installer was not satisfied and told me to
> put 'boot installer' in, and write some (unspecified) text in fstab, but
> wasn't in ETC.
>
> How and what to write in fstab
On Sun 15 Aug 2021 at 22:13:07 +0300, Gunnar Gervin wrote:
> Hi.
> After I put EFI in sda1 Refracta installer was not satisfied and told me to
> put 'boot installer' in, and write some (unspecified) text in fstab, but
> wasn't in ETC.
[...]
This isn't a concern of Debian.
Hi.
After I put EFI in sda1 Refracta installer was not satisfied and told me to
put 'boot installer' in, and write some (unspecified) text in fstab, but
wasn't in ETC.
How and what to write in fstab?
You tell me to specify question.
How to specify a total mess?
I'm trying to put a (Debian fork
On Thu 24 Jun 2021 at 17:06:50 (+0200), Markus wrote:
> I wanted to reinstall grub-efi-amd64 and got this:
>
> markus@bmtMB1:/var/log/apt$ sudo apt install grub-efi-amd64
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
>
5 +0100
>> Explanation: #984520: 'error: symbol "grub_register_command_lockdown"
>> not found' and then lightdm fails to start
>> Package: grub-efi-amd64
>> Pin: version 2.02+dfsg1-20+deb10u3
>> Pin-Priority: 3
>>
>> Explanation: Pinned by apt
Markus writes:
> Hi guys, it is nice that from all of this a little discussion took of.
> But what can I actually do to fix my problem here? Any suggestions?
What was the problem again? Just the suggestion to run apt autoremove
which probably isn't a good idea now?
Easiest is probably waiting
Am 07.07.21 um 12:27 schrieb Markus:
Am 07.07.21 um 09:24 schrieb Andrei POPESCU:
On Mi, 07 iul 21, 08:21:17, Markus wrote:
Am 24.06.21 um 18:51 schrieb Greg Wooledge:
On Thu, Jun 24, 2021 at 06:43:15PM +0200, Markus wrote:
grub-efi-amd64:
Installed: (none)
Candidate: 2.02+dfsg1-20
The Wanderer writes:
> #990082 is for shim-signed, and it does seem to be closed now, but if
> I'm reading the discussion correctly that's not the package we're
> concerned with.
True, especially as #990082 is specific to ARM.
> $984520 is for grub-efi-amd64, which I think is the p
ot the package we're
concerned with.
$984520 is for grub-efi-amd64, which I think is the package we're
concerned with, and as far as I can tell it's still open.
> it seems to me apt-listbugs should clean this up by itself, it's
> supposed to run periodically. I guess you could run i
Markus writes:
> So it seems that apt-listbugs has done the pinning. Right?
Right and while I've never used apt-listbugs, it should've asked you
what to do when you updated your system? Since the issue concerns ARM
based systems only, binning was not the correct choice.
As the bug is fixed now
On Wed, Jul 07, 2021 at 08:21:17AM +0200, Markus wrote:
> Am 24.06.21 um 18:51 schrieb Greg Wooledge:
> > On Thu, Jun 24, 2021 at 06:43:15PM +0200, Markus wrote:
> > > grub-efi-amd64:
> > >Installed: (none)
> > >Candidate: 2.02+dfsg1-20+deb10u3
>
Am 07.07.21 um 09:24 schrieb Andrei POPESCU:
On Mi, 07 iul 21, 08:21:17, Markus wrote:
Am 24.06.21 um 18:51 schrieb Greg Wooledge:
On Thu, Jun 24, 2021 at 06:43:15PM +0200, Markus wrote:
grub-efi-amd64:
Installed: (none)
Candidate: 2.02+dfsg1-20+deb10u3
Version table:
2.02
On Mi, 07 iul 21, 08:21:17, Markus wrote:
> Am 24.06.21 um 18:51 schrieb Greg Wooledge:
> > On Thu, Jun 24, 2021 at 06:43:15PM +0200, Markus wrote:
> > > grub-efi-amd64:
> > >Installed: (none)
> > >Candidate: 2.02+dfsg1-20+deb10u3
> > >Ver
Am 24.06.21 um 18:51 schrieb Greg Wooledge:
On Thu, Jun 24, 2021 at 06:43:15PM +0200, Markus wrote:
grub-efi-amd64:
Installed: (none)
Candidate: 2.02+dfsg1-20+deb10u3
Version table:
2.02+dfsg1-20+deb10u4 500
500 http://ftp.de.debian.org/debian buster/main amd64 Packages
On Thu, Jun 24, 2021 at 06:43:15PM +0200, Markus wrote:
> grub-efi-amd64:
> Installed: (none)
> Candidate: 2.02+dfsg1-20+deb10u3
> Version table:
> 2.02+dfsg1-20+deb10u4 500
> 500 http://ftp.de.debian.org/debian buster/main amd64 Packages
> 500 http:
More information:
markus@bmtMB1:/var/log/apt$ sudo apt policy grub-efi-amd64 grub-common
grub2-common grub-efi-amd64-bin
grub-efi-amd64:
Installed: (none)
Candidate: 2.02+dfsg1-20+deb10u3
Version table:
2.02+dfsg1-20+deb10u4 500
500 http://ftp.de.debian.org/debian buster/main
On Thu, Jun 24, 2021 at 05:06:50PM +0200, Markus wrote:
> I wanted to reinstall grub-efi-amd64 and got this:
>
> markus@bmtMB1:/var/log/apt$ sudo apt install grub-efi-amd64
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
>
I wanted to reinstall grub-efi-amd64 and got this:
markus@bmtMB1:/var/log/apt$ sudo apt install grub-efi-amd64
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible
+deb10u4), grub-efi-amd64-bin:amd64 (2.02+dfsg1-20+deb10u3,
2.02+dfsg1-20+deb10u4), grub-efi-amd64-signed:amd64
(1+2.02+dfsg1+20+deb10u3, 1+2.02+dfsg1+20+deb10u4)
Remove: grub-efi-amd64:amd64 (2.02+dfsg1-20+deb10u3)
End-Date: 2021-03-06 21:08:45
Do you guys maybe find similar entries in apt
David Wright (12021-06-24):
> Only if you'd gone ahead and removed all those other packages.
Not even then. The GRUB packages are useful for installing the GRUB
bootloader. Once it's installed, the computer will boot, and the package
are not necessary, although they might be useful to
On Thu 24 Jun 2021 at 08:49:40 (+0200), Markus wrote:
> Am 23.06.21 um 18:08 schrieb David Wright:
> > On Wed 23 Jun 2021 at 17:01:07 (+0200), Markus wrote:
> > > rc grub-efi-amd64 2.02+dfsg1-20+deb10u3
> >↑↑ There's your problem. It's been removed (but not purged).
t it be gone if it got removed (even though
> it not got purged)? Hmmm...!?!?
Removing the grub packages doesn't remove GRUB from your hard drive(s).
Thankfully.
> How to fix that? Is there actually something wrong (this morning grub
> was there!!!) that needs to be fixed?
> Is it save to
to fix that? Is there actually something wrong (this morning grub
was there!!!) that needs to be fixed?
Is it save to just reinstall grub-efi-amd64?
Cheers
Markus
Am 23.06.21 um 18:08 schrieb David Wright:
On Wed 23 Jun 2021 at 17:01:07 (+0200), Markus wrote:
Am 23.06.21 um 16:43 schrieb David
On Wed 23 Jun 2021 at 17:01:07 (+0200), Markus wrote:
> Am 23.06.21 um 16:43 schrieb David Wright:
> > Has grub-efi-amd64 been accidentally removed? AIUI that's the package
> > which depends on having the packages to boot your machine.
> No, not that I am aware of. But
No, not that I am aware of. But here is the ouput of
markus@bmtMB1:~$ sudo dpkg -l | grep grub
ii grub-common 2.02+dfsg1-20+deb10u4
amd64 GRand Unified Bootloader (common files)
rc grub-efi-amd64 2.02+dfsg1-20+deb10u3
amd64 GRand
matically installed and are no
> longer required:
> efibootmgr grub-efi-amd64-bin grub-efi-amd64-signed grub2-common
> libappindicator3-1 libcanberra-gtk3-0 libcanberra-gtk3-module
> libclutter-gtk-1.0-0 libdbusmenu-glib4 libdbusmenu-gtk3-4 libindicator3-7
> libupsclient4 linux-head
On Wed, Jun 23, 2021 at 03:55:04PM +0200, Markus wrote:
>Hi, just before and also after today's "apt full-upgrade" apt tells me
>that:
> The following packages were automatically installed and are no longer
> required:
> efibootmgr grub-efi-amd64-bin grub-efi-
Hi, just before and also after today's "apt full-upgrade" apt tells
me that:
The following packages were automatically installed and are no longer required:
efibootmgr grub-efi-amd64-bin grub-efi-amd64-signed grub2-common
libappindicator3-1 libcanberra-gtk3-0 l
e 1:7.0.4-3 qui n'a aucune
fonction pour modifier la taille de la fonte de la barre de menu.
> Comment dire è rEFInd d'utiliser 1280x800 ou 1280x720 ?
>
> J'ai bricolé /etc/default/grub et /boot/efi/EFI/boot/refind.conf
> sans sucés
>
> > Encore merci
>
> C'est
368x768
Comment dire è rEFInd d'utiliser 1280x800 ou 1280x720 ?
J'ai bricolé /etc/default/grub et /boot/efi/EFI/boot/refind.conf sans
sucés
> Encore merci
C'est bien évidement moi qui vous remercie ;-)
>
> > Le 14 avr. 2021 à 08:28, Georges a écrit :
> >
> >
&g
; >> demain.
> >>
> >> Je vais essayer Bullseye qui était installé sur l'ancien et
> >> marchait très bien.
> >>
> >> Bonne nuit et je reviens ...
> >
> > Me revoilà,
> >
> > Maintenant UEFI / EFI trituré par MS.
>
e tous cela ce soir et
> >> demain.
> >>
> >> Je vais essayer Bullseye qui était installé sur l'ancien et marchait
> >> très bien.
> >>
> >> Bonne nuit et je reviens ...
> >
> > Me revoilà,
> >
> > Maintenant UEFI
lseye qui était installé sur l'ancien et marchait
>> très bien.
>>
>> Bonne nuit et je reviens ...
>
> Me revoilà,
>
> Maintenant UEFI / EFI trituré par MS.
> Sur un ordinateur récent, il ma fallut partitioner le disque en GPT (
> gparted en live). Installer
1 - 100 of 338 matches
Mail list logo
