Nvidia drivers not loading with HeliumOS images built via CI #1

Open
opened 2024年09月22日 21:47:46 +02:00 by imbev · 0 comments
Owner
Copy link

bootc images can be built by podman locally or via CI such as GitHub Actions. When building the Nvidia image locally, official Nvidia dkms drivers load and operate properly on systems booting the image. When building the Nvidia image using GitHub Actions, the booted system does not use the official Nvidia drivers nor the blacklisted Nouveau drivers.

Steps to reproduce:

  1. Build 9/Containerfile.nvidia using podman on a local device as image A
  2. Push image A to registry
  3. Switch bootc system to image A
  4. Observe system using Nvidia drivers properly
  5. Build 9/Containerfile.nvidia using podman on GitHub Actions as image B
  6. Push image B to registry
  7. Switch bootc system to image B
  8. Observe system using fallback graphics drivers

Reference:

  • Local build
    • image: quay.io/imbev/heliumos-bootc:nvidia
    • commit: 6fc99100dee6d5558f3ac17b610b15f90f4c90e7
    • Output of lsmod | grep nvidia:
nvidia_drm ... ...
nvidia_modeset ... ...
nvidia_uvm ... ...
video ... ...
drm_kms_helper ... ...
drm ... ...
  • CI build
    • image: quay.io/heliumos/bootc:9-canary-nvidia
    • commit: 6fc99100dee6d5558f3ac17b610b15f90f4c90e7
    • Output of lsmod | grep nvidia: (Nothing)
bootc images can be built by podman locally or via CI such as GitHub Actions. When building the Nvidia image locally, official Nvidia dkms drivers load and operate properly on systems booting the image. When building the Nvidia image using GitHub Actions, the booted system does not use the official Nvidia drivers nor the blacklisted Nouveau drivers. Steps to reproduce: 1. Build `9/Containerfile.nvidia` using podman on a **local device** as image A 2. Push image A to registry 3. Switch bootc system to image A 4. Observe system **using Nvidia drivers** properly 5. Build `9/Containerfile.nvidia` using podman on **GitHub Actions** as image B 6. Push image B to registry 7. Switch bootc system to image B 8. Observe system **using fallback graphics drivers** Reference: - Local build - image: `quay.io/imbev/heliumos-bootc:nvidia` - commit: `6fc99100dee6d5558f3ac17b610b15f90f4c90e7` - Output of `lsmod | grep nvidia`: ``` nvidia_drm ... ... nvidia_modeset ... ... nvidia_uvm ... ... video ... ... drm_kms_helper ... ... drm ... ... ``` - CI build - image: `quay.io/heliumos/bootc:9-canary-nvidia` - commit: `6fc99100dee6d5558f3ac17b610b15f90f4c90e7` - Output of `lsmod | grep nvidia`: (Nothing)
Sign in to join this conversation.
No Branch/Tag specified
No results found.
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
HeliumOS/bugs#1
Reference in a new issue
HeliumOS/bugs
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?