Re: [qubes-users] No sound in XPS9310

[Fabrizio Romano Genovese]

After a bit of time I had the opportunity to investigate this a bit 
further. Even running speaker-test on sys-audio results in the audio 
stammering, and sys-audio manages the device directly... Could this be a 
problem between fedora33 and my sound card? What can I do to pinpoint the 
problem?

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 which, 
> having fedora33, correctly recognizes my audio card. 
>
> I first tried the easy way: I created a sys-audio vm, and assigned the 
> audio card to it. Unfortunately, the audio doesn't really work smoothly: 
> Playing youtube videos on sys-audio is very slow and the sound is 
> continuously cackling.
>
> Investigating things further, it seems that there is already some salt 
> script I can use to create sys-audio. So I removed my sys-audio vm and I 
> tried with 
> sudo qubesctl state.sls qvm.sys-audio
> that lists two processes, one succeds and the other one fails. After this 
> I have sys-audio again, but it is not used by default by any other vm. I 
> tested with 
> qvm-prefs untrusted audiovm sysaudio 
> but audio still does not work. Youtube videos now do not really start. If 
> I set audio back to dom0 and reboot the vm instead they do (but obviously I 
> cannot hear anything given that dom0 has fedora32 which doesn't like my 
> card).
>
> I feel like there's something very simple that I am missing. Am I maybe 
> issuing the wrong salt command to set up 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:
>>>
>>>> I think your dell has different wifi and I think audio.   The wifi 
>>>> driver for the xps 9310 is iwlwifi.   Here is some firmware info:  
>>>> https://support.killernetworking.com/knowledge-base/killer-ax1650-in-debian-ubuntu-16-04/
>>>>  
>>>> and here is some qubes specific info on your wifi driver:  
>>>> https://github.com/QubesOS/qubes-issues/issues/5615
>>>>
>>>
>>> Alas, no, I really have the AX500. The AX1650 is waay much more well 
>>> behaved and it is the one that is usually shipped on XPS developer edition. 
>>> Unfortunately XPS developer edition does not have a 32GB RAM option, which 
>>> was absolutely needed for me, being Qubes unbelievably ram hungry. So I was 
>>> forced to purchase the model with the Killer AX500 T_T
>>>
>>>
>>>> I think the audio is different too, as the xps 9700 needs the 5.10 
>>>> kernel to work, but the base-config patch above does enable 
>>>> CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE which I think you need too.
>>>>
>>>> To patch the kernel you must build it from source with qubes-builder 
>>>> https://www.qubes-os.org/doc/qubes-builder/.   First configure it.  
>>>> Then change kernel to master branch in builer.conf.after the "make 
>>>> get-sources"  is when you would patch with config-base in 
>>>> qubes-builder/qubes-src/linux-kernel.
>>>>
>>>
>>> The sad thing is that audio worked perfectly on kernel 5.4... I'll try 
>>> to give a look to this by the end of the week, when I'll have a bit less 
>>> work to do  :)
>>>  
>>>
>>>> fedora 33 5.10 kernel supports much more devices and audio works in the 
>>>> upstream fedora on both the 9700 and 9310 dells.  I'll see if I can get a 
>>>> patch into qubes the upstream kernel modules which fedora has added or at 
>>>> the minimum the SOF stuff in the patch.   Then all our audio will just 
>>>> work 
>>>> with qubes.
>>>>
>>>
>>> That would be a wonderful, wonderful thing. In the meantime I'll try to 
>>> learn how to compile my own kernels, my pc also tends to heat quite a lot 
>>> and I suspect that a taylored kernel could make my overall experience 
>>> better, correct me if I'm wrong... :)
>>>
>>  
>> By any chance, does everyone know if there are any news about these audio 
>> issues? I'm updating the kernel to the latest version every week or so, but 
>> unfortunately sound is still not working :(
>>  
>>
>>>
>>> About awokd suggestions

Re: [qubes-users] No sound in XPS9310

[Fabrizio Romano Genovese]

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 which, 
having fedora33, correctly recognizes my audio card. 

I first tried the easy way: I created a sys-audio vm, and assigned the 
audio card to it. Unfortunately, the audio doesn't really work smoothly: 
Playing youtube videos on sys-audio is very slow and the sound is 
continuously cackling.

Investigating things further, it seems that there is already some salt 
script I can use to create sys-audio. So I removed my sys-audio vm and I 
tried with 
sudo qubesctl state.sls qvm.sys-audio
that lists two processes, one succeds and the other one fails. After this I 
have sys-audio again, but it is not used by default by any other vm. I 
tested with 
qvm-prefs untrusted audiovm sysaudio 
but audio still does not work. Youtube videos now do not really start. If I 
set audio back to dom0 and reboot the vm instead they do (but obviously I 
cannot hear anything given that dom0 has fedora32 which doesn't like my 
card).

I feel like there's something very simple that I am missing. Am I maybe 
issuing the wrong salt command to set up 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:
>>
>>> I think your dell has different wifi and I think audio.   The wifi 
>>> driver for the xps 9310 is iwlwifi.   Here is some firmware info:  
>>> https://support.killernetworking.com/knowledge-base/killer-ax1650-in-debian-ubuntu-16-04/
>>>  
>>> and here is some qubes specific info on your wifi driver:  
>>> https://github.com/QubesOS/qubes-issues/issues/5615
>>>
>>
>> Alas, no, I really have the AX500. The AX1650 is waay much more well 
>> behaved and it is the one that is usually shipped on XPS developer edition. 
>> Unfortunately XPS developer edition does not have a 32GB RAM option, which 
>> was absolutely needed for me, being Qubes unbelievably ram hungry. So I was 
>> forced to purchase the model with the Killer AX500 T_T
>>
>>
>>> I think the audio is different too, as the xps 9700 needs the 5.10 
>>> kernel to work, but the base-config patch above does enable 
>>> CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE which I think you need too.
>>>
>>> To patch the kernel you must build it from source with qubes-builder 
>>> https://www.qubes-os.org/doc/qubes-builder/.   First configure it.  
>>> Then change kernel to master branch in builer.conf.after the "make 
>>> get-sources"  is when you would patch with config-base in 
>>> qubes-builder/qubes-src/linux-kernel.
>>>
>>
>> The sad thing is that audio worked perfectly on kernel 5.4... I'll try to 
>> give a look to this by the end of the week, when I'll have a bit less work 
>> to do  :)
>>  
>>
>>> fedora 33 5.10 kernel supports much more devices and audio works in the 
>>> upstream fedora on both the 9700 and 9310 dells.  I'll see if I can get a 
>>> patch into qubes the upstream kernel modules which fedora has added or at 
>>> the minimum the SOF stuff in the patch.   Then all our audio will just work 
>>> with qubes.
>>>
>>
>> That would be a wonderful, wonderful thing. In the meantime I'll try to 
>> learn how to compile my own kernels, my pc also tends to heat quite a lot 
>> and I suspect that a taylored kernel could make my overall experience 
>> better, correct me if I'm wrong... :)
>>
>  
> By any chance, does everyone know if there are any news about these audio 
> issues? I'm updating the kernel to the latest version every week or so, but 
> unfortunately sound is still not working :(
>  
>
>>
>> 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 right now...
>>
>>
>>>
>>>
>>>
>>>
>>> On Sat, Feb 6, 2021 at 11:34 AM Fabrizio Romano Genovese <
>>> fabr...@statebox.io> wrote:
>>>
>>>>
>>>> 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 a

Re: [qubes-users] No sound in XPS9310

[Fabrizio Romano Genovese]

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.   Here is some firmware info:  
>> https://support.killernetworking.com/knowledge-base/killer-ax1650-in-debian-ubuntu-16-04/
>>  
>> and here is some qubes specific info on your wifi driver:  
>> https://github.com/QubesOS/qubes-issues/issues/5615
>>
>
> Alas, no, I really have the AX500. The AX1650 is waay much more well 
> behaved and it is the one that is usually shipped on XPS developer edition. 
> Unfortunately XPS developer edition does not have a 32GB RAM option, which 
> was absolutely needed for me, being Qubes unbelievably ram hungry. So I was 
> forced to purchase the model with the Killer AX500 T_T
>
>
>> I think the audio is different too, as the xps 9700 needs the 5.10 kernel 
>> to work, but the base-config patch above does enable 
>> CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE which I think you need too.
>>
>> To patch the kernel you must build it from source with qubes-builder 
>> https://www.qubes-os.org/doc/qubes-builder/.   First configure it.  Then 
>> change kernel to master branch in builer.conf.after the "make 
>> get-sources"  is when you would patch with config-base in 
>> qubes-builder/qubes-src/linux-kernel.
>>
>
> The sad thing is that audio worked perfectly on kernel 5.4... I'll try to 
> give a look to this by the end of the week, when I'll have a bit less work 
> to do  :)
>  
>
>> fedora 33 5.10 kernel supports much more devices and audio works in the 
>> upstream fedora on both the 9700 and 9310 dells.  I'll see if I can get a 
>> patch into qubes the upstream kernel modules which fedora has added or at 
>> the minimum the SOF stuff in the patch.   Then all our audio will just work 
>> with qubes.
>>
>
> That would be a wonderful, wonderful thing. In the meantime I'll try to 
> learn how to compile my own kernels, my pc also tends to heat quite a lot 
> and I suspect that a taylored kernel could make my overall experience 
> better, correct me if I'm wrong... :)
>
 
