Please support MSI Modern 15 F13MG017

[deKees687]

Laptop model

MSI Modern 15 F13MG017

EC firmware version

No response

EC memory dump

No response

GPU

iGPU only (Intel)

Is your keyboard RGB?

No (single color)

Additional context

I am looking for battery charge limits, in order to keep my battery alive for more that a few years.

[deKees687]

I tried to get firmware version end memory dump:
fw-version : empty

EC-Dump :
| 0 1 2 3 4 5 6 7 8 9 a b c d e f
-----+------------------------------------------------
0x0 | 02 e4 00 00 0b 00 00 00 00 00 01 00 00 00 00 00
0x1 | 10 00 24 1e 2e 00 00 00 00 00 00 00 80 40 01 00
0x2 | 20 30 38 32 39 32 30 32 34 31 36 33 32 31 35 00
0x3 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x4 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x5 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x6 | 00 80 16 20 47 46 4c 00 00 00 00 00 00 00 00 00
0x7 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x8 | 00 00 00 00 03 00 00 00 00 00 00 00 00 00 00 00
0x9 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xa | 00 00 00 e8 41 00 00 36 00 00 00 08 00 1a 00 78
0xb | 35 35 00 00 00 00 00 00 00 00 08 03 00 2a 00 00
0xc | 02 00 e1 0f 1e 00 86 33 1e 2d 6e 0f e8 0f 64 1c
0xd | 00 00 00 00 00 00 ec 0f 90 01 5b 11 00 00 00 00
0xe | 00 00 00 2f 11 2f 11 27 11 00 00 02 00 00 00 00
0xf | 00 00 00 00 00 00 00 00 03 10 00 ff ff 00 00 00

[glpnk]

You need to write charge limit value to 0xd7

[deKees687]

Thank you for the quick response. Highly appreciated. It took me a while to figure out how to do that. This is all new to me. Currently, this location has value 0x0F. Which value should I write for a 60 % charge limit? Kind regard, Kees Op di 7 jan 2025 om 16:00 schreef Ilya ***@***.***>:

…

You need to write charge limit value to 0xd7 — Reply to this email directly, view it on GitHub <#186 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A67ZAS7YDO7U73ESGQ3YCWL2JPTYTAVCNFSM6AAAAABUXY4BP6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZVGUYTGMZXGA> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>

[deKees687]

I am afraid that this driver does not work on my laptop, as it fails to report its fw-version.

And I just received conformation from MSI service that battery management is not supported:
"Sorry for not expressing clearly, for 13S1,14S1,15S1 these three series of models in MSI center S there is no battery management master function"

Apparently, this laptop is a "15S1", I checked the Bios where it reports "Model : MS-15S1".

[glpnk]

Sorry for not expressing clearly, for 13S1,14S1,15S1 these three series of models in MSI center S there is no battery management master function

Wow, I'm surprised to hear this about current gen laptop. Also, I'm surprised that Intel made new branding for Core CPUs, because your model have 2 type of CPUs - new and old (your one).

About fw-version - I'll not be surprised so much, because MSI launched another app, specially made for laptop series like one you have. This is like 5th MSI Dragon/Center app they have.

@deKees687 Pls reopen issue, because you closed it somehow

[glpnk]

@teackot We probably have another new EC design...

Please note that the BIOS for the Modern 13/14/15 F1MG used a shared version, so the file name displayed in the compressed package is uniformly named E14S1IMS_1xx.

Interesting note

[glpnk]

@deKees687 Do you have Windows on your machine? Can you try to dump EC with RW Everything, like mentioned in our guide device_support_guide.md#windows Screenshot or save file should be enough

[deKees687]

No windows. I am running Debian 12 on this laptop. works great most of the time.

I do have windows on a separate drive, as it came with the machine. And I can switch to windows, but when I do, Linux does not boot anymore. The only way I found sofar to get Debian working again is a full re-installation. That takes me about 4 hours of work.

Would the windows dump be much different from the linux dump that I gave above?

[deKees687]

I see now that there is a Bios update available, as indicated by glpnk above. According to its release notes not worth the effort to update though:

1. Add WOL (Wake on LAN) support.
2. Modify Charging LED behavior.

[glpnk]

Would the windows dump be much different from the linux dump that I gave above?

Good question, if your device is really have new generation software, I doubt that we will help you now.

Linux does not boot anymore

Windows modify boot records, maybe bios reset might help, or manual switching of boot sources. Also, you can copy your bootloader main file to the default windows bootloader location. If you want to do this, answer on these questions:

• what you use Grub2 or SystemdBoot as bootloader? Probably Grub2 if you on default Debian setup
• do you know how to edit/move files on boot partition? And maybe to use Midnight Commander?

[deKees687]

Yes. I use grub to get started. Don't know which version though.

Can I edit the boot partition from Grub? I am not familiar with these tools. It is all a bit scary for me.

I do have CloneZilla on an USB stick. Used that to backup Linux before switching to windows, and restore Linux afterwards. CloneZilla comes with a command prompt so that might do the job.

[glpnk]

You just need to copy 1 file and laptop will think that boots Windows, when it really loads Linux

[glpnk]

Ah, your grub probably saves bootloader to own path, instead of common \EFI\boot\Bootx64.efi

[glpnk]

MSI's BIOS/UEFI prefers Windows default path EFI\Microsoft\Boot\bootmgfw.efi and fallbacks to \EFI\boot\Bootx64.efi

Your grub configured to save it execution file to \EFI\ubuntu\grubx64.efi or \EFI\debian\grubx64.efi

[glpnk]

Assuming your EFI partition is mounted to /boot/efi you need to execute next commands
sudo cp /boot/efi/EFI/debian/grubx64.efi /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi
sudo cp /boot/efi/EFI/debian/grubx64.efi /boot/efi/EFI/Boot/bootx64.efi

But before doing this, please send mount output and sudo tree /boot

[deKees687]

Thanks for the support.

But I doubt this is the case here. I have windows and Debian on separate ssd's, and I switch ssd when switching OS. So no way that windows can affect the linux boot drive.

[glpnk]

When you have Linux, BIOS starts Grub from certain location, previously set with efibootmgr. Windows uses default ones, so each time you loose Linux settings, not Windows

[deKees687]

Ok, here it is.

mount output is at the end of the file.

boot-tree.txt

[glpnk]

You have Debian directory only, so you need to configure GRUB to write its bootloader to 2 places... But GRUB docs are complex...

/boot
├── efi
│   └── EFI
│       └── debian
│           ├── BOOTX64.CSV
│           ├── fbx64.efi
│           ├── grub.cfg
│           ├── grubx64.efi
│           ├── mmx64.efi
│           └── shimx64.efi

The simplest solution I found is:

sudo grub-install --removable

Try it and resend sudo tree /boot/efi, this should make fallback boot option, when your bios become unconfigured.

Next level is modifying GRUB config with dpkg-reconfigure grub-efi-amd64 but I don't have any Debian installation, so I can't help if something will go wrong