Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Dariusz Piatkowski

Pages: 1 2 [3] 4 5 ... 96
31
Programming / Re: stopping cpus
« on: February 28, 2025, 04:51:02 pm »
Hi Doug!

...
3- Dave/Darius - I am afraid to turn off power management after reading the warnings in the ACPI docs - which basically say thermals may become a problem if you mess with power settings.  I did download the ACPI sdk and look through the documentation and I didn't see any function that seemed to address turning on or off processors.  But I might have missed something.
...
I suspect, like Darius, that either the processors aren't getting turned off, or something is turning them back on.  This appears to happen on both Ryzen and Intel processors. One using SNAP and the other using Panaroma.

From a 'good to know how to configure this' perspective the easiest way to TEST this on your machine is to DISABLE the ACPI PowerManager (as per the note that Dave posted, see acpid.cfg file). I believe ACPI daemon dynamically picks this up, so no reboot is necessary.

Then you can shut OFF the cores you do not need running and test your WIN-OS/2 use.

If this work, you know precisely HOW to get this working when you need it working. After all, re-enabling the ACPI PowerManager is just as easy as disabling it. You could literally have a little pm_off.cmd & pm_on.cmd scripts that simply replace the appropriate acpid.cfg files, which ACPI PM then recognizes.

In my experience the big CPU temperature spikes only occur when you really start pushing the machine. We are talking here heavy FLOAT ops such as running the SYSBENCH FLOAT benchmark, etc.

For example: as I play around with this stuff on my end I find that the 48C idle temp of my AMD FX-8370 CPU (8 core, 5GHz) goes up to 51C...which is a pretty tiny amount of just 3C increase. But make note that this is only achieved by deploying the Noctua NH-15D CPU cooler, which is very much in the realm of the overclocking domain.

Prior to installing this cooler I was running a Corsair A70 setup, which was showing 55C at idle and when running the SYSBENCH FLOAT tests the temp would spike all the way to 64C. Heck, a couple of times (as I was screwing around with both CPU frequency and core voltage) I actually had the whole box automatically shut-down.

Soooo....with today's systems there is a good amount of protection built-in...but it's always good to review your specific specs to know exactly what your MAX values are.

Ultimately the experimentation is what will give you the true answers.

EDIT
====

