On Tuesday, August 16, 2016 at 3:10:14 PM UTC-4, Andrew David Wong wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> 
> On 2016-08-16 10:40, [email protected] wrote:
> > On Tuesday, August 16, 2016 at 1:38:08 PM UTC-4, Andrew David Wong wrote: 
> > On 2016-08-16 10:35, [email protected] wrote:
> >>>> On Tuesday, August 16, 2016 at 1:33:05 PM UTC-4, Andrew David Wong 
> >>>> wrote: On 2016-08-16 10:27, [email protected] wrote:
> >>>>>>> I've been trying to install the drivers for my bcm4352 but I\ve
> >>>>>>> been unable so far. I'm on 3.2 rc2. Here's what I'm trying to
> >>>>>>> do:
> >>>>>>> 
> >>>>>>> [...]
> >>>>>>> 
> >>>>>>> However I get "No package aknod-wl available"
> >>>>>>> 
> >>>> 
> >>>> Is your TemplateVM set to allow allow connections to RPMFusion's 
> >>>> servers? You should be to do this either by enabling the RPMFusion 
> >>>> repo or by allowing all connections for N minutes.
> >>>> 
> >>>> 
> >>>> Aren't connections allowed by default on the sys-net? Am I doing all
> >>>>  of this on the wrong vm? I'm trying to get this working for dom0
> >>>> 
> > 
> > Ah, sorry. I misunderstood the original message (thought you were trying
> > to install something in a TemplateVM).
> > 
> > Yes, by default, all connections should be allowed from the default 
> > sys-net. Are you sure that the package actually exists in the repo?
> > 
> > 
> > Yes, it should exist based on everything I've read. I've also tried adding
> >  the bumblebee repos (which the files definitely exist there) and I'm 
> > getting the same errors which is why I believe that the repos aren't 
> > actually being added
> > 
> 
> Let's step back for a moment.
> 
> 1. You're doing all this from the sys-net terminal just to check whether the
> packages are available (because all connections should be allowed from
> sys-net) and/or temporary install the packages to test compatibility or
> something, right? You're not actually attempting to install a package in
> sys-net with the intention of having it persist there, right?
> 
> 2. You said you're trying to get this working for dom0. Normally, you'd
> install the drivers for a Wi-Fi device in the TemplateVM on which the NetVM is
> based, not dom0. Are you doing something special, such as trying to force
> network access in dom0? If you actually wanted to install a package in dom0,
> you'd use qubes-dom0-update, e.g.,
> 
>     $ sudo qubes-dom0-update <package-name>
> 
> 3. How are you attempting to add/enable repos? The first place I'd check is
> /etc/yum.repos.d/ .
> 
> - -- 
> Andrew David Wong (Axon)
> Community Manager, Qubes OS
> https://www.qubes-os.org
> -----BEGIN PGP SIGNATURE-----
> 
> iQIcBAEBCgAGBQJXs2UKAAoJENtN07w5UDAwkrUP/RFFippKtY3B9yjEcuSqZMjL
> UJlowICR/OEN+UqLWnHIGAbu6NjXuqbjY258874Gqand/88yKwWrxdO5sxBotpyP
> EcawKZ1zOJcWenbY5KPMFEpjAxCAgS5w+xLt7lSdjSkcozRVJ+9DI8irKTnFZIn8
> CRr8y4wGfpwIos5bx281XSoNMJdsTIvOh7JcoWbFvJX0zy3yAVzKAP/Jko9MWkoh
> jX/aKmeFZarA3oinfsxIHBQvGljUJ26YsI5laDOFk/zgAwarJYNZl57/FvkJ802N
> EiS8b5kEvYgwuZfpUC0m/AtKsVvdmjGcKQSEhyRLfHnS+hRBBmahmRN3lssTSNbD
> ussMFfJaWe2ycffrMXBWpsUg9n1YJnZie8qGv5cPzC8za6naETvmreLk94Nszjs6
> wWW5a2MehWG92y8d8yBkLEorumYU9AYOajm4F7eZGTfLTpPC2b+GFrZnsFigdRcv
> WHGppovvUpc3C64l0K/jBSWfbnCCEQDezcCYaG06haYhIs/WhCKEhtAG6X8MSe/P
> TbeA9a7rfRU0IrCPFRz/1aJHTaSe+zzBAFOKeWTWfhktFS+2+1+M/5rft5AI90Cn
> UgpT0IiJW+k2UIHoiOC+wRmGEiwT5ukRS/3jdyybvDtIB0FMBU4qwO3ymuMtqv68
> AzcVAgfTdiGZZVyrUJC4
> =YGie
> -----END PGP SIGNATURE-----

Oh duh, that's why it's not persisting. I'm trying to install the wireless 
drivers and bumblebee (for my nvidia card) on the dom0. So I do all of this on 
the fedora template?

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/7d44c34b-8193-4429-82ff-1321ef3ec60a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to