Hello. I am trying to install Rocky Linux so I can practice with Flame but I can’t seem to install a version of Linux that works with Flame. I can install Linux but the Linux option will cause my screen to go black. I’ve disabled secure boot and set everything to UEFI. I made a USB key with Rufus and used the ISO and DD option. I’m not sure what to try next.
Hmm. Are you using the Autodesk Rocky Linux ISO from here?
And what hardware are you using?
Looks like he is based on the first screenshot.
I’ve pm’d him but I may as well post here too. I would also turn disable “launch CSM” otherwise he still might not be getting into a UEFI environment.
Not many clues in the shell, sadly. But it might also be worth trying to put edd=off into the kernel parameters. It’s also worth reflashing the media again (again), or use different media
I would be interested to know what the hardware config is, too.
1 Like
Are you getting to the shell installer where it has language/Timezone/installation media etc; which you modify with number selections or is it going blank before you reach that?
Or is it that you finish installing Linux and on the reboot when it launches the GUI then the screen goes black?
The screen goes black after that shell screen. I’m not getting into any installer at all. I’ve turned of “Lauch CSM”. I’m currently on an i8700k CPU and an ASUS Z370-A, I have a 3090 RTX installed. I’ve tried installing with a more generic graphics card too.
I thought I tried disabling the “Launch CSM” but I must not of because it is working now! Lets see how this goes. Thanks y’all!
1 Like
Thanks! I actually tried turning off “Launch CSM” and it worked! I thought I tried that. I tried so many things. Now Flame installed but I’m getting this error:
“error while loading shared libraries: libcuda.so.1: cannot open shared object file: No such file or directory.”
Do I need to install Cuda drivers?
Did you install the DKU?
I tried but will it not install on a workstation that is not supported? It says “command not found” for lines 15, 18, 19. Then “syntax error near unexpected token ‘(’”
You should be able to install the DKU with a generic configuration. Is the DKU failing to install? If so, best to show a screenshot of where it is falling over.
Eugene and I worked this out over PM. He was trying to run the Install script with:
sudo bash INSTALL_DKU
which was causing the problem. In case others have the same problem this is remedied by just running
sudo ./INSTALL_DKU
2 Likes
Thanks for the help. Why did it not run correctly?
Because the INSTALL_DKU script is perl and not bash 
I had the same source install issue with the ISO. I even set the source location to the files on the USB stick I booted from, and it would only take the RockyLinux source repo to install, but even then I get some package not found for OpenJDK. I made the USB stick from the official ISO on windows with Rufus (Rufus - Create bootable USB drives the easy way) in ISO mode.
So I abandoned that route and just did the pure install Rocky from the boot USB. and I got the same Error 1 with trying to install Flame from the tar. I already installed the DKU and rebooted beforehand as well. So I tried using the collection tool to see if it was a dependency missing issue, and I found I needed
libXss
libGLU
/bin/csh
libglut
my issue is trying to find libglut because its not coming up as any package on yum, and I cant find that library anywhere.
I have just running into the same issue of my usb stick not being recognised as à rocky install source. After hours of trying to force a network install, I read that formatting the usb with rufus on a windows and using the DD copy mode to copy the is, solved all my issues. Don’t waste your time trying to troubleshoot the installation. Just get the usb stick copied properly and the rest should follow easily.
1 Like
Also, for those with old NETAPP E series SANs and ATTO celerity 16GB, you need to install the Santricity and appropiate ATTO drivers in multipath.
They do not seem to be in the 17.3.0 DKU. Santricity works fine on Rocky 8.5.
A good advice is at least pass once the “check media” option on first boot screen, with a fresh new usb boot created. And check the iso downloaded with the md5 hash. I had one stupid issue years ago. Simply , the iso was corrupted.