I just upgraded from a 1070 to a 2070 Super, when I booted into windows 10, I couldn't see the bios screen, or anything else until I get to the lockscreen which also seems to take longer than usual. This is fine, but the main problem is with Linux. I have an encrypted install of Arch Linux, and when I boot it up, I can't see any of the boot process, so I can't see when it says to enter my password to unlock my root partition. I also login from tty and I can't see this either. The keyboard does work and I can login, but I can't physically see anything until i3 starts.

 

How can I fix this?

tower-diagnostics-20200824-1113.zip

Edited August 24, 20205 yr by dGG2uA
spelling

22 minutes ago, dGG2uA said:

I just upgraded from a 1070 to a 2070 Super, when I booted into windows 10, I couldn't see the bios screen, or anything else until I get to the lockscreen which also seems to take longer than usual. This is fine, but the main problem is with Linux. I have an encrypted install of Arch Linux, and when I boot it up, I can't see any of the boot process, so I can't see when it says to enter my password to unlock my root partition. I also login from tty and I can't see this either. The keyboard does work and I can login, but I can't physically see anything until i3 starts.

 

How can I fix this?

Did you do any tweak to your VM? Upgrading from 1070 to 2070 is NOT a drop-in replacement.

 

Always a good idea to attach diagnostics to all your queries (Tools -> Diagnostics -> attach full zip file to your next post).

 

3 minutes ago, testdasi said:

Did you do any tweak to your VM? Upgrading from 1070 to 2070 is NOT a drop-in replacement.

 

Always a good idea to attach diagnostics to all your queries (Tools -> Diagnostics -> attach full zip file to your next post).

 

I havent changed anything else, only updated the GPU section and made sure its IOMMU group was isolated correctly. Should there be any other changes I need to make?

 

I've attached a diagnostic zip aswell.

12 minutes ago, dGG2uA said:

I havent changed anything else, only updated the GPU section and made sure its IOMMU group was isolated correctly. Should there be any other changes I need to make?

 

I've attached a diagnostic zip aswell.

The RTX has 4 functions, unlike the 1070 which only has 2 (GPU + HDMI audio).

You did the binding right but you missed the 2 USB controllers (08:00.2 and 08:00.3) in your xml.

4 minutes ago, testdasi said:

The RTX has 4 functions, unlike the 1070 which only has 2 (GPU + HDMI audio).

You did the binding right but you missed the 2 USB controllers (08:00.2 and 08:00.3) in your xml.

I have tried booting with, and without the 2 extra PCI devices attached to both VM's and the issue still persists. The current XML doesn't have those attached, right now im in my Windows VM without those attached and it's working.

35 minutes ago, dGG2uA said:

I have tried booting with, and without the 2 extra PCI devices attached to both VM's and the issue still persists. The current XML doesn't have those attached, right now im in my Windows VM without those attached and it's working.

It's not unusual to be able to boot into Windows without the 2 USB controllers but sooner or later it will stop working with error code 43. That has already been reported on the forum.

What you are doing is the software equivalent of splitting the card in half.

8 minutes ago, testdasi said:

It's not unusual to be able to boot into Windows without the 2 USB controllers but sooner or later it will stop working with error code 43. That has already been reported on the forum.

What you are doing is the software equivalent of splitting the card in half.

Well I've now passed thrm to both VM's, but I still have the problem of not seeing anything untill the Windows lock screen, and nothing till my window manager starts on Linux.

 

I can't seem to find any information on this for some reason.

14 minutes ago, dGG2uA said:

Well I've now passed thrm to both VM's, but I still have the problem of not seeing anything untill the Windows lock screen, and nothing till my window manager starts on Linux.

 

I can't seem to find any information on this for some reason.

Did you dump your own vbios? Wrong vbios has been known to cause funky issues, which probably is why you can't find any info.

53 minutes ago, testdasi said:

Did you dump your own vbios? Wrong vbios has been known to cause funky issues, which probably is why you can't find any info.

