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.

6

Dear Retopo001
I do it but after I reboot, i can not log in linux.
Please help me.
I do this step:

  • Rocky Linux 9.3
  • DKU 19.2.0
  • Flame 2025.2.2
    -Window Control Tool
    -ALSA MOTU Installation

Thanks

7

Iā€™ve had that problem so many times with Autodesk install .iso. On new computer builds I always buy a new flash drive for install. Also I reset the CMOS on the motherboard to wipe the bios back to the original.

1 Like
8

u need a thumbdrive that can be formatted to do uefi boot.

9

I donā€™t think that issues installing autodeskā€™s custom iso is related to supported or not supported machines. I had that kind of issues on my supported workstation.
Iā€™d recommed 1000% check the md5 hash to verify the iso dowloaded. Download osā€™s isos using http is not a good idea so for me is essential check and verify the iso downloaded and download it again if the file is not verified.
Lately I had some problem even for flame installers, (aborting installation randomly) and I had to download it again (autodesk does not provide md5 hash to check flameā€™s installers).

And I use first usb stick I see when I open my drawer, although yes, use a good usb stick can be a good idea in case of random issues installing rocky.

1 Like
10

Did you use original rocky linux installer or autodeskā€™s custom iso? Do not install rocky using the original installer of rocky distro. Use only autodeskā€™s custom iso. Itā€™s ready to disable nouevau driver properly and install the nvidia driver.

Unless you do disable nouveau driver manually, once dku is installed, you will have a conflict between both drivers, so your screen login will go black.

11

And if you are in the situation where your screen is black upon boot, there are fixes, you donā€™t have to start over.

You can edit the boot menu to change the mode to not switch to video mode but give you a text login and then you can go fix things from there. Search this forum, Iā€™ve posted it here before.

Also when I originally installed 9.3 on my system I had all sorts of issues with a supported GPU. Once I debugged it, it always got hung up on NVidia driver switching display mode. Turns out there was a bug in the driver that has since been fixed.

Never had an issue with USB sticks. That seems like superstition to me. I mean use quality ones. You can also use just a regular external USB hard drive, doesnā€™t have to be a stick. Iā€™ve even used camera SD cards and a card reader one time when I couldnā€™t find a USB stick in the office.

Really comes down to the intended procedures (ADSK ISO) and when it doesnā€™t work systematically debugging it. In my case there were some teething issues with 9.3, I just went back to 8.7 which installed right away. 2025 is still supported on 8.7.

12

I use autodeskā€™s custom iso to install Rocky 9.3
After Install DKU reboot I log in ok by GUI. But after install FLAME 2025.2.2
I can not see the green log in
At this step I need do it?
=> 5. Window Control Tool (wmctrl)

Thanks

13

Try again not installing the ā€œwindow control toolā€. I have no idea what that thing is. Searching, I see is kind of window manager and could be the reason of some conflict. I donā€™t see the need to install it. Donā€™t install foreign stuff like that in the OS.

14

If after installing Flame + DKU and you reboot, you see the boot messages scroll by and then end up on a black screen without any login and just a blinking cursor, then your Nvidia driver failed while switching from text to graphics mode. You need to figure out why that is.

Unfortunately when you look in dmesg, that is not obvious, because it doesnā€™t leave a message there, and the last message in dmesg is from before the switch, so it leads you down all kinds of dead ends if you go there. Itā€™s only on a successful boot that you realize the next message in dmesg would have been ā€˜starting graphics modeā€™ or something like this.

You donā€™t need other tools. You need to find out why the NVidia driver barfed and fix that.

To get a login and debug, you need to edit the Grub command during boot so it stays in multi-user mode and gives you a text based login.

Time to be a detective, not re-installing and hoping for a different outcome, or installing random things hoping magic to happen.

One thing you can do - save a dmesg output from a successful boot before installing Flame and DKU, so you have something to compare to on the failed install.

1 Like
15

Dear Allklier.

I try to reinstall DKU + driver NVIDIA + FLAME, but after I reboot i can not see creen to log in. I search many thing but no seeā€¦i don`t know what to do nextā€¦
Thanks

16

See here: Rocky Road 9.3 - #27 by allklier

1 Like
17

IMG_3712
IMG_37122778Ɨ1284 125 KB

Soft selection, which one do you choose? Or it doesnā€™t make a difference

18

Using custom adsk iso to install rocky, soft selection is locked. No need to select anything on that section of installer.

19

I trust Ventoy more