Sponsored Content
Operating Systems Solaris finding boot reason in solaris Post 302248754 by pupp on Sunday 19th of October 2008 01:13:13 PM
Old 10-19-2008
what type of hardware are you using??? a system with a lom or a system controller can tell you these things. the larger system need to be "setswitchkey off" in order for a complete reboot of that particular system. something with a lom say a netra t1 will need to be 'poweroff' which you can view with the show eventlog command.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Solaris boot problem

I couldnt get my hands on my solaris 2.6 cd soo i used solaris 7 cd to boot to single user mode. I typed boot cdrom -s it bought me to my root prompt , but when i typed fsck.....nothing happened. It was as though it couldnt go ahead with fscking. it just bought up the prompt again,... (1 Reply)
Discussion started by: lealyz
1 Replies

2. Solaris

Solaris (9) won't boot!

Hi, I've just bought an Ultra 60 running solaris 9 (or so I've been led to believe). When I start up, it looks for a (presumably) domain/network to hook up to and the following messages are displayed: Boot device: net file and args: Network link setup failed Please check cable and try... (3 Replies)
Discussion started by: alarmcall
3 Replies

3. Solaris

solaris boot problem boot error loading interpreter(misc/krtld)

When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error. cannot find mis/krtld boot error loading... (0 Replies)
Discussion started by: johncy_j
0 Replies

4. Solaris

cant boot from solaris CD

Hi all , I am trying to isntallsolaris 10 using a DVD , But when i try to boot from the OB Prompt i am getting this error : Rebooting with command: boot cdrom -install Boot device: /pci@1f,700000/pci@0/pci@1/pci@0/ide@1f/cdrom@0,0:f File and args: -install Can't read disk label. Can't open... (2 Replies)
Discussion started by: ppass
2 Replies

5. Shell Programming and Scripting

Finding out how long a script runs for and exit reason.

I am running a daemon program that sends texts via a connected mobile phone. I run this daemon via CLI, and it loops a few commands (checking to see if there are any new texts). It runs perfectly, the problem is, when I leave this to run on my Ubuntu Desktop, and come back to it hours later it... (2 Replies)
Discussion started by: daydreamer
2 Replies

6. Solaris

Solaris in a SAN BOOT

My current situation is like this, I have a v440 connected to a netapp central storage 3140 via fiber channel, my OS and oracle is installed in the internal drive of the v440. What I would like to do is to advertise another LUN in netapp to the v440 and let my v440 boot from it so I can start... (3 Replies)
Discussion started by: q8devilish
3 Replies

7. Solaris

Solaris x86 installation using jumpstart does not local boot ( boot from hdd)

I am trying to install Solaris x86 using the Jumpstart server. I run the add_install_client command with appropriate options, and reboot my x86 Target box. The installation starts fine and unattended. After the installation completes and the target goes for a re-boot, it does not boot from the HDD... (9 Replies)
Discussion started by: hemalsid
9 Replies

8. Solaris

dual boot solaris/solaris zfs file system

Hi, I am running into a some problems creating a dual boot system of 2 solaris instances using ZFS file system and I was wondering if someone can help me out. First some back ground. I have been asked to change the file system of our server from UFS to ZFS. Currently we are using Solaris... (3 Replies)
Discussion started by: estammis
3 Replies

9. Solaris

Solaris 11 no sound despite finding hardware

Hello Everyone, I'm new to Solaris, less than a week to give an idea how green I am.:eek: Although new to UNIX, I've been running Linux (i.e. OpenSUSE, Ultimate Edition, Arch, and obviously Ubuntu) for many years, so, I decided to put Solaris 11 on my 12 core opteron. I had a bit of difficulty... (23 Replies)
Discussion started by: Nostradamus1973
23 Replies

10. Solaris

Solaris stuck during boot after reconfigure boot

Hello, I have a problem with my machine that won't boot properly. The story is that I installed a software called apcupsd, which is a control application for my APC battery UPS. I have used version 3.14.10 earlier, but as part of restoring my previously crashed os harddrive I wanted to... (18 Replies)
Discussion started by: Zorken
18 Replies
tsalarm(7D)							      Devices							       tsalarm(7D)

NAME
tsalarm - Alarm device driver SYNOPSIS
tsalarm@0:ctl DESCRIPTION
The tsalarm driver is a Multi-threaded, loadable non-STREAMS pseudo driver that manages ALOM alarms. The tsalarm driver provides an inter- face through which alarm relays can be controlled on SUNW,Netra-240 and SUNW,Netra-440 platforms. HARDWARE INTERFACE
The alarm hardware differs depending on platform. The Netra 240 and 440 platforms features four dry contact alarm relays which are controlled by ALOM. You can set each alarm to "on" or "off" by using ioctl interfaces provided from the host. The four alarms are labeled as "critical," "major," "minor," and "user." The user alarm is set by a user application depending on system condition. LED's in front of the box provide a visual indication of the four alarms. The number of alarms and their meanings/labels may vary across platforms. IOCTLS
The interface provided by the tsalarm driver comprises ioctls that enable applications to manipulate the alarm module. The alarm module is accessed via two device nodes: i) /dev/lom and /dev/tsalarm:ctl. The following ioctls are supported by the /dev/lom and /dev/tsalarm:ctl devices: TSIOCALCTL - Turn an alarm on or off. The argument is a pointer to the ts_aldata_t/lom_aldata_t structure. This structure is described below. alarm_no member is an integer which specifies the alarm to which the command is to be applied. The alarm_state/state structure member indicates the state to which the alarm should be set (where 0 == off). An error (EINVAL) is returned if either an invalid alarm_no or invalid alarm_state is pro- vided. TSIOCALSTATE - Get the state of the alarms. The argument is a pointer to the ts_aldata_t/lom_aldata_t structure. This structure is described below. alarm_no member is an integer which indicates the alarm to which the command will be applied. The alarm_state member holds the alarm's current state and is filled in by the driver. A zero indicates that the alarm is off. An error (EINVAL) is returned if an invalid alarm_no is provided. The struc- tures and definitions for the values are defined below. Alarm values: The following old style values are defined in <lom.io.h> #define ALARM_NUM_0 0 /* number of zero'th alarm */ #define ALARM_NUM_1 1 /* number of first alarm */ #define ALARM_NUM_2 2 /* number of second alarm */ #define ALARM_NUM_3 3 /* number of third alarm */ Alarm values defined in <lom.io.h> #define ALARM_OFF 0 /* Turn off alarm */ #define ALARM_ON 1 /* Turn on alarm */ Alarm Data Structure: This structure is defined in <lom.io.h> typedef struct { int alarm_no; /* alarm to apply command to */ int alarm_state; /* state of alarm (0 == off) */ } ts_aldata_t; Use the following LOM interfaces to get and set the alarms. These definitions are included in <lom_io.h> #define ALARM_CRITICAL 0 /* number of critical alarm */ #define ALARM_MAJOR 1 /* number of major alarm */ #define ALARM_MINOR 2 /* number of minor alarm */ #define ALARM_USER 3 /* number of user alarm */ The following alarm data structure is provided in <lom_io.h>: typedef struct { int alarm_no; int state; } lom_aldata_t; ERRORS
An open() will fail if: ENXIO The driver is not installed in the system. An ioctl() will fail if: EFAULT There was a hardware failure during the specified operation. EINVAL The alarm number specified is not valid or an invalid value was supplied. ENXIO The driver is not installed in the system or the monitor callback routine could not be scheduled. EXAMPLES
How to set an alarm: #include <sys/unistd.h> #include <fcntl.h> #include <stdio.h> #include <lom_io.h> #define LOM_DEVICE "/dev/lom" int main() { lom_aldata_t lld; int fd = open(LOM_DEVICE, O_RDWR); if (fd == -1) { printf("Error opening device: %s0, LOM_DEVICE); exit(1); } lld.alarm_no = ALARM_CRITICAL; /* Set the critical alarm */ lld.state = ALARM_ON; /* Set the alarm */ if (ioctl(fd, LOMIOCALCTL, (char *)&lld) != 0) printf("Setting alarm failed"); else printf("Alarm set successfully"); close(fd); } FILES
/dev/lom LOM device. /dev/tsalarm:ctl Alarm control device. /platform/platform/kernel/drv/sparcv9/tsalarm Device driver module. /platform/SUNW,Netra-240/kernel/drv/tsalarm.conf Driver configuration file. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcarx.u | +-----------------------------+-----------------------------+ |Architecture |SPARC | +-----------------------------+-----------------------------+ SEE ALSO
attributes(5) Writing Device Drivers SunOS 5.10 16 Mar 2004 tsalarm(7D)
All times are GMT -4. The time now is 08:05 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy