[necron2600]

I installed both Flame and Smoke on an Octane2 (I chose 'film' resolution on installing.. and note I am on a vpro V10.. not V12.. my res is always 1920x1200@70 with no issues).. on reboot I have no X11, just the initial console hardware GUI (blue background with grey console window) looping:
dgl error (access): dgl server access denied - myhostnamehere:0.0 
return -13
...
flamedgl error (access): dgl server access denied.

My monitor loses connection/sync during the attempt X start..  eventually it connects but at the default console term GUI.

I can ssh in and I run:
bash-4.4# ./gfxinfo
Graphics board 0 is "ODYSSEY" graphics.
        Unmanaged 1280x1024 
        BUZZ version B.1
        PB&J version 1
        32MB memory
                Banks: 2, CAS latency: 3
         Monitor 0 type: Unknown
        Dual Channel Display option
         Monitor 1 type: NEC 26639       Monitor 2 type: Unknown
        Xvc info not available for unmanaged boards

SYSLOG shows (after I gfxstop/gfxstart):

Jan 10 23:24:07 6B:octane xdm[1136]: Rescanning both config and servers files
Jan 10 23:24:11 4A:octane unix: WARNING: odsy: frame buffer/fullscreen accum config causes oversubscription of sdram.
Jan 10 23:24:11 3D:octane Xsgi0[3502]: odsyDefaultTTExists: SDBreadOpenDatabase failed to open '/usr/gfx/ucode/ODSY/vof/1280x1024_60p.vfo' with errno 2
Jan 10 23:24:11 3D:octane Xsgi0[3502]: odsyKernInit: ODSY_BRDMGR_CONFIG_FB failed
Jan 10 23:24:11 3D:octane Xsgi0[3502]:
Jan 10 23:24:11 2D:octane Xsgi0[3502]: Fatal server error:
Jan 10 23:24:11 2D:octane Xsgi0[3502]: no screens found


setmon does not work:

./setmon -n 1920x1200_72.vfo
Cannot open display
: Connection refused
bash-4.4# env |grep DIS
DISPLAY=:0.0


Any ideas?  This is def. something with Flame/Smoke.. and syslog is showing "accum config causes oversubscription of sdram." as a warning (V10 has less ram than v12).  How can I recover this system?

---

Well, after further review:
XDM log has:
xdm error (pid 1136): Xsgi0[3653]: odsyDefaultTTExists: SDBreadOpenDatabase failed to open '/usr/gfx/ucode/ODSY/vof/1280x1024_60p.vfo' with errno 2
Xsgi0[3653]: odsyKernInit: ODSY_BRDMGR_CONFIG_FB failed

and that file does not exist:
bash-4.4# ls -ltra /usr/gfx/ucode/ODSY/vof/1280x1024_60p.vfo
Cannot access /usr/gfx/ucode/ODSY/vof/1280x1024_60p.vfo: No such file or directory

[Raion]

ls -la /usr/gfx/ucode/ODSY/vof/*.vfo

In most shells should show you the current VFOs you can use.

[necron2600]

So, I copied a similar vfo to that missing file name..
bash-4.4# ls -ltra 1280x1024_60p.vfo
Cannot access 1280x1024_60p.vfo: No such file or directory
bash-4.4# cp 1280x1024_60.vfo 1280x1024_60p.vfo

It boots and X works, just at a low res.
So I tried to change it to 1920x1200@60 as I usual do (requires 8-bit. not 16bit as its a V10), but it says it is an illegal power-on configuration.

I also tried taking a previous install's vfo files for 1920x1200* placing into /usr/gfx/ucode/ODSY/vof/ . .. rebooting, no luck to change it to 1920x1200.

How can I get my original res back?

[Raion]

No idea man. The Discreet tools seriously change a lot of IRIX, so there's probably issues that stem from their installation. AFAIK it's not easy to reverse those changes without a reinstall.

[necron2600]

while the GUi fails to set res, command line works:
setmon -v -w 1920x1200_60 seemed to come back with no errors (it errors without -w)
However..
now xdm does not like that
xdm error (pid 1138): xdm error (pid 1133): Xsgi0[1258]: odsyDefaultTTExists: Illegal timing file '1920x1200_60.vfo' specified
Xsgi0[1258]: odsyKernInit: ODSY_BRDMGR_CONFIG_FB failed

So I recall having to always set the res in the GUI to be 8bit, not default of 16 (a V10 card cant handle 16bit with that res)..
I set it here:
./setmon -x -v -d8 1920x1200_75 (I probably could have used -w instead of -x, so it would set it on boot)
Now I can login (still low res) and change the res in the GUI without it complaining.

It may be that I had to select the 8 BIT first in the gui before selecting the resolution... not sure but at least I have it back to 1920x1200.

So all fixed!

This thread may be useful to someone else, that just so happens to need 8bit due to a V10 card and installed Flame that made everything go out of whack.

[Irinikus]

I used to play around with Flame on my Tezro, and it was a complete mess!

Seeing that the drives are swappable, in future I'll just have a second set of drives in sleds for my Flame installation! (In this way, there's no way in which it can mess with my main installation on the machine!)