Hey @Linux-RISC, here's just an update for you and for the forum in general.
First off, I think you can positively update your table of tested system (
http://irix.mersisl.com/) with an Indigo R4400 Elan and IRIX 5.3 installation.
All went super smooth.
But hold on, here's the question/tip for the forum instead.
I almost gave up last night when my Indigo kept bouncing back to me saying "Unable to reach server" or "the server path doesn't contain any distribution" or errors like those.
This was happening in the EPROM, either by using the "Install System software" Icon or by using the EPROM console using the bootp()[..]sashARCS -x command.
Eventually, I got it to work and that "shit, I bumped into this before" little lamp in my brain suddenly lit up.
So here's the thing:
When powering on the machine I can go to the terminal and start either "fx" or "sash" by using this syntax:
bootp()192.168.5.120:/IRIX/irix5.3/1/stand/sashARCS -x
then I'm into "sash"
but then the commands to get the installation to kick in and work is the following:
bootp()192.168.5.120:/i/IRIX/irix5.3/1/dist
notice the added "/i" in the path!
(The complete path to the distribution would be "/home/irix/i/IRIX/irix53/1/dist")
without that extra parent directory I couldn't NEVER have the install to reach the distribution and start the installation.
so my question here is, can anybody explain to me why this is happening?
I literally wasted days behind this issue and I don't remember this happening when I was using an IRIX system as a network server instead of a Linux/Raspberry server.
Or have I totally forgot entirely how this was working?
Another thing I had to force on the Indigo was using the setenv tapedevice bootp()192.168.2.46:/export/irix/dist/sa command, cause the "setenv notape 1" variable wasn't enough for the installer to just reach the destination directory without "asking for a tape".
Either way, this helped me and I hope this will help someone else too
Cheers!
Hey @Linux-RISC, here's just an update for you and for the forum in general.
First off, I think you can positively update your table of tested system (
http://irix.mersisl.com/) with an Indigo R4400 Elan and IRIX 5.3 installation.
All went super smooth.
But hold on, here's the question/tip for the forum instead.
I almost gave up last night when my Indigo kept bouncing back to me saying "Unable to reach server" or "the server path doesn't contain any distribution" or errors like those.
This was happening in the EPROM, either by using the "Install System software" Icon or by using the EPROM console using the bootp()[..]sashARCS -x command.
Eventually, I got it to work and that "shit, I bumped into this before" little lamp in my brain suddenly lit up.
So here's the thing:
When powering on the machine I can go to the terminal and start either "fx" or "sash" by using this syntax:
bootp()192.168.5.120:/IRIX/irix5.3/1/stand/sashARCS -x
then I'm into "sash"
but then the path that the "from" commands need to get the installation to work is the following:
bootp()192.168.5.120:/i/IRIX/irix5.3/1/dist
notice the added "/i" in the path!
(The complete path to the distribution would be "/home/irix/i/IRIX/irix53/1/dist")
without that extra parent directory I couldn't NEVER have the install to reach the distribution and start the installation.
so my question here is, can anybody explain to me why this is happening?
I literally wasted days behind this issue and I don't remember this happening when I was using an IRIX system as a network server instead of a Linux/Raspberry server.
Or have I totally forgot entirely how this was working?
Another thing I had to force on the Indigo was using the setenv tapedevice bootp()192.168.5.120:/IRIX/irix53/1/dist/sa command, cause the "setenv notape 1" variable wasn't enough for the installer to just reach the destination directory without "asking for a tape".
Either way, this helped me and I hope this will help someone else too
Cheers!