[Problem] Wrong Keyboard Specs in Panasonic CF-SV9 BIOS

BIOS/UEFI Modding BIOS Modding Guides and Problems
1

Hi everyone, I’m new to the forums. I’ve been trying to convert the keyboard on a Panasonic Let’s Note CF-SV9 .. ive physically replaced the keyboard from japanese to english and looks like the bios still thinks its japanese, and have been digging through the Panasonic BIOS/updater to figure out how the keyboard type is selected.

We’ve determined that the setting is in the MiscTable, specifically Type 0x15 / Item 0x0E (KeyboardId). The current value is 01 and I need to set it to 02.

The problem is that the BIOS update is an AMI PFAT / BIOS Guard image. Editing the value directly works at the binary level, but the Panasonic updater rejects the modified image. I traced the updater and the original image passes MF1307 with Err=00, while the modified image returns Err=01, so it looks like BIOS Guard/signature verification is kicking in.

At this point I’m wondering if modifying the signed BIOS image is the wrong way to do this. Does anyone know how Panasonic normally sets/provisions the MiscTable KeyboardId? Maybe through a service/manufacturing command, NVRAM, or another configuration area?

This is a Comet Lake CF-SV9, so I also don’t want to blindly write a modified SPI image if Boot Guard is involved.

BIOS V2.00L26: BIOSアップデートプログラム - パナソニックパソコンサポート（総合案内）

I can provide the extracted BIOS, offsets, MiscTable entry, IDA pseudocode, or the MF1307 traces if useful.

Thanks! Mainly hoping someone familiar with Panasonic/AMI firmware has seen this setting before or knows the proper way to set it.

thank you so much!


Edit by Fernando: Thread moved into the “BIOS Problems” Category and title customized

2

Really interesting work — thank you for digging this deep into the issue.

I have a CF-SV1 and have been looking into the exact same JIS-to-English keyboard problem, where the English keyboard can be physically installed but some keys don’t work correctly.

Finding the KeyboardId in the MiscTable is the first real technical clue I’ve seen about this problem. I understand that identifying the value doesn’t necessarily mean it can actually be changed, especially with BIOS Guard / Boot Guard involved, but your research is already extremely useful.

I’m very interested to see where this goes. If you make any further progress with the Panasonic provisioning method, NVRAM, or service/manufacturing commands, I’d love to hear about it.

Good luck, and thanks again for investigating such an obscure Let’s Note issue!

1 Like
3

Thanks I am hoping any of our BIOS experts here have successfully worked around those BIOS protections or succesfully patched Let’s Notes in some way can chime in.