Page 1 of 1

BSD corrupting CMOS?

Posted: Tue Apr 14, 2015 12:38 am
by SunOS4
Hello, I have a rather strange problem installing GhostBSD, it is corrupting the CMOS on my system!
When i try to install GhostBSD to my system it boots once, can't find my GForce graphics card so X crashes, then I reboot the computer it won't even POST. After a CMOS reset (remove the coin cell battery and power) the system will boot normal . Any idea as to what's going on here? System is a Gateway LX-200-01.

Re: BSD corrupting CMOS?  [SOLVED]

Posted: Tue Apr 14, 2015 6:31 pm
by ericbsd
That's the first time I here about A problem like that causing by GhostBSD I can't really help on that.

Re: BSD corrupting CMOS?

Posted: Wed Apr 15, 2015 10:04 pm
by SunOS4
Ok, I will blame some ACPI strange-ness.

Re: BSD corrupting CMOS?

Posted: Wed Nov 04, 2015 11:36 am
by TheRaven
GhostBSD is not corrupting your CMOS; if there are system issues involving the CMOS and Graphics card it is more than likely your BIOS. If your CMOS got corrupted there are issues with compatibility and/or video settings possibly instigating the BIOS to activate some type of trouble-shooting system that eventually crashes.

I have had similar issues with Gigabyte mother-boards where the BIOS will roll through different configurations in an attempt to get all hardware properly registered and running and get stuck where I would have to manually reset the BIOS settings and reconfigure them manually. It came to pass that I had a bad RAM slot, but that's a different discussion.

Neither GhostBSD nor its constituent system FreeBSD manipulate the CMOS or BIOS in any way; these systems could be used with specialized software to perform such tasks and FreeBSD may even come with tools that allow root users to engage said systems, but they themselves do not engage or normally allow access to the BIOS or CMOS for security and stability reasons.

CMOS is almost like the basic computer RAM for the BIOS and is reset or flushed at power off requiring a battery for persistence which may be another issue you could be encountering. If the battery dies, or is dying then you may run into issues where your specialized configurations are not remaining in memory and is evident by corrupted timing where the system clock always gives an incorrect time & date.

Conclusively: the problem(s) could be BIOS configuration issues involving incompatible settings, a dead or dying CMOS battery or failing hardware, in this case: either mobo or graphics card primarily, but could be memory too and is most likely not the O.S.

Solution: clean out your box/laptop, reset your BIOS to default settings, and pull all the memory but 1 stick and test the system for stability.