search

ublue-os / bluefin

The next generation Linux workstation, designed for reliability, performance, and sustainability.
https://projectbluefin.io
Apache License 2.0
1.09k stars 149 forks source link

Can't boot to bluefin-dx-nvidia, grub out of memory #1721

Open weavermarquez opened 1 day ago

weavermarquez commented 1 day ago

Describe the bug

For a few months now, I've been unable to boot to the updated bluefin-dx-nvidia:gts images I pull because of a grub memory error. error: grub-core/kern/mm.c:552 out of memory

What did you expect to happen?

Expected the system to boot to most recent bluefin-dx-nvidia:gts, and not be presented with an error message.

Output of rpm-ostree status

❯ rpm-ostree status
State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx:gts
                   Digest: sha256:aa967fd72c30d00a53a2ae40a6d4d048b17f1bc617b284d7bf2ef53681de024f
                  Version: 39.20240921.0 (2024-09-22T05:54:05Z)
             InitramfsEtc: /etc/vconsole.conf

  ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx-nvidia:gts
                   Digest: sha256:8af7cca62464ae8fcc2a762a6f6f15c3694914a44cc40d287fc1603817cdef6a
                  Version: 39.20240804.0 (2024-08-04T05:54:01Z)
             InitramfsEtc: /etc/vconsole.conf
                   Pinned: yes

Output of groups

kwalerie wheel dialout lxd incus-admin libvirt docker

Extra information or context

Specs:

This system was rebased from a vanilla Silverblue installation.

Reproduce:

  1. Have a version of bluefin-dx-nvidia:gts later than 20240804.
  2. Boot into it.
  3. Upon attempting to boot: error: grub-core/kern/mm.c:552 out of memory

Attempted Workarounds:

  1. I recently tried fiddling in the Advanced BIOS, but this did not fix the problem.
  2. I rebased to bluefin-dx:gts, and I was able to boot to an upgraded version like 39.20240921.0 I will stick with this for now.

Similar Discussions

weavermarquez commented 1 day ago

Note: I mention "for a few months" as this issue has occurred twice, though I forgot to file a bug report last time.

The first time was sometime around July to August, not sure. I don't remember how it resolved. However, booting to 39.20240804.0 worked, so I was able to switch to that updated image and discard the previous pinned image.