Sponsored Content
Full Discussion: Bootup Error
Top Forums UNIX for Dummies Questions & Answers Bootup Error Post 49041 by zazzybob on Wednesday 24th of March 2004 07:29:32 AM
Old 03-24-2004
It looks to me that it has nothing to do with remote dialling, but more to do with the CMOS battery on the server's mainboard.

Replace the CMOS battery and then go from there. You may need to reconfigure the bios/cmos/whatever according to the particular system architecture you are using.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Triple bootup

Hi guys, May I know how to install Solaris 8 in the way that I can triple boot it with my the other two OS: WIndows ME and Windows 2000 Pro. Can you all please kindly advise me on how to setup the triple boot process inorder to allow Windows ME to be the default OS when being ask to choose... (1 Reply)
Discussion started by: cia
1 Replies

2. Linux

Preventing a scan of the RAID during bootup

I have a RH 7.3 server that needs a restart today after putting a patch in place. The last time I rebooted this box was almost a year ago and when the uptime is quite long, Linux likes to check all the disks for errors, including the RAID. This adds almost 1.5Hrs to my bootup process:eek: . Does... (1 Reply)
Discussion started by: turbo90awd
1 Replies

3. UNIX for Advanced & Expert Users

bootup script

Hello there I need to run a script whenever i reboot or startup my HP-UX server. This script adds some routes to the route table, and it start third party aplications like "Star Manager". I thought i could do this simply putting the script in "/sbin/init.d, and a link to the script in... (7 Replies)
Discussion started by: vascobrito
7 Replies

4. UNIX for Dummies Questions & Answers

Why not automatic bootup

Evry time I start up my mavhine ,have to type in unix at Boot : Is there a way unix should bootup automatically? Asif (2 Replies)
Discussion started by: asif iqbal
2 Replies

5. AIX

How to start ssh at bootup

Hi i installed ssh of version v 1.21 and my AIX is of 5.3. I want to start my ssh deamon at the startup can any one please help me out reg.. Thanks in advance.. (1 Reply)
Discussion started by: kmalla
1 Replies

6. AIX

File system not mounting at bootup

Hi, I've got a recent problem with 2 file systems on an AIX 5.3 server. The fs's are marked to auto mount at startup and do show as being mounted after a a restart however if you cd to the mount point and 'df -g .' it shows the fs hasn't actually mounted. $ mount |grep SQLT0001.0 ... (2 Replies)
Discussion started by: m223464
2 Replies

7. UNIX for Advanced & Expert Users

system slows after bootup for some time

Hi, I am using a Linux system running at run level 3. I am finding a wired problem, once the system boots, the system terminal slows down, I need to type the characters repeatedly to enter my login and password info. Also running any commands takes time, it stays in this condition for some... (1 Reply)
Discussion started by: cjjoy
1 Replies

8. UNIX for Dummies Questions & Answers

bootup sequence

What is the boot up sequence in UNIX? (2 Replies)
Discussion started by: karthi_g
2 Replies

9. Solaris

Sunfire X4600 Errors on Bootup

Hi Folks, Has anyone seen these errors on bootup. Mar 15 12:22:30 svc.startd: svc:/system/device/local:default: Method "/lib/svc/method/devices-local" failed due to signal SEGV.ht (c) 1983, 2010, Oracle and/or its affiliates. All rights reserved. Configuring devices. ... (1 Reply)
Discussion started by: ESSTEAM
1 Replies

10. SCO

Error F painit on bootup

I have a known good external SCSI HD running SCO UNIX OpenServer 5.0.7. I decided that I wanted to be able to run this drive on another computer, so I bought the same SCSI card as before (LSI) and then attempted to boot on the other system. The bootup process hung with the error F painit. I've... (13 Replies)
Discussion started by: Transpower
13 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 09:48 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy