Solaris 10 x86 X-server can not be started on display :0

Solaris 10 x86 X-server can not be started on display :0

Post by Jo » Sat, 10 Jul 2004 09:30:53



Hello:

I installed the Solaris express (S10 build 58 6/04) a couple of days
ago.
I was using the XFree86 to finish the initial installations.
After 2 reboots, it shows "X-server can not be started on display:0"
on monitor and keyboard doesn't respond thereafter.  Notice, the first
reboot came back with CDE without problems.  The screen blinks 4 times
before showing "The X-server can not be started on display :0.

After this happened, I reinstalled once again and set up a user
account so that I can telnet/ssh to it from other boxes without the
need of X windows.

I have checked many postings and checked /var/dt/Xerrors and
/var/log/XFree86.0.log as many suggested.  No hardware changes
happened between working and non-working X windows.  The only
eye-catching thing is "ioctl (kbd type): invalid argument" constantly
showing up.

kdmconfig has the following:

  Current Window System Configuration:

         Video Device: XF86-SIS SiS6326, SiS530, 5597/5598
          Screen Size: 17-inch (43cm)
    Resolution/Colors: 1024x768 - 65536 colors @ 70Hz

         Monitor Type: MultiFrequency 56kHz (up to 1280x1024
interlaced)

        Keyboard Type: Generic US-English(104-Key)

      Pointing Device: Built-in PS/2 Mouse (3 Button)

The above appears to be correct.

The only thing I can see more obvious to the problem is the keyboard
complaints.

Can anyone provide some insights?

Thanks in advance!

/var/dt/Xerrors:
----------------

(EE) screenInfo.numScreens = 1
(==) Log file: "/var/log/XFree86.0.log", Time: Thu Jul  8 17:23:08
2004
(EE) PreInit done
KIOCTYPE: Invalid argument
ddxSUNWkbd: Keyboard type ioctl KIOCTYPE failed on /dev/kbd

Fatal server error:
failed to initialize core devices

                                     ^Hrun-level
