On 2017-01-11 22:23, Marc Chamberlin wrote:
On 1/10/2017 7:26 PM, Carlos E. R. wrote:
On 2017-01-09 23:53, Marc Chamberlin wrote:
On 12/23/2016 11:19 AM, Andrei Borzenkov wrote:
Did it help enlighten you as to why my laptop is requiring me to re-save the BIOS each time I try to power it up? Hi, I don't see the start of the thread, so apologies if this has already being said.
The first cause to have to re-save the bios is bad bios battery. Bad contact, dead battery, etc. Then there is software error: the bios calculates a checksum. If the checksum is invalid on boot, it assumes the contents of the config area are bad, and resets it (cmos bios memory).
Hi Carlos - This thread actually started just before Christmas, but I got diverted for awhile to other family issues so just trying to get back to solving this problem. (You have actually already responded to me on this thread also, thanks, btw.)
I thought that might be so. I'm accessing the inbox at my ISP, not my local folder that has the historic data, so I can't see posts that long this instant. Only those mails still at my ISP. Ok, I see now the rest of the thread, quite a long one!
Anywise, this is a brand new laptop so I kinda doubt the bios battery is dead.
You can see it in the output of "sensors" I think. Also somewhere under /proc or /sys, I don't remember where exactly, I'd have to search.
If I configure my BIOS to boot up Windows, using their boot loader, I have no problems with the BIOS. But if I boot up OpenSuSE using the GRUB boot loader then each time I power up my laptop, I have to go into the BIOS and simply re-save it, then the GRUB boot loader will let me use the menu to select which operating system I want to boot up and everything proceeds. But it is a PITA to have to jump through the hoops of getting BIOS to open up and then saving it each time before I can use the GRUB boot menu.... If I don't do this then I just get dumped into the low level GRUB console...
This looks to me as a software error in the UEFI implementation on that machine. maybe a firmware update would help. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)