All of lore.kernel.org
 help / color / mirror / Atom feed
* grub config does not match kernel image name after apt upgrade
@ 2022-05-26  8:50 Daniel Squires
  2022-05-26  9:32 ` [poky] " Richard Purdie
  0 siblings, 1 reply; 2+ messages in thread
From: Daniel Squires @ 2022-05-26  8:50 UTC (permalink / raw)
  To: poky

[-- Attachment #1: Type: text/plain, Size: 910 bytes --]

In our custom x86 image, it runs fine after initial deploy, but if we then apt update && apt upgrade and receive a new kernel the installed kernel name does not match that in the grub configuration and thus boot fails if not manually corrected. I don't know if this is a mis-configuration in our build or a bug upstream. any ideas?

yocto:~$ cat /boot/EFI/BOOT/grub.cfg
serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1
default=boot
timeout=5
menuentry 'boot'{
linux /bzImage root=PARTUUID=52cb2dd8-ef93-4f4a-8135-1e3326f181ac rootwait rootfstype=ext4 console=ttyS0,115200 console=tty0
}

yocto:/boot$ ls -lht
-rwxr-xr-x    1 root     root        9.1M Apr 28 13:26 bzImage-5.15.36-yocto-standard
-rwxr-xr-x    1 root     root        9.1M Feb 15 14:19 bzImage-5.15.22-yocto-standard
drwxr-xr-x    3 root     root        2.0K Apr  5  2011 EFI

[-- Attachment #2: Type: text/html, Size: 1416 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [poky] grub config does not match kernel image name after apt upgrade
  2022-05-26  8:50 grub config does not match kernel image name after apt upgrade Daniel Squires
@ 2022-05-26  9:32 ` Richard Purdie
  0 siblings, 0 replies; 2+ messages in thread
From: Richard Purdie @ 2022-05-26  9:32 UTC (permalink / raw)
  To: Daniel Squires, poky

On Thu, 2022-05-26 at 01:50 -0700, Daniel Squires wrote:
> In our custom x86 image, it runs fine after initial deploy, but if we
> then apt update && apt upgrade and receive a new kernel the installed
> kernel name does not match that in the grub configuration and thus
> boot fails if not manually corrected. I don't know if this is a mis-
> configuration in our build or a bug upstream. any ideas?
> 
> yocto:~$ cat /boot/EFI/BOOT/grub.cfg  
> serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1 
> default=boot 
> timeout=5 
> menuentry 'boot'{ 
> linux /bzImage root=PARTUUID=52cb2dd8-ef93-4f4a-8135-1e3326f181ac
> rootwait rootfstype=ext4 console=ttyS0,115200 console=tty0 
> }
> 
> yocto:/boot$ ls -lht 
> -rwxr-xr-x    1 root     root        9.1M Apr 28 13:26 bzImage-
> 5.15.36-yocto-standard 
> -rwxr-xr-x    1 root     root        9.1M Feb 15 14:19 bzImage-
> 5.15.22-yocto-standard 
> drwxr-xr-x    3 root     root        2.0K Apr  5  2011 EFI

On target package upgrades are a best effort sitution and not something
we directly test. THe kernel in particular is tricky as everyone
configured and uses it differently, it varies even by image type. It
sounds like you don't have any configuration in the kernel packages to
adapt to your boot situation and allow them to upgrade grub so that is
the piece you'd need to add. We'd welcome contributions back if it can
be done in a generic way.

Cheers,

Richard

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2022-05-26  9:32 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-05-26  8:50 grub config does not match kernel image name after apt upgrade Daniel Squires
2022-05-26  9:32 ` [poky] " Richard Purdie

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.