On 12/6/23 9:01 AM, Robert McBroom via users wrote:
On 12/5/23 17:54, home user wrote:
menuentry 'Windows 7 (on /dev/sda2)' --class windows --class os
be the culprit? If yes, what's the correct way to get that permanently out?
Yes, and same answer as the previous.
--
Here we go...
-
On 12/5/23 17:54, home user wrote:
menuentry 'Windows 7 (on /dev/sda2)' --class windows --class os
be the culprit? If yes, what's the correct way to get that
permanently out?
Yes, and same answer as the previous.
--
Here we go...
-
-bash.2[~]: grub2-mkconfig -o /boot/grub2/grub.cfg
On 12/5/23 3:16 PM, Samuel Sieb wrote:
On 12/5/23 13:58, home user wrote:
On 12/5/23 2:24 PM, Samuel Sieb wrote:
On 12/5/23 10:06, home user wrote:
The memory test entry listed by that command is the grub menu entry that I want
to keep, not the one that I want to delete. That directory has n
On 12/5/23 13:58, home user wrote:
On 12/5/23 2:24 PM, Samuel Sieb wrote:
On 12/5/23 10:06, home user wrote:
The memory test entry listed by that command is the grub menu entry
that I want to keep, not the one that I want to delete. That
directory has no entry corresponding to what I want to
On 12/5/23 2:24 PM, Samuel Sieb wrote:
On 12/5/23 10:06, home user wrote:
The memory test entry listed by that command is the grub menu entry that I want
to keep, not the one that I want to delete. That directory has no entry
corresponding to what I want to delete.
Check in the /etc/grub2.c
On 12/5/23 10:06, home user wrote:
The memory test entry listed by that command is the grub menu entry that
I want to keep, not the one that I want to delete. That directory has
no entry corresponding to what I want to delete.
Check in the /etc/grub2.cfg file and see if something added it dir
On 12/5/23 10:59 AM, Doug H. wrote:
On Tue, Dec 5, 2023, at 8:53 AM, home user wrote:
On 12/2/23 1:39 PM, home user wrote:
I have not seen anything further about this.
So let's move on to the memory test part of this thread.
/boot/ has one memory test entry:
-rw-r--r--. 1 root root 144344
On Tue, Dec 5, 2023, at 8:53 AM, home user wrote:
> On 12/2/23 1:39 PM, home user wrote:
>
> I have not seen anything further about this.
>
>> So let's move on to the memory test part of this thread.
>>
>> /boot/ has one memory test entry:
>> -rw-r--r--. 1 root root 144344 Aug 3 18:00 memtest8
On 12/2/23 1:39 PM, home user wrote:
I have not seen anything further about this.
So let's move on to the memory test part of this thread.
/boot/ has one memory test entry:
-rw-r--r--. 1 root root 144344 Aug 3 18:00 memtest86+x64.bin
/boot/loader/entries/ has one memory test entry:
-rw-r-
> On 12/1/23 17:23, old sixpack13 wrote:
>
> Not quite.
Hrmph ...
;-)
--
___
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.o
On 12/2/23 15:14, Andras Simon wrote:
Why not remove just kernel-core? dnf will take care of the dependent
packages (kernel-modules and the rest).
Removing kernel-core totally makes sense.
Thomas
--
___
users mailing list -- users@lists.fedoraproject
2023-12-02 18:04 UTC+01:00, Thomas Cameron via users
:
> Here's what I do. It's on RHEL, but the process is the same for Fedora.
>
> First, find all kernels which are installed.The last one is the latest,
> so we ignore that one.
>
> --
> [root@neuromancer ~]# rpm -q
Resuming from last night...
The extra old kernels have been removed from the grub menu. Corresponding
files have been removed from
/boot/
/boot/loader/entries/
Thomas, your post came after I did the above, and I did the above using the
"rm" command. Maybe the time to re-address your suggesti
Here's what I do. It's on RHEL, but the process is the same for Fedora.
First, find all kernels which are installed.The last one is the latest,
so we ignore that one.
--
[root@neuromancer ~]# rpm -qa kernel | sort
kernel-5.14.0-284.25.1.el9_2.x86_64
kernel-5.14.
On Fri, Dec 1, 2023 at 5:42 PM home user wrote:
>
> On 12/1/23 3:36 PM, Joe Zeff wrote:
> > On 12/01/2023 03:25 PM, home user wrote:
> >> The rpm command did not give me enough information, so I had to do the
> >> reboot.
> >
> > You could always look in /boot and see what's there.
> > --
> That
On 12/1/23 9:30 PM, Samuel Sieb wrote:
On 12/1/23 20:23, home user wrote:
On 12/1/23 8:38 PM, Samuel Sieb wrote:
Remove the files for the entry that doesn't have a kernel package.
Here's what I did:
-
-bash.1[~]: cd /boot/loader/entries/
-bash.2[entries]: ls
70857e3fb05849139515e66a3fdc6b
On 12/1/23 20:23, home user wrote:
On 12/1/23 8:38 PM, Samuel Sieb wrote:
Remove the files for the entry that doesn't have a kernel package.
Here's what I did:
-
-bash.1[~]: cd /boot/loader/entries/
-bash.2[entries]: ls
70857e3fb05849139515e66a3fdc6b38-0-memtest86+.conf
70857e3fb0584913951
On 12/1/23 8:38 PM, Samuel Sieb wrote:
On 12/1/23 18:46, home user wrote:
On 12/1/23 6:44 PM, Samuel Sieb wrote:
You mentioned in a previous email that there was a rescue kernel. That one
isn't tracked by any package. You can delete the files and the next kernel
install will update it with t
On 12/1/23 18:46, home user wrote:
On 12/1/23 6:44 PM, Samuel Sieb wrote:
You mentioned in a previous email that there was a rescue kernel.
That one isn't tracked by any package. You can delete the files and
the next kernel install will update it with the latest kernel.
The rescue kernel is
On 12/1/23 6:44 PM, Samuel Sieb wrote:
On 12/1/23 16:50, home user wrote:
Using the wrong version in the "dnf remove" may have caused more problems:
-
bash.1[~]: dnf remove kernel-core-6.5.8-200.fc38.x86_64
No match for argument: kernel-core-6.5.8-200.fc38.x86_64
You mentioned in a previou
On 12/1/23 17:23, old sixpack13 wrote:
...
What is the current, simple, best practice f38 way of removing the oldest
kernel, both
from the hard drive and from the grub menu?
What is the current, simple, best practice, f38 way of removing the oldest
memtest, both
from the hard drive (if it's
On 12/1/23 16:50, home user wrote:
Using the wrong version in the "dnf remove" may have caused more problems:
-
bash.1[~]: dnf remove kernel-core-6.5.8-200.fc38.x86_64
No match for argument: kernel-core-6.5.8-200.fc38.x86_64
You mentioned in a previous email that there was a rescue kernel.
>
> I'm no sys.admin.
tomorrow you *are* the sys.admin !
;-)
--
___
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-U
...
>
> What is the current, simple, best practice f38 way of removing the oldest
> kernel, both
> from the hard drive and from the grub menu?
>
> What is the current, simple, best practice, f38 way of removing the oldest
> memtest, both
> from the hard drive (if it's there) and from the grub m
On 12/1/23 16:41, Samuel Sieb wrote:
On 12/1/23 14:25, home user wrote:
The rpm command did not give me enough information, so I had to do the
reboot. The grub menu shows 4 kernels and 2 memtests (manually typed):
How did it not give you enough information? What were you looking for?
I was
On 12/1/23 14:25, home user wrote:
The rpm command did not give me enough information, so I had to do the
reboot. The grub menu shows 4 kernels and 2 memtests (manually typed):
How did it not give you enough information? What were you looking for?
Fedora Linux (6.6.2-101.fc38.x86_64...
Fedo
On 12/1/23 3:36 PM, Joe Zeff wrote:
On 12/01/2023 03:25 PM, home user wrote:
The rpm command did not give me enough information, so I had to do the reboot.
You could always look in /boot and see what's there.
--
That was a part of that same post. Here it is again:
--
bash.1[~]: ls /boot
On 12/01/2023 03:25 PM, home user wrote:
The rpm command did not give me enough information, so I had to do the
reboot.
You could always look in /boot and see what's there.
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send
On 12/1/23 11:53, Patrick O'Callaghan wrote:
On Fri, 2023-12-01 at 10:28 -0700, home user wrote:
On 12/1/23 10:06 AM, Tim via users wrote:
On Fri, 2023-12-01 at 09:11 -0700, home user wrote:
What is the current, simple, best practice, f38 way of removing
the
oldest memtest, both from the hard
On Fri, Dec 1, 2023 at 11:12 AM home user wrote:
>
> Good morning,
>
> After yesterday's weekly patches via "dnf upgrade", I have more old kernels
> than I want. I also have 2 memtest entries in the grub menu.
>
> What is the current, simple, best practice f38 way of removing the oldest
> kerne
On 12/01/2023 11:53 AM, Patrick O'Callaghan wrote:
'rpm -qa kernel' will list all the installed kernels. The one to be
deleted on the next dnf update will be the oldest.
Fedora once supplied a program to remove all kernels except the running
one and the newest. It's rather old (2011) but shou
On Fri, 2023-12-01 at 10:28 -0700, home user wrote:
> On 12/1/23 10:06 AM, Tim via users wrote:
> > On Fri, 2023-12-01 at 09:11 -0700, home user wrote:
> > > What is the current, simple, best practice, f38 way of removing
> > > the
> > > oldest memtest, both from the hard drive (if it's there) and
On 12/1/23 10:06 AM, Tim via users wrote:
On Fri, 2023-12-01 at 09:11 -0700, home user wrote:
What is the current, simple, best practice, f38 way of removing the
oldest memtest, both from the hard drive (if it's there) and from
the grub menu?
It *ought* to be as simple as
dnf remove kernel...
On Fri, 2023-12-01 at 09:11 -0700, home user wrote:
> What is the current, simple, best practice, f38 way of removing the
> oldest memtest, both from the hard drive (if it's there) and from
> the grub menu?
It *ought* to be as simple as
dnf remove kernel.
Where you use a specific kernel pack
Good morning,
After yesterday's weekly patches via "dnf upgrade", I have more old kernels
than I want. I also have 2 memtest entries in the grub menu.
What is the current, simple, best practice f38 way of removing the oldest
kernel, both from the hard drive and from the grub menu?
What is th
35 matches
Mail list logo
