The collected works of supervinx

Hi !
Question from an IRIX newbie.
I installed IRIX only one time before: it was an Indigo² and installing 6.5 was (almost) a breeze...
Now I got an Indy (IP22 R4400 175MHz, 64Mb).
There was a Debian (I think) which won't boot, leading to
Exception: <vector=XUT>
...
Panic

Diagnostic tests (about two hours) showed no errors.

I tried to install IRIX 5.3 (I have only 6.5 and 5.3, but 64Mb are too few).

boot -f dksc(0,6,8)sahsARCS dksc(0,6,7)stand/fx.ARCS --x
did a)uto, then r, ro)ot , l)abel sy)nc, /exit

I choose "Install system software": tools were loaded on the disk, then
Exception: <vector=UTLB>
...
Panic

What's goin' on ?
5.3 is too old ?
I'm wrong somewhere, somehow ?

Thanks !
Image Image Image Image Image Image Image Image Image Image
I think you're right ... the 175MHz R4400 Indy is treated as a separate beast...
Let's search another IRIX version ;)
Image Image Image Image Image Image Image Image Image Image
I'm a bit upset :(
The 5.3 I tried, should be the right version, for Indy R4400/175 IP22, but it failed to boot.
Same thing happened with 6.2,
Exception: <vector=UTLB>, while the 6.5 gives <vector=XUT>
Could it be an hardware related issue ?
And if so, why diagnostics state that everything is OK ?
Image Image Image Image Image Image Image Image Image Image
I did a complete formatting, repartitioning and relabeling of the disk, with 5.3 a)uto.
It took over two hours ...
I removed the graphic adapter and tried the serial console.
IRIX 5.3 for Indy R4400/175, 6.2, 6.2 patched, 6.5.
Always panic, exception: <vector=UTLB>, only 6.5 <vector=XUT>
Since I'm starting to have headache, I'll try two things
1) complete cleaning of the boards
2) swapping HD
Image Image Image Image Image Image Image Image Image Image
Tried everything, none ...
Then I remembered to check the MAC address.
I didn't think about it because PROM settings were retained ...

It wasn't ff:ff:ff:ff:ff:ff, but some bits were corrupted and the starting values weren't
08:00:69.

dump -w -x 0xbfbe04ec confirmed it

So I did
setenv -f eaddr 08:00:69:08:e2:0a (random values were chosen, no MAC address sticker)
was successfull.

Or
fill -w -v 0x08 0xbfbe04e8
fill -w -v 0x00 0xbfbe04ec
fill -w -v 0x69 0xbfbe04f0
fill -w -v 0x08 0xbfbe04f4
fill -w -v 0xe2 0xbfbe04f8
fill -w -v 0x0a 0xbfbe04fc


printenv now shows the mac address

The installation process now starts :)
Image Image Image Image Image Image Image Image Image Image