07-02-2012
Presently I am just trying to install a simple char driver or say a simple kernel module.
---------- Post updated 07-03-12 at 12:41 AM ---------- Previous update was 07-02-12 at 09:39 PM ----------
Thanks vbe for the inputs.
What if I want just to get the driver module loaded at boot time without building it in the kernel?
How to go about it?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Please Help
Let me start off by saying that I am a total idiot when it comes to unix. Please, if you would care to reply keep this in mind. Thank you.
I have been attempting to get my unix machine online to no avail. I have the rest of the house networked with 3 other windows machines into a... (1 Reply)
Discussion started by: kmer
1 Replies
2. UNIX for Dummies Questions & Answers
Hi...
I m working on UNIX z/OS. Actually i have to pass the parameters from the JCL to java-db2 program thru PARM. I am able to pass the arguments but the problem occured is, it is throwing an exception while loading the db2 driver as 'Javaclassnotfound:com.ibm.db2.jcc.DB2Driver'... (0 Replies)
Discussion started by: Sujatha Gowda
0 Replies
3. Solaris
Hi folks.
By disk cloning on Solaris x86, I used a command dd.
I pulled out the source and inserted the new disk.
By loading I have received the following issue: BAD PBR SIGN. :( (5 Replies)
Discussion started by: wolfgang
5 Replies
4. IP Networking
hello, i need help on setting my coyote linux, i've working on this for last 5 days, can't get it to work. I've been posting this message to coyote forum, and other linux forum, but haven't get any answer yet. Hope someone here can help me...... please see my attached picture first.
... (0 Replies)
Discussion started by: dlwoaud
0 Replies
5. Windows & DOS: Issues & Discussions
We recently replaced an existing Windows Server 2000 with a Windows Server 2003. The server‘s primary function is file/print in our development environment.
One of the directories is shared using NFS. All compiled software is kept in this share (we use C & C++). The generated “.out” and “.ndb”... (0 Replies)
Discussion started by: BigBuff52
0 Replies
6. Hardware
In general terms what are the differences platform driver,codec driver and Machine driver? (1 Reply)
Discussion started by: rupeshkp728
1 Replies
7. Linux
Hi All,
I am trying to make rpm package for unixODBC driver manager 2.3.0 using below spec file. During rpmbuild i am getting the error. Can you pls advice how we can overcome this issue
%define name unixODBC
%define ver 2.3.0
%define prefix /usr
%define sysconfdir /etc
%define libdir... (2 Replies)
Discussion started by: kamauv234
2 Replies
8. Red Hat
Hi Gurus,
I have a odbc in Linux.
when I run command ldd. I got following result:
# ldd DWora26.so
linux-vdso.so.1 => (0x00007fff26355000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fc31e70a000)
librt.so.1 => /lib64/librt.so.1 (0x00007fc31e501000)
... (1 Reply)
Discussion started by: ken6503
1 Replies
9. IP Networking
I'm trying to figure out what circumstances would cause an Open Solaris 11.2 host to switch itself from a static to a DHCP ip address upon reboot. This has only happened once but is a cause for some concern as this machine will be part of a web server pool.
Nothing has changed on the LAN that... (2 Replies)
Discussion started by: SmokeyJoe
2 Replies
10. AIX
I am getting the following error on loading the connector DLL in IHS 8.5 on AIX 7.1
bash-4.2# /usr/32bit/IBM/HTTPServer/bin/apachectl start
httpd: Syntax error on line 902 of /usr/32bit/IBM/HTTPServer/conf/httpd.conf:
Cannot load /usr/<company_name>/IHS85/lib/libApache22Connector.a
into... (3 Replies)
Discussion started by: George47
3 Replies
usoc(7D) Devices usoc(7D)
NAME
usoc - universal serial optical controller for Fibre Channel arbitrated loop (SOC+) device driver
DESCRIPTION
The Fibre Channel adapter is an SBus card that implements two full duplex Fibre Channel interfaces. Each interface can connect to a Fibre
Channel arbitrated loop (FC-AL). The usoc device driver is a nexus driver and implements portions of the FC-2 and FC-4 layers of FC-AL.
FILES
/kernel/drv/usoc
32-bit ELF kernel module
/kernel/drv/sparcv9/usoc
64-bit ELF kernel module
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Architecture |SPARC |
+-----------------------------+-----------------------------+
|Interface stability |Unknown |
+-----------------------------+-----------------------------+
|Availability |SUNWusoc |
+-----------------------------+-----------------------------+
SEE ALSO
fctl(7D), sbus(4), fcp(7D), fp(7D), ssd(7D)
Writing Device Drivers
Fibre Channel Physical and Signaling Interface (FC-PH) ANSI X3.230: 1994
Fibre Channel Arbitrated Loop (FC-AL) ANSI X3.272-1996
Fibre Channel Private Loop SCSI Direct Attach (FC-PLDA) NCITS TR-19:1998
Fabric Channel Loop Attachment (FC-FLA), NCITS TR-20:1998
DIAGNOSTICS
The following messages are logged and may also appear on the system console. On the console these messages are preceded by:
usoc%d:
where
usoc%d:
is the per-port instance number of the usoc controller.
Fibre Channel is ONLINE
The Fibre Channel loop is now online.
Fibre Channel Loop is ONLINE
The Fibre Channel loop is now online.
Fibre Channel Loop is OFFLINE
The Fibre Channel loop is now offline.
attach failed: device in slave-only slot.
Move soc+ card to another slot.
attach failed: alloc soft state.
Driver did not attach, devices will be inaccessible.
attach failed: bad soft state.
Driver did not attach, devices will be inaccessible.
attach failed: unable to map eeprom
Driver was unable to map device memory; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to map XRAM
Driver was unable to map device memory; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to map registers
Driver was unable to map device registers; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to access status register
Driver was unable to map device registers; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to install interrupt handler
Driver was not able to add the interrupt routine to the kernel. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to access host adapter XRAM
Driver was unable to access device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to write host adapter XRAM
Driver was unable to write device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: read/write mismatch in XRAM
Driver was unable to verify device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
SunOS 5.10 20 Jul 1999 usoc(7D)