added neko_paraview323.tardist to incoming.
Can you please move to beta
Cheers
Comp
Can you please move to beta
Cheers
Comp
The collected works of competentcompton - Page 1
Hi,
I was looking to getting a decent size tape system for backups on my irix boxes. I was looking at maybe a scsi exabyte VXA-2E anyone have any success getting one of these working on irix 6.5.xx?
Any thoughts or experiences appreciated.
Cheers
I was looking to getting a decent size tape system for backups on my irix boxes. I was looking at maybe a scsi exabyte VXA-2E anyone have any success getting one of these working on irix 6.5.xx?
Any thoughts or experiences appreciated.
Cheers
wolflord wrote:
Since I have pretty much any tape drive floating around at work...also where my Octane is, I went and checked it out for you. My octane is running 6.5.19F at the moment(I keep meaning to update it but keep not having time) and I can use the tape drive just fine. Scsi inquiry commands come back fine and mt works just fine as well. I ran a quick tar and that worked out fine too.
Hey thanks for checking that it. Sound like good news I'll probably go ahead and get one.
Thanks again
hi,
I don't use blender but wanted to thank you for keeping software alive and current for Irix.
Applaud your time and effort
Thanks again.
I don't use blender but wanted to thank you for keeping software alive and current for Irix.
Applaud your time and effort
Thanks again.
Hi,
I know that this topic is a bit old but seems that this link no longer works.
Did anyone download it? Or is a new link available?
Cheers
I know that this topic is a bit old but seems that this link no longer works.
Did anyone download it? Or is a new link available?
Cheers
Hi again
although the link did not work, went through the normal download, email route and it is now downloading.
Cheers
although the link did not work, went through the normal download, email route and it is now downloading.
Cheers
Intuition wrote: I'd like to try this out. Is there a demo that would run on the O2 r12k?
Hi,
Yes it is still available I downloaded it for IRIX a few weeks ago. Got to their site at
www.realsoft.fi
and click on Download.
At the bottom you get a dropdown (select SIG IRIX MIPS) and put your email address. You will get an email where you can go an download it for IRIX.
It ran straight away on my octane with no problems at all.
Good Luck
Cheers
Hi,
long time since I first posted this.
I tried an EXABYTE on an irix machine and no luck thus far.
hinv reports
Tape drive: unit 6 on SCSI controller 1: unknown
Then when I try to use anything such as status I get the following
mt -f /dev/mt/tps1d6
No such device
I need to try this with a different machine to see if it a bad tape unit, but so far the EXABYTE is not working??
Any thoughts anyone??
Cheers
long time since I first posted this.
I tried an EXABYTE on an irix machine and no luck thus far.
hinv reports
Tape drive: unit 6 on SCSI controller 1: unknown
Then when I try to use anything such as status I get the following
mt -f /dev/mt/tps1d6
No such device
I need to try this with a different machine to see if it a bad tape unit, but so far the EXABYTE is not working??
Any thoughts anyone??
Cheers
Hi,
Thanks, I was playing with scsiha to see what it was reporting first, and then I thought I would dive into that file.
I wonder is wolfblitz? (sorry I forgot your name
) who said that it worked may have and entry in
/var/sysgen/master.d/scsi for the EXABYTE
It is a vxa-2 BTW.
Thanks for the link
Cheers
Thanks, I was playing with scsiha to see what it was reporting first, and then I thought I would dive into that file.
I wonder is wolfblitz? (sorry I forgot your name
) who said that it worked may have and entry in
/var/sysgen/master.d/scsi for the EXABYTE
It is a vxa-2 BTW.
Thanks for the link
Cheers
Hi,
I have completed a first pass at porting the pixie renderer to irix. I only have a n32 version which I have done initial testing on with a fuel and a origin 300 both running Irix 6.5.30.
Is anyone interested in this being packaged as a nekoware package?
Firstly I have yet to get confirmation from the author that he does not object to this port being distributed to the irix community on nekochan but I would guess that he would not.
Secondly I only have a .tar of the port. Would anyone be willling to help me create a .tardist for nekoware. This is the part that I most dislike doing and so I would very much appreciate if someone would offer to take a binary install and package it up for me.
I know - this last one is a bit lame but I am busy with other things and the tardist packaging os not high on my list of todos.
Cheers
I have completed a first pass at porting the pixie renderer to irix. I only have a n32 version which I have done initial testing on with a fuel and a origin 300 both running Irix 6.5.30.
Is anyone interested in this being packaged as a nekoware package?
Firstly I have yet to get confirmation from the author that he does not object to this port being distributed to the irix community on nekochan but I would guess that he would not.
Secondly I only have a .tar of the port. Would anyone be willling to help me create a .tardist for nekoware. This is the part that I most dislike doing and so I would very much appreciate if someone would offer to take a binary install and package it up for me.
I know - this last one is a bit lame but I am busy with other things and the tardist packaging os not high on my list of todos.
Cheers
Like I said it is compiled and seems to be working ok.
I can tarball it but I don't have time to put a neko package together..
Maybe I will in a few weeks but if someone could offer to package it up that would be really kind of them.
Possibly I could put the tarball out on the neko ftp site?
Cheers
I can tarball it but I don't have time to put a neko package together..
Maybe I will in a few weeks but if someone could offer to package it up that would be really kind of them.
Possibly I could put the tarball out on the neko ftp site?
Cheers
Hi,
ok I will try to put together a .tardist. But for impatient amongst you I am including the .tar.gz of the compiled pixie package.
I installed this into /usr/local/pixie and it will untar into pixie/
Hope this lets you all have a play until I can get the .tardist together.
Cheers
ok I will try to put together a .tardist. But for impatient amongst you I am including the .tar.gz of the compiled pixie package.
I installed this into /usr/local/pixie and it will untar into pixie/
Hope this lets you all have a play until I can get the .tardist together.
Cheers
I just wanted to add that it will not render to a framebuffer with a depth of less than 15.
So for example on my fuel (v10) which I have running at 1600x1200 x8 I can only get file as output.
Whereas when I login into my o300 with Xming it does render to the framebuffer as the visual depth is 24.
I thought I would mention this as pixie does not tell you this is just does nothing and like me you might think it is not working (at least you won't spend an hour trying to debug it like someone I know ...
You will also need OpenEXR and FLTK along with the usual tif libraries etc. from nekochan.
It is supposedly multi-threaded maybe one of you guys witha big iron might like to throw a good number of cpus at it to see how well its multi-threaded model holds up (oh yeah and also to see how the port does also).
Cheers
So for example on my fuel (v10) which I have running at 1600x1200 x8 I can only get file as output.
Whereas when I login into my o300 with Xming it does render to the framebuffer as the visual depth is 24.
I thought I would mention this as pixie does not tell you this is just does nothing and like me you might think it is not working (at least you won't spend an hour trying to debug it like someone I know ...
You will also need OpenEXR and FLTK along with the usual tif libraries etc. from nekochan.
It is supposedly multi-threaded maybe one of you guys witha big iron might like to throw a good number of cpus at it to see how well its multi-threaded model holds up (oh yeah and also to see how the port does also).
Cheers
Well,
It seems that this has become a discussion about BMRT. While I agree that BMRT is a fine tool I wanted to give some simple stats.
I am rendering a simple surface of 1000x1000 points using a fresnel shader on a 600Mhz fuel. The results are as follows
using BMRT it took 660 seconds to render using rendrib.
With pixie using rndr it too 59 seconds. Neither was multi-threaded (no point single cpu fuel in both cases) but pixie was 10x faster for this example.
I know that metrivs are a dung hill. But facts speak for themselves.
Cheers
It seems that this has become a discussion about BMRT. While I agree that BMRT is a fine tool I wanted to give some simple stats.
I am rendering a simple surface of 1000x1000 points using a fresnel shader on a 600Mhz fuel. The results are as follows
using BMRT it took 660 seconds to render using rendrib.
With pixie using rndr it too 59 seconds. Neither was multi-threaded (no point single cpu fuel in both cases) but pixie was 10x faster for this example.
I know that metrivs are a dung hill. But facts speak for themselves.
Cheers
I think that 59s versus 660s is a very nice metric which demonstrates that a more modern tool such a pixie is good for us old SGI die hards. Lets face it we do not have oodles of spare CPU bandwidth to splash around. For this reason I would think that this pixie port is interesting. If nothing else it is a good replacement for BMRT. I was somewhat overwhelmed by the BMRT resistance as everyone on the thread started to talk about BMRT as opposed to pixie.
I think that this port seems to be working well and it certaintly has some pretty impressive performance so far.
Good pedigree I would say.
Cheers
I think that this port seems to be working well and it certaintly has some pretty impressive performance so far.
Good pedigree I would say.
Cheers
paulfred
check you pm
Cheers
check you pm
Cheers
Hi
PM consistent rendered model for further analysis
hope you like
PM consistent rendered model for further analysis
hope you like
Well,
I do not use Maya and never have. I am not aware if it has presets or not.
I have all of the C++ code for this it was generated using
1 - a box Muller uniform random number generator
2 - a Pierson Moskowitz ocean wave spectrum
3 - SGI scsl FFT lib call
4 - VTK calls for visualiziing the wave spectra and random number field
5 - pixie to to the rendering based on the Fresnel reflector as described in Tessendorf (Simulating Ocean Water).
the render is quite basic still no actual sky etc. (hence I added a little more blue content).
Why would I write my own?
1 - just as an exercise in doing these things
2 - more importantly, in a previous life I worked on HF measurement of ocean wave spectra and I am building a library which will hopefully render images from actual measured spectra (mixed swell and wind models etc.)
3 - this can be animated although I have been busy and not able to build put the code together for this.
Hope this helps
Cheers
I do not use Maya and never have. I am not aware if it has presets or not.
I have all of the C++ code for this it was generated using
1 - a box Muller uniform random number generator
2 - a Pierson Moskowitz ocean wave spectrum
3 - SGI scsl FFT lib call
4 - VTK calls for visualiziing the wave spectra and random number field
5 - pixie to to the rendering based on the Fresnel reflector as described in Tessendorf (Simulating Ocean Water).
the render is quite basic still no actual sky etc. (hence I added a little more blue content).
Why would I write my own?
1 - just as an exercise in doing these things
2 - more importantly, in a previous life I worked on HF measurement of ocean wave spectra and I am building a library which will hopefully render images from actual measured spectra (mixed swell and wind models etc.)
3 - this can be animated although I have been busy and not able to build put the code together for this.
Hope this helps
Cheers
I use an dual 400Mhz octane for the actual creation of the surface and to render I have been using a fuel (600Mhz). MIPS compilers.
the image takes about 6 seconds to render but it is only 256 by 256 resolution. This is one of my first images and so this is kept down to speed the development cycle.
Gotta use these machines for something right.
the image takes about 6 seconds to render but it is only 256 by 256 resolution. This is one of my first images and so this is kept down to speed the development cycle.
Gotta use these machines for something right.
Hi,
Well lets start by saying no magic bullets on this one.
I am assuming that you are doing this because you suspect a problem not just for the fun of it?
If this is right then you may have the cause (or symptom) of your problem.
I assume that you have replaced cables and hub/switch and rerun the test - do you get the same result.
Could be a back network interface.
The checksum will normally indicate a problem either with hardware or software and assuming that you are software homogeneous we would expect no error due to bad tcp checksum creation.
Also your post is quite technical in nature and your description a little brief.
Can we step back a moment and get a description of the setup and scenario along with motivation for using ethereal to look at this.
I must say that I only ever used tcpdump when I was simulating satellite delay effects on tcp algorithms but anyhow.
Have you considered plugging a linux box into the network and doing your analysis on all data flow from a third machine to observe traffic to verify this finding?
Cheers
Well lets start by saying no magic bullets on this one.
I am assuming that you are doing this because you suspect a problem not just for the fun of it?
If this is right then you may have the cause (or symptom) of your problem.
I assume that you have replaced cables and hub/switch and rerun the test - do you get the same result.
Could be a back network interface.
The checksum will normally indicate a problem either with hardware or software and assuming that you are software homogeneous we would expect no error due to bad tcp checksum creation.
Also your post is quite technical in nature and your description a little brief.
Can we step back a moment and get a description of the setup and scenario along with motivation for using ethereal to look at this.
I must say that I only ever used tcpdump when I was simulating satellite delay effects on tcp algorithms but anyhow.
Have you considered plugging a linux box into the network and doing your analysis on all data flow from a third machine to observe traffic to verify this finding?
Cheers
Not sure I understand that comment
Hi again,
I would take a conservative engineering approach to this. Given that we do not know if it is a cabling, hub/switch, network card or software issue I would try to get a third machine in there to look at things to confirm your findings.
So we have a problem of communication between A talking to B, or A <-> B.
Are you running ethereal on A or B. If you are running etherreal on A and A has a bad card or cable then ehterreal could be subject to errors also and so is incorrectly reporting problems but those that are not with the source.
I would do the following.
I would place a third machine into the mix and try to recreate the test scenario that does not have the error.
At that point you will have a functioning network.
Then work forwards in order to recreate the error. That is to say that you should introduce components one at a time and test to validate in order to recreate the error. The point at which the error occurs indicates that the last introduced component is at fault.
I know that this might seem all a bit obvious and it is not guaranteed to work but I think that it is a good approach that will probably help.
Cheers
I would take a conservative engineering approach to this. Given that we do not know if it is a cabling, hub/switch, network card or software issue I would try to get a third machine in there to look at things to confirm your findings.
So we have a problem of communication between A talking to B, or A <-> B.
Are you running ethereal on A or B. If you are running etherreal on A and A has a bad card or cable then ehterreal could be subject to errors also and so is incorrectly reporting problems but those that are not with the source.
I would do the following.
I would place a third machine into the mix and try to recreate the test scenario that does not have the error.
At that point you will have a functioning network.
Then work forwards in order to recreate the error. That is to say that you should introduce components one at a time and test to validate in order to recreate the error. The point at which the error occurs indicates that the last introduced component is at fault.
I know that this might seem all a bit obvious and it is not guaranteed to work but I think that it is a good approach that will probably help.
Cheers
That is a perfectly legit point but I was not sure if etherreal would see the bad packet when in promiscuous mode and not be filter it out. I would have hoped the NIC would have dropped it and not interrupted the OS for delivery but I guess you never know. What the app gets and what ethereal sees miht be different - I wasn't sure from the description.
So I was alluding more to the point of being thorough and starting with good known working components which had been tested outside of the environment. It might be a bit tedious but network level problems can involved pretty quickly - although they are an excellent way to learn the fundamentals of ETH, IP, TCP, ARP etc
.
I don't recall if tcpdump/ether does this or not but you can get a packet sniffer and see the bad packet (ethernet header as well). You could see the whole packet and armed with this it might guide you to making a more educated stab at what to diagnose. In fact if you can place a linux box in the mix I had some code lying around that will sniff all the packets.
Cheers
So I was alluding more to the point of being thorough and starting with good known working components which had been tested outside of the environment. It might be a bit tedious but network level problems can involved pretty quickly - although they are an excellent way to learn the fundamentals of ETH, IP, TCP, ARP etc
.
I don't recall if tcpdump/ether does this or not but you can get a packet sniffer and see the bad packet (ethernet header as well). You could see the whole packet and armed with this it might guide you to making a more educated stab at what to diagnose. In fact if you can place a linux box in the mix I had some code lying around that will sniff all the packets.
Cheers
Hi,
that was what confused me slightly. I wasn't sure if you were interested in seeing it or just making a comment on this.
Sure I can post it, it is quite scrappy as it is a work in progress and has lots and lots of debug functions for checking numerical values for integrals and power/energy estimates.
To use it though you need cmake, vtk and scsl along with the mips compilers. I have't tried to compile this with gcc.
If you like I can email it. It might quite messy to post here - we aren't talking about 10s of lines of code.
Cheers
that was what confused me slightly. I wasn't sure if you were interested in seeing it or just making a comment on this.
Sure I can post it, it is quite scrappy as it is a work in progress and has lots and lots of debug functions for checking numerical values for integrals and power/energy estimates.
To use it though you need cmake, vtk and scsl along with the mips compilers. I have't tried to compile this with gcc.
If you like I can email it. It might quite messy to post here - we aren't talking about 10s of lines of code.
Cheers
Hi,
Saw a lot of posts about from 4 or so years ago about changing o300 fans for quieter alternatives.
Seems that the NMB equivalents that are listed are no longer used.
Anyone have any ideas on equivalents that are available to day?
gotta quieten these things down a bit they are driving me nuts.
Cheers
Saw a lot of posts about from 4 or so years ago about changing o300 fans for quieter alternatives.
Seems that the NMB equivalents that are listed are no longer used.
Anyone have any ideas on equivalents that are available to day?
gotta quieten these things down a bit they are driving me nuts.
Cheers
Thanks for the link and all the replies.
From the picture it appears that they are 3 pin which would be
Red +12V
Black 0V
Yellow tachometer
right?
So they could be spliced in are the colours/signals the same for the existing one, I can check but I have to wait to open my unit up.
Cheers
From the picture it appears that they are 3 pin which would be
Red +12V
Black 0V
Yellow tachometer
right?
So they could be spliced in are the colours/signals the same for the existing one, I can check but I have to wait to open my unit up.
Cheers
I looked at that and it seems to have the wires seriously crosed over.
Looking at the connector it would appear that the wiring colors match the pin definition for a standard 3 pin fan
from top down
yellow - tach
red - +12V
black - 0V
(took this from http://pcbheaven.com/wikipages/How_PC_Fans_Work/ )
but the wiring to the fan suggests that the pinout for the sgi mainboard connector is swapped over but why did they keep the colors the same (??)
ho hum. Love to do this but just want to be sure about the pin for the wiring splicing.
Cheers
what is the pin ordering of the
Looking at the connector it would appear that the wiring colors match the pin definition for a standard 3 pin fan
from top down
yellow - tach
red - +12V
black - 0V
(took this from http://pcbheaven.com/wikipages/How_PC_Fans_Work/ )
but the wiring to the fan suggests that the pinout for the sgi mainboard connector is swapped over but why did they keep the colors the same (??)
ho hum. Love to do this but just want to be sure about the pin for the wiring splicing.
Cheers
what is the pin ordering of the
I was just surprised that they so mixed up and that they didn't even chage the wiring color to what it should be.
I was wondering if the picture shown might hae been incorrect.
So is that wiring for the original NMB fan the standard wiring for a NMB fan or is it specific to SGI ?
Anyways I'll just buy some and play till I get it right.
Cheers
I was wondering if the picture shown might hae been incorrect.
So is that wiring for the original NMB fan the standard wiring for a NMB fan or is it specific to SGI ?
Anyways I'll just buy some and play till I get it right.
Cheers
Yeah,
Messing around with colour codes is a bit much to swallow even for SGI non-standards.
I think what was throwing me was that I was labouring under the delusion that I had read that the NMB were plugin replacements. For some reason this threw me somewhat as I assumed that their pin out was the same (My mistake I guess
)
I have ordered the fans and will look at the signals with a DMM/scope and splice them accordingly.
Once done I will post back with sucess/fail.
These fans are rated at 2400 +/-10% which puts their possible low RPM bang on the 2160 RPM L1 fail point.
Lets see what happens
cheesr
Messing around with colour codes is a bit much to swallow even for SGI non-standards.
I think what was throwing me was that I was labouring under the delusion that I had read that the NMB were plugin replacements. For some reason this threw me somewhat as I assumed that their pin out was the same (My mistake I guess
)
I have ordered the fans and will look at the signals with a DMM/scope and splice them accordingly.
Once done I will post back with sucess/fail.
These fans are rated at 2400 +/-10% which puts their possible low RPM bang on the 2160 RPM L1 fail point.
Lets see what happens
cheesr
Hi,
I have a deskside Onyx2 with dual RM10-256 boards and GM16-4.
I want to install a DG5-8.
Does anyone have the screen resolution options with this configuration?
Or even a link to a document that details this config.
Cheers
I have a deskside Onyx2 with dual RM10-256 boards and GM16-4.
I want to install a DG5-8.
Does anyone have the screen resolution options with this configuration?
Or even a link to a document that details this config.
Cheers
Hi,
Got this once before. The SGI doco indicates that this is either CPU or memory.
Had a dual 400 Mhz CPU for a few years then got this. Changed the RAM and had some success.
Then installed a dual 600Mhz CPU and things were wotcking along.
The dreaded flashing bar returned and now I can't boot this thing at all.
I tried swapping back to the dual 400Mhz CPU - no dice
Tried swapping the memory again - no dice.
I am thinking motherboard ?? Does anyoe have any other diagnostics that might help narrow things down as I seem to be in a swap out/swap in mode which is becoming costly.
Cheers
Got this once before. The SGI doco indicates that this is either CPU or memory.
Had a dual 400 Mhz CPU for a few years then got this. Changed the RAM and had some success.
Then installed a dual 600Mhz CPU and things were wotcking along.
The dreaded flashing bar returned and now I can't boot this thing at all.
I tried swapping back to the dual 400Mhz CPU - no dice
Tried swapping the memory again - no dice.
I am thinking motherboard ?? Does anyoe have any other diagnostics that might help narrow things down as I seem to be in a swap out/swap in mode which is becoming costly.
Cheers
Hi,
My o300 seems to be playing up. Upon boot I get the error
NVRAM chacksum is incorrect
Then sometimes the walking of the SCSI chain fails but sometimes it succeeds.
I have tried a reset form L1 but I still get the NVRAM error. Is the NVRAM something that can be replaced?
If so what is the chipset and what is the procedure for doing so?
Any help would be very much appreciated.
Cheers
My o300 seems to be playing up. Upon boot I get the error
NVRAM chacksum is incorrect
Then sometimes the walking of the SCSI chain fails but sometimes it succeeds.
I have tried a reset form L1 but I still get the NVRAM error. Is the NVRAM something that can be replaced?
If so what is the chipset and what is the procedure for doing so?
Any help would be very much appreciated.
Cheers
apologies
obviously chacksum should read checksum - my typo!!
obviously chacksum should read checksum - my typo!!
hi,
This is the output that you rrequested
01c01-L1>serial all
Data Location Value
------------------------------ ------------ --------
Local System Serial Number NVRAM M2004389
Reference System Serial Number NVRAM M2004389
Local Brick Serial Number EEPROM MPD712
Reference Brick Serial Number NVRAM MPD712
EEPROM Product Name Serial Part Number Rev T/W
---------- -------------- ------------- -------------------- --- ------
NODE IP45_4CPU MPD712 030_1797_001 B 00
IO8 IO8 MPA366 030_1673_004 C 00
EEPROM JEDEC-SPD Info Part Number Rev Speed SGI
---------- ------------------------ ------------------ ---- ------ --------
DIMM 0 CE000000000000000C0C4700 M3 46L2820BT2-CA0 2B 10.0 N/A
DIMM 2 7F94FFFFFFFFFFFF9374D80D SM57264DSGI100C3 00FF 8.0 N/A
DIMM 1 CE000000000000000C0A4700 M3 46L2820BT2-CA0 2B 10.0 N/A
DIMM 3 7F94FFFFFFFFFFFFB374D80D SM57264DSGI100C3 00FF 8.0 N/A
001c01-L1>log
02/08/13 03:37:23 power up (PANEL)
02/08/13 03:37:30 reset again MIPS
02/08/13 03:54:11 power down (COMMAND)
02/08/13 03:55:25 SMP unregistering events
02/08/13 03:55:25 UNREG: 30005140 0 4
02/08/13 03:55:26 SMP-R: UART:UART_NO_CONNECTION
02/08/13 04:05:05 power up (PANEL)
02/08/13 04:05:13 reset again MIPS
02/08/13 04:07:12 power down (PANEL)
02/08/13 04:08:10 power up (PANEL)
02/08/13 04:08:18 reset again MIPS
02/08/13 04:08:26 SCC WR 0 (len=6) - UART:UART_TIMEOUT
02/08/13 06:19:43 power down (COMMAND)
02/08/13 06:20:11 SMP unregistering events
02/08/13 06:20:11 UNREG: 30005140 0 4
02/08/13 06:20:12 SMP-R: UART:UART_NO_CONNECTION
02/09/13 05:34:07 power up (PANEL)
02/09/13 05:34:15 reset again MIPS
02/09/13 05:34:50 power down (PANEL)
02/09/13 05:35:24 power up (PANEL)
02/09/13 05:35:32 reset again MIPS
02/09/13 05:35:39 SCC WR 0 (len=6) - UART:UART_TIMEOUT
02/09/13 05:37:31 power down (PANEL)
02/09/13 05:37:32 power up (PANEL)
02/09/13 05:37:40 reset again MIPS
02/09/13 05:41:11 power down (COMMAND)
02/09/13 05:42:04 power up (PANEL)
02/09/13 05:42:12 reset again MIPS
02/09/13 05:42:25 SCC WR 0 (len=6) - UART:UART_TIMEOUT
02/09/13 05:49:34 power down (COMMAND)
02/09/13 05:49:50 SMP unregistering events
02/09/13 05:49:50 UNREG: 30005140 0 4
02/09/13 05:49:51 SMP-R: UART:UART_NO_CONNECTION
02/13/13 03:13:18 power up (PANEL)
02/13/13 03:13:26 reset again MIPS
02/13/13 03:13:37 SCC WR 0 (len=6) - UART:UART_TIMEOUT
02/13/13 03:15:56 reset (COMMAND)
02/13/13 03:18:59 power down (COMMAND)
02/13/13 03:19:14 power up (PANEL)
02/13/13 03:19:22 reset again MIPS
02/13/13 03:22:54 power down (PANEL)
02/13/13 03:22:55 power up (PANEL)
02/13/13 03:23:03 reset again MIPS
02/13/13 03:24:54 power down (PANEL)
02/13/13 03:25:36 SMP unregistering events
02/13/13 03:25:36 UNREG: 30005140 0 4
02/13/13 03:25:37 SMP-R: UART:UART_NO_CONNECTION
02/17/13 04:02:11 power up (PANEL)
02/17/13 04:02:19 reset again MIPS
02/17/13 04:03:52 power down (PANEL)
02/17/13 04:03:54 power up (PANEL)
02/17/13 04:04:02 reset again MIPS
Hope that this gives you some insight.
Can't say that at this point in time it means much to me. Any insight you can provide would be useful.
Cheers
This is the output that you rrequested
01c01-L1>serial all
Data Location Value
------------------------------ ------------ --------
Local System Serial Number NVRAM M2004389
Reference System Serial Number NVRAM M2004389
Local Brick Serial Number EEPROM MPD712
Reference Brick Serial Number NVRAM MPD712
EEPROM Product Name Serial Part Number Rev T/W
---------- -------------- ------------- -------------------- --- ------
NODE IP45_4CPU MPD712 030_1797_001 B 00
IO8 IO8 MPA366 030_1673_004 C 00
EEPROM JEDEC-SPD Info Part Number Rev Speed SGI
---------- ------------------------ ------------------ ---- ------ --------
DIMM 0 CE000000000000000C0C4700 M3 46L2820BT2-CA0 2B 10.0 N/A
DIMM 2 7F94FFFFFFFFFFFF9374D80D SM57264DSGI100C3 00FF 8.0 N/A
DIMM 1 CE000000000000000C0A4700 M3 46L2820BT2-CA0 2B 10.0 N/A
DIMM 3 7F94FFFFFFFFFFFFB374D80D SM57264DSGI100C3 00FF 8.0 N/A
001c01-L1>log
02/08/13 03:37:23 power up (PANEL)
02/08/13 03:37:30 reset again MIPS
02/08/13 03:54:11 power down (COMMAND)
02/08/13 03:55:25 SMP unregistering events
02/08/13 03:55:25 UNREG: 30005140 0 4
02/08/13 03:55:26 SMP-R: UART:UART_NO_CONNECTION
02/08/13 04:05:05 power up (PANEL)
02/08/13 04:05:13 reset again MIPS
02/08/13 04:07:12 power down (PANEL)
02/08/13 04:08:10 power up (PANEL)
02/08/13 04:08:18 reset again MIPS
02/08/13 04:08:26 SCC WR 0 (len=6) - UART:UART_TIMEOUT
02/08/13 06:19:43 power down (COMMAND)
02/08/13 06:20:11 SMP unregistering events
02/08/13 06:20:11 UNREG: 30005140 0 4
02/08/13 06:20:12 SMP-R: UART:UART_NO_CONNECTION
02/09/13 05:34:07 power up (PANEL)
02/09/13 05:34:15 reset again MIPS
02/09/13 05:34:50 power down (PANEL)
02/09/13 05:35:24 power up (PANEL)
02/09/13 05:35:32 reset again MIPS
02/09/13 05:35:39 SCC WR 0 (len=6) - UART:UART_TIMEOUT
02/09/13 05:37:31 power down (PANEL)
02/09/13 05:37:32 power up (PANEL)
02/09/13 05:37:40 reset again MIPS
02/09/13 05:41:11 power down (COMMAND)
02/09/13 05:42:04 power up (PANEL)
02/09/13 05:42:12 reset again MIPS
02/09/13 05:42:25 SCC WR 0 (len=6) - UART:UART_TIMEOUT
02/09/13 05:49:34 power down (COMMAND)
02/09/13 05:49:50 SMP unregistering events
02/09/13 05:49:50 UNREG: 30005140 0 4
02/09/13 05:49:51 SMP-R: UART:UART_NO_CONNECTION
02/13/13 03:13:18 power up (PANEL)
02/13/13 03:13:26 reset again MIPS
02/13/13 03:13:37 SCC WR 0 (len=6) - UART:UART_TIMEOUT
02/13/13 03:15:56 reset (COMMAND)
02/13/13 03:18:59 power down (COMMAND)
02/13/13 03:19:14 power up (PANEL)
02/13/13 03:19:22 reset again MIPS
02/13/13 03:22:54 power down (PANEL)
02/13/13 03:22:55 power up (PANEL)
02/13/13 03:23:03 reset again MIPS
02/13/13 03:24:54 power down (PANEL)
02/13/13 03:25:36 SMP unregistering events
02/13/13 03:25:36 UNREG: 30005140 0 4
02/13/13 03:25:37 SMP-R: UART:UART_NO_CONNECTION
02/17/13 04:02:11 power up (PANEL)
02/17/13 04:02:19 reset again MIPS
02/17/13 04:03:52 power down (PANEL)
02/17/13 04:03:54 power up (PANEL)
02/17/13 04:04:02 reset again MIPS
Hope that this gives you some insight.
Can't say that at this point in time it means much to me. Any insight you can provide would be useful.
Cheers
Hi,
thanks to all who have relied. I pulled my IO8 and found the same yellow battery with the same part number on my o300.
I am going to go with that first as it seems to have fixed most people's issues.
There is another NVRAM chip also - a DALLAS DS1742W-120
Any idea why there are two and when they are used. I am guessing that they are used by the L1/L2 and/or the system at different points.
I'll post back when I have my new yellow battery.
thanks again.
Cheers
thanks to all who have relied. I pulled my IO8 and found the same yellow battery with the same part number on my o300.
I am going to go with that first as it seems to have fixed most people's issues.
There is another NVRAM chip also - a DALLAS DS1742W-120
Any idea why there are two and when they are used. I am guessing that they are used by the L1/L2 and/or the system at different points.
I'll post back when I have my new yellow battery.
thanks again.
Cheers
HI,
I am running 7.3.20m and my compilers are at 7.3.4m
Unfortunately I only have a development tools disk for 7.3.1.2m. I think that this is affecting my dbx as I get lots of errors about cpu tye and memory mappings.
{edited commercial software request}
Cheers
I am running 7.3.20m and my compilers are at 7.3.4m
Unfortunately I only have a development tools disk for 7.3.1.2m. I think that this is affecting my dbx as I get lots of errors about cpu tye and memory mappings.
{edited commercial software request}
Cheers
Hi,
I have a piece of code that I was trying to compile and debug with gcc 4.7 and gdb 6.3.
Maybe these two versions are not compatible?
The problem is that when debugging code compiled with the -g option the debugger does not stop in main.
Rather it stops at a line of code that is about 1/3 of the way through the source file.
Anyone else seen this?
Cheers
I have a piece of code that I was trying to compile and debug with gcc 4.7 and gdb 6.3.
Maybe these two versions are not compatible?
The problem is that when debugging code compiled with the -g option the debugger does not stop in main.
Rather it stops at a line of code that is about 1/3 of the way through the source file.
Anyone else seen this?
Cheers
yes I did
under gdb I used
break main
but also I ran it as
gdb -dbx
and used stop in main
both incorrectly stopped at the same line in the code.
Cheers
under gdb I used
break main
but also I ran it as
gdb -dbx
and used stop in main
both incorrectly stopped at the same line in the code.
Cheers
Hi,
My main octane is a dual 600 Mhz with V6 and 2.5GB of RAM.
It has a Xbox 1.3 and I also replaced the NVRAM chip recently.
Thing has problems booting from cold. I always seem to get a flashing red bar (which from the doco is RAM/CPU).
Changed the CPU back to dual 400Mhz and problem still persists.
Swapped the RAM many times and still the problem.
The only fix seems to be - remove the mobo and push it back in.
Doesn't always work but after a few attempts it seems to. Once the machine boots and I have used it for a while I can shut it down and reboot it without problem.
My question is
is this a problem with the mobo, Xbox (possibly being overloaded by the configuration) or just bad connectors ?
Best solution?
New Xbow, mobo or any other ideas?
Cheers
My main octane is a dual 600 Mhz with V6 and 2.5GB of RAM.
It has a Xbox 1.3 and I also replaced the NVRAM chip recently.
Thing has problems booting from cold. I always seem to get a flashing red bar (which from the doco is RAM/CPU).
Changed the CPU back to dual 400Mhz and problem still persists.
Swapped the RAM many times and still the problem.
The only fix seems to be - remove the mobo and push it back in.
Doesn't always work but after a few attempts it seems to. Once the machine boots and I have used it for a while I can shut it down and reboot it without problem.
My question is
is this a problem with the mobo, Xbox (possibly being overloaded by the configuration) or just bad connectors ?
Best solution?
New Xbow, mobo or any other ideas?
Cheers