On 7/3/25 2:34 PM, Bill Cunningham wrote:
OK I see. Sorry to get back so late. The server was not letting me post. REST
error or something. I manually erased the rescue entry but now I have no rescue
entry. Not even for the new kernel
You can reinstall the current kernel or wait until the nex
På Thu, 03 Jul 2025 21:36:38 -
"Bill Cunningham" skrev:
> Can you generate a rescue entry?
Try:
sudo rm /boot/*rescue*
sudo kernel-install add "$(uname -r)" "/lib/modules/$(uname -r)/vmlinuz"
--
___
users mailing list -- users@lists.fedoraprojec
I thought I removed the old kernel and the rpms were there, just like you
suggested.
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fed
Can you generate a rescue entry?
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Gu
test
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproj
OK I see. Sorry to get back so late. The server was not letting me post. REST
error or something. I manually erased the rescue entry but now I have no rescue
entry. Not even for the new kernel
--
___
users mailing list -- users@lists.fedoraproject.org
Bill Cunningham writes:
I just updated my fedora 41 to 42 using dnf. Now everything works find and
boots but the old selection for fedora 41 is still on the bootloader
options. How do I get this off? I tried something with grub2-mkconfig and
that didn't work. I want the fedora 42 option (Ad
> On 2 Jul 2025, at 21:31, Joe Average wrote:
>
> Bill Cunningham wrote:
>> I just updated my fedora 41 to 42 using dnf. Now everything works find and
>> boots but the old selection for fedora 41 is still on the bootloader
>> options. How do I get this off? I tried something with grub2-mkcon
Bill Cunningham wrote:
> I just updated my fedora 41 to 42 using dnf. Now everything works find and
> boots but the old selection for fedora 41 is still on the bootloader options.
> How do I get this off? I tried something with grub2-mkconfig and that didn't
> work. I want the fedora 42 option (
On 30.06.2025 19:52 "Bill Cunningham" wrote:
> I just updated my fedora 41 to 42 using dnf. Now everything works
> find and boots but the old selection for fedora 41 is still on the
> bootloader options. How do I get this off?
I assume this is caused by an old kernel. Can you check which kernel
I just updated my fedora 41 to 42 using dnf. Now everything works find and
boots but the old selection for fedora 41 is still on the bootloader options.
How do I get this off? I tried something with grub2-mkconfig and that didn't
work. I want the fedora 42 option (Adams) and a rescue option and
On Thu, Apr 10, 2025 at 8:52 PM Go Canes wrote:
>
> I recently updated the BIOS on a new Dell XPS 16 running Fedora 40.
> Prior to the update everything was working fine. After the update,
> grub displays the boot menu and indicates it is booting the default
> entry, then...not
Le 30/04/2025 à 13:49, Barry a écrit :
On 30 Apr 2025, at 09:03, François Patte wrote:
Bonjour,
I have a f40 install on one disk (say /dev/sdc) and I want to install F42 on
/dev/sda.
I suppose that after the installation grub will propose to start f42 from the
new disk, how can I add to
> On 30 Apr 2025, at 09:03, François Patte wrote:
>
> Bonjour,
>
> I have a f40 install on one disk (say /dev/sdc) and I want to install F42 on
> /dev/sda.
>
> I suppose that after the installation grub will propose to start f42 from the
> new disk, how can I
Bonjour,
I have a f40 install on one disk (say /dev/sdc) and I want to install
F42 on /dev/sda.
I suppose that after the installation grub will propose to start f42
from the new disk, how can I add to grub the now old f40? Is there a
step during the install process of f42 to say that I want
On Wed Apr16'25 12:59:45AM, Patrick O'Callaghan wrote:
> From: Patrick O'Callaghan
> Date: Wed, 16 Apr 2025 00:59:45 +0100
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users
> Subject: Re: updating the GRUB bootloader on EFI syste
> > Is the command called something else?
>
> FYI: There a a number of ways to answer this question yourself.
>
> 1. ls /usr/bin/*fwupd*
> 2. rpm -ql fwupd
>
> I use the rpm -ql frequently when I'm not sure what an RPM installed and
> where it put it.
>
Thanks very much for this information!
p a boot loader like GRUB2.
The GRUB menu gives you a variety of options about *how* you will boot
Linux (which kernel, rescue modes, etc). UEFI will (usually) just give
you an option for which drive to boot an OS from. For me that's the
hard drive with Fedora installed, or the DVD-ROM d
> On 16 Apr 2025, at 00:54, Ranjan Maitra via users
> wrote:
>
> $ sudo fwupd
> sudo: fwupd: command not found
>
> However, fwupd is installed. Why can it not be found?
>
> $ sudo dnf install fwupd
> Updating and loading repositories:
> Repositories loaded.
> Package "fwupd-1.9.29-1.fc41.x86
On Wed Apr16'25 12:38:41AM, Patrick O'Callaghan wrote:
> From: Patrick O'Callaghan
> Date: Wed, 16 Apr 2025 00:38:41 +0100
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users
> Subject: Re: updating the GRUB bootloader on EFI syste
nity support for Fedora users
> > Subject: Re: updating the GRUB bootloader on EFI systems while upgrading
> >
> > On Tue, 2025-04-15 at 18:00 -0500, Ranjan Maitra via users wrote:
> > > Thanks! But I get fwupd: command not found.
> > >
> > > Is that not
On Tue, 2025-04-15 at 18:00 -0500, Ranjan Maitra via users wrote:
> Thanks! But I get fwupd: command not found.
>
> Is that not different from an update not found?
>
$ rpm -qi fwupd
Name: fwupd
Version : 1.9.29
Release : 1.fc41
Architecture: x86_64
Install Date: Thu 20 Mar 2025 09
On Wed Apr16'25 12:20:56AM, greg wrote:
> From: greg
> Date: Wed, 16 Apr 2025 00:20:56 +0200
> To: Community support for Fedora users
> Reply-To: Community support for Fedora users
> Subject: Re: updating the GRUB bootloader on EFI systems while upgrading
>
> >
> Why do I get fwupd not found?
The commands to use - as root - are:
# fwupdmgr get-updates
If updates are available for any devices on the system, they'll be displayed.
# fwupdmgr update
This will download and apply all updates for your system.
(Taken from
/usr/share/doc/fwupd/README.md)
Also t
Thanks for your response!
On Tue Apr15'25 09:07:27PM, Marco Moock wrote:
> From: Marco Moock
> Date: Tue, 15 Apr 2025 21:07:27 +0200
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users
> Subject: Re: updating the GRUB bootloader on EFI sys
> On 15 Apr 2025, at 19:59, Ranjan Maitra via users
> wrote:
>
> However, the installed or embedded bootloaders are never updated
> automatically.
If you mean the fedora efi code; it is updated in /boot/efi when there is a
change.
I have personally verified this works recently.
Barry
--
Am 15.04.2025 um 13:25:14 Uhr schrieb Ranjan Maitra via users:
> According to
> https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/
> systems with the BIOS firmware have the GRUB RPM packages updated.
> However, the installed or embedded bootloaders are n
According to
https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/
systems with the BIOS firmware have the GRUB RPM packages updated. However, the
installed or embedded bootloaders are never updated automatically.
It is my understanding that my GRUB2 is installed on UEFI
On Sat, 2025-04-12 at 15:32 -0700, Samuel Sieb wrote:
> You mentioned that you installed the non-graphical system, then added
> the desktop later. That's why I thought the server one didn't let you
> add desktops during install.
I mentioned that. I don't recall if it were a case of blind insta
On Sat, Apr 12, 2025 at 6:32 PM Samuel Sieb wrote:
> You mentioned that you installed the non-graphical system, then added
> the desktop later. That's why I thought the server one didn't let you
> add desktops during install.
I installed the desktop as part of the Fedora install. Sorry if I led
On 4/12/25 3:27 PM, Go Canes wrote:
On Sat, Apr 12, 2025 at 6:16 PM Samuel Sieb wrote:
I missed that you were using the netinstall version of the server
install. I didn't realize there was one. The everything install lets
you install the graphical desktop as well. Also, at least the
filesyst
On Sat, Apr 12, 2025 at 6:16 PM Samuel Sieb wrote:
> I missed that you were using the netinstall version of the server
> install. I didn't realize there was one. The everything install lets
> you install the graphical desktop as well. Also, at least the
> filesystem defaults are different with
On 4/12/25 4:46 AM, Go Canes wrote:
On Fri, Apr 11, 2025 at 11:16 PM Samuel Sieb wrote:
On 4/11/25 6:45 PM, Go Canes wrote:
On Fri, Apr 11, 2025 at 9:42 AM Tim via users
wrote:
When I installed Fedora 40 (I think, it's 40), I couldn't get the usual
installation ISOs to work. I had to use t
t the system to boot by manually entering
> the original
> Boot0001.
I will double-check, but I don't think this would affect choosing the
boot using the F12 menu to boot off of USB, etc. Also, I think the
EFI entry points to grub, and we *are* booting grub, just nothing
afte
On Thu, Apr 10, 2025 at 9:52 PM Go Canes wrote:
> I recently updated the BIOS on a new Dell XPS 16 running Fedora 40.
> Prior to the update everything was working fine. After the update,
> grub displays the boot menu and indicates it is booting the default
> entry, then...nothing
On Fri, Apr 11, 2025 at 11:16 PM Samuel Sieb wrote:
>
> On 4/11/25 6:45 PM, Go Canes wrote:
> > On Fri, Apr 11, 2025 at 9:42 AM Tim via users
> > wrote:
> >> When I installed Fedora 40 (I think, it's 40), I couldn't get the usual
> >> installation ISOs to work. I had to use the server spin, I be
> On 11 Apr 2025, at 14:41, Tim via users wrote:
>
> I had to use the server spin, I believe it
> used a different bootloading method.
All my server installs use the exact same boot mechanism as my desktops.
e.g. UEFI shim -> grub -> kernel -&
On 4/11/25 6:45 PM, Go Canes wrote:
On Fri, Apr 11, 2025 at 9:42 AM Tim via users
wrote:
When I installed Fedora 40 (I think, it's 40), I couldn't get the usual
installation ISOs to work. I had to use the server spin, I believe it
used a different bootloading method. I installed a non-graphic
A thought that occurs to me
The various Fedora boot failures are occurring after grub, but before
any kernel output. Failure loading initrd image? So maybe something
to do with RAM that the BIOS testing isn't detecting, or something to
do with decompressing the image? Either way, why
On Fri, Apr 11, 2025 at 9:42 AM Tim via users
wrote:
> When I installed Fedora 40 (I think, it's 40), I couldn't get the usual
> installation ISOs to work. I had to use the server spin, I believe it
> used a different bootloading method. I installed a non-graphical
> system, afterwards installin
On Fri, Apr 11, 2025 at 1:51 AM Marco Moock wrote:
> I assume it is an UEFI (some vendors still call that BIOS).
Yes, UEFI which Dell still calls BIOS
> Can you reset it to the default settings?
While I didn't list it, this has been tried. More than once.
> Does it support CSM?
I can't find
On Thu, 2025-04-10 at 20:52 -0400, Go Canes wrote:
> - booting a f40 netinstall ISO(via Ventoy) (the same one used to
> instal Fedora 40 on this laptop initially) gets as far as the
> "install/test/rescue" menu, but otherwise has the same boot failure
When I installed Fedora 40 (I think, it's 40),
is in AHCI mode (not RAID)
> - tried disabling extra C-states in BIOS - no change
> - BIOS has self-tests, they all pass
> - booting older kernels including the rescue kernel do not change the
> behavior (other than the grub output as to which kernel is being
> booted)
I assume it
I recently updated the BIOS on a new Dell XPS 16 running Fedora 40.
Prior to the update everything was working fine. After the update,
grub displays the boot menu and indicates it is booting the default
entry, then...nothing.
I have performed the following tests and/or remedial actions
actually boots Ubuntu fine, how I don't know as Ubuntu is
installed via UEFI. It wasn't until I upgraded the version of Ubuntu and
my motherboard switched from booting into the Fedora grub menus to
booting into the Ubuntu grub menus, it because apparent that the
relevant component o
Hi All,
I usually do not pay much attention to the kernel entries
on my grub boot screen, but after upgrading my shop computer
from FC40 to FC41 I looked. Oh Goody, I have kernels on
my geub boot screen all the way back to FC32!!! 3/4 of my
screen was filled with kernels!
Checking "r
x27;m running
> an AMD cpu.
> I have also recently been in the situation where I upgraded the version of
> Ubuntu I'm running, which set up its grub environment, and that upgrade
> changed the boot order in the Motherboard bios to boot from Ubuntu instead of
> Fedora, which
grub menus.
I don't think there is any connection between the order of the UEFI
boot variables and the order things are presented in grub menus.
I always wondered why there are two entries for Fedora in the bios boot
settings (that both look to be the same name) and what you have said i
Stephen Morris composed on 2024-10-31 09:11 (UTC+1100):
> I always wondered why there are two
> entries for Fedora in the bios boot settings (that both look to be the
> same name)
Are dates and times on the two directories the same?
What does GRUB_DISTRIBUTOR= contain?
--
Evolution as taught
On Thu, 2024-10-31 at 09:11 +1100, Stephen Morris wrote:
> I always wondered why there are two entries for Fedora in the bios
> boot settings (that both look to be the same name) and what you have
> said is the indication of the shim that is being booted from, I'm now
> wondering why there aren't t
On Wed, Oct 30, 2024 at 6:11 PM Stephen Morris
wrote:
> On 30/10/24 11:51, Go Canes wrote:
> My output from efibootmgr is below. The boot order specified in the
> output is the boot order specified in my motherboard bios, not the boot
> orders specified in the grub menus.
I
output is the boot order specified in my motherboard bios, not the boot
orders specified in the grub menus. I always wondered why there are two
entries for Fedora in the bios boot settings (that both look to be the
same name) and what you have said is the indication of the shim that is
being
On Tue, Oct 29, 2024 at 7:16 PM ToddAndMargo via users
wrote:
> Cool command. Thank you!
You're welcome/
> BootCurrent:
You are currently booted using variable Boot
> Boot* fedora/boot/efi/EFI/fedora/
> HD(1,GPT,6e58cd53-8fbd-4b97-bce2-fa7c43e105f3,0x800,0x64000)/\EFI\FEDORA\GRUBX
On 10/29/24 14:08, Stephen Morris wrote:
On 29/10/24 14:02, ToddAndMargo via users wrote:
On 10/27/24 14:24, Stephen Morris wrote:
If you are still on a legacy bios system, from memory, before running
grub2-install you need to run grub2-mkconfig to build the grub menu
configuration for grub2
-insensitive.
- From that partition, it loads the file "\EFI\FEDORA\SHIMX64.EFI".
- That file in turn continues the bootstrap. For this specific case,
SHIMX64.EFI loads grubx64.efi from the same directory, which
references grub.cfg from the same directory.
- grub.cfg tells grub how to
at partition, it loads the file "\EFI\FEDORA\SHIMX64.EFI".
- That file in turn continues the bootstrap. For this specific case,
SHIMX64.EFI loads grubx64.efi from the same directory, which
references grub.cfg from the same directory.
- grub.cfg tells grub how to find /boot, which it uses to fi
On 29/10/24 14:02, ToddAndMargo via users wrote:
On 10/27/24 14:24, Stephen Morris wrote:
If you are still on a legacy bios system, from memory, before running
grub2-install you need to run grub2-mkconfig to build the grub menu
configuration for grub2-install to build those into the mbr
he one with the long sypher name)
Rename it by appending .save to its name (for security).
4) dnf update. This will reinstall the f39 kernel, but without failure
this time.
5) dnf reinstall kernel-core
6) Reboot: you should now see the f39 kernel in the grub menu --> start
with it.
7) Do
On 10/29/24 04:47, Jonathan Billings wrote:
The directory name should match the contents of /etc/machine-id.
I feel like this has been mentioned a couple times in the last week, have you seen
the posts about this? Most likely part of the package update/downgrades/whatever
have either installe
locate the machine id directory (i.e.:
b4bf0711a.9614). Rename it by appending .save to its name (for
security).
4) dnf update. This will reinstall the f39 kernel, but without failure
this time.
5) Reboot: you should now see the f39 kernel in the grub menu --> start
with it.
6) Do what
ToddAndMargo wrote:
> I do not understand what is meant in step 3: "locate the
> id directory":
> # ls -al /boot/efi
> total 36
> drwx--. 5 root root 16384 Dec 31 1969 .
> dr-xr-xr-x. 9 root root 4096 Oct 25 04:35 ..
> drwx--. 12 root root 4096 Oct 25 04:35 25f870556c344b599c639eb38629
.fc40.x86_64
Problem, only the 38 kernel shows in grub.
How do I get the 40 kernel to show in grub?
Yours in confusion,
-T
This may be the issue:
# mount | grep "/boot "
/dev/nvme0n1p2 on /boot type ext4 (rw,relatime,seclabel)
# grub2-install /dev/nvme0n1
Installing for x86_64-ef
On 10/27/24 14:24, Stephen Morris wrote:
If you are still on a legacy bios system, from memory, before running
grub2-install you need to run grub2-mkconfig to build the grub menu
configuration for grub2-install to build those into the mbr.
regards,
Steve
Hi Steve,
I tried
# grub2
On 28/10/24 09:27, ToddAndMargo via users wrote:
On 10/27/24 14:24, Stephen Morris wrote:
If you are still on a legacy bios system, from memory, before running
grub2-install you need to run grub2-mkconfig to build the grub menu
configuration for grub2-install to build those into the mbr
On 10/27/24 14:24, Stephen Morris wrote:
If you are still on a legacy bios system, from memory, before running
grub2-install you need to run grub2-mkconfig to build the grub menu
configuration for grub2-install to build those into the mbr.
regards,
Steve
NVMe drive require UEFI. My
shows in grub.
How do I get the 40 kernel to show in grub?
Yours in confusion,
-T
This may be the issue:
# mount | grep "/boot "
/dev/nvme0n1p2 on /boot type ext4 (rw,relatime,seclabel)
# grub2-install /dev/nvme0n1
Installing for x86_64-efi platform.
grub2-install: error: This util
shows in grub.
How do I get the 40 kernel to show in grub?
Yours in confusion,
-T
This may be the issue:
# mount | grep "/boot "
/dev/nvme0n1p2 on /boot type ext4 (rw,relatime,seclabel)
# grub2-install /dev/nvme0n1
Installing for x86_64-efi platform.
grub2-install: error: Th
On 10/25/24 03:31, ToddAndMargo via users wrote:
On 10/23/24 20:56, ToddAndMargo via users wrote:
Hi All,
$ rpm -qa kernel
kernel-6.5.10-200.fc38.x86_64
kernel-6.11.3-100.fc39.x86_64
kernel-6.11.4-201.fc40.x86_64
Problem, only the 38 kernel shows in grub.
How do I get the 40 kernel to show
On 25/10/24 21:31, ToddAndMargo via users wrote:
On 10/23/24 20:56, ToddAndMargo via users wrote:
Hi All,
$ rpm -qa kernel
kernel-6.5.10-200.fc38.x86_64
kernel-6.11.3-100.fc39.x86_64
kernel-6.11.4-201.fc40.x86_64
Problem, only the 38 kernel shows in grub.
How do I get the 40 kernel to show
On 10/23/24 20:56, ToddAndMargo via users wrote:
Hi All,
$ rpm -qa kernel
kernel-6.5.10-200.fc38.x86_64
kernel-6.11.3-100.fc39.x86_64
kernel-6.11.4-201.fc40.x86_64
Problem, only the 38 kernel shows in grub.
How do I get the 40 kernel to show in grub?
Yours in confusion,
-T
This may be
On 10/23/24 20:56, ToddAndMargo via users wrote:
Hi All,
$ rpm -qa kernel
kernel-6.5.10-200.fc38.x86_64
kernel-6.11.3-100.fc39.x86_64
kernel-6.11.4-201.fc40.x86_64
Problem, only the 38 kernel shows in grub.
How do I get the 40 kernel to show in grub?
Yours in confusion,
-T
This may be
96% /boot/efi
This is evidence that suggests there may have been kernel installations for a
systemd-boot configured system that in fact is a grub configured system. Kernels
on a systemd-boot configured system are installed on an ESP partition, which
mounts to /boot/efi/, and requires a signifi
On 10/24/24 14:27, Jonathan Billings wrote:
On Oct 23, 2024, at 23:57, ToddAndMargo via users
wrote:
Hi All,
$ rpm -qa kernel
kernel-6.5.10-200.fc38.x86_64
kernel-6.11.3-100.fc39.x86_64
kernel-6.11.4-201.fc40.x86_64
Problem, only the 38 kernel shows in grub.
How do I get the 40 kernel to
On Oct 23, 2024, at 23:57, ToddAndMargo via users
wrote:
>
> Hi All,
>
> $ rpm -qa kernel
> kernel-6.5.10-200.fc38.x86_64
> kernel-6.11.3-100.fc39.x86_64
> kernel-6.11.4-201.fc40.x86_64
>
> Problem, only the 38 kernel shows in grub.
>
> How do I get the 40 k
On 10/23/24 23:07, Jeffrey Walton wrote:
I think you are stumbling through your own self-inflicted problems on
your personal Linux installation.
You have no credibility.
I think you have no idea how to help and your ego is bruised.
--
___
users maili
;> kernel-6.11.3-100.fc39.x86_64
> >> kernel-6.11.4-201.fc40.x86_64
> >>
> >> Problem, only the 38 kernel shows in grub.
> >>
> >> How do I get the 40 kernel to show in grub?
> >
> > Let me Google that for you:
> > <https://www.goo
On 10/23/24 21:26, Jeffrey Walton wrote:
On Wed, Oct 23, 2024 at 11:57 PM ToddAndMargo via users
wrote:
$ rpm -qa kernel
kernel-6.5.10-200.fc38.x86_64
kernel-6.11.3-100.fc39.x86_64
kernel-6.11.4-201.fc40.x86_64
Problem, only the 38 kernel shows in grub.
How do I get the 40 kernel to show in
On Wed, Oct 23, 2024 at 11:57 PM ToddAndMargo via users
wrote:
>
> $ rpm -qa kernel
> kernel-6.5.10-200.fc38.x86_64
> kernel-6.11.3-100.fc39.x86_64
> kernel-6.11.4-201.fc40.x86_64
>
> Problem, only the 38 kernel shows in grub.
>
> How do I get the 40 kernel to show i
Hi All,
$ rpm -qa kernel
kernel-6.5.10-200.fc38.x86_64
kernel-6.11.3-100.fc39.x86_64
kernel-6.11.4-201.fc40.x86_64
Problem, only the 38 kernel shows in grub.
How do I get the 40 kernel to show in grub?
Yours in confusion,
-T
--
~~
Computers are like air
On Tue, 2024-07-30 at 14:49 -0700, Samuel Sieb wrote:
> > Tried that and this time it did get the correct UUID in the boot
> > command line (verified from the grub menu). However the boot failed
> > with some 'not found' errors. I can't completely discount the
to come from dracut. I don't even have an
/etc/default/cmdline.
I think I have that because there's a resume.conf in /etc/dracut.d.
It might be getting it from the kernel command line. Try editing the
loader entry, boot it, then run mkconfig again.
Tried that and this time it did get
s from).
>
> It's certainly not going to come from dracut. I don't even have an
> /etc/default/cmdline.
>
I think I have that because there's a resume.conf in /etc/dracut.d.
> It might be getting it from the kernel command line. Try editing the
> loader entry
On 7/30/24 1:51 PM, Patrick O'Callaghan wrote:
On Tue, 2024-07-30 at 13:23 -0700, Samuel Sieb wrote:
On 7/30/24 5:48 AM, Patrick O'Callaghan wrote:
The loader entry is still pointing to the SSD:
# cat /boot/loader/entries/63f58eeb1e8640c79ad45bdc9261a2bb-6.9.11-
200.fc40.x86_64.conf
title Fedo
On Tue, Jul 30, 2024 at 4:21 PM Patrick O'Callaghan
wrote:
> I'd definitely not edit the grub.cfg files directly. They both have a
> commentary saying they are autogenerated. I assume /etc/kernel/cmdline
> is also autogenerated (rpm says it doesn't belong to any package).
The idea is to edit the
On Tue, 2024-07-30 at 13:23 -0700, Samuel Sieb wrote:
> On 7/30/24 5:48 AM, Patrick O'Callaghan wrote:
> > The loader entry is still pointing to the SSD:
> >
> > # cat /boot/loader/entries/63f58eeb1e8640c79ad45bdc9261a2bb-6.9.11-
> > 200.fc40.x86_64.conf
> > title Fedora Linux (6.9.11-200.fc40.x86
On 7/30/24 5:48 AM, Patrick O'Callaghan wrote:
The loader entry is still pointing to the SSD:
# cat
/boot/loader/entries/63f58eeb1e8640c79ad45bdc9261a2bb-6.9.11-200.fc40.x86_64.conf
title Fedora Linux (6.9.11-200.fc40.x86_64) 40 (KDE Plasma)
version 6.9.11-200.fc40.x86_64
linux /vmlinuz-6.9.11-
On Tue, 2024-07-30 at 10:12 -0400, Go Canes wrote:
> On Tue, Jul 30, 2024 at 8:48 AM Patrick O'Callaghan
> wrote:
> > [grub mounting root from wrong device]
> > Not sure what to do other than manually editing the loader entry.
>
> Congrats on progress!
>
> Ma
On Tue, Jul 30, 2024 at 8:48 AM Patrick O'Callaghan
wrote:
> [grub mounting root from wrong device]
> Not sure what to do other than manually editing the loader entry.
Congrats on progress!
Manually editing files is what I have done when needed. Edit
/boot/efi/EFI/fedora/grub.cfg,
To recap: I'm booting from an NVMe drive, and both /boot and/boot/efi
are successfully mounted there.
I'm using BTRFS for root+/home, and have copied them from an existing
SDD drive, which is still physically present.
The system now boots from the NVMe drive, and /home is also there,
*but* root i
On 6/28/24 11:25 AM, Jeffrey Walton wrote:
Another one to avoid: cheap SSDs with duplicate serial numbers. Some
manufacturers repeat (clone?) serial numbers, and when you try to use
them in a RAID configuration, things go badly. A fellow on a Ubuntu
list struggled for months because of it.
That
On 2024-06-28 14:25, Jeffrey Walton wrote:
Another one to avoid: cheap SSDs with duplicate serial numbers. Some
manufacturers repeat (clone?) serial numbers, and when you try to use
them in a RAID configuration, things go badly. A fellow on a Ubuntu
list struggled for months because of it.
At
t; > and then I tried to run
> > grub2-emu
> >
> > I get the list of installed kernels OK, but any choice for boot returns
> >
> > error: ../../grub-core/loader/emu/linux.c:319:cannot find kernel file
> > /vmlinuz-6.9.4-200.fc40.x86_64.
> >
> > an
: ../../grub-core/loader/emu/linux.c:319:cannot find kernel file
/vmlinuz-6.9.4-200.fc40.x86_64.
and the same error for initramfs. Please note the dot at the end of the
line, is it normal?
No matter which kernel I choose, I get the error that kernel file was not
found. All kernel files are in
_configuration_on_UEFI_systems
and then I tried to run
grub2-emu
I get the list of installed kernels OK, but any choice for boot returns
error: ../../grub-core/loader/emu/linux.c:319:cannot find kernel file
/vmlinuz-6.9.4-200.fc40.x86_64.
and the same error for initramfs. Please note the
On Sat, 2024-06-22 at 23:54 -0400, Frank Bures wrote:
> This is what my efibootmgr returns:
>
> root@ryzen:/# efibootmgr
> BootCurrent: 0002
> Timeout: 1 seconds
> BootOrder: 0002,,0001
> Boot Fedora
> HD(1,GPT,e8838c34-c364-4347-afb7-1c516782b114,0x800,0x12c000)/\EFI\FEDORA\SHIMX64.EFI
On 2024-06-22 20:59, Frank Bures wrote:
Hi,
I just did a kernel update and after reboot I ended up in a grub prompt.
I booted from USB F40 and followed instructions at
https://docs.fedoraproject.org/en-US/quick-docs/grub2-bootloader/#_restoring_the_bootloader_using_the_live_disk
However
Hi,
I just did a kernel update and after reboot I ended up in a grub prompt.
I booted from USB F40 and followed instructions at
https://docs.fedoraproject.org/en-US/quick-docs/grub2-bootloader/#_restoring_the_bootloader_using_the_live_disk
However, whatever I did I was not able to
On Mon, Apr 22, 2024 at 8:26 AM Klaus-Peter Schrage via users <
users@lists.fedoraproject.org> wrote:
> [...]
>
I have checked/rechecked three times:
> /boot/efi/EFI/fedora/grub.cfg with flag "--root-dev-only": grub goes to
> prompt, $prefix is obviously not set.
>
that they appear to be the same
(other than the UUID of course), Try editing that out?
I am really stunned now - thank you for this shot in the dark!
I have checked/rechecked three times:
/boot/efi/EFI/fedora/grub.cfg with flag "--root-dev-only": grub goes to
prompt, $prefix is obviousl
Klaus-Peter Schrage composed on 2024-04-21 18:15 (UTC+0200):
...
It really doesn't take much to load a kernel and initrd. All my EFI PCs have
only one Grub installation, even though there are upwards of 12 distros
installed on each PC, no VMs. One of the latest updated hosts this:
menu
1 - 100 of 1324 matches
Mail list logo
