On Thursday, February 21, 2019 at 7:20:58 PM UTC-5, vadimkly...@gmail.com wrote:
>
> Eric, any chance you could try updating the Bios to the recently released
> version 1.18 which I think should fix the graphics issues allow you to use
> the intel chip and try again with the latest version of
Difficult to setup due to the "I219-LM" Network controller needing
permissive=true and no-strict-reset=true and unable to install latest nvidia
cuda drivers. Kernel-latest and/or Xen 4.8 does not support the Intel UHD GPU
even when disabling nouveau - must use Nvidia only for now.
Sleep not
sys-usb option is disabled during install due to keyboard being USB. Suspend
not working due to known Lenovo BIOS issues (they removed S1 and S3).
Very simple install overall. Touchscreen/pen input acts as normal mouse like
most other touchscreens.
Sleep issue is a known issue of all the
Simple install. Most things working except Suspend and "Yoga Mode" not
disabling the trackpad nor flipping the monitor. Sleep not working with BIOS
1.17
Sleep issue is a known issue of all the latest Lenovo Thinkpad models since
they removed S1 and S3 from BIOS). There are some ACPI hacks
On Sunday, January 13, 2019 at 10:51:14 AM UTC-5, awokd wrote:
> Weird, not sure how it can detect that 14.3 device with it supposedly
> disabled. Check sys-net's Qube Setting/Devices and remove 14.3 from the
> right if it's there. Leave 1f.6/Ethernet enabled and assigned if it's
> not causing
For the record, I am now using 4.0.1 since it released (same problems).
On Monday, January 7, 2019 at 12:49:52 AM UTC-5, awokd wrote:
>
> Try temporarily disabling your wifi card for the install.
>
Good idea! I disabled it, along with just about every device I could find. It
generated a
See inlines.
On Friday, January 4, 2019 at 5:16:16 PM UTC-5, Achim Patzner wrote:
>
> The good old I219-LM problem... Before assigning (or after 8-) it to
> sys-net (I do not really see any reason it should be assigned to sys-
> firewall... are you sure?) it needs to get set to
Trying to install Qubes R4.0 and R4.0.1-rc2 and receiving the same install
error each time.
https://imgur.com/a/haBeVee
/usr/bin/qvm-start sys-firewall failed
stdout: ""
stderr: "Start failed: internal error: Unable to reset PCI device
:00:1f:6:
no FLR, PM reset or bus
other USB devices. I'll add an Introduction as well to
help clarify things and what all that guide covers.
On Friday, January 4, 2019 at 12:54:56 PM UTC-5, Lorenzo Lamas wrote:
> On Friday, January 4, 2019 at 6:29:37 PM UTC+1, Eric Duncan wrote:
> >
> > The odd part is... I
On Friday, January 4, 2019 at 9:54:56 AM UTC-8, Lorenzo Lamas wrote:
> The guide also shows how to hide all USB controlles from Dom0. This is now
> default, so you need to unhide them.
Do you think I need to passthrough an entire controller? Or should I try to
narrow down just the one keyboard
Following this guide to enable a sys-usb qubes, but with a USB keyboard fails:
https://www.qubes-os.org/doc/usb/#how-to-use-a-usb-keyboard
Tried on two ISOs: R4.0 (bare ISO install, no updates) and R4.0-rc2 (up to
date).
Tried on two systems: Thinkpad X1 Tablet 3rd Gen and Apple Macbook Pro
Latest 1.17 BIOS, VT-d and Virtualization enabled in BIOS. Various thunderbolt
assists disable/enable, etc options tried on/off. Must use discrete graphics
during install, which is an Nvidia Quatro P2000 (similar to the GTX 1050qm
generation).
Anaconda installer gets past the initial setup,
On Saturday, December 15, 2018 at 12:52:49 PM UTC-5, archie...@gmail.com wrote:
>
> The second thing i'm wondering is that I don't have /etc/default/grub file
> Where do i have to add the nouveau blacklist? Would echo "blacklist nouveau"
> >> /etc/modprobe.d/blacklist.conf work?
>
Yes, and I
On Sunday, December 16, 2018 at 1:03:45 PM UTC-5, Brendan Hoar wrote:
> On Sunday, December 16, 2018 at 10:44:07 AM UTC-5, Eric Duncan wrote:
> > AES hardware acceleration happens in your CPU, FYI. And usually the more
> > higher end ones.
>
> I would wager that any CPU th
TPM is basically is just a key/value storage on a chip on your motherboard. The
idea is that Secure Boot's certificate is used to gain access to the TPM to
pull out the stored keys. Then the keys are used as the key to unlock your
encrypted partition.
TPM is not used by Qubes by default.
The
Nice setup. I have an 2950x under the tree waiting for qubes for my kiddo.
TPM is only used for the Anti-Evil Maid feature. You can read up on it and if
your threat model includes such an attack or not. Tip, the deal breaker
decision: you loose sys-usb, USB isolation, if you enable AEM because
FYI, I plan on doing this as well when I get my P1 in a few weeks.
> I've installed the nvidia driver and disabled/blacklisted nouveau, however I
> can't use bumblebee due it complaining there's no Intel GPU (Using `00:03.0
> VGA compatible controller: Device 1234: (rev 02)`)
>
My research
On Saturday, November 24, 2018 at 4:54:13 PM UTC-5, micr0@gmail.com wrote:
> Thanks do you have a Link to the merged PR..
Sorry for the delay.
All work was here:
https://github.com/QubesOS/qubes-installer-qubes-os/pull/20
> then you mean mounting the installer usb in macOS
> cd to
Just off the bat, the biggest concern is that dGPU: you can't turn it off in
the bios (as ithet Thinkpad users have reported on /r/thinkpad).
I just ordered the Thinkpad P1 myself, which is the same as the X1 Extreme just
with ECC and Xeon.
I specifically got it for its 32GB ECC ram for
Oh, one other thing to note in the PR that was merged... I added an
00-README.txt to the /boot/EFI partition of Qubes.
Here's a trick to tweak Qubes settings over and over, especially on Macs...
You can boot into macOS normally. You should seen the EFI boot partition
mounted under /Volumes/.
On Tuesday, November 20, 2018 at 2:23:13 PM UTC-5, Koma Kurt wrote:
>
> Hi there im new to Qubes OS and i want to install it on external ssd...
>
Btw, this is exactly how I install Qubes R4 (and RCs) for all the testing I
did. I installed Qubes OS on an M.2 USB3.0 adapter that uses the
On Monday, November 20, 2017 at 12:39:58 PM UTC-5, Unman wrote:
> On Mon, Nov 20, 2017 at 09:04:35AM -0800, Eric Duncan wrote:
> > On Monday, November 20, 2017 at 11:55:35 AM UTC-5, Adrian Rocha wrote:
> > > Hi,
> > >
> > > When I try to update my Whoni
On Monday, November 20, 2017 at 11:55:35 AM UTC-5, Adrian Rocha wrote:
> Hi,
>
> When I try to update my Whonix gateway I have the following error:
>
> user@host:~$ sudo apt-get update
> Hit http://deb.whonix.org jessie InRelease
>
> Hit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I'm having a difficult time attempting an EFI install of
Qubes-R4.0-rc2-x86_64.iso across 4 different machines and 3 different USB
sticks made by various procedures.
* Installing to an Asmedia USB3 device (all systems detect as HDD)
* Must use
On Tuesday, February 17, 2015 at 6:20:36 AM UTC-5, onnozw...@gmail.com wrote:
> Hi,
>
> I didn't find any recipe to install Qubes on a USB stick from OSX;
> specifically at https://qubes-os.org/wiki/InstallationGuideR2 where I would
> expect such info. I'd like to suggest the following text
ModelDell Inc. Studio XPS (1640) (Core2 Duo P8600, PM45, ATI)
BIOSA15
HVMyes
IOMMUno
SLATno
TPMno
QubesR3.2
Kernel4.4.62-12
RemarkRuns great, but no IOMMU nor HAP/SLAT.
CreditEric Duncan
Notes:
With a CPU score
On Friday, June 23, 2017 at 10:51:17 AM UTC-4, David Nogueira wrote:
> Hi all,
>
> I have been struggling to find a good way to use my 4k display. For context,
> I have looked for setting HiDPI, am aware of
> https://github.com/QubesOS/qubes-issues/issues/1951 and others, but at least
> for
On Monday, June 26, 2017 at 10:44:41 PM UTC-4, cooloutac wrote:
>I guess just use testing or unstable repos if you want to have the latest
> for now. I have no idea where to get the beta for 4.0 if thats what you're
> asking.
Yes, that's partly what I am asking. I read where 4.0 is going
On Monday, June 26, 2017 at 1:27:19 PM UTC-4, cooloutac wrote:
>
> upgrading to the latest release from previous version didn't go well for me.
> There are instructions on how to do so and maybe I did something wrong. But
> I had to reinstall fresh and restore backups which went smooth.
>
>
On Monday, June 26, 2017 at 10:09:23 AM UTC-4, Noor Christensen wrote:
> On Thu, Jun 22, 2017 at 08:21:10AM -0700, Eric Duncan wrote:
> > Alternatively... Is there a way to use some type of "Testing" repo for
> > Qubes? Something like rolling updates of Debian
Currently running Qubes 3.2 on one machine. Have a need to install it on
another.
To all of you long-term beta users of 3.x and now 4.x...
1a) Are upgrades simple to RTM versions of Qubes?
Or 1b) Do you wipe and format each time a beta or RC comes out?
I'm debating install Qubes 4.0
On Wednesday, May 3, 2017 at 10:54:50 AM UTC-4, seans...@gmail.com wrote:
> I got Qubesos 3.2 installed on my Surface Pro 3, however the newer touch
> cover (the one made for the pro 4,but works on pro 3) doesn't work out of the
> box and as such I can't type anything, nor login, since the
My Lenovo Thinkpad Helix has the same issue with the touchscreen.
Doesn't matter the number of input devices. The TouchPoint, Trackpad and an
logitech unified mouse adapter works perfect fine with 0 configuration.
The Helix has a wacom digitizer, as well as mouse input - so it's really two
I am in the same position with a Lenovo Thinkpad Helix tablet w/touchscreen. I
selected usb-vm on installation, and cannot get the touchscreen working either.
Subscribing for updates, or of someone wants me to test (not sure how to debug
or try to enable it).
-E
On Friday, June 2, 2017 at
as next to no touchscreen
abilities - especially at login. I am sure Touchscreen is not a priority for
Qubes anytime soon either. Oh wells. i3wm + keyboard dock works awesome.
Eric
On Wednesday, May 31, 2017 at 2:53:39 PM UTC-4, Eric Duncan wrote:
> Model Lenovo Thinkpad Helix (36984SU) (
Model Lenovo Thinkpad Helix (36984SU) (i7-3667U, Ivy Bridge, HD4000)
BIOSGFET56WW (1.35 )
HVM yes
IOMMU yes
SLATyes
TPM yes
Qubes R3.2
Kernel 4.4.67-12
Remark CSM legacy boot on USB3 only, no touchscreen.
Credit Eric Duncan?
Notes:
With such a small screen, tight
C+2, Eric Duncan wrote:
> > Hello:
> >
> > Does Quebes perform a machine-specific installation? IOWs, can I install
> > Quebes on a single USB device and share it across different machine setups?
> >
> > E.g. if I install Qubes on an 8 core desktop, w/64GB ram,
Thanks Vit and Dave C!
@Dave:
Yep, USB sticks get too hot - and the USB2 sticks I tried were far too slow for
my taste.
I have a couple of these laying around from previous laptop builds:
https://www.amazon.com/Transcend-128GB-MSA370-mSATA-TS128GMSA370/dp/B00K64HXAA/?tag=eduncan911-20
Was
On Friday, May 26, 2017 at 3:27:18 PM UTC-4, tombulku...@gmail.com wrote:
> Thanks a lot Eric, already read this post and did all installation after
> verifying it but it didn't solve my issue.
> I need another method to fix this up, KERNEL FAILED is not the only issue, i
> cannot complete the
I get the same message on R3.2, and it works perfectly fine.
https://groups.google.com/forum/#!topic/qubes-users/iKs1ueF0ez8
Verify it with instructions in that thread. If passes, I wouldn't sweat it.
Btw, /r/Qubes didn't get a lot of traffic for me either. I would only post to
this Google
To clarify my original post/question:
What does Qubes use from the physical machine's properties to set up an
installation? I could not find any documentation on the site about this in the
Wiki (I'm happy to contribute it to the Qubes wiki, if it can be explained
here).
Some ideas I have
25, 2017 at 1:00:18 PM UTC-4, Eric Duncan wrote:
> > Hello:
> >
> > Does Quebes perform a machine-specific installation? IOWs, can I install
> > Quebes on a single USB device and share it across different machine setups?
> >
> > E.g. if I install Qubes on a
Hello:
Does Quebes perform a machine-specific installation? IOWs, can I install
Quebes on a single USB device and share it across different machine setups?
E.g. if I install Qubes on an 8 core desktop, w/64GB ram, SSD (just keep it
simple - only 1 SSD), Nvidia GPUs, etc - can I then take that
the password prompt comes up after the blank screen. So it is all
fine now.
I'll chalk it up to a bad installation.
On Friday, May 5, 2017 at 7:38:43 PM UTC-4, Eric Duncan wrote:
> New install, system went into suspend. Upon resume:
>
> - I cannot login / there is no login box.
> -
Humm. Thanks, but a simple validation error would have sufficed. :)
I was wondering where to add bugs. I'll do i there from now on.
On Saturday, May 6, 2017 at 12:34:15 AM UTC-4, Andrew Morgan wrote:
> On 05/05/2017 04:32 PM, Eric Duncan wrote:
> > ...because after waiting nearly
New install, system went into suspend. Upon resume:
- I cannot login / there is no login box.
- Window days that says XScreenSaver 5.35, dom0, "Authentication Failed!" <- I
haven't done anything to authenticate.
- Username: "user" (my username), but there is no Password box.
How do I type a
...because after waiting nearly two hours to install onto a USB stick, you'll
get an error at the very end stating the Python script had an error and
installation has been halted.
Error message: can't create user. user already exists (something like that)
I actually went through three
Hi Rusty,
This workaround does indeed work. Thanks for your help!
D
Rusty Bird:
> Duncan:
>> Coreboot was configured as follows: SeaBIOS as primary payload [...]
>
>> The behavior of trying to boot a stock Qubes install that was installed
>> using the inst
Dear Qubes users,
I am having trouble installing Qubes OS on my Thinkpad T420, after
installing Coreboot on it. Here is what I have to report.
The device is as follows, a Thinkpad T420 with an i7-2720QM. It has the
discrete Nvidia graphics, 16G of RAM, and an SSD.
Coreboot was configured as
On Wednesday, 7 December 2016 14:34:55 UTC, Ronald Duncan wrote:
> HCL-ASUSTeK_COMPUTER_INC_-GL752VW-20161207-142440
>
> Needs nouveau.modeset=0 to run!!
>
>
> Looks like everything is working
>
> Ethernet
>
> Wifi
>
> usb
>
>
>
>
On Tuesday, 3 January 2017 21:33:47 UTC, Andrew David Wong wrote:
> On 2017-01-03 08:38, Ronald Duncan wrote:
> > Looking to reinstall qubes from scratch and would like to optimise
> > the use of the ssd so I execute as much as possible on the ssd and
> > use
Looking to reinstall qubes from scratch and would like to optimise the use of
the ssd so I execute as much as possible on the ssd and use the sata for
storage.
I have a 500gig ssd and 1 tb sata.
Thoughts appreciated
At the moment I installed qubes on the sata drive to test out and experiment
This thread just sprung to life again.
I had a quick look at
https://www.qubes-os.org/doc/templates/
And along with Debian which is installed by default both
Arch and
Ubuntu
Are available...
My personal preference in Ubuntu because it generally just works, and Arch
because it has the
On Friday, 9 December 2016 11:43:04 UTC, Ronald Duncan wrote:
> Any update on
> https://github.com/QubesOS/qubes-issues/issues/1585
>
It looks like qubes-windows-tools breaks the ctl+alt+del and stops it going to
the VM along with any alternative.
I copied over the VM again, and havi
Any update on
https://github.com/QubesOS/qubes-issues/issues/1585
I could not get the work arounds to work.
Situation, could use sticky keys to get into vm and install qubes-windows-tools
Having installed qubes-tools sticky keys, onboard keyboard, and direct sending
of ctl+alt+del and
root.img >> becomes root-cow.img etc and the process was fine.
Was difficult to boot the windows image finally came up.
Then difficult to send ctl + alt + del (looks like this is broke in qubes)
Sticky keys worked.
Trying to get into safemode command prompt to turn off password.
--
You
On Wednesday, 7 December 2016 16:21:19 UTC, Ronald Duncan wrote:
> Where should I put the image file?
/var/lib/qubes/vm-templates/win7-x64-template
use
qvm-create --hvm-template win7-x64-template -l green
to create the template subdirectory
I just sshed the file in using my other ubu
It looks like qubes only supports win7 vm's. I have an old one that I ran
under kvm as a raw disk image.
Which looking at https://www.qubes-os.org/doc/hvm/ should work.
Normally I would just dd the image over an ssh pipe, and then reconfigure the
xml etc. I think I still have it as a raw
HCL-ASUSTeK_COMPUTER_INC_-GL752VW-20161207-142440
Needs nouveau.modeset=0 to run!!
Looks like everything is working
Ethernet
Wifi
usb
Issues during install I tried putting usb in a vm, (checking this and
running under the net vm which hung the install.
Installing the default ticked vm's
Looks like everything is working
Ethernet
Wifi
usb
Issues during install I tried putting usb in a vm, (checking this and running
under the net vm which hung the install.
Installing the default ticked vm's worked.
On installing from USB you need to do the following
just after installation -
On Wednesday, 7 December 2016 00:25:02 UTC, Marek Marczykowski-Górecki wrote:
> > Is there a way on the first boot after install prior to configuration to
> > set nouveau.modeset=0
>
> You can add it from grub menu. In UEFI mode (where grub is not used),
> just after installation - before
On Tuesday, 6 December 2016 13:30:05 UTC, Ronald Duncan wrote:
> Looks like I will need to reinstall since things are not working/strange and
> I remember that when it first started up it did not go through the initial
> set up smoothly, and then would not boot.
>
> Probably
Looks like I will need to reinstall since things are not working/strange and I
remember that when it first started up it did not go through the initial set up
smoothly, and then would not boot.
Probably need to set up with nouveau.modeset=0 and then see the results:)
--
You received this
On Tuesday, 6 December 2016 13:11:41 UTC, Ronald Duncan wrote:
> Changing grub config to boot with nouveau.modeset=0 gave me a good
> repeatable boot.
>
> Now qubes is usable will investigate if everything else works:)
Thanks to Marek Marczykowski-Górecki
--
You received
Changing grub config to boot with nouveau.modeset=0 gave me a good repeatable
boot.
Now qubes is usable will investigate if everything else works:)
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop
On Sunday, 27 November 2016 21:21:01 UTC, Marek Marczykowski-Górecki wrote:
> -BEGIN PGP SIGNED MESSAGE-
> This assume you can boot your system. Does the hang happen all the time,
> or only sometimes? If the former, try disabling nouveau driver (which
> looks to be the problematic one),
Hej folks,
I have installed Grub2 as my Coreboot payload, and now I want to boot Qubes
from a USB drive.
Since I haven't made any changes to Grub2's default config, I am trying to boot
Qubes from the command line Grub provides.
I do the following:
set root=(usb0)
linux /isolinux/vmlinuz
À 25.11.2016 04:36, Jean-Philippe Ouellet a écrit:
On Thu, Nov 24, 2016 at 8:12 PM, Duncan Guthrie <dguth...@posteo.net>
wrote:
And of course Coreboot is fast and fun.
I love your description of BIOS work as "fun" ;)
In my experience, getting things working has been anything
On 25.11.2016 01:44, taii...@gmx.com wrote:
Purism laptops are new intel so they will never have real coreboot
support, only FSP shimboot which is a black box that does most of the
work.
Its pointless, honestly you might as well just get an AMD (with
iommu/amd-vi) laptop if you want to avoid ME
On Tuesday, 22 November 2016 07:15:38 UTC, Me wrote:
> pierremartinf...@gmail.com:
> > Hi, I wonder if the Asus X205ta can handle Qubes ?
> > Thank,
> >
I find the latest ubuntu works well with most things. I have an ASUS ROC that
I got to run Qubes.
It has 32gb of RAM since I want to be able
Will this be using the latest linux kernel since grsecurity only provide the
latest version free.
--
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
logs till crash
rjd@rjd-GL752VW:~$ journalctl -D
/media/rjd/5ce4e7fe-aa0d-42d1-97f0-5c9197677697/var/log/journal/219d2a92843f491aaf97807aa063449c
-- Logs begin at Fri 2016-11-18 19:08:26 GMT, end at Sun 2016-11-20 10:30:15 GMT
Nov 18 19:08:26 dom0 systemd-journal[216]: Runtime journal is using
Asus ROG GL752VW-GS71-HID6 using Inteli7 processor
Boot process
.
.
.
Starting Switch Boot
Error: Driver 'processor_agregator' is already registered, aborting
Error: Driver 'processor_agregator' is already registered, aborting
A start job is running for Qubes NetVM startup (2m 49s
On Friday, 18 November 2016 20:25:41 UTC, Ronald Duncan wrote:
> > reboot - hung at end of Q screen
> Starting Switch Boot
> Error: Driver 'processor_agregator' is already registered, aborting
> Error: Driver 'processor_agregator' is already registered, aborting...
> reboot - hung at end of Q screen
Starting Switch Boot
Error: Driver 'processor_agregator' is already registered, aborting
Error: Driver 'processor_agregator' is already registered, aborting
A start job is running for Qubes NetVM startup (2m 49s /no limit NMI
watchdog:Bug soft
On Friday, 18 November 2016 19:44:09 UTC, Ronald Duncan wrote:
>
> Suggestions on how to turn off the Q screen and see what is happening behind
> the progress bar, and any logs that would be helpful.
Qubes start up Hit F10 for boot time diagnostics
--
You received this message be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 11/07/16 15:14, neilhard...@gmail.com wrote:
> Is it possible that someone who compromised QUBES, could re-write
> the AppVM in a way that whenever it is loaded up, it re-infects
> the entire system all over again...?
>
> In that case, the only
Hi all,
Personally, I think we don't need to have an active "moderator", but when
poison starts seeping through just blacklist the email address/account. We
can't assume everyone is guilty but when the guidelines of common decency are
violated then we need to have a process. It is hardly
On 9 July 2016 13:17:13 BST, Gorka Alonso wrote:
>
>
>https://groups.google.com/d/msg/qubes-users/V8_SvMk0yx0/P4VNTpFnBQAJ
>
>"Achim. Don't forget YOU are the homosexual, NOT ME. That's a mental
>disease, doesn't matter if for political reasons was removed or not
>from
On 9 July 2016 09:32:35 BST, juris...@gmail.com wrote:
>Em sábado, 9 de julho de 2016 05:24:04 UTC-3, Duncan Guthrie escreveu:
>> On 9 July 2016 09:12:28 BST, juris...@gmail.com wrote:
>> >> I definitely think we should remove that guide though. Nouveau
>> >su
in dom0 without the proprietary driver. From
>hardware support perspective we don't need to show people how to
>install proprietary driver in dom0, if they want to, can't they just
>ask on the mailing list? It is also bad for people's software freedom
>to support the proprietary driver. Th
On 8 July 2016 09:56:18 BST, juris...@gmail.com wrote:
>Em sexta-feira, 8 de julho de 2016 05:17:54 UTC-3, Laszlo Zrubecz
>escreveu:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA256
>>
>> On 07/08/2016 09:54 AM, juris...@gmail.com wrote:
>> > Ah and just 1 more thing. Dont forget that a
On 8 July 2016 08:51:00 BST, juris...@gmail.com wrote:
>I think programers have some kinda problem.
>They insist in trying to transform linux in something already is,
>something that wont bring windows users, just people into the IT world.
You do realise that most of us are not programmers?
On 7 July 2016 16:53:35 BST, Chris Laprise <tas...@openmailbox.org> wrote:
>On 07/07/2016 10:40 AM, Duncan Guthrie wrote:
>>
>> On 7 July 2016 03:28:48 BST, Chris Laprise <tas...@openmailbox.org>
>wrote:
>>> On 07/06/2016 09:42 PM, raahe...@gmail.com wrote
On 7 July 2016 03:28:48 BST, Chris Laprise wrote:
>On 07/06/2016 09:42 PM, raahe...@gmail.com wrote:
>> I'm not so adamant about wanting gpu passthrough on qubes, cause
>imo, gaming online usually means all security is out the window. Plus
>I feel as though gpu is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 01/07/16 18:19, raahe...@gmail.com wrote:
> On Friday, July 1, 2016 at 7:47:11 AM UTC-4, Duncan Guthrie wrote:
>
>
> On 01/07/16 02:05, raahe...@gmail.com wrote:
>>>> On Thursday, June 30, 2016 at 8:49:16 PM UTC-4, D
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 01/07/16 02:05, raahe...@gmail.com wrote:
> On Thursday, June 30, 2016 at 8:49:16 PM UTC-4, Duncan Guthrie
> wrote: On 01/07/16 00:03, Marek Marczykowski-Górecki wrote:
>>>> On Thu, Jun 30, 2016 at 10:57:42PM +0100, Duncan
Dear Qubes Users,
I have been using Qubes OS for a couple of days now. I own a Lenovo
Thinkpad X200 and everything works fine, including WiFi.
However, I am concerned about this, because my X200 has an Intel WiFi
chipset, which I know uses proprietary firmware. I am concerned about
this because
88 matches
Mail list logo