[qubes-users] Alienware X17 R2 Almost 100%, no PCI / Device Control - EUFI Error?

2022-12-16 Thread Nedly Cl
Recently I began configuring Qubes 4.1 on an Alienware x17 but one of my
final issues is PCI attachment or passthrough.

(compatibility side note)--
I have managed to get almost everything operational. I had to solve USB
keyboard issues, and update wifi for the killer wifi card. I also had to
change some configurations in order to have backlight controls and had to
adjust bios for graphics. I still need to solve PCI attaching and Bluetooth.


I am trying to make use of the graphics card - nvidia 3080.

The card is recognized by dom0 - I can see it with lspci command.

In Qubes Manager - Qubes Settings, the Device tab is greyed out.

When I try to run qvm-pci in dom0 it says: 'failed to list 'pci' devices,
this device type either does not exist or you do not have access to it'.

This is a EUFI board, and it seems to be EUFI ONLY.

I found a forum where people solved the issue by disabling Volume Control
in BIOS - but I do not see or have this option.

I have tried disabling all security in BIOS with no change. Secure boot is
off, and all of Microsoft's other security utils are disabled.

This unit has Thunderbolt, which I noticed was mentioned in forums. I am
not using the thunderbolt, and I tried disabling it once - dom0 did not
operate fully and no VM could launch.

This issue is making it impossible for me to attach or perform passthrough
of PCI devices to VM's...

Anyone have advice??? Is this a cemented EUFI limitation??

Thanks.

-- 
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 qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CA%2B5PLfPOGH%2B7b7pi%3Dpg%2BF78K7xSQZ5aB9o9Jo6Cs_8n7AqKWHw%40mail.gmail.com.


[qubes-users] Re: PCI Passthrough to Standalone VM

2022-12-15 Thread Nedly Cl
[EDIT]

I do not need specifically PCI passthrough. I am simply seeking to use the
GPU in different VM's, especially a Windows VM.

I am not totally opposed to building the drivers into dom0, but I would
prefer something better.

I just found the documentation on a sys-gui qubes. Maybe this is the
solution? I would really like to put solid effort towards getting this
nvidia card operational in VM's..

On Thu, Dec 15, 2022 at 9:12 AM Nedly Cl  wrote:

> Goal: Nvidia GPU in Standalone Windows VM
>
> Windows 10; Qubes 4.1
>
> Security is not a concern - this is a developers configuration.
>
> I see lots of forums and discussions and some people who claim they've
> done it but I have no luck finding good instruction.
>
> PC: Alienware x17 r2; Nvidia 3080
>
> It is extremely important to me to figure this out.
>
> Can anyone point me in a good direction??
>
>

-- 
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 qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CA%2B5PLfMw1x%3Dx%3D2vMfxW4idsGtCkYWiH%2BuShLM5rhd0W-sUgBPg%40mail.gmail.com.


[qubes-users] PCI Passthrough to Standalone VM

2022-12-15 Thread Nedly Cl
Goal: Nvidia GPU in Standalone Windows VM

Windows 10; Qubes 4.1

Security is not a concern - this is a developers configuration.

I see lots of forums and discussions and some people who claim they've done
it but I have no luck finding good instruction.

PC: Alienware x17 r2; Nvidia 3080

It is extremely important to me to figure this out.

Can anyone point me in a good direction??

-- 
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 qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CA%2B5PLfOSUCmOw2pLX53azNwZSBrXmGXsmTC8Lo7uZBgp6ZHXgg%40mail.gmail.com.


[qubes-users] Broadcom B43 BCM4350 PCI Modules / Device not functional

2019-11-04 Thread Nedly
I have been learning Qubes for a year off and on, and now I am trying to 
install it onto a laptop I use more regularly.

Currently I am working with the latest release (4.0.1 RC2) - testing 
updates, with Dom0 and Fedora completely updated.

I attempted a few tutorials regarding b43-fwwf & b43-fwcutter, but had no 
luck. I also tried the different modules installed, such as iwlwifi, 
iwldvm, iwlmvm, brcm modules - etc.

The most recent module I tried was to setup the WL module. This has not 
worked either. 

The wifi card works - currently I am using an Alfa USB Wifi adapter to make 
this post. I have tested the integrated wifi with other Linux distro's - 
mostly Debian based.

I tried searching resolutions online - including in this Google group, and 
I tried some of the listed solutions. None of them have worked for my card 
yet. The last one I tried can be seen here: 
https://groups.google.com/forum/?nomobile=true#!searchin/qubes-users/b43%7Csort:date/qubes-users/x0oJVv9SdHw/VpN5UwFpAgAJ
 
where the method is to compile and bind the WL module. This process went 
well and the WL module is being attached to the wireless card, however I am 
still not seeing networking options in the toolbar. 

>From what I can tell, brcmfmac is being loaded at boot and assigned to the 
card as well as the WL module.

I have tried rmmod of the brcmfmac module to see if it was interfering, 
however I have not tried that process as a during boot script.

I feel like I am so close to figuring this out! Any tips or hints? Any 
known solutions? 

-- 
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 qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/1a93f096-369c-4870-9a6e-d060c8ac3238%40googlegroups.com.