On Wednesday, 7 December 2016 14:34:55 UTC, Ronald Duncan wrote:
> HCL-ASUSTeK_COMPUTER_INC_-GL752VW-20161207-142440
>
> Needs nouveau.modeset=0 to run!!
>
>
> Looks like everything is working
>
> Ethernet
>
> Wifi
>
> usb
>
>
>
> Issues d
On Tuesday, 3 January 2017 21:33:47 UTC, Andrew David Wong wrote:
> On 2017-01-03 08:38, Ronald Duncan wrote:
> > Looking to reinstall qubes from scratch and would like to optimise
> > the use of the ssd so I execute as much as possible on the ssd and
> > use
Looking to reinstall qubes from scratch and would like to optimise the use of
the ssd so I execute as much as possible on the ssd and use the sata for
storage.
I have a 500gig ssd and 1 tb sata.
Thoughts appreciated
At the moment I installed qubes on the sata drive to test out and experiment o
This thread just sprung to life again.
I had a quick look at
https://www.qubes-os.org/doc/templates/
And along with Debian which is installed by default both
Arch and
Ubuntu
Are available...
My personal preference in Ubuntu because it generally just works, and Arch
because it has the latest
On Friday, 9 December 2016 11:43:04 UTC, Ronald Duncan wrote:
> Any update on
> https://github.com/QubesOS/qubes-issues/issues/1585
>
It looks like qubes-windows-tools breaks the ctl+alt+del and stops it going to
the VM along with any alternative.
I copied over the VM again, and havi
Any update on
https://github.com/QubesOS/qubes-issues/issues/1585
I could not get the work arounds to work.
Situation, could use sticky keys to get into vm and install qubes-windows-tools
Having installed qubes-tools sticky keys, onboard keyboard, and direct sending
of ctl+alt+del and ctl+alt+h
root.img >> becomes root-cow.img etc and the process was fine.
Was difficult to boot the windows image finally came up.
Then difficult to send ctl + alt + del (looks like this is broke in qubes)
Sticky keys worked.
Trying to get into safemode command prompt to turn off password.
--
You receive
On Wednesday, 7 December 2016 18:33:13 UTC, Ronald Duncan wrote:
> On Wednesday, 7 December 2016 16:21:19 UTC, Ronald Duncan wrote:
>
> > Where should I put the image file?
> /var/lib/qubes/vm-templates/win7-x64-template
> use
> qvm-create --hvm-template win7-x64-temp
On Wednesday, 7 December 2016 16:21:19 UTC, Ronald Duncan wrote:
> Where should I put the image file?
/var/lib/qubes/vm-templates/win7-x64-template
use
qvm-create --hvm-template win7-x64-template -l green
to create the template subdirectory
I just sshed the file in using my other ubu
It looks like qubes only supports win7 vm's. I have an old one that I ran
under kvm as a raw disk image.
Which looking at https://www.qubes-os.org/doc/hvm/ should work.
Normally I would just dd the image over an ssh pipe, and then reconfigure the
xml etc. I think I still have it as a raw part
HCL-ASUSTeK_COMPUTER_INC_-GL752VW-20161207-142440
Needs nouveau.modeset=0 to run!!
Looks like everything is working
Ethernet
Wifi
usb
Issues during install I tried putting usb in a vm, (checking this and
running under the net vm which hung the install.
Installing the default ticked vm's worked.
Looks like everything is working
Ethernet
Wifi
usb
Issues during install I tried putting usb in a vm, (checking this and running
under the net vm which hung the install.
Installing the default ticked vm's worked.
On installing from USB you need to do the following
just after installation - bef
On Wednesday, 7 December 2016 00:25:02 UTC, Marek Marczykowski-Górecki wrote:
> > Is there a way on the first boot after install prior to configuration to
> > set nouveau.modeset=0
>
> You can add it from grub menu. In UEFI mode (where grub is not used),
> just after installation - before reboo
On Tuesday, 6 December 2016 13:30:05 UTC, Ronald Duncan wrote:
> Looks like I will need to reinstall since things are not working/strange and
> I remember that when it first started up it did not go through the initial
> set up smoothly, and then would not boot.
>
> Probably
Looks like I will need to reinstall since things are not working/strange and I
remember that when it first started up it did not go through the initial set up
smoothly, and then would not boot.
Probably need to set up with nouveau.modeset=0 and then see the results:)
--
You received this messa
On Tuesday, 6 December 2016 13:11:41 UTC, Ronald Duncan wrote:
> Changing grub config to boot with nouveau.modeset=0 gave me a good
> repeatable boot.
>
> Now qubes is usable will investigate if everything else works:)
Thanks to Marek Marczykowski-Górecki
--
You received
Changing grub config to boot with nouveau.modeset=0 gave me a good repeatable
boot.
Now qubes is usable will investigate if everything else works:)
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receivi
On Sunday, 27 November 2016 21:21:01 UTC, Marek Marczykowski-Górecki wrote:
> -BEGIN PGP SIGNED MESSAGE-
> This assume you can boot your system. Does the hang happen all the time,
> or only sometimes? If the former, try disabling nouveau driver (which
> looks to be the problematic one), fo
On Tuesday, 22 November 2016 07:15:38 UTC, Me wrote:
> pierremartinf...@gmail.com:
> > Hi, I wonder if the Asus X205ta can handle Qubes ?
> > Thank,
> >
I find the latest ubuntu works well with most things. I have an ASUS ROC that
I got to run Qubes.
It has 32gb of RAM since I want to be able
Will this be using the latest linux kernel since grsecurity only provide the
latest version free.
--
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+uns
Added in the journalctl logs
The laptop works best with latest linux kernal
rjd@rjd-GL752VW:~$ uname -a
Linux rjd-GL752VW 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:03:13 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
What is best way of updating qubes to latest kernal and hypervisor.
--
You re
logs till crash
rjd@rjd-GL752VW:~$ journalctl -D
/media/rjd/5ce4e7fe-aa0d-42d1-97f0-5c9197677697/var/log/journal/219d2a92843f491aaf97807aa063449c
-- Logs begin at Fri 2016-11-18 19:08:26 GMT, end at Sun 2016-11-20 10:30:15 GMT
Nov 18 19:08:26 dom0 systemd-journal[216]: Runtime journal is using 8.0
Asus ROG GL752VW-GS71-HID6 using Inteli7 processor
Boot process
.
.
.
Starting Switch Boot
Error: Driver 'processor_agregator' is already registered, aborting
Error: Driver 'processor_agregator' is already registered, aborting
A start job is running for Qubes NetVM startup (2m 49s /no
On Friday, 18 November 2016 20:25:41 UTC, Ronald Duncan wrote:
> > reboot - hung at end of Q screen
> Starting Switch Boot
> Error: Driver 'processor_agregator' is already registered, aborting
> Error: Driver 'processor_agregator' is already regist
> reboot - hung at end of Q screen
Starting Switch Boot
Error: Driver 'processor_agregator' is already registered, aborting
Error: Driver 'processor_agregator' is already registered, aborting
A start job is running for Qubes NetVM startup (2m 49s /no limit NMI
watchdog:Bug soft locku
On Friday, 18 November 2016 19:44:09 UTC, Ronald Duncan wrote:
>
> Suggestions on how to turn off the Q screen and see what is happening behind
> the progress bar, and any logs that would be helpful.
Qubes start up Hit F10 for boot time diagnostics
--
You received this message be
26 matches
Mail list logo
