On 30/06/2022 20:11, Guillermo wrote:

[screenshot]

Doesn't "emerge -a --depclean" remove all these old kernels?

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Thursday, 30 June 2022 19:15:33 BST Guillermo wrote:

Hello,

I still have the same problem, but the command worked fine.

The command "emerge -a --depclean" will only remove uninstall the kernel packages, but will not remove files from /usr/src/, or old kernel images and files from /boot/.

Your /boot partition is full with old kernels you probably no longer use or need. You have to remove them manually as part of your regular maintenance of your installation, or you can install and use 'app-admin/eclean-kernel' as mentioned in the previous thread, to partly automate the cleanup process of stale kernels. Then update your GRUB to refresh the boot menu.


-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmK96gcACgkQseqq9sKV ZxnRvA//RbzYPyskbco7jjZJxIPJWS6ROmZpLvSTs66pQ/6nS3wxXBKKSw+rmHmf vPkx1NePEXNJmqWIWUKMe7y5x+38lp537rfCf1bOpA54QJD9ImnAtl00NaMyXfjh tlM8TPFYdi2TfhwnYN7fj3sxZLXp+CPsCpKFWKiG+I5Hb8dncMXvGmecjLlney/0 d7qoUoMk7cjo9GKtgwbvOi413QCGtxPJc5Ps47Nf+ozaWIp77ut8t7MZguAko0KL sizLwUtazI04aie5bGZ95cMLU4KPRwi+nDLMaXGfQoac0QNynJJ0if6Gm5YoambW 2fOVXvnp6b33KIprxnaohmlEsYgjEa0NUeSrRS2dDcPw6J/Vp9hvbqRgBnwrKwJv ZT6glxClE1gyYQqIlWMbHDHdRXHgdFisXiuFCsHecI+sk6/IXKPpxXnRCGecNdBr dVMq1iY0EvcJ+agDv29lKMqs2L+sTSu2oqnGka51Dmu1qEJFkkR0rdRRNAJ16+yF M8EawrXIeVV58H90hlRU4kXyPBfwYc1U6/Bkx737/cAitY0o5HiHDPSOBoLU9ehP O7NtYjw3N8//0r2+HjEI4JUwrOdTXzmWZITJGrrmOm7TC8EI0I3noMZOee8y8ZXB kL50Qu9G6lvKjOkxTxR51dRIWtssWmCqG68UbvPS+WBd1dIYsbo=
=B9kN
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hello,

I still have the same problem, but the command worked fine.

On 30/06/2022 19:24, Nikos Chantziaras wrote:

On 30/06/2022 20:11, Guillermo wrote:

[screenshot]

Doesn't "emerge -a --depclean" remove all these old kernels?

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 30/06/2022 19:23, Michael wrote:

On Thursday, 30 June 2022 19:15:33 BST Guillermo wrote:

Hello,

I still have the same problem, but the command worked fine.

The command "emerge -a --depclean" will only remove uninstall the kernel packages, but will not remove files from/usr/src/, or old kernel images and files from/boot/.

As far as I'm aware, depclean only installs files it installed, so it
leaves quite a lot of garbage lying around from kernels, including the /usr/src/kernel-xx-xx-xx directory and various files involved in making
your kernel, that you've modified.

Cheers,
Wol

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

The OP should read the section of the Gentoo manual on kernel install to
learn what files are installed where. Yea, but just rm the kernels and initramfs's from /boot and you're golden. FWIW, I usually only upgrade my kernel when it's a major revision.

On Thu, Jun 30, 2022 at 12:39 PM Wols Lists <[email protected]>
wrote:

On 30/06/2022 19:23, Michael wrote:

On Thursday, 30 June 2022 19:15:33 BST Guillermo wrote:

Hello,

I still have the same problem, but the command worked fine.

The command "emerge -a --depclean" will only remove uninstall the kernel packages, but will not remove files from/usr/src/, or old kernel images

and

files from/boot/.

