Flame 2026 - Linux - Error 1 on install

Hello

I am struggling to install Flame 2026 or 2025 linux on a ADSK sourced Rocky 9.5 system on a HP Z8 G4 with NVIDIA RTX 6000 Ada Generation. No funky installs ; DKU corresponds to the flame version. I have setup the BIOS as ADSK recommends.

And yet I never get past 5% of the install before the installer rolls back to 3%, and shows me a Error 1 message. There is nothing in the terminal to indicate an issue. The OS is new. No vestiges.

Can anyone tell me what I might be doing wrong please ?

Sometimes installers get corrupted. Download it again.

remember to download the md5 file to validate your .iso.
you can use:

md5sum -c downloaded-file.md5

or

echo "$(cat downloaded-file.md5)  downloaded-file.iso" | md5sum -c -

Thank you for your replies.

I have downloaded the installs numerous times on linux and mac … and I get the same issue on all of them.

On my ADSK account, I cannot see the md5 file for the flame downloads. I see md5s for the DKU page but not the flame app. Are they hiding somewhere?

you may not see that from the flame app because you are downloading from a privileged source (you need to log inand your connection is monitored), not a public source.
ping me personally and i’m happy to help you

Possible that your disk layout is wonky and the installer runs out of space?

Show us lsblk

Full disk?

150GB on the / volume. Shouldn’t it be enough ?

should be enough, but only just.
i have a dev machine that has a 128GB m.2 but I run htat thing super lean, and wipe / rebuild often.

a 1TB ssd from walmart/best buy/gas station/taco truck is about $100.

i needed an external usb for a different project - 500GB was $25 from goodwill.

at this point, if you’re on support, you should just dial it in and get a hand to hold.

if you want help you need to provide a bit more info.

Newer Flame installs include a lot of ML models. I think the download has bloated to 7GB for Linux.

The stone has 40tb. 150 gb for the /opt install. The adsk default size is 70gb.

I have opened a ticket with adsk. I’m sure it’s something really silly.

2 Likes

that’s the right way - they’ll have you up and running in no time.

2 Likes

@chlowden, did you solve your problem? I assume not. I encountered the exact same error. After a deep dive into the logs with AI assistance and trying several different approaches, I finally found a solution.

First, did you ensure that you created at least a 2 GiB /boot/efi partition when installing Rocky Linux?

Regarding the Flame installation: I was getting a terminal error , where the progress reaches 5%, rolls back to 3%, and then throws Error 1. I noticed a file error specifically mentioning ‘upiconfig_lin.xml’. The Flame installer expects to find this file inside /ODIS/CER/. It is supposed to be created automatically, but for some reason, my system failed to do so.

I solved this by manually installing ODIS onto the system first. This forced the creation of the required file. Once created, I located the file and copied it into the installer package. With this workaround, the Flame installation completed without any terminal errors.

Also, make sure to install the necessary Linux libraries for Flame beforehand. I’m not a Linux expert, so I recommend asking an AI for the specific library list, but do not update your Linux kernel! Give this a try; it might work for you too."

1 Like

Hello Kilker,

I have a similar issue. The error in the installl process is the same ..

sudo ./INSTALL_FLAME 
./INSTALL_FLAME: line 229: expect: command not found
Cleaning done!
[02/09/26 11:15:13] error    UPI Config file /home/admin/Downloads/autodesk_flame_2025.2.5_LINUX64/ODIS/CER/upiconfig_lin.xml does not exist
HTTP/1.1 200 OK
Accept-Ranges: bytes
Content-Length: 294833152
Content-Type: application/x-tar
ETag: "b5a4fd6bf696b68e7646b3cc462e8ac4:1769071254.512628"
Last-Modified: Thu, 22 Jan 2026 08:40:54 GMT
Server: AkamaiNetStorage
Date: Mon, 09 Feb 2026 11:15:13 GMT
Connection: keep-alive

The problem is that the file in the installer is not the same name

autodesk_flame_2025.2.5_LINUX64/ODIS/CER/upiconfig.xml

As what the command is looking for

/home/admin/Downloads/autodesk_flame_2025.2.5_LINUX64/ODIS/CER/upiconfig_lin.xml

If I rename upiconfig.xml to upiconfig_lin.xml, I get

./INSTALL_FLAME: line 229: expect: command not found
Cleaning done!
[02/09/26 11:23:39] error    cannot find UPI element in /home/admin/Downloads/autodesk_flame_2025.2.5_LINUX64/ODIS/CER/upiconfig_lin.xml [Code 1]
[02/09/26 11:23:39] error    Failed to launch /home/admin/Downloads/autodesk_flame_2025.2.5_LINUX64/ODIS/CER/CER/upi /home/admin/Downloads/autodesk_flame_2025.2.5_LINUX64/ODIS/CER/upiconfig_lin.xml /tmp/upi_info.xml, /home/admin/Downloads/autodesk_flame_2025.2.5_LINUX64/ODIS/CER/CER/upi exit with 1
[02/09/26 11:23:39] error    /home/admin/Downloads/autodesk_flame_2025.2.5_LINUX64/ODIS/CER/CER/upi exit with 1
HTTP/1.1 200 OK
Accept-Ranges: bytes
Content-Length: 294833152
Content-Type: application/x-tar
ETag: "b5a4fd6bf696b68e7646b3cc462e8ac4:1769071254.512628"
Last-Modified: Thu, 22 Jan 2026 08:40:54 GMT
Server: AkamaiNetStorage
Date: Mon, 09 Feb 2026 11:23:40 GMT
Connection: keep-alive

I copied the ODS file into the /opt/autodesk folder

sudo cp -R '/home/admin/Downloads/autodesk_flame_2025.2.5_LINUX64/ODIS' '/opt/Autodesk'   

But that did not change anything. Can yo clarify what manually install ODS means please?

I meant by ‘Manually Installing ODIS’: Simply copying the folder is not enough; you need to trigger the ODIS installation script itself so it registers with the system and creates the necessary environment.

  • Go to your Flame installer folder.

  • Navigate to: autodesk_flame_2025.2.5_LINUX64/ODIS/

  • Look for an install script or binary (usually named AdODIS-installer.run or similar).

  • Run it with sudo: sudo ./AdODIS-installer.run (or the exact name of the .run file there).

  • This will install ODIS to /opt/Autodesk/AdODIS/V1.

Regarding the upiconfig_lin.xml file: Don’t just rename the existing upiconfig.xml. The installer is looking for a specific structure. Once you manually install ODIS, check the /opt/Autodesk/AdODIS/V1/ or the ODIS subfolders within the installer. The correct upiconfig_lin.xml should be generated there. If it’s still missing, then you can try to copy the generated one from the system’s ODIS folder back into your installer’s ODIS/CER/ directory.

Also i guess i u need to install a required package is missing on your Rocky Linux. Before running the Flame installer? : sudo dnf install expect and i didnt use any extra command for install flame. just used sudo ./INSTALL_FLAME after fix that upiconfig errror.

If you still encounter ‘Code 1’ after these steps, it likely points to missing system libraries (such as libnsl, libXScrnSaver, etc.) that Flame requires to run. You might need to verify if all prerequisite libraries for Rocky Linux are installed

1 Like

Hello Christopher!

Flame Support team got your ticket. Please make sure to follow up with them since messaged you but got no answer…

I just had this problem and solved with with (I’m probably getting the syntax wrong here,) a --nogui flag. It installed completely via the CLI and then worked.

To be honest, I have not moved forward because since then, when I now install any dku, the reboot gives me a black screen. In my experience, this is a Nvidia driver issue. It maybe also because of the bios changes that I did to align with Autodesk recommendations.

In all my years of installing flames, I have never encountered so many issues. It’s driving me mad.

When I boot up with another disk that has rocky 9.5 and Nvidia for comfyui , all works perfectly. It’s really weird. :frowning:

Concerning the install addition, the adsk help desk suggested the same code. Thank you for the advice

Can you ssh to the workstation and either diagnose the current installation or install other packages?

For those that are interested about where a post dku install black screen during boot up may come from, below is what I did to stop it.

  1. Reset the hp Z8 BIOS to factory default.
  2. Set secure boot to legacy active and no secure boot.
  3. Boot outside of EULER.
  4. Install DKU
  5. Boot now works correctly with Nvidia-smi identifying the GPU.

As for the installer, I have tried with

-nogui

But no joy for me.

~/.autodesk/ODIS/

Has lots of installer log files. There is a summary file that seems to identify errors. I am waiting for adsk help desk to instruct me as to what to do next.

1 Like