Adding repos in dom0

User Support General
,
1

Hello,
I’m trying to add repos to dom0, especially rpmfusion (To have access to nvdia, brave, etc…) but any cmd I type comes back in error
I don’t have /etc/yum.repos.d/rpmfusion-free.repo
And these cmd doesn’t work:

sudo dnf config-manager setopt rpmfusion-free.enabled=1
sudo dnf config-manager setopt rpmfusion-free-updates.enabled=1
sudo dnf config-manager setopt rpmfusion-nonfree.enabled=1
sudo dnf config-manager setopt rpmfusion-nonfree-updates.enabled=1
sudo dnf upgrade --refresh

According to the error message, an argument is missing, meaning one of these seems to be wrong.
I tried with --setopt; I tried with --add-repo; --enable-repo, but none is accepted.

2

it’s a very bad idea to install rpmfusion in dom0. dom0 must be cleaner as possible.
If you want install nvidia’s driver, try this method:

3 Likes
3

Unless you want to enact some unflattering memes from the “Memes about QubesOS” thread … don’t install a browser or any non-qubes repos in dom0.

4 Likes
4

TY, I read and tried this one, but didn’t achieve
And some others …
That’s why I’m at the point to ask for rpmfusion in dom0 :confused:

5

TY, IDK about “memes about Qubes”, I will have a look :slight_smile:

I don’T want to install Brave (nor any browser) in dom0, since no network, I want Brave to be the default browser in all other qubes, not having to install them all one by one

6

you just have to install it in Templates that’s it lol

4 Likes
7

Yes, but that is what I’ve been unable to do so far, so I thought … maybe through dom0 … ya know, the simple mind reflex
I haven’t been able to install package manager in fedora either (I have synaptic in Debian)

Now that I have a working pattern for Qubes, I have no problem reinstalling it completely if I messup too far :-p

8

Nothing ever goes in Dom0 Nothing gets in and Nothing ever gets out :zipper_mouth_face:

Unless it does but that’s very special.

2 Likes
9

Absolutely.
And I might be off … the material should be in dom0, right ? so I should have my NVIDIA in there, no ?
If I install my GPU in a qube, then only that qube will benefit from it, and if I want all my appVM to get it, I will have to install it in each and every of them, while going through dom0 makes it available at all level, no ?
I do get the dom0 segregation and necessary ghetto, but it is the central heart, so anything central should go in there, no ?

10

Probably. I Don’t know. I do know you wouldn’t want to use RPM Fusion or anything like it to do something like this. I look forward to whoever joins the thread to provide the complete answer/solution :slightly_smiling_face:

1 Like
11

Agree, and I confess it’s not a smart move, it’s from frustration to not be able to load the nvidia gpu and wanting to do it before moving to other steps, therefore “rushing” to whatev’ works … which is far from best.
As @Tezeria suggested, I should go back to reading and swallowing my frustration and just wait to find an acceptable solution rather than jumping to cut corners.

2 Likes
12

Still not clear on what you’re hoping to do/what you’re having issues with (whether it be GPU passthrough or software/package installation), but this is really the only guide you need for adding software/packages to a VM/qube/standalone or template:

1 Like
13

Install nvidia to make use of the GPU, system wide

Having a GPU with 6GB GDDR6 and not being able to take advantage of it

And while at it, since I’m still experimenting, I thought that installing other things like Brave at dom0 level would make it easier to get access to it in every domU (where I didn’t manage to install it), but that is now off the table.

1 Like
14

About this, you should take a look at the docs:

And this:

1 Like
15

If this nVidia card is your one and only card you won’t use it more than base igpu.

16

I’d suggest reading more on the Qubes architecture and basics of how dom0 administers domU vms systemwide: Documentation — Qubes Docs

3 Likes
17

I got into a similar problem when starting to use Qubes.
What I did:

  1. I created a template called debian12xfceSomething (choose your name) based of course in debian12xfce.

  2. I installed all I needed on that template (just open the terminal for that template, it will startup and behave like a “normal” VM)

  3. I created my VMs using that template of mine as a base

  4. Voila! All software is in all VMs. All I need to do now, is to keep that template updated.