Thread: [ES40-developers] Interesting messages from Tru64
Status: Alpha
Brought to you by:
iamcamiel
Menu
▾
▴
es40-developers
|
From: Brian W. <bdw...@in...> - 2008-02-27 13:20:02
|
I did a full install from dqb0 to dqa0 and while there were some timeouts (this build was before I started on the interrupt resend code) it installed and configured correctly (I left it run unattended overnight). However, once it came up, it started announcing hardware failures :) ----------------- Broadcast Message from ro...@tr... (???) at 23:37 ... The redundant power supply has failed. Broadcast Message from ro...@tr... (???) at 23:37 ... The system temperature is high. Possible reasons are a clogged air filter or a high ambient room temperature. The system will shut down in 14 minutes and 0 seconds.. ------------------ So...is there any documentation for the hardware monitoring stuff? Brian |
|
From: Camiel V. <iam...@gm...> - 2008-02-27 13:35:29
|
Hi Brian, The ES40 has a management processor that takes care of monitoring power suppies, fans, and other hardware bits and pieces. It is extremely difficult to find any information about this. I managed to find some info in the ES40 service manual, and basically played a lot with things to get them to show up properly in SRM. The management processor communicates with SRM - and I presume with the OS - through a thing called Dual-Port-RAM. One port is connected to the system bus, another to the management-processor. A lot of the bytes are places where the OS can read device information, but in some locations, the OS can deposit commands for the management-processor. The following copmmands were found out through trial-and-error and partial reverse engineering of SRM: Address locations for commands: // 0xf9: buffer size // 0xfb:fa qualifier / address // 0xfc: completion code (0 = ok, 80 = error, 81 = invalid code, 82 = invalid qualifier) // 0xfd: rmc command id for response // 0xfe: command code // 0xff: rmc command id for command Command codes: // 01: update EEPROM // 02: update baud rate // 03: write to OCP // F0: update RMC flash It could very well be that there are more commands I don't know about, and a failure to respond to these in a satisfactory manner may well be the cause of the power supply failures and temperature warnings. You can find most of what I managed to find out in DPR.cpp. Mind you, this is some of the oldest and least-touched code in the emulator. It has not changed (other than some of the standard changes that have been made to the entire emulator) for well over a year, and a lot of my comments are still in Dutch. (I'm sorry about that...) It might be a good idea to put some read/write tracers in DPR.cpp, and try to figure out what Tru64 is doing with these. Camiel. On Wed, Feb 27, 2008 at 2:19 PM, Brian Wheeler <bdw...@in...> wrote: > I did a full install from dqb0 to dqa0 and while there were some > timeouts (this build was before I started on the interrupt resend code) > it installed and configured correctly (I left it run unattended > overnight). > > However, once it came up, it started announcing hardware failures :) > > ----------------- > Broadcast Message from ro...@tr... (???) at 23:37 ... > > The redundant power supply has failed. > > Broadcast Message from ro...@tr... (???) at 23:37 ... > > The system temperature is high. Possible reasons are > a clogged air filter or a high ambient room temperature. > The system will shut down in 14 minutes and 0 seconds.. > ------------------ > > So...is there any documentation for the hardware monitoring stuff? > > Brian > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Es40-developers mailing list > Es4...@li... > https://lists.sourceforge.net/lists/listinfo/es40-developers > |
|
From: Brian W. <bdw...@in...> - 2008-02-27 14:06:13
|
Thanks for the info. I'll play around with it and see what I can come
up with.
Can you apply this patch. It tunes the interrupt re-send code so it
doesn't trigger so often.
Brian
Index: NewIde.cpp
===================================================================
RCS file: /cvsroot/es40/es40/src/NewIde.cpp,v
retrieving revision 1.16
diff -u -r1.16 NewIde.cpp
--- NewIde.cpp 27 Feb 2008 12:34:19 -0000 1.16
+++ NewIde.cpp 27 Feb 2008 14:04:51 -0000
@@ -1881,7 +1881,7 @@
if(CONTROLLER(index).interrupt_fired != 0)
{
- if((SEL_COMMAND(index).command_cycle - CONTROLLER(index).interrupt_fired) > 10)
+ if((SEL_COMMAND(index).command_cycle - CONTROLLER(index).interrupt_fired) > 200)
{
CONTROLLER(index).interrupt_pending=1;
theAli->pic_deassert(1,6+index);
On Wed, 2008-02-27 at 14:35 +0100, Camiel Vanderhoeven wrote:
> Hi Brian,
>
> The ES40 has a management processor that takes care of monitoring
> power suppies, fans, and other hardware bits and pieces. It is
> extremely difficult to find any information about this. I managed to
> find some info in the ES40 service manual, and basically played a lot
> with things to get them to show up properly in SRM.
>
> The management processor communicates with SRM - and I presume with
> the OS - through a thing called Dual-Port-RAM. One port is connected
> to the system bus, another to the management-processor. A lot of the
> bytes are places where the OS can read device information, but in some
> locations, the OS can deposit commands for the management-processor.
> The following copmmands were found out through trial-and-error and
> partial reverse engineering of SRM:
>
> Address locations for commands:
> // 0xf9: buffer size
> // 0xfb:fa qualifier / address
> // 0xfc: completion code (0 = ok, 80 = error, 81 = invalid code, 82
> = invalid qualifier)
> // 0xfd: rmc command id for response
> // 0xfe: command code
> // 0xff: rmc command id for command
>
> Command codes:
> // 01: update EEPROM
> // 02: update baud rate
> // 03: write to OCP
> // F0: update RMC flash
>
> It could very well be that there are more commands I don't know about,
> and a failure to respond to these in a satisfactory manner may well be
> the cause of the power supply failures and temperature warnings.
>
> You can find most of what I managed to find out in DPR.cpp. Mind you,
> this is some of the oldest and least-touched code in the emulator. It
> has not changed (other than some of the standard changes that have
> been made to the entire emulator) for well over a year, and a lot of
> my comments are still in Dutch. (I'm sorry about that...) It might be
> a good idea to put some read/write tracers in DPR.cpp, and try to
> figure out what Tru64 is doing with these.
>
> Camiel.
>
>
>
>
>
> On Wed, Feb 27, 2008 at 2:19 PM, Brian Wheeler <bdw...@in...> wrote:
> > I did a full install from dqb0 to dqa0 and while there were some
> > timeouts (this build was before I started on the interrupt resend code)
> > it installed and configured correctly (I left it run unattended
> > overnight).
> >
> > However, once it came up, it started announcing hardware failures :)
> >
> > -----------------
> > Broadcast Message from ro...@tr... (???) at 23:37 ...
> >
> > The redundant power supply has failed.
> >
> > Broadcast Message from ro...@tr... (???) at 23:37 ...
> >
> > The system temperature is high. Possible reasons are
> > a clogged air filter or a high ambient room temperature.
> > The system will shut down in 14 minutes and 0 seconds..
> > ------------------
> >
> > So...is there any documentation for the hardware monitoring stuff?
> >
> > Brian
> >
> >
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________
> > Es40-developers mailing list
> > Es4...@li...
> > https://lists.sourceforge.net/lists/listinfo/es40-developers
> >
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Es40-developers mailing list
> Es4...@li...
> https://lists.sourceforge.net/lists/listinfo/es40-developers
|
|
From: Brian W. <bdw...@in...> - 2008-02-27 15:59:00
Attachments:
tru64_env.diff
|
Turns out that the temperatures aren't actually in BCD but in degrees Celsius. This patch is a minor refactor of DPR, plus a change to the keyboard driver to ignore the the make/break commands so it'll come up with the vga card inserted. I'm going gather up a tru64 license and see if I can get cde to run. I'll probably also try the networking. Brian On Wed, 2008-02-27 at 14:35 +0100, Camiel Vanderhoeven wrote: > Hi Brian, > > The ES40 has a management processor that takes care of monitoring > power suppies, fans, and other hardware bits and pieces. It is > extremely difficult to find any information about this. I managed to > find some info in the ES40 service manual, and basically played a lot > with things to get them to show up properly in SRM. > > The management processor communicates with SRM - and I presume with > the OS - through a thing called Dual-Port-RAM. One port is connected > to the system bus, another to the management-processor. A lot of the > bytes are places where the OS can read device information, but in some > locations, the OS can deposit commands for the management-processor. > The following copmmands were found out through trial-and-error and > partial reverse engineering of SRM: > > Address locations for commands: > // 0xf9: buffer size > // 0xfb:fa qualifier / address > // 0xfc: completion code (0 = ok, 80 = error, 81 = invalid code, 82 > = invalid qualifier) > // 0xfd: rmc command id for response > // 0xfe: command code > // 0xff: rmc command id for command > > Command codes: > // 01: update EEPROM > // 02: update baud rate > // 03: write to OCP > // F0: update RMC flash > > It could very well be that there are more commands I don't know about, > and a failure to respond to these in a satisfactory manner may well be > the cause of the power supply failures and temperature warnings. > > You can find most of what I managed to find out in DPR.cpp. Mind you, > this is some of the oldest and least-touched code in the emulator. It > has not changed (other than some of the standard changes that have > been made to the entire emulator) for well over a year, and a lot of > my comments are still in Dutch. (I'm sorry about that...) It might be > a good idea to put some read/write tracers in DPR.cpp, and try to > figure out what Tru64 is doing with these. > > Camiel. > > > > > > On Wed, Feb 27, 2008 at 2:19 PM, Brian Wheeler <bdw...@in...> wrote: > > I did a full install from dqb0 to dqa0 and while there were some > > timeouts (this build was before I started on the interrupt resend code) > > it installed and configured correctly (I left it run unattended > > overnight). > > > > However, once it came up, it started announcing hardware failures :) > > > > ----------------- > > Broadcast Message from ro...@tr... (???) at 23:37 ... > > > > The redundant power supply has failed. > > > > Broadcast Message from ro...@tr... (???) at 23:37 ... > > > > The system temperature is high. Possible reasons are > > a clogged air filter or a high ambient room temperature. > > The system will shut down in 14 minutes and 0 seconds.. > > ------------------ > > > > So...is there any documentation for the hardware monitoring stuff? > > > > Brian > > > > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > Es40-developers mailing list > > Es4...@li... > > https://lists.sourceforge.net/lists/listinfo/es40-developers > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Es40-developers mailing list > Es4...@li... > https://lists.sourceforge.net/lists/listinfo/es40-developers |
|
From: Fausto S. <fa...@un...> - 2008-02-27 18:31:26
|
Hello all, about this subject, i'm wondering if there's an hobbyist license for Tru64. Do you know if it's possible to subscribe such kind of licensing? thanks, fausto Quoting Brian Wheeler <bdw...@in...>: > Turns out that the temperatures aren't actually in BCD but in degrees > Celsius. This patch is a minor refactor of DPR, plus a change to the > keyboard driver to ignore the the make/break commands so it'll come up > with the vga card inserted. I'm going gather up a tru64 license and see > if I can get cde to run. I'll probably also try the networking. > > Brian > > > > On Wed, 2008-02-27 at 14:35 +0100, Camiel Vanderhoeven wrote: >> Hi Brian, >> >> The ES40 has a management processor that takes care of monitoring >> power suppies, fans, and other hardware bits and pieces. It is >> extremely difficult to find any information about this. I managed to >> find some info in the ES40 service manual, and basically played a lot >> with things to get them to show up properly in SRM. >> >> The management processor communicates with SRM - and I presume with >> the OS - through a thing called Dual-Port-RAM. One port is connected >> to the system bus, another to the management-processor. A lot of the >> bytes are places where the OS can read device information, but in some >> locations, the OS can deposit commands for the management-processor. >> The following copmmands were found out through trial-and-error and >> partial reverse engineering of SRM: >> >> Address locations for commands: >> // 0xf9: buffer size >> // 0xfb:fa qualifier / address >> // 0xfc: completion code (0 = ok, 80 = error, 81 = invalid code, 82 >> = invalid qualifier) >> // 0xfd: rmc command id for response >> // 0xfe: command code >> // 0xff: rmc command id for command >> >> Command codes: >> // 01: update EEPROM >> // 02: update baud rate >> // 03: write to OCP >> // F0: update RMC flash >> >> It could very well be that there are more commands I don't know about, >> and a failure to respond to these in a satisfactory manner may well be >> the cause of the power supply failures and temperature warnings. >> >> You can find most of what I managed to find out in DPR.cpp. Mind you, >> this is some of the oldest and least-touched code in the emulator. It >> has not changed (other than some of the standard changes that have >> been made to the entire emulator) for well over a year, and a lot of >> my comments are still in Dutch. (I'm sorry about that...) It might be >> a good idea to put some read/write tracers in DPR.cpp, and try to >> figure out what Tru64 is doing with these. >> >> Camiel. >> >> >> >> >> >> On Wed, Feb 27, 2008 at 2:19 PM, Brian Wheeler <bdw...@in...> wrote: >> > I did a full install from dqb0 to dqa0 and while there were some >> > timeouts (this build was before I started on the interrupt resend code) >> > it installed and configured correctly (I left it run unattended >> > overnight). >> > >> > However, once it came up, it started announcing hardware failures :) >> > >> > ----------------- >> > Broadcast Message from ro...@tr... (???) at 23:37 ... >> > >> > The redundant power supply has failed. >> > >> > Broadcast Message from ro...@tr... (???) at 23:37 ... >> > >> > The system temperature is high. Possible reasons are >> > a clogged air filter or a high ambient room temperature. >> > The system will shut down in 14 minutes and 0 seconds.. >> > ------------------ >> > >> > So...is there any documentation for the hardware monitoring stuff? >> > >> > Brian >> > >> > >> > >> > ------------------------------------------------------------------------- >> > This SF.net email is sponsored by: Microsoft >> > Defy all challenges. Microsoft(R) Visual Studio 2008. >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> > _______________________________________________ >> > Es40-developers mailing list >> > Es4...@li... >> > https://lists.sourceforge.net/lists/listinfo/es40-developers >> > >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> Es40-developers mailing list >> Es4...@li... >> https://lists.sourceforge.net/lists/listinfo/es40-developers > |
|
From: Brian W. <bdw...@in...> - 2008-02-27 18:40:44
|
There used to be one offered by Compaq, but I don't know if HP carried it forward. For $100 you got media and a license of some sort. If you can find a copy of the media, you can run it and do some basic things without having the OSF-BASE license PAK. Technically, I think the only way to run Tru64 with any enjoyment (and legally) is to have a license. That said, I have heard of someone that found a way to generate valid licenses on VMS. With the ability to do that, you could generate an OSF-BASE license...both VMS' LICENSE and OSF's lmf use the same validation methods. Brian On Wed, 2008-02-27 at 19:28 +0100, Fausto Saporito wrote: > Hello all, > > about this subject, i'm wondering if there's an hobbyist license for Tru64. > Do you know if it's possible to subscribe such kind of licensing? > > thanks, > fausto > > Quoting Brian Wheeler <bdw...@in...>: > > > Turns out that the temperatures aren't actually in BCD but in degrees > > Celsius. This patch is a minor refactor of DPR, plus a change to the > > keyboard driver to ignore the the make/break commands so it'll come up > > with the vga card inserted. I'm going gather up a tru64 license and see > > if I can get cde to run. I'll probably also try the networking. > > > > Brian > > > > > > > > On Wed, 2008-02-27 at 14:35 +0100, Camiel Vanderhoeven wrote: > >> Hi Brian, > >> > >> The ES40 has a management processor that takes care of monitoring > >> power suppies, fans, and other hardware bits and pieces. It is > >> extremely difficult to find any information about this. I managed to > >> find some info in the ES40 service manual, and basically played a lot > >> with things to get them to show up properly in SRM. > >> > >> The management processor communicates with SRM - and I presume with > >> the OS - through a thing called Dual-Port-RAM. One port is connected > >> to the system bus, another to the management-processor. A lot of the > >> bytes are places where the OS can read device information, but in some > >> locations, the OS can deposit commands for the management-processor. > >> The following copmmands were found out through trial-and-error and > >> partial reverse engineering of SRM: > >> > >> Address locations for commands: > >> // 0xf9: buffer size > >> // 0xfb:fa qualifier / address > >> // 0xfc: completion code (0 = ok, 80 = error, 81 = invalid code, 82 > >> = invalid qualifier) > >> // 0xfd: rmc command id for response > >> // 0xfe: command code > >> // 0xff: rmc command id for command > >> > >> Command codes: > >> // 01: update EEPROM > >> // 02: update baud rate > >> // 03: write to OCP > >> // F0: update RMC flash > >> > >> It could very well be that there are more commands I don't know about, > >> and a failure to respond to these in a satisfactory manner may well be > >> the cause of the power supply failures and temperature warnings. > >> > >> You can find most of what I managed to find out in DPR.cpp. Mind you, > >> this is some of the oldest and least-touched code in the emulator. It > >> has not changed (other than some of the standard changes that have > >> been made to the entire emulator) for well over a year, and a lot of > >> my comments are still in Dutch. (I'm sorry about that...) It might be > >> a good idea to put some read/write tracers in DPR.cpp, and try to > >> figure out what Tru64 is doing with these. > >> > >> Camiel. > >> > >> > >> > >> > >> > >> On Wed, Feb 27, 2008 at 2:19 PM, Brian Wheeler <bdw...@in...> wrote: > >> > I did a full install from dqb0 to dqa0 and while there were some > >> > timeouts (this build was before I started on the interrupt resend code) > >> > it installed and configured correctly (I left it run unattended > >> > overnight). > >> > > >> > However, once it came up, it started announcing hardware failures :) > >> > > >> > ----------------- > >> > Broadcast Message from ro...@tr... (???) at 23:37 ... > >> > > >> > The redundant power supply has failed. > >> > > >> > Broadcast Message from ro...@tr... (???) at 23:37 ... > >> > > >> > The system temperature is high. Possible reasons are > >> > a clogged air filter or a high ambient room temperature. > >> > The system will shut down in 14 minutes and 0 seconds.. > >> > ------------------ > >> > > >> > So...is there any documentation for the hardware monitoring stuff? > >> > > >> > Brian > >> > > >> > > >> > > >> > ------------------------------------------------------------------------- > >> > This SF.net email is sponsored by: Microsoft > >> > Defy all challenges. Microsoft(R) Visual Studio 2008. > >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> > _______________________________________________ > >> > Es40-developers mailing list > >> > Es4...@li... > >> > https://lists.sourceforge.net/lists/listinfo/es40-developers > >> > > >> > >> ------------------------------------------------------------------------- > >> This SF.net email is sponsored by: Microsoft > >> Defy all challenges. Microsoft(R) Visual Studio 2008. > >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> _______________________________________________ > >> Es40-developers mailing list > >> Es4...@li... > >> https://lists.sourceforge.net/lists/listinfo/es40-developers > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Es40-developers mailing list > Es4...@li... > https://lists.sourceforge.net/lists/listinfo/es40-developers |
|
From: Fausto S. <fa...@un...> - 2008-02-28 00:44:36
|
Hello Brian, but where can I found the media and license for $100? From HP site? ebay? thanks, fausto Quoting Brian Wheeler <bdw...@in...>: > There used to be one offered by Compaq, but I don't know if HP carried > it forward. For $100 you got media and a license of some sort. > > If you can find a copy of the media, you can run it and do some basic > things without having the OSF-BASE license PAK. > > Technically, I think the only way to run Tru64 with any enjoyment (and > legally) is to have a license. That said, I have heard of someone that > found a way to generate valid licenses on VMS. With the ability to do > that, you could generate an OSF-BASE license...both VMS' LICENSE and > OSF's lmf use the same validation methods. > > Brian > > > On Wed, 2008-02-27 at 19:28 +0100, Fausto Saporito wrote: >> Hello all, >> >> about this subject, i'm wondering if there's an hobbyist license for Tru64. >> Do you know if it's possible to subscribe such kind of licensing? >> >> thanks, >> fausto >> >> Quoting Brian Wheeler <bdw...@in...>: >> >> > Turns out that the temperatures aren't actually in BCD but in degrees >> > Celsius. This patch is a minor refactor of DPR, plus a change to the >> > keyboard driver to ignore the the make/break commands so it'll come up >> > with the vga card inserted. I'm going gather up a tru64 license and see >> > if I can get cde to run. I'll probably also try the networking. >> > >> > Brian >> > >> > >> > >> > On Wed, 2008-02-27 at 14:35 +0100, Camiel Vanderhoeven wrote: >> >> Hi Brian, >> >> >> >> The ES40 has a management processor that takes care of monitoring >> >> power suppies, fans, and other hardware bits and pieces. It is >> >> extremely difficult to find any information about this. I managed to >> >> find some info in the ES40 service manual, and basically played a lot >> >> with things to get them to show up properly in SRM. >> >> >> >> The management processor communicates with SRM - and I presume with >> >> the OS - through a thing called Dual-Port-RAM. One port is connected >> >> to the system bus, another to the management-processor. A lot of the >> >> bytes are places where the OS can read device information, but in some >> >> locations, the OS can deposit commands for the management-processor. >> >> The following copmmands were found out through trial-and-error and >> >> partial reverse engineering of SRM: >> >> >> >> Address locations for commands: >> >> // 0xf9: buffer size >> >> // 0xfb:fa qualifier / address >> >> // 0xfc: completion code (0 = ok, 80 = error, 81 = invalid code, 82 >> >> = invalid qualifier) >> >> // 0xfd: rmc command id for response >> >> // 0xfe: command code >> >> // 0xff: rmc command id for command >> >> >> >> Command codes: >> >> // 01: update EEPROM >> >> // 02: update baud rate >> >> // 03: write to OCP >> >> // F0: update RMC flash >> >> >> >> It could very well be that there are more commands I don't know about, >> >> and a failure to respond to these in a satisfactory manner may well be >> >> the cause of the power supply failures and temperature warnings. >> >> >> >> You can find most of what I managed to find out in DPR.cpp. Mind you, >> >> this is some of the oldest and least-touched code in the emulator. It >> >> has not changed (other than some of the standard changes that have >> >> been made to the entire emulator) for well over a year, and a lot of >> >> my comments are still in Dutch. (I'm sorry about that...) It might be >> >> a good idea to put some read/write tracers in DPR.cpp, and try to >> >> figure out what Tru64 is doing with these. >> >> >> >> Camiel. >> >> >> >> >> >> >> >> >> >> >> >> On Wed, Feb 27, 2008 at 2:19 PM, Brian Wheeler >> <bdw...@in...> wrote: >> >> > I did a full install from dqb0 to dqa0 and while there were some >> >> > timeouts (this build was before I started on the interrupt >> resend code) >> >> > it installed and configured correctly (I left it run unattended >> >> > overnight). >> >> > >> >> > However, once it came up, it started announcing hardware failures :) >> >> > >> >> > ----------------- >> >> > Broadcast Message from ro...@tr... (???) at 23:37 ... >> >> > >> >> > The redundant power supply has failed. >> >> > >> >> > Broadcast Message from ro...@tr... (???) at 23:37 ... >> >> > >> >> > The system temperature is high. Possible reasons are >> >> > a clogged air filter or a high ambient room temperature. >> >> > The system will shut down in 14 minutes and 0 seconds.. >> >> > ------------------ >> >> > >> >> > So...is there any documentation for the hardware monitoring stuff? >> >> > >> >> > Brian >> >> > >> >> > >> >> > >> >> > >> ------------------------------------------------------------------------- >> >> > This SF.net email is sponsored by: Microsoft >> >> > Defy all challenges. Microsoft(R) Visual Studio 2008. >> >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> >> > _______________________________________________ >> >> > Es40-developers mailing list >> >> > Es4...@li... >> >> > https://lists.sourceforge.net/lists/listinfo/es40-developers >> >> > >> >> >> >> ------------------------------------------------------------------------- >> >> This SF.net email is sponsored by: Microsoft >> >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> >> _______________________________________________ >> >> Es40-developers mailing list >> >> Es4...@li... >> >> https://lists.sourceforge.net/lists/listinfo/es40-developers >> > >> >> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> Es40-developers mailing list >> Es4...@li... >> https://lists.sourceforge.net/lists/listinfo/es40-developers > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Es40-developers mailing list > Es4...@li... > https://lists.sourceforge.net/lists/listinfo/es40-developers > |
|
From: Brian W. <bdw...@in...> - 2008-02-28 02:22:24
|
On Thu, 2008-02-28 at 01:44 +0100, Fausto Saporito wrote: > Hello Brian, > > but where can I found the media and license for $100? > From HP site? ebay? > > thanks, > fausto > You can probably find the media on ebay, but the license is usually tied to a machine. Judging by the lack of hits on the HP site, it doesn't look like they are doing it anymore...which isn't surprising since the last order date for AXP was last year sometime and there's no real development going on. Brian > Quoting Brian Wheeler <bdw...@in...>: > > > There used to be one offered by Compaq, but I don't know if HP carried > > it forward. For $100 you got media and a license of some sort. > > > > If you can find a copy of the media, you can run it and do some basic > > things without having the OSF-BASE license PAK. > > > > Technically, I think the only way to run Tru64 with any enjoyment (and > > legally) is to have a license. That said, I have heard of someone that > > found a way to generate valid licenses on VMS. With the ability to do > > that, you could generate an OSF-BASE license...both VMS' LICENSE and > > OSF's lmf use the same validation methods. > > > > Brian > > > > > > On Wed, 2008-02-27 at 19:28 +0100, Fausto Saporito wrote: > >> Hello all, > >> > >> about this subject, i'm wondering if there's an hobbyist license for Tru64. > >> Do you know if it's possible to subscribe such kind of licensing? > >> > >> thanks, > >> fausto > >> > >> Quoting Brian Wheeler <bdw...@in...>: > >> > >> > Turns out that the temperatures aren't actually in BCD but in degrees > >> > Celsius. This patch is a minor refactor of DPR, plus a change to the > >> > keyboard driver to ignore the the make/break commands so it'll come up > >> > with the vga card inserted. I'm going gather up a tru64 license and see > >> > if I can get cde to run. I'll probably also try the networking. > >> > > >> > Brian > >> > > >> > > >> > > >> > On Wed, 2008-02-27 at 14:35 +0100, Camiel Vanderhoeven wrote: > >> >> Hi Brian, > >> >> > >> >> The ES40 has a management processor that takes care of monitoring > >> >> power suppies, fans, and other hardware bits and pieces. It is > >> >> extremely difficult to find any information about this. I managed to > >> >> find some info in the ES40 service manual, and basically played a lot > >> >> with things to get them to show up properly in SRM. > >> >> > >> >> The management processor communicates with SRM - and I presume with > >> >> the OS - through a thing called Dual-Port-RAM. One port is connected > >> >> to the system bus, another to the management-processor. A lot of the > >> >> bytes are places where the OS can read device information, but in some > >> >> locations, the OS can deposit commands for the management-processor. > >> >> The following copmmands were found out through trial-and-error and > >> >> partial reverse engineering of SRM: > >> >> > >> >> Address locations for commands: > >> >> // 0xf9: buffer size > >> >> // 0xfb:fa qualifier / address > >> >> // 0xfc: completion code (0 = ok, 80 = error, 81 = invalid code, 82 > >> >> = invalid qualifier) > >> >> // 0xfd: rmc command id for response > >> >> // 0xfe: command code > >> >> // 0xff: rmc command id for command > >> >> > >> >> Command codes: > >> >> // 01: update EEPROM > >> >> // 02: update baud rate > >> >> // 03: write to OCP > >> >> // F0: update RMC flash > >> >> > >> >> It could very well be that there are more commands I don't know about, > >> >> and a failure to respond to these in a satisfactory manner may well be > >> >> the cause of the power supply failures and temperature warnings. > >> >> > >> >> You can find most of what I managed to find out in DPR.cpp. Mind you, > >> >> this is some of the oldest and least-touched code in the emulator. It > >> >> has not changed (other than some of the standard changes that have > >> >> been made to the entire emulator) for well over a year, and a lot of > >> >> my comments are still in Dutch. (I'm sorry about that...) It might be > >> >> a good idea to put some read/write tracers in DPR.cpp, and try to > >> >> figure out what Tru64 is doing with these. > >> >> > >> >> Camiel. > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> On Wed, Feb 27, 2008 at 2:19 PM, Brian Wheeler > >> <bdw...@in...> wrote: > >> >> > I did a full install from dqb0 to dqa0 and while there were some > >> >> > timeouts (this build was before I started on the interrupt > >> resend code) > >> >> > it installed and configured correctly (I left it run unattended > >> >> > overnight). > >> >> > > >> >> > However, once it came up, it started announcing hardware failures :) > >> >> > > >> >> > ----------------- > >> >> > Broadcast Message from ro...@tr... (???) at 23:37 ... > >> >> > > >> >> > The redundant power supply has failed. > >> >> > > >> >> > Broadcast Message from ro...@tr... (???) at 23:37 ... > >> >> > > >> >> > The system temperature is high. Possible reasons are > >> >> > a clogged air filter or a high ambient room temperature. > >> >> > The system will shut down in 14 minutes and 0 seconds.. > >> >> > ------------------ > >> >> > > >> >> > So...is there any documentation for the hardware monitoring stuff? > >> >> > > >> >> > Brian > >> >> > > >> >> > > >> >> > > >> >> > > >> ------------------------------------------------------------------------- > >> >> > This SF.net email is sponsored by: Microsoft > >> >> > Defy all challenges. Microsoft(R) Visual Studio 2008. > >> >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> >> > _______________________________________________ > >> >> > Es40-developers mailing list > >> >> > Es4...@li... > >> >> > https://lists.sourceforge.net/lists/listinfo/es40-developers > >> >> > > >> >> > >> >> ------------------------------------------------------------------------- > >> >> This SF.net email is sponsored by: Microsoft > >> >> Defy all challenges. Microsoft(R) Visual Studio 2008. > >> >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> >> _______________________________________________ > >> >> Es40-developers mailing list > >> >> Es4...@li... > >> >> https://lists.sourceforge.net/lists/listinfo/es40-developers > >> > > >> > >> > >> > >> ------------------------------------------------------------------------- > >> This SF.net email is sponsored by: Microsoft > >> Defy all challenges. Microsoft(R) Visual Studio 2008. > >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> _______________________________________________ > >> Es40-developers mailing list > >> Es4...@li... > >> https://lists.sourceforge.net/lists/listinfo/es40-developers > > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > Es40-developers mailing list > > Es4...@li... > > https://lists.sourceforge.net/lists/listinfo/es40-developers > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Es40-developers mailing list > Es4...@li... > https://lists.sourceforge.net/lists/listinfo/es40-developers |
|
From: Fausto S. <fa...@un...> - 2008-02-28 07:48:09
|
Hello all, between an OpenVMS installation and another, I downloaded the netbsd 4.0 cdrom. The boot seems fine, but kernel goes in panic :-) at panic: pci_display_console: no device at 255/255/0 Stopped at 0xffffffc00005da050: ret (zero),ra What is 255/255/0?? a PCI address? regards, fausto |
|
From: Camiel V. <iam...@gm...> - 2008-02-28 09:18:59
|
Hello Fausto, I'm no expert on NetBSD, but a quick google search on "pci_display_console" and "255/255/0" leads me to a couple of discussions on this message, all of them NetBSD on Alpha, so it looks like it's something that happens on real Alpha's as well... Camiel. On Thu, Feb 28, 2008 at 8:47 AM, Fausto Saporito <fa...@un...> wrote: > Hello all, > > between an OpenVMS installation and another, I downloaded the netbsd > 4.0 cdrom. > The boot seems fine, but kernel goes in panic :-) at > > panic: pci_display_console: no device at 255/255/0 > Stopped at 0xffffffc00005da050: ret (zero),ra > > What is 255/255/0?? a PCI address? > > regards, > fausto > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Es40-developers mailing list > Es4...@li... > https://lists.sourceforge.net/lists/listinfo/es40-developers > |
|
From: Fausto S. <fa...@un...> - 2008-02-28 11:30:29
|
Hello Camiel, so it seems the emulated graphic cards are not supported under NetBSD :-) Ok... I give up, and I'll try FreeBSD, maybe I will be more lucky. Fausto Quoting Camiel Vanderhoeven <iam...@gm...>: > Hello Fausto, > > I'm no expert on NetBSD, but a quick google search on > "pci_display_console" and "255/255/0" leads me to a couple of > discussions on this message, all of them NetBSD on Alpha, so it looks > like it's something that happens on real Alpha's as well... > > Camiel. > > On Thu, Feb 28, 2008 at 8:47 AM, Fausto Saporito <fa...@un...> wrote: >> Hello all, >> >> between an OpenVMS installation and another, I downloaded the netbsd >> 4.0 cdrom. >> The boot seems fine, but kernel goes in panic :-) at >> >> panic: pci_display_console: no device at 255/255/0 >> Stopped at 0xffffffc00005da050: ret (zero),ra >> >> What is 255/255/0?? a PCI address? >> >> regards, >> fausto >> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> Es40-developers mailing list >> Es4...@li... >> https://lists.sourceforge.net/lists/listinfo/es40-developers >> > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Es40-developers mailing list > Es4...@li... > https://lists.sourceforge.net/lists/listinfo/es40-developers > |
|
From: Brian W. <bdw...@in...> - 2008-02-28 13:27:26
|
On Thu, 2008-02-28 at 12:30 +0100, Fausto Saporito wrote: > Hello Camiel, > > so it seems the emulated graphic cards are not supported under NetBSD :-) > Ok... I give up, and I'll try FreeBSD, maybe I will be more lucky. > I've been looking at that off and on for ages and I can't figure out what NetBSD is doing before it panics. The only thing I was able to see was it would look at the PCI config and then barf. Tru64 also barfs when trying to start up X. I haven't been able to find an X server for freebsd, so if you find one, let me know. Brian > Fausto > > Quoting Camiel Vanderhoeven <iam...@gm...>: > > > Hello Fausto, > > > > I'm no expert on NetBSD, but a quick google search on > > "pci_display_console" and "255/255/0" leads me to a couple of > > discussions on this message, all of them NetBSD on Alpha, so it looks > > like it's something that happens on real Alpha's as well... > > > > Camiel. > > > > On Thu, Feb 28, 2008 at 8:47 AM, Fausto Saporito <fa...@un...> wrote: > >> Hello all, > >> > >> between an OpenVMS installation and another, I downloaded the netbsd > >> 4.0 cdrom. > >> The boot seems fine, but kernel goes in panic :-) at > >> > >> panic: pci_display_console: no device at 255/255/0 > >> Stopped at 0xffffffc00005da050: ret (zero),ra > >> > >> What is 255/255/0?? a PCI address? > >> > >> regards, > >> fausto > >> > >> > >> ------------------------------------------------------------------------- > >> This SF.net email is sponsored by: Microsoft > >> Defy all challenges. Microsoft(R) Visual Studio 2008. > >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> _______________________________________________ > >> Es40-developers mailing list > >> Es4...@li... > >> https://lists.sourceforge.net/lists/listinfo/es40-developers > >> > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > Es40-developers mailing list > > Es4...@li... > > https://lists.sourceforge.net/lists/listinfo/es40-developers > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Es40-developers mailing list > Es4...@li... > https://lists.sourceforge.net/lists/listinfo/es40-developers |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X