[qubes-users] [PATCH v5.10] drm/i915/userptr: detect un-GUP-able pages early
If GUP-ineligible pages are passed to a GEM userptr object, -EFAULT is
returned only when the object is actually bound.
The xf86-video-intel userspace driver cannot differentiate this
condition, and marks the GPU as wedged. This disables graphics
acceleration and may cripple other functionalities such as VT switch.
Solve this by "prefaulting" user pages on GEM object creation, testing
whether all pages are eligible for get_user_pages() in the process.
On failure, return -EFAULT so that userspace can fallback to software
bliting.
This behavior can be controlled by using a new modparam
"gem_userptr_prefault", which is true by default.
The only known use for this patch is Qubes OS's GUI virtualization.
Userspace is expected to resort to DMA-BUF whenever possible.
Signed-off-by: Jinoh Kang
---
drivers/gpu/drm/i915/gem/i915_gem_userptr.c | 36 +
drivers/gpu/drm/i915/i915_params.c | 3 ++
drivers/gpu/drm/i915/i915_params.h | 1 +
3 files changed, 40 insertions(+)
diff --git a/drivers/gpu/drm/i915/gem/i915_gem_userptr.c
b/drivers/gpu/drm/i915/gem/i915_gem_userptr.c
index f2eaed6aca3d..65596d2b284f 100644
--- a/drivers/gpu/drm/i915/gem/i915_gem_userptr.c
+++ b/drivers/gpu/drm/i915/gem/i915_gem_userptr.c
@@ -712,6 +712,34 @@ static const struct drm_i915_gem_object_ops
i915_gem_userptr_ops = {
.release = i915_gem_userptr_release,
};
+static int i915_gem_userptr_prefault(unsigned long start,
+unsigned long nr_pages,
+bool readonly)
+{
+ struct mm_struct *mm = current->mm;
+ unsigned int gup_flags = (readonly ? 0 : FOLL_WRITE) | FOLL_NOWAIT;
+ int err = 0;
+
+ down_read(>mmap_sem);
+ while (nr_pages) {
+ long ret;
+
+ ret = get_user_pages(start, nr_pages, gup_flags, NULL, NULL);
+ if (ret < 0) {
+ err = (int)ret;
+ break;
+ }
+ if (ret == 0)
+ ret = 1; /* skip this page */
+
+ start += ret << PAGE_SHIFT;
+ nr_pages -= ret;
+ }
+ up_read(>mmap_sem);
+
+ return err;
+}
+
/*
* Creates a new mm object that wraps some normal memory from the process
* context - user memory.
@@ -796,6 +824,14 @@ i915_gem_userptr_ioctl(struct drm_device *dev,
if (!access_ok((char __user *)(unsigned long)args->user_ptr,
args->user_size))
return -EFAULT;
+ if (READ_ONCE(i915_modparams.gem_userptr_prefault)) {
+ ret = i915_gem_userptr_prefault((unsigned long)args->user_ptr,
+ args->user_size >> PAGE_SHIFT,
+ args->flags &
I915_USERPTR_READ_ONLY);
+ if (ret)
+ return ret;
+ }
+
if (args->flags & I915_USERPTR_READ_ONLY) {
/*
* On almost all of the older hw, we cannot tell the GPU that
diff --git a/drivers/gpu/drm/i915/i915_params.c
b/drivers/gpu/drm/i915/i915_params.c
index 7f139ea4a90b..c39766adeda2 100644
--- a/drivers/gpu/drm/i915/i915_params.c
+++ b/drivers/gpu/drm/i915/i915_params.c
@@ -197,6 +197,9 @@ i915_param_named_unsafe(fake_lmem_start, ulong, 0400,
"Fake LMEM start offset (default: 0)");
#endif
+i915_param_named(gem_userptr_prefault, bool, 0600,
+ "Prefault pages when userptr GEM object is created (default:true)");
+
static __always_inline void _print_param(struct drm_printer *p,
const char *name,
const char *type,
diff --git a/drivers/gpu/drm/i915/i915_params.h
b/drivers/gpu/drm/i915/i915_params.h
index 330c03e2b4f7..1169a610a73c 100644
--- a/drivers/gpu/drm/i915/i915_params.h
+++ b/drivers/gpu/drm/i915/i915_params.h
@@ -79,6 +79,7 @@ struct drm_printer;
param(bool, disable_display, false, 0400) \
param(bool, verbose_state_checks, true, 0) \
param(bool, nuclear_pageflip, false, 0400) \
+ param(bool, gem_userptr_prefault, true) \
param(bool, enable_dp_mst, true, 0600) \
param(bool, enable_gvt, false, 0400)
--
2.26.2
--
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/62703d3b-f66e-beb2-640b-63104201f24c%40gmail.com.
OpenPGP_signature
Description: OpenPGP digital signature
[qubes-users] [PATCH v5.4] drm/i915/userptr: detect un-GUP-able pages early
If GUP-ineligible pages are passed to a GEM userptr object, -EFAULT is
returned only when the object is actually bound.
The xf86-video-intel userspace driver cannot differentiate this
condition, and marks the GPU as wedged. This disables graphics
acceleration and may cripple other functionalities such as VT switch.
Solve this by "prefaulting" user pages on GEM object creation, testing
whether all pages are eligible for get_user_pages() in the process.
On failure, return -EFAULT so that userspace can fallback to software
bliting.
This behavior can be controlled by using a new modparam
"gem_userptr_prefault", which is true by default.
The only known use for this patch is Qubes OS's GUI virtualization.
Userspace is expected to resort to DMA-BUF whenever possible.
Signed-off-by: Jinoh Kang
---
drivers/gpu/drm/i915/gem/i915_gem_userptr.c | 36 +
drivers/gpu/drm/i915/i915_params.c | 3 ++
drivers/gpu/drm/i915/i915_params.h | 1 +
3 files changed, 40 insertions(+)
diff --git a/drivers/gpu/drm/i915/gem/i915_gem_userptr.c
b/drivers/gpu/drm/i915/gem/i915_gem_userptr.c
index 6d0cc90401c0..c86862a6f592 100644
--- a/drivers/gpu/drm/i915/gem/i915_gem_userptr.c
+++ b/drivers/gpu/drm/i915/gem/i915_gem_userptr.c
@@ -739,6 +739,34 @@ static const struct drm_i915_gem_object_ops
i915_gem_userptr_ops = {
.release = i915_gem_userptr_release,
};
+static int i915_gem_userptr_prefault(unsigned long start,
+unsigned long nr_pages,
+bool readonly)
+{
+ struct mm_struct *mm = current->mm;
+ unsigned int gup_flags = (readonly ? 0 : FOLL_WRITE) | FOLL_NOWAIT;
+ int err = 0;
+
+ down_read(>mmap_sem);
+ while (nr_pages) {
+ long ret;
+
+ ret = get_user_pages(start, nr_pages, gup_flags, NULL, NULL);
+ if (ret < 0) {
+ err = (int)ret;
+ break;
+ }
+ if (ret == 0)
+ ret = 1; /* skip this page */
+
+ start += ret << PAGE_SHIFT;
+ nr_pages -= ret;
+ }
+ up_read(>mmap_sem);
+
+ return err;
+}
+
/*
* Creates a new mm object that wraps some normal memory from the process
* context - user memory.
@@ -805,6 +833,14 @@ i915_gem_userptr_ioctl(struct drm_device *dev,
if (!access_ok((char __user *)(unsigned long)args->user_ptr,
args->user_size))
return -EFAULT;
+ if (READ_ONCE(i915_modparams.gem_userptr_prefault)) {
+ ret = i915_gem_userptr_prefault((unsigned long)args->user_ptr,
+ args->user_size >> PAGE_SHIFT,
+ args->flags &
I915_USERPTR_READ_ONLY);
+ if (ret)
+ return ret;
+ }
+
if (args->flags & I915_USERPTR_READ_ONLY) {
struct i915_address_space *vm;
diff --git a/drivers/gpu/drm/i915/i915_params.c
b/drivers/gpu/drm/i915/i915_params.c
index 296452f9efe4..90a03cb8ca57 100644
--- a/drivers/gpu/drm/i915/i915_params.c
+++ b/drivers/gpu/drm/i915/i915_params.c
@@ -178,6 +178,9 @@ i915_param_named(enable_gvt, bool, 0400,
"Enable support for Intel GVT-g graphics virtualization host
support(default:false)");
#endif
+i915_param_named(gem_userptr_prefault, bool, 0600,
+ "Prefault pages when userptr GEM object is created (default:true)");
+
static __always_inline void _print_param(struct drm_printer *p,
const char *name,
const char *type,
diff --git a/drivers/gpu/drm/i915/i915_params.h
b/drivers/gpu/drm/i915/i915_params.h
index d29ade3b7de6..c64866c256a3 100644
--- a/drivers/gpu/drm/i915/i915_params.h
+++ b/drivers/gpu/drm/i915/i915_params.h
@@ -76,6 +76,7 @@ struct drm_printer;
param(bool, disable_display, false) \
param(bool, verbose_state_checks, true) \
param(bool, nuclear_pageflip, false) \
+ param(bool, gem_userptr_prefault, true) \
param(bool, enable_dp_mst, true) \
param(bool, enable_gvt, false)
--
2.26.2
--
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/269651ca-7dc9-bbcc-7837-e91c988993f4%40gmail.com.
OpenPGP_signature
Description: OpenPGP digital signature
[qubes-users] [PATCH v4.19] drm/i915/userptr: detect un-GUP-able pages early
If GUP-ineligible pages are passed to a GEM userptr object, -EFAULT is
returned only when the object is actually bound.
The xf86-video-intel userspace driver cannot differentiate this
condition, and marks the GPU as wedged. This disables graphics
acceleration and may cripple other functionalities such as VT switch.
Solve this by "prefaulting" user pages on GEM object creation, testing
whether all pages are eligible for get_user_pages() in the process.
On failure, return -EFAULT so that userspace can fallback to software
bliting.
This behavior can be controlled by using a new modparam
"gem_userptr_prefault", which is true by default.
The only known use for this patch is Qubes OS's GUI virtualization.
Userspace is expected to resort to DMA-BUF whenever possible.
Signed-off-by: Jinoh Kang
---
drivers/gpu/drm/i915/i915_gem_userptr.c | 36 +
drivers/gpu/drm/i915/i915_params.c | 3 +++
drivers/gpu/drm/i915/i915_params.h | 1 +
3 files changed, 40 insertions(+)
diff --git a/drivers/gpu/drm/i915/i915_gem_userptr.c
b/drivers/gpu/drm/i915/i915_gem_userptr.c
index 961abb6ea18e..c1e680cf037d 100644
--- a/drivers/gpu/drm/i915/i915_gem_userptr.c
+++ b/drivers/gpu/drm/i915/i915_gem_userptr.c
@@ -748,6 +748,34 @@ static const struct drm_i915_gem_object_ops
i915_gem_userptr_ops = {
.release = i915_gem_userptr_release,
};
+static int i915_gem_userptr_prefault(unsigned long start,
+unsigned long nr_pages,
+bool readonly)
+{
+ struct mm_struct *mm = current->mm;
+ unsigned int gup_flags = (readonly ? 0 : FOLL_WRITE) | FOLL_NOWAIT;
+ int err = 0;
+
+ down_read(>mmap_sem);
+ while (nr_pages) {
+ long ret;
+
+ ret = get_user_pages(start, nr_pages, gup_flags, NULL, NULL);
+ if (ret < 0) {
+ err = (int)ret;
+ break;
+ }
+ if (ret == 0)
+ ret = 1; /* skip this page */
+
+ start += ret << PAGE_SHIFT;
+ nr_pages -= ret;
+ }
+ up_read(>mmap_sem);
+
+ return err;
+}
+
/*
* Creates a new mm object that wraps some normal memory from the process
* context - user memory.
@@ -815,6 +843,14 @@ i915_gem_userptr_ioctl(struct drm_device *dev,
(char __user *)(unsigned long)args->user_ptr,
args->user_size))
return -EFAULT;
+ if (READ_ONCE(i915_modparams.gem_userptr_prefault)) {
+ ret = i915_gem_userptr_prefault((unsigned long)args->user_ptr,
+ args->user_size >> PAGE_SHIFT,
+ args->flags &
I915_USERPTR_READ_ONLY);
+ if (ret)
+ return ret;
+ }
+
if (args->flags & I915_USERPTR_READ_ONLY) {
struct i915_hw_ppgtt *ppgtt;
diff --git a/drivers/gpu/drm/i915/i915_params.c
b/drivers/gpu/drm/i915/i915_params.c
index 295e981e4a39..702163d85921 100644
--- a/drivers/gpu/drm/i915/i915_params.c
+++ b/drivers/gpu/drm/i915/i915_params.c
@@ -174,6 +174,9 @@ i915_param_named(enable_dpcd_backlight, bool, 0600,
i915_param_named(enable_gvt, bool, 0400,
"Enable support for Intel GVT-g graphics virtualization host
support(default:false)");
+i915_param_named(gem_userptr_prefault, bool, 0600,
+ "Prefault pages when userptr GEM object is created (default:true)");
+
static __always_inline void _print_param(struct drm_printer *p,
const char *name,
const char *type,
diff --git a/drivers/gpu/drm/i915/i915_params.h
b/drivers/gpu/drm/i915/i915_params.h
index 6c4d4a21474b..86915d1fc303 100644
--- a/drivers/gpu/drm/i915/i915_params.h
+++ b/drivers/gpu/drm/i915/i915_params.h
@@ -66,6 +66,7 @@ struct drm_printer;
param(bool, disable_display, false) \
param(bool, verbose_state_checks, true) \
param(bool, nuclear_pageflip, false) \
+ param(bool, gem_userptr_prefault, true) \
param(bool, enable_dp_mst, true) \
param(bool, enable_dpcd_backlight, false) \
param(bool, enable_gvt, false)
--
2.26.2
--
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/d216ab34-c844-0812-2c30-39630430f7a2%40gmail.com.
OpenPGP_signature
Description: OpenPGP digital signature
[qubes-users] Help me test fixes for Intel IGD graphical artifacts on Qubes R4.0
When using some Intel integrated graphic cards on Qubes R4.0, screen glitches may manifest after switching VTs or entering suspend mode. A known workaround does exist for this bug, which is to add a configuration file with the following contents within /etc/X11/xorg.conf.d: > Section "Device" > Identifier "Intel Graphics" > Driver "modesetting" > Option "AccelMethod" "glamor" > Option "DRI" "3" > EndSection However, the X11 modesetting driver version in Fedora 25 has its own drawbacks: * It freezes briefly when re-configuring monitors (e.g. plugging in an external monitor or changing screen resolution) * XRandR keystone support is buggy To remediate this, I've patched the Linux i915 driver and it has been working fine for months. Only the patch for Linux 4.19 has been tested. If anyone is affected by the issue, please feel free to test the follow-up patches and give some feedback here. See also: * https://github.com/QubesOS/qubes-issues/issues/5244 * https://github.com/QubesOS/qubes-issues/issues/5377 * https://github.com/QubesOS/qubes-issues/issues/5460 Cheers, Jinoh Kang -- 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/314ba374-891c-92c2-743b-89b3fef40233%40gmail.com. OpenPGP_signature Description: OpenPGP digital signature
[qubes-users] Bringing guest OS in PVH vs. HVM
I am looking for a small footprint VM for a server, such as POP3/SMTP, or DNS. Qubes developers did a great job by providing a readily available Fedora/Debian minimal templates. It is is not clear whether their footprint is small compared to say Slackware/Gentoo. I am exploring an opportunity to use a different Linux distribution in order to further reduce the footprint. This quest led me to the following questions. What is a difference between bringing a guest OS in PVH vs HVM? 1) An installation of a guest OS in HVM is already covered in "Installing an OS in an HVM" section (see https://www.qubes-os.org/doc/standalone-and-hvm/#creating-an-hvm). So far, so good. 2) What about the installation of a guest OS in PVH? Is it a matter of performing (1), and then pressing a "magic button" to switch the virtualization mode from HVM to PVH? Or, is it a more elaborate process? 3) Let's assume that the guest OS is Slackware. If I understand correctly, (1) is a lighter mode of virtualization compared to (2), resulting in reduction of the memory footprint. How does one gets there? In particular, when the respective template VM is not readily available? 4) Alternatively, let's assume that the guest OS is Gentoo. Thanked to the community support, the minimal template is readily available. Where do you go form here? Does this template represent the outcome of going through all the installation steps (see Installing Gentoo chapter in https://wiki.gentoo.org/wiki/Handbook:X86#Installing_Gentoo)? And any customization of the template only requires installing additional packages? Or, further reduction of the footprint requires you to redo a subset of the installation steps, such as configuring the Linux kernel, configuring the system, and configuring the system tools? It would be nice to hear any experience in this area. -- 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/478760545.3024859.1608756380817%40mail.yahoo.com.
[qubes-users] Possible to run something like recoll in dom0 to index appvms?
I try to be organized and make sure all files are in the appvms they are supposed to be but while it works most of the time it doesnt always. As a result I was wondering if it was possible (aknowledging one would have to trust recoll, its in the fedora repo for what thats worth) if it was possible to install recoll in dom0 and have it search/index files in the different appVMs? I am also open to using something a bit safer (starting somewhere along the lines of ls -l > bigindexfile.txt maybe?) so any suggestions would be really apprecaited. It would be nice to have a gui I could search but just grepping a big (compressed?) index file from a dom0 term i guess would be workable? -- 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/63093dde-7f86-1a46-3db5-3e3ddd339804%40posteo.co.
[qubes-users] Re: HCL - HP ProBook 450 G7
yml was corrupt in last post. Here's it in plaintext: = --- layout: 'hcl' type: 'notebook' hvm: 'yes' iommu: 'yes' slat: 'yes' tpm: 'unknown' remap: 'yes' brand: | HP model: | HP ProBook 450 G7 bios: | S71 Ver. 01.05.04 cpu: | Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz cpu-short: | FIXME chipset: | Intel Corporation Device [8086:9b61] (rev 0c) chipset-short: | FIXME gpu: | Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) gpu-short: | FIXME network: | Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) Realtek Semiconductor Co., Ltd. Device c822 memory: | 16221 scsi: | usb: | 1 versions: - works: 'FIXME:yes|no|partial' qubes: | R4.0 xen: | 4.8.5-25.fc25 kernel: | 4.19.152-1 remark: | FIXME credit: | FIXAUTHOR link: | FIXLINK --- -- 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/20201223152040.GA10054%40mail.michaelaltfield.net.
[qubes-users] Re: HCL - HP ProBook 450 G7
Attaching HCL Support Files after attempting with the latest development release of QubesOS at the time of writing = Qubes Release 4.0.4-rc1 All of the same issues are present as with the latest stable release. QubesOS is *not* compatible with the HP ProBook 450 G7. -- 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/20201223151520.GA8730%40mail.michaelaltfield.net. Qubes-HCL-HP-HP_ProBook_450_G7-20201223-093941.cpio.gz Description: application/gzip Qubes-HCL-HP-HP_ProBook_450_G7-20201223-093941.yml Description: Binary data
[qubes-users] HCL - Asus ZenBook 13 UX331 (UX331UAL)
To whom it may concern: The Asus UX331 laptop is compatible with QubesOS 4.0. Everything works great, except: 1. A few times per day, the touchpad will just suddenly not do anything. I can't click, tap, or move the mouse around. The solution appears to be just to wait about 5 minutes and it starts working again. Or just use an external USB mouse. 2. It never recovers from sleep or hibernate. -- 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/20201223141202.GA24193%40mail.michaelaltfield.net. --- layout: 'hcl' type: 'notebook' hvm: 'yes' iommu: 'yes' slat: 'yes' tpm: 'unknown' remap: 'yes' brand: | ASUSTeK COMPUTER INC. model: | ZenBook 13 UX331UAL bios: | UX331UAL.308 cpu: | Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz cpu-short: | FIXME chipset: | Intel Corporation Device [8086:5914] (rev 08) chipset-short: | FIXME gpu: | Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) gpu-short: | FIXME network: | Intel Corporation Wireless 8265 / 8275 (rev 78) memory: | 16240 scsi: | usb: | 1 versions: - works: 'yes' qubes: | R4.0 xen: | 4.8.5-14.fc25 kernel: | 4.19.94-1 remark: | Touchpad randomly becomes unresponsive for a few minutes a couple times per day. Otherwise it works great. credit: | FIXAUTHOR link: | FIXLINK ---
[qubes-users] HCL - HP ProBook 450 G7
Attaching HCL Support Files > To whom it may concern: > > The HP Probook 450 G7 is not compatible with QubesOS 4.0. > > Last week I tried to install QubesOS 4.0.3 onto a new HP laptop model > Probook 450 G7. It failed in the following ways: > > 1. The touchpad didn’t work during the install process or after install > > 2. It ran extremely slow (just dragging the mouse across the screen had > obvious lag). I confirmed that VTx and Vtd were enabled in BIOS). > > 3. After install, it did not detect my wireless card > > With some work, it may be possible to fix the drivers for the wireless > card and the touchpad. And maybe somehow optimize virtualization. But at > that point, I gave up and installed xubuntu on this machine which > resolved all 3x issues above. > > Unfortunately, I cannot run `qubes-hcl-report` on this machine, but I do > want this entry to be added to the Hardware Compatibility list so that > nobody else attempts to purchase this laptop with the hopes to run > QubesOS on it. -- 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/00008e6585058b2ff2c4%40google.com. Qubes-HCL-HP-HP_ProBook_450_G7-20201223-080822.cpio.gz Description: application/gzip --- layout: 'hcl' type: 'notebook' hvm: 'yes' iommu: 'yes' slat: 'yes' tpm: 'unknown' remap: 'yes' brand: | HP model: | HP ProBook 450 G7 bios: | S71 Ver. 01.05.04 cpu: | Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz cpu-short: | FIXME chipset: | Intel Corporation Device [8086:9b61] (rev 0c) chipset-short: | FIXME gpu: | Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) gpu-short: | FIXME network: | Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) Realtek Semiconductor Co., Ltd. Device c822 memory: | 16221 scsi: | usb: | 1 versions: - works: 'FIXME:yes|no|partial' qubes: | R4.0 xen: | 4.8.5-14.fc25 kernel: | 4.19.94-1 remark: | FIXME credit: | FIXAUTHOR link: | FIXLINK ---
Re: [EXT] [qubes-users] Can a virus be transfered from a USB storage device before or after attaching it to a App VM ?
The window appeared about a little bit lower than the middle of the screen. onsdag den 23. december 2020 kl. 00.02.55 UTC+1 skrev awokd: > ME: > > When I inserted my USB storage device in my Qubes OS pc after login to > > Qubes OS, their appeared a small transparent window (before I mounted the > > USB device to a VM) where I only could see its frame. > > > > I then wondered if it could be caused of a virus that was planted on the > > USB storage device that I only have used to transfer files between two > > Qubes OS pc's. > > > > And if so, how can I get rid of the virus or rootkit on the Qubes OS pc ? > > If it was in the top right corner, it was a message from Qubes telling > you a device was connected. Sometimes the text doesn't always show up. > > -- > - 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/13d4d889-3260-4cde-9b95-28900ebece8en%40googlegroups.com.
Re: [qubes-users] Disable lock screen / screenshot question
On 12/22/20 10:18 PM, Jarrah wrote:
How do you disable the automatic screen lock? I have the screensaver
disabled and the lock screen option unchecked but it still locks after a
few minutes.
For me, there is a "presentation mode" on the battery icon (which shows
on both desktop and laptop) that disables the screen lock.
Also when using the screenshot function in system tools, is it possible to
save to the AppVM file system you are currently using rather than to Dom0?
Or how do I access it once it is saved to Dom0?
You should be able to get them to your AppVM using `qvm-copy-to-vm ` from the terminal.
Better: create in dom0 a file containing:
#!/bin/bash
qvm-copy-to-vm $(zenity --entry --title='Send to VM' --text='Destination
VM') "${BASH_ARGV[@]}"
Save that as an executable script, such as "~/.local/bin/send-to-vm.sh".
Then, open dom0 file manager, right click any png, click open with other
application, and under "use a custom command" enter "send-to-vm.sh %s".
This "registers" the script in the application list.
Then, when you take a screenshot, instead of choosing "save", choose
"open with..." and see if your script shows up in the list of available
applications. If still not, you might have to write a simple .desktop
file in ~/.local/share/applications in order for it to show
up as an option.
--
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/16a62446-060f-1faf-8cb8-daedeb67d440%40web.de.
