-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Grub "error: out of memory" with nvidia extensions #272
Comments
The following schema (
|
@mdallaire could you try this installer image: |
I don't have access to the image: |
sory, should be fixed now |
That installation image with the new grub version works perfectly on my machine now. |
cool, i'll get this tested with another setup also |
This reverts commit 70919d8. Newer grub has issues with loading from XFS filesystems. See siderolabs/talos#8023, and the fix in `70919d82` cannot be backported to older version. So the safe option is to revert while siderolabs/extensions#272 remains open.
This reverts commit 70919d8. Newer grub has issues with loading from XFS filesystems. See siderolabs/talos#8023, and the fix in `70919d82` cannot be backported to older version. So the safe option is to revert while siderolabs/extensions#272 remains open. Signed-off-by: Noel Georgi <git@frezbo.dev>
Re-opening since new grub has other bugs |
Talos 1.7 should have grub 2.12 |
Talos v1.5.5
nonfree-kmod-nvidia:535.54.03-v1.5.5
nvidia-container-toolkit:535.54.03-v1.13.5
Hardware: NUC11PHKi7CAA (UEFI boot)
64g RAM
After performing the initial installation with the vanilla metal-amd64.iso I apply the configuration with the nvidia extensions and kernel modules. All of which work well. When I perform a reboot with the
-m powercycle
option the machine won't boot with the following error:Discussing with frezbo he mentionned this grub issue as a possible cause : https://bugs.launchpad.net/oem-priority/+bug/1842320
I performed other tests in proxmox running on the same hardware model by switching between UEFI and BIOS on VMs with the NVIDIA card in PCI passthrough but I was not able to reproduce the issue.
The text was updated successfully, but these errors were encountered: