• [6.6.1] AMD Reboot bug

    J89eu

    By J89eu

      • Retest Minor

    Hi all

     

    This issue has been discussed on and off around the forum but it doesn't seem anyone has made an actual bug report post so here we go.

     

    Essentially the issue goes as follows, you pass through an AMD GPU, in my case a Vega 56 and then whenever you shutdown or reboot the VM, it will not turn back on until the unRAID system has been fully rebooted.

     

    Now looking around the forums it appears that the VM or unRAID doesn't release the GPU when the host reboots, this does tie in with what I have experienced as my GPU has a "tachometer" that shows the live GPU utilisation by way of LEDs that illuminate increasingly. If I boot unRAID up and do not turn on the VM, there are no LEDs illuminated, showing it's not being used at all, if I then turn on the VM and it sits idle, I have a single LED illuminated. If I then shut it down that LED stays illuminated, to me, showing it's still being held somewhere in the system. I then reboot the whole server and then no LEDs are present and I can power up the VM fine.

     

    This is obviously rather annoying as ANY reboot of the VM, for updates, driver installs etc, result in the whole server needing a bounce.

     

    So what can we do to resolve this? I was hoping that the new linux kernel would help out with this but seemingly no changes!

     

    Here is my XML and diagnostics  

    <?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm' id='1'>
  <name>Pluto</name>
  <uuid>0adf4fd5-0b47-d431-1345-cedc9c73294d</uuid>
  <metadata>
    <vmtemplate xmlns="unraid" name="Windows 7" icon="windows7.png" os="windows7"/>
  </metadata>
  <memory unit='KiB'>8388608</memory>
  <currentMemory unit='KiB'>8388608</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>5</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='1'/>
    <vcpupin vcpu='1' cpuset='2'/>
    <vcpupin vcpu='2' cpuset='3'/>
    <vcpupin vcpu='3' cpuset='4'/>
    <vcpupin vcpu='4' cpuset='5'/>
  </cputune>
  <resource>
    <partition>/machine</partition>
  </resource>
  <os>
    <type arch='x86_64' machine='pc-i440fx-3.0'>hvm</type>
    <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
    <nvram>/etc/libvirt/qemu/nvram/0adf4fd5-0b47-d431-1345-cedc9c73294d_VARS-pure-efi.fd</nvram>
  </os>
  <features>
    <acpi/>
    <apic/>
    <hyperv>
      <relaxed state='on'/>
      <vapic state='on'/>
      <spinlocks state='on' retries='8191'/>
      <vendor_id state='on' value='none'/>
    </hyperv>
  </features>
  <cpu mode='host-passthrough' check='none'>
    <topology sockets='1' cores='5' threads='1'/>
  </cpu>
  <clock offset='localtime'>
    <timer name='hypervclock' present='yes'/>
    <timer name='hpet' present='no'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/local/sbin/qemu</emulator>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/isos/Windows 7 64bit Ultimate.iso'/>
      <backingStore/>
      <target dev='hda' bus='ide'/>
      <readonly/>
      <boot order='2'/>
      <alias name='ide0-0-0'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/isos/virtio-win-0.1.141-1.iso'/>
      <backingStore/>
      <target dev='hdb' bus='ide'/>
      <readonly/>
      <alias name='ide0-0-1'/>
      <address type='drive' controller='0' bus='0' target='0' unit='1'/>
    </disk>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <alias name='usb'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <alias name='usb'/>
      <master startport='0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci2'>
      <alias name='usb'/>
      <master startport='2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci3'>
      <alias name='usb'/>
      <master startport='4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pci-root'>
      <alias name='pci.0'/>
    </controller>
    <controller type='ide' index='0'>
      <alias name='ide'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <alias name='virtio-serial0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:1b:5b:a6'/>
      <source bridge='br0'/>
      <target dev='vnet0'/>
      <model type='virtio'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </interface>
    <serial type='pty'>
      <source path='/dev/pts/0'/>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
      <alias name='serial0'/>
    </serial>
    <console type='pty' tty='/dev/pts/0'>
      <source path='/dev/pts/0'/>
      <target type='serial' port='0'/>
      <alias name='serial0'/>
    </console>
    <channel type='unix'>
      <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-1-Pluto/org.qemu.guest_agent.0'/>
      <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/>
      <alias name='channel0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='tablet' bus='usb'>
      <alias name='input0'/>
      <address type='usb' bus='0' port='4'/>
    </input>
    <input type='mouse' bus='ps2'>
      <alias name='input1'/>
    </input>
    <input type='keyboard' bus='ps2'>
      <alias name='input2'/>
    </input>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>
      </source>
      <boot order='1'/>
      <alias name='hostdev0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
      </source>
      <alias name='hostdev1'/>
      <rom file='/mnt/user/isos/Powercolor.RXVega56.8176.170730.rom'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x09' slot='0x00' function='0x0'/>
      </source>
      <alias name='hostdev2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x03' slot='0x00' function='0x1'/>
      </source>
      <alias name='hostdev3'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x0424'/>
        <product id='0x2228'/>
        <address bus='1' device='8'/>
      </source>
      <alias name='hostdev4'/>
      <address type='usb' bus='0' port='1'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x1e7d'/>
        <product id='0x2dcd'/>
        <address bus='1' device='3'/>
      </source>
      <alias name='hostdev5'/>
      <address type='usb' bus='0' port='2'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x2516'/>
        <product id='0x0004'/>
        <address bus='1' device='4'/>
      </source>
      <alias name='hostdev6'/>
      <address type='usb' bus='0' port='3'/>
    </hostdev>
    <memballoon model='virtio'>
      <alias name='balloon0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/>
    </memballoon>
  </devices>
  <seclabel type='dynamic' model='dac' relabel='yes'>
    <label>+0:+100</label>
    <imagelabel>+0:+100</imagelabel>
  </seclabel>