By any chance, does everyone know if there are any news about these audio 
issues? I'm updating the kernel to the latest version every week or so, but 
unfortunately sound is still not working :(
 

>
> 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 right now...
>
>
>>
>>
>>
>>
>> On Sat, Feb 6, 2021 at 11:34 AM Fabrizio Romano Genovese <
>> fabr...@statebox.io> wrote:
>>
>>>
>>> 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: https://groups.google.com/g/qubes-users/c/Fa65-e8vqdM 
>>> it turns out another user was having a similar problem with a dell 9700, 
>>> which was apparently solved. Indeed in the thread it is said: 
>>>
>>> Audio works (with kernel 5.10 and attached kernel base-config patch  + 
>>> latest 1.6.1 sof-bin firmware https://github.com/thesofproject/sof-bin 
>>> and alsa-ucm-config files.   see 
>>> https://blog.fts.scot/2020/07/04/dell-xps-2020-how-to-get-audio-working-on-linux/
>>>  
>>> for alsa ucm config ).
>>>
>>> Unfortunately, I am not technically skilled enough to really understand 
>>> the fix. Does it mean that I have to download kernel 5.10 (from were?), 
>>> apply the patch provided in the thread (how?), include firmware and config 
>>> files (how?) and then compile and install?
>>> As you can see I don't really have a specific question, and I'm more in 
>>> search of a few clarifications to understand how to apply an apparently 
>>> already available solution. :)
>>>
>>> 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 qubes-users...@googlegroups.com.
>>> To view this discussion on the web visit 

Re: [qubes-users] A start job is running for Start Qubes VM sys-net. FOREVER.

[Fabrizio Romano Genovese]

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 old kernel solved it.
> > Has anyone else experienced something similar with kernel 5.11 or it is
> > just myself? I had a boot fuckup with kernel 5.10 as well a few weeks
> > ago, but I just waited for the next release and that solved it. I'd like
> > to understand if the situation is similar here or if it's a problem of
> > my machine, in which case I'll investigate deeper.
>
> there are several issues. Like
>
> https://github.com/QubesOS/qubes-issues/issues/6446
> https://github.com/QubesOS/qubes-issues/issues/6397
>
> but they might be unrelated, as well.
>
>
> >
> > On Tuesday, March 16, 2021 at 5:29:53 PM UTC+1 rud...@rudd-o.com wrote:
> >
> > You can mask the unit in the GRUB kernel command line with the
> > parameter:
> >
> > systemd.mask=qube...@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 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,
> >> send an email to qubes-users...@googlegroups.com.
> >> To view this discussion on the web visit
> >> 
> https://groups.google.com/d/msgid/qubes-users/7ba1ae0f-4037-4a47-9bf4-aa9eae652a7dn%40googlegroups.com
> >> <
> https://groups.google.com/d/msgid/qubes-users/7ba1ae0f-4037-4a47-9bf4-aa9eae652a7dn%40googlegroups.com?utm_medium=email_source=footer
> >.
> >
> >
> > --
> > Rudd-O
> > https://rudd-o.com/ <https://rudd-o.com/>
> >
> > --
> > 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...@googlegroups.com
> > <mailto:qubes-users...@googlegroups.com>.
> > To view this discussion on the web visit
> > 
> https://groups.google.com/d/msgid/qubes-users/772e2a89-da21-4f87-8977-0e171526978fn%40googlegroups.com
> > <
> https://groups.google.com/d/msgid/qubes-users/772e2a89-da21-4f87-8977-0e171526978fn%40googlegroups.com?utm_medium=email_source=footer
> >.
>
>

-- 
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/ba28f5da-5cd2-43a6-aa2c-86a709289efen%40googlegroups.com.

Re: [qubes-users] A start job is running for Start Qubes VM sys-net. FOREVER.

[Fabrizio Romano Genovese]

Booting from a live version and switching to the old kernel solved it. Has 
anyone else experienced something similar with kernel 5.11 or it is just 
myself? I had a boot fuckup with kernel 5.10 as well a few weeks ago, but I 
just waited for the next release and that solved it. I'd like to understand 
if the situation is similar here or if it's a problem of my machine, in 
which case I'll investigate deeper.

On Tuesday, March 16, 2021 at 5:29:53 PM UTC+1 rud...@rudd-o.com wrote:

> You can mask the unit in the GRUB kernel command line with the parameter:
>
> systemd.mask=qube...@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 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, send an 
> email to qubes-users...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/qubes-users/7ba1ae0f-4037-4a47-9bf4-aa9eae652a7dn%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/qubes-users/7ba1ae0f-4037-4a47-9bf4-aa9eae652a7dn%40googlegroups.com?utm_medium=email_source=footer>
> .
>
>
> -- 
> Rudd-O
> https://rudd-o.com/
>
>

-- 
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/772e2a89-da21-4f87-8977-0e171526978fn%40googlegroups.com.

[qubes-users] A start job is running for Start Qubes VM sys-net. FOREVER.

[Fabrizio Romano Genovese]

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, 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/7ba1ae0f-4037-4a47-9bf4-aa9eae652a7dn%40googlegroups.com.

Re: [qubes-users] No sound in XPS9310

[Fabrizio Romano Genovese]

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.   Here is some firmware info:  
> https://support.killernetworking.com/knowledge-base/killer-ax1650-in-debian-ubuntu-16-04/
>  
> and here is some qubes specific info on your wifi driver:  
> https://github.com/QubesOS/qubes-issues/issues/5615
>

Alas, no, I really have the AX500. The AX1650 is waay much more well 
behaved and it is the one that is usually shipped on XPS developer edition. 
Unfortunately XPS developer edition does not have a 32GB RAM option, which 
was absolutely needed for me, being Qubes unbelievably ram hungry. So I was 
forced to purchase the model with the Killer AX500 T_T


> I think the audio is different too, as the xps 9700 needs the 5.10 kernel 
> to work, but the base-config patch above does enable 
> CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE which I think you need too.
>
> To patch the kernel you must build it from source with qubes-builder 
> https://www.qubes-os.org/doc/qubes-builder/.   First configure it.  Then 
> change kernel to master branch in builer.conf.after the "make 
> get-sources"  is when you would patch with config-base in 
> qubes-builder/qubes-src/linux-kernel.
>

The sad thing is that audio worked perfectly on kernel 5.4... I'll try to 
give a look to this by the end of the week, when I'll have a bit less work 
to do  :)
 

> fedora 33 5.10 kernel supports much more devices and audio works in the 
> upstream fedora on both the 9700 and 9310 dells.  I'll see if I can get a 
> patch into qubes the upstream kernel modules which fedora has added or at 
> the minimum the SOF stuff in the patch.   Then all our audio will just work 
> with qubes.
>

That would be a wonderful, wonderful thing. In the meantime I'll try to 
learn how to compile my own kernels, my pc also tends to heat quite a lot 
and I suspect that a taylored kernel could make my overall experience 
better, 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 right now...


>
>
>
>
> On Sat, Feb 6, 2021 at 11:34 AM Fabrizio Romano Genovese <
> fabr...@statebox.io> wrote:
>
>>
>> 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: https://groups.google.com/g/qubes-users/c/Fa65-e8vqdM it 
>> turns out another user was having a similar problem with a dell 9700, which 
>> was apparently solved. Indeed in the thread it is said: 
>>
>> Audio works (with kernel 5.10 and attached kernel base-config patch  + 
>> latest 1.6.1 sof-bin firmware https://github.com/thesofproject/sof-bin 
>> and alsa-ucm-config files.   see 
>> https://blog.fts.scot/2020/07/04/dell-xps-2020-how-to-get-audio-working-on-linux/
>>  
>> for alsa ucm config ).
>>
>> Unfortunately, I am not technically skilled enough to really understand 
>> the fix. Does it mean that I have to download kernel 5.10 (from were?), 
>> apply the patch provided in the thread (how?), include firmware and config 
>> files (how?) and then compile and install?
>> As you can see I don't really have a specific question, and I'm more in 
>> search of a few clarifications to understand how to apply an apparently 
>> already available solution. :)
>>
>> 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 qubes-users...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/qubes-users/5bde992b-ea73-499f-bcd1-38a0a2f0028fn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/qubes-users/5bde992b-ea73-499f-bcd1-38a0a2f0028fn%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>
>
> -- 
> http://myutil.com
>

-- 
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/77d67c99-0039-487d-a91b-17e46f59010en%40googlegroups.com.

[qubes-users] Sleep does not work on XPS9310

[Fabrizio Romano Genovese]

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 no 
difference.

Any pointers are appreciated!

-- 
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/3959f13f-53ff-4f53-8a23-51271846e15cn%40googlegroups.com.

[qubes-users] No sound in XPS9310

[Fabrizio Romano Genovese]

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: https://groups.google.com/g/qubes-users/c/Fa65-e8vqdM it 
turns out another user was having a similar problem with a dell 9700, which 
was apparently solved. Indeed in the thread it is said: 

Audio works (with kernel 5.10 and attached kernel base-config patch  + 
latest 1.6.1 sof-bin firmware https://github.com/thesofproject/sof-bin and 
alsa-ucm-config files.   see 
https://blog.fts.scot/2020/07/04/dell-xps-2020-how-to-get-audio-working-on-linux/
 
for alsa ucm config ).

Unfortunately, I am not technically skilled enough to really understand the 
fix. Does it mean that I have to download kernel 5.10 (from were?), apply 
the patch provided in the thread (how?), include firmware and config files 
(how?) and then compile and install?
As you can see I don't really have a specific question, and I'm more in 
search of a few clarifications to understand how to apply an apparently 
already available solution. :)

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 qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/5bde992b-ea73-499f-bcd1-38a0a2f0028fn%40googlegroups.com.

