Guest:
> Hi Awokd,
>> If there is no way to disable HDMI audio completely, perhaps try the
>> external monitor or blacklist suggestions in here:
>> https://github.com/QubesOS/qubes-issues/issues/5247.
>
> No option exists to disable HDMI Audio, or any VGA options for that matter in
> the BIOS
Hi Awokd,
>Thanks. Hope I'm not leading you on a wild goose chase.
Most tech things are once you get involved in the details ;-)
>That odd interrupt changed in Debian. I wonder if it is
>https://www.spinics.net/lists/kernel/msg2709360.html. Link is to a
>kernel issue that was occurring with i915
On 9/4/19 12:02 PM, unman wrote:
> On Wed, Sep 04, 2019 at 08:12:27AM +, ronpunz wrote:
>> I have fresh install of Q4.0.2rc1
>>
>> I've setup disposable vm's for sys-net and sys-firewall. Everything
>> works well (i can update Fedora and Whonix) via dispVMs. However, Debian
>> template
ubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/Lo2-PWM--B-1%40tutanota.com.
Qubes-HCL-LENOVO-20M60019SC-20190905-204549.yml
Description: application/yaml
On 9/3/19 10:12 PM, ronpunz wrote:
> I have fresh install of Q4.0.2rc1
>
> I've setup disposable vm's for sys-net and sys-firewall. Everything
> works well (i can update Fedora and Whonix) via dispVMs. However, Debian
> template updates fail because Debian is calling for updates via sys-net
>
unman:
> On Thu, Sep 05, 2019 at 12:23:13PM +0200, donoban wrote:
>> On 9/5/19 11:41 AM, qtpie wrote:> My usecase is this: suspend a laptop
>> with sys-whonix and whonix appvms
>>> running, then resume it a few hours later.
>>>
>>> After resume Tor lost connection, re-connection fails until i
On Wed, Sep 04, 2019 at 08:12:26PM -0400, Stumpy wrote:
> I have a hard drive that i cant seem to connect to any of the appvms yet I
> can see and access it via dom0 (not good i know).
> I can attach a usb flash drive to my appvms but not the hard drive?
>
> This is on my laptop and i do not have
On Thu, Sep 05, 2019 at 12:23:13PM +0200, donoban wrote:
> On 9/5/19 11:41 AM, qtpie wrote:> My usecase is this: suspend a laptop
> with sys-whonix and whonix appvms
> > running, then resume it a few hours later.
> >
> > After resume Tor lost connection, re-connection fails until i manually
> >
On 9/5/19 11:41 AM, qtpie wrote:> My usecase is this: suspend a laptop
with sys-whonix and whonix appvms
> running, then resume it a few hours later.
>
> After resume Tor lost connection, re-connection fails until i manually
> sync time on sys-net then
> @sys-firewall 'sudo ntpdate [timeserver]
>
donoban:
> On 9/3/19 9:31 PM, qtpie wrote:
>> The only issue I keep having with Qubes-Whonix, is that after
>> suspend/resume, Whonix-GW time is out of sync and cant connect to the
>> Tor network. According to Whonix the safe option is to simply not
>> suspend Whonix.
>>
>>
On Thursday, September 5, 2019 at 4:33:31 AM UTC-4, awokd wrote:
> b@gmail.com:
>
> > USB: I generally have not attached USB drives (utilizing the USB IP support
> > via `qvm-usb` aka `qvm-device usb`) to VMs as I find it slow and sometimes
> > buggy.
>
> I don't do that either, but using
brendan.h...@gmail.com:
USB: I generally have not attached USB drives (utilizing the USB IP support
via `qvm-usb` aka `qvm-device usb`) to VMs as I find it slow and sometimes
buggy.
I don't do that either, but using qvm-block to attach USB drives has
been stable for me. More secure too.
--
12 matches
Mail list logo
