|
|
|
|
| Author |
Message |
Kosta Xonis
Guest
|
 Posted: Tue Jan 16, 2007 7:03 am Post subject: Problem with Blade 1000 |
 |
|
Hi,
I am sorry to bother again, but I got a Blade 1000 recently, and it does
not come up, the only things it does are:
- Logo lights (Just means, that power is applied),
- I can hear the HDDs spin up, and then it makes a deep dark beep after
each,
- the System fans speed up,
- then the expected light beep, but nothing else happens
No flashing Keyboard LEDs, but Keyboard OK, tested with a Blade 100, and
even with a PeeCee.
Trying to exit with L1-A and "boot net" gives no response at the switch.
I also had a monitor attached, also no success, 13W3->VGA is OK, tested
on other HW.
Sadly is, I have no matching serial cable yet, and the Blade 1000
Service Manual I have does not refer to which jumper is used to
configure the serials as RS232, AFAIK, they are defaulted to RS423.
Also tried to set NVRAM back by "double-clicking" the power button, but
no effect either.
Did I miss anything ? The Service Manual says nothing about a beep in
case of an error, and the troubleshooting section is not really a help.
Hope some light out there for me...
Thanks a lot !!!
--
XAKiChaos (desperate !!) |
|
| Back to top |
|
 |
