change settings with xrandr or gdk-screensettings.
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this
Ive been using qubes for quite a while. Recently i wanted to pass my USB-Sound
device to a appVM, which is located within a Powered Hub. I noticed that
qvm-usb didn't display it at all. But a USB Storage device was accessable via
the qubes-manager to attach to a appVM.
Biggest issue that limits you with nvidia is the fact that drivers detect that
it is running in a VM / HVM etc.. It is possible to get nvidia drivers
installed into Qubes (dont recommend it) and then you can pass a prime device
through to a app VM with little issue. Ive done this for doing
On Wednesday, 12 April 2017 23:30:51 UTC+1, mystre...@gmail.com wrote:
> Hello, i hope you can help me.
> After I install Qubes to the SSD and reboot, it does not recognize the SSD as
> a bootable device. Using the same install procedures on another SSD (SATA),
> everything works fine. When
Just to update.
I am currently running Nvidia drivers without a issue.
dom0 Kernel: 4.4.31-11
Kernel-module: compiled in dom0;
1. dom0: qubes-dom0-update install gcc devel-kernel ksmod linux-headers
2. appvm: download NVIDIA-Linux-375.20-install.run (any appvm)
On Tuesday, 11 October 2016 23:37:33 UTC+1, Desobediente wrote:
> Additionaly, the Bumblebee howto is here:
There is nothing new about these and frankly anyone could have found them via
google just looking, if you managed to get Nvidia working on Q3.2
I've used qubes for quite a while not and had no issues with my Fn (function)
keys working as should do until the Qubes 3.2 release, all the release
candidates they worked perfectly fine. Ive checked with xev in dom0 and they
are not even detected as XF86 keys so i cant even manually map them
On Sunday, 25 September 2016 15:33:35 UTC+1, Clark Venable wrote:
> On Sunday, September 25, 2016 at 8:42:08 AM UTC-4, Clark Venable wrote:
> > Nope. Allow local data to be set is enabled.
> It all works as I expect in Firefox, So I'm happy to leave this alone and
> just use Firefox rather
Long story short I'd like to share my keyboard and mouse from my Qubes
environment to a windows environment (physically different machine) with
synergy. Any ideas of best way to achieve this? short of adding networking to
dom0 which I'm not willing to do.
You received this message because
I'm getting the feeling the issue might be a lack of nvidia graphics drivers.
- Installed i3 and i3-settings-qubes
- configured .config/i3/config how i wanted it.
- anything CLI works perfectly fine.
- anything GUI will render very very slowly, you can see it rendering as it
Worked perfectly with 3.1 without a issue upgraded to 3.2 to test so far no
issues at all. No AEM due to lack of kernel support for the TPM.
Due to a marvell m.2 chipset for one of the SSDs you need to add
pci-phantom=02:00,1 to the xen.cfg on the installer and in the boot partition
I've got 3.2 RC1 to install and boot with UEFI perfectly fine. edited xen.cfg
in /boot/efi . added pci-phantom= [due to a marvel m.2 ssd] and
removed the 4Gb memory limit for dom0.
I'd like to try some of the new features, not limited to but including the i3
tile window manager. IS there any
Mail list logo