Re: [qubes-users] Include ath11k in kernel 5.10

[Fabrizio Romano Genovese]

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), that is 
> > still detected as unassigned both in sys-net and dom0. 
>
> Check out this thread: 
> https://www.mail-archive.com/qubes...@googlegroups.com/msg04757.html 
> <https://www.mail-archive.com/qubes-devel@googlegroups.com/msg04757.html>. 
>
> Looks like there's a limitation in QEMU that makes it unable to 
> passthrough multiple MSI vectors on a device, so driver upgrades will 
> not help. 

More than "upgrades", is worth pointing out that at the moment there is 
literally no driver for my wireless card in sys-net. 
 I found a few hints on google about how to recompile the kernel to include 
those drivers, but they weren't qubes-specific and I never did kernel 
building before, so I don't know really where to begin.

You could try disabling them and see if it reverts to old 
> style interrupts with the following: 
>
> qvm-prefs sys-net kernelopts "nopat iommu=soft swiotlb=8192 pci=nomsi" 
>
> Qvm-shutdown sys-net and start it again and test. If it doesn't help, 
> repeat the above command less the pci=nomsi option. Only option at that 
> point is to wait until appropriate support is added to QEMU then Xen & 
> Qubes, or to switch to a USB wifi device (but search on this list, etc. 
> to find one known to work with Qubes). 
>
I tried, but nothing changes. My card is still read as "unassigned class". 
Do you know if adding support to QEMU is in the works by any chance? I 
don't mind waiting, but it would be nice to have at least a vague idea of 
the time windows we are looking at (months? years?).
 

>
> > - Sound (must be a problem with the driver, sof-audio-pci 
> > - Sleep (no idea what the problem may be, but sometimes fixing wifi 
> > improves this too) 
> > 
> > The closest thing to what I need is this: 
> > https://groups.google.com/g/qubes-users/c/Fa65-e8vqdM which fixed audio 
> for 
> > XPS9700 (I have XPS9310), but not wifi, even if the drivers were 
> included 
> > in the kernel. 
>
> Mind starting a new thread for these two issues, or pointing me towards 
> one if you already have? They are a bit off-topic from the thread title 
> of ath11k. 
>
 
Will do. Thanks!

-- 
> - 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/7dfd9722-fc67-49c5-bb4e-9c737854e58bn%40googlegroups.com.

Re: [qubes-users] Include ath11k in kernel 5.10

[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), that is 
still detected as unassigned both in sys-net and dom0.
- Sound (must be a problem with the driver, sof-audio-pci
- Sleep (no idea what the problem may be, but sometimes fixing wifi 
improves this too)

The closest thing to what I need is this: 
https://groups.google.com/g/qubes-users/c/Fa65-e8vqdM which fixed audio for 
XPS9700 (I have XPS9310), but not wifi, even if the drivers were included 
in the kernel.

I would very much like to help with this, but I'm totally a novice when it 
comes to kernel building. Should I create a kernel-building vm, build my 
kernels there and then distribute them to dom0/vms for installation? Also, 
in the thread I referenced above, a patch is provided. I don't understand 
where to apply it tho. Should I download some qubes kernel source and patch 
it, or the kernel source has to be downloaded from Fedora repos? Any 
help/guide, way to make this kind of thing more accessible would be 
appreciated,  this seems a very nice skill to master!


On Saturday, February 6, 2021 at 9:10:06 AM UTC+1 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` in `sys-net` detect my wireless card as 
> `Unassigned
> > class [ff00]: Qualcomm Device 1101`
>
> Saw in the other thread you were trying other kernel versions. Were you 
> able to get it working? You might be able to pass it through to a full 
> HVM and experiment with getting it working in there, which could 
> hopefully help guide how to build it in. Haven't done it myself, though.
>
> -- 
> - 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/11777311-a126-43c7-8246-ea3161050d16n%40googlegroups.com.

[qubes-users] Re: LUKS Screen laggy and pixelated

[Fabrizio Romano Genovese]

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 screen when i first login in. Any ideas how i can 
> fix this? 
> I am using very 
> 10th gen i7 cpu
> Intel iris xe graphics
> And have 40GB of Ram
>
> So I would imagine this would be more then enough?
>
> cheers
> St0rm
>

-- 
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/d27bdfa5-3cb2-4362-a0d7-3e8e037cbb1fn%40googlegroups.com.

[qubes-users] Re: HCL - Dell_Inc_-XPS_17_9700

[Fabrizio Romano Genovese]

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 share about what you 
did to make audio work would be super appreciated!

On Sunday, January 10, 2021 at 6:06:24 AM UTC+1 fac...@gmail.com wrote:

> 4.0.4 or 4.0.4rc1 would not install (tried all the workarounds).   4.1 
> alpha installed no problems, no special boot options it just worked.
>
> Upgraded to kernel latest, which fixed bluetooth and some performance.
> Needed to give sys-usb more RAM to function properly (otherwise 
> keyboard/mouse would lag when started usb network).
>
> I built a custom kernel for latest intel sound drivers and Qualcomm wifi6 
> (linux-kernel.patch attached).
>
> Works:
> Everything except wifi works.
> Touchscreen sort of works (acts like a tablet input)
> Bluetooth works.
> Audio works (with kernel 5.10 and attached kernel base-config patch  + 
> latest 1.6.1 sof-bin firmware https://github.com/thesofproject/sof-bin 
> and alsa-ucm-config files.   see 
> https://blog.fts.scot/2020/07/04/dell-xps-2020-how-to-get-audio-working-on-linux/
>  
> for alsa ucm config ).
>
> Does not work:
> Qualcomm AX500 wifi.   I have the latest firmware and it works fine on 
> bare metal fedora 33.   However, with Qubes, the xen pci passthrough is not 
> working.   Here is the error from the sys-net qube dmesg:
> [5.706045] ath11k_pci :00:06.0: WARNING: ath11k PCI support is 
> experimental!
> [5.706448] ath11k_pci :00:06.0: BAR 0: assigned [mem 
> 0xf200-0xf20f 64bit]
> [5.734248] ath11k_pci :00:06.0: failed to get 32 MSI vectors, only 
> -28 available
> [5.734289] ath11k_pci :00:06.0: failed to enable msi: -28
> [5.736589] ath11k_pci: probe of :00:06.0 failed with error -28
> I have tried permissive, no reset etc.   I even tried the latest ath11k 
> driver from the 5.11 kernel but no luck getting it to work with xen pci 
> passthrough.
>
> There is a TPM 2.0 module which the kernel appears to see but HCL report 
> doesn't?
>
>

-- 
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/d5d22b92-8971-4666-9289-f4ef3f897b48n%40googlegroups.com.

Re: [qubes-users] kernel-latest broke my system

[Fabrizio Romano Genovese]

...Following the suggestions on 
https://www.qubes-os.org/doc/pci-troubleshooting/ I was able to start 
sys-net and get internet running. I'm running qubes-dom0-update and it 
works, but the new kernel version is not yet available. I hope that 
installing the new kernel solves the problem, it should be a matter of 
hours before it can be installed. Fingers crossed! If things go well (let's 
hope!) I'll document what I did in 
https://github.com/QubesOS/qubes-issues/issues/6377 in case other people 
end up in the same nasty situation. :)

On Thursday, February 4, 2021 at 10:35:56 PM UTC+1 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 kernel 5.10.11-1.fc25.qubes.x86_64, which is 
> being discussed here: https://github.com/QubesOS/qubes-issues/issues/6377
> The bug will be probably fixed already in 5.10.12, the problem is that I 
> don't see how I can install the upgrade if I cannot launch VMs.
>
> What really puzzles me is that 5.10.11-1 somehow managed to break also 
> 5.4.90-1.qubes.x86_64 and 5.4.91-1.fc25.qubes.x86_64.
>
> In any case, elaborating on your hints it turns out that using kernel 
> 5.4.91-1 I can get a shell by doing Ctrl+Alt+F2. I am greeted by a message 
> saying that X won't start, but at least I can login.
> Here I can launch VMs like vault, that have no device assigned (on kernel 
> 5.10.11-1 I cannot launch anything). 
> Still no hope for sys-net: It says "Unable to reset PCI device : 
> no FLR,  PM reset or bus reset available, see 
> /var/log/libvirt/libxl/libxl-driver.log for details".
> Following the suggestion, the log says "unable to add device with path 
> ", and "libxl_devices_destroy failed for 5".
>
> ...If I manage to get internet running, I may download the new, patched 
> kernel and hopefully be back with a functioning computer. Any clue as what 
> may be the next steps here?
>
> On Thursday, February 4, 2021 at 10:15:01 PM UTC+1 rust...@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 
>> 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 from sysfs for PCI device ...). 
>> > 
>> > I tried to go back to my old kernels by changing `xen.cfg` in 
>> > `/boot/efi/EFI/qubes` (here I have options 5.4.90-1.qubes.x86_64 and 
>> > 5.4.91-1.fc25.qubes.x86_64, besides the one I mentioned above). The 
>> real 
>> > big problem is that these kernels do not seem to appear to work 
>> anymore. As 
>> > soon as I change `default` in `xen.cgf` selecting one of these two 
>> kernels, 
>> > I am not able to access the system (after I insert the LUKS passphrase 
>> I 
>> > get black screen in the authorization manager. Moreover, from boot 
>> messages 
>> > it seems that neither these kernel can start sys-net anymore). 
>> > 
>> > 
>> > Any suggestion is really appreciated, I spent the last week configuring 
>> my 
>> > PC and I would literally break into tears if I had to re-do everything 
>> from 
>> > scratch. 
>>
>> Did you also install kernel-latest-qubes-vm (in addition to 
>> kernel-latest) in dom0? Then maybe that too happens to be somehow 
>> broken on your system. 
>>
>> If you can log in on a console (Ctrl-Alt-F2) *after* all your 
>> autostart VMs have failed to start, check 'qubes-prefs default_kernel' 
>> and try setting the VM kernel to another version - i.e. to one of the 
>> directory names in /var/lib/qubes/vm-kernels/ - like this: 
>>
>> qubes-prefs default_kernel 5.4.90-1 
>> qubes-prefs default_kernel 5.4.91-1.fc25 
>>
>> If you can't log in at all, you could mount the root filesystem from a 
>> Qubes installer console and edit the 'default_kernel' property inside 
>> var/lib/qubes/qubes.xml on the root filesystem mountpoint. 
>>
>> Rusty 
>> -BEGIN PGP SIGNATURE- 
>>
>> iQKTBAEBCgB9FiEEhLWbz8YrEp/hsG0ERp149HqvKt8FAmAcY8ZfFIAALgAo 
>> aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDg0 
>> QjU5QkNGQzYyQjEyOUZFMUIwNkQwNDQ2OUQ3OEY0N0FBRjJBREYACgkQRp149Hqv 
>> Kt9qzQ//VGZZ

Re: [qubes-users] kernel-latest broke my system

[Fabrizio Romano Genovese]

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 kernel 5.10.11-1.fc25.qubes.x86_64, which is 
being discussed here: https://github.com/QubesOS/qubes-issues/issues/6377
The bug will be probably fixed already in 5.10.12, the problem is that I 
don't see how I can install the upgrade if I cannot launch VMs.

What really puzzles me is that 5.10.11-1 somehow managed to break also 
5.4.90-1.qubes.x86_64 and 5.4.91-1.fc25.qubes.x86_64.

In any case, elaborating on your hints it turns out that using kernel 
5.4.91-1 I can get a shell by doing Ctrl+Alt+F2. I am greeted by a message 
saying that X won't start, but at least I can login.
Here I can launch VMs like vault, that have no device assigned (on kernel 
5.10.11-1 I cannot launch anything). 
Still no hope for sys-net: It says "Unable to reset PCI device : no 
FLR,  PM reset or bus reset available, see 
/var/log/libvirt/libxl/libxl-driver.log for details".
Following the suggestion, the log says "unable to add device with path 
", and "libxl_devices_destroy failed for 5".

...If I manage to get internet running, I may download the new, patched 
kernel and hopefully be back with a functioning computer. Any clue as what 
may be the next steps here?

On Thursday, February 4, 2021 at 10:15:01 PM UTC+1 rust...@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 
> 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 from sysfs for PCI device ...).
> > 
> > I tried to go back to my old kernels by changing `xen.cfg` in 
> > `/boot/efi/EFI/qubes` (here I have options 5.4.90-1.qubes.x86_64 and 
> > 5.4.91-1.fc25.qubes.x86_64, besides the one I mentioned above). The real 
> > big problem is that these kernels do not seem to appear to work anymore. 
> As 
> > soon as I change `default` in `xen.cgf` selecting one of these two 
> kernels, 
> > I am not able to access the system (after I insert the LUKS passphrase I 
> > get black screen in the authorization manager. Moreover, from boot 
> messages 
> > it seems that neither these kernel can start sys-net anymore).
> > 
> > 
> > Any suggestion is really appreciated, I spent the last week configuring 
> my 
> > PC and I would literally break into tears if I had to re-do everything 
> from 
> > scratch.
>
> Did you also install kernel-latest-qubes-vm (in addition to
> kernel-latest) in dom0? Then maybe that too happens to be somehow
> broken on your system.
>
> If you can log in on a console (Ctrl-Alt-F2) *after* all your
> autostart VMs have failed to start, check 'qubes-prefs default_kernel'
> and try setting the VM kernel to another version - i.e. to one of the
> directory names in /var/lib/qubes/vm-kernels/ - like this:
>
> qubes-prefs default_kernel 5.4.90-1
> qubes-prefs default_kernel 5.4.91-1.fc25
>
> If you can't log in at all, you could mount the root filesystem from a
> Qubes installer console and edit the 'default_kernel' property inside
> var/lib/qubes/qubes.xml on the root filesystem mountpoint.
>
> Rusty
> -BEGIN PGP SIGNATURE-
>
> iQKTBAEBCgB9FiEEhLWbz8YrEp/hsG0ERp149HqvKt8FAmAcY8ZfFIAALgAo
> aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDg0
> QjU5QkNGQzYyQjEyOUZFMUIwNkQwNDQ2OUQ3OEY0N0FBRjJBREYACgkQRp149Hqv
> Kt9qzQ//VGZZvcU0kmZc/0rphRHJL8Ds5NHqQcFE/tijIxFGin6as/3r/l0hRP5L
> xYA7IXoVlPj/Q2r+Ub5JnPJUl2/0WeYSU40PFJMALCBbjM0Vs1LqE55WbuNu1xBt
> 8uKlRKIxMfe+uJzFGjUBmNbV8elNCPpxMRHeAWG6iqvHfm/62RlEamKj+7xm1DTY
> sOUJzbSFguHWd5P0e/orVpQfaYrfRGexwpLv7+LkM+aQ2i8pDgcnt+ueLtLYDS/F
> yQVAd1PLEuxI5AxaKL4OFgDIT5X6EGSof3yayr7/CSCwPo9fMb2W/30ZOGa5+2J5
> Y2mXfUfnbZsCBCVolOKNZhVC7we0JxcfDElsJ8nWNHhrOq7vtIKm/Z0NUL2fw7Yu
> LFHKgpRRXwnICRETfTWpaCE1mfYx0XA1h+PDxVCNQsn6Qt49Zm993ZGrk6pAS6Dt
> 9zfDt2wB1qEIB0vd/6ao350B6eDkOB2JElldR6H/BXoFbv1m9h3YD7d8KazehpX5
> f2NdT4Zg+ZmJYw4sZbRPIYaYjlNBumJnkF+XyM2ZN/dzDfMe4oY8/AuqxBGeWHln
> BTDgX19GwfMviPeTv6K+FsmcaykA48j4sdw/ns6ZVexJ57KgC4cExsKiIT31jHBL
> vgzUALinx/QwtCfwl7XxL1TakJ9tQqLt42E0UTA6rPBVDXS/074=
> =hqBL
> -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/b8fd8aa8-3bf1-4efc-920f-b14b7ff6cccbn%40googlegroups.com.

[qubes-users] kernel-latest broke my system

[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 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 from sysfs for PCI device ...).

I tried to go back to my old kernels by changing `xen.cfg` in 
`/boot/efi/EFI/qubes` (here I have options 5.4.90-1.qubes.x86_64 and 
5.4.91-1.fc25.qubes.x86_64, besides the one I mentioned above). The real 
big problem is that these kernels do not seem to appear to work anymore. As 
soon as I change `default` in `xen.cgf` selecting one of these two kernels, 
I am not able to access the system (after I insert the LUKS passphrase I 
get black screen in the authorization manager. Moreover, from boot messages 
it seems that neither these kernel can start sys-net anymore).


Any suggestion is really appreciated, I spent the last week configuring my 
PC and I would literally break into tears if I had to re-do everything from 
scratch.


-- 
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/18b1c868-b18f-4bd3-9d9e-dda9391f06abn%40googlegroups.com.

[qubes-users] Include ath11k in kernel 5.10

[Fabrizio Romano Genovese]

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 https://www.qubes-os.org/doc/managing-vm-kernel/ and gave:

`sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable 
kernel-latest-qubes-vm`

...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` in `sys-net` detect my wireless card as `Unassigned 
class [ff00]: Qualcomm Device 1101`
I've spent the whole day trying to understand what to do with scarce 
success, and nearly all solutions involve kernel recompilation. I've never 
attempted that, so any help, or equivalently an idiot-proof guide about how 
to proceed would be super appreciated. :)


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 qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/e63b6b82-f34a-4fe1-b122-d862ceabf8f5n%40googlegroups.com.

Re: [qubes-users] Re: VT-d on XPS 9310

[Fabrizio Romano Genovese]

Ok, my BIOS wasn't updated. That solved the VT-d problem.

Everything seems to work aside of wifi. I have a Killer AX500, which is 
currently supported only in kernel 5.10+. For what I understand, in Qubes 
Fedora comes with Kernel 5.4.something at the moment. I've found some 
tutorials to update a generic Fedora kernel to 5.10, but I suppose the 
kernel I'm running now is customized to be ran within a qubes environment. 
If I try to compile and update sys-net to kernel 5.10 how likely it is that 
I'll make a mess?

Fab
On Sunday, January 31, 2021 at 9:05:07 PM UTC+1 awokd wrote:

> donoban:
> > 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 newer
> > Xen version (although is pretty unstable yet). It will help to know if a
> > newer Xen version runs ok.
> > 
> Try donoban's suggestions for sure, but if that still doesn't help you 
> might get more pointers in the log from messages just prior to the one 
> quoted above. Disabling onboard/PCIe devices such as USB 
> controllers/network cards might let you work around the problem as well.
>
> -- 
> - 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/78d15468-9d35-408f-8f29-9db18ef3f000n%40googlegroups.com.

[qubes-users] Re: VT-d on XPS 9310

[Fabrizio Romano Genovese]

Ok, I found something: Running `xl dmesg` there's a line that says:
(XEN) Failed to parse ACPI DMAR. Disabling VT-d.

The output of `dmesg` looks very technical and is unreadable to me if I 
don't know what I'm looking for.

...I guess VT-x is enabled as well. In bios I have only the options 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 (CPU is intel i7 1165G7). 
>> VT-d is moreover enabled in my bios. Any clue about what the problem could 
>> be?
>>
>> 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 qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/a008af07-9a1a-4d13-9180-638bc03bad45n%40googlegroups.com.

[qubes-users] VT-d on XPS 9310

[Fabrizio Romano Genovese]

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 (CPU is intel i7 1165G7). 
VT-d is moreover enabled in my bios. Any clue about what the problem could 
be?

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 qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/f1120e83-96c2-4acc-82ac-34bee3c9b6abn%40googlegroups.com.

[qubes-users] Re: XPS 13 9310 - Installation fails at boot, Stuck at "xen is relinquishing vga console"

[Fabrizio Romano Genovese]

Someone mailed me some suggestions, but probably did it directly and the 
email does not show in the thread.

Anyway: 
-The installer can take a long time to show up, so I left the pc on 
overnight, but nothing happens. When I woke up I got the same black screen.
- Keyboard layout is US International
- My Chipset is Intel i7-1165G7, which comes with Intel Iris Xe Graphics. I 
have no other GPU on my pc.
- For the boot messages yes, I can take pictures. The output is very arid 
tho. I managed to get more stuff printed on screen by following this 
suggestion:
https://github.com/QubesOS/qubes-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 downloaded the most recent 4.1 alpha ISO from 
> https://openqa.qubes-os.org hoping that a maybe a newer xen version/linux 
> kernel would have helped. The installer freezes anyway, and selecting the 
> verbose mode in the boot menu I get exactly the same message as before 
> before 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 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 under 8GB, and disabled 
>> secure boot in the firmware. 
>>
>> Everything goes well and I can get xen to boot, but then it gets stuck at 
>> `xen is relinquishing vga console`, pretty much as it happens in this 
>> related issue: https://github.com/QubesOS/qubes-issues/issues/5165 
>>
>> I've tried fiddling with different options found both in the Qubes Issues 
>> repo and in the UEFI throubleshooting, but I wasn't successful. 
>>
>> Any help would be appreciated, starting from a very simple fact: Is there 
>> a way to access the xen boot logs? They go very fast on my screen and it's 
>> difficult to get what's going on.
>>
>> 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 qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/678cc12d-f238-4d26-8316-f068756a11d9n%40googlegroups.com.

[qubes-users] Re: Qubes Installer needs update (Part 3 of 3)

[Fabrizio Romano Genovese]

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, 2020 at 10:29:25 PM UTC+1 Ulrich Windl wrote:

> Final Hi!
>
> As can be seen from the issues reported before, it's _very_ hard for the 
> average or beginning user to diagnose when installation or boot fails.
> Therefore (knowing it's bad security and privacy wise) I suggest an 
> addition "blackbox log" debugging aid:
> Can't a log be written on the EFI partition (during install or during 
> boot).
> Then in theory one could read that log using some common operating system 
> and send them for inspection.
>
> Frustrated,
> Ulrich
>
>

-- 
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/473ca747-a3d6-4f6e-bed3-4d4734f69001n%40googlegroups.com.

[qubes-users] Re: XPS 13 9310 - Installation fails at boot, Stuck at "xen is relinquishing vga console"

[Fabrizio Romano Genovese]

So, a small update: I downloaded the most recent 4.1 alpha ISO from 
https://openqa.qubes-os.org hoping that a maybe a newer xen version/linux 
kernel would have helped. The installer freezes anyway, and selecting the 
verbose mode in the boot menu I get exactly the same message as before 
before 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 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 under 8GB, and disabled 
> secure boot in the firmware. 
>
> Everything goes well and I can get xen to boot, but then it gets stuck at 
> `xen is relinquishing vga console`, pretty much as it happens in this 
> related issue: https://github.com/QubesOS/qubes-issues/issues/5165 
>
> I've tried fiddling with different options found both in the Qubes Issues 
> repo and in the UEFI throubleshooting, but I wasn't successful. 
>
> Any help would be appreciated, starting from a very simple fact: Is there 
> a way to access the xen boot logs? They go very fast on my screen and it's 
> difficult to get what's going on.
>
> 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 qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/80587275-ce83-4e35-837a-956374c6713dn%40googlegroups.com.

[qubes-users] XPS 13 9310 - Installation fails at boot, Stuck at "xen is relinquishing vga console"

[Fabrizio Romano Genovese]

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 under 8GB, and disabled 
secure boot in the firmware. 

Everything goes well and I can get xen to boot, but then it gets stuck at 
`xen is relinquishing vga console`, pretty much as it happens in this 
related issue: https://github.com/QubesOS/qubes-issues/issues/5165 

I've tried fiddling with different options found both in the Qubes Issues 
repo and in the UEFI throubleshooting, but I wasn't successful. 

Any help would be appreciated, starting from a very simple fact: Is there a 
way to access the xen boot logs? They go very fast on my screen and it's 
difficult to get what's going on.

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 qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/27fd57ce-d105-4027-8121-1370089f8050n%40googlegroups.com.

Re: [qubes-users] Graphic Tablet Compatibility (basic features)

[Fabrizio Romano Genovese]

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 any reference to 
Wacom in the hid-core.c, and replaced the old drivers with the new one. Still, 
no effect whatsoever. 

Interestingly enough, giving 
cat /sys/kernel/debug/usb/devices
tells me that 
T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  4 Spd=12   MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=32 #Cfgs=  1
P:  Vendor=056a ProdID=00dd Rev= 1.02
S:  Manufacturer=Wacom Co.,Ltd.
S:  Product=CTL-470
C:* #Ifs= 2 Cfg#= 1 Atr=80 MxPwr= 98mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=usbhid
E:  Ad=81(I) Atr=03(Int.) MxPS=  10 Ivl=2ms
I:* If#= 1 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=00 Prot=00 Driver=usbhid
E:  Ad=82(I) Atr=03(Int.) MxPS=  64 Ivl=2ms

So the driver used is the right one. Only, usbhid doesn't recognize my tablet 
as a mouse. I feel like I'm out of options :/

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/27e9182d-6bb7-4271-83e8-1d81eee6bede%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Graphic Tablet Compatibility (basic features)

[Fabrizio Romano Genovese]

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 ctrl+shift+v right :P)

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/30ce8576-e378-4a93-9cd9-3cf05d7ee3a6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Graphic Tablet Compatibility (basic features)