HERE (https://man.netbsd.org/acpicpu.4) is a good summary of all of these C/P/T-states, how they relate to each other, etc.

32
Programming / Re: stopping cpus
« on: February 28, 2025, 04:33:51 pm »
Dave, everyone...

Don't forget that you can disable/enable PowerMan by changing one line in \mptn\etc\acpid.cfg,
Code: [Select]
[PowerMan]

; Enable: 1=enabled, 0=disabled, default=1
Enable = 1

Correct, that is exactly how I control whether PowerManager is running, although in my case it is permanently turned OFF.

...And the ConfigCheckInterval can be changed from the default of 10 secs if you want a faster result from changing the enabled line.
Personally, my little computer will get too hot with PowerMan disabled though disabling for a while may be acceptable.
Also there is the ACPI sdk, which I've never looked at, IIRC it can be installed from the acpi.wpi.

Yeah, good point here. There certainly are numerous available parameters that one can tweak in order to get a more "fitting" configuration enabled. In my case, much like what Lars' comment highlighted, having spent a good amount of time working through these I was simply unable to get that balance. The system was always lagging in turning on the CPU/cores when I needed the extra power, this resulted in that "why are things running so slow?" kind of a feel.

I did actually reach out to DavidA (AOS) to work through this, but following several back'n'forth exchanges I was simply told "that's how it works, nothing to change here, it is correct". It is not that he is wrong, I understood all his points but perhaps the ACPI implementation on our platform just can't provide the sort of seamless power transition experience we normally see on other platforms?

33
Programming / Re: stopping cpus
« on: February 28, 2025, 04:12:50 am »
Ahhh...so I'm going to float an idea here that I have arrived at having personally fought through symptoms such as what you just described, and eventually figure out the relationships at play.

The modern day combination of OS/2 software to support/enable SMP most likely has us all using the ACPI driver, and that by default also means that we have the ACPI daemon managing the CPU/cores according to how you actually configure the system.

What this means is that APCI will attempt to use it's fairly sophisticated logic to enable things such as CPU power saving modes (think of the different CPU Cx states here). Basically these are the PowerManager settings in the acpid.cfg file sitting in \mptn\etc.

Now by DEFAULT the ACPI install has the PowerManager enabled and that also means that ACPI and NOT YOU are deciding what a particular CPU/core should be doing. Heck, on the surface acpid.cfg has enough settings there for you to almost set it up for a nearly seamless "power on when I need it" type of an experience.

....BBBUUUUTTTTT.....that also means that ACPI will insist on being the one who controls your CPU/cores and so subsequently when you are attempting to power off/disable a CPU core using an API call such as DosSetProcessorStatus, it most certainly will, but in the background ACPI will immediately take over and either undo what you just did, or if the system is nearly IDLE it may in fact let that CPU/core stay in disabled status.

This very thing caused me a boat-load of problems b/c on my OS/2 box (4.52, so non AOS install but using the same ACPI release) I occasionally have an OS/2 application that will lock my box (soft freeze, CTRL+ALT+DEL still works to power down) during app startup (I have been told maybe SNAP driver related, I think it is something else), and so I took to using a REXX wrapper to always disable all but a single CPU core before I needed to run such a program. Well, as you can imagine when I moved over to ACPI I all of a sudden was plagued by these soft locks 'once again'...I worked and worked through numerous iterations of configs until I finally discovered that the default ACPI PowerManager settings were occasionally flipping ON one of the just disabled cores and BAM...yup, the lock-up would occur.

Soooo....bottom line here is that on this 24x7 box of mine I do not care at all about how much power that sucker eats up, it is backed up by a 1500W UPS box and stays on all the time, running at full 5.2GHz core speed across all eight of it's cores!

Happy with what I have, combination works for me, but it did require me to disable the ACPI PowerManager.

So what I'm curious about Doug is what that specific error message is that you are seeing? Could it be that DosSetProcessorStatus API was patched to sync it up with the ACPI daemon's logic which is driven by the PowerManager??? That would be fancy, although I doubt that is the case.

Food for thought - I am actually trying to understand the whole ACPI system b/c I'd like to create a little utility that tells us a lot more about what the current hardware configuration, and specifically CPU runtime readings are like, we are talking the Cx core states, the actual frequency different cores are running, heck ACPI is even supposed to give you the ability to see the CPU L1/2/3 cache hit ratios, etc....cool stuff!

34
Hello Alfredo!

The topic you raise here is equally applicable to all the other programming languages on our platform.

'Knowledge is Power', right?

So I would suggest that where things start for us is in establishing a good Developer Library/References.

I've attached what such a library looks like on my machine, specifically focusing on REXX. This is a mix of freely available information, as well as PDF downloads of previously commercial books, etc.

Now you may argue that the PDFs in particular are illegal, etc., etc....OK, fine, so why not provide an executable d/l script that simply uses wget to pull this list down from any of the well recognized archive sites??? That way each end-user makes this decision for themselves!

Bottom line being: tutorial, try-by-example, all these things are great, but when you are new to something you ultimately need a solid 'something to go to in order to understand what the example code/API does', and that's the missing piece for us I think.

35
Virtualization / Re: A new video about OS/2 after more than 4 Years...
« on: February 21, 2025, 04:10:56 pm »
Hi Sigurd,
That's a nice 'write-up', good video coverage of the functionality. Thank you sir!

36
Setup & Installation / Re: How to reinstall files missing from /usr/bin?
« on: February 14, 2025, 05:40:36 am »
'yum history' will give you a breakdown of what what installed and when.

You could then chose to re-execute the specific TRX ID, but by all accounts this is a vastly manual effort.

37
Applications / Re: ePDF
« on: February 14, 2025, 05:29:21 am »
i'm also using 9.18-version.
With STDIO i get:
Error: /undefined in E&k0G&l1T*t600R&u600D*r0F&l0S&l0O&l26A&l1H&l0M&l0E*c5611x8416Y*p0x120Y*c0T
Operand stack:
...

Do all attempts at printing fail this way with this specific error, or is this just a specific job?

For what it's worth, if you can share the document I can attemp to print to ePDF here and we can compare the results...maybe that gives us more details to go off of?

38
Hardware / Re: Printer
« on: February 05, 2025, 04:56:59 am »
Try looking at the Brother range of laser printers.  I have two, a HL-3170cdw and DCP-9020cdw, both have postscript emulation (BR-Script3), hence the use of the PSPRINT driver, do not require special drivers other than SLPR and both work over my local network.

I'll give Brother the vote as well. Running the HL-5470DW model here, duplex, quick and I even managed to tweak the published PPD file and import it to enable controls for MOST of the features. The one thing that failed was the ability for the PSCRIPT driver to run the HQ1200 (so High Quality emulated mode, just faster and obviously less sharp version of the full 1200dpi print option). No problem though b/c for some reason the PSPRINT drive actually handles that one very well. So for quick jobs I send to PSPRINT, for quality jobs I send to PSCRIPT drivers.

39
Applications / Re: ePDF
« on: February 05, 2025, 04:51:49 am »
hello andreas!

What version of eDPF do you have?

I am using '2.99-6 - Jan 2021', and have it configured to use two different Distillers:

1) 9.04
2) 9.18

I use 9.18 regularly and the following are the settings;

