01-14-2006
We finally figured it out. The cause of the problem was a bad pci video card. From our research, we found that this problem is usually caused by a bad RAM. We replaced all of it and we still had the problem.
thanx for everyone's reply.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I couldnt get my hands on my solaris 2.6 cd soo i used solaris 7 cd to boot to single user mode. I typed
boot cdrom -s
it bought me to my root prompt , but when i typed fsck.....nothing happened. It was as though it couldnt go ahead with fscking. it just bought up the prompt again,... (1 Reply)
Discussion started by: lealyz
1 Replies
2. Solaris
Hello everybody,
I installed sun solaris i86 , the programme installation install the
"Mini Root" and after that he doing shutdown.
the camputer coming up and he can't boot.
how i can to resuled this problem ???
Thenk you in advence..... (2 Replies)
Discussion started by: yanly
2 Replies
3. Solaris
I had this working before. I have a 120GB disk with Solaris on the first primary partition, Fedore Core 3 on the second, Slackware on the third, And FreeBSD 5.3 on the 4th. Booting was handled by grub, and everything was working fine.
I decided to wipe everything out and start from scratch... (6 Replies)
Discussion started by: lyonsd
6 Replies
4. Solaris
When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error.
cannot find mis/krtld
boot error loading... (0 Replies)
Discussion started by: johncy_j
0 Replies
5. Solaris
Hi All,
I am newbie in solaris, please guide me.
A week before i installed solaris10 on my x86 system, it was working fine i always used "init 5" to shutdown my system as per my collegue advice.
But yesterday when i started my system it gave me following message
... (6 Replies)
Discussion started by: imrankhan.in
6 Replies
6. Solaris
Okay, let me sketch the problem.
I did have a ubuntu / Windows XP dual boot scenario that ran grub as my boot loader. I decided I wanted to try out solaris, so I popped in the opensolaris CD and hit install and told it to format and install over my linux partition.
Of course it did that, and... (2 Replies)
Discussion started by: syndex
2 Replies
7. Solaris
Hi All,
I have an x86 system which I have just installed Solaris 10 on, I intend to use this as a database server for Oracle, I tried to patch the server with the latest updates from SUN in preparation for the Oracle installation as I wanted to make sure that I was running the latest patches.
... (0 Replies)
Discussion started by: platforminc
0 Replies
8. Solaris
Hi All
We have the Sun Solaris server ... Got a power cut suddenly .... Crash happened to the system almost
You can access through Termnl .. But it seems he did not boot ... How to Make the process of the boot correctly without losing information
Thanks for all (3 Replies)
Discussion started by: gogo888
3 Replies
9. Solaris
Hello,
Can any kind soul please answer this? I want to boot a SunFire v490 with a dvd image we use to boot v480's. Is this possible? Are there caveats to doing this?
Thanks muchly,
mgb (1 Reply)
Discussion started by: mgb
1 Replies
10. Solaris
Hi
I have a problem on a server, when he boot I have this type of message loop, do you know what it corresponds to ?
( requesting internet Adress for 0:3:ba:fa:33:91 )
Regards
Sun Fire V240, No Keyboard
Copyright 2007 Sun Microsystems, INC. All rights reserved.
openboot 4.22.33,... (10 Replies)
Discussion started by: yoyo-tns
10 Replies
socal(7D) Devices socal(7D)
NAME
socal - Serial Optical Controller for Fibre Channel Arbitrated Loop (SOC+) device driver
SYNOPSIS
socal@sbus-slot,0
DESCRIPTION
The Fibre Channel Host Bus Adapter is an SBus card which implements two full duplex Fibre Channel interfaces. Each Fibre Channel interface
can connect to a Fibre Channel Arbitrated Loop (FC-AL).
The socal device driver is a nexus driver and implements portions of the FC-2 and FC-4 layers of FC-AL.
FILES
/kernel/drv/socal ELF Kernel Module
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Architecture |SPARC |
+-----------------------------+-----------------------------+
SEE ALSO
sbus(4), sf(7D), ssd(7D)
Writing Device Drivers
ANSI X3.230-1994, Fibre Channel Physical and Signalling Interface (FC-PH)
ANSI X3.272-1996, Fibre Channel Arbitrated Loop (FC-AL)
Fibre Channel Private Loop SCSI Direct Attach (FC-PLDA)
DIAGNOSTICS
The messages described below may appear on system console in addition to being logged.
On the console, these messages are preceded by:
socal%d: port %a
where %d is the instance number of the socal controller and %a is the port on the host adapter.
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: bad soft state.
Driver did not attach, devices will be inaccessible.
attach failed: unable to alloc xport struct.
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 9 May 1997 socal(7D)