Computer going to GNU GRUB on boot

[PerseusKane]

Hey! I just recently upgraded to Kubuntu 18.10 and, upon my first boot, I was introduced to the GNU GRUB screen. After some searching around, I was able to find out how to actually boot up my computer. After doing all of this, a question popped up in my head. Why isn't GRUB autofinding my Vmlinuz and Initrd files?

I was wondering if there was a way to make GNU GRUB actually use its config file, since several runs of update-grub seems to not have changed anything. While this issue isn't exactly breaking, I find it rather annoying to constantly have to use

set root=(hd0,gpt2)
ls (hd0,gpt2)/
linux /./vmlinuz-4.15.0-24-generic
initrd /./initrd-4.15.0-24-generic
boot

Whenever I want to work on my college work or browse the internet after having my computer turned off.

I hope that this problem gets resolved.
Thanks!
~Perseus Kane

[claydoh]

It is a temporary artifact of running a super-early, un-baked, unfinished, in-progress, barely begun, pre-release version of Kubuntu Upgrading is not advised at this early stage as the upgrade process has is likely not in a usable state at the moment, not until the system has settled into a more stable state. This won't likely be until later Alpha releases, or even into the Betas.

[PerseusKane]

Ah, thank you for the clarification. For a raw, unprocessed version of the OS, I find it to be pretty stable. Haven't had any issues at all except for the whole booting thing. I appreciate the quick response, as it had really cleared things up.

[claydoh]

https://www.kubuntuforums.net/showth...elease-caveats

[jlittle]

Claydoh's answer is generally correct. But, to answer directly...

update-grub just generates a new /boot/grub/grub.cfg. Your problem appears to be the grub boot is not finding it; grub-install is needed, and you need to know what device the computer is using to boot. The details are different between BIOS and UEFI booting.

As well, those hard to type lines can be simplified. They could be:

linux /vmlinux
initrd /initrd.img

Kubuntu (and all debian, APT, distros I imagine) maintains /vmlinux and /initrd.img symbolic links to the latest ones.

Now, if you're installing Cosmic , I'd expect that you're experimenting and have at least another more stable install, that you'd like to boot into at least some of the time to get stuff done. Why not let grub in that install control the boot? For many years now, drives are big enough to have several installs, so keeping, say, an Kubuntu LTS available might give options when troubles occur. And if you're experimenting with several installs like that, a dedicated grub partition or btrfs subvolume not controlled by any install and hand-maintained by you will, IMO, save time and bother in the long run. It certainly has for me in the past.