'Path to Distiller:' - g:\usr\bin\gsos2.exe

'Library path:' - g:\usr\lib;g:\usr\share\fonts\default\ghostscript;G:\usr\share\fonts\default\type1;g:\psfonts

Of course you need to adjust for the proper DRIVE your OS/2 box is using.

To troubleshoot further head on over to the 'Options' tab and check mark the 'enable STDIO (debug mode)', which will leave the Distiller session up after ePDF calls it. At least that way you might get some tell-tale look at what other errors might be coming at ya?

Oh, one more thing: I think ePDF builds a CMD file that it passes to Distiller, which is what that STDIO window shows you. Look for that CMD file wherever your TEMP variable points to, if I recall correctly. Once you find it you always have the option to run it manually from CLI to better assess what's going on.

40
andreas,

i tried chkdsk C:/ F:1    what does /D x: do?

Courtesy of Lewis (AOS) and sTeven Levine (whom he credits for sharing his notes on this topic):

Code: [Select]
Check FS content
Usage: chkdsk drive: [/A] [/B] [/C] [/D] [/F[:n]] [/O] [/P] [/V]

/A - Enable autocheck mode (undocumented)

/B - Perform LVM Bad Block List utility processing only

/C - Process ifdirty after logredo

/D - Enable debug mode (undocumented) all log messages written to stdout in english

/F[:n] Full check

0 => read only (default)
1 => prompt for permission for each repair
2 => preen (default if n omitted)
3 => Assume permission given for all repairs.

If exiting with clean file system, invoke LVM Bad Block List utility processing on the way out.

Note: :1 and :2 are converted to :3

/O - Omit logredo (undocumented)

/P - Enable pmchkdsk mode (undocumented)

/V - Verbose messaging (ignored)

Both / and - prefix supported
Options are case-insenitive Called as chkdsk drive: /F /A [/C] for autocheck

41
Applications / Re: PMMail fails sending messages
« on: January 20, 2025, 08:33:59 pm »
I am desperatly trying to make PMMail sending messages without success.
I am a registered user and I am running PMMail 3.11.30.1767.
Receiving messages works pretty good. But sending doesn't.
...
Any hints what to try to make PMMail send messages succesfully?

What does PMMail log show?

You can find it here: Toolbar => PMMail => View Program Log File

As an idea: could you use POP to handle your Outbound email tasks? I realize that POP is not meant for that, but PMMail 'Send' tab certainly shows POP as a viable choice here (at least on my 3.25 release).

Here is a decent review of all the protocol options => https://world.siteground.com/tutorials/email/protocols-pop3-smtp-imap/

42
Programming / Re: Qt6 Application Testing
« on: January 20, 2025, 05:03:20 pm »
Hello Remy,

Ok, read it.
I don't understand why when adding this switch, Dooble is more stable while it should have no effect but it has here !
(adding this switch, I'm able to use Dooble without setting priorities. Without it, I need to add priorities settings)
 
May it be possible this constant isn't well taken into some parts of the codes ?

Could it be that this SET statement impacts other apps on your system which in turn have an impact on the QT stuff?

I have a few apps here that would fit the bill:
1) FF - where I no longer have this set, while in earlier versions I did
2) PUMONITOR - by default I'm using the hires timer to gether runtime statistics
3) DISKIO - the version I am currently working on is using this approach

Now of course if you are running/testing the QT apps w/o anything else on your OS/2 box currently running, that would at least limit that spillover effect that other apps might have.

43
hi mauro,

ah, ok.  more exactly:
I'm in SM window browser, I browse the web, then if I want to start a new mail message I can do it (compose message window selected from FILE menu opens, I write the message and send it). But I cannot touch the item Mail & Messages from WINDOW menu, the one which opens the email folders pane, at that point OS2 traps.

OK, I understand now...so this is all within the SM application, which I do not have installed here.

When you mentioned that you installed FF I thought I could try to help/test with my FF & TB combo, unfortunately I do not think this is possible. Maybe I misunderstood one of the posts though..sorry about the noise.

44
mauro,

...Dariusz, not understood what you're asking me to do: having both FF and TB installed and then what action...?

OK, in your original post you stated:

...recently discovered that now the email client of Seamonkey -assuming same as Thunderbird-, cause a system trap when calling the "email client" window from Seamonkey (no problem if I start a new message compose)...

I interpret that to mean:

1) you are in web page (browsing) where there is an email link
2) you click on that link and expect that the email client window would pop up, thus allowing you to create an email
3) instead of this outcome you experience a trap/failure

Is that correct?

Subsequently in your post I was responding to you stated:

Quote
...I have installed Thunderbird 45.8 pentium4 to see what happens...

