OS/2, eCS & ArcaOS - Technical > Setup & Installation
Dreaded Desktop/blue screen SMP hang....
Dariusz Piatkowski:
OK...so I've got my MSI motherboard / AMD Phenom XII 6-core based system. It chugs along plenty nice with the exception of 1 (one) thing...I can not for the life of me get the 6-core configuration to get past the dreaded Desktop/blue screen hang. 5-core though...no problemo!!!
Neither the IBM origial OS2APIC.PSD driver nor the ACPI ACPI.PSD drivers impact this...something in the WPS boot process does.
Who else here uses multi-core configuration? And if so, what have you been able to do about this hang?
I spent a few hours today trying to narrow this down further...based on some on-line search hits I disabled the system wide sound and moved WarpCenter to the Startup folder (SET AUTOSTART=TASKLIST,FOLDERS). This actually got me to a point where the WPS did come up, WarpCenter started but whole machine froze (soft-hang) when about 1/3 of the WarpCenter toolbar displayed.
I'll try a few more combinations...as in previous search hits the suggestions always point to some kind of a "WPS boot timing" issue...OK...but what issue is that???
Any pointer would be greatly appreciated!
(BTW: ATI XT850 video, SNAP v505 driver)
Sigurd Fastenrath:
The Problem you have is the SNAP Driver. Please read here for more Information:
https://translate.google.de/translate?sl=de&tl=en&js=y&prev=_t&hl=de&ie=UTF-8&u=http%3A%2F%2Fwww.os2.org%2Fviewtopic.php%3Ff%3D2%26t%3D11&edit-text=
You can use all kernel with the Panorama Driver but your Video Performance will drop.
Holger from Germany tries to adress the SNAP / SMP Problem.
guzzi:
It might be interesting to try if by using QSINIT it will work better. Since it sets the MTRR's correctly it might solve some SNAP problems.
OS4User:
--- Quote from: Dariusz Piatkowski on November 23, 2014, 12:12:21 am ---(BTW: ATI XT850 video, SNAP v505 driver)
--- End quote ---
I have the same set - it works excellent for me.
If you meet SMP SNAP issue, you may try os/4 + new sddhelp.sys - it will definitely help you - otherwise it is not a SMP issue.
http://gus.biysk.ru/os4/ http://gus.biysk.ru/os4/test/sddhelp/
Doug Bissett:
This is not a Snap problem, and it is not even an SMP problem. It is not fixable by QSINIT, or OS4. It is a startup conflict that happens just as the WPS starts up. It is more likely to happen when you have many things trying to start, all at the same time (all of the CALL and RUN statements in CONFIG.SYS, plus STARTUP.CMD, plus the startup sound, plus whatever is in your STARTUP folder. The more things that you have starting, the more likely you are to have the problem).
On my quad core machine, it seems that the problem lies in the early part of starting the WPS. Most of the time, the sound plays, and STARTUP.CMD shows the window, with no controls, and that is the end. Reboot usually succeeds. It seems that there is a "window of opportunity" where something goes wrong. If you can make the "window" happen when it doesn't matter, you have bypassed the problem. If it gets moved to a time when something else is affected, you have a problem.
Some supporting observations:
I made a VBox install of eCS 2.1. After the install, I was having the blue screen hang, about 4 out of 5 boots. I used the VBox controls to limit the machine to about 60% processor usage. I tried booting 20 times, with no hang. I put it back to 100%, and it was failing 4 out of 5 tries. Okay, so I finished my install, and setup, at 60% processor usage. This included adding a number of things that put entries into CONFIG.SYS. After all of that, I put it back to 100%, and had no more trouble. The additional entries in CONFIG.SYS slowed down the boot enough to get whatever was causing the problem to cause the problem at a time when it doesn't matter. Doing that with a real machine is a little harder. :(
Some things to try (any of these can cause, or bypass, the problem):
Put a file named AltF2on.$$$ in the root of the boot drive (this effectively does Alt-F2 without user intervention). Displaying the information slows the boot process a little, and sometimes it will change it enough to let it get past the problem (or, it can cause the problem if you don't have it).
Use http://www.tavi.co.uk/os2pages/utils/delay.zip to insert a one, or two, second delay at the beginning of your CONFIG.SYS, and/or at the end. That should allow all BASEDEV and DEVICE statements to complete, before proceeding to the next step.
Use REXX Autostart http://hobbes.nmsu.edu/download/pub/os2/util/wps/rxast1911.exe to delay starting the contents of the STARTUP folder. Unfortunately, on my system, this never gets started when I have the problem, so I assume that the problem lies in the CALL and RUN statements (but it is not caused by those).
I also use my Logical Config.Sys Sorter (LCSS) http://hobbes.nmsu.edu/download/pub/os2/util/config/lcss-0-4-8.wpi which seems to help (at least on all of my systems). READ the instructions.
Of course, there may be other things that can case the problem, and there may be other things that can move the "window" far enough to prevent it. Good luck...
Navigation
[0] Message Index
[#] Next page
Go to full version