GPTQ-for-LLaMa VS one-click-installers

git clone https://github.com/oobabooga/GPTQ-for-LLaMa

If you're using the model directly from ehartford, that one hasn't been quantized. Try using the GPTQ quantized version here, and use this fork of GPTQ-for-LLaMa. Load in 4-bit with --wbits 4

This worked for me on Ubuntu. If you want to use the CUDA branch instead of triton, do the same steps except clone this GPTQ-for-LLaMa fork and run python setup_cuda.py install

If you don't have triton and you use AutoGPTQ you're gonna notice a huge slow down compared to the old GPTQ-for-LLaMA cuda branch. For me AutoGPTQ gives me a whopping 1 token per second compared to the old GPTQ that gives me a decent 9 tokens per second.. both times I used a same sized model. (I think the slowdown is due to AutoGPTQ using the newer cuda branch which is much slower than the old one)

Are you using a later version of GPTQ-for-LLaMa? If so, go to ooba's CUDA fork (https://github.com/oobabooga/GPTQ-for-LLaMa). That's what I made it in and it definitely works with that. And that's what's included in the one-click-installers.

This usually happens when using models that conflict with your GPTQ installation. You should be using this fork: https://github.com/oobabooga/GPTQ-for-LLaMa. If you did the manual installation wrong, use the one click installer instead.

cd text-generation-webui # wherever you have it installed mkdir -p repositories cd repositories git clone https://github.com/oobabooga/GPTQ-for-LLaMa -b cuda GPTQ-for-LLaMa cd GPTQ-for-LLaMa python setup_cuda install

I'm on GPTQ for LLaMA folder under repositories says it's pointed at https://github.com/oobabooga/GPTQ-for-LLaMa.git. But I've run through the instructions and also applied the monkey patch to train and apply 4 bit lora which may come into play. No idea.

git clone https://github.com/oobabooga/GPTQ-for-LLaMa.git -b cuda

AMD does not offer installation options for ROCm on Windows. I'm not familiar with the workarounds to make it work; if you find a solution, you can contribute it to https://github.com/oobabooga/one-click-installers/

Running start_windows.bat should take care of everything.

Had the same issue, turns out I was using an old 1 click installer / updater, you need to use https://github.com/oobabooga/one-click-installers and reinstall everything from scratch

Are you sure you're looking at the right folder? start_windows.bat is there. It's listed in the source code: https://github.com/oobabooga/one-click-installers

one-click-installers/INSTRUCTIONS.TXT

https://github.com/oobabooga/one-click-installers/issues/56 they explain it over here.

I solved this by adding the Individual components 2019 Windows 10 SDK, C++ CMake tools for Windows, and MSVC v142 - VS 2019 C++ build tools. See https://github.com/oobabooga/one-click-installers/issues/56

It appears one of the extensions isn't pre-compiled on install. I believe you have the same problem as listed here. https://github.com/oobabooga/one-click-installers/issues/56