Re: [qubes-users] Installed software in template not running in appvm - cryptomator
On Monday, 27 February 2017 16:26:42 UTC-5, steve.coleman wrote: > On 02/23/2017 09:08 PM, dumbcyber wrote: > > On Monday, 20 February 2017 17:11:09 UTC-5, steve.coleman wrote: > >> On 02/19/2017 05:41 PM, dumbcyber wrote: > >>> On Friday, 17 February 2017 19:43:45 UTC-5, Unman wrote: > >>>> On Fri, Feb 17, 2017 at 02:26:18AM -0800, dumbcyber wrote: > >>>>> I've installed Cryptomator in my Fedora-24 template vm and tested it - > >>>>> works fine. The install also installed some dependencies. > >>>>> > > >> > >> I installed Cryptomator, just being curious on how it works. > >> > >> Just my 2 cents, the instructions say to use the official java JRE, not > >> the more commonly installed OpenJVM version, and I can confirm that it > >> does run with Java(tm) and does not run with /usr/bin/java, so if I were > >> a betting man I would say to run it using the full path for the proper > >> location of your official jvm installation. You may have to edit your > >> *.desktop file to enforce this path to the proper java binary. Test it > >> from the Dom0 command line with the -p option as below. > >> > >> This works for me: > >> > >> InternetVM> /opt/bin/java -jar /path/to/Cryptomator-1.2.4.jar > >> > >> dom0> qvm-run InternetVM -p "/opt/bin/java -jar > >> /home/user/Cryptomator/Cryptomator-1.2.4.jar" > >> > >> > >> Hope that helps > >> > >> Steve > > > > Thanks Steve. > > > > I only have Java installed in /usr/bin/java and Cryptomator starts fine > > from the menu in the templatevm. I can also start it fine from the command > > line in the appvm. The issue is the appvm menu shortcut does not work. > > > > Ok, here is my latest, more complete test. Before I was only playing > with it in a DispVM. > > dom0> find . -iname \*Cryptomator\*.desktop -exec grep -Hi Exec= \; > > ./.local/share/applications/Internet-Cryptomator.desktop:Exec=qvm-run -q > --tray -a Internet -- 'qubes-desktop-run > /usr/share/applications/Cryptomator.desktop' > > # Now, add the "-p" option to the above qvm-run statement on the dom0 > command line: > > dom0> qvm-run -p -q --tray -a Internet -- 'qubes-desktop-run > /usr/share/applications/Cryptomator.desktop' > > Traceback (most recent call last): >File "/usr/bin/qubes-desktop-run", line 7, in > launch(*sys.argv[1:]) >File "/usr/lib64/python2.7/site-packages/qubes/xdg.py", line 8, in launch > launcher = Gio.DesktopAppInfo.new_from_filename(desktop) > TypeError: constructor returned NULL > > > Do you get the same error here? > > # lets see what was running on the VM side: > > dom0> qvm-run -p -a Internet 'grep Exec > /usr/share/applications/Cryptomator.desktop' > > Exec=/opt/Cryptomator/Cryptomator > > This is wrong! it should be the full path to the java binary, -jar, and > then the full jarfile path. Instead the desktop file in the VM was > changed/mundged/hacked to try and execute the "directory" named > /opt/Cryptomator/Cryptomator where the app stored its keys!! I can't > even put a script there by that name because its a directory that was > originally created by the Cryptomator application itself. > > > Solution? I might find a way to move its key srorage. But, its easier > creating a script /opt/bin/Cryptomator and pointing my template > *.desktop Exec to that script. We will see how that works. > > Bingo! > > fedora-24$ grep Exec= /usr/share/applications/Cryptomator.desktop > Exec=/opt/bin/Cryptomator > > Internet$ cat /opt/bin/Cryptomator > #!/bin/bash > /opt/bin/java -jar /opt/Cryptomator/Cryptomator-1.2.4.jar > > > Works from both dom0 command line and from the menu now! > > Hope that helps. > > > Steve. Thanks Steve. I appreciate the time you are putting into this. I'll give this a go when I get time to play around. Thanks again. -- 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-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/29fba256-bef2-4081-b562-5032b116c2b9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Installed software in template not running in appvm - cryptomator
On Monday, 20 February 2017 17:11:09 UTC-5, steve.coleman wrote: > On 02/19/2017 05:41 PM, dumbcyber wrote: > > On Friday, 17 February 2017 19:43:45 UTC-5, Unman wrote: > >> On Fri, Feb 17, 2017 at 02:26:18AM -0800, dumbcyber wrote: > >>> I've installed Cryptomator in my Fedora-24 template vm and tested it - > >>> works fine. The install also installed some dependencies. > >>> > >>> When I try to run the software in any Fedora-24 appvm's I get nothing. No > >>> errors, no GUI starting. > >>> > >>> Any ideas where i can look for errors? Thanks. > >>> > >> > >> You don't say how you are starting the program. > >> > >> I assume that you have an entry for Cryptomator in the menu list for the > >> appVM. (Check this!) If you haven't use the "Add more shortcuts" entry , > >> and try to use the new entry. > >> > >> It works for me - did you make sure that you restarted the appVM after > >> closing down the Template? > >> > >> certainly if I use the desktop file from the menu then it works, but > >> trying to start at command line throws errors.(I mean just running > >> /opt/Cryptomator/Cryptomator.)But after the first time it seems to work > >> fine. > > > > Thanks for the tips. > > > > I'm trying to start the app from the menu shortcut in the appvm. Yes, I've > > restarted the appvm and templatevm after installing the software in the > > template. > > > > The /home folder looks exactly the same in both the templatevm and appvm. > > > > When I try to start the app from the command line in the appvm, I get these > > messages but Cryptomator does start > > > > [user@work Cryptomator]$ /opt/Cryptomator/Cryptomator > > 2017-02-19 17:22:59,275 INFO [Cryptomator:39] Starting Cryptomator 1.2.3 > > on Linux 4.4.38-11.pvops.qubes.x86_64 (amd64) > > 2017-02-19 17:22:59,292 INFO [SingleInstanceManager:300] no running > > instance found > > 2017-02-19 17:22:59,498 INFO [MainApplication:45] JavaFX application > > started > > 2017-02-19 17:22:59,554 INFO [Localization:44] Detected language "en" and > > region "US" > > 2017-02-19 17:22:59,557 INFO [Localization:49] Attempting to load > > localization from: /localization/en_US.txt > > 2017-02-19 17:22:59,558 INFO [Localization:54] Attempting to load > > localization from: /localization/en.txt > > 2017-02-19 17:22:59,675 INFO [SettingsProvider:88] Failed to load > > settings, creating new one. > > > > I installed Cryptomator, just being curious on how it works. > > Just my 2 cents, the instructions say to use the official java JRE, not > the more commonly installed OpenJVM version, and I can confirm that it > does run with Java(tm) and does not run with /usr/bin/java, so if I were > a betting man I would say to run it using the full path for the proper > location of your official jvm installation. You may have to edit your > *.desktop file to enforce this path to the proper java binary. Test it > from the Dom0 command line with the -p option as below. > > This works for me: > > InternetVM> /opt/bin/java -jar /path/to/Cryptomator-1.2.4.jar > > dom0> qvm-run InternetVM -p "/opt/bin/java -jar > /home/user/Cryptomator/Cryptomator-1.2.4.jar" > > > Hope that helps > > Steve Thanks Steve. I only have Java installed in /usr/bin/java and Cryptomator starts fine from the menu in the templatevm. I can also start it fine from the command line in the appvm. The issue is the appvm menu shortcut does not work. -- 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-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/fb677a47-d0cf-4973-be9f-1dbbd07ec4e7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Installed software in template not running in appvm - cryptomator
On Friday, 17 February 2017 19:43:45 UTC-5, Unman wrote: > On Fri, Feb 17, 2017 at 02:26:18AM -0800, dumbcyber wrote: > > I've installed Cryptomator in my Fedora-24 template vm and tested it - > > works fine. The install also installed some dependencies. > > > > When I try to run the software in any Fedora-24 appvm's I get nothing. No > > errors, no GUI starting. > > > > Any ideas where i can look for errors? Thanks. > > > > You don't say how you are starting the program. > > I assume that you have an entry for Cryptomator in the menu list for the > appVM. (Check this!) If you haven't use the "Add more shortcuts" entry , > and try to use the new entry. > > It works for me - did you make sure that you restarted the appVM after > closing down the Template? > > certainly if I use the desktop file from the menu then it works, but > trying to start at command line throws errors.(I mean just running > /opt/Cryptomator/Cryptomator.)But after the first time it seems to work > fine. Thanks for the tips. I'm trying to start the app from the menu shortcut in the appvm. Yes, I've restarted the appvm and templatevm after installing the software in the template. The /home folder looks exactly the same in both the templatevm and appvm. When I try to start the app from the command line in the appvm, I get these messages but Cryptomator does start [user@work Cryptomator]$ /opt/Cryptomator/Cryptomator 2017-02-19 17:22:59,275 INFO [Cryptomator:39] Starting Cryptomator 1.2.3 on Linux 4.4.38-11.pvops.qubes.x86_64 (amd64) 2017-02-19 17:22:59,292 INFO [SingleInstanceManager:300] no running instance found 2017-02-19 17:22:59,498 INFO [MainApplication:45] JavaFX application started 2017-02-19 17:22:59,554 INFO [Localization:44] Detected language "en" and region "US" 2017-02-19 17:22:59,557 INFO [Localization:49] Attempting to load localization from: /localization/en_US.txt 2017-02-19 17:22:59,558 INFO [Localization:54] Attempting to load localization from: /localization/en.txt 2017-02-19 17:22:59,675 INFO [SettingsProvider:88] Failed to load settings, creating new one. -- 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-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5722b159-51bb-41a2-9c94-a0472ea3e997%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Installed software in template not running in appvm - cryptomator
I've installed Cryptomator in my Fedora-24 template vm and tested it - works fine. The install also installed some dependencies. When I try to run the software in any Fedora-24 appvm's I get nothing. No errors, no GUI starting. Any ideas where i can look for errors? Thanks. -- 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-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/9e0d0611-1a0f-4822-ad17-c4bb94b40f30%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Expand the size of /dev/mapper/qubes_dom000-root - out of space
On Monday, 9 January 2017 08:38:12 UTC-5, Unman wrote: > On Mon, Jan 09, 2017 at 01:12:38PM +0100, Alex wrote: > > On 01/09/2017 01:03 PM, Bernhard wrote: > > > Hello, I am not expert, but often such differences are explained by > > > the following calculation: 1 KB is 2^10 = 1024 bytes and not 1000. > > > While this difference is little, in third power it becomes big: 2^30 > > > * 53= 56,908,316,672 so *real* 53 GiB are approx 60 * 10^6 bytes > > > which sometimes are called GB al well ... Bernhard > > > > > > On 01/09/2017 12:02 PM, dumbcyber wrote: > > >> I built Qubes on a 64Gb USB stick. I then successfully cloned the > > >> stick to an external SSD drive using Clonezilla. The SSD drive is > > >> 500Gb in total size. > > >> > > >> As a result my /dev/mapper/qubes_dom000-root on the SSD is only > > >> 53Gb in total size according to "df -h" in dom0. > > >> > > >> I used gparted on another linux machine to extend the size of this > > >> partition (qubes_dom000) to the full size available. Gparted then > > >> shows 57Gb used and 360Gb free. > > >> > > >> I boot off the SSD into Qubes and run "df -h" again but it still > > >> shows only 53G total size. > > >> > > >> Is there a "right" way to extend the size of > > >> /dev/mapper/qubes_dom000-root, if in fact its at all possible? > > >> > > >> Thanks in advance. > > >> > > > > > The problem here is not the rounding (yes, usb pen drives are usually > > measured with the SI interpretation of the multiplication prefixes) but > > the enlargement of the filesystem. > > > > dumbcyber wrote that he correctly adjusted the partition size, but > > that's not enough; the filesystem on it has to be resized as well. > > > > I'm not an expert with lvm either, but online guides can be found on > > resizing LVM volumes and filesystems... > > > > -- > > Alex > > > > Assuming that the LV has been succesfully resized then resize2fs is what > you need. Thanks, ran this from dom0 and worked fine. -- 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-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/cfeaf6e0-bfb8-4c9a-be4f-ce22a87e45d3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Expand the size of /dev/mapper/qubes_dom000-root - out of space
I built Qubes on a 64Gb USB stick. I then successfully cloned the stick to an external SSD drive using Clonezilla. The SSD drive is 500Gb in total size. As a result my /dev/mapper/qubes_dom000-root on the SSD is only 53Gb in total size according to "df -h" in dom0. I used gparted on another linux machine to extend the size of this partition (qubes_dom000) to the full size available. Gparted then shows 57Gb used and 360Gb free. I boot off the SSD into Qubes and run "df -h" again but it still shows only 53G total size. Is there a "right" way to extend the size of /dev/mapper/qubes_dom000-root, if in fact its at all possible? Thanks in advance. -- 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-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ef1a9b6f-c180-42b8-b69e-223d55040526%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Install windows 7 in HVM template on HP Zbook 15
On Tuesday, 27 December 2016 23:03:31 UTC+11, Ines WALLON wrote: > Hello everybody, > > I try to install Windows 7 in HVM template and my VM displays > "Starting Windows" and freeze. > > Windows 10 fully functional in HVM template but not qubes driver > > > > > best regard > > -- > Ines WALLON Sorry can't find the link but for some people there is a tip to change a driver setting from xen to cirrus to get past the glowing logo. -- 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-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6b6eb481-94fa-4bee-a72d-ef0870acbe3e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Clone qubes machine - any options other than backup and build again?
On Sunday, 18 December 2016 17:18:17 UTC+11, dumbcyber wrote: > On Thursday, 15 December 2016 01:07:12 UTC+11, Andrew David Wong wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA512 > > > > On 2016-12-14 03:19, dumbcyber wrote: > > > Hello, I am running Qubes from a 64Gb USB stick. > > > > > > I am running R3.2 on my Macbook 11,1, and have built several > > > template VMs, for example Windows. > > > > > > What I want to do now is clone the entire USB stick to another USB > > > external SSD drive. In other words I want to be able to stop using > > > the USB stick and move to the SSD drive without building Qubes from > > > again scratch and then performing backup/restore all my VMs. > > > > > > Is this even possible? Am i dreaming? > > > > > > Thanks in advance. > > > > > > > I reckon there's nothing to lose by trying, as long as you keep the > > original USB stick. You can try with dd or any program that makes a > > bitwise identical image from the USB stick and faithfully writes it > > onto the SDD drive. > > > > - -- > > Andrew David Wong (Axon) > > Community Manager, Qubes OS > > https://www.qubes-os.org > > -BEGIN PGP SIGNATURE- > > > > iQIcBAEBCgAGBQJYUVIDAAoJENtN07w5UDAwzAwP/0w1+2cu9qFizHAVfApng01g > > SPwqL9Gt+lNdYRoUUjSIsBHe2bpY1DDllpiZnTVc1EmK6daq9XjSMs1dVlceUNeV > > 01uJ2mN68vY6PqZZ0DrREdmK3EteFRo/761qwr+gvQ1A7BqT3gJZjIACauizQ1EC > > Jlk0Mr5BO34j9b3zj4bv43M+7fM2tL1kB0i1ISELCeiRF8IHcqd3IQMwF8GD7OfC > > iCAXiVj+pBbp7FojUhqrzHYmBj6YK35MmX6BAzwc6L/Zh3XcQsGuBy2SzPPmodgM > > kWJ6uRsKCY7k7hCM3nauDfrIeweOr0d4vhOUivx7CjdayCh/W1Z47A1hbId7E+i7 > > RqSqx/l3ZgEWkgnj5XOM/Pv3CrKIRnBr55fe5EDpgFeAasluGd4XFWHhx/Sx73mt > > iqVsk7KzBvvWL7AjThBWLqbwfk2FU0ajE0DJw3/XsGyJxscap8BXiGCPkTi4NaRd > > Z4Iy/VJ6RRVTSBbqZ87B28qZmZ/dYYJX7Rll//5OZcEI2XzSGopE882rdmaYG62v > > M6fQgpjsBh1QMC36Fe0nlFAN1FPoe2Aneg73wziA1+XKoZRo7iK/rQSb+vL3h9vq > > 2vZfBDbYkplWonJ6LhukGK4LozpuuaL2AK1Q4xhF8b/LZZII7/MWvkhHUDCMAY6t > > nDiTseM0toT5Gp48rPJw > > =GoBG > > -END PGP SIGNATURE- > > Quick update: On a Kali Linux machine, I managed to format and partition the > destination disk as per the Qubes USB stick. I've used DD command to copy the > contents of the two partitions. I get a success message at the end. > > When I boot I get the option to boot from this new disk but nothing else > happens. I've noticed using fdisk and gparted on linux that while the DD > command is successful the second partition is actually empty. The first > partition is fine - looks exactly like the source disk. > > Any ideas appreciated. Just in case this helps anyone else: I managed to do this successfully with Clonezilla. Used the advanced options where I unchecked "reinstall grub". -- 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-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ca649c7b-235d-4931-9a88-8584ef3fb762%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Macbook Pro USB keyboard
I'm very sorry to revive this thread. I've been trying to build another Qubes environment on an SSD drive and have run into the same problem. I'm building R3.2 for a Macbook Pro. I know Macbook's are not very well supported but I've had my original Qubes environment running really well now for some time on the Macbook Pro and want to move away from the USB stick to something more long term. I've built a new Qubes on an SSD which boots fine on the Macbook Pro but the keyboard does not work. I've completed the installation making sure the sys-usb option is not checked, and there is no rd.qubes.hide_all_usb parameter on any kernel lines in xen.cfg. The same SSD boots and keyboard works fine on a Lenovo X1 (if I add the mapbs and noexitboot params). Any help is much appreciated again! -- 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-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4238c592-6744-41a2-8365-c5cd4db351e4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: One step foerward, two steps back on Macbook 11,1 - can't boot into Qubes
On Wednesday, 16 November 2016 22:52:16 UTC+11, dumbcyber wrote: > On Wednesday, 16 November 2016 11:33:03 UTC+11, dumbcyber wrote: > > On Tuesday, 15 November 2016 18:14:00 UTC+11, Jean-Philippe Ouellet wrote: > > > On Tue, Nov 15, 2016 at 12:17 AM, dumbcyber <> wrote: > > > > On Tuesday, 15 November 2016 10:28:52 UTC+11, Marek > > > > Marczykowski-Górecki wrote: > > > >> you need to remove 'rd.qubes.hide_all_usb' from kernel parameters. > > > > > > > > Thanks for the info. For me a noob, how do I remove that parameter from > > > > kernel? Thank you. > > > > > > From the installer, use your favorite editor on > > > /boot/efi/EFI/qubes/xen.cfg to remove just the rd.qubes.hide_all_usb > > > parameter from the kernel= line. It will probably be at the end of the > > > line. > > > > > > Note that your EFI partition might be mounted somewhere other than > > > /boot/efi (I don't remember). The `mount` command should tell you > > > where. Look for something like: > > > /dev/nvme0n1p1 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=... > > > > Thanks for the guide. My boot64x.cfg does not contain this parameter. Here > > is the full CFG file > > > > [global] > > default=4.4.14-11.pvops.qubes.x86_64 > > > > [4.4.14-11.pvops.qubes.x86_64] > > options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M > > kernel=vmlinuz-4.4.14-11.pvops.qubes.x86_64 > > root=/dev/mapper/qubes_dom0-root > > rd.luks.uuid=luks-9b163fd2-93d9-4498-a83d-712baae8432e > > rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap > > i915.preliminary_hw_support=1 rhgb quiet > > ramdisk=initramfs-4.4.14-11.pvops.qubes.x86_64.img > > > > [4.4.14-11.pvops.qubes.x86_64] > > options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M > > kernel=vmlinuz-4.4.14-11.pvops.qubes.x86_64 > > root=/dev/mapper/qubes_dom0-root > > rd.luks.uuid=luks-9b163fd2-93d9-4498-a83d-712baae8432e > > rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap > > i915.preliminary_hw_support=1 rhgb quiet > > ramdisk=initramfs-4.4.14-11.pvops.qubes.x86_64.img > > > > > > Thanks for your help. > > PS I'm building another Qubes install where I'll uncheck "use sys-usb" > > later today > > Finally its working. I rebuilt everything from the beginning making sure > sys-usb was unchecked during installation. Qubes boots on the Mac fine - > little slow but gets there in the end. I can log, keyboard works. Now the > next challenge, getting it networked but thats not for this post. Thanks for > your help everyone. Sorry to revive this thread, but I've been building another Qubes installation for someone else. I've run into the same problem - the Macbook Pro keyboard is not responsive. I've tried many times during installation to get to the screen where I can select/deselect the sys-usb option but do not get it at all! I've already checked if rd.qubes.hide_all_usb is present and its not! I'm an idiot for not writing it down the first time. -- 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-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5535afcd-03d8-4592-b379-4bf186ddbaef%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Clone qubes machine - any options other than backup and build again?
On Thursday, 15 December 2016 01:07:12 UTC+11, Andrew David Wong wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 2016-12-14 03:19, dumbcyber wrote: > > Hello, I am running Qubes from a 64Gb USB stick. > > > > I am running R3.2 on my Macbook 11,1, and have built several > > template VMs, for example Windows. > > > > What I want to do now is clone the entire USB stick to another USB > > external SSD drive. In other words I want to be able to stop using > > the USB stick and move to the SSD drive without building Qubes from > > again scratch and then performing backup/restore all my VMs. > > > > Is this even possible? Am i dreaming? > > > > Thanks in advance. > > > > I reckon there's nothing to lose by trying, as long as you keep the > original USB stick. You can try with dd or any program that makes a > bitwise identical image from the USB stick and faithfully writes it > onto the SDD drive. > > - -- > Andrew David Wong (Axon) > Community Manager, Qubes OS > https://www.qubes-os.org > -BEGIN PGP SIGNATURE- > > iQIcBAEBCgAGBQJYUVIDAAoJENtN07w5UDAwzAwP/0w1+2cu9qFizHAVfApng01g > SPwqL9Gt+lNdYRoUUjSIsBHe2bpY1DDllpiZnTVc1EmK6daq9XjSMs1dVlceUNeV > 01uJ2mN68vY6PqZZ0DrREdmK3EteFRo/761qwr+gvQ1A7BqT3gJZjIACauizQ1EC > Jlk0Mr5BO34j9b3zj4bv43M+7fM2tL1kB0i1ISELCeiRF8IHcqd3IQMwF8GD7OfC > iCAXiVj+pBbp7FojUhqrzHYmBj6YK35MmX6BAzwc6L/Zh3XcQsGuBy2SzPPmodgM > kWJ6uRsKCY7k7hCM3nauDfrIeweOr0d4vhOUivx7CjdayCh/W1Z47A1hbId7E+i7 > RqSqx/l3ZgEWkgnj5XOM/Pv3CrKIRnBr55fe5EDpgFeAasluGd4XFWHhx/Sx73mt > iqVsk7KzBvvWL7AjThBWLqbwfk2FU0ajE0DJw3/XsGyJxscap8BXiGCPkTi4NaRd > Z4Iy/VJ6RRVTSBbqZ87B28qZmZ/dYYJX7Rll//5OZcEI2XzSGopE882rdmaYG62v > M6fQgpjsBh1QMC36Fe0nlFAN1FPoe2Aneg73wziA1+XKoZRo7iK/rQSb+vL3h9vq > 2vZfBDbYkplWonJ6LhukGK4LozpuuaL2AK1Q4xhF8b/LZZII7/MWvkhHUDCMAY6t > nDiTseM0toT5Gp48rPJw > =GoBG > -END PGP SIGNATURE- Quick update: On a Kali Linux machine, I managed to format and partition the destination disk as per the Qubes USB stick. I've used DD command to copy the contents of the two partitions. I get a success message at the end. When I boot I get the option to boot from this new disk but nothing else happens. I've noticed using fdisk and gparted on linux that while the DD command is successful the second partition is actually empty. The first partition is fine - looks exactly like the source disk. Any ideas appreciated. -- 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-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/fe8712a9-14d7-4a4a-bce9-aabe269d2d62%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes 3.2 Install hangs in GRUB on Mac OS X 10.10 - USB Install
On Saturday, 17 December 2016 07:09:50 UTC+11, Sam Johnson wrote: > I have installed Qubes 3.2 on a USB flash drive as follows: > > sudo dd if=Qubes-R3.2-x86_64.iso of=/dev/rdisk2 bs=1m > > When rebooting I hold down Alt and enter the Qubes installation menu. Any > selected option starts processing but quickly ends and returns me to the > menu; no installation is made. > > This page seems to be relevant: > https://www.qubes-os.org/doc/uefi-troubleshooting/ > > But I have no way of actually using vi to edit the file mentioned in the > section of 3.2 > > (I did find an article with a work around to Ctrl-x not working on some > systems: bugzilla.redhat.com/show_bug.cgi?id=1253637 ) > > > Suggestions with any step of this process are welcome and appreciated. > > > > > > > Sent with ProtonMail Secure Email. I run Qubes R3.2 on a Macbook Pro 11,1 but had to run the installer on another machine. I used a Lenovo to boot into Qubes and complete the installation. The resulting disk works fine on the MacBook. Some people have had success creating a EFI folder on the disk and copying the necessary file manually. -- 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-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/417579ef-bd47-4dfd-a7bf-e6fd14c215e0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Installing on macOS Macbook
On Friday, 16 December 2016 01:09:30 UTC+11, pixel fairy wrote: > On Wednesday, December 14, 2016 at 3:38:24 AM UTC-8, dumbcyber wrote: > > > I am reading and responding to this thread on a Macbook Pro 11,1 running > > Qubes R3.2. Andrew and others are right: yes it works, but you need to > > work hard to make it work. I had the keyboard not working issue and in fact > > i had to build my Qubes disk on a Lenovo to get past the install issues the > > Macbook was giving me. > > > > i had the same problem on my 11,3. how did you get it working? On the Macbook I could not get past the initial installation menu (four choices) which kept failing regardless of which option I chose. So I build the Qubes disk on a Lenovo desktop. The same disk boots fine and works fine on the Macbook Pro. -- 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-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f6f29b33-1ab1-48f8-84a8-bbd6df9c0647%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Installing on macOS Macbook
On Wednesday, 7 December 2016 09:31:36 UTC-5, Chibi wrote: > I tried to install QubesOS in Virtualbox on my Macbook and get the following > error: > http://imgur.com/a/dx9oM > I can't fix it somehow. Is there any way to fix it? I am reading and responding to this thread on a Macbook Pro 11,1 running Qubes R3.2. Andrew and others are right: yes it works, but you need to work hard to make it work. I had the keyboard not working issue and in fact i had to build my Qubes disk on a Lenovo to get past the install issues the Macbook was giving me. Re Virtualbox, I don't think either VB or Qubes are designing to work in the way you are trying. -- 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-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/618c40bf-4fff-43b2-a0bf-6f250bcc245c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: I recently installed Qubes and I now have several problems
On Tuesday, 13 December 2016 21:29:28 UTC-5, explodingbee . wrote: > Hi folks, > > I installed qubes several days ago. I now have several problems and I would > appreciate some help: > > 1) How can I open WIndows 7 again? First, I intended to install Qubes beside > Windows 7, which was working fine. Instead I can only boot to Qubes now. > How can I have a dual-boot setup so that I can also go to Windows 7? (Note: > my files from Windows 7 were apparently not damaged and I have recently > managed to get apparently all of them off of the computer and onto an > external hard drive so they should be safe.) (I did read this file > [https://www.qubes-os.org/doc/multiboot/] but it seems to say that one needs > to wipe out everything and reinstall Windows 7 and then reinstall Qubes. > Can't I fix the GRUB file somehow so that I can use my existing installations > and programs?) > > 2) In Qubes the computer often gets slow as molasses. I get error messages > saying "Warning: unresponsive script" sometimes. When I try to open a VM it > says that there is not enough memory and that I should close a VM first. > When the computer gets like this sometimes I click on things and nothing > happens or it takes forever for something to happen; sometimes I can't even > close windows because they don't respond. (I am using an HP Elitebook 8540w > laptop. It has 4 GB of RAM and an i7 CPU.) Also, when I shut down the > computer sometimes it gets stuck and does not shut down all the way. It > freezes with the Qubes splash screen there and the progress bar indicating > partial or complete progress. > > > 3) Problem relating to program installation: When I install programs in the > Fedora or Debian templates they don't appear in the list of available > programs in the templates or in the VMs based on those templates so I don't > see how I can create shortcuts for programs in my VMs. > > > 4) Problem in getting a video player to work: I have installed four > different video players (Snappy, Budgie, Banshee and Parole) and none of them > seem to be able to play videos I have downloaded (with Video Download Helper > and Firefox in an App VM). (I can get the video players to launch not with > the proper shortcuts but in another, awkward way, by going to Domain: > personal -> personal: Software and then clicking around until I get to the > right app which was previously installed and then clicking on "launch.") > Also, the default player, apparently called "Videos," doesn't work. Am I > missing something here? > > > > This paragraph shows the problems which arise when I try to use each of the > above mentioned video players. You may (or may not) want to skip this > paragraph. (I am including these video player error descriptions partly > because they may give a clue as to an overall problem here.) > (a) Snappy: The video player shows that a video has loaded but then when > I click play it does nothing. > (b) Parole: When I try to play a video I get the following error > message: "Error GStreamer backend error Could not intialize Xv output." > The only button to click on the error message dialogue box says: "Close." > (c) Banshee: This video player doesn't play videos when I click play. > It sometimes causes an error message which reads: "Additional multimedia > codecs requires. An application is requesting additional multimedia codecs." > Then there is a button which reads "find in software." (Other times when I > click play after selecting a video the video player just does nothing.) > (d) Budgie: This videos player does nothing when I click play after a > video which has been loaded into the program is selected. > (e) Videos: (Apparently this video player is called "Videos." It is > the default player.) When I select a video and then select "Play with > Videos" an error message comes up. It says: "H.264 (Constrained Baseline > Profile) decoder, MPEG-4 AAC decoder are required to play the file, but are > not installed." Then there is a button which says "Find in software." When > I click that button I get another error message which says "Unfortunately, > the H.264 (Constrained Baseline Profile) decoder and MPEG-4 AAC decoder you > were searching for could not be found. Please see this website for more > information." > > > 5) I can't update Fedora: I have tried to update Fedora 23 to Fedora 25. I > am able to download the update but then I click "Install" and nothing > happens. I also click "restart and install" just below that and again > nothing happens. What is going on with that? (I just tried that again and I > got the following error message this time: "Sorry this did not work Upgrade > to Fedora failed. Details Detailed errors from the package manager > follow: Error running transaction: installing package > filesystem-3.2-37.fc24.x86_64 needs 135168 on the /rw filesystem") >
[qubes-users] Clone qubes machine - any options other than backup and build again?
Hello, I am running Qubes from a 64Gb USB stick. I am running R3.2 on my Macbook 11,1, and have built several template VMs, for example Windows. What I want to do now is clone the entire USB stick to another USB external SSD drive. In other words I want to be able to stop using the USB stick and move to the SSD drive without building Qubes from again scratch and then performing backup/restore all my VMs. Is this even possible? Am i dreaming? Thanks in advance. -- 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-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/96c75461-a5b7-4318-973b-03e47d6bbbfd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: One step foerward, two steps back on Macbook 11,1 - can't boot into Qubes
On Wednesday, 16 November 2016 11:33:03 UTC+11, dumbcyber wrote: > On Tuesday, 15 November 2016 18:14:00 UTC+11, Jean-Philippe Ouellet wrote: > > On Tue, Nov 15, 2016 at 12:17 AM, dumbcyber <> wrote: > > > On Tuesday, 15 November 2016 10:28:52 UTC+11, Marek Marczykowski-Górecki > > > wrote: > > >> you need to remove 'rd.qubes.hide_all_usb' from kernel parameters. > > > > > > Thanks for the info. For me a noob, how do I remove that parameter from > > > kernel? Thank you. > > > > From the installer, use your favorite editor on > > /boot/efi/EFI/qubes/xen.cfg to remove just the rd.qubes.hide_all_usb > > parameter from the kernel= line. It will probably be at the end of the > > line. > > > > Note that your EFI partition might be mounted somewhere other than > > /boot/efi (I don't remember). The `mount` command should tell you > > where. Look for something like: > > /dev/nvme0n1p1 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=... > > Thanks for the guide. My boot64x.cfg does not contain this parameter. Here > is the full CFG file > > [global] > default=4.4.14-11.pvops.qubes.x86_64 > > [4.4.14-11.pvops.qubes.x86_64] > options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M > kernel=vmlinuz-4.4.14-11.pvops.qubes.x86_64 root=/dev/mapper/qubes_dom0-root > rd.luks.uuid=luks-9b163fd2-93d9-4498-a83d-712baae8432e > rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap > i915.preliminary_hw_support=1 rhgb quiet > ramdisk=initramfs-4.4.14-11.pvops.qubes.x86_64.img > > [4.4.14-11.pvops.qubes.x86_64] > options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M > kernel=vmlinuz-4.4.14-11.pvops.qubes.x86_64 root=/dev/mapper/qubes_dom0-root > rd.luks.uuid=luks-9b163fd2-93d9-4498-a83d-712baae8432e > rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap > i915.preliminary_hw_support=1 rhgb quiet > ramdisk=initramfs-4.4.14-11.pvops.qubes.x86_64.img > > > Thanks for your help. > PS I'm building another Qubes install where I'll uncheck "use sys-usb" later > today Finally its working. I rebuilt everything from the beginning making sure sys-usb was unchecked during installation. Qubes boots on the Mac fine - little slow but gets there in the end. I can log, keyboard works. Now the next challenge, getting it networked but thats not for this post. Thanks for your help everyone. -- 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-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ef15c989-5e90-4dcb-a689-fbd46a8423d4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: One step foerward, two steps back on Macbook 11,1 - can't boot into Qubes
On Tuesday, 15 November 2016 18:14:00 UTC+11, Jean-Philippe Ouellet wrote: > On Tue, Nov 15, 2016 at 12:17 AM, dumbcyber <> wrote: > > On Tuesday, 15 November 2016 10:28:52 UTC+11, Marek Marczykowski-Górecki > > wrote: > >> you need to remove 'rd.qubes.hide_all_usb' from kernel parameters. > > > > Thanks for the info. For me a noob, how do I remove that parameter from > > kernel? Thank you. > > From the installer, use your favorite editor on > /boot/efi/EFI/qubes/xen.cfg to remove just the rd.qubes.hide_all_usb > parameter from the kernel= line. It will probably be at the end of the > line. > > Note that your EFI partition might be mounted somewhere other than > /boot/efi (I don't remember). The `mount` command should tell you > where. Look for something like: > /dev/nvme0n1p1 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=... Thanks for the guide. My boot64x.cfg does not contain this parameter. Here is the full CFG file [global] default=4.4.14-11.pvops.qubes.x86_64 [4.4.14-11.pvops.qubes.x86_64] options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M kernel=vmlinuz-4.4.14-11.pvops.qubes.x86_64 root=/dev/mapper/qubes_dom0-root rd.luks.uuid=luks-9b163fd2-93d9-4498-a83d-712baae8432e rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap i915.preliminary_hw_support=1 rhgb quiet ramdisk=initramfs-4.4.14-11.pvops.qubes.x86_64.img [4.4.14-11.pvops.qubes.x86_64] options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M kernel=vmlinuz-4.4.14-11.pvops.qubes.x86_64 root=/dev/mapper/qubes_dom0-root rd.luks.uuid=luks-9b163fd2-93d9-4498-a83d-712baae8432e rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap i915.preliminary_hw_support=1 rhgb quiet ramdisk=initramfs-4.4.14-11.pvops.qubes.x86_64.img Thanks for your help. PS I'm building another Qubes install where I'll uncheck "use sys-usb" later today -- 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-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4ef9850e-d1aa-4aef-98ff-a9a2267c736c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: One step foerward, two steps back on Macbook 11,1 - can't boot into Qubes
On Tuesday, 15 November 2016 10:28:52 UTC+11, Marek Marczykowski-Górecki wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Mon, Nov 14, 2016 at 02:33:50PM -0800, dumbcyber wrote: > > On Tuesday, 15 November 2016 09:02:56 UTC+11, dumbcyber wrote: > > > On Tuesday, 15 November 2016 08:47:30 UTC+11, dumbcyber wrote: > > > > From the beginning I have to ask for forgiveness - I am new to Qubes > > > > and have no knowledge of changing boot managers beyond trial and error. > > > > > > > > My hardware is a Macbook 11,1. In fact I don't have any other machines > > > > at home. > > > > > > > > I want to create a bootable USB drive with Qubes R3.2. I had the usual > > > > problem of seeing the 4-item menu to install but nothing working > > > > regardless of option chosen. I tried some forum suggestions like > > > > adding /noexitboot=1 to the cfg file. No luck. > > > > > > > > I created a working Qubes USB on a Lenovo computer at work. I was able > > > > to create new VM's and set firewall rules. So I know it works. > > > > > > > > Then my uninformed head took over. What if I took that USB and tried > > > > booting it on my Macbook? The Macbook does not even recognise the USB > > > > at boot time. If I boot into OSX I can get to the USB drive through > > > > terminal and mount it. > > > > > > > > I then tried copying rEFInd to the Qubes USB stick but that just hangs > > > > the Macbook after selecting the EFI boot option. I'm resisting > > > > installing rEFInd on the Macbook itself until I know more about it > > > > especially the need to disable SIP. > > > > > > > > My question is: would that even work - copying rEFInd to the working > > > > USB drive built on a Lenovo? Are there any other options I could try? > > > > > > > > Many thanks. > > > > > > > > > I also tried copying the EFI/qubes folder to EFI/BOOT and renaming the > > > two xen files to BOOTX64 - this hangs after selecting the EFI boot option > > > on Mac startup. > > > > Stupidly, when I copied EFI/qubes to EFI/BOOT I left the /noexitboot > > options in the CFG file. I removed them from EFI/BOOT/bootx64.cfg and > > retried. > > > > I can now boot into Qubes as far as the disk password prompt. The progress > > bar on the bottom centre of the screen progresses all the way across but I > > can not enter any characters into the password field. > > Macs have USB keyboard, which makes them incompatible with USB VM (at > least in default configuration). In particular, enabling USB VM prevent > USB controllers being initialized in dom0 - even during disk passphrase > prompt. To disable this part, you need to remove 'rd.qubes.hide_all_usb' > from kernel parameters. > Also the problem may be caused by missing USB controller (or keyboard > itself) driver in initramfs, but AFAIR it was fixed long ago. > > - -- > Best Regards, > Marek Marczykowski-Górecki > Invisible Things Lab > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > -BEGIN PGP SIGNATURE- > Version: GnuPG v2 > > iQEcBAEBCAAGBQJYKkivAAoJENuP0xzK19csPKUIAJjnVSSSTj1oJGyisBEFhNZk > 56thercS0SFlvMpdBmY4xXF+F+TuEuoK8VPFXJeQGUhyH8UtjuWYavC0wzWTsl2H > c3yMucbxHVvzmTTwth3ToYvfcaQUO+Zu89J9CfwsfzRsr2p53n4x6OECfuhuc/Hs > ftqPUDWOG87jXzaJVKS3SbWdg/8ifrDkEWgYCpXy/jTZiC3Zpd3K50aU0dFSG6Ww > Xv61SKSZjRbZNtrjBVgkUXxXgw5lD0rRuddlsUNqJJX4r+n/VlF7acukjYXfyfRM > TMvFoR9k5RH4leniSTMNTeQqQcSUgGAbPaa+dJ/OdyY+x5y6djtCBb72izQVY0k= > =5rjy > -END PGP SIGNATURE- Thanks for the info. For me a noob, how do I remove that parameter from kernel? 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-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/981eb4dd-6a27-48be-ae15-f7dc69714fd3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: One step foerward, two steps back on Macbook 11,1 - can't boot into Qubes
On Tuesday, 15 November 2016 09:02:56 UTC+11, dumbcyber wrote: > On Tuesday, 15 November 2016 08:47:30 UTC+11, dumbcyber wrote: > > From the beginning I have to ask for forgiveness - I am new to Qubes and > > have no knowledge of changing boot managers beyond trial and error. > > > > My hardware is a Macbook 11,1. In fact I don't have any other machines at > > home. > > > > I want to create a bootable USB drive with Qubes R3.2. I had the usual > > problem of seeing the 4-item menu to install but nothing working regardless > > of option chosen. I tried some forum suggestions like adding /noexitboot=1 > > to the cfg file. No luck. > > > > I created a working Qubes USB on a Lenovo computer at work. I was able to > > create new VM's and set firewall rules. So I know it works. > > > > Then my uninformed head took over. What if I took that USB and tried > > booting it on my Macbook? The Macbook does not even recognise the USB at > > boot time. If I boot into OSX I can get to the USB drive through terminal > > and mount it. > > > > I then tried copying rEFInd to the Qubes USB stick but that just hangs the > > Macbook after selecting the EFI boot option. I'm resisting installing > > rEFInd on the Macbook itself until I know more about it especially the need > > to disable SIP. > > > > My question is: would that even work - copying rEFInd to the working USB > > drive built on a Lenovo? Are there any other options I could try? > > > > Many thanks. > > > I also tried copying the EFI/qubes folder to EFI/BOOT and renaming the two > xen files to BOOTX64 - this hangs after selecting the EFI boot option on Mac > startup. Stupidly, when I copied EFI/qubes to EFI/BOOT I left the /noexitboot options in the CFG file. I removed them from EFI/BOOT/bootx64.cfg and retried. I can now boot into Qubes as far as the disk password prompt. The progress bar on the bottom centre of the screen progresses all the way across but I can not enter any characters into the password field. -- 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-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/2a2830e3-47cc-4303-bac7-2d651b4f30b9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: One step foerward, two steps back on Macbook 11,1 - can't boot into Qubes
On Tuesday, 15 November 2016 08:47:30 UTC+11, dumbcyber wrote: > From the beginning I have to ask for forgiveness - I am new to Qubes and have > no knowledge of changing boot managers beyond trial and error. > > My hardware is a Macbook 11,1. In fact I don't have any other machines at > home. > > I want to create a bootable USB drive with Qubes R3.2. I had the usual > problem of seeing the 4-item menu to install but nothing working regardless > of option chosen. I tried some forum suggestions like adding /noexitboot=1 > to the cfg file. No luck. > > I created a working Qubes USB on a Lenovo computer at work. I was able to > create new VM's and set firewall rules. So I know it works. > > Then my uninformed head took over. What if I took that USB and tried booting > it on my Macbook? The Macbook does not even recognise the USB at boot time. > If I boot into OSX I can get to the USB drive through terminal and mount it. > > I then tried copying rEFInd to the Qubes USB stick but that just hangs the > Macbook after selecting the EFI boot option. I'm resisting installing rEFInd > on the Macbook itself until I know more about it especially the need to > disable SIP. > > My question is: would that even work - copying rEFInd to the working USB > drive built on a Lenovo? Are there any other options I could try? > > Many thanks. I also tried copying the EFI/qubes folder to EFI/BOOT and renaming the two xen files to BOOTX64 - this hangs after selecting the EFI boot option on Mac startup. -- 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-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ad439eb1-2536-4ed7-bf9d-5a8c87efabe1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] One step foerward, two steps back on Macbook 11,1 - can't boot into Qubes
>From the beginning I have to ask for forgiveness - I am new to Qubes and have >no knowledge of changing boot managers beyond trial and error. My hardware is a Macbook 11,1. In fact I don't have any other machines at home. I want to create a bootable USB drive with Qubes R3.2. I had the usual problem of seeing the 4-item menu to install but nothing working regardless of option chosen. I tried some forum suggestions like adding /noexitboot=1 to the cfg file. No luck. I created a working Qubes USB on a Lenovo computer at work. I was able to create new VM's and set firewall rules. So I know it works. Then my uninformed head took over. What if I took that USB and tried booting it on my Macbook? The Macbook does not even recognise the USB at boot time. If I boot into OSX I can get to the USB drive through terminal and mount it. I then tried copying rEFInd to the Qubes USB stick but that just hangs the Macbook after selecting the EFI boot option. I'm resisting installing rEFInd on the Macbook itself until I know more about it especially the need to disable SIP. My question is: would that even work - copying rEFInd to the working USB drive built on a Lenovo? Are there any other options I could try? Many thanks. -- 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-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a8601f36-0c2a-4b63-8616-b5e49c65b549%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: macbookpro 11,3 installer keeps returning to grub menu
On Tuesday, 15 November 2016 06:25:25 UTC+11, pixel fairy wrote: > just what the subject line says. there is an error message, but it flashes by > too fast to read. all four choices have the same result. > > hardware is late 2013 15" retina, 11,3 Have the same problem with a Macbook 11,1. I tried adding /noexitboot and a few other options to the cfg file but the same result. Most people that have success seem to have moved to rEFInd for boot management on Macs. -- 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-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d6c3d568-eb24-43ee-ab5a-2d50c3fa8f54%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes: No direct install on MacBook Pro mid-2012 retina (10,1) system
On Monday, August 29, 2016 at 7:11:35 AM UTC+10, nrauh...@gmail.com wrote: > I have a mid-2012 MacBook Pro retina system - a 10,1 machine with 2.7GHz i7, > 750 gig SSD, and the Intel HD Graphics 4000. > > I put Qubes 3.1 on an 8 gig USB and booted the system with option key held > down. Qubes shows up as "EFI Boot" and it starts to a menu with four options: > > Test media and install Qubes R3.1 > Install Qubes R3.1 > Troubleshooting - verbose boot and Install Qubes R3.1 > Rescue a Qubes System > > I tried the first three and played a bit with the command prompt. When > selected the options flash something about a "file path:" which passes to > quickly for me to see, then it returns to the menu. > > My install target is an external USB 3.0 enclosure with a 120 gig SSD that > does a good job of running OSX. I was motivated to attempt this direct > install based on this article, which explains how to get the Broadcom BCM4313 > wireless card working. I realize the author installed Qubes using a PC, then > shifted to running it on a 10,1 Mac similar to mine. > > https://groups.google.com/forum/#!topic/qubes-users/pcPwoNsq-j8/discussion > > https://groups.google.com/forum/#!searchin/qubes-users/broadcom$20success/qubes-users/VVwWqvz5dX4/Xbum_4MaCgAJ > > Next I'll try a PC install to the external drive, then boot it on the Mac. I > just wanted to leave this here in case anyone else is tempted to try this > experiment. Having the same problem with a Macbook 11,1. Did you succeed? -- 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-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/be0f9bde-138e-42f4-805d-76d74cf1c06e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
