upscayl / upscayl

πŸ†™ Upscayl - #1 Free and Open Source AI Image Upscaler for Linux, MacOS and Windows.

Home Page:https://upscayl.org

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

vkEnumeratePhysicalDevices failed 5 🚨 Error: Invalid GPU Device

Garou312 opened this issue Β· comments

Checklist

  • I have tried ALL of the steps mentioned in the troubleshooting guide.
  • I have searched for this in the issues tab.
  • My error involves vkEnumeratePhysicalDevices or vkCreateInstance, which means I should ignore the other issues and file this one despite the last checkbox.

Describe the Bug

I Just shifted to windows 11 canary build but upscayl now doesn't seem to recognize the dGPU, before this I was in windows 10 and Upscayl was working fine, I also tried older version but it also didn't work, I shared the screenshot

To Reproduce

β€Ž

Upscayl Version (or commit hash)

2.11.0

Platform

Windows

OS Version

Windows 11 24H2 Canary Build

GPU Name

RTX 3060 laptop GPU

Expected Behavior

I think it is not recognizing Dedicated GPU

Screenshots

The first one is 2.11.0 and second one is 2.9.1

Logs

βš™οΈ Getting saveImageAs from localStorage:  png
βš™οΈ Getting model from localStorage:  {"label":"General Photo (Real-ESRGAN)","value":"realesrgan-x4plus"}
βš™οΈ Setting gpuId to empty string
πŸ”€ Setting model to 
πŸ”€ Setting model to realesrgan-x4plus
βš™οΈ Getting saveImageAs from localStorage:  png
βš™οΈ Getting model from localStorage:  {"label":"General Photo (Real-ESRGAN)","value":"realesrgan-x4plus"}
βš™οΈ Setting gpuId to empty string
βš™οΈ Getting saveImageAs from localStorage:  png
βš™οΈ Getting model from localStorage:  {"label":"General Photo (Real-ESRGAN)","value":"realesrgan-x4plus"}
βš™οΈ Setting gpuId to empty string
πŸ”€ Setting model to 
πŸ”€ Setting model to realesrgan-x4plus
πŸ”„ Resetting image paths
πŸŽ’ BACKEND REPORTED:  πŸ–ΌοΈ Updating Image Path:  C:\Users\Suryansh\Downloads\Minish cap 3d build\download (25).png
πŸ–Ό Selected Image Path:  C:\Users\Suryansh\Downloads\Minish cap 3d build\download (25).png
πŸ“ Selected Image Directory:  C:\Users\Suryansh\Downloads\Minish cap 3d build
πŸ–Ό imagePath:  C:\Users\Suryansh\Downloads\Minish cap 3d build\download (25).png
πŸ”€ Extension:  png
πŸŽ’ BACKEND REPORTED:  πŸ“„ Selected File Path:  C:\Users\Suryansh\Downloads\Minish cap 3d build\download (25).png
πŸ”„ Resetting Upscaled Image Path
🏁 UPSCAYL
πŸŽ’ BACKEND REPORTED:  βœ… Upscayl Variables:  {"model":"realesrgan-x4plus","gpuId":null,"saveImageAs":"png","inputDir":"C:\\Users\\Suryansh\\Downloads\\Minish cap 3d build","fileNameWithExt":"download (25).png","outputDir":"C:\\Users\\Suryansh\\Downloads\\Minish cap 3d build","outFile":"C:\\Users\\Suryansh\\Downloads\\Minish cap 3d build\\download (25)_upscayl_16x_realesrgan-x4plus.png","fileName":"download (25)","scale":"16","compression":"0","customWidth":"","useCustomWidth":false,"tileSize":null}
πŸŽ’ BACKEND REPORTED:  πŸ“’ Upscayl Command:  -i,C:\Users\Suryansh\Downloads\Minish cap 3d build\download (25).png,-o,C:\Users\Suryansh\Downloads\Minish cap 3d build\download (25)_upscayl_16x_realesrgan-x4plus.png,-s,16,-m,D:\upscayl-2.11.0-win\resources\models,-n,realesrgan-x4plus,-f,png,-c,0
πŸŽ’ BACKEND REPORTED:  πŸ‘Ά Updating Child Processes:  {"binary":"D:\\upscayl-2.11.0-win\\resources\\bin\\upscayl-bin","args":["D:\\upscayl-2.11.0-win\\resources\\bin\\upscayl-bin","-i","C:\\Users\\Suryansh\\Downloads\\Minish cap 3d build\\download (25).png","-o","C:\\Users\\Suryansh\\Downloads\\Minish cap 3d build\\download (25)_upscayl_16x_realesrgan-x4plus.png","-s","16","-m","D:\\upscayl-2.11.0-win\\resources\\models","-n","realesrgan-x4plus","-f","png","-c","0"]}
πŸŽ’ BACKEND REPORTED:  πŸ›‘ Updating Stopped:  false
πŸŽ’ BACKEND REPORTED:  vkEnumeratePhysicalDevices failed 5
🚨 Error: Invalid GPU Device

