SUN Ultra-2 with Solaris 9 constantly self reboots

The Ultra-2 self reboots several times per day.
It is a kernel problem but I was unable to find a solution, so I hope that someone from this forum will help me.
The uname information is:
SunOS ermis 5.9 Generic_118558-14 sun4u sparc SUNW,Ultra-2
The log information is:
Oct 18 12:41:47 ermis SUNW,UltraSPARC: [ID 110026 kern.warning] WARNING: [AFT1] EDP event on CPU1 Data access at TL=0, errID 0x00000691.0326e08e
Oct 18 12:41:47 ermis AFSR 0x00000000.00400100<EDP> AFAR 0xffffffff.ffffffff
Oct 18 12:41:47 ermis AFSR.PSYND 0x0100(Score 95) AFSR.ETS 0x00 Fault_PC 0xfd6dbf38
Oct 18 12:41:47 ermis UDBH 0x0000 UDBH.ESYND 0x00 UDBL 0x0000 UDBL.ESYND 0x00
Oct 18 12:41:47 ermis SUNW,UltraSPARC: [ID 581146 kern.info] [AFT2] errID 0x00000691.0326e08e No error found in ecache (No fault PA available)
Oct 18 12:41:47 ermis SUNW,UltraSPARC: [ID 542596 kern.info] [AFT3] errID 0x00000691.0326e08e Above Error is in User Mode
Oct 18 12:41:47 ermis and is fatal: will reboot
Oct 18 12:41:47 ermis unix: [ID 855177 kern.warning] WARNING: [AFT1] initiating reboot due to above error in pid 580 (httpd)
Oct 18 12:41:52 ermis pseudo: [ID 129642 kern.info] pseudo-device: tod0
Oct 18 12:41:52 ermis genunix: [ID 936769 kern.info] tod0 is /pseudo/tod@0
Oct 18 12:42:04 ermis syslogd: going down on signal 15
Oct 18 12:42:26 ermis genunix: [ID 672855 kern.notice] syncing file systems...
Oct 18 12:42:26 ermis genunix: [ID 904073 kern.notice] done
Oct 18 12:43:09 ermis genunix: [ID 540533 kern.notice] ^MSunOS Release 5.9 Version Generic_118558-14 32-bit
Oct 18 12:43:09 ermis genunix: [ID 943905 kern.notice] Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved.
Oct 18 12:43:09 ermis Use is subject to license terms.
Oct 18 12:43:09 ermis unix: [ID 349649 kern.info]
Oct 18 12:43:09 ermis NOTICE: 64-bit OS installed, but the 32-bit OS is the default
Oct 18 12:43:09 ermis for the processor(s) on this system.
Oct 18 12:43:09 ermis See boot(1M) for more information.
Oct 18 12:43:09 ermis Booting the 32-bit OS ...
Oct 18 12:43:09 ermis genunix: [ID 678236 kern.info] Ethernet address = 8:0:20:8f:82:a0
Oct 18 12:43:09 ermis unix: [ID 389951 kern.info] mem = 393216K (0x18000000)
Oct 18 12:43:09 ermis unix: [ID 930857 kern.info] avail mem = 381861888
Oct 18 12:43:09 ermis rootnex: [ID 466748 kern.info] root nexus = Sun Ultra 2 UPA/SBus (2 X UltraSPARC 200MHz)
Oct 18 12:43:09 ermis rootnex: [ID 349649 kern.info] sbus0 at root: UPA 0x1f 0x0 ...
Oct 18 12:43:09 ermis genunix: [ID 936769 kern.info] sbus0 is /sbus@1f,0
Oct 18 12:43:09 ermis scsi: [ID 365881 kern.info] /sbus@1f,0/SUNW,fas@e,8800000 (fas0):
Oct 18 12:43:09 ermis rev 2.2 FEPS chip
Oct 18 12:43:09 ermis sbus: [ID 349649 kern.info] fas0 at sbus0: SBus0 slot 0xe offset 0x8800000 and slot 0xe offset 0x8810000 Onboard device sparc9 ipl 4
Oct 18 12:43:09 ermis genunix: [ID 936769 kern.info] fas0 is /sbus@1f,0/SUNW,fas@e,8800000
Oct 18 12:43:09 ermis scsi: [ID 193665 kern.info] sd0 at fas0: target 0 lun 0
Oct 18 12:43:09 ermis genunix: [ID 936769 kern.info] sd0 is /sbus@1f,0/SUNW,fas@e,8800000/sd@0,0
Oct 18 12:43:09 ermis scsi: [ID 193665 kern.info] sd1 at fas0: target 1 lun 0
Oct 18 12:43:09 ermis genunix: [ID 936769 kern.info] sd1 is /sbus@1f,0/SUNW,fas@e,8800000/sd@1,0
Oct 18 12:43:09 ermis scsi: [ID 193665 kern.info] sd3 at fas0: target 3 lun 0
Oct 18 12:43:09 ermis genunix: [ID 936769 kern.info] sd3 is /sbus@1f,0/SUNW,fas@e,8800000/sd@3,0
Oct 18 12:43:09 ermis scsi: [ID 193665 kern.info] sd6 at fas0: target 6 lun 0
Oct 18 12:43:09 ermis genunix: [ID 936769 kern.info] sd6 is /sbus@1f,0/SUNW,fas@e,8800000/sd@6,0
Oct 18 12:43:13 ermis swapgeneric: [ID 308332 kern.info] root on /sbus@1f,0/SUNW,fas@e,8800000/sd@1,0:a fstype ufs
Oct 18 12:43:14 ermis sbus: [ID 349649 kern.info] zs0 at sbus0: SBus0 slot 0xf offset 0x1100000 Onboard device sparc9 ipl 12
Oct 18 12:43:14 ermis genunix: [ID 936769 kern.info] zs0 is /sbus@1f,0/zs@f,1100000
Oct 18 12:43:14 ermis sbus: [ID 349649 kern.info] zs1 at sbus0: SBus0 slot 0xf offset 0x1000000 Onboard device sparc9 ipl 12
Oct 18 12:43:14 ermis genunix: [ID 936769 kern.info] zs1 is /sbus@1f,0/zs@f,1000000
Oct 18 12:43:17 ermis sbus: [ID 349649 kern.info] cgsix0 at sbus0: SBus0 slot 0x1 offset 0x0 SBus level 5 sparc9 ipl 9
Oct 18 12:43:17 ermis genunix: [ID 936769 kern.info] cgsix0 is /sbus@1f,0/cgsix@1,0
Oct 18 12:43:17 ermis cgsix: [ID 260993 kern.info] cgsix0: screen 1152x900, single buffered, 1M mappable, rev 11
Oct 18 12:43:17 ermis unix: [ID 270833 kern.info] cpu0: UltraSPARC (portid 0 impl 0x10 ver 0x40 clock 200 MHz)
Oct 18 12:43:17 ermis unix: [ID 270833 kern.info] cpu1: UltraSPARC (portid 1 impl 0x10 ver 0x40 clock 200 MHz)
Oct 18 12:43:17 ermis unix: [ID 721127 kern.info] cpu 1 initialization complete - online
Oct 18 12:43:22 ermis hme: [ID 517527 kern.info] SUNW,hme0 : Sbus (Rev Id = 22) Found
Oct 18 12:43:22 ermis sbus: [ID 349649 kern.info] hme0 at sbus0: SBus0 slot 0xe offset 0x8c00000 and slot 0xe offset 0x8c02000 and slot 0xe offset 0x8c04000 and slot 0xe offset 0x8c06000 and slot 0xe offset 0x8c07000 Onboard device sparc9 ipl 6
Oct 18 12:43:22 ermis genunix: [ID 936769 kern.info] hme0 is /sbus@1f,0/SUNW,hme@e,8c00000
Oct 18 12:43:24 ermis genunix: [ID 454863 kern.info] dump on /dev/dsk/c0t1d0s1 size 513 MB
Oct 18 12:43:26 ermis hme: [ID 517527 kern.info] SUNW,hme0 : Internal Transceiver Selected.
Oct 18 12:43:26 ermis hme: [ID 517527 kern.info] SUNW,hme0 : 100 Mbps Full-Duplex Link Up
Oct 18 12:43:30 ermis pseudo: [ID 129642 kern.info] pseudo-device: devinfo0
Oct 18 12:43:30 ermis genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo@0
Oct 18 12:43:30 ermis pseudo: [ID 129642 kern.info] pseudo-device: laner0
Oct 18 12:43:30 ermis genunix: [ID 936769 kern.info] laner0 is /pseudo/laner@0
Oct 18 12:43:43 ermis inetd[189]: [ID 965992 daemon.error] pop/tcp: unknown service
Oct 18 12:43:46 ermis pseudo: [ID 129642 kern.info] pseudo-device: tod0
Oct 18 12:43:46 ermis genunix: [ID 936769 kern.info] tod0 is /pseudo/tod@0
Oct 18 12:43:47 ermis pseudo: [ID 129642 kern.info] pseudo-device: pm0
Oct 18 12:43:47 ermis genunix: [ID 936769 kern.info] pm0 is /pseudo/pm@0
Oct 18 12:43:55 ermis pseudo: [ID 129642 kern.info] pseudo-device: vol0
Oct 18 12:43:55 ermis genunix: [ID 936769 kern.info] vol0 is /pseudo/vol@0
Oct 18 12:44:04 ermis pseudo: [ID 129642 kern.info] pseudo-device: pm0
Oct 18 12:44:04 ermis genunix: [ID 936769 kern.info] pm0 is /pseudo/pm@0

Hello,
I don't think it is a kernel problem but a h/ware problem.
CPU 1 reported an ecache (sram) data parity event,
the fault handling code in 5.9 can't do anything about the
error as it is in a page belonging to a user process so it reboots the box.
The no error found in ecache means that either the
fault handling code displaced the error from the cache or there
wasn't one and you had a transient transport error between the
cache and the cpu.
I would engage your h/ware support vendor to work out what h/ware component is broken as these things are quite complex, but the score of 95 would (to a h/ware novice like me) point to cpu 1 being the culprit - but check with an expert.
tim

Similar Messages

Sun Ultra 10 with SunStorEDGE A1000/D1000 unable to setup

I realise this covers old ground but I have not been able to trace a uitable resolvement and would be grateful for assistance.
I have a Sun Ultra 10 with 256MB RAM and 440GHz cpu.. It has a pci Adaptec 2944UW HVD SCSI interface card. The storage system is a tray of eight scsi 72GB disks housed in a D1000 case. NetBSD reported it as an A1000 SunStorEDGE at sd0 having 16 targets and 8 luns. However NetBSD did not have a readily available controller to setup the raid system so I installed an alternative. I presume the case is a reused old case housing an A1000 unit.
I tried to format the drives directly but they are not lists as devices such as ct1sd1 etc. and so this is not possible.
I have installed Sun Solaris 10 but could not communicate and reported inability to use rdriver and rdnexus and after reading a number of reports that driver hooks had been removed from the kernel in Solaris 10 I have installed Solaris 9.
On both occasions I installed a number of RAID Manager 6.1.1 control packs, namely SUNWosafw, osar, osau, osamn and vtsse direct from my CD here.
I commanded dr_hotadd.sh to take up the challenge but it failed to communicate.
I added a number of Rdac amendments to rparams in /etc/osa but this did not resolve the issue.
I have tried to call probe-scsi-all after doing a reset-all from the OBP but this fails to report anything. I presume this is because the unit is connected by the interface card rather than a direct scsi disk.
dmesg pipe grep scsi reports:
unknown scsi sd0 at uata0 target 2 lun 0
I would be very grateful fr guidance to resolve this connection so that I can create a suitable filestore.
Thanks
c

blackfoot wrote:
I realise this covers old ground but I have not been able to trace a uitable resolvement and would be grateful for assistance.
I have a Sun Ultra 10 with 256MB RAM and 440GHz cpu.. It has a pci Adaptec 2944UW HVD SCSI interface card. The storage system is a tray of eight scsi 72GB disks housed in a D1000 case. NetBSD reported it as an A1000 SunStorEDGE at sd0 having 16 targets and 8 luns. However NetBSD did not have a readily available controller to setup the raid system so I installed an alternative. I presume the case is a reused old case housing an A1000 unit.If it's really an A1000, you won't have access to the drives. You'll only see exposed LUNS from the raid controller. Do you have a dial in the rear with a scsi address? That will be the address that the A1000 will respond on. In addition, the A1000 has only one pair of SCSI ports. The D1000 has two pair and doesn't have the scsi adress dial (because each of the disks in the chassis respond on their own addresses). Instead you have some DIP switches to change the addressing behavior.
I tried to format the drives directly but they are not lists as devices such as ct1sd1 etc. and so this is not possible.
I have installed Sun Solaris 10 but could not communicate and reported inability to use rdriver and rdnexus and after reading a number of reports that driver hooks had been removed from the kernel in Solaris 10 I have installed Solaris 9.That's fine. You can ignore them. Neither the A1000 nor D1000 require those drivers. You should still be able to use 'rm6' or the CLI tools to interact with an A1000.
On both occasions I installed a number of RAID Manager 6.1.1 control packs, namely SUNWosafw, osar, osau, osamn and vtsse direct from my CD here.
I commanded dr_hotadd.sh to take up the challenge but it failed to communicate.
I added a number of Rdac amendments to rparams in /etc/osa but this did not resolve the issue.
I have tried to call probe-scsi-all after doing a reset-all from the OBP but this fails to report anything. I presume this is because the unit is connected by the interface card rather than a direct scsi disk.If the controller doesn't support the OBP environment, then yes, you won't see anything then.
dmesg pipe grep scsi reports:
unknown scsi sd0 at uata0 target 2 lun 0So that might be a single LUN from an A1000 controller. If the selector switch in the back is set to '2', then it's even more likely.
Darren

Parallel port programming for a Sun Ultra 5 running Solaris 8

Hi I'm trying to look for information about reading/writing to the parallel port of a Sun Ultra 5 running Solaris 8. I'd just like to see some basic programs written in C, nothing fancy, just reading and wrting to the port, getting the port address etc. toggling the lines.
I've tried searching for this information and there is plenty of information about PC parallel port programming with windows or Linux. But there seems to be little for Sun's
I've tried doing 'man ecpp' but that doesn't really give any clear example. What I need is an idiots guide.
I've tried searching this Forum and I see that other people have asked the same question before but no one has replied to them. Why is this?
Thanks if you can help.
fishman.

The key is gettting the port into diag mode. Here's a quickly little example that turns all the data pins on and then turns them off:
#include <sys/types.h>
#include <sys/conf.h>
#include <sys/stat.h>
#include <unistd.h>
#include <stropts.h>
#include <fcntl.h>
#include <stdio.h>
#include <sys/ecppio.h>
int fd = 0;
// ecpp structures
ecpp_transfer_parms etp;
ecpp_regs eregs;
// returns -1 if error otherwise returns fd
int openoutput()
fd = open("/dev/ecpp0",O_RDWR);
if (fd==-1) { return -1; }
// default is 90
etp.write_timeout = 10;
// the big secret
etp.mode = ECPP_DIAG_MODE;
ioctl(fd,ECPPIOC_SETPARMS,&etp);
return fd;
unsigned char in()
unsigned char data;
// from the man pages
ioctl(fd,ECPPIOC_GETREGS,&eregs);
data = eregs.dsr;
return data;
void out( unsigned char data )
write(fd,&data,1);
int main( void )
int dummy;
openoutput();
//all data pins on
out( 255 );
scanf("%d", &dummy);
//all data pins off
out( 0 );
scanf("%d", &dummy);
close( fd );
return 0;
}

Can not use SVM disc mirror on Sun X2200 M2 with solaris u7

Last year,I tried to build cluster with solaris u6, but I got this error "Insufficient metadevice database replicas located" after SVM set up.
I tried lastest solaris 10 u7(09/05) with Sun x2200 M2 server again, but I got the same error.
I think it maybe driver's problem,so I tested solaris 10 u7 again with one old x86 machines and this machines has pure scsi card and scsi disc.
Also I tried it with ide drive, and everything is fine without any error message.
I checked that solaris 10 u5 will consider sata disc on x2200 m2 as ide disc, so SVM works fine.
But after I upgrade to solaris 10 u7,system will consider sata disc as scsi drive, and SVM will not work.
So I can see this is a bug of solaris 10 u7?
Edited by: cheung79 on 2009/7/3 ?? 11:04

-bash-3.00# metadb -i
flags first blk block count
a m p lu 16 8192 /dev/dsk/c0t0d0s7
a p l 8208 8192 /dev/dsk/c0t0d0s7
a p l 16400 8192 /dev/dsk/c0t0d0s7
M u 16 unknown /dev/dsk/c0t1d0s7
M u 8208 unknown /dev/dsk/c0t1d0s7
M u 16400 unknown /dev/dsk/c0t1d0s7
r - replica does not have device relocation information
o - replica active prior to last mddb configuration change
u - replica is up to date
l - locator for this replica was read successfully
c - replica's location was in /etc/lvm/mddb.cf
p - replica's location was patched in kernel
m - replica is master, this is replica selected as input
W - replica has device write errors
a - replica is active, commits are occurring to this replica
M - replica had problem with master blocks
D - replica had problem with data blocks
F - replica had format problems
S - replica is too small to hold current data base
R - replica had device read errors
I don't have "set md:mirrored_root_flag=1" line in /etc/system.
Do you mean boot device is scsi hdd? but it is sata hdd.
-bash-3.00# ls -l /dev/rdsk/c0t0d0s0
lrwxrwxrwx 1 root root 51 Jul 7 17:55 /dev/rdsk/c0t0d0s0 -> ../../devices/pci@0,0/pci108e,534b@5/disk@0,0:a,raw

Can't suspend Ultra 25 with Solaris 10

Folkses,
i try to suspend my machine with gnome-sys-suspend and get the following error:Apr 18 15:43:40 obelix2 cpr: System is being suspended
Apr 18 15:45:29 obelix2 cpr: WARNING: Could not stop "ufsreclaim" kernel thread. Please try again later.
Apr 18 15:45:41 obelix2 cpr: NOTICE: Suspend operation failed.
Apr 18 15:45:41 obelix2 cpr: System has been resumed.and obviously the system doen't suspend.
any ideas, what the means, why this is?
thomas

Hello,
You can use kdmconfig.
Let me know if it solved your issue. I have the same problem with solaris 10 b72... JDS cannot be loaded, and I come back to the login screen. But no problem with CDE.

NIC on Ultra 10 with Solaris 10 not running

Hi,
I have a couple of Old Ultra 10's. I've installed Solaris 10 on both of them. I tried to give them a point to point connectivity using a Cross-over cable. But, when I do a ifconfig -a on both of them, I get it as
<UP, BROADCAST, MULTICAST> MTU ...... if you noticed here, I did not get them as RUNNIING. I have given them private IP's 192.168.1.1 and .2 and they are both on 255.255.255.0. I have them both plumbed and up with the above IP and netmasks. but they do not ping each other. I wonder where I am wrong. Can somebody gimme a insight into this, as to what has to be done to rectify this problem. One of them had the MTU value as 8232 and the other one at 1500 so, I gave the one with 8232
# ifconfig hme0 mtu 1500
1. Are the IPs correct ?
2. Are the net mask values set right ?
3. Should any of the files need to be updated?
4. what about the /etc/defaultrouter does this have to do anything with the servers not pinging each other ?
5. Does the NIC driver need an update for Solaris 10 ? If so can you pls specify the link for me to download ?
Advice Pls.
David

I've had tremendous trouble in the past with making crossover ethernet cables function properly on some Ultra 10 machines. As far as I'm aware, it should have the same hardware as other Sun models, but that's the only one I've had real problems with.
I've had several jumpstart setups that failed until I was able to bring in a hub or switch instead of working them back-to-back.
So no direct help from me, I'm afraid. But it could just be the hardware. Use 'kstat' (or the ndd method) to check if the link is up. No link, no traffic. Until that happens your questions 1-4 are irrelevant. Question 5 is a good one, but no, Solaris 10 would include the hardware drivers. And for equipment as old as the Ultra 10, I'm guessing there haven't been many recent updates.
Darren

Wireless PCI for Sun Ultra 24?

Hi
I'm trying to find a wireless PCI card with appropriate drivers for Sun Ultra 24 with Solaris 10 8/07.
Can anyone recommend cards that have been validated with this machine / OS combination?
Help appreciated
Lance

Hello Lance,
have you reviewed the following page ?
Solaris Ready WIFI Products
http://www.sun.com/io_technologies/wifi/WiFi0.html
Michael
Edited by: MAAL on 27.06.2008 07:10
Adding a link didn't work as expected ...

Solaris 2.6 upgrade to version 8 on SUN ULTRA 10

Dear Mr. or Mrs:
I met the same question as uxdms who left the message on Dec 20,2001.
When I was trying to upgrade from solaris 2.6 to 8 release , there is "failed" warning and the upgrade isn't created.
There is a detailed info:
Mechine: SUN ULTRA 10
Media:
Solaris 8 installation -- SPARC Platform Edition
Solaris 8 software 1 of 2 -- SPARC Platform Edition
Solaris 8 software 2 of 2 -- SPARC Platform Edition
Installation step:
Accordidng to the guide of installation, run step by step,
and there are some special steps below:
(1) use the /dev/dsk /c0t0d0s4 as disk slice to upgrade.
(2) selet networked
(3) don't use DHCP
(4) disable IPv6
(5) no NIS+, NIS, DNS ..
.... displaying the wolcome to solaris dialog box
(1) Solaris 8 installation SPARC Platform Edition is ejected.
(2) prompted to insert the Solaris 8 software 1 of 2.
(3)After selecting serial the dialog box of the upgrade..
(4)system prompted upgrading...
initialation is done.
Checking file system is done.
(5) There is a installation summary displayed:
installation summary
The solaris installation status is shown below
product status infor.
Solaris 8 software Failed Detailed(button)
After click the Detailed button, there is a dialog box
Failed:
Log file: /a/var/sadm.system/logs/upgrade_log
Question is:
I can't find the file of upgrade_log , and the webstart install stops on it.
I appreciate for your kind help
Melanie
the webstart install stops on initalization -- with 'failed' warning

Hi,
If this problem is reproduceable, provide me the exact console error (failed) message to further investigate on this issue.
Senthilkumar
Developer Technical Support
Sun Microsystems, Inc.
http://www.sun.com/developers/support

Sun DS 5.2 p3 with Solaris 10

I've been trying to test out using LDAP to replace NIS.
My setup is a Sun Sparc box with Solaris 10 running
Sun One Directory 5.2 patch level 3. I have two x86_64 client
machines; one running Red Hat 4 and the other Solaris 10.
I have been able to authenticate on the RH 4 machine
with no problems, but have been unable to on the
Solaris 10 machine. I'm using Sun's native LDAP
client tools.
I've tried configuring the DS for anonymous access
to proxy access with simple authentication, but neither
one seems to matter.
I've copied over the pam.conf example provided by Sun
today, but it still doesn't seem to work. I can do a
"getent passwd" on the RH 4 and get all the local accounts
and the test one in the LDAP server. If I try that on the
Sun box I only get the local accounts, however if I
do a "getent password testuser" on the Solaris 10 box,
then I get the right account info. It looks like I can even
see the passwords, which are stored using md5; not
crypt, if that matters.
I'm tried searching for more info, but it doesn't appear
that DS 5.2 has been used too much on Solaris 10;
nor does Gary Tay's great documentation cover
Solaris 10. Is there something obvious I'm missing?
I can't believe it would be this hard to set LDAP up
with just Sun software.

See related posts:
http://www.sunmanagers.org/pipermail/summaries/2005-August/006688.html
1) make sure /etc/nsswitch.conf has this entry in it:
ipnodes: files
2) must run these commands as root:
crle -u -s /usr/lib/mps
crle -64 -u -s /usr/lib/mps/64
Other than that I didn't need to do anything different than solaris 9.
I did have to run this command on occasion though:
svcadm enable svc:/network/ldap/client:defaulthttp://forum.sun.com/thread.jspa?forumID=271&threadID=25523
Gary

Sun Ultra 40 Suppl. CD V1.3 Bios + SLi Broadcast Aperture + Nvidia 91.29

I am using a Sun Ultra 40 with dual Opteron and dual Quadro FX 4500 in SLi-Configuration.
I just upgraded the Bios to the new release V1.3 and I just noticed an entry inside the Bios regarding the "SLi Broadcast Aperture". Following values are possible:
1. Disabled
2. SLi on Master
3. SLi on Slave
What is the recommended value for my system in order to maximize the performance? I assume the master is the first graphics card, but I would like to know the correct value.
Another issue I found out with the newest supplied Graphics driver on the supplemental CD by Sun (Nvidia V91.29), after startup the driver recognizes the sysem as an SLi-System but by enabling the SLi-support it is stated that the system does not have two identical graphics cards and SLi stays disabled. With the older driver on the supplemental CD V1.2 everything works fine. I have the doubt, that Sun was slightly to fast by releasing this driver?!
Anyhelp is more than welcome/needed and appreciated! For anybody intrested, the Sun Ultra 40 is an awesome system and for any heavy workload in CAD first choice!

Both of these problems are now documented on the X2100 server release notes (which wasn't the case when I originally posted the topic).
http://www.sun.com/products-n-solutions/hardware/docs/html/819-3722-15/
The problem with sharing the bge0 port between Solaris and the IPMI is a bug in the bge driver, fixed by patch 122028-02.
The problem with the bmc driver was more mysterious. Finally a note ("Adding SMDC Card Requires BIOS Flash") was added to the release notes web page. I had already upgraded my BIOS to the latest (1.1.1) revision, but re-flashing with the /cd switch as detailed in the note and performing a reconfiguration boot of Solaris fixed the problem.

Sunpci2 with solaris 10

Hello everybody!
I have following question please:
I am working on a Sun Blade 100 with Solaris 10. In this blade a SUNpci2 card exists.
So, is it possible to use this card? I tried SUNWspci2 (2.3), but I got some errors. I tried to patch it, but it does not work. Or have I to downgrade on solaris 8?
Could please be anyone so kind, and help me?
Thanks in advance,
Gerald

All you're going to get is suggestions for, and pointers to, work-arounds.
The SunPCi2 card is not a supported peripheral under Solaris 10(SPARC).
It's not supposed to work, though the modifications shown by Michael seem to succeed.
If you have the time to experiment...
Install Solaris 9 and then install the coprocessor board and its software.
(Solaris downloads are here)
Observe whatever you need to do to get it working.
Then go back to these work-arounds and edit whatever you need to do for Solaris 10.

Sun Ultra 40

Has anyone gotten dual-display to work with a Sun Ultra 40 with Red Hat Enterprise Linux AS 4.0? The dual-display works when booting and shutting down but doesn't work in normal operation when the machine is booted. I've tried both the nvidia driver that comes on the disc with the machine and the latest driver from Nvidia's website.
Any help would be my appreciated.
mike

The best option is to contact Sun support ( or Red Hat if your contract is with Red Hat ), the systems GA date was Feb. 14 and at this time there is limited InfoDocs and SRDBs.

Unable to install Solaris Sparc 10 on SUN Ultra 10

Downloaded ISO of SPARC 10 DVD from Oracle site, burnt it and tried to install on SUN Ultra 10 (300 MGz / 256 MB RAM / 80 GB IDE HDD)
Followed the process as specified below:
1. Stop+A to stop the current boot process.(Already SPARC 8 is installed)
2. AT OK prompt typed boot cdrom
3. After some time (3-5 min) prompting error
*"boot device: /pci@1f,0/pci@1,1/ide@3/cdrom@2,0:f File and args:*_
Panic - Kernel : kmem64 allocation failure+_
Program Terminated+_
ok "+_
Checked in few blogs and burnt another DVD with less writing speed, still same error.
Checked with Sparc 8 CD's, Sparc 5.8 installing without any errors.

985393 wrote:
... (300 MGz / 256 MB RAM / ) ...I suggest you forget about trying Solaris 10 on a system with such limited resources.
If I recall correctly, Solaris 10 needs a minimum of 768MB of RAM to install and 1GB or more of RAM to run, even if you had a cpu that was fast enough to run anything.
Perhaps consider it this way:
Would you even dream of trying to install MS Windows 7 on a Pentium-I at 300MHz?
Stay with your Solaris 8. It's from the same late 1990's era as that hardware and fits it just right.

Hard disk problem after installing Solaris 10 u5 on a Sun Ultra 24

Hi.
After receiving a new Sun Ultra 24, shipped with Solaris 10 u4, the first thing I did was installing Solaris 10 u5. X wouldn't start but that was not a big problem and installed it in text mode. Installation went fine but, when the system starts, a single beep is heard and after some seconds some warning message appear on the console, before the "Hostname: ..." message, informing that some read operation on my hard disk had timed out and were aborted. The system then starts up normally. The only other anomaly is that the diagnostic partition in unbootable.
I ran the hard disk tests from the tools and drivers CDs and all of the tests were passed. Solaris 10 u4 was working normally so I'm wondering if this may be a bug.
Thanks for your help,
Enrico.

Thanks anyway, I discovered what the problem was: a bug in Solaris 10 u5:
http://opensolaris.org/jive/thread.jspa?threadID=58768&tstart=75
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6536722
Thanks,
Enrico

How to install Solaris 10 on sun ultra enterprise 450

I just got a used sun ultra enterprise 450 and need to get a username and password. If I cannot get easily how do I reinstall the OS. What OS can I put on its? I am new to some equipment. It also came with a a storage unit for extra hard drives and how would I use it and set it up also?
It now says type ctrl-d. What do I do?
http://www.unix.com/sun-solaris/114206-how-get-root-password-how-install-sun-os.html
http://www.linuxquestions.org/questions/solaris-opensolaris-20/how-to-install-solaris-10-on-sun-ultra-enterprise-450-739614/

This same question was cross-posted to another forum site
[http://www.linuxquestions.org/questions/solaris-opensolaris-20/how-to-install-solaris-10-on-sun-ultra-enterprise-450-739614/|http://www.linuxquestions.org/questions/solaris-opensolaris-20/how-to-install-solaris-10-on-sun-ultra-enterprise-450-739614/]
with the same unintelligible drivel.
O.P.
Go to Docs.Sun.Com and get the system's documentation. Also go get the OBP 3.x Command Reference manual while you are there. All you questions are answered in that documentation, except for those that are easily found with Google.
[Example of a Google search for your question.|http://www.google.com/#hl=en&q=solaris+root+password&aq=f&oq=&aqi=g9&fp=KxYPMM6r3XA]

SUN Ultra-2 with Solaris 9 constantly self reboots

Similar Messages

Maybe you are looking for