[qubes-users] Re: install Qubes 3.2 Stucked at "Starting Switch Root..."
On Thursday, June 1, 2017 at 8:33:07 PM UTC-7, Paulo Marques wrote: > Hi There, > > I hope you guys can help me, I'm new to Qubes Os and i was trying to install > Qubes 3.2 but i'm stacked at "Starting to switch root..." and it just won't > proceed the installation. I've tried do enabled/disabled Uefi mode on the > bios, changed it to Uefi with legacy OPROM, but the result is always the > same, i'm stalled there. Can someone help me please! I really would like to > make a change in my system and i'd love to change to Qubes Os. > > I'm running on a core I5 6500 With a Z270-P Asus Motherboard, 275GB SSD > Crucial disk and 16GB of Ram. I'm curious whether the approach I posted to https://groups.google.com/forum/#!topic/qubes-users/4VsKdxnKHBk works for 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/0af6af8d-c676-4641-b52a-be878db165e0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: trouble with Lenovo P51 (nvidia quadro m1200)
I'm happy to report that I have Qubes running on the P51 now. I had considerable trouble getting it installed on the NVME drive. What finally worked for me, I've shared in a separate post: https://groups.google.com/forum/#!topic/qubes-users/4VsKdxnKHBk I did not end up needing nvidia drivers. Maybe in the future I'll mess around with that again. But for the time being I'm content with the display, and appreciate the kernel without nvidia's proprietary "taint". One problem that does bother me... the laptop occasionally does not wake from suspend. More often than not, it resumes just fine. But from time to time it does not and I have to power off then reboot. HCL report attached! -- 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/9ebc9af6-238b-46fd-b648-7e695a477542%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-LENOVO-20HHCTO1WW-20170625-233603.yml Description: Binary data
[qubes-users] Qubes 3.2 UEFI install media
I recently had some success install Qubes 3.2 on a lenovo p51, booting UEFI. I went through a lot of a trial and error in the process. I'm hoping this post can save others some time. I've seen in other threads some struggling to get Qubes working with UEFI firmware. I intended to save my command history to disk so that I could post step-by-step exactly what to do. But I must have been in a dispvm at the time, because now I can't find that history. So the following is from memory and not precise. I tried every trick I could find related to Qubes UEFI installation, and thinkpad troubleshooting. What finally worked does not appear to be documented in any of the Qubes documentation. Qubes uses Fedora's installer, Anaconda, and the following approach is documented on Fedora's wiki. 1. Follow Qubes install guide up to the `dd` command. Don't write to usb with `dd`. https://www.qubes-os.org/doc/installation-guide/ 2. Instead, use Fedora's `livecd-iso-to-disk` tool. You'll need the `livecd-tools` package. See https://fedoraproject.org/wiki/How_to_create_and_use_Live_USB#Command_line_method:_Using_the_livecd-iso-to-disk_tool_.28Fedora_only.2C_non-graphical.2C_both_non-destructive_and_destructive_methods_available.29 I don't recall for certain exactly what I passed to `livecd-iso-to-disk`. Try this: sudo livecd-iso-to-disk --efi --format Qubes-R3.2-x86_64.iso /dev/xvdi The media as written will not quite boot, yet. Qubes EFI boot is configured to find a label "Qubes-R3.2-x86_64", but the media written by the livecd tool is labelled "BOOT" (and the filesystem does not support the longer label, so the --label option would not help). 3. Mount the usb media (/dev/xvdi in the example above) 4. Edit xen.cfg. If I recall correctly, `/EFI/BOOT/xen.cfg`. In this file, replace every occurrence of `LABEL=Qubes-R3.2-x86_64` with `LABEL=BOOT` You should now have install media that work on UEFI firmware! After install, I recommend upgrading kernel version for recent hardware. I.e. with sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable kernel kernel-qubes-vm -- 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/54565916-4ae7-4029-8349-3c0afc59bb24%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] switch to integrated Intel graphic
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/26/2017 01:07 AM, Chris Laprise wrote: > On 06/25/2017 03:14 PM, Eva Star wrote: >> After I remove Radion card, system loaded. But resolution is >> only 1280x800 and no network access (network managed do not see >> wired network) Is it because Qubes installeted&updated on Radion >> card? Or I have too old integrated intel graphic (hd 2000 ) ? >> > > I'd guess that the PCI order/ID of your devices changed when you > removed the Radeon card, causing the NIC to no longer be recognized > by its old ID. If you go into Devices tab for your sys-net and > remove/re-add the NIC (then restart) it may work. > > Thanks. I will try, but it's part of the problem... How to fix resolution? Look like Qubes do not recognize intel graphic... But how it's possible... - -- Regards -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJZUDnRAAoJEGSin3PC/C0AiRAP/1tXQQuHl3AKpl9gQqN23CqO Yqq4tzDNLEP9Z/Q/y62HAdmErsMDLAu9ihtJYMw4FhzD17bAoCelpE1a7Lw0rzHh LJuS5Sm2ECa8rhdw7k+D45Td3fApr2/TDs7Q4jtqPDISFvOV1obKNPTDuCqyv/4k f3DRipimk4FdTRDrqCSr/0mHfYqKmdbAqYf8basVjubHos4NQ4gsf4WUXaZhUKuf eCUlLiamIhF1BXhzp7ZL3f3FFrvgYsIPTsbXRN70ZtVX1hzD4t/QsoUzGnYTHEv2 XjlGtrDTOG7co4JXCYGF7XeQspy5VhdwLE7wX/yJ/kGwUoSYhbLqBeKzFQDtG6XK f9m0pcCuXSyucJDtbP9+5LTieav0qzGxtLC07M3gogloupWTgzTCm5QBj8m9xyew qqfH24QafnGKxty07kXZidmHTru3IJZQDTXgrnVH3zGQFKjx9op+uAQcHqBVJjxP GG0lqBD2YKjbSOg9Fe7YfCQftKo12uIye4+PGv0lHWh2if+2+0S8yG0vuYuvJhvY 2xgFXAcRPDWwD5BsButeUzfJcYEr5U1I4Pf0k0Ssr2afEbQXXfLNKYqsh63KHdW+ cGS/Cg7TQD9aiVPQJfjpDZz8+X5G/QTzBBFlKt1qhrztjDXS8RVXMR1MPMgsv62O 0uT+qYJivEz3qDSHC8Ar =tR+7 -END PGP SIGNATURE- -- 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/f4d1b06b-0633-17b5-954a-b77035bb3a7a%40openmailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] switch to integrated Intel graphic
On 06/25/2017 03:14 PM, Eva Star wrote: After I remove Radion card, system loaded. But resolution is only 1280x800 and no network access (network managed do not see wired network) Is it because Qubes installeted&updated on Radion card? Or I have too old integrated intel graphic (hd 2000 ) ? I'd guess that the PCI order/ID of your devices changed when you removed the Radeon card, causing the NIC to no longer be recognized by its old ID. If you go into Devices tab for your sys-net and remove/re-add the NIC (then restart) it may work. -- Chris Laprise, tas...@openmailbox.org https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- 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/fa42aa05-bb66-a629-e68b-aafd892fc70a%40openmailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] switch to integrated Intel graphic
After I remove Radion card, system loaded. But resolution is only 1280x800 and no network access (network managed do not see wired network) Is it because Qubes installeted&updated on Radion card? Or I have too old integrated intel graphic (hd 2000 ) ? On 06/25/2017 09:45 PM, Eva Star wrote: > Hello, > > I'm always on Radion (no proprietary drivers, default Qubes setup). > Now, I'm trying to switch to Intel integrated Graphic at the same > machine (Intel HD 2000 on my processor). But I have troubles with > booting Qubes. I see only blinked keyboard cursor at the top left > corner. It show _after_ Qubes question what kernel to load (default or > advanced). Every kernel show the same cursor. > > Maybe somebody know how to fix this issue? > I think Qubes must work perfect with any intel integrated graphic... > Thanks > > -- Regards -- 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/a7fb6568-31b4-9bac-d502-46b148072abd%40openmailbox.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Can't install windows-tools, following docs.
I followed the docs to install Windows 7 via the 90 day trial from M$. I then followed the separate docs on install the windows-tools, but I keep getting a fail on installing windows-tools. Before submitting a bug report I wanted to see if there was something I'm just missing (since the docs tend to be more correct than I am). It seems enough of the tools installed for me to have networking, but not the rest. Since the log isn't so long I'll just paste it here: ``` [0AA0:0AA4][2017-06-25T18:14:36]i001: Burn v3.9.1208.0, Windows v6.1 (Build 7601: Service Pack 1), path: D:\qubes-tools-WIN7x64-3.2.2.3.exe, cmdline: '' [0AA0:0AA4][2017-06-25T18:14:36]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\IEUser\AppData\Local\Temp\Qubes_Windows_Tools_3.2.2.3_20170625181436.log' [0AA0:0AA4][2017-06-25T18:14:36]i000: Setting string variable 'WixBundleOriginalSource' to value 'D:\qubes-tools-WIN7x64-3.2.2.3.exe' [0AA0:0AA4][2017-06-25T18:14:36]i000: Setting string variable 'WixBundleOriginalSourceFolder' to value 'D:\' [0AA0:0AA4][2017-06-25T18:14:36]i000: Setting string variable 'WixBundleName' to value 'Qubes Windows Tools 3.2.2.3' [0AA0:0AB8][2017-06-25T18:14:36]i000: Setting version variable 'WixBundleFileVersion' to value '3.2.2.3' [0AA0:0AA4][2017-06-25T18:14:36]i100: Detect begin, 2 packages [0AA0:0AA4][2017-06-25T18:14:36]i101: Detected package: vcredist_x64.exe, state: Absent, cached: None [0AA0:0AA4][2017-06-25T18:14:36]i101: Detected package: qubes_tools_WIN7x64_3.2.2.3.msi, state: Absent, cached: Complete [0AA0:0AA4][2017-06-25T18:14:36]i104: Detected package: qubes_tools_WIN7x64_3.2.2.3.msi, feature: DisableUac, state: Absent [0AA0:0AA4][2017-06-25T18:14:36]i104: Detected package: qubes_tools_WIN7x64_3.2.2.3.msi, feature: Common, state: Absent [0AA0:0AA4][2017-06-25T18:14:36]i104: Detected package: qubes_tools_WIN7x64_3.2.2.3.msi, feature: Complete, state: Absent [0AA0:0AA4][2017-06-25T18:14:36]i104: Detected package: qubes_tools_WIN7x64_3.2.2.3.msi, feature: XenBase, state: Absent [0AA0:0AA4][2017-06-25T18:14:36]i104: Detected package: qubes_tools_WIN7x64_3.2.2.3.msi, feature: XenPvDrivers, state: Absent [0AA0:0AA4][2017-06-25T18:14:36]i104: Detected package: qubes_tools_WIN7x64_3.2.2.3.msi, feature: XenDisk, state: Absent [0AA0:0AA4][2017-06-25T18:14:36]i104: Detected package: qubes_tools_WIN7x64_3.2.2.3.msi, feature: XenNetwork, state: Absent [0AA0:0AA4][2017-06-25T18:14:36]i104: Detected package: qubes_tools_WIN7x64_3.2.2.3.msi, feature: CoreAgent, state: Absent [0AA0:0AA4][2017-06-25T18:14:36]i104: Detected package: qubes_tools_WIN7x64_3.2.2.3.msi, feature: MoveProfiles, state: Absent [0AA0:0AA4][2017-06-25T18:14:36]i104: Detected package: qubes_tools_WIN7x64_3.2.2.3.msi, feature: GuiAgentWindows, state: Absent [0AA0:0AA4][2017-06-25T18:14:36]i199: Detect complete, result: 0x0 [0AA0:0AB8][2017-06-25T18:14:40]i000: Setting numeric variable 'EulaAcceptCheckbox' to value 1 [0AA0:0AA4][2017-06-25T18:14:40]i200: Plan begin, 2 packages, action: Install [0AA0:0AA4][2017-06-25T18:14:40]w321: Skipping dependency registration on package with no dependency providers: vcredist_x64.exe [0AA0:0AA4][2017-06-25T18:14:40]i000: Setting string variable 'WixBundleLog_vcredist_x64.exe' to value 'C:\Users\IEUser\AppData\Local\Temp\Qubes_Windows_Tools_3.2.2.3_20170625181436_0_vcredist_x64.exe.log' [0AA0:0AA4][2017-06-25T18:14:40]i204: Plan 10 msi features for package: qubes_tools_WIN7x64_3.2.2.3.msi [0AA0:0AA4][2017-06-25T18:14:40]i203: Planned feature: DisableUac, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None [0AA0:0AA4][2017-06-25T18:14:40]i203: Planned feature: Common, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None [0AA0:0AA4][2017-06-25T18:14:40]i203: Planned feature: Complete, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None [0AA0:0AA4][2017-06-25T18:14:40]i203: Planned feature: XenBase, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None [0AA0:0AA4][2017-06-25T18:14:40]i203: Planned feature: XenPvDrivers, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None [0AA0:0AA4][2017-06-25T18:14:40]i203: Planned feature: XenDisk, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None [0AA0:0AA4][2017-06-25T18:14:40]i203: Planned feature: XenNetwork, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None [0AA0:0AA4][2017-06-25T18:14:40]i203: Planned feature: CoreAgent, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None [0AA0:0AA4][2017-06-25T18:14:40]i203: Planned feature: MoveProfiles, state: Absent, default requested: Unknown, ba requested: Unknow
[qubes-users] switch to integrated Intel graphic
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, I'm always on Radion (no proprietary drivers, default Qubes setup). Now, I'm trying to switch to Intel integrated Graphic at the same machine (Intel HD 2000 on my processor). But I have troubles with booting Qubes. I see only blinked keyboard cursor at the top left corner. It show _after_ Qubes question what kernel to load (default or advanced). Every kernel show the same cursor. Maybe somebody know how to fix this issue? I think Qubes must work perfect with any intel integrated graphic... Thanks - -- Regards -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJZUATHAAoJEGSin3PC/C0A/S8QAMjS9Gn4kDGg+IKPrmNy0VeR TAlryE/RXyLzZURHWWEgnKsiXhg52L9RIgjOZhugVEQfRSL2FpePYxnuvZ+S10wJ Ky/law492Ys8cDHWhJ31CZe78/o7WeMhqjXW0uLyzcLSTCy4DF8DPTs9SC8V6qjH m2ELSkgTY+F/TNljiv3u8MvArSe83Og/VhXZ6dOv4repAZSpKWE/C/dZn1WmIhtr poZUQsKso+Cb/sOjOXlzxV80rj66ZKqbBGBDljOiYJqEC9bM9ObDfZyKpdlnBFdF 7Hdb+QdQsuTln4eTNjmtM78OReii7igAoftp/tRTCUCzVxPyS25X4MlykYRIgAZk tMawN/O5BdTbwzRtUpTiiui/O67Qz5u2wr12TX1dyIL+clmZ0PiDIgB3fDXMJ0ko CAP3o/4pCZwyFhI/Ajbq1j3EP2htNUsJ2dzLHCAGhGv+TXeH2lWPCa7hHy5mZk+W kt/xbW+APzkvULm5Bu/JnG1TThOvtX+d4rD5tfHd5X0BaDWtAEaF1QvXo9xBAgoX xp0UM4Vp8MEaGzq0TNvyANhCgLxUhGixEYqYud9D0kJFEJBFY3g1YK75u2KWa6X8 Hzt56VBAPeswAGxwPk55NANEkttE0ZgGLdFQC90WELOy4BmFmMm0/vkhslQgToir JF0ped/NrGPHLuSmxK9U =HfZD -END PGP SIGNATURE- -- 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/16e2c92c-1b55-8fe2-2364-2a512d54a8e3%40openmailbox.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Laptop Dual Win10 boot problem
On 06/24/2017 11:52 PM, Alchemist wrote:
On Saturday, June 24, 2017 at 7:09:32 PM UTC-7, yreb-qusw wrote:
Hello, so I have win10 on the 1st 2 partitions of my SSD, and install
Qubes 3.2 onto the empty partition/s after the win10 installation.
However, looking in my InsydeH20 BIOS, I am given no option to select a
win10 vs. Qubes boot. Only "notebook HD", "USB" etc.
Perhaps my mistake for thinking the laptop BIOS might function the way
the ASrock BIOS, does, which does give me a choice.
So, Now the "notebook" option just boots Qubes,Can I still boot
Win10 on the other , 1st, partitions?
if so, how ?
thx
What you want to do is install Windows first and then install Qubes, you want
to edit GRUB so you can boot Windows from GRUB.
https://www.qubes-os.org/doc/multiboot/
thanks, so if I got Qubes installed and up and running, does this mean
my Bios is in "legacy mode" already? As I don't really see an option in
the INSYDEH20 Bios to enable Legacy mode.
re:
--
Add this stanza to /etc/grub.d/40_custom,
menuentry "Windows" {
insmod part_msdos
insmod ntldr
insmod ntfs
ntldr (hd1,X)/bootmgr
}
(Change X to reflect the relevant system partition.)
--
What would be an example of what goes in "X" ?
--
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/221277a8-c542-38b1-b168-ef362e517076%40riseup.net.
For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] getting win7 VM working licenses etc
On 06/25/2017 04:07 AM, Unman wrote: On Sat, Jun 24, 2017 at 04:51:36PM -1000, yreb-qusw wrote: forgive me , if this seems off topic. but, somehow I need to have a working version of windows that doesn't require me to reboot preferably. And i've been looking around, for this answer , but maybe someone else here might know: I have a windows 7 license that came preinstalled on an old desktop, I then used that license on a laptop reinstall, for win7, I then upgraded and have been using win10 on the laptop, is the original win7 license likely now invalid? as it was upgraded to win10 which uses a different system? Because I guess I need win7 to use in a Qubes VM ; and further, the win10 is still installed on the 1st partitions of the laptop, though I am at a loss how to boot it, as you can see in my other post. If I can't dual boot the win10 with Qubes on this InsydeH20 Bios , I may have to go reinstall win10 and not use Qubes on the laptop , hmmm In the arcane world of Windows licensing, the Windows7 on your laptop was almost certainly not licensed, and therefore your Windows10 isnt either. Even if it had been licensed properly, it now wouldnt be. This doesnt mean that you might not be able to install 7 and pass online licensing. thx, so what I am afraid of , is say, I "edit GRUB" and do get the win10 (that was already installed before Qubes) working correctly, since the win10 upgrade was based on the original win7 license (from an old desktop), then If I were to go and download a win7.iso (which seems to require the original code before allowing download), to install in a Qubes VM, THEN, that would invalidate the currently installed win10 on the other partition, if you follow ? I may not be allowed to have win7 in a Qubes VM and win10 on a partition on the same laptop that trace back to the same original license ? :) -- 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/ed68b4f3-c0a1-1eed-ffb3-5a42293a39c5%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Ubuntu Template
On Sun, Jun 25, 2017 at 04:31:15AM -0700, Michael MENG wrote: > > I was trying to build the Ubuntu 16.04 Xenial+Desktop template > using qubes-builder with help from these instructions: > > https://www.reddit.com/r/Qubes/comments/5vzg04/idiots_guide_to_installing_qbuntu_ubuntu_1604/ > > Everything was alright until the `make template` step where it would > fail on the following: > > makefile:294: recipe for target 'template-local-xenial+desktop' failed > Some of the recent commits have broken the Ubuntu builds. I'll provide patches soon. unman -- 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/20170625140934.rtlpjnfytqhysxbc%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] getting win7 VM working licenses etc
On Sat, Jun 24, 2017 at 04:51:36PM -1000, yreb-qusw wrote: > forgive me , if this seems off topic. but, somehow I need to have a working > version of windows that doesn't require me to reboot preferably. And i've > been looking around, for this answer , but maybe someone else here might > know: > > I have a windows 7 license that came preinstalled on an old desktop, I then > used that license on a laptop reinstall, for win7, I then upgraded and > have been using win10 on the laptop, is the original win7 license likely > now invalid? as it was upgraded to win10 which uses a different system? > > Because I guess I need win7 to use in a Qubes VM ; and further, the > win10 is still installed on the 1st partitions of the laptop, though I am > at a loss how to boot it, as you can see in my other post. > > If I can't dual boot the win10 with Qubes on this InsydeH20 Bios , I may > have to go reinstall win10 and not use Qubes on the laptop , hmmm In the arcane world of Windows licensing, the Windows7 on your laptop was almost certainly not licensed, and therefore your Windows10 isnt either. Even if it had been licensed properly, it now wouldnt be. This doesnt mean that you might not be able to install 7 and pass online licensing. -- 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/20170625140743.qf3vdsmdsml5hbs3%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Keyboard shortcuts in /etc/qubes/guid.conf
On Sat, Jun 24, 2017 at 11:13:34AM +0200, Noor Christensen wrote: > On Sat, Jun 24, 2017 at 10:44:14AM +0200, Noor Christensen wrote: > > Hi, > > > > I was about to change the key sequences gobally used for VM clipboard > > managament and found /etc/qubes/guid.conf to be the correct place. > > > > Then I got curious, what subsystem is Qubes using for the keyboard > > bindings? I need to figure out what the Mod4/Meta/Windows key is called > > in this particular context. > > > > I took a peek at the libconfig manual[0] as mentioned in the "Getting > > started" docs[1] but it does not mention anything specific about > > keyboard or input control, so I guess those values are parsed by some > > other entity actually handling the key bindings. > > I found some clues in the qubes-gui-daemon source: > > https://github.com/QubesOS/qubes-gui-daemon/blob/ad966ddd5d57b30a47651471a1cbdbe7ac8231fa/gui-daemon/xside.c#L2957 > > However, I'm having problems using Mod4 as a key identifier here. > > Anybody else having success with this? > > -- noor I assume you mean the "Side view of four qubes waving around" key?(TM Rusty Bird) Use xev and you will probably find it's mapped to Super_L, but "Super" will probably do. Try it. unman -- 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/20170625140344.vfmx2j7gzmxyolxc%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Internet
On Fri, Jun 23, 2017 at 09:16:57PM -0700, davidchoy...@gmail.com wrote: > I have installed qubes os and I can't figure out how to connect to the > internet at all. I have no idea what to do and I so far nothing has helped me > at all. Please tell me step by step how to connect to the internet after > freshly installing > Qubes > I'm afraid that without a good deal more information it's quite difficult to help you. I have no idea what hardware you are using or what level of experience you have, nor what you have tried to do so far. In general, the problems of getting online in Qubes are those of getting online in whatever distro you are using as template for sys-net. So a first step would be: 1. Search for problems with the NIC and the distro you are using. The Qubes specific areas: Make sure that your NIC is assigned to sys-net. (Devices tab on Settings.) Open a terminal in sys-net: check boot and any messages.(journalctl dmesg etc.) In particular, look to see if there are any errors associated with the NIC. Check output of lspci, lsusb, 'ip addr' - depending on what type of device you have assigned to sys-net. In most cases, the problem is that the NIC requires firmware that isnt loaded in sys-net. As with any template based qube, you will have to install the firmware in the Template used by sys-net. When you do this, remember to close down the Template and then restart sys-net. unman -- 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/20170625135829.4qkfvr7wbjsp64d2%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Booting with dom0 exposed to usb controllers.
On Sat, Jun 24, 2017 at 03:10:07PM -0300, Franz wrote: > On Sat, Jun 24, 2017 at 12:16 PM, Alan Got wrote: > > > Hi, > > I'm using usb mouse and keyboard attached to InputVM (usb controler 1). > > Another usb controller (2) is attached to UntrustedVM. When I need to > > restart computer I'm disconnecting physically all usb devices attached to > > controller (2). It is possible that controller (2) would compromise Qubes > > at boot time? > > > > I suppose that with the word "attached" you mean what in Qubes definitions > is called "assigned". > > In this case can tell that when I tried to assign two different USB > controllers to two different VMs, dom0 refused to do that claiming that the > controllers were sharing some resources and so there was a security risk. > So, if in your case you were allowed to do that, then your controllers > should be really separated and that may be encouraging. > > best > Fran > > > > My mainboard don't have any PS/2 ports and my processor don't support TXT > > (to use AEM), it only support IOMMU. The boot option rd.qubes.hide_all_usb is intended to stop dom0 from being compromised by a malicious controller. Since you have VT-d you should be all right. (Check that you are booting with that option obviously.) unman -- 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/20170625134154.pb2hq2mw4udnukqv%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] power9 and qubes os
On 06/24/2017 08:16 PM, Johnysecured88 wrote: Are you a developer? No. Can we get input from a developer on this issue? You should email the community liaison, as it is definitely a question worth asking. a...@qubes-os.org If you want a supported build done by them you would probably have to provide the funds for a new/used recent POWER system. -- 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/6e954b5d-f979-2c8a-aaa0-f35d569c6fa0%40gmx.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: certified laptop delivery to Russia
For reference here is a link to an "off the shelf" system that has vendor supplied init code and hardware specs https://en.wikipedia.org/wiki/Novena_(computing_platform) "Free" high performance systems are not as easily found but here is one http://www.tyan.com/EN/solution/openpower-GN70BP010/index.htm AFAIK what stops more performance (ie: power not arm) vendors from doing this more often is that it costs money without providing a substantial reward so systems like these are generally only made for other vendors instead of end users. -- 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/446e7257-b571-d3cf-2012-a62d6961da4d%40gmx.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Ubuntu Template
I was trying to build the Ubuntu 16.04 Xenial+Desktop template using qubes-builder with help from these instructions: https://www.reddit.com/r/Qubes/comments/5vzg04/idiots_guide_to_installing_qbuntu_ubuntu_1604/ Everything was alright until the `make template` step where it would fail on the following: makefile:294: recipe for target 'template-local-xenial+desktop' failed -- 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/e31c0b0d-dd07-4b8f-ba6b-00c1502b913a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Laptop Dual Win10 boot problem
On Saturday, June 24, 2017 at 7:09:32 PM UTC-7, yreb-qusw wrote: > Hello, so I have win10 on the 1st 2 partitions of my SSD, and install > Qubes 3.2 onto the empty partition/s after the win10 installation. > > However, looking in my InsydeH20 BIOS, I am given no option to select a > win10 vs. Qubes boot. Only "notebook HD", "USB" etc. > > Perhaps my mistake for thinking the laptop BIOS might function the way > the ASrock BIOS, does, which does give me a choice. > > So, Now the "notebook" option just boots Qubes,Can I still boot > Win10 on the other , 1st, partitions? > > if so, how ? > > thx What you want to do is install Windows first and then install Qubes, you want to edit GRUB so you can boot Windows from GRUB. https://www.qubes-os.org/doc/multiboot/ -- 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/1715a92a-1db1-4168-960a-73d38ca4adb0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL -- Lenovo Yoga 3 Pro?
Hi, I'm a little stuck doing an HCL report and submitting a how-to wiki. Could you please help me collect some mailing-list experiences and debug info? I'm stuck in a loop on 3 issues -- any tips to make things simpler? 1. I get the "nmi watchdog soft lockup" error every three boots or so -- I think this issue screws up other things like attaching a USB device, as well. I've tried the Xen configs in the UEFI Troubleshooting wiki, but I can't tell any change in behavior. Sometimes Plymouth hangs the boot, sometimes unlocking the drive hangs it ... Could you please help me collect debug info at this level? With a little refresher, I could capture boot logs onto a USB. 2. Wifi is not working for me. What info would be useful here? I'm not sure what commands to run. 3. I've had trouble finding a USB ethernet dongle that works out of the box. My StarTech dongle needs the asix.ko driver ... Fedora ships this, but loading modules into Qubes seems like a pain. My 3 leads seem really hard, like I'm doing something wrong. Am I even close? Would appreciate your help a lot, Mitch -- 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/3658ac0a-4e99-4e0d-8240-daf7d0e1ffe7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
