Hi.

Got a new "toy" yesterday.
A 2 CPU 1 GHz 4 GB DS25 in floor cabinet.

Now, just trying to get something out of the consol port.
The User Guide only says that the the serial consol is on
COM1 *or* COM2 and nothing about what decides which port
becomes the serial console port.

There is no graphic card in the box and we did have output
at the place where I picked it up. We could also se that
"consol" was set to "serial".

The POST seems to run. If reseted using the small "reset"
button on the front, the CD drive spins up and so on.

At one time while moving the cable back and forth between
the two ports, I turn around and saw "P00>>>" on the screen
but then I didn't know from which port that had come ! Arg...

I use Reflection on a laptop using a USB/RS232 adapter.
Default 9600 81n setup. This setup always works perfectly
as console on the XP900.

Now, for someone having a DS25, what can make DS25 not
outputing anything on the *serial* consol port ? And
which of COM1 and COM2 is most likely to act as console ?

I'm beginning to think of a bad conection between the
actual DB-9 connecter on the back and the PCB card in the
DS25. I will check on that tomorrow.

The good thing is that the DS25 is more silent then the
current XP900 together with the external 14-disk cabinet !

Jan-Erik.

In article <j4bcls$pb2$1@news.albasani.net>, Jan-Erik Soderholm <jan-erik.soderholm@telia.com> writes:
>Hi.
>
>Got a new "toy" yesterday.
>A 2 CPU 1 GHz 4 GB DS25 in floor cabinet.
>
>Now, just trying to get something out of the consol port.
>The User Guide only says that the the serial consol is on
>COM1 *or* COM2 and nothing about what decides which port
>becomes the serial console port.
>
>There is no graphic card in the box and we did have output
>at the place where I picked it up. We could also se that
>"consol" was set to "serial".
>
>The POST seems to run. If reseted using the small "reset"
>button on the front, the CD drive spins up and so on.
>
>At one time while moving the cable back and forth between
>the two ports, I turn around and saw "P00>>>" on the screen
>but then I didn't know from which port that had come ! Arg...
>
>I use Reflection on a laptop using a USB/RS232 adapter.
>Default 9600 81n setup. This setup always works perfectly
>as console on the XP900.

I'll bet your transmit and receive are backward.



>Now, for someone having a DS25, what can make DS25 not
>outputing anything on the *serial* consol port ? And
>which of COM1 and COM2 is most likely to act as console ?
>
>I'm beginning to think of a bad conection between the
>actual DB-9 connecter on the back and the PCB card in the
>DS25. I will check on that tomorrow.
>
>The good thing is that the DS25 is more silent then the
>current XP900 together with the external 14-disk cabinet !

DS10L, DS10, DS20E, ES40... COM1

I'd expect that you'd use the same on the DS25.

9600 should be the speed.  If you can't get this to talk, you may have to
try swapping pins 2 and 3 (the transmit and receive pins).  If you had a
breakout box, this would be much easier.

-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

All your spirit rack abuses, come to haunt you back by day.
All your Byzantine excuses, given time, given you away.

Jan-Erik,

on a DS25 with CONSOLE = SERIAL, the bottom DB9 connector (labelled
<=>1 BELOW the connector) is OPA0:

Volker.

VAXman- @SendSpamHere.ORG wrote 2011-09-09 00:50:
> In article<j4bcls$pb2$1@news.albasani.net>, Jan-Erik Soderholm<jan-erik.soderholm@telia.com>  writes:
>> Hi.
>>
>> Got a new "toy" yesterday.
>> A 2 CPU 1 GHz 4 GB DS25 in floor cabinet.
>>
>> Now, just trying to get something out of the consol port.
>> The User Guide only says that the the serial consol is on
>> COM1 *or* COM2 and nothing about what decides which port
>> becomes the serial console port.
>>
>> There is no graphic card in the box and we did have output
>> at the place where I picked it up. We could also se that
>> "consol" was set to "serial".
>>
>> The POST seems to run. If reseted using the small "reset"
>> button on the front, the CD drive spins up and so on.
>>
>> At one time while moving the cable back and forth between
>> the two ports, I turn around and saw "P00>>>" on the screen
>> but then I didn't know from which port that had come ! Arg...
>>
>> I use Reflection on a laptop using a USB/RS232 adapter.
>> Default 9600 81n setup. This setup always works perfectly
>> as console on the XP900.
>
> I'll bet your transmit and receive are backward.
>

