Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Reboot the physical machine and enter the CMOS.
"some assembly language"? I could wipe the /mbr and some with debug.exe but I never heard of, nor saw any similar routine for "clear"ing a BIOS.
Whatever that means.
Any details of this endeavor, IMO are futile, as BIOSs/CMOSs integration is not what it used to be.
In the Pre-NT days, you could nuke your mbr with debug.exe, but since? Not sure you can "clear the BIOS",
Whatever that means.
Many of the "stories of Windows," today, are legends, dating from the earliest days when Windows did not have any sort of protection. (Nor did it need any, because computers by-and-large were not connected to one another.) Operating systems ran "in Real mode." Having one megabyte of RAM was an expensive luxury. A 20-megabyte hard drive was "huge." If you did have a network in your office, it probably used coax. If you wanted to have a phone in your car, you needed a really long piece of wire. And, so on.
Today, all operating systems provide a protected environment, and use virtual storage, so that "user-land" programs can only see what they're allowed to see, and can only touch what they're allowed to touch. Even the prerogatives of the "all-powerful" (sic) root user are restricted, and, in the latest versions, are becoming even more so.
So, you can't touch the BIOS, or its modern-day equivalent. You can't even see it. And, on most motherboards, it is physically write-protected from such software that can see it.
Last edited by sundialsvcs; 07-08-2016 at 08:00 AM.
On many laptops the BIOS password is stored in flash memory, and in those cases flashrom may indeed get the job done. Unlike vendor-specific BIOS flash tools, it will reprogram the entire flash chip, instead of just the parts containing updated code. Hence, it may very well wipe the password in the process.
On desktop PCs, the BIOS password is stored in the CMOS RAM inside the RTC chip, which one can access through I/O ports $70 and $71 ($70 is the index register and $71 is the data in/out port; see this page for more information and some examples in C).
The first 12 bytes of the CMOS RAM are actually the RTC clock, but the remaining 52+ bytes are used to hold various CMOS settings and possibly the password. Note that since there's almost always a checksum at the end, changing a single byte is enough to trigger a CMOS checksum error message upon reboot, which in turn tends to let you access the BIOS setup utility without entering a password.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.