As far as I'm aware, depclean only installs files it installed, so it
leaves quite a lot of garbage lying around from kernels, including the /usr/src/kernel-xx-xx-xx directory and various files involved in making
your kernel, that you've modified.

Cheers,
Wol

--
Lee 😎
<[email protected]>

<div dir="ltr">The OP should read the section of the Gentoo manual on kernel install to learn what files are installed where. Yea, but just rm the kernels and initramfs&#39;s from /boot and you&#39;re golden. FWIW, I usually only upgrade my kernel when
it&#39;s a major revision.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jun 30, 2022 at 12:39 PM Wols Lists &lt;<a href="mailto:[email protected]">[email protected]</a>&gt; wrote:<br></div><blockquote class="
gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 30/06/2022 19:23, Michael wrote:<br>
&gt; On Thursday, 30 June 2022 19:15:33 BST Guillermo wrote:<br>
&gt;&gt; Hello,<br>
&gt;&gt;<br>
&gt;&gt; I still have the same problem, but the command worked fine.<br>
&gt; The command &quot;emerge -a --depclean&quot; will only remove uninstall the kernel<br>
&gt; packages, but will not remove files from/usr/src/, or old ker

This is a multi-part message in MIME format.
and don't forget to run "uname -a" to get your currently running kernel
version and make sure you don't delete that!

"IF" "uname -a" isn't the latest version you have in /boot, some more investigation as to why will be needed.

BillK


On 1/7/22 04:29, Lee wrote:

The OP should read the section of the Gentoo manual on kernel install
to learn what files are installed where. Yea, but just rm the kernels
and initramfs's from /boot and you're golden. FWIW, I usually only
upgrade my kernel when it's a major revision.

On Thu, Jun 30, 2022 at 12:39 PM Wols Lists <[email protected]>
wrote:

On 30/06/2022 19:23, Michael wrote:
> On Thursday, 30 June 2022 19:15:33 BST Guillermo wrote:
>> Hello,
>>
>> I still have the same problem, but the command worked fine.
> The command "emerge -a --depclean" will only remove uninstall
the kernel
> packages, but will not remove files from/usr/src/, or old kernel
images and
> files from/boot/.

As far as I'm aware, depclean only installs files it installed, so it
leaves quite a lot of garbage lying around from kernels, including
the
/usr/src/kernel-xx-xx-xx directory and various files involved in
making
your kernel, that you've modified.

Cheers,
Wol

--
Lee 😎 
<[email protected]>

<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>and don't forget to run "uname -a" to get your currently running
kernel version and make sure you don't delete that!</p>
<p>"IF" "uname -a" isn't the latest version you have in /boot, some
more investigation as to why will be needed.<br>
</p>
<p>BillK</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 1/7/22 04:29, Lee wrote:<br>
</div>
<blockquote type="cite" cite="mid:CABpw4G87Q7xvM9wH+qTz1ZuDrVoQxvXtJNWNyT+AH=[email protected]">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">The OP should read the section of the Gentoo manual
on kernel install to learn what files are installed where. Yea,
but just rm the kernels and initramfs's from /boot and you're
golden. FWIW, I usually only upgrade my kernel when it's a major
revision.</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Jun 30, 2022 at 12:39
PM Wols Lists &lt;<a href="mailto:[email protected]"
moz-do-not-send="true" class="moz-txt-link-freetext">[email protected]</a>&gt;
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On
30/06/2022 19:23, Michael wrote:<br>
&gt; On Thursday, 30 June 2022 19:15:33 BST Guillermo wrote:<br>
&gt;&gt; Hello,<br>
&gt;&gt;<br>
&gt;&gt; I still have the same problem, but the command worked
fine.<br>
&gt; The command "emerge -a --depclean" will only remove
uninstall the kernel<br>
&gt; packages, but will not remove files from/usr/src/, or old
kernel images and<br>
&gt; files from/boot/.<br>
<br>
As far as I'm aware, depclean only installs files it
installed, so it <br>
leaves quite a lot of garbage lying around from kernels,
including the <br>
/usr/src/kernel-xx-xx-xx directory and various files involved
in making <br>
your kernel, that you've modified.<br>
<br>
Cheers,<br>
Wol<br>
<br>
</blockquote>
</div>
<br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr" class="gmail_signature">
<div dir="ltr">
<div><font face="comic sans ms, sans-serif">Lee</font> 😎 </div>
<div>&lt;<a href="mailto:[email protected]" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">[email protected]</a>&gt;</div>
</div>
</div>
</blockquote>
</body>
</html>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

