Changes between Initial Version and Version 1 of Ticket #2, comment 76


Ignore:
Timestamp:
Jan 9, 2012, 5:28:34 PM (13 years ago)
Author:
Lars Erdmann

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #2, comment 76

    initial v1  
    11Please retry (forget about disassembling your PC).
    22
    3 0.) please let me know how much RAM your system has. I'd expect it to have at least 4 GB.
     30.) please let me know how much RAM your system has. I'd expect it to have at least 4 GB.[[BR]]
    441.) send trace in any case (if fixed or not)[[BR]]
    552.) reget device report from USB dock for the camera. It should now announce itself as a USB 2.0 device (with a non-functional USBEHCD it announces itself as a USB 1.1 device ...)[[BR]]
    6 3.) let me know if all your USB 2.0 devices now work ok
     63.) let me know if all your USB 2.0 devices now work ok[[BR]]
    774.) it should now work with/without ACPI.PSD regardless. The error was somewhere else, see below.
    88
    9 If it works: please let the ACPI developer know about it ! The error was so fundamental that about everything could have happened, in particular, the EHCI HC DMA engine could overwrite/corrupt memory in the system arena with whatever side effect that can have. You should retry to run ACPI.PSD without any parameters (unless you also had problems with USBEHCD.SYS 10.162).[[BR]]
     9If it works: The error was so fundamental that about everything could have happened, in particular, the EHCI HC DMA engine could overwrite/corrupt memory in the system arena with whatever side effect that can have. You should retry to run ACPI.PSD without any parameters (unless you also had problems with USBEHCD.SYS 10.162). If it now works, report back to the ACPI developer ![[BR]]
    1010Be aware that your EHCI HC HW has a severe bug and what I did was to work around it. The negative side effect is that more memory <= 16 MB physical address is now used. This could lead to the well known problem that if you have many device drivers loaded (where for historical reasons most of these dynamically allocate below the 16 MB phys. addr. boundary) that some device driver might refuse to load. The USBEHCD.SYS device driver is now behaving like 10.162 in that respect.