bmaltais / kohya_ss

Apache License 2.0
9.54k stars 1.23k forks source link

ModuleNotFoundError: No module named 'bitsandbytes.cuda_setup.paths' #1704

Closed venomsoft1 closed 11 months ago

venomsoft1 commented 11 months ago

image

venomsoft1 commented 11 months ago

go to .\venv\scripts using cmd write "activate", then "pip install bitsandbytes-windows"

kyesniper commented 9 months ago

go to .\venv\scripts using cmd write "activate", then "pip install bitsandbytes-windows"

Oh my god thank you, this finally solved my problem.

Casey-bit commented 9 months ago

thank u so much!!!!!!! really helps me a lot

Lucfifael commented 9 months ago

go to .\venv\scripts using cmd write "activate", then "pip install bitsandbytes-windows"

You are the best, so quick and simple!

MOGRAINEREPORTS commented 9 months ago

go to .\venv\scripts using cmd write "activate", then "pip install bitsandbytes-windows"

For anyone still having this problem in the future, it definitely works. Hopefully its fixed in setup soon ;P

nikolatesla20 commented 8 months ago

ran into this problem today. The quoted fix got me past the problem, thanks.

wallypop commented 8 months ago

mine randomly broke today on windows, had to uninstall bitsandbytes-windows and then reinstall it, but I'm up and running again. For those not sure how to do that, open a command prompt in the kohya_ss directory, then:

cd ./venv/scripts/ ./activate pip uninstall bitsandbytes-windows pip install bitsandbytes-windows pip check

You should show clean, and should be able to run kohya_ss again.

github-gil commented 7 months ago

I see following errors when I try to execute "activate" or activate.bat "Install the latest PowerShell for new features and improvements! https://aka.ms/PSWindows

PS D:\Kohya-ss\kohya_ss\venv\Scripts> activate activate : The term 'activate' is not recognized as the name of a cmdlet, function, script file, or operable program. C heck the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1 + activate + ~~ + CategoryInfo : ObjectNotFound: (activate:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException Suggestion [3,General]: The command activate was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default. If you trust this command, instead type: ".\activate". See "get-help about_Command_Precedence" for more details. PS D:\Kohya-ss\kohya_ss\venv\Scripts> activate.bat activate.bat : The term 'activate.bat' is not recognized as the name of a cmdlet, function, script file, or operable pr ogram. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1 + activate.bat + ~~~~~~

if I run this as an administrator in standard command line, I see: D:\Kohya-ss\kohya_ss\venv>.\activate '.\activate' is not recognized as an internal or external command, operable program or batch file. or D:\Kohya-ss\kohya_ss\venv>activate 'activate' is not recognized as an internal or external command, operable program or batch file. or D:\Kohya-ss\kohya_ss\venv>activate.bat 'activate.bat' is not recognized as an internal or external command, operable program or batch file.

wallypop commented 7 months ago

I see following errors when I try to execute "activate" or activate.bat "Install the latest PowerShell for new features and improvements! https://aka.ms/PSWindows

PS D:\Kohya-ss\kohya_ss\venv\Scripts> activate activate : The term 'activate' is not recognized as the name of a cmdlet, function, script file, or operable program. C heck the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1 + activate + ~~ + CategoryInfo : ObjectNotFound: (activate:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException Suggestion [3,General]: The command activate was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default. If you trust this command, instead type: ".\activate". See "get-help about_Command_Precedence" for more details. PS D:\Kohya-ss\kohya_ss\venv\Scripts> activate.bat activate.bat : The term 'activate.bat' is not recognized as the name of a cmdlet, function, script file, or operable pr ogram. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1 + activate.bat + ~~~~~~ + CategoryInfo : ObjectNotFound: (activate.bat:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException"

if I run this as an administrator in standard command line, I see: D:\Kohya-ss\kohya_ss\venv>.\activate '.\activate' is not recognized as an internal or external command, operable program or batch file. or D:\Kohya-ss\kohya_ss\venv>activate 'activate' is not recognized as an internal or external command, operable program or batch file. or D:\Kohya-ss\kohya_ss\venv>activate.bat 'activate.bat' is not recognized as an internal or external command, operable program or batch file.

In a powershell window it needs to be ./activate from the webui\venv\Scripts\ directory. It looks like in your powershell window you didn't use the ./ and in the standard command line you weren't in the Scripts directory.

mAlazwari commented 7 months ago

go to .\venv\scripts using cmd write "activate", then "pip install bitsandbytes-windows"

You're a legend

github-gil commented 7 months ago

In a powershell window it needs to be ./activate from the webui\venv\Scripts\ directory. It looks like in your powershell window you didn't use the ./ and in the standard command line you weren't in the Scripts directory.

I don't have "webui" directory in my Kohya directory. The path to "scripts" directory is D:\Kohya-ss\kohya_ss\venv\scripts I launched CMD there and typed "activate" but it ended with 0 messages in CMD as you can see on printscreen. is it expected? image

wallypop commented 7 months ago

In a powershell window it needs to be ./activate from the webui\venv\Scripts\ directory. It looks like in your powershell window you didn't use the ./ and in the standard command line you weren't in the Scripts directory.

I don't have "webui" directory in my Kohya directory. The path to "scripts" directory is D:\Kohya-ss\kohya_ss\venv\scripts I launched CMD there and typed "activate" but it ended with 0 messages in CMD as you can see on printscreen. is it expected? image

Got my wires crossed with automatic1111. You already have it installed. Do a pip uninstall bitsandbytes-windows and then do a pip install bitsandbytes-windows