...and I was commenting on the fact that I have FF & TB here, which have been pretty solid for me, so I could certainly try to reproduce your scenario, and if I fail to, we could try to chase the DLLs down given that I am on CP2 release as opposed to AOS install.

45
Hello mauro,

...Just to point, I have installed Thunderbird 45.8 pentium4 to see what happens, it behaves exactly the same: it let mi begin to configure a profile plus the account, then at the moment to display the folders pane, the system goes away (trap).
Also in Seamonkey browser, it perfectly works till the request to go in the email folders pane.
No problem, I will survive without.

Can you provide a step-by-step instructions to replicate this?

Here is why I ask:

1) FF & TB installs here: they coexist very peacefully, and normally after a good 5 days of runtime I usually hard-kill FF because it grows to over 1G RAM consumption...re-starts brings it back and no issues

2) This last post of yours seems to indicate this issue can be replicated in my configuration as well (FF & TB), so I'd like to try this but w/o making any assumptions, thus the ask for 'step-by-step' instructions

I do have a 4.52 SMP install here, so the UNI vs SMP thing is certainly going to introduce a variable.

For what it's worth, here are the releases I'm running:

1) FF - 45.9.0
Code: [Select]
Compiler Version Compiler flags

gcc.exe 9.2.0 -Wall -Wempty-body -Wpointer-to-int-cast -Wsign-compare -Wtype-limits -Wno-unused -Wcast-align -Zomf -std=gnu99 -fgnu89-inline -fno-strict-aliasing -Zomf -fno-math-errno -pthread

c++ 9.2.0 -idirafter K:/usr/include/os2tk45 -Wall -Wempty-body -Woverloaded-virtual -Wsign-compare -Wwrite-strings -Wno-invalid-offsetof -Wcast-align -Zomf -fno-exceptions -fno-strict-aliasing -Zomf -flifetime-dse=1 -fno-delete-null-pointer-checks -Wclass-memaccess -fno-rtti -fno-exceptions -fno-math-errno -std=gnu++0x -pthread -DNDEBUG -DTRIMMED -g -march=pentium4 -mtune=generic -O2 -flifetime-dse=1 -fno-delete-null-pointer-checks -Wclass-memaccess -msse2 -fomit-frame-pointer

Configure arguments
--enable-application=browser '--enable-optimize=-march=pentium4 -mtune=generic -O2 -flifetime-dse=1 -fno-delete-null-pointer-checks -Wclass-memaccess -msse2' --disable-debug --enable-debug-symbols --disable-tests --enable-os2-high-mem --without-x --enable-official-branding --enable-system-cairo --enable-system-pixman --with-intl-api --with-system-icu --with-system-zlib --with-system-libvpx --prefix=/usr --disable-webrtc --disable-telemetry --disable-devtools --disable-crashreporter --disable-gamepad --disable-web-speech --disable-updater --disable-startupcache


2) TB - 45.8.0
Code: [Select]
Compiler Version Compiler flags

gcc.exe 9.2.0 -Wall -Wempty-body -Wpointer-to-int-cast -Wsign-compare -Wtype-limits -Wno-unused -Wcast-align -Zomf -std=gnu99 -fgnu89-inline -fno-strict-aliasing -Zomf -fno-math-errno -pthread

c++ 9.2.0 -idirafter K:/usr/include/os2tk45 -Wall -Wempty-body -Woverloaded-virtual -Wsign-compare -Wwrite-strings -Wno-invalid-offsetof -Wcast-align -Zomf -fno-exceptions -fno-strict-aliasing -Zomf -flifetime-dse=1 -fno-delete-null-pointer-checks -Wclass-memaccess -fno-rtti -fno-exceptions -fno-math-errno -std=gnu++0x -pthread -DNDEBUG -DTRIMMED -g -march=pentium4 -mtune=generic -O2 -flifetime-dse=1 -fno-delete-null-pointer-checks -Wclass-memaccess -msse2 -fomit-frame-pointer

Configure arguments

--enable-application=mail --prefix=/usr --libdir=/usr/lib --with-system-zlib --with-system-bz2 --enable-system-hunspell --disable-tests '--enable-optimize=-march=pentium4 -mtune=generic -O2 -flifetime-dse=1 -fno-delete-null-pointer-checks -Wclass-memaccess -msse2' --disable-mochitest --disable-installer --disable-updater --disable-debug --enable-debug-symbols --enable-system-cairo --enable-os2-high-mem --disable-crashreporter --enable-calendar --with-intl-api --with-system-icu --with-system-libvpx --with-system-png --disable-system-sqlite --with-system-jpeg --enable-release --enable-official-branding --prefix=/usr --disable-telemetry --disable-devtools --disable-crashreporter --disable-gamepad --disable-updater --disable-webrtc --enable-crypto --with-external-source-dir=Y:/work/cc45-git

Pages: 1 2 [3] 4 5 ... 96