HSZcfxQQaacNg6dl-TKD-iOwhcKbcI22liKgemdBcDZMAAq0cDwy4ks1kczz7l2z37S3Pa2tM%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.
Qubes-HCL-LENOVO-_INVALID_-20180114-115601.cpio.gz
Description: Binary data
Qubes-HCL-LENOVO-_INVALID_-20180114-115601.yml
Description: Binary data
On Sunday, 14 January 2018 03:07:09 GMT jerr...@disroot.org wrote:
> the template is whonix-ws
> when running command
> sudo qubes-dom0-update --action=reinstall qubes-template-package-name
This is quite broken in 4.0 and you have to be a bit clever to work around
this; here are some tips.
Den lørdag den 13. januar 2018 kl. 19.37.57 UTC+1 skrev Bertrand Lec:
> Hello,
>
> I'm fresh installing Qubes R3.2 on my desktop PC, aside from Ubuntu.
> The PC is configured with UEFI.
>
> The installation goes well. At that time, I can reboot directly to Qubes.
>
> However, after I update
Den søndag den 14. januar 2018 kl. 12.55.00 UTC+1 skrev awokd:
> On Sun, January 14, 2018 11:19 am, erikmunkander...@gmail.com wrote:
> > Den lørdag den 13. januar 2018 kl. 19.37.57 UTC+1 skrev Bertrand Lec:
>
> >> From my understanding, it says that Qubes is the first one to be booted
> >> but
On Sun, January 14, 2018 3:02 pm, jerr...@disroot.org wrote:
> can you somehow save the data? is it a corrupt file? when i put this file
> in the template folder in /var/lib/qubes, the data is not there.
Try to copy it into a VM, then do a loop mount on it. In Stretch it would be:
cd ~
mkdir mnt
On Sun, January 14, 2018 11:19 am, erikmunkander...@gmail.com wrote:
> Den lørdag den 13. januar 2018 kl. 19.37.57 UTC+1 skrev Bertrand Lec:
>> From my understanding, it says that Qubes is the first one to be booted
>> but the currently booted is ubuntu (which is true :) )
>>
>> Do you have any
Den søndag den 14. januar 2018 kl. 12.55.00 UTC+1 skrev awokd:
> On Sun, January 14, 2018 11:19 am, erikmunkander...@gmail.com wrote:
> > Den lørdag den 13. januar 2018 kl. 19.37.57 UTC+1 skrev Bertrand Lec:
>
> >> From my understanding, it says that Qubes is the first one to be booted
> >> but
can you somehow save the data? is it a corrupt file? when i put this file in
the template folder in /var/lib/qubes, the data is not there.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails
Managed to find what was causing the error and how to remove the error:
https://askubuntu.com/questions/778875/tpm-error-6-when-booting-thinkpad
https://bugzilla.redhat.com/show_bug.cgi?id=1413409
In my BIOS I went to Security -> Security Chip -> Security Chip set to "Active"
However this
Good point, I forgot this one. of course, it would, but I am not sure if Qubes
is ready for that.
But it could be useful to use 32-bit stubdoms for those reasons. They do rather
I/O-bound work (=> minimal performance penalty) and they don't need so much
memory to utilize more than 32-bit
Hello,
R3.2
I have installed yesterday and this morning AEM and sys-usb.
I had problem to make AEM working, but it seems now to work.
When booting I should have my two VMs "netVM and proxyVM" running ... Not the
case anymore.
My wifi device doesn't seems to be up as it was before (internal not
what about the cpu microcode? can a package be backported for it? or does that
have to be done through xen?
fedora 26 has some (theoretical?) protection against meltdown, maybe qubes-4
should update dom0 to that in the rc.
--
You received this message because you are subscribed to the Google
Having an issue with lenovo y520. I was getting the installer working and then
recieved an error- Errno 5 input/output error.
Then i tried again and when it starts to boot get "pane is dead" error.
Now im trying all the uefi config troubleshooting and all it gives me after
adding the /mapbs
On 01/14/2018 06:05 AM, 'Emil Novik' via qubes-users wrote:
Mostly works fine, but has some issues :
- Can't use any HVM(crashes the computer every time).
Have you applied awokd's patch?
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To
As far as I understand it, microcode update cannot fix it. It just brings some
new instructions that can be used for Spectre fix. (But they don't help on
their own.)
You can try to update your BIOS if it is well supported by your vendor. Mine is.
Alternatively, you can try to update microcode
I did, no idea why HVM still doesn't work.
---
Emil Novik
Original Message
On Jan 14, 2018, 19:48, taii...@gmx.com wrote:
> On 01/14/2018 06:05 AM, 'Emil Novik' via qubes-users wrote:
>
>> Mostly works fine, but has some issues :
>> - Can't use any HVM(crashes the computer
On Sunday, 14 January 2018 15:02:48 GMT jerr...@disroot.org wrote:
> can you somehow save the data? is it a corrupt file? when i put this file
> in the template folder in /var/lib/qubes, the data is not there.
'private.img' is the contens of /home and /rw
you may be looking for 'root.img' if you
Does anyone have direct knowledge of a USB to VGA or USB to HDMI adapter
that is known to work in Qubes?
I've installed Qubes 4.0-rc3 on my new Dell 7577 laptop (Nvidia Geforce
GTX). Everything seems good except I can not get another monitor to work
on the HDMI port (HCL forthcoming). I
Le dimanche 14 janvier 2018 14:36:06 UTC+1, erikmunk...@gmail.com a écrit :
> Den søndag den 14. januar 2018 kl. 12.55.00 UTC+1 skrev awokd:
> > On Sun, January 14, 2018 11:19 am, erikmunk...@gmail.com wrote:
> > > Den lørdag den 13. januar 2018 kl. 19.37.57 UTC+1 skrev Bertrand Lec:
> >
> > >>
Qubes refuses to install with graphical installer and I get the mssage that I
have to pass the inst.text option at boot. I tried it by appending
option=inst.text to the bootloader, but it still tries to do graphical install
and then anaconda surrounds itself and squeezes to death.
So how do
On Monday, January 15, 2018 at 12:20:48 AM UTC+7, Vít Šesták wrote:
> As far as I understand it, microcode update cannot fix it. It just brings
> some new instructions that can be used for Spectre fix. (But they don't help
> on their own.)
>
> You can try to update your BIOS if it is well
I have done in the same time an upgrade of the fedora-26 template ...
Le dimanche 14 janvier 2018 13:40:41 UTC+2, ThierryIT a écrit :
> Hello,
>
> R3.2
>
>
> I have installed yesterday and this morning AEM and sys-usb.
> I had problem to make AEM working, but it seems now to work.
> When
Great news, thank you!
--
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 does not have GPU virtualization for security reasons. As a result,
additional GPU is used only in dom0 (od GuiVM in future). GPU might be useful
for:
* additional output like HDMI (well, good luck…)
* window manager acceleration (but integrated GPU usually does the job well for
less
update: All type of VMs can run only if there is no selected devices.
Le dimanche 14 janvier 2018 13:40:41 UTC+2, ThierryIT a écrit :
> Hello,
>
> R3.2
>
>
> I have installed yesterday and this morning AEM and sys-usb.
> I had problem to make AEM working, but it seems now to work.
> When
25 matches
Mail list logo
