• Welcome to OS2World OLD-STATIC-BACKUP Forum.
 

News:

This is an old OS2World backup forum for reference only. IT IS READ ONLY!!!

If you need help with OS/2 - eComStation visit http://www.os2world.com/forum

Main Menu

Recent posts

#21
Setup & Installation / Re: Intel chipset not fully su...
Last post by rwklein - 2012.09.29, 16:33:18
Quote from: StefanZ on 2012.09.29, 15:45:06
Hello Roderick,

thank you for your reply.

The main idea behind my question was if there is anything specific what I can do - as a single end user - to make sure that my system is better support in the future versions of ACPI?
...or is it better to wait for newer versions of ACPI that will get progressively better?

(I decided to act because it seems a bit ridiculous why my (standard Intel) system should not be supported at any time by any  of (even  the old) versions of acpi. I'm getting worried a bit that my system might actually never be fully supported...).

Thanks.
St.

You conclude from the fact that the throttle support is not supported that your chipset is not fully supported basically.
Before eCS 2.1 we never shipped any type of CPU method to cool down the CPU.

People had noted that the old _W4 kernel would keep CPU's cool. The SMP kernel we use in eCS does did have that HLT support the _W4 kernel has! So powerman.exe demon was implemented. It turned out these two ways it tries todo throttle support depend on the BIOS implementation. A lot of CPU's did this not work.

Infact based on the measurements David (who works on ACPI). The two throttle ways powerman.exe supports
slow down your system as it has to get from a "speed" up to a full speed.

Over the years we looked at implementing a way to get HLT support on an SMP system. But it was not easy as the SMP kernel has different ways of doing stuff then _W4 kernel does. The HLT support does not have the negative performance effect the throttle support powerman.exe offers. On top of that the HLT support provides even better power savings then the technology that powerman.exe provides. So the GUI to setup powerman and powerman.exe itself will go away in eCS 2.2.

The HLT support is effective automaticly by installing recent ACPI versions.
You can see it under acpistat.exe

ACPI name [CPU0]
IPIGenCount = 27585      IPICount    = 84680
IPIHLT      = 0          IdleCount   = 213371     BusyCount   = 25384

This works on just about any system with an AMD/Intel CPU. The success rate is WAAAY higher then with the ways powerman.exe supports.

So from that perspective it seems your throttle support we already support your system optimal. As an added bonus if the system is not being used other CPU cores are switched of automatically by ACPI and switched on back within a blink of an eye! So when it comes to throttle support of the CPU we are in good shape!

Roderick Klein
Mensys
#22
Setup & Installation / Re: Intel chipset not fully su...
Last post by StefanZ - 2012.09.29, 15:45:06
Hello Roderick,

thank you for your reply.

The main idea behind my question was if there is anything specific what I can do - as a single end user - to make sure that my system is better support in the future versions of ACPI?
...or is it better to wait for newer versions of ACPI that will get progressively better?

(I decided to act because it seems a bit ridiculous why my (standard Intel) system should not be supported at any time by any  of (even  the old) versions of acpi. I'm getting worried a bit that my system might actually never be fully supported...).

Thanks.
St.
#23
Article Discussions / Re: What is the future of this...
Last post by dryeo - 2012.09.29, 08:39:34
Quote from: DougB on 2012.09.28, 23:03:08
Well, now I am running into configuration problems. For some reason, Paul's build seems to want to configure to build a Mozilla derivative, and it wants to use U:\moztools\config.site-gcc335b4. That file is from a release of moztools, as released by Dave Yeo, not too long ago. It bears no relation, at all, to my system, and a number of the entries don't make sense, to me. I don't think it should be using that anyway.

So, I removed the environment variables for MOZILLA, and CONFIG_SITE. Then, I get some reasonable output from:
ash ./configure
but it seems to want a different GREP than what is available. The error lines, from config.log are;
configure:5382: checking for grep that handles long lines and -e
configure:5433: error: no acceptable grep could be found in U:\foo;U:\usr\bin;U:\usr\local\bin;U:\GLIBIDL335\GLIB\gcc\bin;U:\GLIBIDL335\LIBIDL\gcc\bin;u:\PERL\bin;u:\bin;U:\MOZTOOLS;U:\EMX\bin;u:\extras\bin;u:\dev\qt\trunk\bin;U:\python25;M:\MPTN\BIN;M:\IBMCOM;M:\ECS\SYSTEM\Samba;M:\ECS\BIN;M:\TCPIP\BIN;W:\PROGRAMS\EMX\BIN;M:\IBMGSK50\BIN;M:\IBMGSK40\BIN;M:\IBMGSK\BIN;M:\OS2;M:\OS2\SYSTEM;M:\OS2\INSTALL;M:\;M:\OS2\MDOS;M:\OS2\APPS;M:\ECS\KLIBC\BIN;W:\PROGRAMS\JAVA142\BIN;M:\MMOS2\FREEDB;M:\MMOS2;M:\MMOS2\MMPLAYER;W:\PROGRAMS\4OS2;W:\PROGRAMS\OPENSSH;W:\UTILITY;W:\APPS\WGET\BIN;W:\TOOLS\dfsee\bin;W:\ODIN\SYSTEM32;W:\LOTUSW4\COMPNENT;W:\LOTUSW4\ORGANIZE;W:\LOTUSW4\APPROACH;W:\LOTUSW4\FLG;W:\LOTUSW4\WORDPRO;W:\APPS\BA2KWS;W:\PROGRAMS\qt4\bin;W:\APPS\EMBLSH;M:\ecs\ACPI\UTIL;U:\WATCOM\BINP;U:\WATCOM\BINW;U:\VISPRORX;;;/usr/xpg4/bin


Question: What is that all about?

As Paul hinted, it is looking for grep instead of grep.exe. You need exeext=.exe or/and ac_executable_extensions=.exe in your environment, preferably in config.site or set GREP=grep.exe, then perhaps PERL=perl.exe and so on.
BTW, I didn't release that moztools though it is basically the same as the one I use.
#24
Article Discussions / Re: What is the future of this...
Last post by dryeo - 2012.09.29, 08:27:01
Quote from: DougB on 2012.09.28, 07:22:47
QuoteI think it may help if someone can write some article on the EDM/2 on how to set up Paul's environment.
[...]

The download file contains a directory (wget-1.14). Put that on the same drive as Paul's build environment. Then, click on the icon that you built to launch paul's build environment. That should get you to a command line. Change to the wget-1.14 directory, and now we need to figure out how to build it. Paul's instructions are a little confusing at this point (and somewhat incomplete in some more complicated cases).

Since I am tired, I will quit here, and hopefully, somebody will make this a little easier. I am not at all sure if I still have the original setup files, or if I have messed around with them. I don't normally use the setup as Paul supplied it (which seems to be set up to build a mozilla derivative, and I do not have the latest version), so I am somewhat lost here. I am sure that most people will have the same problem.

What I'd do (I don't have Pauls environment) is open EPM,  and open a shell within EPM. (Command --> Create command shell). Now we have a scrolling window for reviewing output.
Start out by doing sh configure --help (I use [pdk]sh.exe, substitute ash if you prefer) and examine the output. Of interest are options such as --enable-threads={posix|solaris|pth|windows} --disable-ipv6, ssl options, libiconv, libintl and whether to support nls options. We'll come back to this if configure makes mistakes in configuring for the build system.
Then try sh configure and watch the configure script figure out the build environment, what tools we have installed and what our libc supports.
Eventually here configure errors out with,

checking for libgnutls... no
configure: error: --with-ssl was given, but GNUTLS is not available


So we have to decide whether to use openssl. (Openssl has an incompatible license with GPL v2 ). For our first test build we'll disable it, so rerun configure as sh configure --without-ssl.
Eventually configure ends by creating a bunch of makefiles, so now we can do
make
and after a bunch of output make dies with
epbase=`echo spawn-pipe.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
gcc.exe -DHAVE_CONFIG_H -I. -I../src   -I/usr/local/include  -O2 -Wall -MT spawn-pipe.o -MD -MP -MF $depbase.Tpo -c -o spawn-pipe.o spawn-pipe.c &&\
mv -f $depbase.Tpo $depbase.Po
In file included from ./spawn.h:37,
                 from spawn-pipe.c:47:
./sched.h:43: error: redefinition of 'struct sched_param'

So need to examine what is different between lib\spawn.h and lib\sched.h and how they relate to our headers.
Search \usr\include for sched_param, we find it in spawn.h with a comment, todo implement sched.h.
Perhaps configure got confused by not finding sched.h? As we have sched_param we should be able to ignore the one included by lib\spawn.h. Best seems to try to change line 35 in spawn.h.in from
#if !(defined __GLIBC__ && !defined __UCLIBC__)
to
#if !(defined __GLIBC__ && !defined __UCLIBC__ || defined __OS2__)
and try again.
This time make finishes by building src\wget.exe so see if it runs by cd src && wget --version and it seems to work.
Now to test by doing make check which unluckily dies here due to perl issues. These can probably be fixed or can test wget by downloading things and seeing if they work.
Ideally after the build error is to contact the authours of wget for advice on the best way to fix the problem and get a fix into the code so the next version builds out of the box.
#25
Quote from: DougB on 2012.09.28, 23:03:08
Well, now I am running into configuration problems. For some reason, Paul's build seems to want to configure to build a Mozilla derivative, and it wants to use U:\moztools\config.site-gcc335b4. That file is from a release of moztools, as released by Dave Yeo, not too long ago. It bears no relation, at all, to my system, and a number of the entries don't make sense, to me. I don't think it should be using that anyway.

So, I removed the environment variables for MOZILLA, and CONFIG_SITE. Then, I get some reasonable output from:
ash ./configure
but it seems to want a different GREP than what is available. The error lines, from config.log are;
configure:5382: checking for grep that handles long lines and -e
configure:5433: error: no acceptable grep could be found in U:\foo;U:\usr\bin;U:\usr\local\bin;U:\GLIBIDL335\GLIB\gcc\bin;U:\GLIBIDL335\LIBIDL\gcc\bin;u:\PERL\bin;u:\bin;U:\MOZTOOLS;U:\EMX\bin;u:\extras\bin;u:\dev\qt\trunk\bin;U:\python25;M:\MPTN\BIN;M:\IBMCOM;M:\ECS\SYSTEM\Samba;M:\ECS\BIN;M:\TCPIP\BIN;W:\PROGRAMS\EMX\BIN;M:\IBMGSK50\BIN;M:\IBMGSK40\BIN;M:\IBMGSK\BIN;M:\OS2;M:\OS2\SYSTEM;M:\OS2\INSTALL;M:\;M:\OS2\MDOS;M:\OS2\APPS;M:\ECS\KLIBC\BIN;W:\PROGRAMS\JAVA142\BIN;M:\MMOS2\FREEDB;M:\MMOS2;M:\MMOS2\MMPLAYER;W:\PROGRAMS\4OS2;W:\PROGRAMS\OPENSSH;W:\UTILITY;W:\APPS\WGET\BIN;W:\TOOLS\dfsee\bin;W:\ODIN\SYSTEM32;W:\LOTUSW4\COMPNENT;W:\LOTUSW4\ORGANIZE;W:\LOTUSW4\APPROACH;W:\LOTUSW4\FLG;W:\LOTUSW4\WORDPRO;W:\APPS\BA2KWS;W:\PROGRAMS\qt4\bin;W:\APPS\EMBLSH;M:\ecs\ACPI\UTIL;U:\WATCOM\BINP;U:\WATCOM\BINW;U:\VISPRORX;;;/usr/xpg4/bin


Question: What is that all about?

FWIW - I don't recommend removing the CONFIG_SITE reference.  Yes the config.site is located in a /moztools directory, and yes, it started life as a version used to build mozilla, but it's progressed a long way from that, and contains many things that 'help' configure - including grep.

Another way around the grep issue is to run:
'set grep=grep.exe' before running ./configure
#26
Setup & Installation / Re: Intel chipset not fully su...
Last post by rwklein - 2012.09.29, 02:24:41
Quote from: StefanZ on 2012.09.28, 19:27:05
What should one do, if running on Intel ICH9 family chipset and gets this out of ACPI:

This system does not support CPU Performance Control via ACPI.

This system does not support CPU Throttling.

Thermal information:
  No Thermal information is available for this computer


Does it mean my system is so nonstandard?  :'(
St.

The latest versions if ACPI the use the HLT instruction with the SMP kernel (its active automaticly) just like it was in _W4 kernel. The old throttle stuff is less efficient and the GUI will be removed. Since the HLT instruction is much more efficient
and works on just about any CPU.

Roderick Klein

#27
Article Discussions / Re: What is the future of this...
Last post by DougB - 2012.09.28, 23:03:08
Well, now I am running into configuration problems. For some reason, Paul's build seems to want to configure to build a Mozilla derivative, and it wants to use U:\moztools\config.site-gcc335b4. That file is from a release of moztools, as released by Dave Yeo, not too long ago. It bears no relation, at all, to my system, and a number of the entries don't make sense, to me. I don't think it should be using that anyway.

So, I removed the environment variables for MOZILLA, and CONFIG_SITE. Then, I get some reasonable output from:
ash ./configure
but it seems to want a different GREP than what is available. The error lines, from config.log are;
configure:5382: checking for grep that handles long lines and -e
configure:5433: error: no acceptable grep could be found in U:\foo;U:\usr\bin;U:\usr\local\bin;U:\GLIBIDL335\GLIB\gcc\bin;U:\GLIBIDL335\LIBIDL\gcc\bin;u:\PERL\bin;u:\bin;U:\MOZTOOLS;U:\EMX\bin;u:\extras\bin;u:\dev\qt\trunk\bin;U:\python25;M:\MPTN\BIN;M:\IBMCOM;M:\ECS\SYSTEM\Samba;M:\ECS\BIN;M:\TCPIP\BIN;W:\PROGRAMS\EMX\BIN;M:\IBMGSK50\BIN;M:\IBMGSK40\BIN;M:\IBMGSK\BIN;M:\OS2;M:\OS2\SYSTEM;M:\OS2\INSTALL;M:\;M:\OS2\MDOS;M:\OS2\APPS;M:\ECS\KLIBC\BIN;W:\PROGRAMS\JAVA142\BIN;M:\MMOS2\FREEDB;M:\MMOS2;M:\MMOS2\MMPLAYER;W:\PROGRAMS\4OS2;W:\PROGRAMS\OPENSSH;W:\UTILITY;W:\APPS\WGET\BIN;W:\TOOLS\dfsee\bin;W:\ODIN\SYSTEM32;W:\LOTUSW4\COMPNENT;W:\LOTUSW4\ORGANIZE;W:\LOTUSW4\APPROACH;W:\LOTUSW4\FLG;W:\LOTUSW4\WORDPRO;W:\APPS\BA2KWS;W:\PROGRAMS\qt4\bin;W:\APPS\EMBLSH;M:\ecs\ACPI\UTIL;U:\WATCOM\BINP;U:\WATCOM\BINW;U:\VISPRORX;;;/usr/xpg4/bin


Question: What is that all about?
#28
Setup & Installation / Intel chipset not fully suppor...
Last post by StefanZ - 2012.09.28, 19:27:05
What should one do, if running on Intel ICH9 family chipset and gets this out of ACPI:

This system does not support CPU Performance Control via ACPI.

This system does not support CPU Throttling.

Thermal information:
 No Thermal information is available for this computer


Does it mean my system is so nonstandard?  :'(
St.
#29
Applications / Re: WebDav and eComStation
Last post by miturbide - 2012.09.28, 16:54:02
Thanks Batchheizer

Even that I don't understand German, Google Translate gives me a very good hint of the article contents. Thanks
#30
Article Discussions / Re: What is the future of this...
Last post by DougB - 2012.09.28, 07:22:47
QuoteI think it may help if someone can write some article on the EDM/2 on how to set up Paul's environment.

Setting up the environment means following the readme.os2 that comes with it. There is no magic there, just do as it says. Of course, you do complicate things somewhat, if you use a different drive letter.

I think the main problem is "what do I do now?" I guess the answer would be to pick a project that you want to build, and then do it. Then, it will either build, or it won't. If it does, you can be pretty sure that your basic setup is good. If it won't build, you need to figure out why it won't build, and that is where asking lots of questions (without being a PITA) comes in. The WGET program was suggested as a reasonable staring point, because it is relatively simple, and it is known to build, without problems (at least that is what I understand, I haven't actually tried it, so let's have a go.

The source is available at: http://www.gnu.org/software/wget/

You have the basic choice of an HTML page, or a FTP page. Now, you need to determine what package to get. Lets be brave, and pick the latest version (1.14). Now, there are 4 files for that. 2 are .sig files, which are probably some sort of file verification thing. We will ignore them. Now, you have a choice between wget-1.14.tar.gz or wget-1.14.tar.xz. I have no idea what .xz is, but .gz is something that the eCS archive viewer will unwrap, so lets see what we get. Looks okay to me (but what do I know?).

The download file contains a directory (wget-1.14). Put that on the same drive as Paul's build environment. Then, click on the icon that you built to launch paul's build environment. That should get you to a command line. Change to the wget-1.14 directory, and now we need to figure out how to build it. Paul's instructions are a little confusing at this point (and somewhat incomplete in some more complicated cases).

Since I am tired, I will quit here, and hopefully, somebody will make this a little easier. I am not at all sure if I still have the original setup files, or if I have messed around with them. I don't normally use the setup as Paul supplied it (which seems to be set up to build a mozilla derivative, and I do not have the latest version), so I am somewhat lost here. I am sure that most people will have the same problem.