Re: [qubes-users] HCL - Clevo N850

2018-05-02 Thread bruno ais
On Wednesday, May 2, 2018 at 7:35:11 AM UTC+1, awokd wrote:
> On Tue, May 1, 2018 3:14 pm, Brunoais wrote:
> 
> >
> > GPU (GTX1050TiM) passthrough: Unfortunately, I was completely unable to
> > setup a passthrough for this GPU. I've tried many other success stories.
> > According to my research, I'd need nouveau working on DOM0 and qubes
> > allowing OpenGL (or equivalent) because the contents of the qube would be
> > shown on a window instead of a different screen and then I'd need to get
> > bumblebee (or equivalent) to work on DOM0. (E.g. guide:
> > https://gist.github.com/Misairu-G/616f7b2756c488148b7309addc940b28)
> 
> That's an interesting link. Looks like he is using QEMU and passing
> through the discrete GPU to his VM, then getting output back over
> RDP/RemoteFX. You should be able to pass the GPU through to a Qube by
> attaching it, but I'm not sure anyone has been able to get it to work like
> you describe.

No matter what I try, I keep getting crashes from the OS in the VM when I do a 
GPU passthrough. I'm still investigating if I'm missing something by using more 
permissive OSs (ubuntu MATE, for now).
I did notice that, with ubuntu, I'd have to set "nomodeset" for the booting 
parameters, otherwise, it would exponentially get slower up to a complete 
unresponsiveness.

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/7298a082-f6c6-42da-ac4f-523f1d0b29e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] HCL - Clevo N850

2018-05-02 Thread 'awokd' via qubes-users
On Tue, May 1, 2018 3:14 pm, Brunoais wrote:

>
> GPU (GTX1050TiM) passthrough: Unfortunately, I was completely unable to
> setup a passthrough for this GPU. I've tried many other success stories.
> According to my research, I'd need nouveau working on DOM0 and qubes
> allowing OpenGL (or equivalent) because the contents of the qube would be
> shown on a window instead of a different screen and then I'd need to get
> bumblebee (or equivalent) to work on DOM0. (E.g. guide:
> https://gist.github.com/Misairu-G/616f7b2756c488148b7309addc940b28)

That's an interesting link. Looks like he is using QEMU and passing
through the discrete GPU to his VM, then getting output back over
RDP/RemoteFX. You should be able to pass the GPU through to a Qube by
attaching it, but I'm not sure anyone has been able to get it to work like
you describe.

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/c08980455d56dd097e815b4d2a342e40.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] HCL - Clevo N850

2018-05-01 Thread Brunoais


 Problems and some background*
 *


 *Booting:*

Booting only worked with

1. UFI turned off.
2. nuveau blacklisted (blacklist.drivers=nouveau)

With UFI turned on, it was always unable to find Qubes on my flashdrive.
With nuveau not blacklisted, Xorg was always unable to start (I don't 
know how to get the logs for here).


For about 1/10th of the times (I've been manually counting 20) for the 
past weeks, boot fails. It asks for the decryption passphrase and it 
fails to decrypt the partition.



 *Installation:*

*Background:* I have an SSD and an HDD. I tried splitting OS data 
(larger information which changes less often) into the SSD and the 
regular data (smaller data that changes much more often) into the HDD.
This included storing "/boot" and "/" into the SSD and "/home" and 
"/swap" to the HDD.
*Problem: *Unfortunately, no matter the way I tried to configure (unless 
if placing all into the SSD), It only boots from the HDD and can't boot 
from the SSD, for some reason.



   *Setup:*

Worked without issues.


   Qubes features:

Sleep does *not *restore reliably: Every time I put the PC to sleep, it 
is a gamble of whether or not it will come back Even though the odds 
have been more turned to "it will come back". When it doesn't turn back, 
it exits from sleep, turns on the screen but nothing ever appears on 
screen. Instead, XScreenSaver password prompt should appear, instead.


Dom0 has a task manager... Which unfortunately, doesn't tell me how much 
%CPU each machine is working. Knowing about hypervisors, I suspect that 
is caused by how a hypervisor itself works, where the host can't know 
how it is using the hardware unless it is running in HVM mode (in Xen's 
case)



   *Unofficially supported features:*

GPU (GTX1050TiM) passthrough: Unfortunately, I was completely unable to 
setup a passthrough for this GPU. I've tried many other success stories. 
According to my research, I'd need nouveau working on DOM0 and qubes 
allowing OpenGL (or equivalent) because the contents of the qube would 
be shown on a window instead of a different screen and then I'd need to 
get bumblebee (or equivalent) to work on DOM0. (E.g. guide: 
https://gist.github.com/Misairu-G/616f7b2756c488148b7309addc940b28)


My main objective for this was 3D rendering (and other usages for the 
CUDA cores, including, for programming use) and for gaming.


Unless someone is able to help me handing the only problem which 
prevents me from using Qubes.



   Results

Everything worked as the manual described and I didn't have any 
surprises with actions and features on this platform.



   Aftermath

Since the beginning of last year I've been wanting to use qubes. It has 
so so many features which makes having a very secure system much easier 
than most other OS. Not only that, it also makes privacy and anonymity 
(when chosen to) a much easier and straightforward job to implement. 
Even then backing up any of the qubes is a job almost without hassle. In 
nearly all I did, qubes was doing a great job behind the scenes to keep 
me informed about nearly all that was being done.


--
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/558db6d5-a41c-ea6e-f303-c028277d3cc3%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
---
layout:
  'hcl'
type:
  'notebook'
hvm:
  'yes'
iommu:
  'yes'
slat:
  'yes'
tpm:
  'unknown'
remap:
  'yes'
brand: |
  Notebook
model: |
  N85_N87,HJ,HJ1,HK1
bios: |
  1.05.18
cpu: |
  Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
cpu-short: |
  FIXME
chipset: |
  Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM 
Registers [8086:5910] (rev 05)
chipset-short: |
  FIXME
gpu: |
  Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
gpu-short: |
  FIXME
network: |
  Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit 
Ethernet Controller (rev 12)
  Intel Corporation Wireless 8265 / 8275 (rev 78)
memory: |
  16141
scsi: |
  ST1000LM048-2E71 Rev: SDM1
usb: |
  1
versions:

- works:
'yes'
  qubes: |
R4.0
  xen: |
4.8.3
  kernel: |
4.14.18-1
  remark: |
Cannot passthrough GTX1050Ti NVidia card (VM crashes every time I try)
Recovering from sleep sometimes fails, forcing me to do a PCI reset
  credit: |
Brunoais
  link: |
https://github.com/brunoais

---