You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i trained a LoRA yesterday, and for no apparent reason, bitsandbytes showed up and complained that it couldn't find any of the cuda libraries, and the very famous issue called:
CUDA Setup failed despite GPU being available. Please run the following command to get more information:
python -m bitsandbytes
and very unfortunately, when i do execute the command python -m bitsandbytes, i get an almost identical wall of errors which actually calls the same string literal saying to execute the command python -m bitsandbytes, I don't want to get off on a tangent, but it really feels like bitsandbytes is mocking me when i execute that command and the best advice it has is to execute the same command that i just executed.
it's just not the right answer to change the LD_LIBRARY_PATH in .bashrc to fix a problem like this also. I don't want everything that uses bash to be looking in the same library locations. all software is liable to be using different versions, and software such as comfyui has the magic or talent to put the libraries it needs in a location where it can find them again.
I'm not astute enough to know if the shortcoming is at bitsandbytes or at kohya, but all too often I keep seeing the phrase bitsandbytes, and the same problems happening over and over for so many different users. so if you are friends with the dev of kohya could you advise them or could they advise you how to fix this kind of issue? it seems like a really elementary and basic problem of dependency management, which i presume is the entire reason for bitsandbytes in the first place.
so is bitsandbytes being mis-implemented by programs like Kohya or is bitsandbytes a bit of a diamond in the rough?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
i trained a LoRA yesterday, and for no apparent reason, bitsandbytes showed up and complained that it couldn't find any of the cuda libraries, and the very famous issue called:
and very unfortunately, when i do execute the command python -m bitsandbytes, i get an almost identical wall of errors which actually calls the same string literal saying to execute the command python -m bitsandbytes, I don't want to get off on a tangent, but it really feels like bitsandbytes is mocking me when i execute that command and the best advice it has is to execute the same command that i just executed.
it's just not the right answer to change the LD_LIBRARY_PATH in .bashrc to fix a problem like this also. I don't want everything that uses bash to be looking in the same library locations. all software is liable to be using different versions, and software such as comfyui has the magic or talent to put the libraries it needs in a location where it can find them again.
I'm not astute enough to know if the shortcoming is at bitsandbytes or at kohya, but all too often I keep seeing the phrase bitsandbytes, and the same problems happening over and over for so many different users. so if you are friends with the dev of kohya could you advise them or could they advise you how to fix this kind of issue? it seems like a really elementary and basic problem of dependency management, which i presume is the entire reason for bitsandbytes in the first place.
so is bitsandbytes being mis-implemented by programs like Kohya or is bitsandbytes a bit of a diamond in the rough?
Beta Was this translation helpful? Give feedback.
All reactions