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
47 matches
Mail list logo