[Fabrizio Romano Genovese]

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 fedora, I wanted to try something easier 
before. In the comments someone says

"I found it easier to add usbhid.quirks=0x056a:0x0318:0x4000 to the kernel 
commandline in /etc/default/grub.
0x4000 is HID_QUIRK_NO_IGNORE. The first two numbers is the device’s ID."

So I tried to do the same. I clone the template-vm on which sys-usb is based 
and I added in /etc/default/grub
usbhid.quirks=0x056a:0x00dd:0x4000

where 056a identifies wacom as producer and 00dd is my product number, found in
/sys/kernel/debug/usb/devices.

When I rebooted nothing happened. I also tried to put this line in grub.qubes, 
with no success whatsoever. Then I tried following the guide, but I fail pretty 
quicly: Trying to remove 

/lib/modules/4.9.56-21.pvops.qubes.x86_64/kernel/drivers/input/tablet/wacom_serial4.ko
 

Gives me the error

/lib/modules/4.9.56-21.pvops.qubes.x86_64/kernel/drivers/input/tablet/wacom_serial4.ko
 

Then I tried at least to monitor usb with usbmon. I gave

modprobe usbmon 

and then started monitoring my wacom tablet, that is on 2u, with:

sudo cat /sys/kernel/debug/usb/usbmon/2u

usbmon doesn't sense anything when I move the pen on the tablet, it only senses 
something when I connect/disconnect it. When I connect the tablet I get:

8cefcce66540 3453394997 C Ii:2:001:1 0:2048 2 = 0200
8cefcce66540 3453395017 S Ii:2:001:1 -115:2048 4 <
8cefca1b00c0 3453395039 S Ci:2:001:0 s a3 00  0001 0004 4 <
8cefca1b00c0 3453395053 C Ci:2:001:0 0 4 = 01010100
8cefca1b00c0 3453395057 S Co:2:001:0 s 23 01 0010 0001  0
8cefca1b00c0 3453395067 C Co:2:001:0 0 0
8cefca1b00c0 3453395072 S Ci:2:001:0 s a3 00  0001 0004 4 <
8cefca1b00c0 3453395086 C Ci:2:001:0 0 4 = 0101
8cefca1b00c0 3453422046 S Ci:2:001:0 s a3 00  0001 0004 4 <
8cefca1b00c0 3453422064 C Ci:2:001:0 0 4 = 0101
8cefca1b00c0 3453449146 S Ci:2:001:0 s a3 00  0001 0004 4 <
8cefca1b00c0 3453449166 C Ci:2:001:0 0 4 = 0101
8cefca1b00c0 3453476120 S Ci:2:001:0 s a3 00  0001 0004 4 <
8cefca1b00c0 3453476138 C Ci:2:001:0 0 4 = 0101
8cefca1b00c0 3453503126 S Ci:2:001:0 s a3 00  0001 0004 4 <
8cefca1b00c0 3453503155 C Ci:2:001:0 0 4 = 0101
8cefca1b00c0 3453503256 S Co:2:001:0 s 23 03 0004 0001  0
8cefca1b00c0 3453503279 C Co:2:001:0 0 0
8cefca1b00c0 3453555111 S Ci:2:001:0 s a3 00  0001 0004 4 <
8cefca1b00c0 3453555135 C Ci:2:001:0 0 4 = 1101
8cefca1b00c0 3453607116 S Ci:2:001:0 s a3 00  0001 0004 4 <
8cefca1b00c0 3453607141 C Ci:2:001:0 0 4 = 03011000
8cefca1b00c0 3453607152 S Co:2:001:0 s 23 01 0014 0001  0
8cefca1b00c0 3453607162 C Co:2:001:0 0 0
8cefca1b00c0 3453659185 S Ci:2:000:0 s 80 06 0100  0040 64 <
8cefca1b00c0 3453659601 C Ci:2:000:0 0 18 = 12010002 0020 6a05dd00 
02010102 0001
8cefca1b00c0 3453659620 S Co:2:001:0 s 23 03 0004 0001  0
8cefca1b00c0 3453659633 C Co:2:001:0 0 0
8cefca1b00c0 3453711790 S Ci:2:001:0 s a3 00  0001 0004 4 <
8cefca1b00c0 3453711808 C Ci:2:001:0 0 4 = 1101
8cefca1b00c0 3453763103 S Ci:2:001:0 s a3 00  0001 0004 4 <
8cefca1b00c0 3453763128 C Ci:2:001:0 0 4 = 03011000
8cefca1b00c0 3453763133 S Co:2:001:0 s 23 01 0014 0001  0
8cefca1b00c0 3453763143 C Co:2:001:0 0 0
8cefca1b00c0 3453827084 S Ci:2:006:0 s 80 06 0100  0012 18 <
8cefca1b00c0 3453827583 C Ci:2:006:0 0 18 = 12010002 0020 6a05dd00 
02010102 0001
8cefca1b00c0 3453827613 S Ci:2:006:0 s 80 06 0600  000a 10 <
8cefca1b00c0 3453827726 C Ci:2:006:0 -32 0
8cefca1b00c0 3453827741 S Ci:2:006:0 s 80 06 0600  000a 10 <
8cefca1b00c0 3453827856 C Ci:2:006:0 -32 0
8cefca1b00c0 3453827871 S Ci:2:006:0 s 80 06 0600  000a 10 <
8cefca1b00c0 3453828010 C Ci:2:006:0 -32 0
8cefca1b00c0 3453828038 S Ci:2:006:0 s 80 06 0200  0009 9 <
8cefca1b00c0 3453828359 C Ci:2:006:0 0 9 = 09023b00 02010080 31
8cefca1b00c0 3453828384 S Ci:2:006:0 s 80 06 0200  003b 59 <
8cefca1b00c0 3453829398 C Ci:2:006:0 0 59 = 09023b00 02010080 31090400 
00010301 02000921 10010001 22b80007 0581030a
8cefca1b00c0 3453829420 S Ci:2:006:0 s 80 06 0300  00ff 255 <
8cefca1b00c0 3453829624 C Ci:2:006:0 0 4 = 04030904
8cefca1b00c0 3453829642 S Ci:2:006:0 s 80 06 0302 0409 00ff 255 <
8cefca1b00c0 3453830002 C Ci:2:006:0 0 16 = 10034300 54004c00 2d003400 
37003000
8cefca1b00c0 3453830023 S Ci:2:006:0 s 80 06 0301 0409 00ff 255 <
8cefca1b00c0 3453830594 C Ci:2:006:0 0 30 = 1e035700 61006300 6f006d00 
20004300 6f002e00 2c004c00 74006400 2e00
8cefca1b0cc0 3453831094 S Co:2:006:0 s 00 09 0001   0

[qubes-users] Re: Qubes 4.0 rc3 boot and performance is quite slow

[Fabrizio Romano Genovese]

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 reboots and then I'll 
confirm if and how this helped.

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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/17c482cf-9274-4b62-aa94-9a0868465425%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Graphic Tablet Compatibility (basic features)

[Fabrizio Romano Genovese]

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. The tablet is listed among 
the usb devices but, if for instance one is using the standard fedora template, 
nothing is shown clicking on the "wacom tablet" application that can be found 
in /urs/share/applications, nor is it possible to use it to draw stuff.

This looks like an old issue:
https://github.com/QubesOS/qubes-issues/issues/2715

I'd be interested in using only the basic tablet features (essentially moving 
the mouse and clicking around using the tablet would be enough). In the issue 
linked above it is said that 

"this in theory should be easy (a matter adding proper metadata - min/max - to 
the protocol handshake, and filtering events based on this info)"

I'd like to help with this, but I am no coder. I just know a bit of bash 
scripting and trying to check the code in 

https://github.com/QubesOS/qubes-app-linux-input-proxy/blob/master/src/protocol.h#L17-L28

didn't really help. I understand that developers are quite busy with much more 
hardcore problems to solve, but if someone could at least point me to the right 
research direction I could try to investigate this by myself.

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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/c5aeb07c-25ad-4d71-913d-369f08980fef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes 4.0 rc3 boot and performance is quite slow

[Fabrizio Romano Genovese]

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 stays the same.

Booting unplugged: FUBAR. Slow, unresponsive, battery draining over 9000. 
Plugging AC adapter in afterwards doesn't help at all.

Dunno if my intuition is the right one, but it may be that the booting process, 
when unplugged, triggers some sort of fucked up setting regarding power 
management that causes havoc. Note that, in my case, the only important factor 
to consider is if the AC adapter is plugged/unplugged AT BOOT. 
Connecting/disconnecting it afterwards has no effect whatsoever on performance.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/a089f789-47ea-493e-be0a-dc8630ed8897%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes 4.0 rc3 boot and performance is quite slow

[Fabrizio Romano Genovese]

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 instance if I 
type qvm-ls I obtain some output straight away. Moreover, if I start a VM the 
notification "VM blabla is starting" is displayed immediately.

- When QubesOS is not happy, it starts in ~3mins. The overall system is very 
slow, qvm-ls takes 3-4 seconds to display output, and starting a VM takes up to 
20 seconds. Even the notification "VM blabla is starting" is displayed 4-5 
seconds after the command is issued. Moreover the battery is drained much much 
quicker (200% quicker give or take).

What makes Qubes happy or not happy to start seems to be completely random. I 
have a slight suspect that this may depend on booting the laptop while 
plugged/unplugged, but I cannot confirm this.
Essentially my Qubes experience atm can be exemplified as follows: "At boot, 
throw a coin. If it's heads then it's fine, otherwise it's fubar". Any 
suggestion (or report of similar behavior) would be greatly appreciated!

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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/938de199-7b6f-4132-983e-0720f1929720%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Netowork Manager not running (minimal VM)

[Fabrizio Romano Genovese]

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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/48939291-4b96-4530-9d11-bae7fe3c66e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes 4.0 rc3, Whonix template: update-command-not-found

[Fabrizio Romano Genovese]

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 applications, run 
update-command-not-found as root to fix this"

Equivalently, you may just directly try to type 'update-command-not-found' and 
find that the template tries to curl some files without success...

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/8561b5a9-7229-4035-ba65-05c40f298be4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Qubes 4.0 rc3, Whonix template: update-command-not-found

[Fabrizio Romano Genovese]

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 the database of available applications, run 
update-command-not-found as root to fix this"

If I try to give sudo update-command-not found then whonix tries to curl some 
files, but not having any connection (template vm) fails. The result of this is 
that I have to run this command directly in the interested appvm, EVERY TIME I 
start them up. Is there a way to make whonix communicate with the outside 
world, so that curl succeeds?

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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20f4a89e-3012-4868-93df-a49c2b15d85c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Netowork Manager not running (minimal VM)

[Fabrizio Romano Genovese]

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 suggest to 
>mention (at least) the existence of the qubes-core-agent-... packages in 
https://www.qubes-os.org/doc/software-update-vm/

I'd also suggest to mention qubes-core-agent-passwordless-root in 
https://www.qubes-os.org/doc/vm-sudo/

I am aware that building an entire operating system is a lot of work and there 
are literally thousands of packages, always changing, to consider. But pages 
like these should be kept up to date. I wouldn't suggest to edit them (some 
information that is still useful for previous qubes versions may be lost), but 
just to index them according to qubes new versions: I'd propose to have a qubes 
3.1, a qubes 3.2 and a qubes 4.0 section, for each page.

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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/fa908829-0448-4ba9-b68a-c9a39b839c73%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Netowork Manager not running (minimal VM)

[Fabrizio Romano Genovese]

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
qubes-usb-proxy
Are not included by default in the minimal template vm. The first one gives you 
the cute (send here/move there/open in dispVM) stuff in Nautilus. 
The next two are (I suppose) to make networking not a pain in the bum.
The fourth one should do what is done in https://www.qubes-os.org/doc/vm-sudo/ 
for you. 
The fifth one is needed if you are setting up a template you'll use as the 
underlying one for the vm that takes care of updating dom0. 
The last two are to set up a template for sys-usb.

All this information was somewhere between here and the github issues page, but 
it should really (REALLY) be listed in 
https://www.qubes-os.org/doc/templates/fedora-minimal/ since nearly always one 
will end up needing at least one of the packages listed above.
At the moment setting up a template based on a minimal fedora distribution 
looks like a treasure hunt, and I am pretty sure it would save people a lot of 
energy and time to have this stuff added to the fedora-minimal reference page.

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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/fff5052c-6739-4179-aeaf-2989fcb8ea07%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Netowork Manager not running (minimal VM)

[Fabrizio Romano Genovese]

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 minimal template as the underlying one for sys-usb, 
but I still have problems with sys-net.

