Flame 2025 - Rocky Linux 8.7 Successfully Installed On RTX Threadripper PC - Complete Breakdown

Flame Flame Questions
1

Flame 2025 Rocky Linux 8.7 RTX Successfully Installed - Complete Breakdown

This post (requested by kily) outlines my success at taking a gaming workstation with Windows 10, partitioning a dual-boot of Linux Rocky 8.7 alongside Windows, and getting Flame 2025 installed and running. I think with GPT-4o being able to store system specs, it is viable for Threadripper RTX users completely new to Linux to get Flame working in under 20 hours. The troubleshooting is meticulous and many solutions are undocumented, but it’s possible. Sometimes the official method to a thing might be to contact Autodesk support and be given a specific configuration or setting. Obscure forum threads and Github repos often have the answers to issues in Linux. Using GPT-4o as a personalized research assistant and Linux tutor has 10x-30x’d the viability of this install method.

Notes:
-This process can be adapted to your own pc by researching drivers for your specific hardware.

  • During this successful installation, I NEVER used sudo dnf install to batch install packages; I always avoided getting repos directly from the terminal. I always tried to install drivers by directly navigating to the correct page with Google Chrome and downloading the packages directly into my user download folder.
  • Beware that su -, which gives root control, can mess up installation by somehow creating duplicate download folders; type exit to return to user. It is usually safer to stay in the user mode and just use sudo.

Here are the pc specs I started with.

My PC Specifications

  • Platform: AMD Threadripper PRO WRX80 EATX
  • Motherboard: Asus Pro WS WRX80E-SAGE SE WIFI
  • CPU: AMD Ryzen Threadripper Pro 5965WX 3.8GHz 24 Core 280W
  • RAM: 8x Kingston DDR4-3200 16GB ECC Reg.
  • Video Card: NVIDIA GeForce RTX 3090 Ti 24GB Founders Edition
  • Sound Card: Onboard Sound
  • Networking: Integrated Ethernet, WiFi, and Bluetooth
  • Storage: Samsung 980 Pro 2TB Gen4 M.2 SSD (Primary drive)
  • Audio Interface: MOTU M2
  • Chassis & Cooling:
    • Case: Fractal Design Define 7 XL
    • Power Supply: Super Flower LEADEX Platinum 1600W
    • CPU Cooling: Noctua NH-U14S TR4-SP3
    • Additional Cooling: Case Fans Upgrade Kit (PWM Ramping)
  • Software: Windows 10 Pro 64-bit

The only hardware that needed config files tweaked was the audio interface. Threadripper 5000 series CPUs work fine. Nvidia driver for the RTX3090 Ti installed automatically with DKU 19.0.0 (but not 19.0.1 for some reason).

Steps Taken:

1. Disk Partitioning and Installation Setup

  1. Shrink SSD: On Windows 10, I used Ease US Master Partition (not necessary if Windows disk management works) to shrink a 2TB SSD to 1.5TB, leaving 500GB unallocated for the dual boot of Linux Rocky 8.7.

  2. Created Bootable USB:

  3. Manual Partitioning Setup:
    Note Made sure secure boot is disabled from BIOS

    • a) Boot from USB: Booted from the USB drive with Rocky Linux 8.7 installer.
    • b) Partition Sizes:
      • /boot/efi (UEFI partition): 1024MB
      • /swap: 32000MB (32GB)
      • / (root partition): Allocate the remaining space.
    • c) Static IP Network Configuration:
      • IP Address: xxx.x.x.x
      • Gateway: xxx.xxx.x.xxx
      • DNS Servers: 8.8.8.8, 1.1.1.1, 8.8.4.4, 1.0.0.1
      • Hostname: name-desktop
    • d) Create User: Created a user with a simple name (e.g., yourname).
    • e) Set Time Zone: Set the appropriate time zone during installation.
    • f) Run Installation: Let the installation run and rebooted the system after completion. Removed the thumbdrive as reboot starts.

2. Disabled Automatic Updates

  • Note: I manually turned off automatic updates updates in the settings then used the following commands just to be sure.
    sudo systemctl disable dnf-makecache.timer
sudo systemctl disable dnf-makecache.service

3. DKU 19.0.0 Installation (https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/CentOS-ISO-installer-and-Linux-Driver-Kernel-Utilities-for-Flame-Family.html)

  • Included NVIDIA Drivers: NVIDIA drivers were automatically installed with DKU 19.0.0.
    cd /home/yourname/Downloads/
tar -xvf DKU_19.0.0.tar
cd DKU_19.0.0
sudo ./INSTALL_DKU
sudo reboot

4. Flame 2025 Installation (Downloaded Flame 2025.0.1 HotFix Linux)

  • Extracted and Installed Flame:
    cd /home/yourname/Downloads/
tar -xvf autodesk_flame_2025.0.1_LINUX64.tar
cd autodesk_flame_2025.0.1_LINUX64/
sudo ./INSTALL_FLAME

5. Window Control Tool (wmctrl)

  • Issue: During startup of Flame, the Autodesk Licensing Agent window was unclickable, blocking progress. To manage this, I used wmctrl.
  • Usage: wmctrl or similar tools were used to manage and manipulate window focus.
    sudo dnf install wmctrl
wmctrl -lx
wmctrl -i -a [window_id]

-Note: I would recommend saving ‘wmctrl -lx’ and ‘wmctrl -i -a [window_id]’ as copypasta. I still use it often since I get unclickable windows blocking on the first Flame startup anytime I reboot.

6. ALSA MOTU Installation

  • Installed ALSA Libraries (GitHub - kiosion/alsa-motu-m2: Information about using the MOTU M2 under Alsa on Linux)(Index of /files/pub/lib/):

    cd /home/yourname/Downloads/
tar -xvjf alsa-lib-1.2.7.1.tar.bz2
tar -xvjf alsa-ucm-conf-1.2.7.1.tar.bz2

cd alsa-lib-1.2.7.1
./configure
make
sudo make install

cd ../alsa-ucm-conf-1.2.7.1
./configure
make
sudo make install

  • Configured ALSA for MOTU Devices:

    cd /home/yourname/Downloads/alsa-motu-m2-main/src
sudo cp -r MOTU/* /usr/share/alsa/ucm2/USB-Audio/MOTU/
sudo cp USB-Audio.conf /usr/share/alsa/ucm2/USB-Audio/
sudo nano /usr/share/alsa/ucm2/USB-Audio/USB-Audio.conf

  • Edited /usr/share/alsa/ucm2/USB-Audio/USB-Audio.conf to include the correct configuration for MOTU M2:

    If.Motu {
Condition {
  Type String
  Haystack "${CardComponents}"
  Needle "USB07fd:000b"
}
True.If.M4 {
  Condition {
    Type String
    Haystack "${CardLongName}"
    Needle "MOTU M4"
  }
  True.Define.ProfileName "MOTU/M4"
  False.Define.ProfileName "MOTU/M2"
  }
}

  • Ensured Correct Permissions:

    sudo chown -R root:root /usr/share/alsa/ucm2/USB-Audio/MOTU
sudo chmod -R 644 /usr/share/alsa/ucm2/USB-Audio/MOTU

  • Used these settings in Autodesk Setup under the General tab - Video: None, Audio: ALSA

8 Likes
2

Installed RL Linux 8.7. Installed DKU 9.0.0.
Nvidia A4000 working . Flame 2025 installer is not proceeding past 3%.
System Specs AMD 5950x, Asua 570x. 128GB ram,

3

@rohan Did you use a brand new flash drive and Balena Etcher? That was the main factor for me that would similarly stop the installation. I’m so superstitious about this part of the installation that I would not use any thumb drive other than the one recommended.

Also, make sure that the Rocky 8.7 iso is specifically the one from the Autodesk website. It cannot be the one from the Linux website.

4

Used Balena Etcher but on a used pen drive, Linux and DKU install was successful,
Flame 2025 installation is the issue ,
following is the Autodesk Lic log.

sudo: unable to execute /usr/local/share/FNP/service64/11.18.0/FNPLicensingService: No such file or directory
Checking FNPLicensingService is running
No PID file for FNPLicensingService

5

@rohan That sounds almost exactly like what happened to me when I used an old thumb drive. I would really recommend ordering a few of those Cruzers, the smallest ones. Also make sure to do the checksum to make sure that the iso was correctly downloaded.