Sponsored Content
Operating Systems AIX AIX 7.2 - Error initializing a device into the kernel. Post 303029162 by Don Cragun on Tuesday 22nd of January 2019 03:24:26 PM
Old 01-22-2019
Thank you for telling us what you found. It will help someone else who runs into this same problem later and see your thread.
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Dleting a Device in AIX 4.3

I need to delete a TTY in my AIX 4.3 system. I have tried using the smit but everytime I try it, there is a message telling me that the device is in use and cannot be changed. How do I take the device "offline", so to speak, so that I can edit the settings and/or delete it. V/R Djassi (3 Replies)
Discussion started by: djassi
3 Replies

2. UNIX for Advanced & Expert Users

Kernel and Device Driver Programming

I am looking for a guide on how to program for either the Linux or FreeBSD (includes 4.4BSD, NetBSD or OpenBSD) kernel. I would prefer to learn how to write device drivers, but anything would help. If you know, please email me at *removed* or leave a post here Regards, Farhan (0 Replies)
Discussion started by: Farhan
0 Replies

3. Linux

Linux Device Driver: avoid mem copy from/to user/kernel space

I recently started working with Linux and wrote my first device driver for a hardware chip controlled by a host CPU running Linux 2.6.x kernel. 1. The user space process makes an IOCTL call with pointer to a user memory buffer. 2. The kernel device driver in the big switch-case of IOCTL,... (1 Reply)
Discussion started by: agaurav
1 Replies

4. Fedora

Is Kernel module is the same as a device driver?

I have been reading prep questions for my second unix academy exam, and there's a nuance, I'm not sure I understand it correctly. I've been under impression from my readings of book by Evi Nemeth and from unix academy DVDs I've been watching, that kernel's modules are drivers. I think of it, as... (25 Replies)
Discussion started by: newlinuxuser1
25 Replies

5. UNIX for Advanced & Expert Users

Get pointer for existing device class (struct class) in Linux kernel module

Hi all! I am trying to register a device in an existing device class, but I am having trouble getting the pointer to an existing class. I can create a class in a module, get the pointer to it and then use it to register the device with: *cl = class_create(THIS_MODULE, className);... (0 Replies)
Discussion started by: hdaniel@ualg.pt
0 Replies

6. Android

Running only the Linux kernel of an Android device

