Sponsored Content
Full Discussion: Drivers
Operating Systems AIX Drivers Post 302094809 by eth0 on Wednesday 1st of November 2006 08:34:13 AM
Old 11-01-2006
The adapter is an Adaptec SCSI card 39160
Dual Channel Ultra 160 SCSI

It will be used to connect an Ultrium 3 tape drive.
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Hardware and drivers

Dear All Can somebody help me how H/W and H/W drivers will affect the application? When I port my application from HP-UX to Solaris should I take care this area? What are the application touch point in H/W or H/W drivers on these two O.S.? (1 Reply)
Discussion started by: charlcy
1 Replies

2. Linux

wirelesslan Drivers

Can any body help me out, to setting up Wlan Drivers in Redhat 9 Thanks kranthi (1 Reply)
Discussion started by: kumar_d
1 Replies

3. HP-UX

SDLT Drivers

Greetings I looking for the drivers for an sdlt tape drive for hp-ux 11.0. I think the drivers i need are stape and tape2 does anyone know where i can get them Thanks Alan (2 Replies)
Discussion started by: Flipper_Al
2 Replies

4. Solaris

Drivers

Hi guys, Im totally new to solaris 10, I've just installed it & it works fine However, I get no sound when playing cds. Am wondering where I get the solaris 10 drivers for my soundblaster live from and how to install them? Thx in advance. Frizz (0 Replies)
Discussion started by: Frizz
0 Replies

5. UNIX for Dummies Questions & Answers

drivers unix 5.01 is compatible with drivers epson fx-2190

Please, I'm From Argentina, And I Need To Know If The Drivers Of Program Unix, Version 5.01 Is Compatible Whit Drivers Of The Printer Epson Fx-2190 Thanks, And I Hope Yuor Answer. (0 Replies)
Discussion started by: juan alberghina
0 Replies

6. Solaris

Rhine3 drivers out there?

Hi all, I have problems finding out a network driver for solaris... I am using D-link DFE-520TX Ethernet card and apparently that does not seem to have any support with solaris After having googled it up, i found out that it belongs to Rhine3 family.. So can anyone of you please help me... (0 Replies)
Discussion started by: wrapster
0 Replies

7. UNIX for Dummies Questions & Answers

Mach drivers

hello everyone, can anyone tell me what drivers the Mach kernel works with. I'm thinking about experimenting with the Mach kernel, and yes I know there are other kernels that are easier to work with but I just want to use the Mach kernel. So with that being said, can the Mach kernel work with... (11 Replies)
Discussion started by: neur0n
11 Replies

8. UNIX for Dummies Questions & Answers

Microkernel drivers

If microkernels do not load drivers into the kernel, does mean that the drivers are daemons that run in user space, or are there some other provision for drivers? I know it may sound a bit elementary but I'm not certain and I want to clear it up. Thanks in advance. (3 Replies)
Discussion started by: neur0n
3 Replies

9. AIX

DS8K drivers

Hi, We have all our servers connected to IBM DS8k via SVC. Some servers have SDD drivers and some have SDDPCM drivers. Now we have 2 servers one is physical other is IVM server, which dosen't have these drivers installed on them. They bothe are in production. Now we need to installe these... (6 Replies)
Discussion started by: vjm
6 Replies
cfgmgr_set_status(9r)													     cfgmgr_set_status(9r)

NAME
cfgmgr_set_status - General: Reports failure to the cfgmgr framework SYNOPSIS
int cfgmgr_set_status( char *driver_name ); ARGUMENTS
Specifies the name of the device driver for which you want to report an associated failure. This name is a string that matches the string you specified for the entry_name item in the /etc/sysconfigtab database. Typically, third-party driver writers specify the driver name (followed by a colon) in the sysconfigtab file fragment, which gets appended to the /etc/sysconfigtab database during the driver product installation. DESCRIPTION
The cfgmgr_set_status routine reports to the cfgmgr framework that a failure has occurred during static configuration. If the specified device driver is in the static configuration state, it does not know that the configuration operation is complete until all register call- back requests (routines) have successfully completed. Therefore, a device driver calls cfgmgr_set_status to report a possible failure dur- ing static configuration to the cfgmgr framework. Specifically, cfgmgr_set_status performs the following failure operations: Adjusts the state of the specified device driver Unconfigures the specified device driver from the cfgmgr framework The cfgmgr_set_status routine calls the device driver's configure routine at its CFG_OP_UNCONFIGURE entry point as part of these failure operations. The code associated with the CFG_OP_UNCONFIGURE entry point is responsible for determining how to deallocate any allocated resources during these failure operations. The cfgmgr_set_status routine does not notify the operator of a configuration failure. Part of the code associated with the CFG_OP_UNCON- FIGURE entry point could include an error logging operation to record the fact that a failure has occurred. The reason for doing this is that the cfgmgr framework's task is to accomplish the unconfigure operation of a statically configured device driver. You call the cfgmgr_set_status routine in the device driver's callback routine when the static configuration operation fails. You register a callback routine by calling the register_callback routine. RETURN VALUES
Upon successful completion, cfgmgr_set_status returns the value ESUCCESS. This success value indicates that cfgmgr_set_status adjusted the state of the device driver and caused the cfgmgr framework to unconfigure the driver. Otherwise, cfgmgr_set_status returns one of the fol- lowing error constants defined in /usr/sys/include/sys/sysconfig.h and /usr/sys/include/sys/errno.h: The device driver that you specified in the driver_name argument does not exist. In this case, cfgmgr_set_status cannot adjust the state and unconfigure the device driver. The device driver that you specified in the driver_name argument was not statically configured. The device driver that you specified in the driver_name argument is not in the static configuration state. EXAMPLES
See Writing Device Drivers: Tutorial for a code example of the cfgmgr_set_status interface. SEE ALSO
Routines: cfgmgr_get_state(9r), register_callback(9r) cfgmgr_set_status(9r)
All times are GMT -4. The time now is 01:45 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy