[qubes-users] Re: Help regarding installing CUBES
> Here is what i have done: > > 1. Downloadet and verified Cubes ISO > 2. From Windows 10, used Rufus (in DD mode) and wrote ISO to a Sandisk > Extreme Pro 32 GB SD card > 3. Im using a Dell XPS 9350 U6500 i7 laptop, in BIOS i have disabled "Secure > boot", which let me select legacy mode, so i can boot from the SD card > 4. Booting works fine - Qubes menu shows up... > 5. It does not matter what i select (install/test and install) the result is > the same... > 6. After i select one of them...it start checking some different stuff > (Loading xem.gz = OK, loading vmlinuz = OK, Loading initrd.img OK) > 7. I used my iphone to record the following text because it only shows up for > a sec... > > "9.179648 - dracut-pre-trigger[522]: cat: /tmp/dd_disk: No such file or > directory" > > after the error message above the screen stays black/blank and nothing > happens. I think that I had a similar issue with Qubes installing on an iMac. If memory serves me correctly, it was the same error message with dracut. I had to turn to rEFIt ( http://refit.sourceforge.net/ ) to get it to work. You're working on different hardware that might be more forgiving of that. In fact, the things you've listed, aside from trying a USB drive instead, are the things that I'd do. Secondly, it sounds like that the installer media isn't loading up the ramdisk that it will use to make itself work right. Maybe something as simple as the little plastic latch on the SD card that puts it into read only mode? Third, Qubes. It's spelled Qubes. Thought I'd correct that misspelling, before the more ... passionate Qubes users have the opportunity to do so. -- 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/788fd269-46a6-4a36-b38b-ea2a09962b65%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Help regarding installing CUBES
I'd encourage you to try checking different boot options in the BIOS. EFI, legacy, whatever. Try all of them. I'm unfamiliar with that hardware, but I've had success with tinkering with those sort of settings for getting Qubes installer media to boot. Also, I've never tried to boot Qubes installer from an SD card, so maybe try a USB drive too. -- 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/75f5441a-6b97-40f3-ba34-4c26e7a9b470%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: AMD Ryzen working with IOMMU, HCL results attached
On Tuesday, May 16, 2017 at 1:35:20 AM UTC-4, Bjoern Christoph wrote: > Am Montag, 15. Mai 2017 23:00:25 UTC+2 schrieb Grzesiek Chodzicki: > > W dniu poniedziałek, 15 maja 2017 21:24:30 UTC+2 użytkownik Bjoern > > Christoph napisał: > > > Hi all, > > > > > > Attached are the HCL results of my Ryzen system. > > > > > > It did NOT work out of the box on Qubes - IOMMU was not available. > > > However, Ubuntu stated it's working (BIOS IOMMU looks great) so I played > > > around a bit. > > > > > > Basically, two things are needed for working IOMMU in Xen used by Qubes: > > > 1) Update Xen with an IOMMU patch from AMD > > > 2) Update Xen with family 17h == Ryzen > > > > > > For step 1): Apply this patch (part or Xen 4.8.0): > > > https://patchwork.kernel.org/patch/9145119/ > > > > > > For step 2): xen/arch/x86/oprofile/nmi_int.c - Create a "case 0x17:" > > > entry which is the same as "case 0x15:" > > > > > > I installed Qubes, then proceeded as described to compile Qubes from > > > scratch. Before I did "make vmm-xen" I changed the above files within the > > > xen*.gz file. After that, I moved the files to dom0 and forced a > > > reinstall of the RPM files. > > > > > > Rebooted and voila, you can see the resul in the files :) Now I can get a > > > TPM I guess ;) > > > > > > I posted this nmi_int.c patch also on the xen-devel mailing list, let's > > > see if it's enough for them. > > > > > > Maybe these two patches can be added to Qubes 3.2 (if they work > > > properly). Not sure if there is anything else I can do to test if IOMMU > > > is working properly, if something is there to test that please let me > > > know! > > > > > > Cheers, > > > Bjoern > > > > Does PCI passthrough work for Windows VMs now that IOMMU is enabled? > > Ok, it's NOT working after all. Trying to install a HVM causes a reboot... so > I guess there is more work left there after all. > > You can ignore the HCL report then as well. Thanks for looking into this though. I'm starting to part out a system that will be specifically for Qubes usage and I'm very interested in the new AMD chips. -- 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/81bfbbe5-f063-41da-a45a-52bba3de4015%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
