We are trying to upgrade our P620 from 2026.0 to 2026.2.
Rocky Linux version is 8.10
it seems to meet all systems requirements, but the installer fails saying the machine doesn’t meet minimum requirements. (is there a way to see which minumum requirement it fails?)
We installed it on an identical machine running a 3090 and that worked perfectly. The only difference we can see is that the Graphics card is an A5000. The drivers are all the same.
I have it working on another p620 that has a 3090 in it.
rocky 8.10 and nvidia drivers 570.195.03 on both (which comes in DKU 20.2)
Im half thinking that maybe because 3090 is consumer card and A5000 is workstation card, maybe its more stringent for which driver is running on the A5000
yea i have 570.195.03 driver that came with the dku installed. thinking maybe the A5000 needs something lower, like 550 or 535
looking into all that now.
nvidias workstation tool doesnt show 2026 or 2026.2 in it yet,
2025 and 2024 state drivers 550.78 for A5000 so might give that a go and see what breaks XD
got it installing.
still not 100% on what caused it, i went through the shell scripts that run with the installer to dig through what the checks were looking for, and yea.
ended up downgrading the drivers, then reinstalling the upgraded drivers and something in there made it start workign again.
Are you suggesting moving to 9.3 or 9.5 ??
We haven’t shifted to 9 because we are always mid-job and can’t get the 3 flames empty.
We were on 2023.. it’s taken us this long to find a window to upgrade.
if your jobs are big enough rent three rocky 9.5 machines for a month.
upgrade your own machines.
use them as burn nodes while you’re renting.
send the rentals back.
carry on
Yet again…. another example of why centralized Project Server is the only rational way to run Flame. If you had been doing that, then you would only incur a few hours downtime at most. The Flame machine becomes an ephemeral dumb compute node, with no data on it.
@ALan
It’s just not true for everyone.
There are many other ways to not incur downtime.
You’re just tied to your own solution.
Which is fine.
But far from unique.
Let’s remember what it was like before you had your own flavour of centralized project server and how many years it took for you to develop that.
Let’s stop pretending that an ice cream truck drove down the street and dropped off the answer for $0.99 with a sugary cone.
And to be clear, the only logikal way to run flame is to not isolate yourself using technology that has already been deprecated.
No…. literally there is ZERO ways to not incur downtime with a traditional Flame deployment. With Project Server, I can set a workstation on fire. Walk over to the next desk, and launch right into my project, and start up right where I left off, Libraries, Desktops, Batch Groups, Timelines, the whole fucking shebang. There is NO other way to do that.
Yes I had an un-official Project Server workflow for many years, but it has also been many years that it has officially been supported, documented and even facilitated by the INSTALL_PROJECTSERVER script which comes with every Flame distribution package. It is NOT deprecated in ANY way. It has NEVER been discussed by ADSK in ANY forum that it is or will be deprecated. It is quite relevant to all current and future workflows.
But oh well… everyone should enjoy their data island that they can’t get off of.
But I think we need to be careful about generalizing. The OP discusses a setup with 3 flames, and so it’s similar to your setup or what Alan is doing (i.e. multi-seat).
But there are a lot of single flame users out there, for whom project server makes no sense. It adds complexity and you’re not eliminating single point of failure AFAIK.
Just be mindful that Flame lives in diverse set of deployments. From Alan’s infamous undie guy to big facilities. And as covered already, not all single seat operators are indecent, ignorant, or incapable of sysadmin tasks.
Regarding the original problem - if you finally found a window to upgrade from 2023 to 2026.2, I would have absolutely tried to use the same window to jump to Rocky 9.x. 8.10 is getting long on the tooth and it won’t be long before it may become unsupported. So if your next window is another 3 years out, you will be on very old OS versions and likely get grief if you have to file a support request. Isn’t Rocky 9.x now on .7? So this is past it’s teething problems as major release.