Same RS232 cable, same RS232/USB adapter and same laptop as
when I run against the XP900/DS10. Are the pins swapped
in the DS25? I don't think so.

Would have been a thought if it was a whole new cable setup.

Volker Halle wrote 2011-09-09 10:14:
> Jan-Erik,
>
> on a DS25 with CONSOLE = SERIAL, the bottom DB9 connector (labelled
> <=>1 BELOW the connector) is OPA0:
>
> Volker.


Bottom... This is the piedistal mount so there is one
"left" and one "right" connector. :-)

The one close to the fan is marked COM2 and the other
COM1. I don't know which is the bottom connecter when
rack mount.

I'll look at it some more today.

Thanks !

Jan-Erik.

Jan-Erik,

for the rack-mount version the DB9 connector labeled <=>2 is the one
near the fan.

Volker.

Volker Halle wrote 2011-09-09 10:55:
> Jan-Erik,
>
> for the rack-mount version the DB9 connector labeled<=>2 is the one
> near the fan.
>
> Volker.

OK, fine. Then they are not miss-labeled at least. :-)

In article <j4bcls$pb2$1@news.albasani.net>, Jan-Erik Soderholm <jan-erik.soderholm@telia.com> writes:
> 
> Now, just trying to get something out of the consol port.
> The User Guide only says that the the serial consol is on
> COM1 *or* COM2 and nothing about what decides which port
> becomes the serial console port.

   If it's like my DS10L, the console port is the serial port you hit 
   RETURN on when the OS is not running.  That is, the system reponds
   with the console prompt on either port.  But one is OPA0 and will have
   OPCOM, the other will not, unless you use REPLY commands to change it.
   Also, the first will show power-on diagnostics, but the other won't.

   This confused me somewhat when I moved the system the other day and
   plugged my VT320 into the other port.  It booted and ran, but where
   were all the other console messages?  Not getting OPCOM clued me in.

Bob Koehler wrote 2011-09-09 15:42:
> In article<j4bcls$pb2$1@news.albasani.net>, Jan-Erik Soderholm<jan-erik.soderholm@telia.com>  writes:
>>
>> Now, just trying to get something out of the consol port.
>> The User Guide only says that the the serial consol is on
>> COM1 *or* COM2 and nothing about what decides which port
>> becomes the serial console port.
>
>     If it's like my DS10L, the console port is the serial port you hit
>     RETURN on when the OS is not running.  That is, the system reponds
>     with the console prompt on either port.  But one is OPA0 and will have
>     OPCOM, the other will not, unless you use REPLY commands to change it.
>     Also, the first will show power-on diagnostics, but the other won't.
>
>     This confused me somewhat when I moved the system the other day and
>     plugged my VT320 into the other port.  It booted and ran, but where
>     were all the other console messages?  Not getting OPCOM clued me in.
>

OK. That is like I remember older Alphas also.
Right now I'm struggling with the system. Can't get any
consol att all, appart from a sudden P000>> three times,
non-reproducable. (So the cabling as such seems OK).

There is also something written in the manual about RMC (remote-something)
and if that is enabled, the consol port might be limited to COM2. If
I understand the manual correctly...

I also got a hint that the mem test (5 GB here) might take "a while"
like several minutes.

Ah, well...

Jan-Erik.

On Sep 9, 8:48=A0am, Jan-Erik Soderholm <jan-erik.soderh...@telia.com>
wrote:
> Bob Koehler wrote 2011-09-09 15:42:
>
>
>
> > In article<j4bcls$pb...@news.albasani.net>, Jan-Erik Soderholm<jan-erik=
..soderh...@telia.com> =A0writes:
>
> >> Now, just trying to get something out of the consol port.
> >> The User Guide only says that the the serial consol is on
> >> COM1 *or* COM2 and nothing about what decides which port
> >> becomes the serial console port.
>
> > =A0 =A0 If it's like my DS10L, the console port is the serial port you =
hit
> > =A0 =A0 RETURN on when the OS is not running. =A0That is, the system re=
ponds
> > =A0 =A0 with the console prompt on either port. =A0But one is OPA0 and =
will have
> > =A0 =A0 OPCOM, the other will not, unless you use REPLY commands to cha=
nge it.
> > =A0 =A0 Also, the first will show power-on diagnostics, but the other w=
on't.
>
> > =A0 =A0 This confused me somewhat when I moved the system the other day=
 and
> > =A0 =A0 plugged my VT320 into the other port. =A0It booted and ran, but=
 where
> > =A0 =A0 were all the other console messages? =A0Not getting OPCOM clued=
 me in.
>
> OK. That is like I remember older Alphas also.
> Right now I'm struggling with the system. Can't get any
> consol att all, appart from a sudden P000>> three times,
> non-reproducable. (So the cabling as such seems OK).
>
> There is also something written in the manual about RMC (remote-something=
)
> and if that is enabled, the consol port might be limited to COM2. If
> I understand the manual correctly...
>
> I also got a hint that the mem test (5 GB here) might take "a while"
> like several minutes.
>
> Ah, well...
>
> Jan-Erik.

I've never had the chance to use a DS25 (and years since I set up a
DS15) but you might try accessing the RMC on both ports.

