pop pop
12-25-2005, 01:23 PM
I've been chasing some issues with my new Linux build and it came down to a BIOS update and/or a kernel bug. I updated the BIOS and the problem remains so I submitted a bug report and have received one response/request so far.
Here's the BIOS update questions, keep in mind that this was the first time I ever did one. The BIOS (AMI) that was on the Asus P5LD2-VM mobo when it arrived was version 301 with a release date of 10/12/2005. The only available update was version 406 with a "date" shown on the Asus site of 11/21/2005. The update was "add support for additional CPUs".
I did the update and all appeared to go fine. But there's a puzzler or two. The BIOS now shows the new version number--406--but the release date is still the original 10/12/2005. Secondly, all my settings remained, were retained, after the burn.
The questions:
Is it normal or unusual for the BIOS date to stay the same after a flash update?
Is it normal or unusual for non-default settings to remain after a flash update?
Do I need to do something like remove/replace the CMOS battery after the flash update?
Thanks
Here's the BIOS update questions, keep in mind that this was the first time I ever did one. The BIOS (AMI) that was on the Asus P5LD2-VM mobo when it arrived was version 301 with a release date of 10/12/2005. The only available update was version 406 with a "date" shown on the Asus site of 11/21/2005. The update was "add support for additional CPUs".
I did the update and all appeared to go fine. But there's a puzzler or two. The BIOS now shows the new version number--406--but the release date is still the original 10/12/2005. Secondly, all my settings remained, were retained, after the burn.
The questions:
Is it normal or unusual for the BIOS date to stay the same after a flash update?
Is it normal or unusual for non-default settings to remain after a flash update?
Do I need to do something like remove/replace the CMOS battery after the flash update?
Thanks