Am 06.10.20 um 01:50 schrieb Chris Murphy:
> In this case you can replace it by just copying a substitute
> grubx64.efi to the proper location on the USB stick... which might be
> EFI/BOOT, I'd have to poke it with a stick to find out.
>
>
I already tried to replace it with a f31 one, it did
On Mon, Oct 5, 2020 at 12:59 PM Samuel Sieb wrote:
>
> On 10/5/20 11:21 AM, Marius Schwarz wrote:
> > Am 04.10.20 um 21:01 schrieb Samuel Sieb:
> >> On 10/4/20 9:36 AM, Marius Schwarz wrote:
> >>> And still,we do not know why the f33 livedisc does not boot at all when
> >>> inserted early
> >>>
On 10/5/20 11:21 AM, Marius Schwarz wrote:
Am 04.10.20 um 21:01 schrieb Samuel Sieb:
On 10/4/20 9:36 AM, Marius Schwarz wrote:
And still,we do not know why the f33 livedisc does not boot at all when
inserted early
AND
why grub-install /dev/USBDRIVE (correct devicename ofcourse ) is
Am 04.10.20 um 21:01 schrieb Samuel Sieb:
> On 10/4/20 9:36 AM, Marius Schwarz wrote:
>> And still,we do not know why the f33 livedisc does not boot at all when
>> inserted early
>> AND
>> why grub-install /dev/USBDRIVE (correct devicename ofcourse ) is
>> overwriting the ssd boot setup, instead
On Sun, Oct 4, 2020 at 10:50 AM Marius Schwarz wrote:
>
> Am 03.10.20 um 22:07 schrieb Chris Murphy:
> >
> > No the correct invocation is "dnf reinstall grub2-efi-x64 shim-x64"
> >
> > Suggesting UEFI users install GRUB with grub2-install is asking for a
> > support nightmare, it's untenable.
> >
On Sun, Oct 4, 2020 at 10:37 AM Marius Schwarz wrote:
>
> now, the efi stuff is installed, i accept a few "oh, theres efi, i do
> efi" mistakes from time to time. But i don't have a clue, how the system
> could boot with those symlinks before that grub-install destroyed it.
The symlinks are in
On Sun, Oct 4, 2020 at 3:01 PM Samuel Sieb wrote:
>
> On 10/4/20 9:36 AM, Marius Schwarz wrote:
> > And still,we do not know why the f33 livedisc does not boot at all when
> > inserted early
> > AND
> > why grub-install /dev/USBDRIVE (correct devicename ofcourse ) is
> > overwriting the ssd boot
On 10/4/20 9:36 AM, Marius Schwarz wrote:
And still,we do not know why the f33 livedisc does not boot at all when
inserted early
AND
why grub-install /dev/USBDRIVE (correct devicename ofcourse ) is
overwriting the ssd boot setup, instead of the usbdrive bootconfig.
You can't use
Am 03.10.20 um 22:07 schrieb Chris Murphy:
>
> No the correct invocation is "dnf reinstall grub2-efi-x64 shim-x64"
>
> Suggesting UEFI users install GRUB with grub2-install is asking for a
> support nightmare, it's untenable.
>
Isn't a simple check "are we booted with efi" a working solution to
Am 03.10.20 um 22:23 schrieb Chris Murphy:
>
>> after investigating the problem with not finding grub.cfg in the
>> proprosed bootpath /boot/ .. the solution was simple.
>>
>> The system died not use secure boot, as secure-boot was disabled for the
>> kernel-surface kernelseries. They are
On Sat, Oct 3, 2020 at 4:09 AM Marius Schwarz wrote:
>
> Am 03.10.20 um 11:43 schrieb Tomasz Torcz:
>
> If you do not state the devicename, how does grub choose the correct
>
> drive? I don't want to overwrite the bootloader on the ssd.
>
> There is only one correct ESP partition in EFI system
On Fri, Oct 2, 2020 at 3:12 AM Petr Pisar wrote:
>
> On Thu, Oct 01, 2020 at 11:07:28AM -0700, Samuel Sieb wrote:
> > On 10/1/20 5:52 AM, Marius Schwarz wrote:
> > >
> > > >
> > > > Is it possible to boot from the stick and then perform a grub-install
> > > > with an old grub?
> > > >
> > >
> > >
Am 03.10.20 um 11:43 schrieb Tomasz Torcz:
> If you do not state the devicename, how does grub choose the correct
>> drive? I don't want to overwrite the bootloader on the ssd.
> There is only one correct ESP partition in EFI system to install
> bootloader to. You can read the code finding it at
On Sat, Oct 03, 2020 at 11:17:44AM +0200, Marius Schwarz wrote:
> Am 02.10.20 um 11:12 schrieb Petr Pisar:
> > On Thu, Oct 01, 2020 at 11:07:28AM -0700, Samuel Sieb wrote:
> >> On 10/1/20 5:52 AM, Marius Schwarz wrote:
> Is it possible to boot from the stick and then perform a grub-install
>
Am 03.10.20 um 11:17 schrieb Marius Schwarz:
>
> FYI: Not working without manual corrections
>
> insmod lvm
> insmod xfs
> set root=(hd0,gpt3)
> configfile /grub2/grub.cfg
> linux /vmlinuz-5.8.10
> initrd /initramfs-5.8.10
> boot
>
> Q: Why is configfile read, but not used if anything
Am 02.10.20 um 11:12 schrieb Petr Pisar:
> On Thu, Oct 01, 2020 at 11:07:28AM -0700, Samuel Sieb wrote:
>> On 10/1/20 5:52 AM, Marius Schwarz wrote:
Is it possible to boot from the stick and then perform a grub-install
with an old grub?
>>> This attempt failed too:
>>>
>>> #
On Thu, Oct 01, 2020 at 11:07:28AM -0700, Samuel Sieb wrote:
> On 10/1/20 5:52 AM, Marius Schwarz wrote:
> >
> > >
> > > Is it possible to boot from the stick and then perform a grub-install
> > > with an old grub?
> > >
> >
> > This attempt failed too:
> >
> > # grub2-install /dev/sda
> >
On 10/1/20 5:52 AM, Marius Schwarz wrote:
Is it possible to boot from the stick and then perform a grub-install
with an old grub?
This attempt failed too:
# grub2-install /dev/sda
grub2-install: Fehler: /usr/lib/grub/x86_64-efi/modinfo.sh existiert
nicht. Bitte geben Sie --target oder
>
> Is it possible to boot from the stick and then perform a grub-install
> with an old grub?
>
This attempt failed too:
# grub2-install /dev/sda
grub2-install: Fehler: /usr/lib/grub/x86_64-efi/modinfo.sh existiert
nicht. Bitte geben Sie --target oder --directory an.
and that file seems not
Am 01.10.20 um 07:22 schrieb Chris Murphy:
> On Wed, Sep 30, 2020 at 4:22 PM Marius Schwarz wrote:
>> Am 01.10.20 um 00:02 schrieb Chris Murphy:
>>
>> I made some more tests. It's a race, 1 out of 10 tries succeeds and the
>> chance that it does is improoved by inserting the usb drive while being
On 9/30/20 10:28 PM, Elliott Sales de Andrade wrote:
On Wed, 30 Sep 2020 at 18:27, Marius Schwarz wrote:
The working/non-working procedure is:
Power on
...
inserting the stick
OK, but why insert the USB stick after power on?
Wouldn't it be less trouble to insert beforehand so that the
On Wed, 30 Sep 2020 at 18:27, Marius Schwarz wrote:
>
> Am 01.10.20 um 00:19 schrieb Elliott Sales de Andrade:
>
> Could it be a timing issue of some kind?
>
> the sooner i hit the boot from usb button, after the stick got inserted,
> the higher is the propability to start.
>
> Are you saying you
On Wed, Sep 30, 2020 at 4:22 PM Marius Schwarz wrote:
>
> Am 01.10.20 um 00:02 schrieb Chris Murphy:
>
> I made some more tests. It's a race, 1 out of 10 tries succeeds and the
> chance that it does is improoved by inserting the usb drive while being
> in the bios.
>
> The F31 grub files i
Am 01.10.20 um 00:19 schrieb Elliott Sales de Andrade:
>> Could it be a timing issue of some kind?
>>
>> the sooner i hit the boot from usb button, after the stick got inserted,
>> the higher is the propability to start.
>>
> Are you saying you insert the USB stick _after_ turning on the
>
Am 01.10.20 um 00:02 schrieb Chris Murphy:
>> I made some more tests. It's a race, 1 out of 10 tries succeeds and the
>> chance that it does is improoved by inserting the usb drive while being
>> in the bios.
>>
>> The F31 grub files i exchanged do not seem to have something to do with it.
> The
On Wed, 30 Sep 2020 at 17:42, Marius Schwarz wrote:
>
> Am 30.09.20 um 23:00 schrieb Chris Murphy:
> >
> >
> > And then these are current
> > grub2-efi-x64-2.04-31.fc33.x86_64
> > grub2-efi-x64-2.04-23.fc32.x86_64
> > grub2-efi-x64-2.02-110.fc31.x86_64
> >
> > I wonder if the affected hardware is
On Wed, Sep 30, 2020 at 3:42 PM Marius Schwarz wrote:
>
> Am 30.09.20 um 23:00 schrieb Chris Murphy:
> >
> >
> > And then these are current
> > grub2-efi-x64-2.04-31.fc33.x86_64
> > grub2-efi-x64-2.04-23.fc32.x86_64
> > grub2-efi-x64-2.02-110.fc31.x86_64
> >
> > I wonder if the affected hardware
Am 30.09.20 um 23:00 schrieb Chris Murphy:
>
>
> And then these are current
> grub2-efi-x64-2.04-31.fc33.x86_64
> grub2-efi-x64-2.04-23.fc32.x86_64
> grub2-efi-x64-2.02-110.fc31.x86_64
>
> I wonder if the affected hardware is adversely affected by all three
> of these versions of GRUB?
>
I made
On Wed, Sep 30, 2020 at 10:46 AM Stephen John Smoogen
wrote:
>
> The Fedora secure boot signing keys were updated after F32 was initially
released to deal with the grub2 problems found during the summer. I believe
some systems have needed firmware updates from the manufacturer to work
with the
Am 30.09.20 um 18:45 schrieb Stephen John Smoogen:
>
> The Fedora secure boot signing keys were updated after F32 was
> initially released to deal with the grub2 problems found during the
> summer. I believe some systems have needed firmware updates from the
> manufacturer to work with the new key
Am 30.09.20 um 20:54 schrieb Brian C. Lane:
> On Wed, Sep 30, 2020 at 12:45:40PM -0400, Stephen John Smoogen wrote:
>> The Fedora secure boot signing keys were updated after F32 was initially
>> released to deal with the grub2 problems found during the summer. I believe
>> some systems have needed
Am 30.09.20 um 18:45 schrieb Stephen John Smoogen:
>
>
>
> The Fedora secure boot signing keys were updated after F32 was
> initially released to deal with the grub2 problems found during the
> summer. I believe some systems have needed firmware updates from the
> manufacturer to work with the new
Am 30.09.20 um 17:17 schrieb Chris Murphy:
>
> That suggests the scary region of firmware, hybrid ISO, shim, and boot loader.
>
> The bug reports have the wrong component set on them, and aren't
> discrete actionable bug reports. It's just saying "this doesn't work"
which one do you suggest?
>> An
On Wed, Sep 30, 2020 at 12:45:40PM -0400, Stephen John Smoogen wrote:
> The Fedora secure boot signing keys were updated after F32 was initially
> released to deal with the grub2 problems found during the summer. I believe
> some systems have needed firmware updates from the manufacturer to work
>
On Wed, 30 Sep 2020 at 11:54, Erich Eickmeyer
wrote:
> On 9/30/2020 8:17 AM, Chris Murphy wrote:
> > On Wed, Sep 30, 2020 at 2:05 AM Marius Schwarz
> wrote:
> >> Hi,
> >>
> >> the livecds from F32 and F33 are suffering from a problem not booting on
> >> Microsoft device(s)
> >>
> >>
On 9/30/2020 8:17 AM, Chris Murphy wrote:
> On Wed, Sep 30, 2020 at 2:05 AM Marius Schwarz wrote:
>> Hi,
>>
>> the livecds from F32 and F33 are suffering from a problem not booting on
>> Microsoft device(s)
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1879921
>>
On Wed, Sep 30, 2020 at 2:05 AM Marius Schwarz wrote:
>
> Hi,
>
> the livecds from F32 and F33 are suffering from a problem not booting on
> Microsoft device(s)
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1879921
> https://bugzilla.redhat.com/show_bug.cgi?id=1883593
>
> F31 is booting fine,
Hi,
the livecds from F32 and F33 are suffering from a problem not booting on
Microsoft device(s)
https://bugzilla.redhat.com/show_bug.cgi?id=1879921
https://bugzilla.redhat.com/show_bug.cgi?id=1883593
F31 is booting fine, the newer ones not. Looks like a GrubBootloader
issue to me, as not even
38 matches
Mail list logo
