Re: [qubes-users] Copying text to/from Dom0

2019-09-26 Thread unman
On Thu, Sep 26, 2019 at 09:28:00AM +, duc...@disroot.org wrote:
> 799:
> > Hello
> > 
> >  schrieb am So., 22. Sep. 2019, 13:40:
> > 
> >>
> >> In the official documentation "Copying from (and to) dom0", there is no
> >> mention at all of how to copy text via the clipboard from a domain to
> >> dom0. What is the method to use?
> > 
> > 
> > Copying from dom0 to an AppVM is ok, as dom0 has to be trusted. 
> 
> But how is this done? Like I say, the official documentation references
> a **Qubes Clipboard** widget, but I can't seem to locate it in practice.
> Sorry if I'm overlooking something very simple.
> 

Look in panel - there should be qui-clipboard widget. (icon in KDE is
usual "copy" icon.)
Click and there is option to "Copy dom0 clipboard"

If you don't see it check that qui-clipboard is running in dom0

-- 
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/2019092609.GA30919%40thirdeyesecurity.org.


Re: [qubes-users] Copying text to/from Dom0

2019-09-26 Thread duc01k
unman:
> On Thu, Sep 26, 2019 at 09:28:00AM +, duc...@disroot.org wrote:
>> 799:
>>> Hello
>>>
>>>  schrieb am So., 22. Sep. 2019, 13:40:
>>>

 In the official documentation "Copying from (and to) dom0", there is no
 mention at all of how to copy text via the clipboard from a domain to
 dom0. What is the method to use?
>>>
>>>
>>> Copying from dom0 to an AppVM is ok, as dom0 has to be trusted. 
>>
>> But how is this done? Like I say, the official documentation references
>> a **Qubes Clipboard** widget, but I can't seem to locate it in practice.
>> Sorry if I'm overlooking something very simple.
>>
> 
> Look in panel - there should be qui-clipboard widget. (icon in KDE is
> usual "copy" icon.)
> Click and there is option to "Copy dom0 clipboard"
> 
> If you don't see it check that qui-clipboard is running in dom0
> 

I've just booted Qubes and for the _first time ever_ I have a clipboard
icon sitting between the drive widget and the network widget. I know for
a fact this wasn't present on any other boot occasion... Spooky isn't
the word for it.

Murphy's Law:  A problem will be reproducible up until the point you
attempt to demonstrate it to, or elicit help from, support personnel.

But it's there now. Hopefully it'll be there on every subsequent boot.

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/0a4a447f-dbe1-0c4f-b6f2-e03acbbddda3%40disroot.org.


signature.asc
Description: OpenPGP digital signature


Re: [qubes-users] using two whonix-gw instances

2019-09-26 Thread tetrahedra via qubes-users

On Wed, Sep 25, 2019 at 11:32:20PM +, 'awokd' via qubes-users wrote:

Sven Semmler:

On 9/25/19 5:26 PM, 'Jackie' via qubes-users wrote:

even different applications within the same vm, will use different tor circuits.


I know this is true of apps that come with whonix-ws, but is it the 
case for apps added later like Signal? I think you'd still be OK if 
Signal was the only thing added, but don't know about something like 
Signal and Discord in the same AppVM.


I'm fairly sure the answer is "no, stream isolation is only automatic
for apps which are wrapped by `uwt` or which otherwise take steps to be
isolated, and this just happens to be the case for most whonix-default
apps"...

--
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/20190926092207.GA1787%40danwin1210.me.


[qubes-users] R4.0.1 Initial Setup wizard didn't run

2019-09-26 Thread duc01k
Hi,

Just installed R4.0.1 onto a friend's PC and the Initial Setup wizard
didn't run on first boot into the fresh installation, so we have no VMs.
How do we initiate this manually?

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/e74fe441-72ba-a647-5eff-1476ed7da1c6%40disroot.org.


signature.asc
Description: OpenPGP digital signature