Assuming its the same method as a DS10/20 you have the port set to
9600,n,8,1 and do <esc><esc>rmc.  If you're on a real keyboard that
would be ctrl-[ ctrl-[ rmc   with no spaces.  If you get the RMC
prompt then at least you know comm is working.

Again if its the same as a DS10 you can type HELP at RMC>  or QUIT to
return to 'the console'

Rich Jordan wrote 2011-09-09 16:27:
> On Sep 9, 8:48 am, Jan-Erik Soderholm<jan-erik.soderh...@telia.com>
> wrote:
>> Bob Koehler wrote 2011-09-09 15:42:
>>
>>
>>
>>> In article<j4bcls$pb...@news.albasani.net>, Jan-Erik Soderholm<jan-erik.soderh...@telia.com>    writes:
>>
>>>> Now, just trying to get something out of the consol port.
>>>> The User Guide only says that the the serial consol is on
>>>> COM1 *or* COM2 and nothing about what decides which port
>>>> becomes the serial console port.
>>
>>>      If it's like my DS10L, the console port is the serial port you hit
>>>      RETURN on when the OS is not running.  That is, the system reponds
>>>      with the console prompt on either port.  But one is OPA0 and will have
>>>      OPCOM, the other will not, unless you use REPLY commands to change it.
>>>      Also, the first will show power-on diagnostics, but the other won't.
>>
>>>      This confused me somewhat when I moved the system the other day and
>>>      plugged my VT320 into the other port.  It booted and ran, but where
>>>      were all the other console messages?  Not getting OPCOM clued me in.
>>
>> OK. That is like I remember older Alphas also.
>> Right now I'm struggling with the system. Can't get any
>> consol att all, appart from a sudden P000>>  three times,
>> non-reproducable. (So the cabling as such seems OK).
>>
>> There is also something written in the manual about RMC (remote-something)
>> and if that is enabled, the consol port might be limited to COM2. If
>> I understand the manual correctly...
>>
>> I also got a hint that the mem test (5 GB here) might take "a while"
>> like several minutes.
>>
>> Ah, well...
>>
>> Jan-Erik.
>
> I've never had the chance to use a DS25 (and years since I set up a
> DS15) but you might try accessing the RMC on both ports.
>
> Assuming its the same method as a DS10/20 you have the port set to
> 9600,n,8,1 and do<esc><esc>rmc.  If you're on a real keyboard that
> would be ctrl-[ ctrl-[ rmc   with no spaces.  If you get the RMC
> prompt then at least you know comm is working.
>
> Again if its the same as a DS10 you can type HELP at RMC>   or QUIT to
> return to 'the console'
>

I was looking fpr a DS15 but that are still quite costly.
THis DS25 in floor cabinet mount are not that wanted, according
to my source. It will be interesting to compare the output from
CALCULATE_VUP.COM from the XP900 (466MHz) and the DS25 :-)


I have now manage to get contact with COM2 by powering up an old
laptop with a hardware COM port. That is, the usual SRM consol.
Seems as the COM2 doesn't like the USB/RS232 adapter...

I can still not get any contact att all with COM1. Neither POST
messages or <esc><esc>rmc works.

I have noticed that "com1_mode" is set to "through", which means
that all COM1 traffic goes through the RMC.

I have also noticed now that the diagnostic LEDs on the front
shows <lit><lit><lit><unlit> which according to the user guide
means  "Bad RMC flash" with an additional note :

 > NOTE: If the RMC flash is bad, the system will still come up;
 > however, the bad RMC flash LED will remain lit until a new RMC
 > flash image is loaded. RMC will not have full functionality,
 > use COM2 or VGA display to flash the RMC.

That might be the reason for <esc><esc>rmc not working and also
why COM1 doesn't output anything since "com1_mode" = "through"
means that the RMC will read/filter everything going over COM1.

Now, I'm not that interested in RMC anyway, so I tried to set
"com1_mode" to "firm_bypass" which should : "Data bypasses RMC.
RMC remote management features are disabled"

Now, this setting of com1_mode desn't work. I guess this might
have something with "Bad RMC flash" to do, since com1_mode is
one (of just a few) variables that can be set from within RMC.

Other environment variables are settable just fine.

There is also a hardware jumper (J68) which can override the
com1_mode environment variable. I'll check that.
"No jumper" is "Always bypass the RMC" which would be fine.

Well, I guess the system is runnable as-is and using COM2
as console and without POST messages.

Still a few things to look up.

And it's still a very nice system so far. :-)


Jan-Erik.

On 9 sep, 17:36, Jan-Erik Soderholm <jan-erik.soderh...@telia.com>
wrote:
> Rich Jordan wrote 2011-09-09 16:27:
>
>
>
>
>
> > On Sep 9, 8:48 am, Jan-Erik Soderholm<jan-erik.soderh...@telia.com>
> > wrote:
> >> Bob Koehler wrote 2011-09-09 15:42:
>
> >>> In article<j4bcls$pb...@news.albasani.net>, Jan-Erik Soderholm<jan-er=
ik.soderh...@telia.com> =A0 =A0writes:
>
> >>>> Now, just trying to get something out of the consol port.
> >>>> The User Guide only says that the the serial consol is on
> >>>> COM1 *or* COM2 and nothing about what decides which port
> >>>> becomes the serial console port.
>
> >>> =A0 =A0 =A0If it's like my DS10L, the console port is the serial port=
 you hit
> >>> =A0 =A0 =A0RETURN on when the OS is not running. =A0That is, the syst=
em reponds
> >>> =A0 =A0 =A0with the console prompt on either port. =A0But one is OPA0=
 and will have
> >>> =A0 =A0 =A0OPCOM, the other will not, unless you use REPLY commands t=
o change it.
> >>> =A0 =A0 =A0Also, the first will show power-on diagnostics, but the ot=
her won't.
>
> >>> =A0 =A0 =A0This confused me somewhat when I moved the system the othe=
r day and
> >>> =A0 =A0 =A0plugged my VT320 into the other port. =A0It booted and ran=
, but where
> >>> =A0 =A0 =A0were all the other console messages? =A0Not getting OPCOM =
clued me in.
>
> >> OK. That is like I remember older Alphas also.
> >> Right now I'm struggling with the system. Can't get any
> >> consol att all, appart from a sudden P000>> =A0three times,
> >> non-reproducable. (So the cabling as such seems OK).
>
> >> There is also something written in the manual about RMC (remote-someth=
ing)
> >> and if that is enabled, the consol port might be limited to COM2. If
> >> I understand the manual correctly...
>
> >> I also got a hint that the mem test (5 GB here) might take "a while"
> >> like several minutes.
>
> >> Ah, well...
>
> >> Jan-Erik.
>
> > I've never had the chance to use a DS25 (and years since I set up a
> > DS15) but you might try accessing the RMC on both ports.
>
> > Assuming its the same method as a DS10/20 you have the port set to
> > 9600,n,8,1 and do<esc><esc>rmc. =A0If you're on a real keyboard that
> > would be ctrl-[ ctrl-[ rmc =A0 with no spaces. =A0If you get the RMC
> > prompt then at least you know comm is working.
>
> > Again if its the same as a DS10 you can type HELP at RMC> =A0 or QUIT t=
o
> > return to 'the console'
>
> I was looking fpr a DS15 but that are still quite costly.
> THis DS25 in floor cabinet mount are not that wanted, according
> to my source. It will be interesting to compare the output from
> CALCULATE_VUP.COM from the XP900 (466MHz) and the DS25 :-)
>
> I have now manage to get contact with COM2 by powering up an old
> laptop with a hardware COM port. That is, the usual SRM consol.
> Seems as the COM2 doesn't like the USB/RS232 adapter...
>
> I can still not get any contact att all with COM1. Neither POST
> messages or <esc><esc>rmc works.
>
> I have noticed that "com1_mode" is set to "through", which means
> that all COM1 traffic goes through the RMC.
>
> I have also noticed now that the diagnostic LEDs on the front
> shows <lit><lit><lit><unlit> which according to the user guide
> means =A0"Bad RMC flash" with an additional note :
>
> =A0> NOTE: If the RMC flash is bad, the system will still come up;
> =A0> however, the bad RMC flash LED will remain lit until a new RMC
> =A0> flash image is loaded. RMC will not have full functionality,
> =A0> use COM2 or VGA display to flash the RMC.
>
> That might be the reason for <esc><esc>rmc not working and also
> why COM1 doesn't output anything since "com1_mode" =3D "through"
> means that the RMC will read/filter everything going over COM1.
>
> Now, I'm not that interested in RMC anyway, so I tried to set
> "com1_mode" to "firm_bypass" which should : "Data bypasses RMC.
> RMC remote management features are disabled"
>
> Now, this setting of com1_mode desn't work. I guess this might
> have something with "Bad RMC flash" to do, since com1_mode is
> one (of just a few) variables that can be set from within RMC.
>
> Other environment variables are settable just fine.
>
> There is also a hardware jumper (J68) which can override the
> com1_mode environment variable. I'll check that.
> "No jumper" is "Always bypass the RMC" which would be fine.
>
> Well, I guess the system is runnable as-is and using COM2
> as console and without POST messages.
>
> Still a few things to look up.
>
> And it's still a very nice system so far. :-)
>
> Jan-Erik.- Tekst uit oorspronkelijk bericht niet weergeven -
>
> - Tekst uit oorspronkelijk bericht weergeven -

Have you considered hitting ^P or BREAK?
Hans

Hans Vlems wrote 2011-09-09 20:22:
> On 9 sep, 17:36, Jan-Erik Soderholm<jan-erik.soderh...@telia.com>
> wrote:
>> Rich Jordan wrote 2011-09-09 16:27:
>>
>>
>>
>>
>>
>>> On Sep 9, 8:48 am, Jan-Erik Soderholm<jan-erik.soderh...@telia.com>
>>> wrote:
>>>> Bob Koehler wrote 2011-09-09 15:42:
>>
>>>>> In article<j4bcls$pb...@news.albasani.net>, Jan-Erik Soderholm<jan-erik.soderh...@telia.com>      writes:
>>
>>>>>> Now, just trying to get something out of the consol port.
>>>>>> The User Guide only says that the the serial consol is on
>>>>>> COM1 *or* COM2 and nothing about what decides which port
>>>>>> becomes the serial console port.
>>
>>>>>       If it's like my DS10L, the console port is the serial port you hit
>>>>>       RETURN on when the OS is not running.  That is, the system reponds
>>>>>       with the console prompt on either port.  But one is OPA0 and will have
>>>>>       OPCOM, the other will not, unless you use REPLY commands to change it.
>>>>>       Also, the first will show power-on diagnostics, but the other won't.
>>
>>>>>       This confused me somewhat when I moved the system the other day and
>>>>>       plugged my VT320 into the other port.  It booted and ran, but where
>>>>>       were all the other console messages?  Not getting OPCOM clued me in.
>>
>>>> OK. That is like I remember older Alphas also.
>>>> Right now I'm struggling with the system. Can't get any
>>>> consol att all, appart from a sudden P000>>    three times,
>>>> non-reproducable. (So the cabling as such seems OK).
>>
>>>> There is also something written in the manual about RMC (remote-something)
>>>> and if that is enabled, the consol port might be limited to COM2. If
>>>> I understand the manual correctly...
>>
>>>> I also got a hint that the mem test (5 GB here) might take "a while"
>>>> like several minutes.
>>
>>>> Ah, well...
>>
>>>> Jan-Erik.
>>
>>> I've never had the chance to use a DS25 (and years since I set up a
>>> DS15) but you might try accessing the RMC on both ports.
>>
>>> Assuming its the same method as a DS10/20 you have the port set to
>>> 9600,n,8,1 and do<esc><esc>rmc.  If you're on a real keyboard that
>>> would be ctrl-[ ctrl-[ rmc   with no spaces.  If you get the RMC
>>> prompt then at least you know comm is working.
>>
>>> Again if its the same as a DS10 you can type HELP at RMC>     or QUIT to
>>> return to 'the console'
>>
>> I was looking fpr a DS15 but that are still quite costly.
>> THis DS25 in floor cabinet mount are not that wanted, according
>> to my source. It will be interesting to compare the output from
>> CALCULATE_VUP.COM from the XP900 (466MHz) and the DS25 :-)
>>
>> I have now manage to get contact with COM2 by powering up an old
>> laptop with a hardware COM port. That is, the usual SRM consol.
>> Seems as the COM2 doesn't like the USB/RS232 adapter...
>>
>> I can still not get any contact att all with COM1. Neither POST
>> messages or<esc><esc>rmc works.
>>
>> I have noticed that "com1_mode" is set to "through", which means
>> that all COM1 traffic goes through the RMC.
>>
>> I have also noticed now that the diagnostic LEDs on the front
>> shows<lit><lit><lit><unlit>  which according to the user guide
>> means  "Bad RMC flash" with an additional note :
>>
>>   >  NOTE: If the RMC flash is bad, the system will still come up;
>>   >  however, the bad RMC flash LED will remain lit until a new RMC
>>   >  flash image is loaded. RMC will not have full functionality,
>>   >  use COM2 or VGA display to flash the RMC.
>>
>> That might be the reason for<esc><esc>rmc not working and also
>> why COM1 doesn't output anything since "com1_mode" = "through"
>> means that the RMC will read/filter everything going over COM1.
>>
>> Now, I'm not that interested in RMC anyway, so I tried to set
>> "com1_mode" to "firm_bypass" which should : "Data bypasses RMC.
>> RMC remote management features are disabled"
>>
>> Now, this setting of com1_mode desn't work. I guess this might
>> have something with "Bad RMC flash" to do, since com1_mode is
>> one (of just a few) variables that can be set from within RMC.
>>
>> Other environment variables are settable just fine.
>>
>> There is also a hardware jumper (J68) which can override the
>> com1_mode environment variable. I'll check that.
>> "No jumper" is "Always bypass the RMC" which would be fine.
>>
>> Well, I guess the system is runnable as-is and using COM2
>> as console and without POST messages.
>>
>> Still a few things to look up.
>>
>> And it's still a very nice system so far. :-)
>>
>> Jan-Erik.- Tekst uit oorspronkelijk bericht niet weergeven -
>>
>> - Tekst uit oorspronkelijk bericht weergeven -
>
> Have you considered hitting ^P or BREAK?
> Hans

OK. sorry. Yes, eny thinkable cntl character... :-)

Soice the post abowe, I have booted a backup of the
sstem disk from the XP900. Everythings seems OK so far.

Jan-Erik.

Jan-Erik Soderholm wrote 2011-09-09 17:36:




> I have also noticed now that the diagnostic LEDs on the front
> shows <lit><lit><lit><unlit> which according to the user guide
> means "Bad RMC flash" with an additional note :
>
>  > NOTE: If the RMC flash is bad, the system will still come up;
>  > however, the bad RMC flash LED will remain lit until a new RMC
>  > flash image is loaded. RMC will not have full functionality,
>  > use COM2 or VGA display to flash the RMC.
>

There is also a note in the "Service Manual" that says :

 > NOTE: If the RMC is corrupt, you may not get an output from COM1.
 > If this occurs, remove J68 and move the serial line to the COM2 port.

I have now removed J68 and *now* I get the usual power up messages
on COM1 ! And also a lot messages like :

 > RMC error status 80
 > RMC command: 03 qualifier: 32ff size: 10
 > RMC command failure

 > *** Error - RMC detected power up error - RMC Flash corrupted ***


I also got (when booting VMS 8.3) :

 > jumping to bootstrap code
 >
 > %SYSBOOT-W-FIRMREV, Firmware rev. 6.4 is below the recommended
 > minimum of 6.8.
 >   Please update your firmware to the recommended revision,
 >   which can be found on the firmware CD labeled:
 >   alpha systems firmware update 6.8.


If anyone knows some online place to find firmware update,
I'm interested... :-)

Jan-Erik.

On Sep 10, 7:04=A0am, Jan-Erik Soderholm <jan-erik.soderh...@telia.com>
wrote:

> If anyone knows some online place to find firmware update,
> I'm interested... :-)

   And a Google search for keywords like, say:
      alpha firmware
didn't work?

In article <530952c0-843f-435f-b8e2-c9d7045f14c1@d25g2000yqh.googlegroups.com>, Steven Schweda <sms.antinode@gmail.com> writes:
>On Sep 10, 7:04=A0am, Jan-Erik Soderholm <jan-erik.soderh...@telia.com>
>wrote:
>
>> If anyone knows some online place to find firmware update,
>> I'm interested... :-)
>
>   And a Google search for keywords like, say:
>      alpha firmware
>didn't work?

You mean like the very first link found is it?  :rolleyes:
-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

All your spirit rack abuses, come to haunt you back by day.
All your Byzantine excuses, given time, given you away.

On 10 sep, 14:04, Jan-Erik Soderholm <jan-erik.soderh...@telia.com>
wrote:
> Jan-Erik Soderholm wrote 2011-09-09 17:36:
>
> > I have also noticed now that the diagnostic LEDs on the front
> > shows <lit><lit><lit><unlit> which according to the user guide
> > means "Bad RMC flash" with an additional note :
>
> > =A0> NOTE: If the RMC flash is bad, the system will still come up;
> > =A0> however, the bad RMC flash LED will remain lit until a new RMC
> > =A0> flash image is loaded. RMC will not have full functionality,
> > =A0> use COM2 or VGA display to flash the RMC.
>
> There is also a note in the "Service Manual" that says :
>
> =A0> NOTE: If the RMC is corrupt, you may not get an output from COM1.
> =A0> If this occurs, remove J68 and move the serial line to the COM2 port=
..
>
> I have now removed J68 and *now* I get the usual power up messages
> on COM1 ! And also a lot messages like :
>
> =A0> RMC error status 80
> =A0> RMC command: 03 qualifier: 32ff size: 10
> =A0> RMC command failure
>
> =A0> *** Error - RMC detected power up error - RMC Flash corrupted ***
>
> I also got (when booting VMS 8.3) :
>
> =A0> jumping to bootstrap code
> =A0>
> =A0> %SYSBOOT-W-FIRMREV, Firmware rev. 6.4 is below the recommended
> =A0> minimum of 6.8.
> =A0> =A0 Please update your firmware to the recommended revision,
> =A0> =A0 which can be found on the firmware CD labeled:
> =A0> =A0 alpha systems firmware update 6.8.
>
> If anyone knows some online place to find firmware update,
> I'm interested... :-)
>
> Jan-Erik.

Is there something wrong with this URL:

http://h18002.www1.hp.com/alphaserver/firmware/readmes/ds25.html

???
Hans