Jump to content

scorcho99

Members
  • Content Count

    120
  • Joined

  • Last visited

Everything posted by scorcho99

  1. Good tip on the uefi shell. I think I actually had to do that when I installed the modded bios to disable write protection or something, I didn't get that far but I did wonder at the time if I could have just used the shell to change the option. I don't know much about bios modding (more than I did now) A guy on win-raid forums created the bios mod for me and I sent him a amazon card as thanks. Anyway, I ultimately decided against using GVT-g, but it was a fun experiment...required me to figure out a lot of pieces I didn't know anything about. It was a death of a thousand cuts for final purpose though. In addition to having pretty weak performance potential, it didn't support old Windows OSes, without openGL in unraid I couldn't get it to display in spice, it didn't support saving VM states and I believe I had a fair amount of trouble with it in linux guests? I can't remember. And there is (currently) no (straightforward) way to direct output to another display which I wanted. It just wasn't a great fit for any of the use cases I'd dreamed up for it. Maybe after it bakes a little longer. I ended up selling my Intel hardware and went with a Ryzen setup for more cores. I ended up deciding that a mining riser with a bunch of zerocore supporting AMD graphics cards was more flexible even if it is a big cabling mess. Only thing I feel like I'm missing out on is quicksync which is pretty good.
  2. Is there a reason you have all the acs override options on? I'm mostly asking because I don't know if its required for this chipset or not since its so new!
  3. I tried yesterday to run 3dmark firestrike for first time ever on a z77 and rx 470 with a windows 8.1 VM, seabios based. I got crashing on scan systeminfo as well. So as a sanity test, I installed Windows 10 (1709?) fresh onto bare metal and tried it today and the benchmark ran without any apparent issues. I'm not sure the cause or if it ever worked. I was running unraid 6.8.3, its just on my test rig. I'll have to try and isolate the issue I guess. It seemed pretty stable, I was running heaven benchmark before. The system was having a lot of issues once I tried 3dmark though, not sure if all of them were related. I assume you were running Windows 10 in your VM? I know there is a MSRS fix that you sometimes have to do, I've never done it myself but that seems like a possible culprit to me.
  4. Are you doing primary GPU passthrough? (You only have one GPU) If so have you tried adding video=efifb:off,video=vesafb:off to your syslinux.cfg? I had to do that to get primary working with my nvidia gpus. Note you will lose unraid console video out early in the process.
  5. I don't know much about Volumino (never heard of it before now) but it sounds like its debian based. I run GTX950 and GTX1060 3GB cards in linux mint 18 VMs for my HTPC/Couch gaming VM and they run fine. They are seabios 440bx based VMs. For sound, I needed to use the MSI fix (its similar to the one used for Windows) otherwise the audio was garbled and the VM ran awful but otherwise I didn't do anything special.
  6. I have a 4tb parity disk that I'm going to let go, way back when it was used as a ntfs disk with some sensitive information as it was used as backup drive. I installed it in a test unraid machine with a 1tb drive, a 500gb drive and a few other smaller drives. Was the act of parity syncing effectively the same as having performed a secure erase? Nothing on there can be recovered right? I actually don't care array data, just the stuff that was on the disk when it was ntfs. Just a sanity check question here, it seems like the entire disk should have been filled with effectively random data or zeroes.
  7. @0x00000111 Can you show us the device listing/lspci so we can see what bridges and chips it uses? What platform are you running this on? (Ryzen, Intel, what chipset?) Thanks for the update.
  8. My mistake, these cards aren't Startech, they are Syba. They aren't a lot of use for people here perhaps because they aren't 4 USB controllers. I basically use a bunch of them to get SATA ports and USB ports out of all my PCI-e 1x slots. https://www.amazon.com/gp/product/B00MVTB8TK/
  9. Surprised so many people have trouble with these. I own a bunch of startech SATA/USB3.0 combo cards with the same USB controllers and asmedia bridges and they all passthrough the USB controller fine.
  10. I've had this problem with earlier releases when changing other configuration options. Never really did figure it out, but it never seemed to happen when I wasn't messing with things so I wasn't to worried about it. In my case I never seemed to lose anything, just an annoyance since I had to reboot after re-enabling.
  11. I find switching to i440fx from q35 the pci structure doesn't automatically fix itself up. In practice its easier for me to create a whole new VM than try to fix the xml.
  12. Hmmm, I thought the BIND method did use PCI addresses not device ids. That's what I entered anyway, since that was the format that a forum post referenced. Maybe that is why it didn't work for me.
  13. So I want to get access to dma-buf and it appears it requires opengl support to be enabled in the qemu build. How hard would it be to build a one with this feature enabled? I downloaded the source and started the make last night, and noticed it needed a lot of dependencies.
  14. I tried this method a few days ago as a part of troubleshooting something else and also found that it didn't work at all. vfio-pci-ids works but I thought it was perhaps binding to late.
  15. Second this, for same reason as Pauven. Its not as easy as it sounds though, because what happens when you change a file on the cache? How will that link up to the array?
  16. Another component I've found that is missing is unraid's qemu appears to not be compiled with opengl support. This isn't required to make gvt-g function, but there is a dmabuf function that requires it to link the VM display to the mediated card. You can use a client installed vnc, rdp...maybe looking glass, instead but its a real QoL improvement that isn't there. That said, given how unraid is built its not clear to me if openGL would actually work. The i915 driver must be loaded for this to work, but that might not be the only backend piece missing.
  17. Sorry, stock one. There are no nvidia drivers. I tried a number of things yesterday, OVMF VMs actually do work. I'm probably going to proceed with the dummy vm during i915 load. Its kludgy but if its stable I guess I'll be satisfied.
  18. I have a passed through ROM, although that didn't make a difference.
  19. I don't think that is it because its plugged into a monitor the whole time. It also worked reliably until I started this whole i915 adventure. Although maybe there is something going on there.
  20. So this isn't really about plex, but people doing quick sync on unraid have a similar use case to me. I've found that once I modprobe the i915 my nvidia card just gives a black screen when passed through. If I don't modprobe after boot it works fine. In my case the igpu is primary, nvidia is secondary. I found if I pass the nvidia through (so its in use) and then modprobe, things are OK. Based on that I added nvidia to vfio pci ids in syslinux.cfg, and confirmed vfio was in use at boot. The modprobed but it still broke nvidia passthrough! This is perplexing to me. i915 shouldn't be able to taint the nvidia card in my mine, since its not a compatible driver. I assumed all the displays were reignited or something when the driver loaded and this was tainting the nvidia card somehow, but if its bound to vfio I don't see how it should be able to get at it at all. I think I can workaround this with scripts and a dummy vm to "protect" the nvidia card from i915 but that seems ridiculous. Anyone else seeing this behavior or is it just me? I've only tried nvidia on seabios vms so maybe that is a component.
  21. Yeah, sorry I just noticed that thread. I was sure googling for the chipset and unraid would have shown that thread but google seems worse and worse these days.
  22. So every time I've gone looking for sata controllers there hasn't been much to find. We've had the asmedia 1061, the marvels that don't have a good reputation with unraid and then there's SAS controllers with flashed firmware that most people settle on. I've seen a newer version of the Asmedia but its still a 2 port version. I saw this pop up last month: https://www.amazon.com/dp/B07T3RMFFT https://www.amazon.com/dp/B07ST9CPND Some one in the reviews already claims to have tried it with Unraid. If you look the chip up on jmicron's site this is a Gen3 pci-e x 2 port SATA3 controller, giving you 5 ports. Seems like an interesting alternative in a land of currently sparse options. Pretty sure even if you installed these things in a 1x slot you'd have enough bandwidth to service 5 spinning rust drives. The question is if they are reliable.
  23. Yeah, it doesn't seem like there is a lot of interest I guess. That's kind of why I set out to try it myself. I actually didn't think I was going to get it to work at all, much less transfer the setup to unraid. I'd given up on the idea since coffeelake support was initially not going to happen and then finally showed up in 5.1 kernel. Next step is to mod my bios to support increased aperture sizes. That's a large problem for anyone running this on consumer motherboards, the mediated GPUs take their slice from the GPU aperture pie, not the shared variable memory. While changing the aperture size is a supported option, most motherboards seem to just lock it to 256MB. This means I can only create 2 of the smallest type of virtual GPU at the moment.