Sponsored Content
Operating Systems Linux Red Hat Installing RedHat 8.0 onto Dell PowerEdge SC1425 - hdc: status error: status = 0x58 Post 302079732 by stdout on Wednesday 12th of July 2006 02:44:46 PM
Old 07-12-2006
hello,

do you really need to pass a kernel parameter??

cheers.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Couldn't open status file /var/samba/STATUS.LCK

I believe i have most of samba configured right but i get this error each time time try to run it. I was given suggestion that i touch the file, i did, but i still cannot rid myself of this error. Any suggestions (2 Replies)
Discussion started by: macdonto
2 Replies

2. Linux Benchmarks

Dell Dual Xeon PowerEdge 4600

Notes: System Configuration: Dell Computer Corporation PowerEdge 4600 (4 X Intel(R) XEON(TM) CPU 2.00GHz 1988.782 MHz) hyperthreaded System clock frequency: 99.0827 MHz Memory size (approximate): 2559 Megabytes ========================= CPUs ======================== CPU # CPU... (0 Replies)
Discussion started by: tnorth
0 Replies

3. Linux Benchmarks

Dell Poweredge 2400 / 533

CPU/Speed: Dual PIII 533 Ram: 256Mb PC133 Motherboard: Unknown, Intel Chipset Cache: 256k on board Controller: PARC Raid 2/Si, AIC-7880U Disk: 30Gb RAID 5 Load: 1 user. Clean boot, init 5 but X-Windows not loaded. Kernel: See Benchmarks. pgms: gcc 3.2.3 ... (2 Replies)
Discussion started by: Garp
2 Replies

4. Solaris

Installing Solaris 10 on Dell PowerEdge 2800

hi, i am trying to install solaris 10 (on 4 cd's downloaded from the sun website) on my dell poweredge 2800 server. 2 xeon processors, 2GB of RAM and 2 NICS, 73 GB SCSI (maxtor ultra320, 3.5 series), i can give more details on request... the installation crashes when trying to detect the NICS... (0 Replies)
Discussion started by: xinugeek
0 Replies

5. Filesystems, Disks and Memory

Linux and Dell 1500sc Poweredge Server

Does anybody no how to get around the fact that the Red Hat installation does not see the SCSI hard drives. It lets you manually pick the proper device, but still fails saying no drive detected (or something to that effect). I was going to install windows 2003 Server and use VMware...but again,... (1 Reply)
Discussion started by: Fatflea
1 Replies

6. Programming

/dev/mem on Dell Poweredge

Hi, I have a C++ program to access /dev/mem and retrieve details like Vendor, Manufacturer details of the motherboard. This works fine on all the machines except for on Dell Poweredge 2850,1950... machines. I receive a 'EFAULT' when I try to access /dev/mem on these servers. I suspect some... (1 Reply)
Discussion started by: ragisreekanth
1 Replies

7. SCO

Dell PowerEdge 2600 tape backup

I was asked to get a Dell PowerEdge 2600 server, out of warranty, running SCO 3.2v5.06 to perform a full backup. I spent hours researching and preparing a strategy only to fail on-site. The only device names in /dev for a tape drive were /dev/xStp0 /dev/xcdt0 /dev/xct0 ... (6 Replies)
Discussion started by: ezlarry
6 Replies

8. Programming

How to track table status delete/update/insert status in DB2 V10 z/os?

Dear Team I am using DB2 v10 z/os database . Need expert guidance to figure out best way to track table activities ( Ex Delete, Insert,Update ) Scenario We have a table which is critical and many developer/testing team access on daily basis . We had instance where some deleted... (1 Reply)
Discussion started by: Perlbaby
1 Replies

9. UNIX for Beginners Questions & Answers

Redhat Virtualization EN error : InitLogger main process terminated with status 1

My server has /var/log/messages with 'init: initLogger main process (608798) terminated with status 1' errors. I researched about the error and also followed the steps from stackexchange : 157059/error-init-ttys0-dev-ttys0-main-process-1612-terminated-with-status-1]linux - ERROR: init: ttyS0... (0 Replies)
Discussion started by: Paras Pandey
0 Replies
register_callback(9r)													     register_callback(9r)

NAME
register_callback - General: Registers a configuration callback routine SYNOPSIS
int register_callback( void (*function) (), int point, int order, ulong argument ); ARGUMENTS
Specifies the name of the routine that you want called at a later time. Specifies the dispatch point at which the kernel calls this call- back routine. The kernel passes the value associated with this dispatch point to the kernel module's callback routine when it calls it. Specifies the order in which you want callback routines registered for the same dispatch point to be executed. The kernel passes the value associated with this order to the kernel module's callback routine when it calls it. You use this argument to control the order of execu- tion of multiple callback routine within each dispatch point. The register_callback routine executes a kernel module's callback routine for the same dispatch point in increasing numerical order of the value specified in the order argument. Specifies an argument that you want the kernel to pass to the kernel module'scallback routine when the kernel calls it. You pass the integer constant 0L to indicate that you do not want to pass an argument. DESCRIPTION
The register_callback routine registers a kernel module's callback routine. The kernel calls a kernel module's callback routine when execu- tion reaches the point specified in the point and order arguments. The kernel passes the values specified in the point and argument argu- ments to the kernel module's callback routine. Kernel modules implement one or more callback routines to handle the different dispatch points in the boot path. The dispatch point constants you can pass to the point argument are defined in the /usr/sys/include/sys/sysconfig.h file. The following ta- ble lists the dispatch point constants that kernel modules can use: The dispatch point is hardware preconfiguration. Tasks that do not require completion of hardware configuration can be performed at this dispatch point. The dispatch point is hardware postconfiguration. Tasks that require completion of hardware configuration can be performed at this dispatch point. The dispatch point is root file system available. Tasks that require completion of the root file system mount operation can be performed at this dispatch point. The order constants you can pass to the order argument are defined in the /usr/sys/include/sys/sysconfig.h file. The following table lists the order constants that kernel modules can use: This callback routine is registered at the lowest priority. Typically, you pass this con- stant with an appropriate offset. The kernel executes callback routines registered at this priority last. This callback routine is regis- tered at the highest priority. Typically, you pass this constant with an appropriate offset. The kernel executes callback routines regis- tered at this priority first. NOTES
The kernel maintains an internal callback list that stores the values you pass to the register_callback routine. These callbacks remain registered until the user removes them. Only statically configured kernel modules need to implement callback routines. Thus, only statically configured kernel modules need to call the register_callback routine. You typically call the cfgmgr_get_state routine to determine if the kernel module is in the dynamic configuration state or the static con- figuration state. RETURN VALUES
Upon successful completion, the register_callback routine returns the value ESUCCESS. Otherwise, register_callback returns one of the following error constants defined in /usr/sys/include/sys/errno.h: The system limit on the maximum number of callback requests was exceeded. To change the maximum number of callback requests, set the new value for the boot-time tunable parameter max_callbacks in the cm subsystem (located in the /etc/sysconfigtab database) and reboot the system. You can use the sysconfigdb utility to accomplish this task. The value you passed to the point argument is outside the minimum and maximum range. FILES
SEE ALSO
Kernel routines: cfgmgr_get_state(9r), unregister_callback(9r) register_callback(9r)
All times are GMT -4. The time now is 08:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy