?
Any help is appreciated!
Fab
On Friday, September 17, 2021 at 2:49:54 AM UTC+2 Fabrizio Romano Genovese
wrote:
> Hello all,
>
> I managed to finally install Qubes 4.1, but the audio problem is still not
> fixed. As awokd pointed out, in Qubes 4.1 I can define an audio-vm whic
sys-audio?
Cheers,
Fab
On Sunday, April 18, 2021 at 11:55:34 AM UTC+2 Fabrizio Romano Genovese
wrote:
> On Monday, February 8, 2021 at 10:25:20 PM UTC+1 Fabrizio Romano Genovese
> wrote:
>
>> On Monday, February 8, 2021 at 3:14:43 PM UTC+1 fac...@gmail.com wrote:
>>
>
On Monday, February 8, 2021 at 10:25:20 PM UTC+1 Fabrizio Romano Genovese
wrote:
> On Monday, February 8, 2021 at 3:14:43 PM UTC+1 fac...@gmail.com wrote:
>
>> I think your dell has different wifi and I think audio. The wifi driver
>> for the xps 9310 is iwlwifi. Her
These are not directly related to kernel 5.11. My problem started when I
upgraded from 5.10 to 5.11.
On Wednesday, March 17, 2021 at 8:11:03 AM UTC+1 haa...@web.de wrote:
> On 3/17/21 12:13 AM, Fabrizio Romano Genovese wrote:
> > Booting from a live version and switching to the o
be...@sys-net.service
>
> And then you will be able to log in and fix the kernel issue (without
> networking, of course).
>
> You can also choose the older kernel in the GRUB menu.
>
> On 16/03/2021 16.49, Fabrizio Romano Genovese wrote:
>
> As the title says. I've upgraded to t
As the title says. I've upgraded to the latest kernel (5.11) on qubes 4.0
and now boot is stuck. How do I get out of this? :)
Fab
--
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,
ter, correct me if I'm wrong... :)
About awokd suggestions: I tried to install 4.1 but the installer doesn't
boot on my machine. Also, I've always been very unlucky with Qubes backups
(traditionally I do them and they never work on restore), so I'd gladly
avoid having to reinstall everything ri
As the title says, if I put my pc to sleep it never wakes up. I have to say
that I'm also having wifi problems (card is not correctly detected), which
in my limited experience are sometimes related to sleep problems. I tried
to fiddle with some C-states related options in the bios, but it makes
I installed qubes on a Dell XPS9310. I was using kernel 5.4.90 and sound
was working, but wi-fi did not. So I upgraded to kernel 5.10.13 and now I
have both wifi and sound not working :D
It seems that the sound issues are due to a problem with driver
sof-audio-pci.
In this thread:
On Saturday, February 6, 2021 at 7:12:52 PM UTC+1 awokd wrote:
> Fabrizio Romano Genovese:
> > Yes, I managed to get 5.10.13-1 working. The things that do not work at
> the
> > moment are:
> > - Wifi (AX500, according to google a notorious throublemaker), tha
awokd wrote:
> Fabrizio Romano Genovese:
>
> > ...Which installed kernel 5.10.8. Unfortunately, it appears that the
> ath11k
> > drivers are still missing. Indeed, `modprobe ath11k_pci` says it can't
> find
> > the module.
> > At the moment, `lspci`
Same here. In addition to this, pressing any of the F keys to switch to
textual boot just shows a black screen.
On Friday, February 5, 2021 at 12:33:49 PM UTC+1 st0rmth3g8s wrote:
> Hi guys,
> I have tried all the latest kernels and I am still experiencing a lag and
> pixelation on the LUKS
Hello, I have an XPS9310 and I'm in a very similar situation with AX500.
Any news there?
Also, audio does not work. I'm running qubes 4.0.4 and It used to work
until I upgraded to kernel 5.10.13-1. I have absolutely no experience with
kernel building, any possible further detail you could
Fabrizio Romano Genovese
wrote:
> Yes, I installed kernel-latest-qubes-vm as well, while still using
> 5.4.90-1 on dom0, and things ran smoothly without much problems, even after
> several restarts. I did what you suggested but nothing really happens.
> It turns out this is a bug of ke
net-c.com wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Fabrizio Romano Genovese:
> > In trying to make my wifi adapter working, I decided to try
> `kernel-latest`
> > on Dom0, which installed kernel `5.10.11-1.fc25.qubes.x86_64`. The
> re
In trying to make my wifi adapter working, I decided to try `kernel-latest`
on Dom0, which installed kernel `5.10.11-1.fc25.qubes.x86_64`. The result
is a system where I cannot start VMs (not even VMs with no devices
connected to them) due to `libvirt` errors ( The kernel doesn't support
reset
So, I have a XPS13. Unfortunately it comes with an horrid killer AX500
wireless card that is moreover soldered on the motherboard, so no hope to
replace it.
The drivers for this wireless card should be shipped with kernel version
5.10.8.
So I followed
ban:
> > On 1/31/21 6:26 PM, Fabrizio Romano Genovese wrote:
> >> Ok, I found something: Running `xl dmesg` there's a line that says:
> >> (XEN) Failed to parse ACPI DMAR. Disabling VT-d.
> >
> > I only think to try updating BIOS or using Qubes R4.1 which has ne
to
enable VT and VT-d. I guess the former refers to VT-x?
Fab
On Sunday, January 31, 2021 at 5:46:30 PM UTC+1 qubesth...@gmail.com wrote:
>
> Probably a dumb question, but is VT-x also enabled?
> On Sunday, January 31, 2021 at 10:16:38 AM UTC-6 Fabrizio Romano Genovese
> wrote:
>
Hello all,
My problem is quite simple: I tried to install qubes 4.0.4-rc2. During the
installation procedure, it says that I don't have IOMMU/VT-d. Accordingly,
I cannot even start sys-net once the installation completes because of lack
of VT-d.
The problem is that my computer supports VT-d
-issues/issues/5165#issuecomment-511175580
...In which case output goes on forever until it says that boot failed.
I'll try to take some pictures of this later on today!
Fab
On Saturday, December 5, 2020 at 6:49:53 PM UTC+1 Fabrizio Romano Genovese
wrote:
> So, a small update: I downloa
I second this idea. This should at least be an option you can enable by
editing the boot config as explained here:
https://www.qubes-os.org/doc/uefi-troubleshooting/
I'm in a similar situation, and my best option is taking picture of my boot
screen with a phone.
Fab
On Saturday, December 5,
the black screen. I'm a bit at a loss here, any suggestion is
appreciated!
Fab
On Saturday, November 28, 2020 at 7:02:53 PM UTC+1 Fabrizio Romano Genovese
wrote:
>
> Hello all,
>
> I just got a new lappy and I'm trying to install Qubes on it, which is my
> main O
Hello all,
I just got a new lappy and I'm trying to install Qubes on it, which is my
main OS. I understand that the hardware is very new, so problems are to be
expected.
My main problem at the moment is that I cannot get the installation to
boot. I prepared a usb medium, kept partition size
On Friday, November 2, 2018 at 7:54:44 PM UTC+1, Marcus Linsner wrote:
> On Thursday, November 1, 2018 at 11:21:08 AM UTC+1, peter.p...@gmail.com
> wrote:
> > On Monday, October 15, 2018 at 11:17:48 AM UTC+2, fabr...@statebox.io wrote:
> > > On Friday, October 12, 2018 at 7:13:56 AM UTC+2, awokd
On Friday, October 12, 2018 at 7:13:56 AM UTC+2, awokd wrote:
> fabri...@statebox.io wrote on 10/11/18 9:40 AM:
> > On Friday, May 4, 2018 at 5:05:45 PM UTC+1, gaxi...@gmail.com wrote:
> >> The system tray device widget is not visible anymore. It was there after a
> >> fresh 4.0 install but
On Friday, May 4, 2018 at 5:05:45 PM UTC+1, gaxi...@gmail.com wrote:
> The system tray device widget is not visible anymore. It was there after a
> fresh 4.0 install but disappeared after some days. How can i get it back?
Bad news!: After today's Dom0 update, I got exactly this problem. Trace is
Well, I blacklisted the relevant module and recompiled the driver as the guide
said. The hid-core.c file hasn't the line described in the guide tho: It has a
definition by cases that collapses the wacom driver to the standard one if
wacom specific driver is not loaded. In doubt, I eliminated
Sorry, when I tried to remove
/lib/modules/4.9.56-21.pvops.qubes.x86_64/kernel/drivers/input/tablet/wacom_serial4.ko
I get the error
rm: cannot remove
'/lib/modules/4.9.56-21.pvops.qubes.x86_64/kernel/drivers/input/tablet/wacom_serial4.ko':
Read-only file system
(Not always I get
I saw this reply only yesterday, unfortunately.
So, I followed your suggestion and looked around. I found this, that should do
exactly what you say:
https://cwcode.wordpress.com/2014/01/14/compiling-a-new-kernel-module-to-use-hid-core-for-a-wacom-bamboo-pad/
Now, since this guide is not for
Well, I disabled intel speedstep in the bios and things seem to be better.
Startup time now is around 1.20 mins (still better than 3mins), both in plugged
and unplugged state (booting in plugged state was around 45 secs before tho).
I'll use my PC for a bit more, trying another couple of
Hello all,
I'd like to use a wacom bamboo graphic tablet as an alternative pointing
device, mainly to draw on virtual whiteboards to do maths in conference calls.
At the moment, this is not possible: Connecting the graphic tablet and passing
it to the relevant VM produces no effect whatsoever.
No, my PC is a Dell XPS13, not a Latitude. But I have some news:
The booting problem is 100% dependent on being plugged or not. Precisely, I
observed the following behaviors:
Booting plugged: Everything is normal, PC is fast. If I unplug it afterwards
nothing really happens and performance
Ok, I dug a bit deeper into this. It doesn't look like a problem of how much
memory I give to VMs. Essentially, my QubesOS boots in two different ways:
- When QubesOS is happy, it starts in ~1 min (yup, starting up all the VMs
still takes a while). The overall system is very reactive, for
Great! I just proposed some changes ^_^
https://github.com/QubesOS/qubes-doc/pull/508
Cheers,
Fab
--
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
Yup, if you type curl it works, but you can't curl anything out of it because
you don't have connection. To reproduce what I'm talking about, open a terminal
in whonix-ws/gw and type some random stuff (like "sdshgow"). Press enter.
Whonix will tell you
"Could not find the database of available
Hello all,
This very very annoying thing happened to me also on Qubes 3.2. Essentially, on
a whonix-based template, (whonix-ws or whonix-gw, doesn't really matter), every
time I type something (aside of some basic commands such as sudo, firefox, ls
etc) I receive the message:
"Could not find
I obviously checked that page (it is the first thing I did, actually). But
qubes-core-agent is not mentioned at all there. After hours of research, I
stumbled into this thread
https://github.com/QubesOS/qubes-issues/issues/2771
>From here, dnf search qubes-core-agent gave me what I needed. I'd
Yo everyone,
For future reference, problem solved. The packages
qubes-core-agent-nautilus
qubes-core-agent-networking
qubes-core-agent-network-manager
qubes-core-agent-passwordless-root
qubes-core-agent-dom0-updates
qubes-input-proxy-sender
Exciting news: I didn't know that polkit was a package, so even if I followed (
https://www.qubes-os.org/doc/vm-sudo/ ) in detail, nothing worked.
Giving sudo dnf install polkit in the minimal template vm solves the
authorization problems, both for sys-usb and sys-net.
Now I am able to use the
yes, I have network-manager listed in the services tabs for sys-net (I suppose
that this what the service you were referring to. adding NetworkManager causes
the VM startup to fail).
Moreover, if I try to use the same template for sys-usb and then try to open
some usb stick, I get the message:
> On Wednesday, 3 January 2018 16:16:13 GMT Fabrizio Romano Genovese wrote:
> > I am trying to install texlive on a fedora-26 template vm. The package is
> > quite big, nevertheless it is correctly downloaded. After this, when the
> > actual installation process would
As the title says, Qubes 4.0rc3 boot is very slow compared to Qubes 3.2.
Looking at the console messages at startup, it looks like the problem is that
Qubes takes more than one minute to boot sys-net, sys-firewall, sys-usb and
sys-whonix. That was not the case in 3.2.
Also, when giving
I am trying to set up a sys-net based on fedora-26-minimal. I installed all the
suggested packages in https://www.qubes-os.org/doc/templates/fedora-minimal/
When I start sys-net I can see the network-manager applet, but if I click on it
it says "NetworkManager is not running..."
If I manually
Ok, so for future reference (I found the instructions in
https://www.qubes-os.org/doc/vm-sudo/ to be not completely clear):
The files mentioned in the first part of https://www.qubes-os.org/doc/vm-sudo/,
namely:
/etc/sudoers.d/qubes
/etc/polkit-1/rules.d/00-qubes-allow-all.rules
Hello everyone,
I am trying to install texlive on a fedora-26 template vm. The package is quite
big, nevertheless it is correctly downloaded. After this, when the actual
installation process would be supposed to start, it fails with the message:
At least *MB more space needed on the /
Hello all,
Thanks for the replies! I have already installed sudo just doing
qvm-run -u root fedora-25-minimal xterm
as Marek suggested, and then installing sudo as I usually do via dnf. The
problem is that now sudo asks for the root password anyway. If for instance I
give
sudo dnf update
As in https://github.com/QubesOS/qubes-issues/issues/3157, by default the
fedora minimal template will ask for a password while trying to perform any
action as root. The rationale behind this is that the "ask/don't ask for root"
policy should be customizable by the user.
...But how? I tried
Hello everyone,
As in
https://github.com/QubesOS/qubes-issues/issues/1673
It looks like PCI Hotplug is disabled by default in Qubes. I just bought a new
laptop with thunderbolt port, and I really need PCI hotplug since I attach and
detach it from my dockstation multiple times per day.
I am
Hello All,
Just a very simple problem: My screenlock does not work. After fiddling around
a lot I discovered that the screenlock starts correctly if I set the screen
lock timer as 15 seconds or less.
Experimenting a bit more, I discovered that if I give, say,
xset s 30 30
then the screen never
Nope, no problems whatsoever for me during install, but mine was R3 so
things may be different. I remember I had a lot of problems while using the
system though, as an instance the screen did not wake up after sleep.
Needless to say, I completely gave up on using the Nvidia card and relied
Thanks Rusty Bird, you made my day!
Cheers,
Fab
On Mon, Mar 6, 2017 at 1:15 PM, Rusty Bird <rustyb...@openmailbox.org>
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Fabrizio Romano Genovese:
> > I've built a little toggle script to automatically a
As the title says. I've built a little toggle script to automatically
attach/detach my camera to an appvm. For the sake of completeness, I'd like to
do the same for the internal microphone.
Since microphone can be attached/detached to/from an appvm using Qubes manager,
I suppose there is some
edu> wrote:
> On Thu, Feb 16, 2017 at 10:51 PM, Fabrizio Romano Genovese
> <themasterofdisast...@gmail.com> wrote:
> > Well, I have considered it, yes, and it's true that launching many
> terminals
> > can be resource intensive. But it's also faster: Using &
Wong <a...@qubes-os.org> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 2017-02-16 18:20, Fabrizio Romano Genovese wrote:
> > Hello all,
> >
> > I'm trying to write a little script to globally update my qubes
> > templates. It should work
Hello all,
I'm trying to write a little script to globally update my qubes templates.
It should work more or less like this:
- It prepares a window layout for i3, so that all the opening terminals from
the various templates will occupy the right place in a dedicated desktop;
- Then it launches
Looks like qubes-mgmt-salt-vm-connector is already installed in my templates.
Are you sure the command is
pkg.uptodate: []
? This looks right in the salt documentation, but there is nothing else I can
think about...
--
You received this message because you are subscribed to the Google
The error I get is 127, that should be "command not found" if I got it right...
--
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
Dear Marek,
I've tried the solution you proposed in that post. I've managed to make that
little script to work (strangely enough, it looks like salt minds about
indenting in the code. I'm mainly used to latex that doesn't care and this left
me a bit surprised.
I created a file
As the title says: I've cloned my fedora 23 templates and followed the
procedure to upgrade them to fedora 24. Everything is splendid, the only two
disappointing things are:
a) Network manager applet icon is missing. May this be related to the fact that
my netvm runs on a minimal template?
b)
Thank you very much, your solution worked (actually I had to give
virsh -c xen:/// undefine trim-fedora-23
and not
virsh -c xen:/// undefine fedora-23-fstrim
and then I had to manually remove the trim-fedora-23 files in
/var/lib/qubes/appvm).
The problem started when I decided to make a
Hello all, I'm basically having the same error described here:
https://github.com/QubesOS/qubes-issues/issues/1910
When I try to perform qvm-trim-template on any template, the error
'libvirterror operation failed: domain 'fedora-23-fstrim' already exists with
uuid '
pops up. As in the
Ok, I figured out what the problem was: I was trying to use my phone as a usb
storage in mtp mode. To do that you also need the package gvfs-mtp.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving
Hello everyone,
I have installed the fedora-24-minimal template and I'm loving it. I'm using it
as the underlying template in my Netvm and FirewallVM, I just followed the
guide on Qubes website and everything went well. I'd like to do the same for my
sys-usb vm but I'm clearly missing
64 matches
Mail list logo