William Kenworthy wrote:

and don't forget to run "uname -a" to get your currently running
kernel version and make sure you don't delete that!

"IF" "uname -a" isn't the latest version you have in /boot, some more investigation as to why will be needed.

BillK

Just to add another method.  I have uprecords installed here.  It lists
the kernels and their uptime.  I keep the last two with reasonably high uptimes with fairly recent version and the most recent kernel.  I don't upgrade automatically so I control what and when I update.  Of course, I
also have long uptimes as well.  My thinking on this.  I want kernels
that are known to be stable that I can use as a backup boot option but I
also want newer kernels that have fixes etc in them.  By keeping a
couple with long uptimes, I get stable kernels.  By also picking a
recent kernel version, I get a kernel that I can boot into to see if it
is stable.  Over time, the versions get higher on both parts.  When I do
my checks, I look for kernels with at least 30 days or more of uptime.  Generally, if a kernel can run that length of time, it is pretty
stable.  That said, I have some with many months of uptime.

When I upgrade to a new kernel, I run for a month or so and then
manually clean out /boot, that would include kernel, init thingy,
System.map and config files. 

Seeing this reminds me it might be a good time to look into updating,
even tho I might not reboot for a while yet. 

Just a thought. 

Dale

:-)  :-) 

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 01/07/2022 00:21, Dale wrote:

When I upgrade to a new kernel, I run for a month or so and then
manually clean out /boot, that would include kernel, init thingy,
System.map and config files.

Seeing this reminds me it might be a good time to look into updating,
even tho I might not reboot for a while yet.

When I update, I wait until I'm happy the new one seems okay, and then I
just leave the most recent one and the one before.

That said, I need to upgrade, and I need to see if my random hangs are
fixed (there's apparently a bug in the Ryzen 3000, and I'm guessing
that's what I'm hitting).

Cheers,
Wol

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Wols Lists wrote:

On 01/07/2022 00:21, Dale wrote:

When I upgrade to a new kernel, I run for a month or so and then
manually clean out /boot, that would include kernel, init thingy,
System.map and config files.

Seeing this reminds me it might be a good time to look into updating,
even tho I might not reboot for a while yet.

When I update, I wait until I'm happy the new one seems okay, and then
I just leave the most recent one and the one before.

That said, I need to upgrade, and I need to see if my random hangs are
fixed (there's apparently a bug in the Ryzen 3000, and I'm guessing
that's what I'm hitting).

Cheers,
Wol

After my previous reply, I updated to a newer kernel.  It's in /boot but
it may be months before I reboot.  Anyway, I currently have four kernels
in /boot.  My current running kernel and two backup kernels plus the new untested one.  Whenever I get around to rebooting and the new kernel
works fine, I'll remove the oldest one including sources etc. 

I try to keep at least two backup kernels.  One reason I do that, the
init thingy.  I admit dracut is working well for me but given the
history I have with those thingys, I want extra protection.  The odds of
three boot options going bad are pretty slim and if it did happen, I
likely have a serious hard drive problem anyway, file system at the very least.  Either way, I have a lot to worry about. 

Maybe one of the suggestions mentioned here will help the OP.  It seems
he is letting the updater do the install or something and the kernel is
a fast moving target.  One has to have some way, automated or manual, to
clean up the unneeded bits.  I doubt most anyone makes their /boot to
large anyway.  Usually 300 or 400MBs is enough. 

Dale

:-)  :-) 

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)