03-17-2004
Check to see if /dev/fb is linked to anything - if not, you can set it up but may have a problem with booting into multi-user mode.
First, check what output-device is equal to in the output of the eeprom command.
(Save the output as you might need it later - best to save it in a file on another system).
Shutdown the system, setenv output-device screen. Boot -sr to reconfigure into single user mode. This should create your /dev/fb. Shutdown and setenv output-device back to original setting.
Reboot and see if you can now start up X-applications.
10 More Discussions You Might Find Interesting
1. Solaris
I am currently setting up rdiff-backup to use ssh to connect and remotely backup and retrieve data. I am doing so by creating rsa keys for each server and copying the relevant key to the /.ssh folder on the relevant server.
All seems to work well when severs running solaris 8 with ssh 3.6.1 are... (6 Replies)
Discussion started by: falklandtim
6 Replies
2. Solaris
Good Day,
I've remotely mounted a cdrom (no problems theere). The kicker is I can see the directories on the remote CD bout I can't see the files. What am I doing wrong? I'm logged in as root on both systems. All the permissions seem okay - what am I missing? Thanks (2 Replies)
Discussion started by: greg69
2 Replies
3. Solaris
Hi All
I have a Solaris 10 jumpstart boot/config server set up on a subnet, and am trying to use it to build a client (the only other machine on the network). Things start out just fine, with the client booting into the Solaris Installation program, but then it just coredumps just as it's... (4 Replies)
Discussion started by: rickedwards44
4 Replies
4. Solaris
Morning all,
I am attempting to load a package from a Solaris 8 CDROM.
This fails with the error :
"pkgadd: ERROR: unable to access pkgmap file </cdrom/ .........../SUNWlibC/pkgmap>
No changes were made to the system"
Any help would be appreciated
Andy (6 Replies)
Discussion started by: AndyD
6 Replies
5. Solaris
version of solaris: SunOS 5.8 Generic-117350-39 sun4u sparc SUNW,Netra-240
version of SSH: OpenSSH_4.4p1, OpenSSL 0.9.8d 28 Sep 2006
Task:
I need to have another Machine ssh into my machine, by either RSA authentication or username/pass authentication.
History:
In the begining my... (4 Replies)
Discussion started by: EWTGPAC
4 Replies
6. Solaris
Greetings Forumers!
I've been fighting a locale problem on a v490 running Solaris 10 u4 (8/07). When I login to the system, I get several "locale" error messages:
user1's password:
Last login: Wed May 26 2010 09:14:13 -0400 from system1
You have mail.
couldn't set locale correctly
couldn't... (0 Replies)
Discussion started by: bluescreen
0 Replies
7. Solaris
Hi,
I am unable to login into my terminal hosting Solaris 10 and get the below error message
"Server refused to allocate pty
ld.so.1: sh: fatal: libc.so.1: open failed: No such file or directory "
Is there anyways i can get into my machine and what kind of changes are required to be... (7 Replies)
Discussion started by: sankasu
7 Replies
8. Solaris
Hi, It's a Solaris 10 zone. I can ssh to other systems without problems, but can not ssh to it (output attached). I don't think there is a firewall here. /etc/ipf/ipf.conf contains nothing.
What could be the problem cause? Please help. Thank you in advance!
sshclient$ ssh -v thiserver... (1 Reply)
Discussion started by: aixlover
1 Replies
9. Solaris
Got a strange problem.
I have 4 Solaris servers all configured the same, Solaris 10 x86 update 10.
When I try to ssh from one Solaris 10 server to another server ssh hangs.
I have an identical server and when I try this everything works fine.
The weird thing is if I am root on the server... (1 Reply)
Discussion started by: ccj4467
1 Replies
10. AIX
Hi all
With the recent virus attacks we have been tasked with upgrading Samba to a "secure" version. Currently running 3.0.29a and looking to put the latest version down 4.6.5.
Being a lazy bod I have only ever installed this, a long time ago, when you could get it in BFF filesets. Have... (6 Replies)
Discussion started by: splattty
6 Replies
REBOOT(8) System Manager's Manual REBOOT(8)
NAME
reboot - stopping and restarting the system
SYNOPSIS
/sbin/reboot [ -lqnhdarsfRD ]
/sbin/halt [ -lqndars ]
/sbin/fastboot [ -lqndarsRD ]
DESCRIPTION
2.11BSD is started by placing it in memory at location zero and transferring to its entry point. Since the system is not reentrant, it is
necessary to read it in from disk or tape each time it is to be boot strapped.
Rebooting a running system: When the system is running and a reboot is desired, shutdown(8) is normally used to stop time sharing and put
the system into single user mode. If there are no users then /sbin/reboot can be used without shutting the system down first.
Reboot normally causes the disks to be synced and allows the system to perform other shutdown activities such as resynchronizing hardware
time-of-day clocks. A multi-user reboot (as described below) is then initiated. This causes a system to be booted and an automatic disk
check to be performed. If all this succeeds without incident, the system is then brought up for multi-user operation.
Options to reboot are:
-l Don't try to tell syslogd(8) what's about to happen.
-q Reboot quickly and ungracefully, without shutting down running processes first.
-n Don't sync before rebooting. This can be used if a disk or the processor is on fire.
-h Don't reboot, simply halt the processor.
-d Dump memory onto the dump device, usually part of swap, before rebooting. The dump is done in the same way as after a panic.
-a Have the system booter ask for the name of the system to be booted, rather than immediately booting the default system (/unix).
-r Mount the root file system as read only when the system reboots. This is not supported by the kernel in 2.11BSD.
-s Don't enter multi-user mode after system has rebooted - stay in single user mode.
-f Fast reboot. Omit the automatic file system consistency check when the system reboots and goes multi-user. This is accomplished by
passing a fast reboot flag on to the rebooting kernel. This currently prevents the use of -f flag in conjunction with the -h (halt)
flag.
-D Set the autoconfig(8) debug flag. This is normally not used unless one is debugging the autoconfig program.
-R Tells the kernel to use the compiled in root device. Normally the system uses the device from which it was booted as the
root/swap/pipe/dump device.
Reboot normally places a shutdown record in the login accounting file /usr/adm/wtmp. This is inhibited if the -q or -n options are
present. Note that the -f (fast reboot) and -n (don't sync) options are contradictory; the request for a fast reboot is ignored in this
case.
Halt and fastboot are synonymous with ``reboot -h'' and ``reboot -f'', respectively.
Power fail and crash recovery: Normally, the system will reboot itself at power-up or after crashes if the contents of low memory are
intact. An automatic consistency check of the file systems will be performed, and unless this fails, the system will resume multi-user
operations.
SEE ALSO
autoconfig(8), sync(2), utmp(8), shutdown(8), syslogd(8)
3rd Berkeley Distribution May 24, 1996 REBOOT(8)