Github messages for voidlinux
 help / color / mirror / Atom feed
From: basploeger <basploeger@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Missing initrd line in grub.cfg after updating kernels
Date: Tue, 14 Feb 2023 22:04:37 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42266@inbox.vuxu.org> (raw)

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

New issue by basploeger on void-packages repository

https://github.com/void-linux/void-packages/issues/42266

Description:
### Is this a new report?

Yes

### System Info

Void 6.1.4_1 x86_64 GenuineIntel notuptodate rrFFF

### Package(s) Affected

linux6.1 linux5.15

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

Every menuentry in `/boot/grub/grub.cfg` contains lines of the form:
```
  echo  'Loading initial ramdisk ...'
  initrd  /boot/initramfs-${VERSION}.img
```

### Actual behaviour

For the newly installed kernel versions, the above lines are missing from the `menuentry` in `/boot/grub/grub.cfg`. This makes the new kernels unbootable. I have to restart the machine and pick an older kernel that was previously installed.

Running `update-grub` fixes the problem. The `initrd` lines then are added to all menuentrys  in `/boot/grub/grub.cfg`.

### Steps to reproduce

Pre-conditions (not sure which are actually relevant, but they might all be):

1. I have installed both `linux` and `linux-lts` packages.
2. I have also installed package `zfs` (DKMS module).
3. Both packages mentioned under #1 are out of date.

Steps to reproduce:

1. Run `sudo xbps-install -Su`

             reply	other threads:[~2023-02-14 21:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-14 21:04 basploeger [this message]
2023-08-16  4:01 ` ChesterJFGould

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42266@inbox.vuxu.org \
    --to=basploeger@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).