Fix your Windows Problems - FAST.
FREE Safe Scan Registry Check. Locate & Fix Errors in Minutes!
|
|
Kosta Xonis
Guest
|
| Posted: Tue Jan 16, 2007 7:05 am Post subject: Re: Problem with Blade 1000 |
|
|
CJT schrieb:
| Quote: | Kosta Xonis wrote:
[...]
You don't have a serial cable, and only tried it with a monitor briefly,
if I understand you correctly.
|
No, not briefly, I have been patient for half an hour or so. Could it be
possible, it has been used in a dual head config, and the now
"missing"/removed graphics was set as primary ?? OTOH, setting the NVRAM
to deafults via double-click on the power button should have had the
desired effect. Thre is one Creator in UPA0 present.
| Quote: |
So how do you know it doesn't "come up?" What do you even mean by that?
Does its disk drive contain a viable OS? Many vendors zero disks on
used equipment (as they probably should).
|
That is clear and expected, then at least it should stop at the OBPs
"ok" and wait for input like "boot net", or if it has been set up to
automagically boot from net the switch should show any activity on the
port used by the Blade 1000. This is not the case. I also snooped the
network segment, and nothing happened. I filtered out all known MACs.
| Quote: |
BTW, not all 13W3 adapters are created equal. Some are made for SGI,
IBM, or HP equipment, which can have different pinouts.
|
This adapter is definitely a matching one, because I used it on another
Creator, and there it works, that still leaves the question, if the
Blades Creator is working or not (defective. But thats another issue.)
--
XAKiChaos (desperate !! & tired @04:40AM) |
|
| Back to top |
|
|
CJT
Guest
|
| Posted: Tue Jan 16, 2007 7:08 am Post subject: Re: Problem with Blade 1000 |
|
|
Kosta Xonis wrote:
| Quote: | CJT schrieb:
Kosta Xonis wrote:
[...]
You don't have a serial cable, and only tried it with a monitor briefly,
if I understand you correctly.
No, not briefly, I have been patient for half an hour or so. Could it be
possible, it has been used in a dual head config, and the now
"missing"/removed graphics was set as primary ??
|
I think that's possible.
OTOH, setting the NVRAM
| Quote: | to deafults via double-click on the power button should have had the
desired effect. Thre is one Creator in UPA0 present.
I've never tried that double-click, so don't know whether it works. |
| Quote: |
So how do you know it doesn't "come up?" What do you even mean by that?
Does its disk drive contain a viable OS? Many vendors zero disks on
used equipment (as they probably should).
That is clear and expected, then at least it should stop at the OBPs
"ok" and wait for input like "boot net", or if it has been set up to
automagically boot from net the switch should show any activity on the
port used by the Blade 1000.
|
Or, if it's set to go to ttya or ttyb, the "ok" might be there.
This is not the case. I also snooped the
| Quote: | network segment, and nothing happened. I filtered out all known MACs.
BTW, not all 13W3 adapters are created equal. Some are made for SGI,
IBM, or HP equipment, which can have different pinouts.
This adapter is definitely a matching one, because I used it on another
Creator, and there it works, that still leaves the question, if the
Blades Creator is working or not (defective. But thats another issue.)
|
--
The e-mail address in our reply-to line is reversed in an attempt to
minimize spam. Our true address is of the form che...@prodigy.net. |
|
| Back to top |
|
|
Rich Teer
Guest
|
| Posted: Tue Jan 16, 2007 7:11 am Post subject: Re: Problem with Blade 1000 |
|
|
On Tue, 16 Jan 2007, Kosta Xonis wrote:
| Quote: | Sadly is, I have no matching serial cable yet, and the Blade 1000
Service Manual I have does not refer to which jumper is used to
configure the serials as RS232, AFAIK, they are defaulted to RS423.
|
That doesn't matter: RS423 has the same signals as RS232, except they're
at 5V rather than 12V. In most situations these days, they're essentially
interchangeable. WHich is the long way of saying that you don't need
to change the jumper. :-)
--
Rich Teer, SCSA, SCNA, SCSECA, OpenSolaris CAB member
President,
Rite Online Inc.
Voice: +1 (250) 979-1638
URL: http://www.rite-group.com/rich |
|
| Back to top |
|
|
CJT
Guest
|
| Posted: Tue Jan 16, 2007 7:21 am Post subject: Re: Problem with Blade 1000 |
|
|
Kosta Xonis wrote:
| Quote: | Hi,
I am sorry to bother again, but I got a Blade 1000 recently, and it does
not come up, the only things it does are:
- Logo lights (Just means, that power is applied),
- I can hear the HDDs spin up, and then it makes a deep dark beep after
each,
- the System fans speed up,
- then the expected light beep, but nothing else happens
No flashing Keyboard LEDs, but Keyboard OK, tested with a Blade 100, and
even with a PeeCee.
Trying to exit with L1-A and "boot net" gives no response at the switch.
I also had a monitor attached, also no success, 13W3->VGA is OK, tested
on other HW.
Sadly is, I have no matching serial cable yet, and the Blade 1000
Service Manual I have does not refer to which jumper is used to
configure the serials as RS232, AFAIK, they are defaulted to RS423.
Also tried to set NVRAM back by "double-clicking" the power button, but
no effect either.
Did I miss anything ? The Service Manual says nothing about a beep in
case of an error, and the troubleshooting section is not really a help.
Hope some light out there for me...
Thanks a lot !!!
You don't have a serial cable, and only tried it with a monitor briefly, |
if I understand you correctly.
So how do you know it doesn't "come up?" What do you even mean by that?
Does its disk drive contain a viable OS? Many vendors zero disks on
used equipment (as they probably should).
BTW, not all 13W3 adapters are created equal. Some are made for SGI,
IBM, or HP equipment, which can have different pinouts.
--
The e-mail address in our reply-to line is reversed in an attempt to
minimize spam. Our true address is of the form che...@prodigy.net. |
|
| Back to top |
|
|
|
|
Gerry Sinkiewicz
Guest
|
| Posted: Fri Jan 26, 2007 9:05 am Post subject: Re: Problem with Blade 1000 |
|
|
"CJT" <abujlehc@prodigy.net> wrote in message
news:45AC4C5A.4020709@prodigy.net...
| Quote: | Kosta Xonis wrote:
CJT schrieb:
Kosta Xonis wrote:
[...]
You don't have a serial cable, and only tried it with a monitor briefly,
if I understand you correctly.
No, not briefly, I have been patient for half an hour or so. Could it be
possible, it has been used in a dual head config, and the now
"missing"/removed graphics was set as primary ??
I think that's possible.
OTOH, setting the NVRAM
to deafults via double-click on the power button should have had the
desired effect. Thre is one Creator in UPA0 present.
I've never tried that double-click, so don't know whether it works.
So how do you know it doesn't "come up?" What do you even mean by that?
Does its disk drive contain a viable OS? Many vendors zero disks on
used equipment (as they probably should).
That is clear and expected, then at least it should stop at the OBPs "ok"
and wait for input like "boot net", or if it has been set up to
automagically boot from net the switch should show any activity on the
port used by the Blade 1000.
Or, if it's set to go to ttya or ttyb, the "ok" might be there.
This is not the case. I also snooped the
network segment, and nothing happened. I filtered out all known MACs.
BTW, not all 13W3 adapters are created equal. Some are made for SGI,
IBM, or HP equipment, which can have different pinouts.
This adapter is definitely a matching one, because I used it on another
Creator, and there it works, that still leaves the question, if the
Blades Creator is working or not (defective. But thats another issue.)
--
The e-mail address in our reply-to line is reversed in an attempt to
minimize spam. Our true address is of the form che...@prodigy.net.
|
I have had to set-defaults after the quick double click when you hear the
beep.
I works fine. You do need to be quck with the double click though.
After setting defaults everything worked fine just like you would expect.
Maybe other problems. Is it a Sun monitor, like they say not all 13W3's are
equal? |
|
| Back to top |
|
|
Guest
|
| Posted: Fri Jan 26, 2007 11:06 pm Post subject: Re: Problem with Blade 1000 |
|
|
On Jan 15, 8:11 pm, Kosta Xonis <ChaosKo...@web.de> wrote:
| Quote: | Hi,
I am sorry to bother again, but I got a Blade 1000 recently, and it does
not come up, the only things it does are:
- Logo lights (Just means, that power is applied),
- I can hear the HDDs spin up, and then it makes a deep dark beep after
each,
- the System fans speed up,
- then the expected light beep, but nothing else happens
No flashing Keyboard LEDs, but Keyboard OK, tested with a Blade 100, and
even with a PeeCee.
Trying to exit with L1-A and "boot net" gives no response at the switch.
I also had a monitor attached, also no success, 13W3->VGA is OK, tested
on other HW.
Sadly is, I have no matching serial cable yet, and the Blade 1000
Service Manual I have does not refer to which jumper is used to
configure the serials as RS232, AFAIK, they are defaulted to RS423.
Also tried to set NVRAM back by "double-clicking" the power button, but
no effect either.
Did I miss anything ? The Service Manual says nothing about a beep in
case of an error, and the troubleshooting section is not really a help.
Hope some light out there for me...
Thanks a lot !!!
--
XAKiChaos (desperate !!)
|
If the POST levels are set to max the POST can take as much as 30
minutes for a dual 750 with 2gb of memory according to the Sun docs for
a Blade 1000 |
|
| Back to top |
|
|
Kosta Xonis
Guest
|
| Posted: Sun Jan 28, 2007 3:58 pm Post subject: Re: Problem with Blade 1000 |
|
|
Gerry Sinkiewicz schrieb:
| Quote: | "CJT" <abujlehc@prodigy.net> wrote in message
news:45AC4C5A.4020709@prodigy.net...
Kosta Xonis wrote:
CJT schrieb:
Kosta Xonis wrote:
[...]
You don't have a serial cable, and only tried it with a monitor briefly,
if I understand you correctly.
No, not briefly, I have been patient for half an hour or so. Could it be
possible, it has been used in a dual head config, and the now
"missing"/removed graphics was set as primary ??
I think that's possible.
OTOH, setting the NVRAM
to deafults via double-click on the power button should have had the
desired effect. Thre is one Creator in UPA0 present.
I've never tried that double-click, so don't know whether it works.
So how do you know it doesn't "come up?" What do you even mean by that?
Does its disk drive contain a viable OS? Many vendors zero disks on
used equipment (as they probably should).
That is clear and expected, then at least it should stop at the OBPs "ok"
and wait for input like "boot net", or if it has been set up to
automagically boot from net the switch should show any activity on the
port used by the Blade 1000.
Or, if it's set to go to ttya or ttyb, the "ok" might be there.
This is not the case. I also snooped the
network segment, and nothing happened. I filtered out all known MACs.
BTW, not all 13W3 adapters are created equal. Some are made for SGI,
IBM, or HP equipment, which can have different pinouts.
This adapter is definitely a matching one, because I used it on another
Creator, and there it works, that still leaves the question, if the
Blades Creator is working or not (defective. But thats another issue.)
--
The e-mail address in our reply-to line is reversed in an attempt to
minimize spam. Our true address is of the form che...@prodigy.net.
I have had to set-defaults after the quick double click when you hear the
beep.
I works fine. You do need to be quck with the double click though.
After setting defaults everything worked fine just like you would expect.
Maybe other problems. Is it a Sun monitor, like they say not all 13W3's are
equal?
|
That is impossible, because as I said, it was tested with other HW
(Ultra 80, with a creator).
Anyways, I managed to get a matching serial cable, and there was the
"solution"...
On a tip connection bad Blade 1000 said,
<quote>
| Quote: |
@(#)OBP 4.0.40 2000/11/29 18:02
Clearing TLBs Done
Power-On Reset
Executing Power On SelfTest
{{0ecuting Power On SelfTest
8:0}@(#)POST, v4.1.6 10/03/2000 02:46 PM
{1}
{0}* Test CPU present
{1}@(#)POST, v4.1.6 10/03/2000 02:46 PM
{1}* Test CPU present
{0}Soft POR to the whole system
{1}Soft POR to the whole system
{0}* Configure I2C controller 0
{0}* Configure I2C controller 1
{0}* I2C Controller Loopback Test
{0}* Read JTag IDs of all ASICs
{0} BBC JTag ID: 1483203b
{0} SCSI JTag ID: 15060045
{0} I chip JTag ID: d1e203b
{0} RIO JTag ID: 13e5d03b
{0} Schizo JTag ID: 1824c06d
{0} CPMS JTag ID: 1142903b
{0} CPMS JTag ID: 1142903b
{0} CPMS JTag ID: 1142903b
{0} CPMS JTag ID: 1142903b
{0} CPMS JTag ID: 1142903b
{0} CPMS JTag ID: 1142903b
{0}* Read JTag ID of FCAL
{0} FC-AL JTag ID: 1000a12f
{0}* Probing Seeprom on DIMMs and CPU modules
{0}CPU0 Sensor package temperature 0 oC
{0}ERROR: TEST = * Probing Seeprom on DIMMs and CPU modules TESTID = 96
{0}H/W under test = I2C/Serial Proms
{0} Slave not responded
{0} Cannot read thermal sensor on CPU1 module
{0} I2C bus 5
{0} I2C address 98
{0}* Probing Seeprom on DIMMs and CPU modules FAILED
{0}POST failed
{0}POST_END
@(#)OBP 4.0.40 2000/11/29 18:02
Clearing TLBs Done
POST Results: Cpu 0
%o0 0000.0000.0000.0001
%o1 0000.07ff.f015.0530
%o2 0000.0000.0000.0000
POST Results: Cpu 1
%o0 0000.0000.0000.0001
%o1 0000.07ff.f015.0530
%o2 0000.0000.0000.0000
Membase: 0000.0000.0000.0000
MemSize: 0000.0000.0010.0000
Init CPU arrays Done
Init E$ tags Done
Setup TLB Done
MMUs ON
Copy Done
PC = 0000.07ff.f000.3644
PC = 0000.0000.0000.36b8
Decompressing Done
Size = 0000.0000.0006.d9a0
ttya initialized
Start Reason: Initialize Machine
Configuring the machine:
ERROR: get-sys-i2c-config: SYSTEM FRUprom is invalid or inaccessible!
Powering off system!
/quote |
and powers off, as told. The quote is all I get via the tip connection.
I think I am %&$%&, right ?? Dead Mainboard component ?
I do not think, there might be an FRU involved I could just swap to fix
it. I already permuted RAM and CPUs to no difference.
Anyway then it is a DOA, it will be right back to its seller next day... :-(
Thanks for your help !!
--
XAKiChaos
(disappointed, now his B1K seems to be dead) |
|
| Back to top |
|
|
gerryt
Guest
|
| Posted: Mon Jan 29, 2007 5:31 am Post subject: Re: Problem with Blade 1000 |
|
|
On Jan 28, 1:58 am, Kosta Xonis <ChaosKo...@web.de> wrote:
much snippage
| Quote: | On a tip connection bad Blade 1000 said,
@(#)OBP 4.0.40 2000/11/29 18:02
Clearing TLBs Done
Power-On Reset
Executing Power On SelfTest
{{0ecuting Power On SelfTest
8:0}@(#)POST, v4.1.6 10/03/2000 02:46 PM
|
etc. I'm not getting anything like this from my Blade 1000
I do have a more recent OBP:
@(#)OBP 4.13.0 2004/01/19 18:27
and these spurious "{" charcters suggest that your serial cable
or serial settings may be off.
Anyway, I would try resetting the eeprom by holding down Stop n
after power up, set your serial to 9600,N,1
Get an ok prompt if possible and do this:
ok setenv diag-level max
ok reset-all
and record the output properly. Post that if anything new comes up |
|
| Back to top |
|
|
Guest
|
| Posted: Wed Jan 31, 2007 8:33 am Post subject: Re: Problem with Blade 1000 |
|
|
On Jan 28, 3:58 am, Kosta Xonis <ChaosKo...@web.de> wrote:
| Quote: | Gerry Sinkiewicz schrieb:
|
| Quote: | ttya initialized
Start Reason: Initialize Machine
Configuring the machine:
ERROR: get-sys-i2c-config: SYSTEM FRUprom is invalid or inaccessible!
Powering off system!
/quote
and powers off, as told. The quote is all I get via the tip connection.
I think I am %&$%&, right ?? Dead Mainboard component ?
|
Or the Field Replaceable Unit (FRU) prom died. This maybe the idprom
which a battery backed unit and the battery. When the battery died all
the id information was lost. A new eeprom is inexpensive ($10) and can
be replaced in a few minutes. I have'nt had to replace a Blade 1000
eeprom but have had to replace Blade-150 eeprom already. |
|
| Back to top |
|
|
|
|
|
  |
Index
-> SUN |
All times are GMT
|
| Page 1 of 1 |
|
| |
Watched Topics
Search
Register
Log in to check your private messages
Profile
Log in
Memberlist
Usergroups