Sponsored Content
Full Discussion: cmos check sums
Top Forums UNIX for Dummies Questions & Answers cmos check sums Post 2128 by mib on Sunday 22nd of April 2001 08:16:08 AM
Old 04-22-2001
The reason is your computer forgets its CMOS settings. During the boot-up process or POST (Power-On Self Test) a checksum is generated by the BIOS from the CMOS and compared to the one saved the last time the CMOS Setup was run or the BIOS defaults were loaded. If the two numbers don't agree it is an indication that the data in the CMOS has been corrupted. and a checksum error is issued by the BIOS.

Reason:
A bad battery.
A battery that has become discharged (the computer has been off a very long time).
A disconnected battery.
Static electricity.
Grounding the CMOS circuitry.
A bad motherboard.
A bad real-time clock.


A simple solution you can try:
change the CMOS battery.

Write down all of the settings from the various setup menus.
Power off your PC.
Open the case and locate the battery on the motherboard.
Obtain a replacement battery from a local or online computer parts dealer.
Remove the old battery and replace it with the new one.
Replace the case and power on the PC.
Enter your PC's setup mode.
Reenter the settings you have written down from the various setup menus.


HTH
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Doing sums

Let me explain my problem, I have a file in the following format 9602622 - User ID 01 -2 - Question number & Grade 02 - 3 03 - 7 04 - 12 05 - 9 06 - 0 9601664 - User ID 01 -2 02 - 3 03 - 7 04 - 12 05 - 9 06 - 0 I need to change the file so it looks like this 9601664 54 -... (1 Reply)
Discussion started by: Captain Woods
1 Replies

2. Windows & DOS: Issues & Discussions

EISA CMOS checksum error

I have a UNIX server w/an Adaptec aha-2740 card and i keep getting this error during post: EISA CMOS checksum error. It then tries to boot from the floppy. Upon researching this problem i found that it could be one of two things. Either it is the battery on the m/b (which i have all but ruled out),... (3 Replies)
Discussion started by: dlee35
3 Replies

3. UNIX for Dummies Questions & Answers

Script to check for a file, check for 2hrs. then quit

I wish to seach a Dir for a specific file, once the file is found i will perform additional logic. If the file is not found within two hours, i would like to exit. Logically, I'm looking for the best way to approach this Thanks for any assistance in advance. Note: I'm using a C shell and... (2 Replies)
Discussion started by: mmarsh
2 Replies

4. Solaris

CMOS settings on SUN V20Z from Solaris10

Hello Guys, and good day to everybody. I am battling to redirect console on this V20Z 'beast', and would really like to know if it's possible to 'see' CMOS settings from Solaris10 point of view. Machine is remote and I can't easily go and reboot the box and press F2 etc... So is there a... (3 Replies)
Discussion started by: mponjevic
3 Replies

5. UNIX for Advanced & Expert Users

Check EOF char in Unix. OR To check file has been received completely from a remote system

Advance Thanks. (1) I would like to know any unix/Linux command to check EOF char in a file. (2) Or Any way I can check a file has been reached completely at machine B from machine A. Note that machine A ftp/scp the file to machine B at unknown time. (5 Replies)
Discussion started by: alexalex1
5 Replies

6. Shell Programming and Scripting

Create md5 sums and archive the resulting md5 files

Hello everyone, I am looking to basically creating md5sum files for all iso files in a directory and archive the resulting md5 files into a single archive in that very same directory. I worked out a clumsy solution such as: #find files for which md5sum are to be created and store the... (1 Reply)
Discussion started by: SurfTranquille
1 Replies

7. Shell Programming and Scripting

Perl code to check date and check files in particular dir

