Octane1 V6 Upgrade Problems
Eric Mejdrich
I am having difficulty getting my Octane1 Vpro V6 graphics upgrade
to work correctly once installed.
My original OS installation was 6.5.7m, and to get current I
downloaded the 6.5.16m maintenance release from SGI and installed.
This also updated the PROM. After installation the machine was
rebooted to make sure that I didn't hork up something basic.
Then I halted the machine and installed the VPro XIO Tri-Module
assembly according to the instructions that were shipped with the
upgrade.
Power up time. The system comes up to the boot screen, and the
Stop for Maintenance screen just fine. I can enter the command
monitor, and run the confidence tests ok. When I run the confidence
tests, graphics are reported as ODYSSEY. Sweeeeeet, no problems so
far. Then I try to start the system, and the screen freezes when
bringing up the system - no xdm login screen appears. Doh! The system
boots, and when I log in remotely and do a hinv -m, it doesn't
report any graphics!
Because the boot screen and the Stop for Maintenance screen both
display, it would seem that the V6 XIO card is working correctly.
I'm suspecting that I don't have the correct IRIX support for V6,
although I thought that maintenance releases always contained
support for new hardware. I do have the 6.5.9f overlays that came
with the upgrade but no CDROM - I installed 6.5.16m from a remote
Winbloze machine with a big hardrive and Sharity.
Any insight is greatly appreciated!
Eric
--
-- Eric Oliver Mejdrich
-- eome...@yahoo.com
--
-- " What can change the nature of a man? Regret. "
--
Wolfgang Szoecs
eome...@yahoo.com (Eric Mejdrich) writes:
> Power up time. The system comes up to the boot screen, and the
> Stop for Maintenance screen just fine. I can enter the command
> monitor, and run the confidence tests ok. When I run the confidence
> tests, graphics are reported as ODYSSEY. Sweeeeeet, no problems so
> far. Then I try to start the system, and the screen freezes when
> bringing up the system - no xdm login screen appears. Doh! The system
> boots, and when I log in remotely and do a hinv -m, it doesn't
> report any graphics!
what else would you expect now ? :-)))
if you upgraded your system with an IMPACT gfx, how the hell could
'inst' guess, that you want to put an ODYSSEY board into it later ?
(so inst just upgraded whatever was necessary for the current gfx)
IF you were clever, you could have told 'inst' before the upgrade,
that it should install/upgrade stuff for the new gfx.
something like this:
inst -m CPUARCH=R10000 -m SUBGR=IP30 -m GFXBOARD=ODYSSEY -m MACHINE=Octane -m MODE=64bit -m CPUBOARD=IP30
> Because the boot screen and the Stop for Maintenance screen both
> display, it would seem that the V6 XIO card is working correctly.
> I'm suspecting that I don't have the correct IRIX support for V6,
> although I thought that maintenance releases always contained
> support for new hardware.
sure do they contain support for new hw ;-)
but inst cannot guess what you will do in the future ;-)
> I do have the 6.5.9f overlays that came
> with the upgrade but no CDROM - I installed 6.5.16m from a remote
> Winbloze machine with a big hardrive and Sharity.
>
> Any insight is greatly appreciated!
NOW, as you have the new gfx in the box, and the new PROM,
I would do this:
a.) boot a 6.5.16 miniroot
check inside inst with 'admin hardware', that GFXBOARD=ODYSSEY is there.
b.) and from there, reinstall AT A MINIMUM the gfx stuff:
by saying 'keep *' 'install eoe.sw.gfx x_eoe.sw eoe.sw64.gfx x_eoe.sw64'
(or simply say: install same) --- but it will take longer.)
After that, it should be fine.
wolfgang
Scott Henry
W> In article <f9fa3286.02052...@posting.google.com>,
W> eome...@yahoo.com (Eric Mejdrich) writes:
W> NOW, as you have the new gfx in the box, and the new PROM,
W> I would do this:
W> a.) boot a 6.5.16 miniroot
W> check inside inst with 'admin hardware', that GFXBOARD=ODYSSEY is there.
W> b.) and from there, reinstall AT A MINIMUM the gfx stuff:
W> by saying 'keep *' 'install eoe.sw.gfx x_eoe.sw eoe.sw64.gfx x_eoe.sw64'
W> (or simply say: install same) --- but it will take longer.)
W> After that, it should be fine.
Or, to install less but correct stuff, say "install fresh" (or is it
"install stale"? one of those 2...). Inst will then select just
whatever subsystems it needs for the new hardware.
--
Scott Henry <sco...@sgi.com> / Help! My disclaimer is missing!
IRIX/Linux MTS, / http://reality.sgiweb.org/scotth/
Silicon Graphics, Inc / SGI-One step ahead