sys-net keeps telling me that NetworkManager is not running. If I open up a 
terminal and give sudo NetworkManager then i can see the networks clicking on 
the wifi tray icon, but I can't connect. If I click on a network nothing 
happens (no error displayed, of any kind. Just nothing). 

Any suggestions?

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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/5e1ebbf7-250c-46ac-b09d-41970235718e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Netowork Manager not running (minimal VM)

[Fabrizio Romano Genovese]

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:

Not authorized to perform operation (polkit authority not available and caller 
is not uid0), so again an authorization issue. I suspect this may have 
something to do with the procedure to make the minimal template passwordless ( 
https://www.qubes-os.org/doc/vm-sudo/ )

If someone has some insight about this I'd really appreciate it :)

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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/698af639-dd30-40b3-82cc-eb4db5f1f2e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes 4rc3: More space needed on the / filesystem.

[Fabrizio Romano Genovese]

> 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 be supposed to start, it fails with the
> > message:
> > 
> > At least *MB more space needed on the / filesystem
> 
> Have you considered making the root filesystem of your VM have more space?
> 
> In the settings dialog for a VM its the "System storage max size" item which 
> you can change. Be aware that the VM likely needs to restart to access the 
> extra space.

I did and I solved the problem now, thanks. I have to say that the problem here 
was the absence of qubes-manager: I wasn't able to see where to set the root 
partition dimensions. Also, I am using i3, so the idea of moving "all the 
relevant stuff" to the start menu is like saying "we really, really hate our i3 
users" :D

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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/21bfa3ea-93eb-48f8-8369-ba254e7e2207%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Qubes 4.0 rc3 boot and performance is quite slow

[Fabrizio Romano Genovese]

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 
qvm-start someVM
the startup time is again quite slow. Could it be that my VMs are based on 
Fedora26?

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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/cf8c3f00-9b40-4f67-a633-233430679430%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Netowork Manager not running (minimal VM)

[Fabrizio Romano Genovese]

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 give 
sudo NetworkManager then I can see all the wireless networks I usually see in 
my place (hence the network card is recognized) but when I try to connect to 
one of them I receive the message
(1) Not authorized to control networking.

I suspect there is some service that needs to be started when the VM boots that 
I haven't specified, but I don't know how to proceed.

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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/3b9463d9-2407-45a1-9a3c-3e74d047785f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Disable root password on fedora-25-minimal (Qubes 4.0rc3)

[Fabrizio Romano Genovese]

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 
/etc/polkit-1/localauthority/50-local.d/qubes-allow-all.pkla

are to be created/edited in the VM, not in Dom0. This effectively solves the 
problem.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/2cd7e068-7238-4356-9220-9e8cafdc1718%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Qubes 4rc3: More space needed on the / filesystem.

[Fabrizio Romano Genovese]

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 / filesystem

I have tried to use qvm-block to attach some cache file to the vm (as 
suggested, for instance, in ( 
https://www.qubes-os.org/doc/template/fedora/upgrade-21-to-23/ )
but giving 

qvm-block attach fedora-26 cachefile.img 

produces the error 

qvm-block: error: backend vm 'dom0' doesn't expose device 'cachefile.img'

How do I solve this? I read around that qvm-block is buggy with loop devices, 
but I am not sure this is the kind of problem I am facing. I also supposed this 
may have something to do with having a sys-usb VM (the references I found to 
qvm-block usage are all very outdated and antecedent to the sys-usb era), but 
then again I don't know precisely how should I proceed.

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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/d309ba18-bd7f-4612-9980-24d74da529d2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Disable root password on fedora-25-minimal (Qubes 4.0rc3)

[Fabrizio Romano Genovese]

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

on a "standard" terminal shell, I will be prompted for a password. 

I already checked at 

https://www.qubes-os.org/doc/vm-sudo/

What I don't have there is the file and 
/etc/polkit-1/localauthority/50-local.d/qubes-allow-all.pkla. Should I add it?

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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/fa8ea166-ad10-412a-9a66-6d6a34037c01%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Disable root password on fedora-25-minimal (Qubes 4.0rc3)

[Fabrizio Romano Genovese]

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 editing the /etc/shadow file to remove the root password, 
with no success whatsoever. I basically would like my minimal template to 
behave like any other, that is, to have a passwordless root. Any help would be 
greatly appreciated!

Thanks for your Time,
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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/9cfbdb37-f52f-4650-8c86-f1d2f98e0178%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Enable PCI_HOTPLUG

[Fabrizio Romano Genovese]

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 aware of the risks of having PCI hotplug enabled, but I do not take my PC 
out of my house very often, so it is in general quite difficult for someone to 
have physical access to it. Moreover, I also use thunderbird port blockers 
(that are just some plastic caps that you stick into your port and can't take 
out without a particular key). Obviously this solution is still not 100% secure 
but, all things considered, it is enough for my use case.
So, how do I enable PCI hotplug? Do I have to manually compile the kernel? I'm 
a total noob when it comes to this sort of things so if someone could at least 
redirect me to a guide to do this I'd really appreciate it!

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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/2e720f96-f8c2-420a-8968-6a47c10bfd9f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Screensaver timer resets automatically

[Fabrizio Romano Genovese]

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 blanks. If I give 
xset s 5 5
then the screen blanks correctly after 5 seconds, but after some more seconds 
(~15 usually) my pc wakes up again, even if I do not touch mouse/keyboard at 
all. After 5 seconds this cycle starts again.

It is quite clear to me that there is something that is mistakenly registered 
as user activity and that periodically resets my screensaver timer, the only 
problem is that I do not know how to find which process/service/whatever causes 
this. Is there a way to find out what resets this timer?

Thanks for your Time,
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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/2ae7ccb5-79ce-4689-8b8a-4f7dd23e04ac%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes 3.0 RC2 on Alienware M17XR3: What works and what not.

[Fabrizio Romano Genovese]

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
entirely on the intel one.

At the end of the day, I bought a linux 100% compatible laptop and now I'm
happier than ever. I installed Windows and a shitload of emulators on the
good old Alienware and I use it for what is meant for, gaming. There is no
personal data whatsoever on the PC now, so this approach does not spoil my
privacy and security.

I'm pretty sure you can make a lot of stuff work with a sufficient amount
of headaches and swearing, but in the end some things won't be fixable
(drivers issues, mainly). Also, you should consider that Qubes won't make
justice to such a beautiful machine, and that you may not be able to use
most of the nice features of the Alienware. I love Qubes but according to
my experience Alienware is not the kind of computer you want it installed
on. This is obviously just my personal opinion, so take it for what is
worth (nothing :P )

Cheers,
Fab

On Fri, Mar 17, 2017 at 11:23 PM,  wrote:

> How did you get it installed? Did you do anything special?
>
> Im currently trying to install on an Alienware 17 r4; GeForce GTX 1060;
> and the GUI Installations Screens fail and the text based install has bugs
> that wont let me get past partitioning due to LUKS not getting a password.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "qubes-users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/qubes-users/ogKupxioIAQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> qubes-users+unsubscr...@googlegroups.com.
> To post to this group, send email to qubes-users@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/qubes-users/07a22d4f-4fce-49cb-81ac-c92e48304100%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CAAZqLaOR4YsdSHMSd7XsZNLSryg4VUMAWtEgxFw4xSeywNxf%3Dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Assigning microphone to AppVM from terminal

[Fabrizio Romano Genovese]

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 attach/detach my
> camera to an appvm. For the sake of completeness, I'd like to do the same
> for the internal microphone.
>
> https://github.com/rustybird/qubes-stuff/blob/master/dom0/
> bin/qvm-microphone
>
> Rusty
> -BEGIN PGP SIGNATURE-
>
> iQJ8BAEBCgBmBQJYvWDiXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
> ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4NEI1OUJDRkM2MkIxMjlGRTFCMDZEMDQ0
> NjlENzhGNDdBQUYyQURGAAoJEEadePR6ryrfoD8P/1Of6v/HyTh/mw/P8+K/CARY
> H+4f1IvASKO5srRM2vYtDs+kEyU+ykN/Rs05ru3HCmI2NVRfrVQftRlZqx55JIgm
> 6/mEud28WuLAk+ZwRsDEtklgsdIc+XshbvoW9yjuVTruD7KoC361LfqLjG7NJRzO
> EEbKwjTK3PsZLpedUAzokE/xfEDhbxUhWDPZMKuOz5zkuMZVW8dQFU/va7+xsAHO
> IPB9FsJk0kTN43OaeUGado7z5N5UQOfmXMEM12fAj3KHbGm8nV9cyEF3xmN48ey9
> tZ/Zykmw7OahTBqXROzDLXLbkVFKpR86YQE1fIx7KM9Lqz6VGPn7L/zBsHz3dG4z
> RXpC9X/WibY1CZek3myI7Jstd4LkGW8WH7PTwgZwUP61LpnH/gsJukDM4CEjBWGX
> NuqRFmhokBqjkHGmumzW+h0I7DSnPULkGGy5tHULQ4HOm5r4o/O5LTTEgHMQHSPQ
> jaQxoSVRZ2fdpu1BE7nPTqlt0/gFP9HesEy7q6Q5OlQg38k7j+oe6LHtKWQ272B4
> 3LQbQXmvCkHXoIew72ywN8WkFEuBy6uArGwetIDZ53bderxep+Bvo1064DUwObf/
> KJ1rRYlIlapa5fECPZ6UJyseLlGOgOSCopSLEY6T83LC0ZmOa0HzJDKi8CfoNt/Z
> ltlD2fZXowwhhM8ToKpk
> =kAjE
> -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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CAAZqLaNLRxgF8nC3JHwmA5Pk2bKafi7boxLg4SP4jtRgaoF%2BEQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Assigning microphone to AppVM from terminal

[Fabrizio Romano Genovese]

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 kind of script in dom0 that is invoked to perform this 
operation.The problem is that I don't know where I have to look to find it.

Can someone help me?

Thanks for your Time,
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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/d36dae6c-98ca-4d3b-9893-cd5a1d648820%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Global updates question

[Fabrizio Romano Genovese]

Thanks everyone, that code does exactly what I wanted. Calling
bash /etc/qubes-rpc/qubes.InstallUpdatesGUI
with qvm-run for a given VM produces the same result of uptating the VM via
qubes-manager.

Thanks for your Time,
Fab

T

On Fri, Feb 17, 2017 at 4:18 AM, Jean-Philippe Ouellet <j...@vt.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 & I can launch
> all
> > the terminals at the same time, while cycling as in the script you
> linked I
> > should wait for the previous update process to finish.
>
> Not if you just background the process, like:
>
> for dom in templateA templateB ...; do
> qvm-run -p -u root some-template 'dnf update' &
> done
>
> Anyway... the code you're looking for is here:
> https://github.com/QubesOS/qubes-core-agent-linux/blob/
> master/qubes-rpc/qubes.InstallUpdatesGUI
>

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CAAZqLaPKZ0T5dgFhgSJo-kR2zwq1BUtY3S5YNmH0nCBcb6VC-A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Global updates question

[Fabrizio Romano Genovese]

Well, I have considered it, yes, and it's true that launching many
terminals can be resource intensive. But it's also faster:  Using & I can
launch all the terminals at the same time, while cycling as in the script
you linked I should wait for the previous update process to finish.

Moreover, I confess that staring at the terminals for 5 mins every couple
of days relaxes me, so I like it better :)

Anyway I feel like I'm missing something, what I want to do doesn't look so
difficult and I'm not sure why it doesn't work!

Cheers,
Fab

On Fri, Feb 17, 2017 at 2:50 AM, Andrew David 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 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 the terminal in every
> > template vm, feeding it a nice 'sudo dnf update' - When the update
> > is finished, one should have the chance to close the vm by
> > pressing enter like it happens now on qubes manager.
> >
> > I already implemented the first point (window layout) but I'm
> > having problems at launching the terminals in the right way. I'm
> > basically passing to the vm commands like 'xterm -e "sudo dnf
> > update"', but what happens is that the terminal opens up, checks
> > for updates and then closes without giving me the chance to say
> > y/n.
> >
> > As I mentioned above, in qubes manager when one clicks on "update
> > vm" a nice terminal window opens up, does everything it has to do
> > and then asks you if you want to shutdown the vm or not by
> > pressing enter or control+c, respectively, if I remember well.
> > Since I would really like to have a similar feature in my script, I
> > am wondering if qubes-manager calls some script to behave like it
> > does.
> >
> > If this is the case, I could just call the same script once for
> > every template and solve my problems without struggle.
> >
> > Thanks for your Time, Fab
> >
>
> Have you considered not starting terminals in the TemplateVMs? By
> using --pass-io and not starting the GUI of each TemplateVM, you can
> save resources and hassle. Here's an example:
>
> https://gist.github.com/andrewdavidwong/d0b109186de65835255d467ae103c289
>
> - --
> Andrew David Wong (Axon)
> Community Manager, Qubes OS
> https://www.qubes-os.org
> -BEGIN PGP SIGNATURE-
>
> iQIcBAEBCgAGBQJYpmTdAAoJENtN07w5UDAwIhkP/R81vgO979DTCObP/hKE2E5h
> 0m5ewGt3TH1Ing51Ueiws8PoYdNDyAkPogdXG4cQZX4a4kMzyzEjJ/zzEzddzoDQ
> 32uFSYzEq7el+eoKyS+OiYiniFlDy4RFAIsjDndkiC+ZPGbfEcvgrrzvm7Ggdcvt
> cD+ZGJaoVOuoN6bRRqNkE73VAkSFoIG0LOeaK/keqJwZobQo28UdMYtvsGvONsDR
> 2vWjDO0jT1K0UEsp0eYuqWDN9B8Ihzw+dYDhSzbKrF3nMGPNXxjcE4edsVdmvL6m
> LzCRisoi2k+C+w/AMFjHNjmxTUrx+Gw2/YoytWsXFrCXUIJSr5g/kWyoqVdKVCtx
> hwOxVFQQdTDJFUl5vbb+9CvAjc6EXddASslyfXXC3iB1mEAy7ATHvSsMiIup/Lx9
> mj2HUk3X6j8uxALo1/+31cqfegEYpuXRtYxRz8sRxFlo9AYDRRNGKgWIn9OJgxl8
> 6mZ/Cfj2qPDttKvPsYhtvUftiTALzy5g5wZLzQh6SEWCizwkR7dUxeX5k/XMWREg
> 9d4WgN2zQ3kTN2FtgNFhd37T/O5z4MZoXWMgcwGW3ZgygGNeO9g+t+OqAYypaHQZ
> 4I0iCIhZTaOC74x0o2yiGd6IKnWLHFXJj+igOKmRve1KE/x0e+EMgahcsKnY0dbM
> OmaMAnd1i7oT+ngnDdSJ
> =X6k5
> -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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CAAZqLaPzjjwqchAfk3RXMBX6ff5yMdvW8cuKF3abTbEjYd053g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Global updates question

[Fabrizio Romano Genovese]

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 the terminal in every template vm, feeding it a nice 'sudo 
dnf update'
- When the update is finished, one should have the chance to close the vm by 
pressing enter like it happens now on qubes manager.

I already implemented the first point (window layout) but I'm having problems 
at launching the terminals in the right way. I'm basically passing to the vm 
commands like 'xterm -e "sudo dnf update"', but what happens is that the 
terminal opens up, checks for updates and then closes without giving me the 
chance to say y/n. 

As I mentioned above, in qubes manager when one clicks on "update vm" a nice 
terminal window opens up, does everything it has to do and then asks you if you 
want to shutdown the vm or not by pressing enter or control+c, respectively, if 
I remember well.
Since I would really like to have a similar feature in my script, I am 
wondering if qubes-manager calls some script to behave like it does.

If this is the case, I could just call the same script once for every template 
and solve my problems without struggle.

Thanks for your Time,
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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/bfd89968-9bb5-464c-a091-0f7f2e229ef1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] qvm-trim-template fails (Qubes 3.2)

[Fabrizio Romano Genovese]

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 Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/1a41543f-21aa-40d6-aee6-11222a647ba1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] qvm-trim-template fails (Qubes 3.2)

