Jump to content

infuscomus

Members
  • Posts

    102
  • Joined

  • Last visited

  • Days Won

    3

infuscomus last won the day on January 14

infuscomus had the most liked content!

Profile Information

  • OS
    non-selected

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

infuscomus's Achievements

  1. I have the exact same A5 BSOD problem on windows 8.0 - I made a thread here - is IDA absolutely necessary? I don't have it installed, can I use windbg? If IDA is necessary, can you help me setup windows 8.0 pre-install environment for debugging?
  2. @Mov AX, 0xDEAD Do you know of a way to properly fix AMLILoadDDB error?
  3. @Dietmar OK, I've resolved the missing exports for vista beta 5112 acpi.sys chk build. Can you please debug when you have time? https://ufile.io/giwcu5ic
  4. @ExtremeGrief I've noticed some differences between yours and mine, but so far no changes that I've made to my DSDT have gotten it working.
  5. @Mov AX, 0xDEAD Can you make an attempt to compile the reactos ACPI driver for XP using razzle?
  6. @simon73 Happy to hear you got it running, now you can find out which one is failing by enabling them one at a time. @ExtremeGrief Thanks.
  7. @ExtremeGrief Nope, I've shared mine so you can see for yourself what's in there.
  8. @simon73 The only way to find out for sure what the cause is would be to get out the debugger and start crawling through the code to trace the BSOD. Try disabling devices in device manager while in safe mode, disable anything unnecessary for boot like sound, COM ports etc...
  9. *!*ERROR Descriptor too short: PortPwrCtrlMask needs 2 bytes to hold 10 bits @Mov AX, 0xDEAD could this have something to do with my USB problem?
  10. @ExtremeGrief Can you send me a copy of your ACPI tables?
  11. @George King I'm going to give @skulltrail's acpi.sys a try and report back to you. The x86 version was buggy though and I doubt the x64 version will be any better. On the plus side, source code is available for it so fixing any bugs would be easier than hacking at it with assembly.
  12. Some further research - 148C controller - works in XP - is device \_SB.PCI0.D0B8.XHC0 in ACPI table if win10 is correct. 149C controller - does not work in XP - is device \_SB.S0D2.D2A0.BYUP.BYD8.XHC1 in ACPI table if win10 is correct. Now I just need to figure out what exactly in the table I need to change. ^device tree too long? I've attached my ACPI tables for anyone curious. TRX40_DESIGNARE_ACPI_TABLES.7z
  13. A disable and re-enable of Root Hub (xHCI) doesn't fix it, only doing that to the controller works.
  14. @Mov AX, 0xDEAD Thats the device ID I get for devices connected to the 149C controller. note that the host controller and root hub (xHCI) report no problems and say "This device is working properly." even though it's not.
×
×
  • Create New...