Re: [qubes-users] Copying text to/from Dom0

2019-09-26 Thread duc01k
799:
> Hello
> 
>  schrieb am So., 22. Sep. 2019, 13:40:
> 
>>
>> In the official documentation "Copying from (and to) dom0", there is no
>> mention at all of how to copy text via the clipboard from a domain to
>> dom0. What is the method to use?
> 
> 
> Copying from dom0 to an AppVM is ok, as dom0 has to be trusted. 

But how is this done? Like I say, the official documentation references
a **Qubes Clipboard** widget, but I can't seem to locate it in practice.
Sorry if I'm overlooking something very simple.


-- 
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/cdc3edcb-a54b-5706-9210-820b6a4fc208%40disroot.org.


signature.asc
Description: OpenPGP digital signature


Re: [qubes-users] using two whonix-gw instances

2019-09-26 Thread Sven Semmler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

My understanding is that TOR actually runs in the gateway and the the 
workstation(s) enable typical Qubes style compartmentalization. Meaning that if 
app-anon-1 is compromised, the sys-whonix and a potential app-anon-2 are not. 
When I create a second sys-whonix-id I can see via the Tor control panel that 
it uses a different Onion circuits than the first instance. 

Patrick pointed me to the Whonix forum and to the Tor project for answers. I'll 
report back here once I got clarification.

/Sven
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE18ry22WNibwI1qeq2m4We49UH7YFAl2M1TIACgkQ2m4We49U
H7ZK5w/8Dtbj/qPRGiyUkcay+KrK7Vw/VWlf5uEGsxLFnjyU/rVzZ+hFq6G1Y4Vy
2xwnmi9oygMuPpzTfDBw8pXS+mrqEIaIyzw6rEYgqZDAIcb2JBJiQ967EqIWuwWD
pqo8q5t8mlh2YQ+JNKF/IQi0lzoxyZnxeT8uKaVC/7oYvpFWz8DsbRFybjUfc4YI
tVj7J4RHOu5kzszTNBTMM0Dp0oFH+U4vIH/maIwB9ufhcQyLtXkDUKWVuQ2/Q+UO
nTSd52wvjcYE+eHbplDE6jqJNqsXoMEGfbr8NwgkUyeohtwlX/mNo9vosih+SGO5
abklDdwZPrKwigo5BQ7tH1GroXfjZKWbhEW28d22UVvM1FaSqHAwBDm0uO+E+J25
LCLClOcdYRYf7/Qh6d2UkaPcp1bWKdLNbUYjwvKlm19bJBxCWQJn4lCPV0/GQiiV
vddzRw340zIsFi1qAfrYMlKN7Xl0oHmqQPKM9FnDHBCsem7NkCItWTrbYvpizEXO
t/V+EKCBpPy0/e0z3JlkzDWij2PMh8gZ/eytchQ+664sWX+2pqCs67/lNLE2RlEn
lPQ4Y9J+wqsRhDg/4sflO/KDeBIVwUwrhuqvVuKu9237zUh3N8GsCbVtx3tSApFR
jyFtaSj09u0l3rsd/0Ph5wN7nS9brA8Q8dL+Rqv+hog65YY1Z8E=
=doZL
-END PGP SIGNATURE-

-- 
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/e4e51178-c9a2-e67a-a3ce-49c101d84586%40svensemmler.org.


Re: [qubes-users] R4.0.1 Initial Setup wizard didn't run

2019-09-26 Thread 'awokd' via qubes-users

duc...@disroot.org:

Hi,

Just installed R4.0.1 onto a friend's PC and the Initial Setup wizard
didn't run on first boot into the fresh installation, so we have no VMs.
How do we initiate this manually?


https://www.mail-archive.com/qubes-users@googlegroups.com/msg28168.html

--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots

--
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/11b9ceb4-d546-0f1f-8acd-ef32bc71cacc%40danwin1210.me.


Re: [qubes-users] Modify the Qubes Domain menu?`

2019-09-26 Thread Stumpy

On 2019-09-24 14:45, donoban wrote:

On 9/24/19 2:25 PM, Stumpy wrote:

Is there a way to add "restart" to the qubes domain menu, like the Qubes
manager has?



You will need to hack a little on:
'/usr/lib/python3.5/site-packages/qui/tray/domains.py'



Oi, I couldn't code (python or even a batch file) if my life depended on 
it, beleive me I have tried, hello world in perl was a challenge  :(


I don't suppose anyone out there has done such a thing? and/or added 
"percentage" for mem usage (not only cpu)?


fingers crossed.

--
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/742aa6c9-6367-f960-1d0b-f4521cbb885d%40posteo.net.


Re: [qubes-users] Qubes 4.0.x - Linux kernel 4.19.15 package available in testing repository

2019-09-26 Thread donoban
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 2019-09-26 13:50, Michał "rysiek" Woźniak wrote:
> Hey,
>
> On 1/29/19 10:33 AM, Patrik Hagara wrote:
>> Managed to get rid of the error (and more importantly, the
>> annoying artifacts) by forcing Xorg to use the generic
>> modesetting driver instead of i915/i965. ... ...
> After this procedure, do you get hardware acceleration? In my case,
> I do get `name:modesetting`, but I also get these in Xorg.0.log
> (and no hardware acceleration, obviously):
>
> [29.654] EGL_MESA_drm_image required. [29.654] (EE)
> modeset(G0): glamor initialization failed (...) [29.728] (EE)
> AIGLX: reverting to software rendering
>

I did same steps and I have acceleration working fine.

> Did you install/remove any packages? Can you share the output you
> get from `dnf list mesa* libdrm* xorg*`?
>
>> My hardware (sorry for not mentioning this earlier): Lenovo T480s
>> with i7-8650U, no discrete GPU.
>
> I'm on a T490. Will also test on a T470 later.
>

I think that I did not install nothing additional but I attached my
dnf output.
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEznLCgPSfWTT+LPrmFBMQ2OPtCKUFAl2MqBMACgkQFBMQ2OPt
CKWG+Q/+Iu4u8f5FHZ7+grxRpxlZ3d8M4TUpVaBRVnhJwHVgpr6x99NGsXR7c7fK
LdhHv4oES1uYwvksATXlYcKwpQs7bLZo8+UOXAWhgrMrzy+YZTdbmvOWCrSo/Cys
idoNM6P8N8ByzXZ/TwLx5Zoco2dE5vwHorSpvkDBASG4OL4CgpQcdUOQcJApS4+v
fAV6nn5rukkb7svrvF7UJVJNrMPikWQbeJRtkwIHKcyX7qNc2oOCs+3yBn9vIOEA
AZux704wCdzJnMnKG16raA2HhMZCikijefUMzDc4ihdMKAcpaBebuUU1wc7zIHKS
hF73jnUzEX5QmOwC6UEoHAYsgETpbSnAwxBToZRVjlqdZ4jy825XcWwZQ6qwKkSF
lFTvB4p296xoAsTbZB+867YsS/GVCG+/eBIew/9lPYLTTTh14zWqPujuUs9cD6U+
JlrAnFEqBCQ+Ky2520Q++yb8UsrlxqQ/uTWAtAlOToP30EXHkmG7T0QEevGISU+0
FTK87h8lFEkjOjQ7/906/YhL2lTLO7oWwgrgA6JIGgTj5yiuOwW0SPDkVg/0BvXp
cTbMrtbhI3R8KWtKV0avet4Ckv4xmwKO4Nxci6bn0az4e/u3+Mylmc1jSjavZ7cc
RhHdDcGd0Oh0nj1YXUn1XB6ZzV1jtTxEGhyUTPDjtrOqK1MuZp0=
=nr5J
-END PGP SIGNATURE-

-- 
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/df5dfe37-5296-ac06-7989-ed811820b998%40riseup.net.
Last metadata expiration check: 23 days, 22:32:35 ago on Mon Sep  2 15:25:23 
2019.
Installed Packages
libdrm.x86_64   2.4.85-1.fc25 @anaconda 
mesa-dri-drivers.x86_64 17.0.5-3.fc25 @anaconda 
mesa-filesystem.x86_64  17.0.5-3.fc25 @anaconda 
mesa-libEGL.x86_64  17.0.5-3.fc25 @anaconda 
mesa-libGL.x86_64   17.0.5-3.fc25 @anaconda 
mesa-libGLU.x86_64  9.0.0-10.fc24 @qubes-dom0-cached
mesa-libgbm.x86_64  17.0.5-3.fc25 @anaconda 
mesa-libglapi.x86_6417.0.5-3.fc25 @anaconda 
mesa-libwayland-egl.x86_64  17.0.5-3.fc25 @anaconda 
mesa-libxatracker.x86_6417.0.5-3.fc25 @anaconda 
xorg-x11-apps.x86_647.7-15.fc24   @qubes-dom0-cached
xorg-x11-drivers.x86_64 7.7-18.fc25   @anaconda 
xorg-x11-drv-ati.x86_64 18.0.1-1.fc25 @anaconda 
xorg-x11-drv-dummy.x86_64   0.3.7-1.fc25  @anaconda 
xorg-x11-drv-evdev.x86_64   2.10.5-1.fc25 @anaconda 
xorg-x11-drv-fbdev.x86_64   0.4.3-25.fc25 @anaconda 
xorg-x11-drv-intel.x86_64   2.99.917-32.20171025.fc25 @anaconda 
xorg-x11-drv-libinput.x86_640.23.0-4.fc25 @anaconda 
xorg-x11-drv-nouveau.x86_64 1:1.0.15-4.fc25   @anaconda 
xorg-x11-drv-openchrome.x86_64  0.5.0-2.fc25  @anaconda 
xorg-x11-drv-qxl.x86_64 0.1.5-2.fc25  @anaconda 
xorg-x11-drv-v4l.x86_64 0.2.0-47.fc25 @anaconda 
xorg-x11-drv-vesa.x86_642.3.2-25.fc25 @anaconda 
xorg-x11-drv-vmware.x86_64  13.2.1-1.fc25 @anaconda 
xorg-x11-drv-wacom.x86_64   0.34.2-1.fc25 @anaconda 
xorg-x11-font-utils.x86_64  1:7.5-32.fc25 @anaconda 
xorg-x11-fonts-ISO8859-1-100dpi.noarch
7.5-16.fc24   @anaconda 
xorg-x11-fonts-misc.noarch  7.5-16.fc24   @qubes-dom0-cached
xorg-x11-server-Xorg.x86_64 1.19.3-1.fc25 @anaconda 
xorg-x11-server-common.x86_64   1.19.3-1.fc25 @anaconda 
xorg-x11-server-utils.x86_647.7-20.fc25   @anaconda 
xorg-x11-utils.x86_64   7.5-21.fc24  

Re: [qubes-users] Neither WiFi card nor USBs work

2019-09-26 Thread acharya . sagar . sagar5
It is
kernel doesn't support reset from sysfs for PCI devices

and many more probably irrelevant things. I'm updating to Fedora 30 now. 
Mostly it should update the driver.

On Thursday, September 26, 2019 at 5:03:49 PM UTC+5:30, awokd wrote:
>
> acharya.s...@gmail.com : 
> > I did it using GUI earlier. I again tried using permissive=true in dom0 
> > terminal and started sys-usb. I still get the error. 
> > libxenlight failed to create new domain 'sys-usb' 
> > 
> > Updated dom0 using ethernet cable. Still broadcom WiFi and USBs do not 
> work. 
> > 
> > On Wednesday, September 25, 2019 at 10:02:37 PM UTC+5:30, awokd wrote: 
> >> 
> >> acharya.s...@gmail.com : 
> >>> I've made a fresh install of Qubes OS on my Laptop where I face the 
> >> problem 
> >>> of configuring USB and network devices to VMs 
> >> 
> >>> When I add 00:14.0 USB Controller: Intel Corp. Wildcat Point-LP USB 
> xHCI 
> >>> Controller (rev 03) to sys-net and try to start the VM, it gives me 
> the 
> >>> error 
> >>> no FLR, PM reset or bus reset available. 
> >>> 
> >>> When I enable no strict reset for USB Controller, this error shows up. 
> >>> Unable to reset USB Controller : libxenlight failed to create new 
> domain 
> >>> 'sys-net' 
> >> 
> >> Did you try enabling permissive mode in addition to no-strict-reset for 
> >> the USB controller? When you get the "failed to create new domain" 
> >> error, see if there is a more detailed error message in 
> >> /var/log/libvirt/libxl/libxl-driver.log. 
>
> Did you check the log? 
> Wifi is probably something different. Make sure the drivers/firmware for 
> your model wifi card are installed in the template used by sys-net. 
>
> -- 
> - don't top post 
> Mailing list etiquette: 
> - trim quoted reply to only relevant portions 
> - when possible, copy and paste text instead of screenshots 
>

-- 
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/7a48eeba-f501-40af-8698-252c65c74b42%40googlegroups.com.


Re: [qubes-users] Neither WiFi card nor USBs work

2019-09-26 Thread 'awokd' via qubes-users

acharya.sagar.sag...@gmail.com:

I did it using GUI earlier. I again tried using permissive=true in dom0
terminal and started sys-usb. I still get the error.
libxenlight failed to create new domain 'sys-usb'

Updated dom0 using ethernet cable. Still broadcom WiFi and USBs do not work.

On Wednesday, September 25, 2019 at 10:02:37 PM UTC+5:30, awokd wrote:


acharya.s...@gmail.com :

I've made a fresh install of Qubes OS on my Laptop where I face the

problem

of configuring USB and network devices to VMs



When I add 00:14.0 USB Controller: Intel Corp. Wildcat Point-LP USB xHCI
Controller (rev 03) to sys-net and try to start the VM, it gives me the
error
no FLR, PM reset or bus reset available.

When I enable no strict reset for USB Controller, this error shows up.
Unable to reset USB Controller : libxenlight failed to create new domain
'sys-net'


Did you try enabling permissive mode in addition to no-strict-reset for
the USB controller? When you get the "failed to create new domain"
error, see if there is a more detailed error message in
/var/log/libvirt/libxl/libxl-driver.log.


Did you check the log?
Wifi is probably something different. Make sure the drivers/firmware for 
your model wifi card are installed in the template used by sys-net.


--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots

--
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/164f0518-5bac-324f-39e5-dd555a0cbd40%40danwin1210.me.


Re: [qubes-users] Neither WiFi card nor USBs work

2019-09-26 Thread acharya . sagar . sagar5
I did it using GUI earlier. I again tried using permissive=true in dom0 
terminal and started sys-usb. I still get the error.
libxenlight failed to create new domain 'sys-usb'

Updated dom0 using ethernet cable. Still broadcom WiFi and USBs do not work.

On Wednesday, September 25, 2019 at 10:02:37 PM UTC+5:30, awokd wrote:
>
> acharya.s...@gmail.com : 
> > I've made a fresh install of Qubes OS on my Laptop where I face the 
> problem 
> > of configuring USB and network devices to VMs 
>
> > When I add 00:14.0 USB Controller: Intel Corp. Wildcat Point-LP USB xHCI 
> > Controller (rev 03) to sys-net and try to start the VM, it gives me the 
> > error 
> > no FLR, PM reset or bus reset available. 
> > 
> > When I enable no strict reset for USB Controller, this error shows up. 
> > Unable to reset USB Controller : libxenlight failed to create new domain 
> > 'sys-net' 
>
> Did you try enabling permissive mode in addition to no-strict-reset for 
> the USB controller? When you get the "failed to create new domain" 
> error, see if there is a more detailed error message in 
> /var/log/libvirt/libxl/libxl-driver.log. 
>
> -- 
> - don't top post 
> Mailing list etiquette: 
> - trim quoted reply to only relevant portions 
> - when possible, copy and paste text instead of screenshots 
>

-- 
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/42f2dd38-bfa3-45e9-a45e-fd375a834907%40googlegroups.com.


Re: [qubes-users] Qubes 4.0.x - Linux kernel 4.19.15 package available in testing repository

2019-09-26 Thread rysiek
On 9/26/19 11:59 AM, donoban wrote:
>> On 1/29/19 10:33 AM, Patrik Hagara wrote:
>>> Managed to get rid of the error (and more importantly, the
>>> annoying artifacts) by forcing Xorg to use the generic
>>> modesetting driver instead of i915/i965. ... ...
>>>
>> After this procedure, do you get hardware acceleration? In my case,
>> I do get `name:modesetting`, but I also get these in Xorg.0.log
>> (and no hardware acceleration, obviously):
> (...)
> I did same steps and I have acceleration working fine.

Right. Just tried on a T470 (i5-7200U) and it worked! Many thanks.

So it's the T490 Intel chipset that refuses to cooperate. R4.1 will have
Fedora 29 in dom0, so I guess that should fix it too.

--
Best,
r

-- 
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/77c11851-3a94-0105-c590-8e410160daa0%40hackerspace.pl.


signature.asc
Description: OpenPGP digital signature


Re: [qubes-users] Qubes 4.0.x - Linux kernel 4.19.15 package available in testing repository

2019-09-26 Thread rysiek
Hey,

On 1/29/19 10:33 AM, Patrik Hagara wrote:
> Managed to get rid of the error (and more importantly, the annoying
> artifacts) by forcing Xorg to use the generic modesetting driver instead
> of i915/i965.
> 
> Steps (all commands in dom0):
> 
> 1) check the driver currently in use (`xrandr --listproviders`), it's
> the last string (should be "name:Intel" now)
> 
> 2) create file /etc/X11/xorg.conf.d/20-intel.conf (as root) with the
> following contents (also make sure there are no other files in that
> directory with "Device" "Driver" set to "intel"):
> 
>> Section "Device"
>>   Identifier "Intel Graphics"
>>   Driver "modesetting"
>>   Option "AccelMethod" "glamor"
>>   Option "DRI" "3"
>> EndSection
> 
> 3) restart the X server (eg. using `sudo systemctl restart lightdm`)
> 
> 4) use the same xrandr command as in step 1, the driver should now be
> "modesetting" and you should see no errors in /var/log/Xorg.0.log, nor
> any graphical artifacts

After this procedure, do you get hardware acceleration? In my case, I do
get `name:modesetting`, but I also get these in Xorg.0.log (and no
hardware acceleration, obviously):

[29.654] EGL_MESA_drm_image required.
[29.654] (EE) modeset(G0): glamor initialization failed
(...)
[29.728] (EE) AIGLX: reverting to software rendering

Did you install/remove any packages? Can you share the output you get
from `dnf list mesa* libdrm* xorg*`?

> My hardware (sorry for not mentioning this earlier): Lenovo T480s with
> i7-8650U, no discrete GPU.

I'm on a T490. Will also test on a T470 later.

--
Best
r

-- 
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/4818b401-2add-13c8-4d8e-0a4bf71a323e%40hackerspace.pl.


signature.asc
Description: OpenPGP digital signature


[qubes-users] HCL - Lenovo Thinkpad X240

2019-09-26 Thread Julius Zint
For AEM (4.0.1-1.fc25) to work, i had to change the XEN iommu parameter
to required instead of no-igfx. Also if you use the internal drive as
installation target the SINIT module was not appended to the grub entry.
The parameter can be changed by editing the /boot/grub2/grub.cfg.

-- 
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/4C0EA730-83A3-4740-A8B2-8E7F2E3255F1%40gmail.com.


Qubes-HCL-LENOVO-20AMS21B00-20190926-213149.cpio.gz
Description: GNU Zip compressed data


Qubes-HCL-LENOVO-20AMS21B00-20190926-213149.yml
Description: application/yaml


[qubes-users] Re: Qubes 4,02 Fails on sudo apt-get update

2019-09-26 Thread American Qubist 001


On Thursday, September 26, 2019 at 10:26:09 PM UTC-4, American Qubist 001 
wrote:
>
> Never had trouble in Qubes 4.0 is it possible to access the repositories 
> from this testing version? Here is the result of the command:
>
>
> user@debian-10-clone-1:~$ sudo apt-get update
> Hit:1 https://deb.qubes-os.org/r4.0/vm buster 
> InRelease
> Get:2 https://cdn-aws.deb.debian.org/debian buster InRelease [122 
> kB]  
> Get:3 https://cdn-aws.deb.debian.org/debian-security buster/updates 
> InRelease [39.1 kB]
> Reading package lists... Done  
> N: Repository 'https://cdn-aws.deb.debian.org/debian buster InRelease' 
> changed its 'Version' value from '' to '10.1'
> E: Repository 'https://cdn-aws.deb.debian.org/debian buster InRelease' 
> changed its 'Suite' value from 'testing' to 'stable'
> N: This must be accepted explicitly before updates for this repository can 
> be applied. See apt-secure(8) manpage for details.
> N: Repository 'https://cdn-aws.deb.debian.org/debian-security 
> buster/updates InRelease' changed its 'Version' value from '' to '10'
> E: Repository 'https://cdn-aws.deb.debian.org/debian-security 
> buster/updates InRelease' changed its 'Suite' value from 'testing' to 
> 'stable'
> N: This must be accepted explicitly before updates for this repository can 
> be applied. See apt-secure(8) manpage for details.
> user@debian-10-clone-1:~$ 
>

NOTE: THIS IS IN A TEMPLATE VM!!! 

-- 
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/38f75d7c-c355-481e-9bed-9791fd7c5e82%40googlegroups.com.


[qubes-users] Qubes 4,02 Fails on sudo apt-get update

2019-09-26 Thread American Qubist 001
Never had trouble in Qubes 4.0 is it possible to access the repositories 
from this testing version? Here is the result of the command:


user@debian-10-clone-1:~$ sudo apt-get update
Hit:1 https://deb.qubes-os.org/r4.0/vm buster 
InRelease
Get:2 https://cdn-aws.deb.debian.org/debian buster InRelease [122 kB]  
Get:3 https://cdn-aws.deb.debian.org/debian-security buster/updates 
InRelease [39.1 kB]
Reading package lists... Done  
N: Repository 'https://cdn-aws.deb.debian.org/debian buster InRelease' 
changed its 'Version' value from '' to '10.1'
E: Repository 'https://cdn-aws.deb.debian.org/debian buster InRelease' 
changed its 'Suite' value from 'testing' to 'stable'
N: This must be accepted explicitly before updates for this repository can 
be applied. See apt-secure(8) manpage for details.
N: Repository 'https://cdn-aws.deb.debian.org/debian-security 
buster/updates InRelease' changed its 'Version' value from '' to '10'
E: Repository 'https://cdn-aws.deb.debian.org/debian-security 
buster/updates InRelease' changed its 'Suite' value from 'testing' to 
'stable'
N: This must be accepted explicitly before updates for this repository can 
be applied. See apt-secure(8) manpage for details.
user@debian-10-clone-1:~$ 

-- 
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/66f7ba71-f9f5-4b51-b41b-bd7e501d4868%40googlegroups.com.