Changes between Version 22 and Version 23 of KnownProblems
- Timestamp:
- Apr 18, 2012, 7:10:54 AM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
KnownProblems
v22 v23 1 = Known Problems =1 = Known Problems = 2 2 3 These are the known problems that may affect many users. Problems which only affect 1 or 2 unique systems are not listed here. Since these are already known problems, you do not need to open a ticket or report any of the problems listed on this page. 3 With the current version (3.20.01) the PSD and related software works well and reliably on almost all systems. Some systems from certain vendors may still have problems, and a few unique and unusual systems may have issues, but for most users, the PSD and related software will work reliably without any tweaking, and without experimenting with different switches. 4 5 This page lists the known problems that may affect many users. Problems which only affect 1 or 2 unique systems are not listed here. Since these are already known problems, you do not need to open a ticket or report any of the problems listed on this page. 4 6 5 7 == Problematic Vendors == … … 10 12 Suspend / Resume only works on a very small number of systems. If Suspend / Resume works for you, consider yourself among the few lucky ones. If it does not work for you, please wait for more progress to be made and try a later version. Please do not report problems with Suspend / Resume at this time. 11 13 14 == Slow booting from a JFS boot disk == 15 16 Starting with version 3.20.01, a significant defect was fixed that affects many things including the way the system operates during the early part of the boot process. A peculiarity in the way the JFS boot loader works makes booting from JFS disks much slower. We are investigating a way to correct this problem. If you have a JFS boot disk and experience this slowness, you can use the /VW switch as a workaround until a fix is found for booting from JFS disks. Booting from HPFS disks is not significantly affected. Other ways to speed up the boot process are: 17 * Make sure you are using the retail version of the PSD. 18 * Do not use the ALT-F2 function or the ALT-F4 function. 19 * Don't load basedevs that you don't need. (Possible examples: PRINT01.SYS, IBM1FLPY.SYS, APM.ADD) 20 12 21 == Spurious interrupts with certain motherboards which use an NVIDIA chipset == 13 22 14 23 Some motherboards which use an NVIDIA chipset will generate spurious interrupts in Mode 1 (/VW mode), usually when the desktop starts. These interrupts occur in an unusual, unpredictable way and cause problems for both the kernel and the PSD. There currently is no solution to this problem. You cannot use the /VW switch on these motherboards until a fix for this problem is found. 24 25 == SCSI drivers == 26 27 While this is not an ACPI.PSD problem, I am listing it here because the PSD can reconfigure the system in a way that the drivers don't like. 28 29 It appears that most SCSI drivers have one or both of 2 problems. 30 1. Some SCSI drivers cannot handle interrupt numbers greater than 15. 31 2. Some SCSI drivers cannot handle the interrupt being changed from what the BIOS has set it to, regardless of whether or not it is greater than 15. 32 Both of these problems can be handled by using the /VW switch. 33 34 = Previous Problems That Have Been Fixed = 15 35 16 36 == Power Off == … … 55 75 The iasl -g command also writes a few files to the current directory which are unneeded and you can delete them. 56 76 57 == Slow booting from a JFS boot disk ==58 59 Starting with version 3.20.01, a significant defect was fixed that affects the way the system operates during the early part of the boot process. A peculiarity in the way the JFS boot loader works makes booting from JFS disks much slower. We are investigating a way to correct this problem. If you have a JFS boot disk and experience this slowness, you can use the /VW switch as a workaround until a fix is found for booting from JFS disks. Booting from HPFS disks is not significantly affected. Other ways to speed up the boot process are:60 * Make sure you are using the retail version of the PSD.61 * Do not use the ALT-F2 function.62 * Don't load basedevs that you don't need. (Possible examples: PRINT01.SYS, IBM1FLPY.SYS, APM.ADD)63 64 77 == Immediate suspend due to misbehaving SLPB device == 65 78 … … 67 80 68 81 NOTE: In version 3.19.16 and later, a workaround was implemented to ignore SLPB events if one occurs within 10 seconds of starting !AcpiDaemon.exe. The SLPB events are still generated by the hardware every 2 seconds, but they are simply ignored. If !AcpiDaemon logging is enabled, the log file could grow very large logging these events. An actual fix is still being investigated. 69 70 == SCSI drivers ==71 72 While this is not an ACPI.PSD problem, I am listing it here because the PSD can reconfigure the system in a way that the drivers don't like.73 74 It appears that most SCSI drivers have one or both of 2 problems.75 1. Some SCSI drivers cannot handle interrupt numbers greater than 15.76 2. Some SCSI drivers cannot handle the interrupt being changed from what the BIOS has set it to, regardless of whether or not it is greater than 15.77 Both of these problems can be handled by using the /VW switch.