I didn't, I used one from TechPowerUp, I matched my card to the one on the site and used that one. I will double check I have the correct one and try again.

3 hours ago, testdasi said:

Did you dump your own vbios? Wrong vbios has been known to cause funky issues, which probably is why you can't find any info.

I have tried again with a different vbios, i checked the device ID and subsystem ID were identical and the issue still persists. Not really sure where to go next with this.

 

Also tried with no vbios at all, same problem.

17 hours ago, dGG2uA said:

I have tried again with a different vbios, i checked the device ID and subsystem ID were identical and the issue still persists. Not really sure where to go next with this.

 

Also tried with no vbios at all, same problem.

 

Let's try to fix your Windows VM since I'm more familiar with that.

 

From your diagnostics, you only have the RTX 2070 as the single graphics card in the system. Hence, I don't think you need the Unraid boot GUI / console (i.e. you access and configure Unraid remotely through the network). If it isn't the case then don't proceed as the tweaks below will cause you to require configuring Unraid remotely through the network with another device.

 

Now:

1. Update to 6.9.0-beta25. You are on 6.9.0-beta1 which is neither here nor there in terms of datedness. Just note that if you intend to revert back, you should not format any SSD with Unraid while in 6.9.0-beta25 because of the new 1MiB alignment, which isn't backward compatible with older versions.
   • 6.9.0-beta25 has vfio.pci config already built-in so no need to have that plugin anymore. Just go to Tools -> System Devices to check your vfio binding. If everything is fine then just uninstall the vfio-pci config.
2. Reboot Unraid and retest your VM with and without vbios. New kernel sometimes fixes funky issues. Obviously no need to proceed further if it works.

3. Boot Unraid in legacy mode (Main -> Flash, scroll to the bottom to check your "Server boot mode", if it's not "Legacy" then untick Permit UEFI boot mode, save, reboot and check again that it's in Legacy).

   • If it doesn't boot, you will need to change your motherboard BIOS settings e.g. changing boot order.

   • If it still doesn't boot then you need another PC to run the make_bootable .bat file (but I don't think you will need it if you created the USB stick the official way).

4. Retest your VM with and without vbios. Obviously no need to proceed further if it works.

5. Start a new template with the same settings but pick Q35-5.0 machine type and NO vbios rom. Do NOT autostart. Just save.

6. Now edit the newly created template in xml mode.

   • With vendor id, use exactly 12 characters e.g. 'a0123456789b'. Using 'none' may not work in some cases so I would suggest to use 12 characters instead.

   • Under <features> or above </features> add this. 

         <kvm>
           <hidden state='on'/>
         </kvm>
         <ioapic driver='kvm'/>

     (note the "or" above)

   • Do the multifunction edits (similar to your Arch Linux VM)

7. Test your VM to see if it fixes things, with and without vbios. Obviously no need to proceed further if it works.

8. Main -> Flash -> scroll to the Syslinux Configuration section. Add this between "append" and "initrd=/bzroot" only on the 2 lines below "label unRAID OS" and "label unRAID OS GUI Mode" (i.e. don't touch the Safe Mode lines).

   video=efifb:off

   Then save, reboot. You should see nothing after "Loading bzroot... OK".

   • In other words, after this step, you will only be able to interact with Unraid GUI / console through the network i.e. using another device with a browser e.g. a laptop / tablet / phone etc.

9. Test your VM again. Again with and without vbios rom. Obviously no need to proceed further if it works.

10. If it still doesn't work then you will need to borrow another graphics card to boot Unraid with this new card (i.e. NOT the 2070) in order to dump your own vbios rom file of the 2070. That's the only way to guarantee that you have the right vbios rom. Then test it again with this new vbios rom.

    • Also test whether your VM would work if Unraid boots with your borrowed graphics card. If that's the case, you probably have no choice but to buy a cheap low-end graphics card for Unraid to boot with in order for your VM to work properly with the 2070. e.g. the GT710 is a popular choice that goes for around £30/$30.

That's as much as I can help.

Edited August 25, 20205 yr by testdasi