[qubes-users] No Network access
I'm running Qubes 3.2 on an Asus R541U My system isn't able to utilize the built in Ethernet and Wifi adapters. lspci command in sys-net shows both of them. ifconfig shows lo and vif2.0 interfaces. I tried to perform "sudo dnf install linux-firmware" as recommended by the user's FAQ and get "Error: Failed to synchronize cache for repo 'updates'" (by the way, the faq still has yum instead of dnf) I'm currently trying to find an offline workaround or solution. I would appreciate assistance in that endeavor, or alternately, a heads up that I need to find another tree to bark up. -- 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/e2401f4d-33ac-4c06-94fd-494113c7dd37%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Can't figure out how to configure WiFi (Qubes 3.2)
This is honestly a pretty stupid question, but no matter how I search, I can't find the button that allows me to connect to WiFi. What do I do? -- 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/b7d1b8f3-e988-4611-bf6d-641829f4a89f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes-R4.0-rc1 installation fails
W dniu piątek, 25 sierpnia 2017 18:40:32 UTC+2 użytkownik sigmu...@gmail.com napisał: > Hello, > > I just acquired a new computer with the following characteristics: > > - Motherboard: MSI X370 Gaming Pro Carbon > - CPU: AMD Ryzen 7 1700X > > With another computer, I installed the Qubes 4.0 RC1 iso on a USB stick from > Ubuntu, following the tutorial on the official site. (I also checked its > integrity beforehand) > > Once plugged in the new computer, the installation UI (cyan background) shows > up. I select "Install Qubes R4.0-rc1", the screen turns black and my computer > reboots after some seconds to bring me again to this menu. > > In the troubleshooting section, I selected "Install Qubes R4.0-rc1 in basic > graphics mode" to see the debug logs. I had to record my computer with my > phone because here again the screen turns black and my PC reboots ; I managed > to grasp the last frame before it turns black, here's a screenshot : > > > http://puu.sh/xjjbb/f487abdd69.jpg > > > I didn't try to install Qubes 3.2 on it. Also, the hard drive is blank and I > don't have coreboot/libreboot installed (not compatible with my hardware)... > > The line "xenoprof: Initialization failed. AMD processor family 23 is not > supported" worries me a bit. Anyone knows a solution to this problem, if > there is one? > > > Thanks in advance! > > N.W. Qubes ships with Kernel 4.9 however Ryzen support was only added in kernel 4.11 -- 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/767fddf6-ebad-4bbc-b625-8565fc2bb039%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Audio broken in R4.0 rc1 / qvm-run fails to start AppVM
W dniu piątek, 25 sierpnia 2017 16:38:09 UTC+2 użytkownik nicholas roveda napisał: > I've checked the BIOS configs and VT-d is enabled. Try with pci_strictreset set to false for this particular 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/bc1e8258-20c5-47a4-ab9e-2ec3066bc07b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes-R4.0-rc1 installation fails
Hello, I just acquired a new computer with the following characteristics: - Motherboard: MSI X370 Gaming Pro Carbon - CPU: AMD Ryzen 7 1700X With another computer, I installed the Qubes 4.0 RC1 iso on a USB stick from Ubuntu, following the tutorial on the official site. (I also checked its integrity beforehand) Once plugged in the new computer, the installation UI (cyan background) shows up. I select "Install Qubes R4.0-rc1", the screen turns black and my computer reboots after some seconds to bring me again to this menu. In the troubleshooting section, I selected "Install Qubes R4.0-rc1 in basic graphics mode" to see the debug logs. I had to record my computer with my phone because here again the screen turns black and my PC reboots ; I managed to grasp the last frame before it turns black, here's a screenshot : http://puu.sh/xjjbb/f487abdd69.jpg I didn't try to install Qubes 3.2 on it. Also, the hard drive is blank and I don't have coreboot/libreboot installed (not compatible with my hardware)... The line "xenoprof: Initialization failed. AMD processor family 23 is not supported" worries me a bit. Anyone knows a solution to this problem, if there is one? Thanks in advance! N.W. -- 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/0e0a1a78-af67-491c-97c7-c3641e225b1f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Network Manager: 'Device not ready' after suspend.
Hi, I had the same issue, and the workaround metioned by Reg worked for me: https://www.qubes-os.org/doc/wireless-troubleshooting/#automatically-reloading-drivers-on-suspendresume Maybe there are two differen issues. Just to be sure, do you restarted the sys-net after modify the /rw/config/suspend-module-blacklist file? -- 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/5cc0c7b1-b614-474a-ab5b-6472f022bf99%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Unofficial forward-ported grsec 4.9 Qubes kernel branch
On 2017-08-25 8:35 AM, nicholas roveda wrote: > Thanks for all the details. > > I've tested on the R4.0 rc1, so fc25, I'll try it soon on the R3.2 (fc23 and > fc24), so we can crosscheck the script. > > I saw both dom0 and vm rpms are generated, but is it better to generate > different rpms for them with config-host and config-vm? > Having the build script spit out separate rpms (or ideally, use config-host for the kernel.rpm and config-guest for the kernel-qubes-vm.rpm) would be ideal (but then figuring out how to handle kernel-devel.rpms for both might be a challenge), but I really just intended for that grsec branch to be a proof-of-concept using existing Qubes build infrastructure. I wasn't intending on extending things (and to be honest, I don't have the time), but if someone else wanted to take it on, they're certainly welcome to! -- 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/onpd6u%2425a%241%40blaine.gmane.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Audio broken in R4.0 rc1 / qvm-run fails to start AppVM
I've checked the BIOS configs and VT-d is enabled. -- 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/538d3d0e-0cda-4259-bc7f-fbac12880401%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Unofficial forward-ported grsec 4.9 Qubes kernel branch
Thanks for all the details. I've tested on the R4.0 rc1, so fc25, I'll try it soon on the R3.2 (fc23 and fc24), so we can crosscheck the script. I saw both dom0 and vm rpms are generated, but is it better to generate different rpms for them with config-host and config-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/9bbd1168-99c1-4d44-8733-4d0fff65f44d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Unofficial forward-ported grsec 4.9 Qubes kernel branch
Thanks for all the details. I've tested on the R4.0 rc1, so fc25, I'll try it soon on the R3.2 (fc23 and fc24), so we can crosscheck the script. I saw both dom0 and vm rpmd are generated, but wouldn't be better to generate different rpms based on config-host and config-guest? -- 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/8082f643-5ac7-464c-861b-2e2030fbd5f0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Android-x86 6.0 (Marshmallow) on HVM, relatively usable for app debugging
On 08/25/2017 10:07 AM, Alex wrote: Following up on my previous post on setting up Android 6.0 as a Qubes HVM for app debugging purposes, I'm fixing some of the things that were left unsolved, namely: * screen goes to unrecoverable standby after little time * fix vga settings in grub config * enable adb via tcp * allow VNC connections First, we fix the screen timeout. That's relatively easy: * Open Settings * Go to "About Tablet" * Tap 8 times over the build number (until you're a developer) * Go back to settings * Go to newly added "Developer Options" * Enable "Stay awake" Then we need to setup TCP connection to our work appvm (or the one in which Android Studio is installed and will be used). These steps are adapted from qubes-os.org/doc/firewall * Gather IP addresses (qubes ones) for work and android-6 * Open a shell in sys-firewall [sys-fw]$ sudo iptables -I FORWARD 2 -s -d -j ACCEPT [sys-fw]$ sudo iptables -I FORWARD 2 -s -d -j ACCEPT * Open a shell in work appVM [work]$ sudo iptables _I INPUT -s -j ACCEPT * Firewall in Android-x86 already allows connections, so test: [work]$ ping [android-terminal-emulator]$ ping * Should be able to ping. If this is the case, follow instructions in qubes-os.org/doc/firewall to ensure persistence of these settings in both work appVM and sys-firewall. Now we can configure the ADB TCP port for remote debugging: * inside Android open the terminal emulator again if closed [android-terminal-emulator]$ su [android-terminal-emulator]# setprop service.adb.tcp.port [android-terminal-emulator]# stop adbd [android-terminal-emulator]# start adbd * check from work appVM (Android studio and the tools should have already been installed, so that you have "adb" available) [work]$ adb connect : * Should say "connected to 10.137.xx.yy:" If this is the case, you now have a friendlier connection for your system! Now our Android HVM will have to be booted from dom0 command line, but we can make it easier by persisting the vga= config in grub. To do that, we must restart Android and: * from the GRUB menu select the second line (Debug Mode) * boot will stop at a temporary root MirBSD Korn shell * give it a couple of Enter keys to clear logs out of the way * now type: [android]# mount -o rw,remount /mnt [android]# cd /mnt/grub [android]# vi menu.lst * edit the file as to append the VGA parameter * press "i", move the cursor, add text * save and quit * press Esc, then type ":wq" * exit the shell TWICE and android will try to complete its boot * but because we did not set the "vga" parameter in the debug line, it will most likely fail * kill the VM from VM Manager Now we can start the android vm with a relatively easy dom0 command, it will automatically and quickly boot to a relatively usable android (sometimes some google background service will crash) with no problems with screen timeouts. The only problem remaining is the mouse, that can be bypassed with a VNC connection. Problem is, our Android is x86 and most VNC servers out there are for ARM devices. There is an x86 build of android-vnc-server at http://xmodulo.com/how-to-run-vnc-server-on-android-x86.html but it has not PIE enabled (some exploit protection) so Marshmallow will refuse to load it. Now you have TWO paths available: one is * download the android-vnc-server project * update it and compile it for x86 with PIE * load it into our HVM and use it to connect the other is * patch the /system/bin/linker executable in Marshmallow to avoid PIE check * load the already compiled assembly found at previous link * use it to connect I went through the second path, since I'm more of a reverse engineer than a library archaeologist, and really don't like the idea of trying to compile things from the past with obscure (to me) options. I found a nice explanation at https://forum.xda-developers.com/google-nexus-5/development/fix-bypassing-pie-security-check-t2797731/page13#127 about a guy that did exactly this patch for Android 5.1. Following his steps I disassembled /system/bin/linker from our Marshmallow HVM and found that the 4 bytes to patch for the check are at 0xD25A (file offset): they start with 0x0F 0x85. Patch the 4 bytes with four NOPs (0x90), save, and replace the linker with your patched version. * put the new linker in /storage/emulated/0/linker_new * restart the Android HVM in Debug mode again * once there the layout of the FS is completely different * find linker_new inside /mnt/android-6.0-r1/data/media/0/ * copy it over to /android/system/bin * chmod it to 755 * exit TWICE from the MirBSD shell and kill HVM * start android normally (via the qvm-start custom command, as usual) * push droidvnc_x86 you downloaded from the link above into the VM [work]$ adb push droidvnc_x86 /storage/emulated/0/ [work]$ adb shell [adb]$ su [adb]# mv /storage/emulated/0/droidvnc_x86 /system/bin/ [adb]# chmod
[qubes-users] Re: Qubes 4rc1 and Windows 7 :: Can it be done (already)?
Am Mittwoch, 16. August 2017 20:22:41 UTC+2 schrieb PR: > hello, > > for my business tasks I need to have a windows 7 HVM running as some > programs are only available in windows like our ERP/CRM. > > After some testing windows was running ok under Qubes 3.2, but I haven't > found any information regarding Qubes 4.x and Windows 7. > It seems that it can't be done with the current version RC1 as I can't > choose "stand alone" when creating a new AppVM. > > As windows support is very important to me and I guess also other > (potential) business users: > What are the plans for supporting windows including seamless mode on > Qubes 4? > > If this is not supported I am forced to use Qubes 3.2 which results in > another question: > How long will Qubes 3.2 be supported? > > kind regards > > - PhR Any new informations ? Greetings -- 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/716efe8d-1919-4e69-8b9b-27086dab7539%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Android-x86 6.0 (Marshmallow) on HVM, relatively usable for app debugging
Following up on my previous post on setting up Android 6.0 as a Qubes HVM for app debugging purposes, I'm fixing some of the things that were left unsolved, namely: * screen goes to unrecoverable standby after little time * fix vga settings in grub config * enable adb via tcp * allow VNC connections First, we fix the screen timeout. That's relatively easy: * Open Settings * Go to "About Tablet" * Tap 8 times over the build number (until you're a developer) * Go back to settings * Go to newly added "Developer Options" * Enable "Stay awake" Then we need to setup TCP connection to our work appvm (or the one in which Android Studio is installed and will be used). These steps are adapted from qubes-os.org/doc/firewall * Gather IP addresses (qubes ones) for work and android-6 * Open a shell in sys-firewall [sys-fw]$ sudo iptables -I FORWARD 2 -s -d -j ACCEPT [sys-fw]$ sudo iptables -I FORWARD 2 -s -d -j ACCEPT * Open a shell in work appVM [work]$ sudo iptables _I INPUT -s -j ACCEPT * Firewall in Android-x86 already allows connections, so test: [work]$ ping [android-terminal-emulator]$ ping * Should be able to ping. If this is the case, follow instructions in qubes-os.org/doc/firewall to ensure persistence of these settings in both work appVM and sys-firewall. Now we can configure the ADB TCP port for remote debugging: * inside Android open the terminal emulator again if closed [android-terminal-emulator]$ su [android-terminal-emulator]# setprop service.adb.tcp.port [android-terminal-emulator]# stop adbd [android-terminal-emulator]# start adbd * check from work appVM (Android studio and the tools should have already been installed, so that you have "adb" available) [work]$ adb connect : * Should say "connected to 10.137.xx.yy:" If this is the case, you now have a friendlier connection for your system! Now our Android HVM will have to be booted from dom0 command line, but we can make it easier by persisting the vga= config in grub. To do that, we must restart Android and: * from the GRUB menu select the second line (Debug Mode) * boot will stop at a temporary root MirBSD Korn shell * give it a couple of Enter keys to clear logs out of the way * now type: [android]# mount -o rw,remount /mnt [android]# cd /mnt/grub [android]# vi menu.lst * edit the file as to append the VGA parameter * press "i", move the cursor, add text * save and quit * press Esc, then type ":wq" * exit the shell TWICE and android will try to complete its boot * but because we did not set the "vga" parameter in the debug line, it will most likely fail * kill the VM from VM Manager Now we can start the android vm with a relatively easy dom0 command, it will automatically and quickly boot to a relatively usable android (sometimes some google background service will crash) with no problems with screen timeouts. The only problem remaining is the mouse, that can be bypassed with a VNC connection. Problem is, our Android is x86 and most VNC servers out there are for ARM devices. There is an x86 build of android-vnc-server at http://xmodulo.com/how-to-run-vnc-server-on-android-x86.html but it has not PIE enabled (some exploit protection) so Marshmallow will refuse to load it. Now you have TWO paths available: one is * download the android-vnc-server project * update it and compile it for x86 with PIE * load it into our HVM and use it to connect the other is * patch the /system/bin/linker executable in Marshmallow to avoid PIE check * load the already compiled assembly found at previous link * use it to connect I went through the second path, since I'm more of a reverse engineer than a library archaeologist, and really don't like the idea of trying to compile things from the past with obscure (to me) options. I found a nice explanation at https://forum.xda-developers.com/google-nexus-5/development/fix-bypassing-pie-security-check-t2797731/page13#127 about a guy that did exactly this patch for Android 5.1. Following his steps I disassembled /system/bin/linker from our Marshmallow HVM and found that the 4 bytes to patch for the check are at 0xD25A (file offset): they start with 0x0F 0x85. Patch the 4 bytes with four NOPs (0x90), save, and replace the linker with your patched version. * put the new linker in /storage/emulated/0/linker_new * restart the Android HVM in Debug mode again * once there the layout of the FS is completely different * find linker_new inside /mnt/android-6.0-r1/data/media/0/ * copy it over to /android/system/bin * chmod it to 755 * exit TWICE from the MirBSD shell and kill HVM * start android normally (via the qvm-start custom command, as usual) * push droidvnc_x86 you downloaded from the link above into the VM [work]$ adb push droidvnc_x86 /storage/emulated/0/ [work]$ adb shell [adb]$ su [adb]# mv /storage/emulated/0/droidvnc_x86 /system/bin/ [adb]# chmod 755 /system/bin/droidvnc_x86 [adb]# droidvnc_x86 * if everything is ok, you will
Re: [qubes-users] Re: Qubes-R4.0-rc1-x86_64 how to Install a Browser
Hello after rebooting the Qubes OS Laptop and restarting with qvm-start fedora-25 i got a error b' Snapshot origin LV vm-fedora25-privat not found Volume group qubes_dom0 .\n have a nice day vinc -- 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/03ffbc0fa149fc4fca6d95a0384dcbda%40kozo.ch. For more options, visit https://groups.google.com/d/optout.
