[SOLVED] can't find an initial ram disk I can handle error msg

[Member stevesr0]

Hi,

I was able to update the kernel on a liveUSB I was using. However, subsequently, both on liveUSBs, a frugal install and now a “regular” install, I get an error that “I can’t find an initial ram disk that I can handle.” With this mesaage, the additional kernels didn’t show up when I used the live kernel updater and I haven’t tried to use these on the regular install yet.

I have searched on the internet and haven’t found an explanation of what this means and how to fix.

Appreciate any thoughts comments, advice, recommendations for dealing with this.

thanks in advance.

stevesr0

• This topic was modified 4 years, 10 months ago by stevesr0.

[Forum Admin anticapitalista]

Helpful

Up

0

::

Which kernel did you update to?

Try running in a root terminal,

update-initramfs -k all -u -t

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member stevesr0]

Helpful

Up

0

::

Hi anticapitalista,

I did that and it generated a new initram, without any message about cannot find an init ramdisk that I can’t handle.

I then rebooted and the newer kernel is being used.

Thanks, much.

Can that error message on installing a new kernel (“can’t find an init ramdisk I can handle”) be ignored, or is it necessary to then run the update-initramfs command?

stevesr0

[Forum Admin anticapitalista]

Helpful

Up

0

::

I sometimes get that message with no ill-effect.
But, it is probably best to run update-initramfs -k all -u -t
to be sure.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member stevesr0]

Helpful

Up

0

::

Well that seemed to work – at the next boot, there was the new kernel.

However, I have now added another kernel (4.16.13) and got the same message. This time, I just rebooted and the new kernel was there.

(Unfortunately, with this kernel, my boot time INCREASED dramatically from about 75 s to 180 s. So, I am not planning to use it.

(Hmm, could the failure to generate an initramfs with that command cause the time to be so high. I will repeat the generate initramfs command and reboot with that kernel to test that.)

stevesr0

[Author]

Posts