Opened 17 years ago
Closed 17 years ago
#140 closed defect (fixed)
WIn-OS/2 and DOS sessions do not work with SMP in 2.0 RC1/RC2
Reported by: | Chuck McKinnis | Owned by: | pasha |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | ACPI PSD | Version: | 3.01 |
Keywords: | Cc: |
Description
I am unable to get Win-OS/2 and DOS windows (Full screen or windowed) to work on my K9N4 motherboard while running SMP. It worked until I added the /SMP switch.
When in SMP mode, the DOS/Win-OS/2 session thinks that it has completed. When not in SMP, DOS/Windows runs fine. Once I remove the /SMP I can run DOS.
Tell me what more you need, and I can provide it.
Attachments (3)
Change History (25)
follow-up: 2 comment:1 by , 17 years ago
Status: | new → assigned |
---|
by , 17 years ago
comment:2 by , 17 years ago
Replying to pasha:
Always I need in "copy acpica$ acpi.log". For you need in list of drivers, what you are add to WinOs2 session via "prooetries->WinOs2 setup->drivers"
I attached the zip file with both the /SMP (acica.mp.log) and the non-smp verion (acpica.1p.log). There are no drivers loaded for the DOS VDM and only l:\tcpip\bin\vdostcp.sys loaded. Neither VDM works.
follow-up: 4 comment:3 by , 17 years ago
Try boot with psd=acpi.psd /SMP
I see , you are use APIC mode. This can be the problem for WinOs2 session
follow-up: 6 comment:4 by , 17 years ago
Replying to pasha:
Try boot with psd=acpi.psd /SMP
I see , you are use APIC mode. This can be the problem for WinOs2 session
Maybe it's the DOS kernel itself that doesn't like high IRQs? In that case, maybe there could be some kind of IRQ mapping for VDMs? Or maybe an ACPI switch to disable high IRQs but still use APIC mode? I'm just throwing out ideas...
comment:5 by , 17 years ago
I have DOS and WinOs2 without drivers (tcpip too) - this work with /APIC. You can use REMAP directive from acpi.cfg for remap all your IRQ to low. But it is the process.
comment:6 by , 17 years ago
Replying to guest:
Replying to pasha:
Try boot with psd=acpi.psd /SMP
I see , you are use APIC mode. This can be the problem for WinOs2 session
I tried without the APIC, but it reboots (leaving the drive dirty).
Maybe it's the DOS kernel itself that doesn't like high IRQs? In that case, maybe there could be some kind of IRQ mapping for VDMs? Or maybe an ACPI switch to disable high IRQs but still use APIC mode? I'm just throwing out ideas...
follow-up: 8 comment:7 by , 17 years ago
Ok. you have nVidia like chipset. So now you can't boot in PIC mode. You can use acpi 2.22 before resolving this problem in 3.xx
comment:8 by , 17 years ago
Replying to pasha:
Ok. you have nVidia like chipset. So now you can't boot in PIC mode. You can use acpi 2.22 before resolving this problem in 3.xx
Which files will have to be installed (replaced) to go back to 2.22. What can be affected by this? What things need to be watched out for? I can go use 3.04, but 1P, not SMP mode. Will 2.22 will work with rc3?
comment:9 by , 17 years ago
follow-up: 15 comment:10 by , 17 years ago
Changing back to 2.22 fixes that problem with VDMs. Now all the IRQs are below 16.
comment:11 by , 17 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
OK, we add this fact to the Restrictions section:
- VDM *may not* work if running in SMP APIC mode. Use PIC mode.
comment:12 by , 17 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Lets not, but fix it. Or at least give some instructions to remap to low IRQs. I have not seen any instructions to do so.
My machine does not seem to work in PIC mode.
follow-up: 14 comment:13 by , 17 years ago
I wonder if this may also be related to the DOS kernel level? The installed level is 14.097. 14.103 is available from www.ecomstation.com.
Chuck McKinnis mckinnis@…
comment:14 by , 17 years ago
Replying to guest:
I wonder if this may also be related to the DOS kernel level? The installed level is 14.097. 14.103 is available from www.ecomstation.com.
Don't think so. I have DOSKRNL v14.103 and I have the same problem, which is new since ACPI 3.x enabled high IRQs on my nVidia board.
-Mike Forester
comment:15 by , 17 years ago
Replying to guest:
Changing back to 2.22 fixes that problem with VDMs. Now all the IRQs are below 16.
I just noticed that drive speed is much slower since I went to 2.22.
comment:19 by , 17 years ago
Replying to pasha:
3.5 available in betazone
I tried 3.5 with and w/o !NOD and my system hangs when starting the graphic desktop display. Just before the graphics display inits, I see the character T in the top left corner of the screen.
comment:20 by , 17 years ago
Add to AcpiD.cfg
then set first line in config.sys, run=c:\os2\AcpiDaemon.exe, try boot and attach here Acpica.log
comment:21 by , 17 years ago
I attached both my trap screen picture along with the log file requested. With 3.5, I also had a hang at the graphics screen (it cleared to a backround, then hang).
comment:22 by , 17 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
Did you tried ACPI 3.7? It contains fixes for you problem.
Always I need in "copy acpica$ acpi.log". For you need in list of drivers, what you are add to WinOs2 session via "prooetries->WinOs2 setup->drivers"