this post was submitted on 12 Jan 2026
18 points (100.0% liked)

Selfhosted

54450 readers
1304 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Sup. I have proxmox configured to start a Jellyfin LXC whenever the host (re)starts. However, the /dev/nvidia* devices do not appear until I manually run nvidia-smi (probably anything nvidia* would would work) on the host, so the autostart is failing. Any ideas why I would need to run something likenvidia-smi first to get/dev/nvidia* devices to show up?

top 2 comments
sorted by: hot top controversial new old
[–] Shadow@lemmy.ca 4 points 6 hours ago

Check lsmod and see if the kernel modules are loaded. Nvidia smi is probably loading them for you on first run.

[–] kumi@feddit.online 3 points 6 hours ago* (last edited 6 hours ago)

Nope but I guess a workaround would be to make a oneshot workaround-nvidia-gpu.service systemd unit file that runs the command and have the lxc autostart depend on it?

Might be something about PCI resets that running the command triggers 🤷‍♀️