6^A63\255\321\366\231\354@^Hrc2s2\^H\255\321^D\226\354@^Hrc3s3<^A^H\
255\321 \226\354@^Hsacsc\200^A^H^O\255\321\366\231\354@^HLOGINcoconsole\201^A^H^
O\255\321\366\231\354@^HzsmonPM10\203^A^Fee
\226\354@\321rootdtconsoleh^D^H\276\321\366\231\354@^C:0\321cah4pts/4J^B^H^D^H\3
12\226\354@^O^L`\3210b^D^H^AXIO:  fatal IO error 146 (Connection
refused) on X s
erver "unix:0.0"
      after 0 requests (0 known processed) with 0 events remaining.
XIO:  fatal IO error 146 (Connection refused) on X server "unix:0.0"
      after 0 requests (0 known processed) with 0 events remaining.

Wed Jul  7 18:02:04 2004
error (pid 351): Server for display :0 terminated unexpectedly 1
(EE) screenInfo.numScreens = 1
(==) Log file: "/var/log/XFree86.0.log", Time: Wed Jul  7 18:02:04
2004
(EE) PreInit done
KIOCTYPE: Invalid argument
ddxSUNWkbd: Keyboard type ioctl KIOCTYPE failed on /dev/kbd

Fatal server error:
failed to initialize core devices

Wed Jul  7 18:02:05 2004
error (pid 351): Server for display :0 terminated unexpectedly 1
(EE) screenInfo.numScreens = 1
(==) Log file: "/var/log/XFree86.0.log", Time: Wed Jul  7 18:02:05
2004
(EE) PreInit done
KIOCTYPE: Invalid argument
ddxSUNWkbd: Keyboard type ioctl KIOCTYPE failed on /dev/kbd

Fatal server error:
failed to initialize core devices

Wed Jul  7 18:02:07 2004
error (pid 351): Server for display :0 terminated unexpectedly 1
(EE) screenInfo.numScreens = 1
(==) Log file: "/var/log/XFree86.0.log", Time: Wed Jul  7 18:02:07
2004
(EE) PreInit done
KIOCTYPE: Invalid argument
ddxSUNWkbd: Keyboard type ioctl KIOCTYPE failed on /dev/kbd

Fatal server error:
failed to initialize core devices

Wed Jul  7 18:02:08 2004
error (pid 351): Server for display :0 terminated unexpectedly 1

Wed Jul  7 18:02:08 2004
error (pid 351): Server for display :0 can't be started.
Couldn't open display connection

Thu Jul  8 11:41:26 2004
error (pid 350): Server for display :0 terminated unexpectedly 1
(EE) screenInfo.numScreens = 1
(==) Log file: "/var/log/XFree86.0.log", Time: Thu Jul  8 11:41:26
2004
(EE) PreInit done
KIOCTYPE: Invalid argument
ddxSUNWkbd: Keyboard type ioctl KIOCTYPE failed on /dev/kbd

Fatal server error:
failed to initialize core devices

Thu Jul  8 11:41:27 2004
error (pid 350): Server for display :0 terminated unexpectedly 1
(EE) screenInfo.numScreens = 1
(==) Log file: "/var/log/XFree86.0.log", Time: Thu Jul  8 11:41:27
2004
(EE) PreInit done
KIOCTYPE: Invalid argument
ddxSUNWkbd: Keyboard type ioctl KIOCTYPE failed on /dev/kbd

Fatal server error:
failed to initialize core devices

Thu Jul  8 11:41:28 2004
error (pid 350): Server for display :0 terminated unexpectedly 1
(EE) screenInfo.numScreens = 1
(==) Log file: "/var/log/XFree86.0.log", Time: Thu Jul  8 11:41:28
2004
(EE) PreInit done
KIOCTYPE: Invalid argument
ddxSUNWkbd: Keyboard type ioctl KIOCTYPE failed on /dev/kbd

Fatal server error:
failed to initialize core devices

Thu Jul  8 11:41:29 2004
error (pid 350): Server for display :0 terminated unexpectedly 1

Thu Jul  8 11:41:29 2004
error (pid 350): Server for display :0 can't be started.
Couldn't open display connection
XIO:  fatal IO error 146 (Connection refused) on X server "unix:0.0"
      after 0 requests (0 known processed) with 0 events remaining.
XIO:  fatal IO error 146 (Connection refused) on X server "unix:0.0"
      after 0 requests (0 known processed) with 0 events remaining.

Thu Jul  8 15:10:07 2004
error (pid 350): Server for display :0 terminated unexpectedly 1
(EE) screenInfo.numScreens = 1
(==) Log file: "/var/log/XFree86.0.log", Time: Thu Jul  8 15:10:07
2004
(EE) PreInit done
KIOCTYPE: Invalid argument
ddxSUNWkbd: Keyboard type ioctl KIOCTYPE failed on /dev/kbd

Fatal server error:
failed to initialize core devices

Thu Jul  8 15:10:08 2004
error (pid 350): Server for display :0 terminated unexpectedly 1
(EE) screenInfo.numScreens = 1
(==) Log file: "/var/log/XFree86.0.log", Time: Thu Jul  8 15:10:08
2004
(EE) PreInit done
KIOCTYPE: Invalid argument
ddxSUNWkbd: Keyboard type ioctl KIOCTYPE failed on /dev/kbd

Fatal server error:
failed to initialize core devices

Thu Jul  8 15:10:09 2004
error (pid 350): Server for display :0 terminated unexpectedly 1
(EE) screenInfo.numScreens = 1
(==) Log file: "/var/log/XFree86.0.log", Time: Thu Jul  8 15:10:09
2004
(EE) PreInit done
KIOCTYPE: Invalid argument
ddxSUNWkbd: Keyboard type ioctl KIOCTYPE failed on /dev/kbd

Fatal server error:
failed to initialize core devices

Thu Jul  8 15:10:11 2004
error (pid 350): Server for display :0 terminated unexpectedly 1

Thu Jul  8 15:10:11 2004
error (pid 350): Server for display :0 can't be started.
Couldn't open display connection

Thu Jul  8 17:23:10 2004
error (pid 350): Server for display :0 terminated unexpectedly 1
(EE) screenInfo.numScreens = 1
(==) Log file: "/var/log/XFree86.0.log", Time: Thu Jul  8 17:23:10
2004
(EE) PreInit done
KIOCTYPE: Invalid argument
ddxSUNWkbd: Keyboard type ioctl KIOCTYPE failed on /dev/kbd

Fatal server error:
failed to initialize core devices

Thu Jul  8 17:23:12 2004
error (pid 350): Server for display :0 terminated unexpectedly 1
(EE) screenInfo.numScreens = 1
(==) Log file: "/var/log/XFree86.0.log", Time: Thu Jul  8 17:23:12
2004
(EE) PreInit done
KIOCTYPE: Invalid argument
ddxSUNWkbd: Keyboard type ioctl KIOCTYPE failed on /dev/kbd

Fatal server error:
failed to initialize core devices

Thu Jul  8 17:23:13 2004
error (pid 350): Server for display :0 terminated unexpectedly 1
(EE) screenInfo.numScreens = 1
(==) Log file: "/var/log/XFree86.0.log", Time: Thu Jul  8 17:23:13
2004
(EE) PreInit done
KIOCTYPE: Invalid argument
ddxSUNWkbd: Keyboard type ioctl KIOCTYPE failed on /dev/kbd

Fatal server error:
failed to initialize core devices

Thu Jul  8 17:23:14 2004
error (pid 350): Server for display :0 terminated unexpectedly 1

Thu Jul  8 17:23:14 2004
error (pid 350): Server for display :0 can't be started.
Couldn't open display connection

/var/log/XFree86.0.log:
-----------------------

(EE) screenInfo.numScreens = 1
(==) Log file: "/var/log/XFree86.0.log", Time: Thu Jul  8 17:23:13
2004
(WW) XFree86 Configuration file does not exist, use
Solaris OWconfig file
(==) ServerLayout "SimpleLayout"
(**) |-->Screen "DefaultScreen 1" (0)
(**) |   |-->Monitor "DefaultMonitor"
(**) |   |-->Device "DefaultDevice"
(WW) No FontPath specified.  Using compiled-in default.
(==) FontPath set to
"/usr/openwin/lib/X11/fonts/Type1/,/usr/openwin/lib/X11/fonts/Type1/sun/,/usr/openwin/lib/X11/fonts/F3bitmaps/,/usr/openwin/lib/X11/fonts/Speedo/,/usr/openwin/lib/X11/fonts/misc/,/usr/openwin/lib/X11/fonts/75dpi/,/usr/openwin/lib/X11/fonts/100dpi/,/usr/openwin/lib/X11/fonts/TrueType"
(==) RgbPath set to "/usr/openwin/lib/X11/rgb"
(==) ModulePath set to "/usr/openwin/sfw/server//lib/modules"
(II) Module ABI versions:
        XFree86 ANSI C Emulation: 0.2
        XFree86 Video Driver: 0.6
        XFree86 XInput driver : 0.4
        XFree86 Server Extension : 0.2
        XFree86 Font Renderer : 0.4
(II) Loader running on solaris
(II) LoadModule: "pcidata"
(II) Loading /usr/openwin/sfw/server//lib/modules/libpcidata.a
(II) Module pcidata: vendor="The XFree86 Project"
        compiled for 4.3.0.1, module version = 1.0.0
        ABI class: XFree86 Video Driver, version 0.6
(II) PCI: Probing config type using method 1
(II) PCI: Config type is 1
(II) PCI: stages = 0x03, oldVal1 = 0x00000cf8, mode1Res1 = 0x00000cf8
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 1039,0740 card 0000,0000 rev 01 class 06,00,00
hdr 80
(II) PCI: 00:01:0: chip 1039,0001 card 0000,0000 rev 00 class 06,04,00
hdr 01
(II) PCI: 00:02:0: chip 1039,0008 card 0000,0000 rev 25 class 06,01,00
hdr 80
(II) PCI: 00:02:5: chip 1039,5513 card 0000,0000 rev 00 class 01,01,80
hdr 00
(II) PCI: 00:02:6: chip 1039,7013 card 1039,7013 rev a0 class 07,03,00
hdr 00
(II) PCI: 00:02:7: chip 1039,7012 card 13f6,0300 rev a0 class 04,01,00
hdr 00
(II) PCI: 00:03:0: chip 1039,7001 card 1462,5470 rev 0f class 0c,03,10
hdr 80
(II) PCI: 00:03:1: chip 1039,7001 card 1462,5470 rev 0f class 0c,03,10
hdr 00
(II) PCI: 00:03:3: chip 1039,7002 card 1462,5470 rev 00 class 0c,03,20
hdr 00
(II) PCI: 00:04:0: chip 1039,0900 card 1039,0900 rev 90 class 02,00,00 ...

read more »

 
 
 

Solaris 10 x86 X-server can not be started on display :0

Post by Alan Coopersmit » Sat, 10 Jul 2004 16:07:59



|KIOCTYPE: Invalid argument
|ddxSUNWkbd: Keyboard type ioctl KIOCTYPE failed on /dev/kbd

Some thing has gone wrong in the keyboard driver and the X server can't
talk to your keyboard.  Can you use it in console mode?  Is it plugged
in?

--
________________________________________________________________________

 http://www.csua.berkeley.edu/~alanc/   *   http://blogs.sun.com/alanc/
  Working for, but definitely not speaking for, Sun Microsystems, Inc.

 
 
 

Solaris 10 x86 X-server can not be started on display :0

Post by Casper H.S. Di » Sat, 10 Jul 2004 19:22:47



>I installed the Solaris express (S10 build 58 6/04) a couple of days
>ago.
>I was using the XFree86 to finish the initial installations.

I'm assuming you're using the built-in Xfree86 code, right?

Quote:>After 2 reboots, it shows "X-server can not be started on display:0"
>on monitor and keyboard doesn't respond thereafter.  Notice, the first
>reboot came back with CDE without problems.  The screen blinks 4 times
>before showing "The X-server can not be started on display :0.
>KIOCTYPE: Invalid argument
>ddxSUNWkbd: Keyboard type ioctl KIOCTYPE failed on /dev/kbd

It looks to me like the keyboard goes off to nowhere.

What type of keyboard are you using and what type of motherboard?

Casper
--
Expressed in this posting are my opinions.  They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.

 
 
 

Solaris 10 x86 X-server can not be started on display :0

Post by Jo » Sun, 11 Jul 2004 05:00:52




> >I installed the Solaris express (S10 build 58 6/04) a couple of days
> >ago.
> >I was using the XFree86 to finish the initial installations.

> I'm assuming you're using the built-in Xfree86 code, right?

> >After 2 reboots, it shows "X-server can not be started on display:0"
> >on monitor and keyboard doesn't respond thereafter.  Notice, the first
> >reboot came back with CDE without problems.  The screen blinks 4 times
> >before showing "The X-server can not be started on display :0.

> >KIOCTYPE: Invalid argument
> >ddxSUNWkbd: Keyboard type ioctl KIOCTYPE failed on /dev/kbd

> It looks to me like the keyboard goes off to nowhere.

> What type of keyboard are you using and what type of motherboard?

> Casper

I have a SiS740 north bridge, SiS962 south bridge motherboard.
It is a US English 104-key keyboard.
I changed 2 different keyboards but the same error message.
 
 
 

Solaris 10 x86 X-server can not be started on display :0

Post by Jo » Sun, 11 Jul 2004 05:11:28




> |KIOCTYPE: Invalid argument
> |ddxSUNWkbd: Keyboard type ioctl KIOCTYPE failed on /dev/kbd

> Some thing has gone wrong in the keyboard driver and the X server can't
> talk to your keyboard.  Can you use it in console mode?  Is it plugged
> in?

That's what I expected too but I didn't know how to correct it.
I used 2 different (new) PS/2 keyboards but no difference.
 
 
 

Solaris 10 x86 X-server can not be started on display :0

Post by Casper H.S. Di » Sun, 11 Jul 2004 05:33:39





>> |KIOCTYPE: Invalid argument
>> |ddxSUNWkbd: Keyboard type ioctl KIOCTYPE failed on /dev/kbd

>> Some thing has gone wrong in the keyboard driver and the X server can't
>> talk to your keyboard.  Can you use it in console mode?  Is it plugged
>> in?
>That's what I expected too but I didn't know how to correct it.
>I used 2 different (new) PS/2 keyboards but no difference.

I doubt the problem is with the keyboard; more likely it's a chipset
problem, a BIOS problem or a BIOS setting problem.

(I had a lot of trouble with a USB keyboard on a ASUS MB until
I upgraded the BIOS to the latest version)

It could, of course, also be a Solaris problem in which case
we need more information to debug it.

Casper
--
Expressed in this posting are my opinions.  They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.

 
 
 

Solaris 10 x86 X-server can not be started on display :0

Post by Jo » Sun, 11 Jul 2004 11:00:33






> >> |KIOCTYPE: Invalid argument
> >> |ddxSUNWkbd: Keyboard type ioctl KIOCTYPE failed on /dev/kbd

> >> Some thing has gone wrong in the keyboard driver and the X server can't
> >> talk to your keyboard.  Can you use it in console mode?  Is it plugged
> >> in?

> >That's what I expected too but I didn't know how to correct it.
> >I used 2 different (new) PS/2 keyboards but no difference.

> I doubt the problem is with the keyboard; more likely it's a chipset
> problem, a BIOS problem or a BIOS setting problem.

> (I had a lot of trouble with a USB keyboard on a ASUS MB until
> I upgraded the BIOS to the latest version)

> It could, of course, also be a Solaris problem in which case
> we need more information to debug it.

> Casper

I don't think a keyboard is the core problem since I used 2 working
PS/2 keyboards.  They work until the system is about to run X windows.
 I did read some postings about USB keyboard problems but mine are
PS/2.

As I mentioned in my original post, it worked the first 2 reboots with
X windows coming up.  After that, the X-server could never be started
any more.

Where can I get more information to help me debug/troubleshoot?

Thanks.

 
 
 

Solaris 10 x86 X-server can not be started on display :0

Post by Jo » Wed, 14 Jul 2004 07:34:51




> >I installed the Solaris express (S10 build 58 6/04) a couple of days
> >ago.
> >I was using the XFree86 to finish the initial installations.

> I'm assuming you're using the built-in Xfree86 code, right?

> >After 2 reboots, it shows "X-server can not be started on display:0"
> >on monitor and keyboard doesn't respond thereafter.  Notice, the first
> >reboot came back with CDE without problems.  The screen blinks 4 times
> >before showing "The X-server can not be started on display :0.

> >KIOCTYPE: Invalid argument
> >ddxSUNWkbd: Keyboard type ioctl KIOCTYPE failed on /dev/kbd

> It looks to me like the keyboard goes off to nowhere.

> What type of keyboard are you using and what type of motherboard?

> Casper

New /var/dt/Xerrors:
--------------------

(EE) screenInfo.numScreens = 1
(==) Log file: "/var/log/XFree86.0.log", Time: Mon Jul 12 15:03:11 2004
(EE) PreInit done
KIOCTYPE: Invalid argument
ddxSUNWkbd: Keyboard type ioctl KIOCTYPE failed on /dev/kbd

Fatal server error:
failed to initialize core devices
XIO:  fatal IO error 146 (Connection refused) on X server "unix:0.0"
      after 0 requests (0 known processed) with 0 events remaining.
XIO:  fatal IO error 146 (Connection refused) on X server "unix:0.0"
      after 0 requests (0 known processed) with 0 events remaining.

Mon Jul 12 15:03:14 2004
error (pid 350): Server for display :0 terminated unexpectedly 1
(EE) screenInfo.numScreens = 1
(==) Log file: "/var/log/XFree86.0.log", Time: Mon Jul 12 15:03:14 2004
(EE) PreInit done
KIOCTYPE: Invalid argument
ddxSUNWkbd: Keyboard type ioctl KIOCTYPE failed on /dev/kbd

Fatal server error:
failed to initialize core devices

Mon Jul 12 15:03:15 2004
error (pid 350): Server for display :0 terminated unexpectedly 1
(EE) screenInfo.numScreens = 1
(==) Log file: "/var/log/XFree86.0.log", Time: Mon Jul 12 15:03:15 2004
(EE) PreInit done
KIOCTYPE: Invalid argument
ddxSUNWkbd: Keyboard type ioctl KIOCTYPE failed on /dev/kbd

Fatal server error:
failed to initialize core devices

Mon Jul 12 15:03:16 2004
error (pid 350): Server for display :0 terminated unexpectedly 1
(EE) screenInfo.numScreens = 1
(==) Log file: "/var/log/XFree86.0.log", Time: Mon Jul 12 15:03:17 2004
(EE) PreInit done
KIOCTYPE: Invalid argument
ddxSUNWkbd: Keyboard type ioctl KIOCTYPE failed on /dev/kbd

Fatal server error:
failed to initialize core devices

Mon Jul 12 15:03:18 2004
error (pid 350): Server for display :0 terminated unexpectedly 1

Mon Jul 12 15:03:18 2004
error (pid 350): Server for display :0 can't be started.
Couldn't open display connection

 
 
 

Solaris 10 x86 X-server can not be started on display :0

Post by Casper H.S. Di » Thu, 15 Jul 2004 23:01:36





>> >I installed the Solaris express (S10 build 58 6/04) a couple of days
>> >ago.
>> >I was using the XFree86 to finish the initial installations.

>> I'm assuming you're using the built-in Xfree86 code, right?

>> >After 2 reboots, it shows "X-server can not be started on display:0"
>> >on monitor and keyboard doesn't respond thereafter.  Notice, the first
>> >reboot came back with CDE without problems.  The screen blinks 4 times
>> >before showing "The X-server can not be started on display :0.

>> >KIOCTYPE: Invalid argument
>> >ddxSUNWkbd: Keyboard type ioctl KIOCTYPE failed on /dev/kbd

>> It looks to me like the keyboard goes off to nowhere.

>> What type of keyboard are you using and what type of motherboard?

>> Casper
>I have a SiS740 north bridge, SiS962 south bridge motherboard.
>It is a US English 104-key keyboard.
>I changed 2 different keyboards but the same error message.

Perhaps it's time to collect some data with dtrace; specifically
so we can tell where the kbd ioctl fails.

Casper
--
Expressed in this posting are my opinions.  They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.

 
 
 

1. The X-server can not be started on display :0...

Hi Guys,

I just ran into a problem.

I am running a sparc solaris 7 machine.  after I installed the latest
recommended patch clusters the X window will not come up.

It will give me the error "the x-server can not be started on display :0...

The files under /etc/dt/cofnig/X* looks good.
and I've also tried /usr/dt/bin/dtconfig -reset  ..
-e ....
m64config -defaults with no luck.

can anyone tell me how to fix this problem?
Greatly appreciated!!!

tony

2. At Wit's end re 3C905C-TX

3. HELP: X-Server can not be started on display :0

4. Apache proxy module

5. The X-server can not be started on display:0..

6. FreeBSD + tomcat

7. "The X-server can not be started on display :0..."

8. Will I be abble to restore ?

9. X-Server can not be started on display :0

10. x-server can not be started on display 0

11. Blade 100, PGX64 card: X-server can not be started on display 0:

12. lsof 4.70D for Solaris 10 [was Re: Lsof on Solaris 10 x86?]

13. More on The X-server cannot be started on display 0: ...