πŸ”„ Resetting image paths
🚧 UPSCAYL_PROGRESS:  vkEnumeratePhysicalDevices failed 5
🚨 Error: Invalid GPU Device

βš™οΈ Getting saveImageAs from localStorage:  png
βš™οΈ Getting model from localStorage:  {"label":"General Photo (Real-ESRGAN)","value":"realesrgan-x4plus"}
βš™οΈ Setting gpuId to empty string

Please follow the troubleshooting steps. Also, this is a duplicate of #735 so I'm closing this but we can continue the discussion there.

Please follow the troubleshooting steps. Also, this is a duplicate of #735 so I'm closing this but we can continue the discussion there.

I have done troubleshooting but can't see any GPU numbers in logs and I also one by one entered 0,1,2 in GPU ID but still not working

@NayamAmarshe This error is usually different for each system and shouldn't be closed as a duplicate.

Does VulkanCapsViewer report capabilities?

@NayamAmarshe This error is usually different for each system and shouldn't be closed as a duplicate.

Does VulkanCapsViewer report capabilities?

The error is the same in the issue I linked. I see no reason to create another thread for it. OP can simply find support on the other issue.

Even if the system is different, the error code is exactly the same. It shouldn't require another thread imho, otherwise, we'll keep having to create a new issue for each configuration for the exact same error and error code.

The error code basically means that something is wrong with the drivers or hardware. The error code being the same doesn't mean much.

The error code basically means that something is wrong with the drivers or hardware. The error code being the same doesn't mean much.

I still don't see why one can't find support in the other thread by mentioning the same details in a comment, because that's what issues are for. We want to avoid duplicate vulkan issues, it's better to have everyone with the same problem in a single thread so that we may find a solution.

Another reason was that using CPUs also often causes this, and referring people to the checklist, which prevents most unneeded posts. But there's now a troubleshoot button in the dialog box, so maybe you're right.

The error is the same in the issue I linked. I see no reason to create another thread for it. OP can simply find support on th
Even if the system is different, the error code is exactly the same. It shouldn't require another thread imho, otherwise, we'll keep having to create a new issue for each configuration for the exact same error and error code.

This is a different issue and you clearly didn't read my reply and if you read, then it blew over your head, I did everything written in troubleshoot, changed GPU ID and also sent logs but you didn't read it.
If you don't have to help, then don't suck time of anyone, end support for this thing.

The error is the same in the issue I linked. I see no reason to create another thread for it. OP can simply find support on th
Even if the system is different, the error code is exactly the same. It shouldn't require another thread imho, otherwise, we'll keep having to create a new issue for each configuration for the exact same error and error code.

This is a different issue and you clearly didn't read my reply and if you read, then it blew over your head, I did everything written in troubleshoot, changed GPU ID and also sent logs but you didn't read it. If you don't have to help, then don't suck time of anyone, end support for this thing.

It's not a different issue, afaics. Pretty much the same error:

🐞 BACKEND REPORTED:  image upscayl:  vkEnumeratePhysicalDevices failed 5
invalid gpu device

This happens due to misconfigured device drivers. If you've really tried everything mentioned in the troubleshooting, I'm sorry I can't really suggest anything else. I cannot reproduce your machine configuration and then the bug, the troubleshooting in these cases depends on the one reporting the issue.

I apologize for the other irrelevant 'issue management' comments in this thread though.

We can track in #735, the logs don't differ much. It's not like you can assume #735's reporter didn't try the troubleshooting steps either.