Chris Laprise:
On 5/22/19 3:17 PM, Claudia wrote:
Thanks for all the info! All good news except for the part about
BIOS/UEFI feature support, which doesn't come as a surprise.
I understand that, for maximum certainty, one should look at high-end,
business-class, Linux-friendly product lines
Stefan Schlott:
On 6/18/19 12:39 PM, cycle via qubes-users wrote:
recently I logged in into dropbox with a browser from my qubes box and
had to confirm my login. Afterwards I got a mail saying that there was
an login attempt from:
*Desktop-Client Linux 4.14.116-1.pvops.qubes.x86_64
*How can
Hello,
I've read the system requirements page, the HCL, and the "advice on
finding a Qubes compatible notebook" thread, all of which seem to refer
to Intel almost exclusively. I've also done some searching around, but
there seems to be very little information about Qubes' compatibility on
Chris Laprise:
On 5/22/19 9:44 AM, Claudia wrote:
Hello,
I've read the system requirements page, the HCL, and the "advice on
finding a Qubes compatible notebook" thread, all of which seem to
refer to Intel almost exclusively. I've also done some searching
around, but there seems
27casanov...@gmail.com:
Any links on this explaining it in depth and showing how to sett it up?
I looked in to Qubes site but dident find it.
You should be fine without doing any packet capture. As long as you
install and use the whonix VM and leave most everything as default, you
davidmizr2...@gmail.com:
Hi, i'm asking because my hardware is not compatible with qubes 4.0
Is not safe to use Qubes OS 3.2?
Thanks
Just curious, I'm guessing it's because of the VT-d requirement?
Like others have said, 3.2 is still probably safer than some random distro.
I wish we could
27casanov...@gmail.com:
Hi, Im trying to install Wasabi on Qubes.
Downloading works fin. Then I klick on the downloaded file and a new folder
apears (I guse the files has bin un packed or something). Theres a bunch of
files in there. And I have no ideer what to do from there on.
This might
The "Custom Installation" doc gives instructions about how to create a
non-default dm-crypt partition, or other custom setup, and install Qubes
to it. But when I follow these instructions on R4.0.1, and try to assign
my dm-crypt device to "/", I get a message something like
"You must create a
Andrew David Wong:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 31/08/2019 11.23 AM, Claudia wrote:
The "Custom Installation" doc gives instructions about how to
create a non-default dm-crypt partition, or other custom setup, and
install Qubes to it. But when I follow these in
Andrew David Wong:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/09/2019 8.03 AM, Claudia wrote:
Andrew David Wong:
On 31/08/2019 11.23 AM, Claudia wrote:
The "Custom Installation" doc gives instructions about how to
create a non-default dm-crypt partition, or other cu
drogo:
On Sunday, June 24, 2018 at 10:12:17 PM UTC-4, cooloutac wrote:
On Friday, June 15, 2018 at 5:59:46 PM UTC-4, drogo wrote:
My newly built system is unable to suspend. The process starts, but
fails and ends up with just a locked screen. This is a desktop, so there
shouldn't be any
drogo:
On Tuesday, September 10, 2019 at 5:22:32 PM UTC-4, Claudia wrote:
drogo:
On Sunday, June 24, 2018 at 10:12:17 PM UTC-4, cooloutac wrote:
On Friday, June 15, 2018 at 5:59:46 PM UTC-4, drogo wrote:
My newly built system is unable to suspend. The process starts, but
fails
'awokd' via qubes-users:
duc...@disroot.org:
This is an issue that's been reported before, and some solutions appear
to be out there, including re-installing with Legacy boot. However, they
all seem to involve modifying the installer prior to installation or
making changes via a GRUB menu. I'm
'awokd' via qubes-users:
dimi:
Could not find a solution how, if even possible to pick which kernel to
boot or/and modify kernel parameters before booting like i am used from
grub by pressing 'e'.
Does UEFI Boot support this or/and how can i safely switch my setup to grub
boot? I would like to
'awokd' via qubes-users:
Claudia:
So I'm not sure why it would be unsafe. In fact I'm thinking about
manually enabling grub (in UEFI mode) just to ease troubleshooting in
the future should I ever run into any boot issues. Just my take, but I
could be wrong.
It wasn't the boot sequence itself
brendan.h...@gmail.com:
On Friday, July 26, 2019 at 1:24:57 PM UTC-4, Claudia wrote:
Just to humor myself, I was going to try testing if I could hear sound
from Qubes after resume, but it seems audio isn't working at all. Which
is a whole 'nother problem. Aplay says "... unable to open
Claudia:
Chris Laprise:
On 7/22/19 11:38 AM, Claudia wrote:
So I finally got around to doing this.
Qubes works and all the basic features are supported, VT-x VT-d, and
so on, as far as I can tell.
One major issue, hardware/firmware-wise:
1) It doesn't come back from suspend. The fan stops
Chris Laprise:
On 7/22/19 11:38 AM, Claudia wrote:
So I finally got around to doing this.
Qubes works and all the basic features are supported, VT-x VT-d, and
so on, as far as I can tell.
One major issue, hardware/firmware-wise:
1) It doesn't come back from suspend. The fan stops
Daniil Travnikov:
On Tuesday, October 16, 2018 at 4:58:31 PM UTC+3, qube...@tutanota.com wrote:
Hi, I would like to ask you about experiences with the i2p in Qubes 4. What setup would you consider as
"best" in case I would like to use i2p without routing it through Tor first? I read the >Use
Chris Laprise:
My experience is that consumer BIOS will result in poor suspend
compatibility.
Not surprising :( But there are indeed some Thinkpads, MSI, System76,
Purism, and other high-end business-class machines on the HCL with
suspend not working. So it's still a bit of crapshoot. Just
Chris Laprise:
On 5/22/19 3:17 PM, Claudia wrote:
Thanks for all the info! All good news except for the part about
BIOS/UEFI feature support, which doesn't come as a surprise.
I understand that, for maximum certainty, one should look at high-end,
business-class, Linux-friendly product lines
I hope I did this right. If not, please let me know and I'll try to fix it.
-
This free account was provided by VFEmail.net - report spam to ab...@vfemail.net
ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the
NSA's
asn't made it to Qubes. Still way too early to say, though.
Claudia:
Have you tried suspend/resume with no VMs running at all? This can be
accomplished by manually shutting down appVMs then service VMs, or with
the command 'qvm-shutdown --all --force --wait'.
Pretty sure I did, but
tetrahedra via qubes-users:
On Sun, Sep 29, 2019 at 02:42:29PM +, Claudia wrote:
You can try viewing your active tor settings in Nyx (preinstalled in
Whonix) rather than from torrc directly. Just in case some setting is
being overridden or something like that. See
https://www.whonix.org
tetrahedra via qubes-users:
On Sun, Sep 22, 2019 at 02:51:00PM +, 'awokd' via qubes-users wrote:
tetrahedra via qubes-users:
Is there any way to automatically do stream isolation on a per-VM basis?
Right now it appears this is not necessarily the case -- the network
traffic of AppVMs A
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
tetrahedra via qubes-users:
On Fri, Sep 27, 2019 at 01:37:06PM +, Claudia wrote:
Isolating apps in the same VM is a different issue, but you're saying
traffic from different VMs is appearing to come from the same address?
Hmm, that definitely should not be happening. VM isolation
'Jackie' via qubes-users:
Sven Semmler:
In addition to my fairly standard dvm based on whonix-ws connected to
sys-whonix based on whonix-ws I have now done the following:
1) cloned sys-whonix to sys-whonix-id
2) created app-signal based on whonix-ws
3) installed signal in whonix-ws
4)
tetrahedra via qubes-users:
On Mon, Sep 30, 2019 at 08:05:44AM +, Claudia wrote:
Glad to hear it's working. I guess I should have asked at the
beginning... What brought you to the conclusion they were using the
same circuits? I assumed you were using check.torproject.org or
another "
ehag...@gmail.com:
Den torsdag 27 juni 2019 kl. 10:49:43 UTC-4 skrev eha...@gmail.com:
This takes som explanation. With capita I mean that box that comes up when
preforming a registration or setting up a new account at a webbpage. In order
to confirm thar youre not a robot and so on.
I tried
Matthias Kolja Miehl:
Hey Luc,
On 07/09/2019 05:57 PM, Luc libaweb wrote:
just a question, why use Google with the positioning of Qubes OS? There are so
many other alternatives?
Just do a search google groups to know anyone who uses/particpate to Qubes OS,
contradictory no ?
This is the
Russ:
Hi,
Is it possible to move core files to an ssd after the operating system has
been installed on an internal hdd?
I'd like to move to the ssd to increase speed, it is now physically install
(wasn't before). Ideally, this would not require reinstalling to the entire
system.
It's
Andrew David Wong:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2019-10-31 10:01 AM, Claudia wrote:
re:
https://www.mail-archive.com/qubes-users@googlegroups.com/msg30379.html
So as I understand, there were two problems with rc1. Bug #5149,
which was closed as resolved three days ago
The last message on the console is always "[OK] Started Monitoring of
LVM2 mirrors, snapshots, etc. using dmeventd or progress polling" at
which point it just hangs. The cursor doesn't blink, and pressing enter
doesn't do anything. Some keys cause it to beep, though, and it does
respond to
Claudia:
Claudia:
The last message on the console is always "[OK] Started Monitoring of
LVM2 mirrors, snapshots, etc. using dmeventd or progress polling" at
which point it just hangs. The cursor doesn't blink, and pressing
enter doesn't do anything. Some keys cause it to be
'Zeko' via qubes-users:
Hello
I managed to screw up my Qubes install and it fails at boot, resetting every
time. However, that happens after the partition gets mounted and I screwed it
up without having my /boot partition (a USB pendrive, since I multiboot)
mounted, so I expect I'll be able
Claudia:
The last message on the console is always "[OK] Started Monitoring of
LVM2 mirrors, snapshots, etc. using dmeventd or progress polling" at
which point it just hangs. The cursor doesn't blink, and pressing enter
doesn't do anything. Some keys cause it to beep, though, a
Andrew David Wong:
I asked Marek about this. Here is his reply:
"Basically the answer is 'current-testing' is disabled by default,
even in rc builds. This may mean some packages on the rc installation
image are newer than those in the stable repository, but the update
mechanism won't try to
rathol obcheek:
Dear all, after installing Qubes 3.2.1 on a laptop (HP 255 G5), I want to
migrate the Windows system previously installed on there. Furthermore,
there is an Opensuse (Leap 15.1) installed on a second laptop I want to
migrate into Qubes as well.
My thought is to image both
Rafael Reis:
Hey,
So I was able to figure this one out on my own.
The installer expects you to format filesystems prior to allocating the
mountpoints. I honestly wasn't sure which FSes I should use. So i checked
out what auto mode would do, and mimicked it with the custom created pools.
As
Dane Goodwin:
Hey all
It's new laptop time. i got a lenovo legion y540 with the nvidia RTX
graphics card, and got qubes installed on it. Everything works great except
HDMI output. I want to fill in an HCL submission, but want to try get this
sorted before doing so.
The problem I'm having is
Guerlan:
When I press hibernate, nothing happens. Was it supposed to work? If so,
how can I debug what's happening?
No. Xen doesn't support hibernate (suspend-to-disk). And XFCE doesn't
check if it's running under Xen, so it still shows a button for
hibernate anyway.
Audio works fine in Fedora 25-1.3 livecd and codec is detected as
"ALC3234 Analog", alsa version k4.8.6-300.fc25.x86_64. It also works in
F30.
On Qubes 4.0.2-rc2, I can't get audio to work at all. Codec shows up as
"Generic Analog" in `aplay -l`, in alsamixer chip (codec) is "Generic
uot;
Date: Wed, 13 Nov 2019 19:11:55 +0000
From: Claudia
To: qubes-users
Audio works fine in Fedora 25-1.3 livecd and codec is detected as
"ALC3234 Analog", alsa version k4.8.6-300.fc25.x86_64. It also works in F30.
On Qubes 4.0.2-rc2, I can't get audio to work at all. Codec s
Claudia:
# tar -C / -cvzf ~/boot-backup.tar.gz boot/
# qubes-dom0-update grub2-efi
# chmod ugo+x /etc/grub.d/10_linux
# echo GRUB_CMDLINE_LINUX=\"$(cat /boot/efi/EFI/qubes/xen.cfg | grep
kernel | cut -d ' ' -f 4- | head -n 1)\" >> /etc/default/grub
# grub2-mkconfig -o /boo
'awokd' via qubes-users:
Claudia:
So I was wondering, is it possible to run the Qubes dom0 kernel directly
on the hardware instead of under Xen? How might one go about this? And
how much work would it involve?
I've had similar troubleshooting needs. Closest I found was to download
Fedora 25
Germann Fabio:
Hi qubes-users,
Recently I tried to present a presentation using LibreOffice on qubes. I'm
not able to get into the presentation mode where I got the fullscreen
presentation on the HDMI display and the presentation mode screen (current
slide, next slide and comments) on the
'Zeko' via qubes-users:
‐‐‐ Original Message ‐‐‐
On Saturday, November 9, 2019 4:54 PM, Claudia wrote:
'Zeko' via qubes-users:
Hello
I managed to screw up my Qubes install and it fails at boot, resetting every
time. However, that happens after the partition gets mounted and I
'Zeko' via qubes-users:
Hello
I ran sudo qubesctl state.sls qvm.sys-usb on a LUKS install with USB keyboard
and mouse. (Yeah bad idea)
I use a removable drive to boot since I multiboot on that PC and the drive was
unmounted at the time so the command reported that 4 out of 5 steps succeeded
I've recently run into some hardware problems in Qubes which are not
present in the equivalent Fedora version (F25). I have a feeling Xen may
be a likely culprit, just simply because of how Xen controls the use of
certain hardware for security reasons (VT-d, and such).
If it were possible to
Anac:
Hi all,
Is it just me or does the iso really not fit onto a regular DVD? I tried
several burn programs - same result. The 4.8 GB iso doesn't fit onto a
4.7 GB DVD. Is a double-layer DVD required or is it possible to delete
some seldomly needed parts from the iso? Or did I catch a
Sphere:
However, a ram stick just died on me this week and I badly need all the RAM
that I could get. Even right now, my dom0 is actively using just about 940
MB worth of RAM... which is why I think it would be best if I could
permanently allocate 2048M to dom0 instead of 4096M for my case.
Sphere:
https://discussions.citrix.com/topic/354913-error-increasing-dom0-memory-in-61/
So I am looking to reduce the max set on dom0_mem because a considerable
amount of ram is being wasted (roughly 1500 MB) and I want to use it on my
RAM heavy appvms instead
I've been searching all over the
Claudia:
By default network cards are assigned to sys-net and are not visible in
dom0 (as far as I know). Open the Qubes Manager -> sys-net -> VM
settings -> Devices tab, and make sure your network card is assigned to
it. So you need to run lsusb or lspci from within sys-net, not
Qubes User:
Thank you for your help.
Happy to do what I can.
First, if you can, please generate an HCL report on the machine and send
it to the mailing list. This will tell us some basic info about your
machine so we have a better idea what we're troubleshooting. (It also
helps the Qubes
Frédéric Pierret (fepitre):
Before end of the month we hope to have a testing ISO for dev purpose.
Currently we are on upgrading Fedora installer which have drastically
changed the way of creating ISO.
Awesome. I'll keep my eye out for it. Thanks.
Qubes User:
I just installed Qubes on a new laptop. I'm trying to do some basic things
not listed on https://www.qubes-os.org/getting-started/
1. How do I get connected to my wi-fi?
The networkmanager applet should appear in the task tray (next to the
clock). Just click on that and select a
tetrahedra via qubes-users:
see the corresponding issue:
https://github.com/QubesOS/qubes-issues/issues/5508
The tldr is that ever since I upgraded to fedora-30, sys-net has started
dying intermittently (or less intermittently, nearly every time) I put
my laptop to sleep.
This is really
Master Node:
I will try to not top post iv read how it's done but it does not seem to have
worked on my last msg, I dont see any other way to rely and I'm replying to the
last msg of this thread.
My intel cpu is a i7-4930MX with haswell gpu integrated. As I said before my
whole system worked
quix...@tutanota.com:
Hi, I have tried installing Qubes on two seperate usb sticks using two
different methods (etcher and pendrivelinux. The installation completes
successfully, however when I boot Qubes, it shows the startup coding lanuguage
and then Qubes will automatically shut down and
Master Node:
Hey I recently made a post about x start up failing, I'm thinking this was from
trying to run a raid configuration between two m2 drives in a sata adapter
case. After I stopped doing that I have not seen the same error.
I guess anything is possible. Glad to hear it's solved.
Myros:
Hello,
I'm a relatively new user and not very fit at this.
Windows and Ubuntu i had before could handle the sound very good, but since
i installed Qubes it sounds like a metal bin.
Any suggestions what i can do?
Greez Myros
What soundcard do you have? And what driver is it using?
brendan.h...@gmail.com:
Disposable VMs were not developed with anti-forensics in mind (e.g. no
protection in jurisdictions where you can be forced to hand over your drive
password
Never thought about it, but that makes sense. I can see how it would be
easy to confuse "non-persistence of
I'm wondering what the best way is to go about installing two instances
of Qubes 4.1 on the same machine, which are more or less independent of
each other.
It's fairly easy to dual boot different OSes because they each have
their own EFI directory, e.g. /boot/efi/EFI/{qubes,fedora,ubuntu},
'marioski' via qubes-users:
Hi,
simple question:
Can i choose different OS (Windows, Linux, MacOS) in Qubes OS?
as if I had a trial boot on my pc reserved for Qubes OS
thanks
You mean dual booting?
On UEFI systems, Qubes 4.0 will install the Xen loader and create a UEFI
boot menu entry
Claudia:
[...]
So, to recap what I've found so far:
Fedora 25 live cd: works
Qubes without Xen: works
Qubes with Xen: codec probe error
Qubes with Xen, VT-x & VT-d disabled: codec probe error
Qubes with Xen, single_cmd=1: codec detected, but no sound
[...]
Just following up. Audio w
josefh.maier via qubes-users:
Hello list,
I heard that a Qubes-user was forced to hand over the Qubes-password, and that
a forensic examiner was able to restore artifacts of a deleted disposeable form
the harddisk...
Is this story possible? And what's the best aprroach to wipe diskspace used
Master Node:
My 3rd post on this forum seems like the only person who offers to pay some one
over and over and yet one of the few that doesnt even get a response back, this
is getting depressing.
I thought I replied to this thread but it appears I didn't. I must have
dreamt it. Anyway,
Steve Coleman:
On 2019-12-10 10:26, rickey wrote:
Good morning Everyone,
I have installed previously Qubes 3.2.1 on a Dell small form factor
desktop pc, and lenovo x120e, and I was able to use them.
When I tried to install the Qubes versions mentioned above on the same
hardware, it is showing
Bernhard:
By default network cards are assigned to sys-net and are not visible
in dom0 (as far as I know). Open the Qubes Manager -> sys-net -> VM
settings -> Devices tab, and make sure your network card is assigned
to it. So you need to run lsusb or lspci from within sys-net, not
dom0. You
Claudia:
I looked at your HCL report, and given the number of issues you're
facing, it might be worth trying a R4.1 pre-release build, which is
based on F29 and Xen 4.12. These builds are considered unstable, but you
very well might end up with fewer headaches than the older stable releases
Qubes User:
Hi everyone,
Thank you for all your help and discussion. I posted the HCL for the device
I'm troubleshooting -- the latest Lenovo Flex 14 with the i5-10210U. You
can find it here:
https://groups.google.com/forum/#!topic/qubes-users/kamMImlGMNQ
I'm guessing the plan is to set up
AndrewS:
Good evening
First post here...
I made a bootable USB istaller for Qubws 4.0.1 using the dd comand in Linux
Mint 19.2. This gave me a USB stick that booted OK on the (rather old, and
totally unsuitable for Qubes I know) laptop I made it on. When I tried the
stick in a more modern
Arild:
I'm interested in running a script in dom0 at 30 min intervals, but it
seems that cron and systemd timers might be limited in dom0. Is that true?
I'm not sure I understand. Limited how?
You should be able to make a .service file and set up your .timer file like:
[Timer]
Is there any way to get a newer Xen on the R4.0 series? Short of
building it myself, that is. Current-testing and unstable both appear
have the newest at 4.8.5-13 (current is 4.8.5-12), despite R4.1 being on
Xen 4.12. Does Qubes receive updates for newer versions of Xen? Or is
the Xen version
Andrew David Wong:
Please note that no user action is required regarding the OS version in
dom0. For details, please see our Note on dom0 and EOL. [6]
[6] https://www.qubes-os.org/doc/supported-versions/#note-on-dom0-and-eol
Is it *possible* to upgrade dom0 to, say, F30, if we wanted to? I
Frédéric Pierret:
On 2019-12-02 01:01, Andrew David Wong wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2019-11-28 1:16 AM, Claudia wrote:
Andrew David Wong:
Please note that no user action is required regarding the OS
version in dom0. For details, please see our Note on dom0
Chris Laprise:
On 10/24/19 9:17 AM, tetrahedra via qubes-users wrote:
From Ratliff's "The Mastermind":
"...they were told to close the computer immediately. The TrueCrypt
software would be activated as soon as the laptop lid was shut."
While most Qubes users are probably not interested in
re: https://www.mail-archive.com/qubes-users@googlegroups.com/msg30379.html
So as I understand, there were two problems with rc1. Bug #5149, which
was closed as resolved three days ago. And an unknown "pending security
issue".
Where can we find more info on this pending security issue? I
Guerlan:
In KVM with Qemu I used a lot of VM state saving, where I could save the
entire VM to disk and restore that. Since my SSD is very fast that only
took 5 seconds in average, so it was very useful. Specially, since I cannot
put my laptop to sleep and hibernate wont work either, my only
'awokd' via qubes-users:
And to follow on, is there a way to tell if I have 4.0 or 4.0.1 or
4.02rc2?
If it's like previous releases, if you have Qubes 4 patched to the
"current" (default) repository, you are running the latest point release
(4.0.1). If you have it patched to "current-testing",
Rafael Reis:
Hey everyone!
I'd like to know where I can find doc / information on how the UEFI boot
process of Qubes is configured / structured. Since the files repeat
themselves on different folders at /boot, I'm unsure how / what to change
in order to use a freshly generated ramdisk image.
Claudia:
Claudia:
Claudia:
The last message on the console is always "[OK] Started Monitoring of
LVM2 mirrors, snapshots, etc. using dmeventd or progress polling" at
which point it just hangs. The cursor doesn't blink, and pressing
enter doesn't do anything. Some keys cause
Claudia:
Claudia:
# tar -C / -cvzf ~/boot-backup.tar.gz boot/
# qubes-dom0-update grub2-efi
# chmod ugo+x /etc/grub.d/10_linux
# echo GRUB_CMDLINE_LINUX=\"$(cat /boot/efi/EFI/qubes/xen.cfg | grep
kernel | cut -d ' ' -f 4- | head -n 1)\" >> /etc/default/grub
# grub2-mkconfig
Claudia:
(cc xen-users; see original message below)
So I was able to boot Qubes as a regular kernel, without Xen, and the
codec is properly detected as Realtek ALC3234. Same exact kernel, same
commandline, same userspace, just without Xen. (Xen 4.8.5-11.fc25)
Any ideas on what might
Tomáš Vondra:
On Saturday, October 5, 2019 at 7:45:40 PM UTC+2, Tomáš Vondra wrote:
On Friday, October 4, 2019 at 4:36:57 PM UTC+2, Claudia wrote:
...
There is a pre-release 4.1 iso available.
https://openqa.qubes-os.org/tests/3021
<https://www.google.com/url?q=https%3A
Guerlan:
Whenever I close the lid of the notebook, when I open again, I see the
keyboard light lightning up but the screen never lights and I have to
reboot.
Is there a fix for it?
It sounds like suspend/resume isn't working correctly on your laptop
under Qubes. Does the same thing happen
Tomáš Vondra:
Hi,
I'm still struggling with the suspend issue, unfortunately, and I'm kinda
stuck so I'd appreciate some ideas what to try.
Everything else seems to be working, but during suspend the laptop gets
stuck (black screen, but I can hear the fans still spinning). And then it
does not
Guerlan:
I did the HCL report and sent.
I tried the manual sleep and it wont work, the same thing happens as when I
close the lid: the keyboard goes off and the screen goes blank and nothing
returns when I open. I tried pressing the power button but also didn't work.
The workaround isn't good
Guerlan:
I installed some drivers on a sys-net-2 VM. Does that men they are
installed on the template then?
No. Probably not. The root directory is shared, but only for reading.
Any changes are visible only within that VM, and are lost on reboot.
Exceptions are anything mapped to /rw (e.g.
I just wanted to drop a note here before I forget. Out of the box, Qubes blanks
the screen after a few minutes, but never powers off the screen, even though
it's configured to do so in the XFCE Power Manager. I've had this problem on
several machines, all the way back to R3.2, and I always
December 22, 2019 10:33 AM, "Vít Šesták"
wrote:
> As far as I know/understand:
>
> * At start, all the PCI devices are assigned to dom0.
> * When a qube with an attached PCI device starts, dom0 assigns the PCI device
> to the qube, so it is
> no longer attached to dom0. It never gets actually
December 20, 2019 9:13 PM, "Claudia" mailto:claud...@disroot.org?to=%22Claudia%22%20)> wrote:
December 20, 2019 6:05 PM, brendan.h...@gmail.com
(mailto:brendan.h...@gmail.com) wrote:
On Friday, December 20, 2019 at 9:29:55 AM UTC-5, Claudia wrote:December 19,
2019 12:13 AM, &qu
December 20, 2019 2:19 PM, "Claudia" wrote:
>
> I decided I'm going to try the dual-ESP approach first and see if it works.
> If not, then I'll try
> the EFI directory hack.
>
> I formatted my disk like: ESP, /boot, root, ESP, /boot, root, (swap); and
> install
December 22, 2019 5:45 PM, "Vít Šesták" wrote:
> Helllo,
>
> Dec 22, 2019 15:17:27 Claudia :
>
>
>> I don't know which step -- unbinding xhci_pci, or binding pciback --
>> actually causes the crash in
> this case. I can say, however, that one of them
I'm very new to all this iommu stuff, but as I understand it, devices in the
same iommu group are
supposed to be treated as a single unit, meaning if any of them are assigned to
a VM then they all
must be assigned to the same VM. This is because those devices cannot be
isolated from each other
December 23, 2019 7:31 AM, "qubes123" wrote:
> Suspend/resume problem is most likely caused by a recently added security
> feature in Xen, that
> checks CPUID after resume with the previously (at boot time) known CPUID.
> This is to ensure, that
> the CPU microcode level - along with the
December 20, 2019 6:05 PM, brendan.h...@gmail.com
(mailto:brendan.h...@gmail.com) wrote:
On Friday, December 20, 2019 at 9:29:55 AM UTC-5, Claudia wrote:
December 19, 2019 12:13 AM, "Claudia"
wrote:
> This is R4.1 build 20191013
>
> It works pretty well, definit
Myros:
Hi Claudia, thanks for your response
aplay -l responds this:
card 0: PCH HDA INTEL PCH device 0 ALC255 analog
the other command does work, but i dont know how to export those from dom 0
and its like 2 pages long, i hope it works without these infos.
If you just want to copy a few
Robert M:
I'm trying to install Qubes 4.0 on laptop that has UEFI firmware (without the
Legacy option)
But I cannot get to the blue boot screen.
The official "Troubleshooting UEFI related problems", requires me to switch
to tty2 (Ctrl+Alt+F2) . But seems that there is no combination of
1 - 100 of 192 matches
Mail list logo
