Setting up the CMOS clock:
datecommand like so:
exitand SLES9 should boot without issue.
neonwas also available on that same server here. Simply install with a
rpm -i neon-0.24.7-6.1.1.ia64.rpm.
./autogen.sh, I ran
./configurefrom within my newly installed Subversion source code only to get this warning: [shell] configure: WARNING: Detected SWIG version 1.1 (Patch 5) configure: WARNING: This is not compatible with Subversion configure: WARNING: Subversion can use SWIG versions 1.3.19, 1.3.20, 1.3.21 configure: WARNING: or 1.3.24 or later [/shell] SLES SP3 apparently only has 1.1 (Patch 5) bundled with it, but fortunately the source code is readily available for SWIG. Keeping the age of Subversion 1.1.4, I chose to download 18.104.22.168 from SourceForge, extracting it with the following commands:
configurefor Subversion, I was pleasantly surprised to find everything compiled and installed properly. Unfamiliar with how to package my own rpm (it's on my todo list), the only thing I can provide folks is locally hosted direct links to the files you'll need:
001?01-L1>log 04/14/12 10:54:46 L1 booting 1.44.0 04/14/12 10:54:49 ** fixing invalid SSN value 04/14/12 10:54:49 ** fixing BSN mismatch 04/14/12 11:13:53 L1 booting 1.44.0So, good it auto-fixed the invalid SSN and BSN mismatch.
001?01-L1>brick rack: 001, slot: 01, partition: none, type: Unknown [2MB flash], serial:MRH006, source: NVRAMGood again, it sees the brick, but doesn't know what it is. Then tried:
001?01-L1>brick type C brick type changed (nvram) (takes effect on next L1 reboot/power cycle) 001?01-L1>reboot_l1Upon rebooting the L1, still not avail. Going to have to get creative with this problem...
scsiha -p 0;on IRIX. Immediately following that running a
4 500 MHZ IP35 Processors CPU: MIPS R14000 Processor Chip Revision: 1.4 FPU: MIPS R14010 Floating Point Chip Revision: 1.4 Main memory size: 2048 Mbytes Instruction cache size: 32 Kbytes Data cache size: 32 Kbytes Secondary unified instruction/data cache size: 2 Mbytes Integral SCSI controller 3: Version Fibre Channel QL2200A Integral SCSI controller 0: Version QL12160, low voltage differential Disk drive: unit 1 on SCSI controller 0 Disk drive: unit 2 on SCSI controller 0 Integral SCSI controller 1: Version QL12160, low voltage differential IOC3/IOC4 serial port: tty3 IOC3/IOC4 serial port: tty4 Integral Fast Ethernet: ef0, version 1, module 001c16, pci 4 IOC3/IOC4 external interrupts: 1 USB controller: type OHCIIRIX found the drive on Controller 0, so I was ready to begin the cloning procedure. Following these steps, 10 minutes later, I had my data copied to the Fujitsu drive and was ready to become my new root drive on my Origin 300. Pretty cool Silicon Graphics built that in, cloning a Windows system drive is a huge pain natively. Although there is a sweet tool by Arconis if you own a Western Digital on there site, here for free. I used that when I moved off of my RAID 0 stripe of 2 Western Digital Black 500gb drives to the 1TB versions and didn't feel like reinstalling all of my applications including the ones that had limited activations without having to call the company to get them to reset the activations. Maxtor, you've been good from 2004-2008 and from 2011-2012: [caption id="attachment_976" align="aligncenter" width="225" caption="Maxtor ATLAS 15k 36gb drive, finally being retired"][/caption]
env off. This is dangerous though as the server will not shutdown automatically if a fan fails or the server overheats. Having said that, it came to my attention that IRIX does not install a Serial/Terminal client by default. The common
cuis on the IRIX 6.5 Foundation CD 1 disk. Turn on the Subsystems Only in the IRIX Software Manager and scroll down until you see it. Chances are you're not running a base 6.5 install so you'll also need the first disk of your overlays (6.5.30 Overlay CD 1 in my case) in order to install it to resolve the package conflicts. After installing you may receive a "CONNECT FAILURE: NO DEVICES AVAILABLE". Open up
vior your favorite text editor and open up
/etc/uucp/DevicesAdd in a line:
Direct ttyd2 - 38400 directMake sure the spaces are there. You can also try setting it up via the Serial Manager under the System Manager application. Afterwards, simply running:
cu -l /dev/ttyd2 -s38400Allowed me into my L1 console to turn off environment monitoring. Then hit
Control + Dto get back into the PROM Monitor and hit "1" to start IRIX.
gmemusage). I tested it twice to make sure, but a word to the wise, do not run Quake 2 in a window if you only have 128mb of memory. I'll test it out with 192mb shortly. In case anyone was interested here is an updated list: 320x240 128mb - 180mhz R5000SC - 4.1 / 169.6 seconds 1024mb - 180mhz R5000SC - 14.9 / 46.3 seconds 1024mb - 300mhz R5200SC - 18.8 / 36.7 seconds 640x480 128mb - 180mhz R5000SC - 12.2 / 56.3 seconds 1024mb - 180mhz R5000SC - 12.4fps / 55.4 seconds 1024mb - 300mhz R5200SC - 14.5fps / 47.4 seconds 800x600 128mb - 180mhz R5000SC - 10.2 / 67.3 seconds 1024mb - 180mhz R5000SC - 10.3 / 67.2 seconds 1024mb - 300mhz R5200SC - 11.7 / 58.7 seconds
CRIMEgraphics core is tightly integrated with the CPU. Using the following commands on the console:
timedemo 1 map demo1.dm2Here's the results: 320x240 180mhz - 14.9 / 46.3 seconds 300mhz - 18.8 / 36.7 seconds 640x480 180mhz - 12.4fps / 55.4 seconds 300mhz - 14.5fps / 47.4 seconds 800x600 180mhz - 10.3 / 67.2 seconds 300mhz - 11.7 / 58.7 seconds Kind of surprised at the results, I'll be testing my 180mhz R5000PC vs 180mhz R5000SC shortly to see what if any difference the Level 2 cache makes.
SDLQuakeand running into x86 assembly, UDP and linking issues I decided to try the "official" IRIX port from SGI. Oddly enough, Quake II runs at 640x480x16 with full textures on my Silicon Graphics O2. Feeling adventurous, I wanted to see if it would play with the x86 Windows 3.20 version. Sure enough, I was able to play with an IRIX hosted game (it would probably work the other way as well) with my Windows 7 workstation. [caption id="attachment_927" align="aligncenter" width="300" caption="Quake II on my O2"][/caption] On a side note, I got
SDLQuaketo get all the way to the linking stage before giving up on it. For whatever reason using
-lSDLwas not including what looks like X11 or OpenAL libraries. I included both of those libraries and was still getting the errors.
viand start editing on my SGI O2 faster than I could open up
Visual Studio 2010, then browse to the project and start coding on my Phenom II system. It saddens me to know that so many people will frown upon not top of the line specs even if they are only going to use 50% of the power available. Gluttony it seems has taken hold of consumers...
Media Error: Unrecovered data block read errorsGoogling the error (and just intuition), the hard drive I spent all week prepping, installing and getting frustrated on is on it's way out. Luckily I remembered from years back upgrading a drive in my origin Silicon Graphics Octane you can pretty easily clone a root drive. Pulled up this link over at the SGI Depot. Followed the steps, tons of errors followed when copying. Crossing my fingers upon pulling out the original installation drive...