Support Katana GF66 12UG (EC ver 1583EMS1) #259
Comments
|
Hey! So it looks like the Katana model has a different battery threshold address. I don't know about the other addresses (since this was the only one I was interested about). I can tell you that cooler boost, for instance, work out of the box. Other things might work as well, who knows. That said, for the battery address, change the Once you've done this and saved the file, you can simply do |
|
Hi! Thank you for this info! It is actually the main thing I needed. Meanwhile I found other addresses and values to share: As you said those controls works out of the box so it was really simple to find them. Here my 1287,1288c1287,1288
< cooler_boost_off = 0
< cooler_boost_on = 128
---
> cooler_boost_off = 6
> cooler_boost_on = 134
1293,1294c1293,1294
< usb_backlight_half = 193
< usb_backlight_full = 129
---
> usb_backlight_half = 129
> usb_backlight_full = 131
1300,1301c1300,1301
< usb_backlight_address = 0xf7
< battery_charging_threshold_address = 0xef
---
> usb_backlight_address = 0xd3
> battery_charging_threshold_address = 0xd7at this point just Note: the |
|
That looks nice. Can I ask you to share how you're proceeding about this? I mean, how are you finding addresses and so on. |
I totally agree with this since it took me a while to get into the process of doing this. To my understanding there are three ways you can do this:
The first method is trivial and really simple. The second and third methods are comparable but, even if it is much more painful and time consuming switching between OSes, I prefer the second because I couldn't find the source code of the suggested software anywhere and I'm not comfortable running such invasive tools without the possibility to look at the code. Probably the third way should be "the way to go" but only if someone finds, or knows, a Windows alternative to editI forgot to mention that there might be EC values that wont survive on boot which could leave you only with method 3. editStriked out RWEverything to avoid people blindly follow the link. |
|
I have good updates: I found the tool I was looking for ec-probe. It will allow you to dump the EC while changing parameters in MSI Center and it is open-source. Using CameraAddress: 2E MicrophoneAddress: 2C Screen Off (the one controlled with Fn+RightArrow on this model)Address: D9 Speakers Volume ToggleAddress: 2D Super Key Toggle (Windows key disabler)Seems controlled by software because there are no apparent changes in the dumped EC while switching it on/off. Switch Fn key with Super keyAddress: E8 Switch Fn mode (the one controlled by Fn+ESC on this model)Address: D9 USB Power Share (allows to power USB devices while computer is off and not plugged to the wall)Address: BF Fan mode / User scenarioUnfortunately I'm still confused about this but I took some notes:
Last three columns are the addresses that are changing while switching "User scenarios" in MSI Center. It appears that D2 is somehow related with the performances (C4 = performance, C1 = Balanced, C2 = Power save maybe) and D4 with the fan mode (4D = advanced, 0D = auto, 1D = off or something like that). Still no idea what EB does but I would bet that it is controlling some other feature (maybe disabling it) to save battery. Final notesSince in D4 the difference between 4D and 0D is exactly 64 (decimal) just like 64 was the difference between the fan modes as shown by this if statements I feel pretty confident about being D4 the Fan mode controller indeed. |
|
This is amazing! Thank you so much for this comment. I think this allows us (and other people) to actually effectively develop windows-like functionality for all models in (kind of) a safe way. If you need any help or want to contact me, I'm sending you an email address with my contacts. Good job! |
|
So, I have explored a bit with the tool you provided. So, I noticed that the (almost) whole row 90 changed between extreme and silent (basically from |
|
I did more testing: I leave here two recordings annotated with what I was changing; this is the result of calling
(time advances to the right)
As you can se there are no other changes that can be directly related with changing User Scenario. In the row you cited (9X) I see only the aforementioned 91 plus 9E changing with the latter changing no matter if I was changing User Scenario or not. That seems to be what I would call an output address since the value is changing one unit at a time. It appears to be the measurement of something, maybe. Here it is the updated table
do not forget that all values in this table are in hex (64 is 100 decimal and 53 is 83). |
|
A small update with what I tested today under GNU/Linux:
I will try to keep this table up-to-date. For now I'm leaving the Fan Mode out of this table since there are still too many ifs. updateSwitch Fn mode is not working for me when set using updateUSB Power Share is working perfectly when set using |
|
Great job really! super useful. I'll test some stuff as well as soon as I have time |
|
Guess what: the in They probably figured that it was a good idea to respect the order used before in the schema (CPU before GPU). |
|
No big surprise there, I honestly figured that basically everything changed here. One question though: how did you figure this out this time? Thanks again for your work btw :) |
Just turning on/off the cooler_boost to make the RPMs goes up and down and of course I was expecting them not to be so different from the GPU on (which I knew was working as shown by NoteActually they could have been just C9 and CD (for CPU and GPU respectively) I just assumed that the original schema was right assigning "two addresses" to the RPM addresses since the max values I registered on my laptop were 004D for the CPU and 0051 for the GPU. Those 00 could be just padding, right? I guess it doesn't really matter as long as the software which is reading the value is considering this. |
|
Hi, I have some good updates but since keeping track of all discoveries was getting harder and harder and because I wanted to check if there was some kind of pattern in the design of the EC (for instance something like a "CPU area" and a "battery area") I started drawing a schema inspired by this, I'm just posting here a PNG export of my spreadsheet. Most noticeable discovery are plugged status, charging status and battery charge. Note: the text in italic and wrapped inside square brackets means that the feature was either not tested or never actually seen on my computer but can be assumed since is a "well known behavior" for that particular feature (see some value for the Shift Mode for instance).
You probably have to open it in another tab to see it clearly. PS: I noticed that there are some similarities with this by BeardOverflow; just adding this as reference since I used it to understand what was going on with 0xD2 (Shift Mode) and 0xD4 (Fan Mode) addresses. editJust noticed that there is a typo in Shift Mode for value Turbo: 0xC4 is 196 in decimal (not 195). Suggestion: do not apply any of the provided values before trying to question it. Please, do not assume blindly that everything I write is perfectly correct. |
|
Amazing job as usual! I'm super busy these months so I don't really have time to check on all the stuff you posted...but sooner or later I'll try it out! |
Add support Katana GF66 12UG (EC ver 1583EMS1).
Result of command
isw -cp MSI_ADDRESS_DEFAULT:Once this is working on my system I plan on starting the development of an
AppIndicatorto controlisw(see: OpenFreezeCenter by YoCodingmonster as reference for what I have in mind).Additional notes
I think EC updates for this laptop are released within the BIOS updates (but I may be mistaken) so I leave a list of the laptop models with share the same BIOS as listed in the MSI BIOS Release Notes contained in the BIOS update zip file.
MKT Name:
The text was updated successfully, but these errors were encountered: