Jump to content

bamhm182

Members
 View Profile  See their activity

  • Posts

    67

  • Joined

  • Last visited

 Content Type 

Everything posted by bamhm182

  1. bamhm182
    My install has been booting just fine, and then I upgraded to 6.7.0-rc1 from 6.6.6 and am getting the following when I try to boot from any of my options: Loading /bzimage... ok Loading /bzroot... ok Loading /bzroot-gui... ok exit_boot() failed! efi_main() failed! I have moved my vfio-pci arguments over to the new config file, but other than that, I haven't touched anything since the last reboot. I'm on UEFI. Any ideas? I'm going to go remove that config file and see if that helps any. EDIT: It didn't change anything. Also, my default syslinux.cfg file entry is as follows: label unRAID... kernel /bzimage append pcie_acs_override=downstream initrd=/bzroot,/bzroot-gui I could probably roll back to 6.6.6 and be fine, but I'm going to take the time waiting to set up my bare metal hard drive. Let me know if there is anything you would like me to try. EDIT 2: I rolled back to 6.6.6 and as I predicted, everything was fine again. I then reinstalled 6.7.0-rc1 and it did the same thing. I made sure not to make any changes to syslinux.cfg or vfio-pci.cfg this time.
  2. bamhm182
    My install has been booting just fine, and then I upgraded to 6.7.0-rc1 from 6.6.6 and am getting the following when I try to boot from any of my options: Loading /bzimage... ok Loading /bzroot... ok Loading /bzroot-gui... ok exit_boot() failed! efi_main() failed! I have moved my vfio-pci arguments over to the new config file, but other than that, I haven't touched anything since the last reboot. I'm on UEFI. Any ideas? I'm going to go remove that config file and see if that helps any. EDIT: It didn't change anything. Also, my syslinux.cfg file entry is as follows: label unRAID... kernel /bzimage append pcie_acs_override=downstream initrd=/bzroot,/bzroot-gui
  3. bamhm182
    I didn't even catch that he probably just missed the 0. Haha. I thought he actually meant 6.7.9. Glad to hear it'll be released sooner than that. >_<
  4. bamhm182
    Changed Status to Solved
  5. bamhm182
    Will do. Thanks for all the help!
  6. bamhm182
    Been running my kernel for a few days with no issues. I'm going to close this. In other news, still can't get this card to work, I even installed Windows baremetal on a spare disk, got the card working there, then copied the disk to an img. I booted that and it still told me to reboot to finish the driver installation. I feel like the programmers put that in there instead of "it isn't working and we don't know why." I think I'm going to stop trying to get this to work with unRAID and just dual boot windows and unRAID. No fault to unRAID, just this crappy card. Keep up the great work!
  7. bamhm182
    Thanks for doing that! I'm beginning to think the card is garbage as well. I have a little mSATA drive I'm not using, I may install that and toss Windows on there just to give it one final go before I send it back to Amazon. I've just got one final question since I've been stuck on this for a few days. What's the proper way to extract and compile the bzroot file? All the information I can find suggests piping it from xzcat to cpio, but when I do that, xzcat complains about an invalid format. I was finally able to get it to do something with cpio -id < /boot/bzroot, but all that was extracted was a kernel folder. Is that all that's in there? As for compiling it, I never had any luck.
  8. bamhm182
    That is correct. The person who originally made the patch was using Arch, but he had a virtual machine running on Arch and ran into the same issues as we are running into now. Making these changes and a few in syslinux solved the reboot VM crash for him. He modified his sysconfig to look similar to the one I have set up here: label unRAID OS (Elgato Fix) kernel /bzimage-new append pcie_acs_override=downstream pci-stub.ids=<removed>,12ab:0380 vfio-pci.ids=12ab:0380 disable_idle_d3=1 initrd=/bzroot-new EDIT: Making progress! I just took a moment to step back and think about the steps and realized that this whole time I've been trying to compile both bzroot and bzimage, but I haven't really been doing anything to bzroot, but extracting and recompiling it (wrong, I might add). I was replacing bzroot for no reason, so I used the bzroot that came with unRAID and the bzimage that I have been compiling, low and behold, I CAN REBOOT! There are some issues with the card still, but I think they may not be related. It's just weird, it prompts me to reboot to finish installing the drivers, but when I reboot, that message doesn't go away and the card still doesn't work. I'm wondering if maybe Windows isn't shutting down cleanly...
  9. bamhm182
    Haha, that's true. That is the gist where I found the code, yes. I have been working on a script that checks the unRAID, Slackware and Kernel versions, then goes out and downloads the appropriate packages and files and follows similar steps to gfjardim's gist and the one on the wiki. Only problem is they're both pretty old and this is the first time I've ever tried to compile a kernel. I managed to get rid of most of the negative sounding things, except for what looks like a few warnings when running the make. I finally managed to get a bzimage and bzroot that look pretty similar to the bzroot and bzimage that come with unRAID, but it was late last night and I was unable to test it. With that, I haven't been able to verify that it fixes the problem just yet, but it worked for the Creator of that patch once he also made a few changes to syslinux.
  10. bamhm182
    I just bought an Elgato HD60 Pro and when I pass the card through to my Windows 10 VM, it crashes the entire server when I turn off/reboot the VM. It appears as though the issue is resolvable by inserting the following lines into a few kernel files. drivers/pci/quirks.c: DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_YYE, PCI_DEVICE_ID_YYE_MOZARD_395S, quirk_no_bus_reset); include/linux/pci_ids.h #define PCI_VENDOR_ID_YYE 0x12ab #define PCI_DEVICE_ID_YYE_MOZART_395S 0x0380 I have been working for a while to rebuild the kernel with this code and I think I've got it building now but all I really have to show for my work is a pissed off wife. I also know that all this work I'm doing will go away as soon as Unraid updates the kernel again, so I figured I would ask if there's any way the code could get added into the next release. Thanks and keep up the great work! EDIT: I don't know if this should be marked Minor or Urgent, sorry. It crashes the entire server forcing me to hold down the power to reboot it, which the side bar says is urgent, but it only affects people who are trying to use this capture card, so it doesn't seem like it's an urgent issue. Additionally, I'm trying to generate the diagnostics zip, but for some reason it is changing my page to the link it should be downloading from and not actually downloading anything. I confirmed that it is working on my other Unraid server (both on 6.6.6) and it generates the diagnostics zip without any problems. tardis-diagnostics-20190112-2028.zip
  11. bamhm182
    Anyone figure out how to get this working with a separate IP yet?
  12. bamhm182
    Upon reading through the rest of the posts, I decided it wasn't NEARLY secure enough. Now I just need to figure out the steps to have my cellphone's presence on the LAN prompt the server to request that I insert and touch my YubiKey U2F. If my phone is not present, the server wouldn't care about the YubiKey. Only after the YubiKey is inserted and verified, will the server care about its attached retinal and finger printer scanners, which are the final key to decrypting the first server. Now the only way to get anything off of there is to... Steal me as well? God forbid I need to ask someone to boot my servers while I'm out of town because of a power outage. Haha
  13. bamhm182
    Thanks for the info! I have been toying around with running 2 unRAID servers (One on a Dell R710, one on my primary Desktop w/ VM's getting passed hardware) and I took what you did and built upon it. We will call these servers U1 and U2. Both have a static IP and are plugged into a switch. U2 has a share named U1-key and U1 has a share named U2-key. Both have corresponding secure accounts. If both are on and I reboot U1, upon boot it reaches out to U2 and gets its key. If both are on and I reboot U2, it reaches out to U1 and gets its key. If both are off, I boot both and manually start the array on U2 (much faster boot time) and by the time U1 is up, it pulls its key from U2. Seems to be working well for me so far. Best of all, with this setup, if both are off (as would happen if someone walked off with my server rack), both keys are on encrypted drives, so the neither of them should be able to be booted without my key.
  14. bamhm182
    72 GB. Bought a Dell R710, 4GB sticks seemed to offer the most bang for the buck. Fully populated it.
×
×
  • Create New...