Sponsored Content
Operating Systems Solaris unable to detect new cpu/memory module Post 302306593 by incredible on Monday 13th of April 2009 08:48:07 AM
Old 04-13-2009
Its either you're not using the correct part OR its not secured properly on the slot, which may show this sort of errors or cause these..
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Not able to detect nr of cpu in Solaris System

Hello, how can I detect the nr of cpu of my SUN E250 Solaris server? I have tryed with top but I was not able to find the information. Thanks. (1 Reply)
Discussion started by: pbonato
1 Replies

2. UNIX for Dummies Questions & Answers

Unable to detect my modem

I am new user to linux Mandrake. I am unable to install my modem "D-Link". I have double booting such as windows 98se and linux Mandrake. Linux Mandrake automatically detects all other harewares but unable to detect my modem "D-Link". Please send reply in this regard what to do? (1 Reply)
Discussion started by: Masud Mallik
1 Replies

3. OS X (Apple)

Not detect my memory card.

I'm using Mac OS X 10.3.9. My Problem is its not detect my memory card built in my camera. I have reinstall new clean install my OS X but still persist. Help me please... (2 Replies)
Discussion started by: shamsulamar
2 Replies

4. HP-UX

Memory re-allocation Failure HP-UX for C++ module

HI I am getting core dump with "Memory re-allocation Failure" error can any one help me to get the possible reasons of getting this type of error, I am running the C++ code on HP-UX. Please help me thanx in advance (1 Reply)
Discussion started by: gyanusoni
1 Replies

5. UNIX for Dummies Questions & Answers

cpu, memory and virtual memory usage

Hi All, Does anyone know what the best commands in the UNIX command line are for obtaining this info: current CPU usage memory usage virtual memory usage preferably with date and time parameters too? thanks ocelot (4 Replies)
Discussion started by: ocelot
4 Replies

6. Solaris

Unable to load module

Hey guys i got this error in my messages: warning : mod_load: cannot load module sbd - I dont know anything about this. - How do i verify if there is a module sbd - What are the reasons modules cant be loaded (1 Reply)
Discussion started by: sbn
1 Replies

7. Solaris

Need to identlfy memory module

Hi, Recently one of my server V490 showed memory issues on "Fault_PC 0x10158dec Esynd 0x01e2 Slot A: J3001" Below is the prtdiag info ========================= Memory Configuration =============================== Logical Logical Logical MC Bank Bank Bank ... (6 Replies)
Discussion started by: mpics66
6 Replies

8. OS X (Apple)

Unable to install Perl module via CPAN

Hi, I am trying to install Unicode::String from the cpan shell, and here is what I get: Checking if your kit is complete... Looks good Writing Makefile for Unicode::String cp String.pm blib/lib/Unicode/String.pm cp lib/Unicode/CharName.pm blib/lib/Unicode/CharName.pm... (3 Replies)
Discussion started by: psychomachine
3 Replies

9. Shell Programming and Scripting

Unable to install module using cpan

Hi, I am unable to install module using cpan. It says 407 Proxy Authentication Required I did setup proxy server and given username and password in .bashrc file and apt.conf file. export http_proxy=http://username:password@proxyserver:portno/ However, still unable to install... (1 Reply)
Discussion started by: Anjan1
1 Replies

10. Red Hat

Unable to detect HP backup tapes in RHEL 6.2

Hi All, We connected 2 new tape drives to the servers. I am not able to see both HP tape drives in OS level. I am using RHEL 6.2 OS. I have scanned and rebooted the server but still can't able to find the drives. Thanks in advance..!!!! ---------- Post updated 10-22-13 at 05:07 PM... (1 Reply)
Discussion started by: Navkreddy
1 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)
All times are GMT -4. The time now is 12:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy