On Sat, March 3, 2018 3:54 pm, alternateg...@gmail.com wrote:
> Yeah. I appreciate your feedback. It took me a lot to finally post. I
> saw everything. I tried everything. Disabled hyperthreading etc. Every
> time I got to the configuration part it would crash at Setting up
> Network. I sear
And I actually know my way around a Linux command line, but the resources do
not exist to help users like me. I returned the Latitude.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails fr
Yeah. I appreciate your feedback. It took me a lot to finally post. I saw
everything. I tried everything. Disabled hyperthreading etc. Every time I
got to the configuration part it would crash at Setting up Network. I searched
every Linux forum. I tried repairing my install six or seven
On Fri, March 2, 2018 3:44 am, alternateg...@gmail.com wrote:
> I have the same issue, except Qubes fails to install on my Dell Latitude
> E6410. This was the second machine I was unable to install Qubes on, and
> this one I purchased specifically because I saw it on the Hardware
> Compatibility L
I have the same issue, except Qubes fails to install on my Dell Latitude E6410.
This was the second machine I was unable to install Qubes on, and this one I
purchased specifically because I saw it on the Hardware Compatibility List. My
system also presumably met the core requirements on site.
On Sunday, August 7, 2016 at 3:42:15 AM UTC-4, koto...@gmail.com wrote:
> I experience the same. It is slightly disturbing since this one of the first
> message appearing in the console with big red letters: FAILED. :)
I have same issue too on both my qubes machines. I've always just ignored it.
I experience the same. It is slightly disturbing since this one of the first
message appearing in the console with big red letters: FAILED. :)
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, Jul 02, 2016 at 10:12:02AM +0200, Alex wrote:
> It is harmless indeed, and I have a laptop with a simple Fedora 23 on it
> with the same error message on boot. Still I find it active (exited) in
> systemctl status, as in Qubes. It started to
On 07/01/2016 10:31 PM, Marek Marczykowski-Górecki wrote:
> On Fri, Jul 01, 2016 at 07:50:51PM +, amad...@riseup.net wrote:
>> On 2016-07-01 18:26, Marek Marczykowski-Górecki wrote:
>>> Anyway, probably harmless.
>>
>> I did fresh install and restored some templatevms and appvms from
>> R3.1.
On Fri, Jul 01, 2016 at 07:50:51PM +, amad...@riseup.net wrote:
> On 2016-07-01 18:26, Marek Marczykowski-Górecki wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > On Fri, Jul 01, 2016 at 08:13:32AM +, am wrote:
> > > During the boot process I get messages Failed to Lo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, Jul 01, 2016 at 08:13:32AM +, am wrote:
> During the boot process I get messages Failed to Load Kernel Modules.Is
> this sometyhing I should be concerned about? It does not appear to have
> affected the operation of Qubes in any way.
Did
During the boot process I get messages Failed to Load Kernel Modules.Is
this sometyhing I should be concerned about? It does not appear to have
affected the operation of Qubes in any way.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubsc
12 matches
Mail list logo
