Custom Query (581 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (16 - 18 of 581)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Ticket Resolution Summary Owner Reporter
#195 fixed problem with suspend/resume, problem with reboot/estyler pasha Chuck McKinnis
Description

I have a computer with an ASUS M2N-E mobo, 5600+ AMD 64 Dual Core CPU.

Suspend does not happen automatically. When I induce it manually from the power icon, the system will not resume. Shutting down the system by turning off the power completely and then rebooting is the only way to get the system to resume. Using reset button or the power button on the case results in a reboot to suspend mode.

2. When the shutdown dialog box is set to enhanced reboot works only intermittantly. I cannot find a reason why sometimes it does not reboot, but once it stops that function it does not seem to pick it up again. The system does not freeze, the function simply stops working. Shutdown and Power Off both continue working.

I am including the files: acpica$ log, pci.log and acpidaemon.log

#503 Unrelated pmmail won't start eco Peter Verweij
Description

Hi,

Tested the special build of acpi, acpi319PollingFullOnly.zip for while on a test system, worked good. So decided to install it on the normal working system, problem is Pmmail 3.10 won't start. The icon gets the open status but that's all. Sometimes 100% cpu, sometimes the system just hangs. Changed the acpidaemon.exe to load in the startup.cmd (for using more than one time the suspend feature, mention on another ticket), made a stupid typo but then pmmail starts! As soon as acpidaemon is loaded pmmail won't start. Funny thinks:

  • on the test system the same pmmail starts, but the test build has alot less programms to run.
  • with the unofficial os2.ru kernel the normal working system works without a problem, even pmmail starts with acpidaemon.

Don't know if it helps if you have logs, let me know.

#408 worksforme nmake fails to report compiler errors when building on JFS volume Steven Levine Steven Levine
Description

Pasha reports that nmake sometimes fails to report compile errors when building on a jfs volume

A typical report looks like

Entering directory: .\src\acpi\intel Entering directory: .\src\acpi\psd

icc /O3 /Os- /Op- /Ms /Rn /C /Ss /Sp8 /W3 /Gi+ /Gf+ /Gs+ /Fa+ /G5 /qtune=pentium /qarch=pentium /DMJVER=3 /DMNVER=14 /DACPI_DEBUG /D_ACPI_DEBUG /DACPI_FULL_DEBUG /FoD:\work\ddk\base32\src\acpi\obj\acpi\psd\nonintel.obj /FaD:\work\ddk\base32\src\acpi\obj\acpi\psd\nonintel.lst nonintel.c

nonintel.c(39:1) : error EDC0046: Syntax error.

D:\work\ddk\base32\src\acpi\createpath.cmd D:\work\ddk\base32\src\acpi\bin\os2 ilink /nofree /map /nod /exepack @D:\work\ddk\base32\src\acpi\obj\acpi\psd\acpi.lnk

IBM(R) Linker for OS/2(R), Version 03.06.PPK1010917.011116ilink

To correct response would be to stop after the syntax error.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Note: See TracQuery for help on using queries.