</domain>

     

    atlas-diagnostics-20180925-1006.zip

    Go to reports Stable Releases

    User Feedback

    Recommended Comments

    bastl

    I remember that bug also appeared on AMD systems and was fixed for most people by updating the kernel + BIOS update. I think 4.16 or 4.17 fixed it. Unraid 6.6 is on kernel 4.18 now. You might check, if there is a newer BIOS available. Yours is from 2017 and i guess there will be lots of updates for your board.

    • Upvote 1
    Link to comment
    J89eu

    Just updated the BIOS and now the server is boot looping straight after loading /bzroot shows OK... 

     

    It boots fine WITH GUI but not without! Safe mode doesn't with without the GUI either 

     

    I also cannot start my VM with either my soundcard or my GPU passed through, though this may be a knock on effect of the above? The error I get is:


    internal error: unknown pci source type 'vendor'

     

    Here's my latest diagnostics 

    atlas-diagnostics-20180925-1848.zip

    Edited by J89eu
    Link to comment
    phbigred

    I had something similar with my VM after the upgrade. Unassigned devices passed through other than VNC. Started vm, stopped vm, reassigned and everything started working again. Worth a shot.

    Link to comment
    J89eu
    5 hours ago, limetech said:

    I also suggest rebooting in 'safe mode' just to rule out plugins which may be clobbering newer packages with older ones.

    Hi, this doesn't work, I can only boot into safe mode with GUI or nornal mode with GUI. This would tell me it's not a plugin issue I'd think?

    8 hours ago, phbigred said:

    I had something similar with my VM after the upgrade. Unassigned devices passed through other than VNC. Started vm, stopped vm, reassigned and everything started working again. Worth a shot.

    I've tried this but cannot reassign any passed through device. No matter what I select I get the unknown vendor issue 

    Link to comment
    bastl

    @J89eu You passthrough your UPS (Cyber Power System, Inc. CP1500 AVR UPS) to the VM right? The last libvirt logs showing that a USB device can't be found. Looks like your UPS isn't recognized bei UNRAID or is not connected. For me VMs wont start if i passthrough a USB mouse or keyboard for example that aren't connected.

    Link to comment
    J89eu
    On 9/26/2018 at 2:26 AM, bastl said:

    @J89eu You passthrough your UPS (Cyber Power System, Inc. CP1500 AVR UPS) to the VM right? The last libvirt logs showing that a USB device can't be found. Looks like your UPS isn't recognized bei UNRAID or is not connected. For me VMs wont start if i passthrough a USB mouse or keyboard for example that aren't connected.

    Hi, I've tried it with and without and still the same :( I don't actually want it passed through 

    Link to comment
    bastl

    Did you tried to recreate the VM from scratch? @J89eu Add a new VM and configure everything as before with the GUI? Don't copy paste your old XML settings into it. Set up your core pinnings, amount of RAM and the GPU to passthrough.

    Link to comment
    J89eu

    I have just tried that and I can create it just fine but when I tried to add the XML for my NVME drive it gave me an error so I thought I'd just add a normal disk through unraid rather than passing through and I get the same error which is:

     

    Unsupported configuration: per-device boot elements cannot be used together with os/boot elements

     

    Any ideas?

    Link to comment
    bastl

    Do you use the old method passthing through the NVME controller and using a clover image? Still works for me as it's shown in SpaceInvaders Video. Can you post the XML throwing out that error?

    Link to comment
    J89eu

    I'm just passing it through with the XML as I found the clover image method to give me some weird lags in games. Here's the XML

      

    <?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm'>
  <name>Windows 10</name>
  <uuid>f7924a7b-24f4-a50f-9c47-8bca810aa128</uuid>
  <metadata>
    <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>
  </metadata>
  <memory unit='KiB'>4194304</memory>
  <currentMemory unit='KiB'>4194304</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>5</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='1'/>
    <vcpupin vcpu='1' cpuset='2'/>
    <vcpupin vcpu='2' cpuset='3'/>
    <vcpupin vcpu='3' cpuset='4'/>
    <vcpupin vcpu='4' cpuset='5'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-i440fx-3.0'>hvm</type>
    <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
    <nvram>/etc/libvirt/qemu/nvram/f7924a7b-24f4-a50f-9c47-8bca810aa128_VARS-pure-efi.fd</nvram>
    <boot dev='hd'/>
  </os>
  <features>
    <acpi/>
    <apic/>
    <hyperv>
      <relaxed state='on'/>
      <vapic state='on'/>
      <spinlocks state='on' retries='8191'/>
      <vendor_id state='on' value='none'/>
    </hyperv>
  </features>
  <cpu mode='host-passthrough' check='none'>
    <topology sockets='1' cores='5' threads='1'/>
  </cpu>
  <clock offset='localtime'>
    <timer name='hypervclock' present='yes'/>
    <timer name='hpet' present='no'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/local/sbin/qemu</emulator>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>
      </source>
      <boot order='1'/>
      <alias name='hostdev3'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/>
    </hostdev>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/isos/virtio-win-0.1.141-1.iso'/>
      <target dev='hdb' bus='ide'/>
      <readonly/>
      <address type='drive' controller='0' bus='0' target='0' unit='1'/>
    </disk>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <master startport='0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci2'>
      <master startport='2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci3'>
      <master startport='4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pci-root'/>
    <controller type='ide' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:66:14:08'/>
      <source bridge='br0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='unix'>
      <target type='virtio' name='org.qemu.guest_agent.0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
      </source>
      <rom file='/mnt/user/isos/Powercolor.RXVega56.8176.170730.rom'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x09' slot='0x00' function='0x0'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x03' slot='0x00' function='0x1'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x1e7d'/>
        <product id='0x2dcd'/>
      </source>
      <address type='usb' bus='0' port='1'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x2516'/>
        <product id='0x0004'/>
      </source>
      <address type='usb' bus='0' port='2'/>
    </hostdev>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
    </memballoon>
  </devices>
</domain>


     

    Edited by J89eu
    Link to comment
    bastl

    EDIT:

     

    Remove the "<boot dev='hd'/>" part only in your xml and try if that fixes it. 

      <os>
    <type arch='x86_64' machine='pc-i440fx-3.0'>hvm</type>
    <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
    <nvram>/etc/libvirt/qemu/nvram/f7924a7b-24f4-a50f-9c47-8bca810aa128_VARS-pure-efi.fd</nvram>
    <boot dev='hd'/>
  </os>

    EDIT END

     

     

     

    @J89eu

    If i use this xml i get the same error

    error.JPG.60b58dd71c12735dbb1eccd3fd9b90f6.JPG

     

    Removing the following part removes that error for me. I guess thats the part you added to passthrough your NVME.

    error2.JPG.374924ca987316719f2b92ac63b5e6f7.JPG

     

    Can you try to passthrough your NVME like i did with my second SSD.

      

        <disk type='block' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source dev='/dev/disk/by-id/ata-Samsung_SSD_850_EVO_1TB_S2RFNX0J606029L'/>
      <backingStore/>
      <target dev='hdd' bus='virtio'/>
      <alias name='virtio-disk3'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </disk>

     

    Edited by bastl
    Link to comment
    J89eu

    Ok your edit got the VM up and running, sadly the AMD reboot bug still persists with the latest BIOS update.. And to add to that I now have that bug with not being able to boot the host without using the GUI mode! I'll update to 6.6.1 and see if that fixes the second issue perhaps...

    Link to comment
    bastl

    Can you post your Syslinux configuration? Click on Main than flash and scroll down. I bet there is an extra parameter for GUI boot in that config which is missing for the non gui boot entry ;)

    Edited by bastl
    Link to comment
    J89eu

    Here we go

     

      

    default menu.c32
menu title Lime Technology, Inc.
prompt 0
timeout 50
label unRAID OS
  menu default
  kernel /bzimage
  append pcie_acs_override=downstream initrd=/bzroot
label unRAID OS GUI Mode
  kernel /bzimage
  append pcie_acs_override=downstream initrd=/bzroot,/bzroot-gui
label unRAID OS Safe Mode (no plugins, no GUI)
  kernel /bzimage
  append pcie_acs_override=downstream initrd=/bzroot unraidsafemode
label unRAID OS GUI Safe Mode (no plugins)
  kernel /bzimage
  append pcie_acs_override=downstream initrd=/bzroot,/bzroot-gui unraidsafemode
label Memtest86+
  kernel /memtest

     

    Edited by J89eu
    Link to comment
    bastl

    Damn. Now i have no idea why your system only starts up in Gui mode. You can test to put your Vega in another PCIE slot. It's in the first one i guess. Your IOMMU groups might change and you have to reassign the card to the VM. Another idea, people reported if you don't passthrough the audio part of the card to the VM the reset bug is gone. Maybe worth a test. Also the next kernel version 4.19 will have a fix for that bug. Check this forum thread 

    There might be also a workaround for the AMD reset bug worth checking out. I can't test it cause i have no vega card but it looks promissing. Reseting the card inside the VM before shuting it down via script should work however windows update and the automated restart after it might ignore the script. Keep that in mind. Check out that step-by-step guide, it might be a good solution till unraid switched to kernel 4.19

    https://forum.level1techs.com/t/linux-host-windows-guest-gpu-passthrough-reinitialization-fix/121097

     

    Link to comment
    J89eu

    Cheers, I'll try that though it has been working for months in the slot it's in! 

     

    Interestingly someone else is now having the same issue with the GUI boot issue:

     

    Let's hope 4.19 kernel comes soon :P

     

    Appreciate your help by the way. Thanks.

    Edited by J89eu
    Link to comment
    limetech
    8 hours ago, J89eu said:

    Let's hope 4.19 kernel comes soon

    Checked 4.18.11 and above mentioned patch is not in that release.

     

    Illustrates the two-edge sword: we have to keep up with kernel releases in order to get the latest device support and other device-related fixes; however, it also means we get the latest regressions introduced into the kernel which no one has previously reported.  That's the price we pay...

    Link to comment
    T65

    Tested with an AMD R9 Nano ( GPU + Audio Passthrough ) and the new Unraid 6.6.2 version. So far everything looks good, but I will test this bug with an AMD RX 56 Nano this weekend.

    • Like 1
    Link to comment
    Tower_Of_Power
    On 10/18/2018 at 7:45 PM, T65 said:

    Tested with an AMD R9 Nano ( GPU + Audio Passthrough ) and the new Unraid 6.6.2 version. So far everything looks good, but I will test this bug with an AMD RX 56 Nano this weekend.

    Novice here.. I've been trying multiple VM setups only to get stuck at boot.. I want to run Ubuntu on my R9 Nano as I'm already running Win10 on my 2nd card, a Vega 64... if you still got setup, I would appreciate any advice on setup you have that I may be missing.. TIA

    Link to comment
    T65
    On 7/17/2019 at 7:49 AM, Tower_Of_Power said:

    Novice here.. I've been trying multiple VM setups only to get stuck at boot.. I want to run Ubuntu on my R9 Nano as I'm already running Win10 on my 2nd card, a Vega 64... if you still got setup, I would appreciate any advice on setup you have that I may be missing.. TIA

    Sorry, but I haven't found a solution yet either.

    Link to comment
    Tower_Of_Power
    13 hours ago, T65 said:

    Sorry, but I haven't found a solution yet either.

    thx.. i got my Vega 64 to work relatively stable... i guess i'll search the used market for a NVDA card to replace my Nano and experiment from there.

    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.