01-09-2004
Xserver won't come up on Solaris 8
Hi all,
My Ultra 10, running Solaris 8, is giving me problems
Currently, whenever it boots, the Xserver will not come up, saying "Xserver cannot be started on display 0".
I thought this might have something to do with OWconfig, and so poked it a little (moving params onto different lines), and so now it kinda gets halfway there... The display flicks between black-on-white console login, and white-on-black with eggtimer as mouse pointer..
Anyone experienced anything like this before, or have any ideas?
Thanks
Gemma
10 More Discussions You Might Find Interesting
1. Solaris
Hi,
I've just bought an Ultra 60 running solaris 9 (or so I've been led to believe). When I start up, it looks for a (presumably) domain/network to hook up to and the following messages are displayed:
Boot device: net file and args:
Network link setup failed
Please check cable and try... (3 Replies)
Discussion started by: alarmcall
3 Replies
2. UNIX for Dummies Questions & Answers
I have just installed Solaris 10 x86 version on a Compaq Evo desktop station with a Sun 19" SVGA monitor model # CM751U. The desktop has 256MB RAM. The video card is a nVidia Riva TNT2 64. If I do a scanpci command; it returns the card as a nVidia Corporation NV6 (Vanta/Vanta LT)
The Xserver... (1 Reply)
Discussion started by: sjteng
1 Replies
3. UNIX for Advanced & Expert Users
Hi,
From my workstation (win XP)I open a telnet session on Linux(Red Hat) server.
When I issue :
# xclock
I have :
Error: Can't open display:
Then :
# export DISPLAY=192.16.1.87:0.0
# xclock
Error: Can't open display: 192.16.1.87:0.0
Do you have an idea ?
Many thanks. (6 Replies)
Discussion started by: big123456
6 Replies
4. Solaris
I have problem with my V490 server which running on solaris 8. The error show on log file
X_mkdir: nosuch file or directory
Fatal server error:
Failed to establish all listening sockets
error (pid 299): server unexpectedly died
error (pid 299): server for display :0 cant be started
... (1 Reply)
Discussion started by: shamsul
1 Replies
5. Solaris
Hi
I am trying to debug an issue with an automated install I have set-up. So to start I just ran a simple
ok; boot cdrom - install
but when it came to the IP address field it would only take the following format 123.123.123.12 and would not let me enter the last digit
Anybody got any... (9 Replies)
Discussion started by: eeisken
9 Replies
6. AIX
Hello:
NOOB here. I attempted to use smit mkcd. Failed on first attempt, not enough space. 2nd attempt tried to place iso on /usr, not enough space there. Cleanup ran for about 5 minutes after aborting. Now AIX won't boot. LCD display on 7029-6E3 says: 0517 MOUNT /USR. Attempted to boot from CD... (11 Replies)
Discussion started by: bbird
11 Replies
7. Solaris
Hi all,
I've somehow gained the idea that I _need_ to run at least 1 box with Solaris, but things don't go as I had planned :-)
I pulled this ancient IBM eserver xseries 305 out of the dust, and got myself a fresh copy of the required cd's for Solaris 10u7. FAIL, for some reason the box and the... (7 Replies)
Discussion started by: mr.aart
7 Replies
8. Solaris
This is the error message that I am getting on a Solaris 10 sparc server
scsi: no major number
cannot load drivers for /pci@400.....
Can't load the root filesystem
Type 'go' to resume
{0} ok
Is there a way for me to correct this issue. It looks like I am missing a scsi driver to boot up... (5 Replies)
Discussion started by: trinityforce
5 Replies
9. Solaris
Hello guys,
I am a newbie. Just freshly installed Solaris 11. When I try to type for example root@t1000:~# man zpool It says bash: man: command not found. It used to show manual pages before installation. Any help is appreciated. Thanks. (5 Replies)
Discussion started by: nazimbilir
5 Replies
10. UNIX for Beginners Questions & Answers
Can anyone offer any advice on how to modify the script below to work on a new system we have, that has no graphics capability? We admin the system through a serial RAS device. I've tried running the below script through the RAS and through an ssh -X session. It failed with something like "GTK... (3 Replies)
Discussion started by: yelirt5
3 Replies
LEARN ABOUT NETBSD
iteconfig
ITECONFIG(8) BSD System Manager's Manual ITECONFIG(8)
NAME
iteconfig -- modify console attributes at run time
SYNOPSIS
iteconfig [-i] [-f file] [-v volume] [-p pitch] [-t msec] [-w width] [-h height] [-d depth] [-x offset] [-y offset] [color ...]
DESCRIPTION
iteconfig is used to modify or examine the attributes of the console bell and bitmapped console display. The console bell's volume, pitch,
and count may be specified, as well as the bitmapped display's width, height, horizontal and vertical offset, pixel depth, and color map.
The following flags are interpreted by iteconfig:
-i After processing all other arguments, print information about the console's state.
-f Open and use the terminal named by file rather than the default console /dev/ttye0.
-v Set the volume of the console bell to volume, which must be between 0 and 63, inclusive.
-p Set the pitch of the console bell to pitch, which must be between 10 and 1399.
-t Set the duration of the beep to msec milliseconds which must be between 1 and 5000 (5 seconds).
-w Set the width of the console display to width pixel columns. Width must be a positive integer.
-h Set the height of the console display to height pixel rows. Height must be a positive integer.
-d Set the number of bitplanes the console view should use to depth. For example, if depth is 3 then 8 colors will be used.
-x Set the horizontal offset of the console view on the monitor to offset pixel columns. The horizontal offset may be a positive or a
negative integer, positive being an offset to the right, negative to the left.
-y Set the vertical offset of the console view on the monitor to offset pixel rows. The vertical offset may be a positive or a negative
integer, positive being an offset down, negative up.
Any additional arguments will be interpreted as colors and will be used to supply the color values for the console view's color map, starting
with the first entry in the map. (See the COLOR SPECIFICATION section of this manual page for information on how to specify colors.) If
more colors are supplied than are usable by the console view, a warning is printed and the extra colors are ignored.
COLOR SPECIFICATION
Colors are hexadecimal numbers which have one of the following formats:
0xRRGGBB RR, GG, and BB are taken to be eight-bit values specifying the intensities of the red, green and blue components, respectively, of
the color to be used. For example, 0xff0000 is bright red, 0xffffff is white, and 0x008080 is dark cyan.
0xGG GG is taken to be an eight-bit value specifying the intensity of grey to be used. A value of 0x00 is black, a value of 0xff is
white, and a value of 0x80 is a grey approximately half way in between.
0xM M is taken to be the one-bit monochrome value to be used. A value of 0x1 is black, and a value of 0x0 is white.
BUGS
The iteconfig command is only available on the amiga and atari ports.
BSD
February 3, 1994 BSD