Troubleshooting the Lenovo M710q: A Guide to Overcoming BIOS Lock Issues
Hello tech enthusiasts,
Today, I find myself facing an intriguing challenge with a Lenovo M710q mini PC. This compact machine, equipped with an Intel i3-7100T processor, 8GB of DDR4 RAM, and a 128GB SSD, came from an auction where many of its counterparts were touted as functional. However, I’ve encountered a roadblock that’s proving to be a bit more complicated than I anticipated.
Understanding the Situation
Upon powering up the M710q, I discovered that it was running an outdated version of Chromium OS. Despite my efforts, I have been unable to access the BIOS settings using the usual keys such as F1, F2, Delete, and more. Oddly enough, even without the SSD installed, I continue to face the same issues:
- No Access to BIOS: Attempts to enter the BIOS using various key combinations have been fruitless.
- Keyboard Challenges: The keyboard seemingly doesn’t function before booting into ChromeOS. I’ve tried activating the caps lock and other keys, but there’s no response.
- Operating System Installation: I have been unable to install any OS, whether it be Linux or Windows.
- Boot Order Modification: The inability to change the boot order is particularly frustrating.
- BIOS Chip Reading: Using a BIOS programmer to read the BIOS chip has yielded no success, likely due to my inexperience in this area.
In an effort to remedy the situation, I’ve attempted to reset the CMOS battery and reposition the jumper, but each time, I’m met with the same result: no initial splash screen or pre-POST messages, just an error relating to Chromium that suggests the issue may be embedded in the BIOS itself.
Seeking Solutions
Given that this is my first encounter with such a BIOS-related issue, I’m reaching out for insights and advice on how to proceed further. My ultimate goal is to revive this machine and install a Linux operating system, and I would appreciate any tips or strategies from those experienced in similar situations.
Thank you for your suggestions in advance! Let’s collaborate and figure this out together.
Share this content:
