Thanks Marcus! Interesting thread. How do I apply any of their solutions in
the installer, though?
Also, since it is just a little tedious (to click on every button and hold
and drag etc.) or can be fixed with a different mouse (at least according
to that thread) people might be interested to k
Once QWT was installed, the next reboot or two takes longer to finalise all the
qubes settings and transfer user folders etc.
I was getting stuck here again and again until I realised I'd been overlooking
this step (in Dom0) from the windows appvm guide.
qvm-prefs -s qrexec_timeout 300
I found how to fix problem with gnome terminal. It was issue with "locale".
And seems sys-whonix work, but does does not answer to ping.
Also very disappointed with Qubes shutdown :( It's never end...
--
You received this message because you are subscribed to the Google Groups
"qubes-users"
On Sun, Jun 26, 2016 at 12:46 PM, Andrew David Wong
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 2016-06-26 06:33, Salmiakki wrote:
> > Currently the installer does not allow me to create USB qubes
> > because I am using a USB keyboard. I do however have 3 USB
> > controllers
Hi,
Got some updates, it appears the problem was caused due to UEFI issues as
described here - https://www.qubes-os.org/doc/uefi-troubleshooting/
I manage to install Qubes R3.2Rc1 and followed the instructions in order to
append the mapbs=1
& noexitboot=1 to the file /mnt/sysimage/boot/efi/EFI/
On Wednesday, June 22, 2016 at 6:26:50 PM UTC+3, Marcus at WetwareLabs
wrote:
>
> Hello all,
>
> I've been tinkering with GPU passthrough these couple of weeks and I
> thought I should now share some of my findings. It's not so much unlike the
> earlier report on GPU passthrough here (
> https
I do not know what happens.
1) Maybe template update or dom0 latest update, but I can not start gnome
terminal for some VMs. Most of all for TemplateVMs and for ProxyVMs. New
tab appeared and pointer show "loading" then new tab close/crash without
starting window,
2) sys-whonix not work for
On 06/26/2016 02:08 PM, 41wycb+5v6q0qb48s8dk via qubes-users wrote:
Hello,
I've disabled all support for UEFI in the BIOS, having enabled only support to
Legacy mode. I've also disabled the secure boot having enabled the 'USB UEFI
BIOS Support'.
At this stage I'm able to get the grub splash
On Friday, June 24, 2016 at 11:10:58 AM UTC+3, Salmiakki wrote:
>
> I tried installing 3.2 this morning but in the installer whenever I click
> the left mouse button the cursor jumps to the left edge of the screen.
>
> I can still click buttons by clicking+holding then moving back to the
> butt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-06-26 12:07, Niels Kobschaetzki wrote:
> On 16/06/26 08:40, Andrew David Wong wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA512
>>
>> On 2016-06-26 04:27, Niels Kobschaetzki wrote:
>>> Hi,
>>>
>>> does anyone have experiences with r
On 16/06/26 08:40, Andrew David Wong wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-06-26 04:27, Niels Kobschaetzki wrote:
Hi,
does anyone have experiences with running Crashplan in Qubes? If
yes, how did you install it?
Niels
I installed it in a StandaloneVM with the insta
Marek Marczykowski-Górecki:
> On Sun, Jun 26, 2016 at 05:07:44PM +, Andrew wrote:
>> Keld Norman:
>>> Started getting this today and lost my USB dedicated to my
>>> Standalone vm:
>>>
>>> ERROR in output from running "dmesg" > can't claim BAR 0 [mem
>>> 0xb4a2-0xb4a2 64bit]: address
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, Jun 26, 2016 at 05:07:44PM +, Andrew wrote:
> Keld Norman:
> > Started getting this today and lost my USB dedicated to my Standalone vm:
> >
> > ERROR in output from running "dmesg" > can't claim BAR 0 [mem
> > 0xb4a2-0xb4a2 6
Hello,
I've disabled all support for UEFI in the BIOS, having enabled only support to
Legacy mode. I've also disabled the secure boot having enabled the 'USB UEFI
BIOS Support'.
At this stage I'm able to get the grub splash screen and when I try to boot
Qubes I get:
'Loading xen.gz ok'
'L
Keld Norman:
> Started getting this today and lost my USB dedicated to my Standalone vm:
>
> ERROR in output from running "dmesg" > can't claim BAR 0 [mem
> 0xb4a2-0xb4a2 64bit]: address conflict with System RAM
>
> Any one here have an idea of what could have caused that problem ?
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-06-26 08:54, Salmiakki wrote:
> Yeah, but the installer does not seem to know that and refuses to
> create a USB qube for me which would be pretty handy even if I have
> to assign the controllers afterwards.
>
Ok, thanks for the suggestion.
Yeah, but the installer does not seem to know that and refuses to create a
USB qube for me which would be pretty handy even if I have to assign the
controllers afterwards.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-06-26 06:33, Salmiakki wrote:
> Currently the installer does not allow me to create USB qubes
> because I am using a USB keyboard. I do however have 3 USB
> controllers (as this is a desktop machine). So it would be nice if
> that worked s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-06-26 04:27, Niels Kobschaetzki wrote:
> Hi,
>
> does anyone have experiences with running Crashplan in Qubes? If
> yes, how did you install it?
>
> Niels
>
I installed it in a StandaloneVM with the installer's default options.
(As I'm g
Currently the installer does not allow me to create USB qubes because I am
using a USB keyboard. I do however have 3 USB controllers (as this is a
desktop machine). So it would be nice if that worked somehow...
--
You received this message because you are subscribed to the Google Groups
"qubes
On 06/26/2016 06:50 AM, Marek Marczykowski-Górecki wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, Jun 26, 2016 at 06:45:50AM -0400, Chris Laprise wrote:
More info, Marek...
When I try to scan the /dev/sdb device with partx, it says the device is not
readable or not valid devi
Hi,
does anyone have experiences with running Crashplan in Qubes? If yes,
how did you install it?
Niels
--
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-us
On 06/26/2016 06:50 AM, Marek Marczykowski-Górecki wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, Jun 26, 2016 at 06:45:50AM -0400, Chris Laprise wrote:
More info, Marek...
When I try to scan the /dev/sdb device with partx, it says the device is not
readable or not valid devi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, Jun 26, 2016 at 06:45:50AM -0400, Chris Laprise wrote:
> More info, Marek...
>
> When I try to scan the /dev/sdb device with partx, it says the device is not
> readable or not valid device.
>
> When I plug in another USB stick, the partitio
More info, Marek...
When I try to scan the /dev/sdb device with partx, it says the device is
not readable or not valid device.
When I plug in another USB stick, the partitions are enumerated as
/dev/sdc1 etc. but they cannot be mounted (devices are unreadable).
From dmesg, these errors occu
25 matches
Mail list logo
