• Unraid uses stubbed device


    ks2016
    • Solved Minor

    In VM settings, I set PCIe ACS override to BOTH.

    Then, I have stubbed 3 devices as preparation for passthrough.

     

    pci-stub.ids=10de:1c03,10de:10f1,1033:0194 

     

    > lspci -k

    01:00.0 VGA compatible controller: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] (rev a1)
            Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 6GB]
            Kernel driver in use: pci-stub
    01:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev a1)
            Subsystem: eVga.com. Corp. GP106 High Definition Audio Controller
            Kernel driver in use: pci-stub
    09:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 03)
            Kernel driver in use: pci-stub

     

    So far it seems the devices are stubbed.

     

    Issue:

    When Unraid starts it outputs the command line text on the stubbed graphics card and there is no output on the onboard one (non-stubbed).

     

    00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
            Subsystem: ASRock Incorporation HD Graphics 530
            Kernel modules: i915
     

    When I try to start a VM configured to use the discreet VGA there is only garbage on the screen.

     

     




    User Feedback

    Recommended Comments



    As mentioned ... it will use the onboard VGA if the HDMI cable is removed from the dedicated VGA at boot.

    Initially I though that it needs a cable in the onboard VGA (because I had only one cable and was switching between them). Once I attached a second cable I realized it is not the presence of the cable, but actually the absence that changes behavior.

    Link to comment

    Proof that stupidity is limitless (Asrock response bug report regarding this issue):

     

    Thank you for sharing the result.

    The BIOS has two different mode called Legacy and UEFI.

    In the new generation of the BIOS, it’s all support the UEFI now, Intel Z170 platform also using the UEFI BIOS.

    There still have a lot of older devices on the marketing.

    Therefore, the UEFI BIOS build an option CSM (compatibility support module) to support legacy devices.

    That’s why the CSM function will influence your system.

     

     

     

    Edited by ks2016
    Link to comment

    Ok, this is making more and more sense now.  So if a cable is connected to the discrete graphics card and you boot in UEFI, you can't use that discrete card with a VM because you get a garbled display.  But if you disconnect the cable from the discrete graphics card, wait for Unraid OS to boot, THEN plug in the cable to the discrete graphics card, everything works fine.

     

    Conversely, if you leave all cables connected but boot in NON-UEFI mode, everything works as expected as well.  This leads me to believe that this is a BIOS bug that only applies to UEFI boot mode.  For whatever reason, the BIOS isn't respecting the setting you are applying for forcing the primary graphics.

     

    As far as not buying ASRock products, I have to say, they do make rather good motherboards, but UEFI is just not as commonly used yet (especially in non-OEM products).  

    Link to comment

    Exactly as you describe it. However, when you get that response after a 2 page step-by-step explanation that should make an idiot understand it. .... It gets me out of my skin.

    Link to comment

    After more than 10 days of ping-pong with Asrock. There is finally some light at the end of the tunnel:

     

    Thank you so much for providing the video to us.

    Finally, we got the point and can see the same symptom in our lab.

    I reported this bug to our relate team.

    Edited by ks2016
    Link to comment

    They actually did fix it.

     

    I’m sorry for late reply.

    About the display under UEFI mode, we found other vendors have the same symptom too.

    After checking with the AMI, it’s a known behavior.

    However, our R&D team still helps to provide a solution for you.

    Please update the attached BETA BIOS P7.50G to check the result.

     

    I have tested the Asrock fix and confirmed it is working as expected.

    However, there seems to be another issue (this time with Unraid).

    I created a new report for that:

     

     

     

     

     

    Link to comment

    I must admit you were correct when you wrote:
    "I have to say, they do make rather good motherboards"

     

    After initial stubbornness, they did provide the fix quite fast.

    Link to comment



    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.