Contribute
Register

Lenovo Yoga 910-13IKB

Status
Not open for further replies.
Hi Josiah,
It's interesting: I have quite mixed results here.
For starters, I've set it so that the F-keys work as hotkeys.
Then, proceeding from left to right on the keyboard, here is what happens.
  • Fn + Esc triggers Paper Display and changes the icon in the Lenovo Settings app.
  • F1, F2, F3 (without pressing Fn) changes the audio output and brings up the Windows audio bar, but there is no change in Lenovo Settings icons.
  • F4 does nothing. Fn + F4 does nothing. No changes to the system or the microphone icon in Lenovo Settings.
  • F5 does nothing. Fn + F5 does nothing. No changes at all.
  • F6 turns the trackpad on and off, and it changes the icon in Lenovo Settings.
  • F7 does nothing. Fn + F7 does nothing. No changes to the system or the airplane icon in Lenovo Settings.
  • F8 does nothing. Fn + F8 does nothing. No changes to the system or the camera icon in Lenovo Settings.
  • F9 locks the screen, and in my case requires sign in. No change in Lenovo Settings.
  • F10 brings up the Windows projector/display bar.
  • F11 and F12 change the brightness, but this has no effect in Lenovo Settings icons.
  • Fn + Spacebar changes the keyboard backlight and this also changes the icon in Lenovo Settings.
Hope this helps!
 
Hi Josiah,
It's interesting: I have quite mixed results here.
For starters, I've set it so that the F-keys work as hotkeys.
Then, proceeding from left to right on the keyboard, here is what happens.
  • Fn + Esc triggers Paper Display and changes the icon in the Lenovo Settings app.
  • F1, F2, F3 (without pressing Fn) changes the audio output and brings up the Windows audio bar, but there is no change in Lenovo Settings icons.
  • F4 does nothing. Fn + F4 does nothing. No changes to the system or the microphone icon in Lenovo Settings.
  • F5 does nothing. Fn + F5 does nothing. No changes at all.
  • F6 turns the trackpad on and off, and it changes the icon in Lenovo Settings.
  • F7 does nothing. Fn + F7 does nothing. No changes to the system or the airplane icon in Lenovo Settings.
  • F8 does nothing. Fn + F8 does nothing. No changes to the system or the camera icon in Lenovo Settings.
  • F9 locks the screen, and in my case requires sign in. No change in Lenovo Settings.
  • F10 brings up the Windows projector/display bar.
  • F11 and F12 change the brightness, but this has no effect in Lenovo Settings icons.
  • Fn + Spacebar changes the keyboard backlight and this also changes the icon in Lenovo Settings.
Hope this helps!

Thanks a lot!!!! I thought that my machine might have been defective. You probably just saved me a whole lot of headache!
 
I'm back, since DSDT battery patching was frying my brain. I started over and got to here. I'm a little stuck trying to understand some errors on the compiler
 

Attachments

  • DSDT.dsl
    1.3 MB · Views: 167
I'm back, since DSDT battery patching was frying my brain. I started over and got to here. I'm a little stuck trying to understand some errors on the compiler

You did not provide original DSDT.
You did not provide the set of patches you're applying.
The compiler is telling you that the code you have written is invalid... For example:
17628, 6084, Object does not exist (ATM0)
Tells you that this line:
Code:
                        Store (B1B2(ATM0,ATM1), Index (RETB, 0x0E))
The ATM0 symbol does not exist.
 
You did not provide original DSDT.
Didn't know I had to attach original dsdt (original attached)
You did not provide the set of patches you're applying.

Patching for battery still



The compiler is telling you that the code you have written is invalid... For example:
17628, 6084, Object does not exist (ATM0)
Tells you that this line:
Code:
                        Store (B1B2(ATM0,ATM1), Index (RETB, 0x0E))
The ATM0 symbol does not exist.

Can I just delete the line then?
 

Attachments

  • DSDT.dsl
    1.3 MB · Views: 233
Didn't know I had to attach original dsdt (original attached)

The DSDT.dsl is not native. It is patched.
Native ACPI files are extracted by pressing F4 in Clover. You will find them in EFI/Clover/ACPI/origin on your EFI partition.

Patching for battery still

Battery patching guide has you construct a set of patches to automate the patching process.
You did not attach the patches...

Can I just delete the line then?

No.
 
The DSDT.dsl is not native. It is patched.
Native ACPI files are extracted by pressing F4 in Clover. You will find them in EFI/Clover/ACPI/origin on your EFI partition.



Battery patching guide has you construct a set of patches to automate the patching process.
You did not attach the patches...



No.
I'm trying to learn, but with me, I have to see a before and after to really "understand" how to do something. Could you write a patch for my dsdt, that way I can compare the two DSDT's (battery patched and battery unpatched) to see how I would go about deeply patching, comparing the two as I go, because this is way too confusing just following the guide o_O:crazy::(
 

Attachments

  • DSDT.aml
    170.6 KB · Views: 206
I'm trying to learn, but with me, I have to see a before and after to really "understand" how to do something. Could you write a patch for my dsdt, that way I can compare the two DSDT's (battery patched and battery unpatched) to see how I would go about deeply patching, comparing the two as I go, because this is way too confusing just following the guide o_O:crazy::(

The battery patching guide goes through an example...

Do not remove BNUM from the EC region (remove the External(BNUM, ...) line that is causing your error).

First error in your patched DSDT refers to this line:
Code:
 Store (B1B2(ATM0,ATM1), Index (RETB, 0x0E))

Original code there:
Code:
  Store (B1TM, Index (RETB, 0x0E))

The B1TM field was broken into ZTM0 and ZTM1:
Code:
 ZTM0,8,ZTM1,8,

Yet in the code you wrote ATM0/ATM1...
 
Last edited:
I think I fixed the errors. I used the command line iASL in windows and used notepad++ to fix the errors.
 

Attachments

  • DSDT.dsl
    1.3 MB · Views: 188
I think I fixed the errors. I used the command line iASL in windows and used notepad++ to fix the errors.

That's fine, but easier to use MaciASL...
 
Status
Not open for further replies.
Back
Top