IRIX and Software

Just tried, same thing.

Just tried putting a "." for the Remote Directory IP Address and got this:

duplicate IP address!! sent from ethernet address: 18 87 96 be 92 f1
duplicate IP address!! sent from ethernet address: 18 87 96 be 92 f1
duplicate IP address!! sent from ethernet address: 18 87 96 be 92 f1
duplicate IP address!! sent from ethernet address: 18 87 96 be 92 f1
duplicate IP address!! sent from ethernet address: 18 87 96 be 92 f1
duplicate IP address!! sent from ethernet address: 18 87 96 be 92 f1
Unable to execute bootp().:/irix/6.5/1/dist/sa(sash64): could not connect to server
Cannot load bootp().:/irix/6.5/1/dist/sa(sash64) -- could not connect to server.

I would recomend starting up another SGI and verify that it can reach DINA and read the NFS directories etc.

The last error message informs you that you have two or more computers having the same IP number.
One of the computers have the 18:87... MAC adress.

//Harry

Tried a different switch with only my Linux box and the Origin 300, now I'm getting:



Is there way to wipe the drive from prom? I'm guessing it doesn't like the non-irix partitions?

See Clearing Old Data Prior to Installation.

Thanks! But how would that work doing a netboot? I don't have a cd-rom drive to boot fx from my IRIX CDs unfortunately.

Never tried it with a networked install, but if you're able to get into the installation menu you might be able drop into the Admin menu (#13) and run run fx from the admin chrooted shell.

I wish I could get that far, it simply dies on the:

Should I try wiping the partitions in another system?

Hard to tell from only two lines out of the netboot process where things are going south. Can you invoke fx using this method? http://www.nekochan.net/wiki/IRIX_Netwo ... figuration

That worked! Doing an "auto" on it now.

Just to eliminate the potential for additional headaches I'd suggest following that guide's directions to explicitly partition it as a root option (ro) drive - but use a block size of 4096 .

Depending on the size of the disk, "auto" could take a very long time. I second the notion of "partition it as a root option (ro) drive".

R.

General note: tingo has reported success using DINA under VirtualBox . I wonder what the changes were besides network interface name...

Anyway, I changed a couple sentences in the wiki guide to reflect the news.

Got IRIX up and running, thanks all for your help.

Woke up this morning to tons of



Time to reinstall everything again

.. and update your signature

R.

Done

I was able to clone it to another Maxtor ATLAS 15k luckily, so all was not lost

Hmm, I can't remember now, and it doesn't look like I wrote abything about it in my worklog.
I think it was just changing settings in VirtualBox for the (virtual) hardware until the virtual machine worked.

I realize this is an older post I'm responding to, but I recently decided to revive a couple Indy's I had sitting in a closet so I just recently stumbled across this info. Apologies, but I hope someone finds my info useful.

I already had VirtualBox installed on a machine and didn't want to mess with VMWare player so migrated deBug's VMWare image VirtualBox. It's not a difficult procedure. Here's what I did:

I created a new NetBSD VM and matched as many settings as I could:
1 Processor
256MB Ram
32MB Video Memory
PIX3 Chipset
Hardware Clock in UTC (My host OS is MacOS)
Enable VT-x + Nested Paging
32MB Video Memory
IDE HD and CD on PIX4 controller
Attach the existing DINA image to the HD
PCnet-FAST III Ethernet attached as a Bridged Adapter

Since the default install of NetBSD is fairly hardware agnostic, there weren't many changes required. The main issue is that graphics won't work so there are a couple changes that need to be made.

First off, from the start menu choose "4" to drop to the shell. Before working on getting graphics working I needed to fix the keyboard because the default encoding is set for SV, which maps all my keys wrong. To fix, enter this command:

wsconsctl -k -w encoding=us

This will instantly fix your keyboard mapping, however it's easier said than done because all the non-letter keys are initially mapped wrong. For me I can get the "-" by pressing the "/" key. For the "=" I used Shift+0. That may or may not work for you depending on your keyboard. Trial and error is the only option here.

To make that change persist after a reboot, you need to edit the /etc/wscons.conf file and find the "encoding=sv" line and change it to "encoding=us", or whatever your country code is. They give some examples (us, uk, de, dk, it, fr, jp, sv, no, es, pt). Save that file with the correct country code and you won't have to worry about the keyboard anymore.

From there it's probably best to get networking going. Enter "/usr/dina/startmeu" and choose "3" to set your IP address. After you enter all the info it will cause you to reboot, but hopefully your network will be working after that.

Finally it's time to fix graphics. startx fails because the display and video card are defined wrong for the VirtualBox emulators. Just run "xf86config" from the shell and it will walk your through setting up a new config.
There are other options that aren't critical, but everything should work if you choose:
wsmouse and just hit enter to choose the default mouse device
I used Generic 101-key PC for the keyboard. It seems to work fine.
For monitor I chose "6" and then "1" for the vertical sync. I'm on a LCD display so this matches up. Yours may need to be different.
From the Video Card Database I chose 0, VESA compatible and set it to the 32768K to match the 32MB I configured in the VM settings
Change display modes as necessary. I left mine default.
Let it save the file to /etc/X11/XF86Config
You can either type "startx" or run "/usr/dina/startmenu" and choose "2" to start the graphics. It should boot into the graphical display now.

The only other issue is that SeaMonkey, which is the web browser, is also using the SV locale. Easiest fix I have found is to launch a "Term" window (little computer icon on the launch bar) and enter "mv .mozilla MozBack". Then open a "Web" window and SeaMonkey should be reset to en-US. (It *may* read the locale from the wscons.conf file setting, but I doubt it). The only thing I believe you lose is the bookmarks, which have a couple links to setting up IRIX installs on a network. If you want them back you have to close all your SeaMonkey windows and open a Term session. Make sure to open SeaMonkey from the "Web" icon at least once after running the mv command but before doing this next step to reset the preferences to default, then enter the following command:

mv MozBack/default/p6j8l230.slt/bookmarks.html ./mozilla/default/*.slt/

When you launch a Web window again your bookmarks should be restored. You can delete the MozBack folder now (rm -rf MozBack) and you should be up and running.

That should be everything you need to get this image moved over to VirtualBox. Thanks to deBug for putting this VM together.

FWIW - both the language changes should work on the VMWare version as well.

Also, if anyone is interested, I had some issues with my existing DHCP server on my LAN conflicting and didn't want to rip everything apart temporarily to make the SGIs work, so I did a Virtual to Physical (V2P) move on this image and installed it as the primary OS on an old laptop I had laying around. The laptop now boots to DINA and I can plug it in directly into the SGI I'm setting up and not have to worry about the conflicts I was having. It was a bit more complicated of a process (a lot of which was due to my drive in the laptop being smaller than the 60G the VM disk image), but I can try to capture what I did if anyone is interested.