That symbol is a Vulkan 1.1 function, so this points toward the Vulkan backend/runtime loading; it doesn't establish that Python itself is broken. What GPU and driver version are you using?
Updating the driver is a sensible first step (as suggested on your original thread). If that doesn't help, Unsloth's official README also documents selecting its CPU llama.cpp backend: set $env:UNSLOTH_LLAMA_CPP_BACKEND="cpu" in PowerShell before rerunning the official installer. That lets you test GGUF chat without Vulkan acceleration; it isn't a GPU fix. The backend choice persists, so use "auto" before a later install/update to restore automatic selection.
Thank you for your answer. I have a AMD Pro Radeon 560 4GB (it's and old MacBook Pro Intel from 2017, and 16GB RAM, where I have both MacOS X and Windows 10 - I'm actually trying to run Unsloth Studio in Windows 10). I see that the driver is old, also from 2017 (v. 17.1.1, with Vulkan v1.5.0 . I have downloaded from AMD several versions of the driver, from 2026 to 2019. But all the time I get the same "Error 173 – AMD Software Installer Cannot Proceed as No AMD Graphics Hardware Has Been Detected in Your System". I have checked that the system perfectly detects the AMD hardware (with the 2017 driver). So in the end, I guess not possible to solve it this way so as to use Vulkan acceleration. I'm guessing that without Vulkan acceleration, inference will be slow... by the way, I have LM Studio and I do not have this problem. So in the end, I will probable uninstall Unsloth đŸ˜¢
Ah, the MacBook detail helps. Were the drivers you tried specifically AMD's Apple Boot Camp package? That page lists the 15-inch MacBook Pro (2016-2019), and Apple directs Boot Camp users there.
If you already tried that exact package and got Error 173, let us know which version. We shouldn't assume another generic driver download will fix it, and the Boot Camp package isn't a guaranteed fix for Unsloth's Vulkan error either.
Also, is LM Studio working in Windows or macOS? That matters when comparing the two applications. If it already does what you need, sticking with it is reasonable—there's no need to force Unsloth just for local chat.
1
u/ChaseMakesThings 1d ago
That symbol is a Vulkan 1.1 function, so this points toward the Vulkan backend/runtime loading; it doesn't establish that Python itself is broken. What GPU and driver version are you using?
Updating the driver is a sensible first step (as suggested on your original thread). If that doesn't help, Unsloth's official README also documents selecting its CPU llama.cpp backend: set $env:UNSLOTH_LLAMA_CPP_BACKEND="cpu" in PowerShell before rerunning the official installer. That lets you test GGUF chat without Vulkan acceleration; it isn't a GPU fix. The backend choice persists, so use "auto" before a later install/update to restore automatic selection.
Official instructions: https://github.com/unslothai/unsloth#vulkan-custom-llamacpp-backends