I followed this Logik Live Flame Rocky 8.5 installation video: https://youtu.be/E254S9g4fMo?si=JoG7OL1xuklLS-b_
I will try again tonight using those install instructions, thanks
On linux I normally use dd to create installer media:
sudo dd if=/path/to/Downloads/rockylinux.iso of=/dev/sdd bs=16M status=progress
I interpret âifâ as input file and âofâ as output file.
the /dev/ label may change on your system.
If you are running Windows itâs worth considering an installation of Windows Subsystem for Linux
According to what you say, i think it has nothing to do with the gpu but with the system. Have you tried on RL8.7? 8.7 seems to be more stable than 9.3 for me. I know cases of people having issues on 9.3 just because of certain monitors. Maybe adsk will need to make another revision of their rl9.3
2 Likes
So, did you complete the OS installation right? and DKU? What do you call âwizard for flame?â ⌠is it the software installer? If so, the fix could be as simple as the installer being corrupted and you just need to download it again.
We did talk to ADSK as part of a recent LogikLive about 9.3. All their reference systems seem to be fine. But there do seem to be some corner cases with 9.3 that are fixed by staying with 8.7. I ran into that myself during the 2025 upgrade.
If you experience an issue with 9.3 install, before wasting too much time, Iâd try 8.7 and see if that addresses the issue. Not sure if there are major benefits to 9.3 weâd be missing out on, other than itâs shinier. 8.7 is officially supported for 2025.
Over time this will hopefully be ironed out.
1 Like
I tried the 8.7 installation (Flame 2025.0.1 HotFix Linux + Latest DKU) last night and got Flame running. However, I could not get any audio working. My audio devices did not show up in the settings. pavu was indefinitely establishing a connection. So I asked chat GPT for help. These are just the first half of the following commands I tried at some point:
sudo dnf install alsa-utils
sudo dnf update
sudo dnf install pulseaudio pulseaudio-utils
pulseaudio --check
pulseaudio --start
sudo usermod -a -G audio $(whoami)
journalctl | grep audio
pulseaudio -k
pulseaudio --start
sudo alsactl restore
pulseaudio -k
pulseaudio --start --log-level=debug
sudo dnf reinstall alsa-lib pulseaudio
coredumpctl list
coredumpctl info
rm -r ~/.config/pulse/* # Clears out user configuration to reset to defaults
pulseaudio -k # Kills the currently running PulseAudio, if any
pulseaudio --start # Attempts to start PulseAudio again
pulseaudio --log-level=debug --log-target=stderr
coredumpctl list pulseaudio
coredumpctl debug # Replace with the process ID from the list
sudo dnf reinstall pulseaudio pulseaudio-libs
pulseaudio -k
pulseaudio --start
One of the commands (I forget which), caused it to go into a kernel panic, and now every time I boot up into Rocky, Iâm stuck indefinitely with a kernel panic. Iâm thinking to start over with a new Rocky installation.
Trying 8.7 was a really good suggestion and did get my Flame 2025 running for the first time. However I had a problem with audio devices not showing up (Flame 2023 - Rocky Linux - rtx 3090 - non DKU video driver? - #66 by Retopo001)
Not sure what to try now. is it possible that 9.3 could work for me whereas 8.7 did not? I didnât have audio issues with 9.3 though I also couldnât install Flame. But that was before I tried the recommended thumb drive. Iâm thinking to try 9.3 or 8.5 again.
You should seriously consider the advice from others here to either switch to a Mac or find a certified system config for Linux of ADSK.
Installing Linux does require a bit of OS admin understanding. It cannot be solved alone by ChatGPT throwing proverbial mud at the wall and see what sticks.
A lot of those commands ChatGPT gave you are not invalid, but they come with a lot of context you need to understand. Some may be for different versions of Linux, some may make assumptions about hardware you have, etc. And as you saw, without that context youâre playing with fire.
When you end in a boot loop, there is a way out. You can interrupt the grub boot loader, edit the line and add âsystemd.unit=multi-user.targetâ to it and then boot. It should drop you into a single user command line where you can fix what went wrong, but then more so than ever do you need to know what commands to type, because youâre in the equivalent of a Mac OS recovery shell.
Neither 8.5, 8.7, or 9.3 are the answer, and all of them are the answer, for different reasons that are hard to pinpoint without sitting at your system and systematically working through it.
1 Like
You may indeed have better luck with 9.3 to solve those audio problems. I have noticed better support in my tests. What was the problem with 9.3? only the error when creating the usb?
On the other hand, you should only use chatgpt as general hints for possible solutions, but try to check what you are going to do first. You should look for specfic info for your motherboard or audio controller, and maybe ask in some linux forums.
The kernel panic is most likely due to this:
sudo dnf update
Never never never do that. it will ruin it. It is common to see this in all kinds of guides, something possibly advisable for other contexts. Not for us. Donât waste time trying to recover the system. Just reinstall and continue testing.
I installed rocky + flame on a workstation motherboard. I think it is doable.The audio problem should be minor, and âeasyâ to fix, unless you are unlucky and that motherboard have a specifically unsupported driver.
1 Like
9.3 gave an error message during Flame installation. USB is fine.
I just had an interesting attempt (so close!!). I installed rocky 8.7 and got the sound working by finding a patch that got my audio working. All I needed was Flame install to work (like it did for my last 8.7 attempt), but no cigar â the installer window came up blank! I tried a bunch of display driver stuff, but I think Iâll try another fresh install. Maybe this time will go better since I wonât be messing around with audio driver stuff and using sudo dnf update.
One odd thing that irritates me is that at some point after I install DKU and reboot, another partition option shows up when booting up. In addition to showing 8.7 Green Obsidian and the rescue version, an 8.10 Green Obsidian option appears! Even when I choose the 8.7 version, my system details show that I am now on 8.10.
btw do we always use the latest DKU? Thatâs what Iâve been doing, though out of desperation, I downloaded some others.
You should use the DKU that matches the Flame version youâre using. Theyâve been tested together, and we donât know if Flame makes assumptions about specific driver versions supporting features. If you mix and match, thereâs a potential for Flame calling a driver with non-present features.
Regarding 8.10 - I think the DKU installs OS patches that lead to the higher number. Back in the 2023/24 days I only installed Rocky 8.5 but as I was adding a new version of Flamer, it suddenly it showed 8.7. Iâm not actually sure if this is a separate partition vs. just an alternate kernel image on boot partition that is reference from Grub.
1 Like
I do plan to get a mac pro asap. GPT 4o is actually quite good though. It can update its memory with your specs. It helped me fix my audio issue. Itâs definitely not a substitute for using your head but still seriously speeds up the search for commands I wouldnât have found otherwise.
1 Like
I used the latest DKU mainly because I saw it listed next to Flame 2025 latest version and assumed I would need it to install Flame 2025. Is that not the case?
18.0.0 is the DKU release that notes added support for Rocky 8.7. Is that the one you think I should try?
The Flame 2025 DKU does support 8.7, I would use that.
Use the DKU that was released with the version of Flame youâre using, not the one one that added support for the version of Linux youâre using. They have may added patches in later DKUs.
1 Like