Contribute
Register

Battery randomly went from working to [ x ]-

Status
Not open for further replies.
Enigmahack

Enigmahack

Joined
Nov 25, 2017
Messages
61
Motherboard
Toshiba Tecra Z50-C
CPU
i7-6600U
Graphics
HD 520
Mobile Phone
  1. Android
  2. iOS
  3. Other
So I've been working with RehabMan, he's been helping me get this thing up and running properly. Things have been working well minus a bluetooth issue, but there's a workaround.

Anyway, so I've been using the laptop but haven't made any changes to the DSDT and SSDT's once they were 'done'. Randomly, one reboot, the battery stopped responding and shows the battery at 100% but with the x through it. Oddly enough, another minor issue I noticed was that when I adjust the mouse sensitivity, it doesn't change. When I took out the SSDT's, the backlight brightness was broken again, but then the mouse speed worked properly. I don't really care about that as much.

I DID notice this which was new during verbose setup:
ACPI: Executed 23 blocks of module-level executable AML code
ACPI: sleep states S3 S4 S5
ACPI Error: Method parse/execution failed [\_SB_.VALZ._STA] (Mode ffffff002z329e10). AE_AML_INFINITE_LOOP (20140828/psparse-270)
ACPI Error: Method parse/execution failed [\_SB_.VALZ._STA] (Mode ffffff002z329e10). AE_AML_INFINITE_LOOP (20140828/psparse-270)
ACPI Error: Method execution failed [\_SB_.VALZ._STA] (Mode ffffff002z329e10). AE_AML_INFINITE_LOOP (20140828/uteval-b9)

The boot up is slightly slower now (I'm imaging it's because of what's above) but it's not substantial.

So, I thought I MUST have changed something... So I did a time machine restore to earlier today where things were working properly but it remains broken. The only thing I can think of is something's up with my SSDT's or DSDT since it exists outside of the file system (EFI, etc.)

Anyway. I'm lost. As far as I know, nothing at all has changed but obviously I've implemented something incorrectly somewhere despite it working and then not working suddenly.

Anyone with insight - I would appreciate the help.
 

Attachments

  • debug_2794.zip
    1.5 MB · Views: 64
I ended up actually fixing this one - I had made a change to the bios that I didn't think would in any way be impacting (Had to do with MEBx) but... it turns out it was entirely impacting. My DSDT was messed up due to the changes. I knew I'd have to re-do the DSDT if I made any major changes in the BIOS, but I didn't know that even making a change and then CHANGING IT BACK can still lead to problems. I only got things back after deleting my DSDT.aml

I had an old copy of the native / non patched DSDT and even that was causing the battery error. Only after I re-read the patching guide here:

https://www.tonymacx86.com/threads/guide-patching-laptop-dsdt-ssdts.152573/

RehabMan mentioned in the both the 3rd and 4th paragraphs that *ANY* changes to the hardware/BIOS configuration requires a new DSDT.

I still have my SSDT's in place except for the Fake EC SSDT which had a very odd behavior of breaking the Tracking slider speed for mouse movement. (Sliding ended up doing nothing and kept the mouse always at default no matter the slider position) I ended up taking it out.

As for the patches in the DSDT - I ended up hotpatching what I needed instead of DSDT editing. Knowing how much I experiment, having to re-extract and re-compile patches every time would be a huge waste of time.

So let this be a lesson to you all. Read things CAREFULLY and make notes if you must. There seems to be so much essential information in these guides... Missing a single point can drastically change your outcome. In this case, I didn't know making a change and then changing things back could still have an adverse effect.

Sidenote, the Fake EC code I used is here:

Code: 
// Inject Fake EC device

//DefinitionBlock("", "SSDT", 2, "hack", "EC", 0)
//{
    Device(_SB.EC)
    {
        Name(_HID, "EC000000")
    }
//}
//EOF

Does anyone know why this would cause issues with RehabMan's PS2 Voodoo driver? (Or at least the tracking speed implementation under Settings > Mouse?)
 
Enigmahack said:
...
Sidenote, the Fake EC code I used is here:

Code: 
// Inject Fake EC device

//DefinitionBlock("", "SSDT", 2, "hack", "EC", 0)
//{
    Device(_SB.EC)
    {
        Name(_HID, "EC000000")
    }
//}
//EOF

Does anyone know why this would cause issues with RehabMan's PS2 Voodoo driver? (Or at least the tracking speed implementation under Settings > Mouse?)
Click to expand...

No "Problem Reporting" files attached.
Read FAQ, "Problem Reporting" again. Carefully. Attach all requested files/output.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/
Use the gen_debug.sh tool mentioned in the FAQ, that way it is less likely you'll omit something.
 
RehabMan said:
No "Problem Reporting" files attached.
Read FAQ, "Problem Reporting" again. Carefully. Attach all requested files/output.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/
Use the gen_debug.sh tool mentioned in the FAQ, that way it is less likely you'll omit something.
Click to expand...

Problem Reporting files attached related to the SSDT-EC.aml

Note - the only obvious indication that anything is wrong is the mousepad movement (using the PS2Voodoo drivers) becomes default and no manipulation within the System Preferences -> Mouse -> Tracking Speed makes any difference (even after making a change and rebooting)

Please let me know if you require anything else.
 

Attachments

  • debug_304.zip
    1.7 MB · Views: 55
Enigmahack said:
Problem Reporting files attached related to the SSDT-EC.aml

Note - the only obvious indication that anything is wrong is the mousepad movement (using the PS2Voodoo drivers) becomes default and no manipulation within the System Preferences -> Mouse -> Tracking Speed makes any difference (even after making a change and rebooting)

Please let me know if you require anything else.
Click to expand...

I don't see any difference here regarding SSDT-EC.aml or PS2 when I compare these files to the ones you attached in post #1.

If you have some "change" that makes a particular "difference", perhaps you should attach problem reporting files for both such that the difference and effect can be seen clearly and in isolation.
 
RehabMan said:
I don't see any difference here regarding SSDT-EC.aml or PS2 when I compare these files to the ones you attached in post #1.

If you have some "change" that makes a particular "difference", perhaps you should attach problem reporting files for both such that the difference and effect can be seen clearly and in isolation.
Click to expand...
Agreed.

I'll take the problem reporting files in both instances (working and not working) and include them for further investigation.
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top