Hi Experts, I am checking how to get day in Perl. If it is “Monday” I need to process…below is the pseudo code. Can you please prove the code for below condition. if (today=="Monday" ) { while (current_time LESS THAN 9:01 AM) ... (1 Reply)
Discussion started by: ajaypatil_am
1 Replies

8. UNIX for Dummies Questions & Answers

Script that sums the contents of a folder (help me)

I'm looking for a script that sums the contents of a folder, When you give a parameter to the script , i want to know the size of the directory, the number of files, number of folders, These are commands that I have already found du -s find . -type f | wc -l find . -type d | wc -ly ... (19 Replies)
Discussion started by: Roggy
19 Replies

9. UNIX for Dummies Questions & Answers

Group sums by matching and then multiplying by weights

Hi Experts, Please help with the following. I have 3 columns in File 1 , variables with values nested within groups. File 1 gr1 var1 a gr1 var2 b gr1 var3 a gr1 var4 c gr2 var1 a gr2 var2 a gr2 var4 c gr3 var1 b gr3 var3 b gr3 var4 a gr3 var5 a (3 Replies)
Discussion started by: ritakadm
3 Replies
NVRAMTOOL(1)						      General Commands Manual						      NVRAMTOOL(1)

NAME
nvramtool - read/write coreboot-related information SYNOPSIS
nvramtool [OPTS] [-n] -r NAME nvramtool [OPTS] -e NAME nvramtool [OPTS] -a nvramtool [OPTS] -w NAME=VALUE nvramtool [OPTS] -p INPUT_FILE nvramtool [OPTS] -i nvramtool [OPTS] -c [VALUE] nvramtool [OPTS] -l [ARG] nvramtool [OPTS] -d nvramtool [OPTS] -Y nvramtool [OPTS] -b OUTPUT_FILE nvramtool [OPTS] -B INPUT_FILE nvramtool [OPTS] -x nvramtool [OPTS] -X DUMPFILE nvramtool [OPTS] -v nvramtool [OPTS] -h DESCRIPTION
nvramtool is a utility for reading/writing coreboot parameters and displaying information from the coreboot table. The coreboot table resides in low physical memory. It is created at boot time by coreboot, and contains various system information such as the type of mainboard in use. It specifies locations in the CMOS (nonvolatile RAM) where the coreboot parameters are stored. This program is intended for (x86-based) systems that use coreboot. For information about coreboot, see http://www.coreboot.org/. PARAMETERS
[-n] -r NAME Show the value of the coreboot parameter given by NAME. If -n is specified, show only the value. Otherwise show both parameter name and value. -e NAME Show all possible values for parameter given by NAME. -a Show the names and values for all coreboot parameters. -w NAME=VALUE Assign VALUE to coreboot parameter given by NAME. -p INPUT_FILE Assign values to coreboot parameters according to the contents of INPUT_FILE. The format of this file is described below. -i This is similar to the -p option, except that the contents of the input file are taken from standard input. -c [VALUE] If VALUE is present then set the CMOS checksum for the coreboot parameters to VALUE. Otherwise, show the checksum value. -l [ARG] If ARG is present then show information from the coreboot table as specified by ARG. Otherwise show all possible values for ARG. -d Do a low-level dump of the coreboot table. -Y Write CMOS layout information to standard output. If redirected to a file, the layout information may be used as input for the '-y LAYOUT_FILE' option (see below). -b OUTPUT_FILE Write the contents of CMOS memory to the binary file OUTPUT_FILE. The first 14 bytes of OUTPUT_FILE do not contain actual CMOS data, and are always written as zeros. This is because the first 14 bytes of the CMOS area do not contain CMOS memory. These bytes are involved with the functioning of the real time clock. -B INPUT_FILE Read binary data from INPUT_FILE and write the data to CMOS memory. The first 14 bytes of INPUT_FILE are skipped and data is writ- ten to CMOS starting at the 15th byte of the CMOS area. This is because the first 14 bytes of the CMOS area do not contain CMOS memory. These bytes are involved with the functioning of the real time clock. -x Show a hex dump of all CMOS data. The first 14 bytes of the dump do not contain actual CMOS data, and are always shown as zeros. This is because the first 14 bytes of the CMOS area do not contain CMOS memory. These bytes are involved with the functioning of the real time clock. -X DUMPFILE Read binary data from DUMPFILE (presumably a CMOS dumpfile created using the -b OUTPUT_FILE option) and show a hex dump of the data. -v Show version information for this program. -h Show a help message for this program. OPTIONS
In all cases above, [OPTS] evaluates to the following: [-y LAYOUT_FILE | -t] The '-y LAYOUT_FILE' option tells nvramtool to obtain CMOS layout information from the contents of LAYOUT_FILE. Likewise, the '-t' option tells nvramtool to obtain CMOS layout information from the CMOS option table (contained within the coreboot table). If neither option is specified, the CMOS option table is used by default. LAYOUT_FILE follows the format of the cmos.layout files provided by coreboot. If the coreboot installed on your system was built without specifying HAVE_OPTION_TABLE, then the coreboot table will not contain a CMOS option table. In this case, the '-y LAYOUT_FILE' option must be used. These two options are silently ignored when used in combination with other options (such as -h, for instance) for which they are not appli- cable. FILE FORMAT
For the -p option, INPUT_FILE must consist of a sequence of lines such that each line is either a blank line, a comment, or an assignment. A blank line consists only of zero or more whitespace characters (spaces and tabs). A comment is constructed as follows: [ws]#[text] Here, [ws] indicates optional whitespace characters and [text] indicates optional text. Blank lines and comments are both ignored. An assignment is constructed as follows: [ws]NAME[ws]=[ws]VALUE[ws] Here, NAME is the name of a coreboot parameter and VALUE is the value that will be assigned to NAME. VALUE is allowed to contain white- space characters, but it must begin and end with nonwhitespace characters. Note that each comment must appear on a line by itself. If you attempt to add a comment to the end of an assignment, then the comment will be interpreted as part of VALUE. It is useful to observe that the output produced by both the -a and the '[-n] NAME' options (without -n specified) adheres to this file format. BUGS
This program does not implement any type of synchronization to ensure that different processes don't stomp on each other when trying to access the nonvolatile RAM simultaneously. Therefore, corruption of the BIOS parameter values may occur if multiple instances of this pro- gram are executed concurrently. AUTHORS
David S. Peterson <dsp@llnl.gov> <dave_peterson@pobox.com> Stefan Reinauer <stepan@coresystems.de> Linux September 2008 NVRAMTOOL(1)
All times are GMT -4. The time now is 08:01 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy