HAMM3REXTREME
Can't run "./install.sh --amd for AMD"
How does this install.sh file compatible with Arch use? It literally have "sudo apt install" codes for the most important dependencies. I'm a slightly newcomer to the Linux and Arch community, so excuse me for my ignorance when i looked up to the code and can't see any arch fitting code alternative. I don't know If It's because of this (probably not) but I have faced with this error code when I try to execute the command "./install.sh --amd for AMD" and for extra; I have an RX 6900XT and run it on Arch Based OS (EndevourOS):
./install.sh --amd ─╯
[*] [.settings] file found, loading.
[*] Installing [multitail].
[sudo] password for abgungas:
sudo: apt: komut bulunamadı
sudo: apt: komut bulunamadı
[*] Installing [ComfyUI].
[*] [ComfyUI] installed.
[*] Creating [ComfyUI.service] file.
./install.sh: satır 94: /media/rizzo/DATA/ComfyUI-Installer/scripts/ComfyUI.service: Böyle bir dosya ya da dizin yok
cp: '/media/rizzo/DATA/ComfyUI-Installer/scripts/ComfyUI.service' durumlanamadı: Böyle bir dosya ya da dizin yok
[*] [Backup] directory not found, creating.
mkdir: `/media' dizini oluşturulamıyor: Erişim engellendi
mv: 'ComfyUI/web' durumlanamadı: Böyle bir dosya ya da dizin yok
mv: 'ComfyUI/user' durumlanamadı: Böyle bir dosya ya da dizin yok
mv: 'ComfyUI/output' durumlanamadı: Böyle bir dosya ya da dizin yok
mv: 'ComfyUI/models' durumlanamadı: Böyle bir dosya ya da dizin yok
mv: 'ComfyUI/input' durumlanamadı: Böyle bir dosya ya da dizin yok
mv: 'ComfyUI/custom_nodes' durumlanamadı: Böyle bir dosya ya da dizin yok
[*] [Backup] directory created.
[*] [ omfyUI/webm] directory moved to: [/media/rizzo/DATA/ai-stuff\web]
./install.sh: 169. satır: printf: \u için unicode rakamı eksik
[*] [ComfyUI/user] directory moved to: [/media/rizzo/DATA/ai-stuff\user]
[*] [ComfyUI/output] directory moved to: [/media/rizzo/DATA/ai-stuff\output]
[*] [ComfyUI/models] directory moved to: [/media/rizzo/DATA/ai-stuff\models]
[*] [ComfyUI/input] directory moved to: [/media/rizzo/DATA/ai-stuff\input]
[*] [ComfyUI/custom_nodes] directory moved to: [/media/rizzo/DATA/ai-stuff\custom_nodes]
ln: 'ComfyUI' sembolik bağı oluşturulamadı: Dosya var
ln: 'ComfyUI' sembolik bağı oluşturulamadı: Dosya var
ln: 'ComfyUI' sembolik bağı oluşturulamadı: Dosya var
ln: 'ComfyUI' sembolik bağı oluşturulamadı: Dosya var
ln: 'ComfyUI' sembolik bağı oluşturulamadı: Dosya var
ln: 'ComfyUI' sembolik bağı oluşturulamadı: Dosya var
[*] Installing [ComfyUI-Manager].
[*] [ComfyUI-Manager] installed.
[*] Installing [ComfyUIMini].
[*] [ComfyUIMini] installed.
[*] Creating [ComfyUIMini.service] file.
./install.sh: satır 140: /media/rizzo/DATA/ComfyUI-Installer/scripts/ComfyUIMini.service: Böyle bir dosya ya da dizin yok
cp: '/media/rizzo/DATA/ComfyUI-Installer/scripts/ComfyUIMini.service' durumlanamadı: Böyle bir dosya ya da dizin yok
Starting ComfyUI.service.'
Failed to start ComfyUI.service: Unit ComfyUI.service not found.
Starting ComfyUIMini.service.'
Failed to start ComfyUIMini.service: Unit ComfyUIMini.service not found.
chmod: '/media/rizzo/DATA/ComfyUI-Installer/scripts/*.sh' ögesine erişilemedi: Böyle bir dosya ya da dizin yok
chmod: '/media/rizzo/DATA/ComfyUI-Installer/ComfyUI/custom_nodes/ComfyUIMini/scripts/*.sh' ögesine erişilemedi: Böyle bir dosya ya da dizin yok
Finished!
To Launch ComfyUI manually, use: 'scripts/run_gpu.sh' or 'scripts/run_cpu.sh'
To Launch ComfyUIMini manually, use: 'ComfyUI/custom_nodes/ComfyUIMini/scripts/start.sh'
To start ComfyUI as systemd service, run: 'sudo systemctl start ComfyUI.service'
To start ComfyUIMini as systemd service, run: 'sudo systemctl start ComfyUIMini.service'
To enable ComfyUI service at boot, run: 'sudo systemctl enable ComfyUI.service'
To enable ComfyUIMini service at boot, run: 'sudo systemctl enable ComfyUIMini.service'
To view the logs of ComfyUI, run: 'multitail -f ComfyUI/user/comfyui.log'
To view the logs of ComfyUI, run: 'journalctl -f -u ComfyUI.service'
To view the logs of ComfyUIMini, run: 'journalctl -f -u ComfyUIMini.service'
Open a browser and go to: 'http://0.0.0.0:8188' for ComfyUI
Open a browser and go to: 'http://0.0.0.0:3000' for ComfyUIMini
./install.sh: satır 242: multitail: komut yok
Also, sorry for the language barrier. Thanks!
(I have installed git, venv, pip and other stuff and rocm too)
and seems nothing wrong with my ROCM according to test-rocm.py that I found on Github , the output:
Checking ROCM support...
GOOD: ROCM devices found: 2
Checking PyTorch...
GOOD: PyTorch is working fine.
Checking user groups...
GOOD: The user abgungas is in RENDER and VIDEO groups.
GOOD: PyTorch ROCM support found.
Testing PyTorch ROCM support...
Everything fine! You can run PyTorch code inside of:
---> AMD Ryzen 9 5950X 16-Core Processor
---> gfx1030
Sorry for the confusion, the main branch had recent contributions that added more features but also made it more system-specific (Ubuntu) . Since you have all the dependencies installed on your Arch system, try using the simple (original script) branch, which should just install ComfyUI.
git clone -b simple https://github.com/HAMM3REXTREME/ComfyUI-Installer && cd ComfyUI-Installer
./install-amd.sh
./menu-entry.sh # Optional
launch ComfyUI using: ./launch.sh
I will add a disclaimer so it's not confusing.
this should not be a problem anymore with my most recent changes (the ones I made after https://github.com/HAMM3REXTREME/ComfyUI-Installer/pull/12) if there is no .settings file present, it should ask the user now for where to install, what gpu to use and if you want to use systemd etc.. store that in a .settings file and then proceed to install.
however; if one creates a .settings file beforehand, i.e there is a .settings file present during first run, it should just use that and then proceed to install without any user input, making it a unattended non-interactive installation process.
this way it should work for the best of both situations in both of our debian/arch worlds.
sorry for causing any confusion.
If anyone but me can test and confirm that it works (apart from the tests I did on-my-machine), then this issue can be closed. let me know if anyone has any questions, suggestions or comments. id like to know, honestly, see if someone is familiar with the retropie-setup script, thats what I had initially in mind for this too, so I looked at that a while. I even made some script_modules for them in the past after researching on how they used dialog. this time I figured whiptail was a bit easier and just started coding.
I guess it can be expanded upon.. (make an actual main menu with sub-menu like "managing .settings" managing/activating the venv. handling installation, or updating. installing/cloning of custom_nodes upon installation either by providing a list of github urls and then handling the hassle and installation of their independent requirements. starting and stopping the services. etc..)