[Fabrizio Romano Genovese]

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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/82b9ca5d-632a-4fdc-a2b7-2a47ad9bb88b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] qvm-trim-template fails (Qubes 3.2)

[Fabrizio Romano Genovese]

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 /srv/salt/update-templates.sls and wrote 

uptodate:
 pkg.uptodate: []

into it. Then I created /srv/salt/update-templates.top and wrote 

base:
 qubes:type:template:
  - match: pillar
  - update-templates 

into it. Then I gave ' sudo qubesctl top.enalbe update-templates ' and tested 
it with ' sudo qubesctl --all state.highstate ' (these commands don't work for 
me if I'm not superuser). unfortunately, this doesn't work for me. There is 
some green stuff going on (like qvm.exists and other things that I don't really 
understand). Then, it runs through the templates returning errors (it basically 
says, as an instance, 'fedora-23: ERROR'). On the app vm it just skips saying 
that there is nothing to do (and this is what it is supposed to do, so at least 
it recognizes that it has to run only on templates).

My feeling (that may be wrong, obviously) is that the command  pkg.uptodate: [] 
does not work for god only knows what reason. Any idea?

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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/28a0a898-f265-4189-9d05-d3578eb2a1dc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Fedora 24 Network Manager icon is missing (and other small issues).

[Fabrizio Romano Genovese]

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) Fonts look a bit changed. Again, not that much of a problem, it's just 
unexpected.

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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/80a6a6a6-55de-400c-87a3-0c078d0bdeda%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] qvm-trim-template fails (Qubes 3.2)

[Fabrizio Romano Genovese]

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 little script to automatize the 
trim process for all my templates at once, but it is evident that I must have 
made some mistake while doing it :D

Anyway, a "global trim function", as well as a "global update function" would 
be very helpful, updating/trimming of templates can be quite time consuming!

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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/53fffefd-49a7-4422-82d1-1e2eacc144a2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] qvm-trim-template fails (Qubes 3.2)

[Fabrizio Romano Genovese]

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 linked thread, rebooting doesn't help. I don't understand 
the proposed solution. I tried to remove the temporary vm (that in my case it 
has name trim-template-name) giving 

'qvm-remove trim-template-name'

but I get the error

'A VM with the name 'trim-template-name' does not exist in the system.'

Can you help me? My Template VM are becoming a bit too big now...

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/26eeb42b-9e46-410c-aee2-42a616e63307%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Needed Packages for sys-usb on Fedora-minimal

[Fabrizio Romano Genovese]

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 emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/398a403e-bf21-4a4a-aaf9-30bcbcb20c48%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Needed Packages for sys-usb on Fedora-minimal

[Fabrizio Romano Genovese]

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 something, since if I plug a USB key in it 
doesn't get recognized. Any suggestion about what packages may I need for a 
smooth usb experience on this template?

Thanks for your help,
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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/db26a976-61e0-4834-ae54-d3f6f20b9422%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.