The error you see could be the result of many, many things.
It would help to know a description of what you have and what are the system circumstances:
Did this configuration <i>ever</i> work properly, or are you trying this for the very first time?
What distribution of the OS did you install? [ Core, Developer, etc, etc ]
What Sun video adapter is installed to the system?
Are the correct framebuffer packages installed?
What settings do you have for the input-device and the output-device?
(you can run <u>printenv</u> from OBP or you can run <u>eeprom</u> from the OS)
You do have your Sun mouse plugged into the keyboard ?
and then you have your Sun keyboard directly connected to the system?
What keyboard and which mouse are you using?
What desktop? CDE or GNOME?
It sounds like a path issue? From the command line login add the following lines to end of /etc/profile
PATH=/usr/local/bin:/usr/bin:/usr/openwin/bin:$PATH
LD_LIBRARY_PATH=/usr/local/lib:/usr/lib:$LD_LIBRARY_PATH
export PATH LD_LIBRARY_PATH
Hi
I cn't this b'coz customer didn't able to give the solution this one whether it is working fine or not from very first time
this eeprom output
keyboard-click?=false
keymap: data not available.
ttyb-rts-dtr-off=false
ttyb-ignore-cd=true
ttya-rts-dtr-off=false
ttya-ignore-cd=true
ttyb-mode=9600,8,n,1,-
ttya-mode=9600,8,n,1,-
pcia-probe-list=1,2
pcib-probe-list=1,3,2,4,5
enclosure-type=540-4284
banner-name=Sun Enterprise 220R
energystar-enabled?=false
mfg-mode=off
diag-level=min
#power-cycles=72
system-board-serial#=5015606185164
system-board-date=3d202135
fcode-debug?=false
output-device=screen
input-device=keyboard
load-base=16384
boot-command=boot
auto-boot?=true
watchdog-reboot?=false
diag-file: data not available.
diag-device=net
boot-file: data not available.
boot-device=disk:a disk net
local-mac-address?=false
ansi-terminal?=true
screen-#columns=80
screen-#rows=34
silent-mode?=false
use-nvramrc?=false
nvramrc: data not available.
security-mode=none
security-password: data not available.
security-#badlogins=0
oem-logo: data not available.
oem-logo?=false
oem-banner: data not available.
oem-banner?=false
hardware-revision: data not available.
last-hardware-update: data not available.
diag-switch?=false
yes keyboard and mouse are connected directly to server as well as they SUN keyboard & mouse
With Regards
OK, <i>Min2</i>, that's a beginning.
Are you the administrator, or is this the customer's system?
Have you tried the path modification suggested by <i>Error</i> ?
We still do not know the rest of the hardware config.
Can you successfully log in using command-line only?
That would rule out a bad keyboard, but would not rule out a bad mouse, and you need both before a GUI will work.You would need to wait for the next shutdown, to replace the mouse.
login into the command line as root
1. /etc/init.d/dtlogin stop
2 try cleaning up temp files in /usr/tmp/wscon*
3. /etc/init.d/dtlogin start
4. logout , then log back into dtlogin
if that does not work repeat the same process but before you log back out, remove the:
rm -r $HOME/userid/.dt*
.Xauthority
and logout and logback in
look in the bug database on Sunsolve.sun.com, if your can not find one then submit a ticket for the bug, after you have applied the recommended Solaris paches if possable.