I am looking for a way to run on top of the Linux kernel of an Android device. I want to use the existing configured Linux beneath Android rather than put a new Linux distribution onto a device. The article "The Android boot process from power on" (sorry, forum won't let me paste the link)... (0 Replies)
Discussion started by: raoulney
0 Replies

7. UNIX for Advanced & Expert Users

Kernel crash - NULL pointer dereference when calling DEVICE_WRITE from KTHREAD in a USB device drive

I'm writing a simple USB driver to drive a stepper motor based on USB Skeleton 2.2 Driver, kernel 3.8. The basic version is running properly. As a advancement, I introduced KTHREAD to call the DEVICE_WRITE (skel_write) (), so that the driver will be available for other tasks & requests. Calling... (0 Replies)
Discussion started by: miteshgaware
0 Replies

8. AIX

AIX - NIC device explanation need

Hello, I have some doubt about the NIC device on my AIX box. When using lsdev command / > lsdev -Cc adapter | grep en ent0 Available 03-00 2-Port 10/100/1000 Base-TX PCI-Express Adapter (14104003) ent1 Available 03-01 2-Port 10/100/1000 Base-TX PCI-Express Adapter (14104003) ent2... (11 Replies)
Discussion started by: Phat
11 Replies
cfg_attr_t(9s)															    cfg_attr_t(9s)

NAME
cfg_attr_t - General: Contains information for managing the loading and unloading of kernel modules SYNOPSIS
typedef struct cfg_attr { char name[CFG_ATTR_NAME_SZ]; uchar type; uchar operation; uint status; long index; union { struct { caddr_t val; ulong min_size; ulong max_size; void (*disposal)(); ulong val_size; } bin; struct { caddr_t val; ulong min_len; ulong max_len; void (*disposal)(); } str; struct { ulong val; ulong min_val; ulong max_val; } num; } attr; } cfg_attr_t; MEMBERS
Specifies the ASCII name of the attribute. The name must be between 2 and CFG_ATTR_NAME_SZ characters in length, including the terminating null character. Do not begin the ASCII name of the attribute with the Method_ or Device_ characters. The cfgmgr framework reserves certain names that begin with the Method_ and Device_ characters. Specifies the data type associated with the name attribute. See the DESCRIPTION section for the constants you can pass to the type member. Specifies the operations that the cfgmgr framework can perform on the attribute. See the DESCRIPTION section for the constants you can pass to the operation member. Stores the return code from operations (configure, unconfigure, query) that the cfgmgr framework performs. See the DESCRIPTION section for the operation codes that the cfgmgr framework can return to the status member. Stores a value that scopes the target for indexed attributes. Specifies a union of the possi- ble attribute types used for storing values, kernel locations, validation criteria, and disposal routines. The cfgmgr framework uses the appropriate union element according to the attribute type. For example, attributes of type CFG_ATTR_ULONGTYPE use the union element num. DESCRIPTION
The cfg_attr_t data structure contains information for managing the configuring and unconfiguring of kernel modules. The cfgmgr framework passes a pointer to this data structure to the kernel module's configure routine. The kernel module can parse this structure pointer to check the validity of the values associated with the module's associated sysconfigtab file fragment and the /etc/sysconfigtab database. You must set the type member to one of the following constants: Data type is a null-terminated array of characters. Data type is a 32-bit signed integer. Data type is a 32-bit unsigned integer. Data type is a 64-bit signed integer. Data type is a 64-bit unsigned integer. Data type is an array of bytes. Data type is an 8-bit unsigned character. Data type is a 16-bit unsigned short integer. You can set the operation member to one of the following constants: The cfgmgr framework configures the attribute. This means the cfgmgr framework obtains a data value for the attribute from the /etc/sysconfigtab database. The configure operation occurs when the cfgmgr frame- work calls the configure routine at its CFG_OP_CONFIGURE entry point. (That is, the optype argument of the configure routine evaluates to the CFG_OP_CONFIGURE constant.) The cfgmgr framework queries (reads) the attribute. This means the kernel module cooperates with the cfg- mgr framework to provide the value associated with the attribute as a result of user-initiated query requests. These requests are typically the result of the sysconfig -q command. The query operation occurs when the cfgmgr framework calls the configure routine at its CFG_OP_QUERY entry point. (That is, the optype argument of the configure routine evaluates to the CFG_OP_QUERY constant.) The cfgmgr framework reconfigures the attribute. This means the cfgmgr framework reconfigures the data value for the attribute. This functionality allows a user to modify the attribute. A reconfigure request is typically the result of the sysconfig -r command. The reconfigure opera- tion occurs when the cfgmgr framework calls the configure routine at its CFG_OP_RECONFIGURE entry point. (That is, the optype argument of the configure routine evaluates to the CFG_OP_RECONFIGURE constant.) The cfgmgr framework can return one of the following operation codes: Successful operation. The attribute you specified in the name member does not exist. The attribute you specified in the name member does not support the operation. The subsystem failed. The value or size of the attribute you specified in the name member is too small. The value or size of the attribute you specified in the name member is too large. The data type that you specified for the attribute you specified in the name member is invalid or is a mismatch. The index associ- ated with the attribute that you specified in the name member is invalid. The cfgmgr framework could not allocate memory for the specified attribute. The attribute that you specified in the name member cannot be converted to a number. FILES
SEE ALSO
Data Structures: cfg_subsys_attr_t(9s) cfg_attr_t(9s)
All times are GMT -4. The time now is 10:24 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy