AIX 7.2 - Error initializing a device into the kernel.


 
Thread Tools Search this Thread
Operating Systems AIX AIX 7.2 - Error initializing a device into the kernel.
# 1  
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.
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. 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

2. 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

3. 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

4. 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

5. 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

6. 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

7. 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

8. 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
Login or Register to Ask a Question
pcilib(7)                                                        The PCI Utilities                                                       pcilib(7)

NAME
pcilib - a library for accessing PCI devices DESCRIPTION
The PCI library (also known as pcilib and libpci) is a portable library for accessing PCI devices and their configuration space. ACCESS METHODS
The library supports a variety of methods to access the configuration space on different operating systems. By default, the first matching method in this list is used, but you can specify override the decision (see the -A switch of lspci). linux-sysfs The /sys filesystem on Linux 2.6 and newer. The standard header of the config space is available to all users, the rest only to root. Supports extended configuration space, PCI domains, VPD (from Linux 2.6.26), physical slots (also since Linux 2.6.26) and information on attached kernel drivers. linux-proc The /proc/bus/pci interface supported by Linux 2.1 and newer. The standard header of the config space is available to all users, the rest only to root. intel-conf1 Direct hardware access via Intel configuration mechanism 1. Available on i386 and compatibles on Linux, Solaris/x86, GNU Hurd, Win- dows, BeOS and Haiku. Requires root privileges. intel-conf2 Direct hardware access via Intel configuration mechanism 2. Available on i386 and compatibles on Linux, Solaris/x86, GNU Hurd, Win- dows, BeOS and Haiku. Requires root privileges. Warning: This method is able to address only the first 16 devices on any bus and it seems to be very unreliable in many cases. fbsd-device The /dev/pci device on FreeBSD. Requires root privileges. aix-device Access method used on AIX. Requires root privileges. nbsd-libpci The /dev/pci0 device on NetBSD accessed using the local libpci library. obsd-device The /dev/pci device on OpenBSD. Requires root privileges. dump Read the contents of configuration registers from a file specified in the dump.name parameter. The format corresponds to the output of lspci -x. darwin Access method used on Mac OS X / Darwin. Must be run as root and the system must have been booted with debug=0x144. PARAMETERS
The library is controlled by several parameters. They should have sensible default values, but in case you want to do something unusual (or even something weird), you can override them (see the -O switch of lspci). Parameters of specific access methods dump.name Name of the bus dump file to read from. fbsd.path Path to the FreeBSD PCI device. nbsd.path Path to the NetBSD PCI device. obsd.path Path to the OpenBSD PCI device. proc.path Path to the procfs bus tree. sysfs.path Path to the sysfs device tree. Parameters for resolving of ID's via DNS net.domain DNS domain containing the ID database. net.cache_name Name of the file used for caching of resolved ID's. Parameters for resolving of ID's via UDEV's HWDB hwdb.disable Disable use of HWDB if set to a non-zero value. SEE ALSO
lspci(8), setpci(8), update-pciids(8) AUTHOR
The PCI Utilities are maintained by Martin Mares <mj@ucw.cz>. pciutils-3.5.2 03 October 2016 pcilib(7)