Home.... | log in.... | Pub my question! | Sign-up....
Java-index >> Solaris Operating System >> Solaris 10 Features

Unable to start GUI

I have an Ultra 45 installed with an XVR-2500. I have attempted to install both Solaris 10 01/06 and Solaris 10 06/06, and both times I have had real issues getting the GUI login to work.

During install, I have no problems with the GUI. It is only after the install that problems occur. Sometimes they happened on first boot, sometimes they occur later, but inevitably I get dumped to the text console.

I have attempted to add the flag "-dev /dev/fbs/kfb0" to "/usr/openwin/lib/X11/xdm/Xservers" and "/usr/dt/config/Xservers". I have switched hardware to the extent of actually swapping out machines, so a completely new system and new graphics card. No luck. All I get is the console login. I have looked in /var/adm/messages, /var/log/syslog, and /var/dt/Xerrors. The only thing that jumped out at me was in /var/dt/Xerrors:

fbconsole: ioctl SRIOCSREDIR: Device busy

I have googled around for that error message and nothing turned up.

Any help would be greatly appreciated. Oh, and I have seen the threads that suggest 'kdmconfig', but unfortunantly that is only available on x86, not SPARC.

[1134 byte] By [belisarius@usermail.com] at [2007-11-26 8:45:29]
«« Engine Died Errors Scripting doesnt seem to be "replace() function related"
»» Session Id
# 1
I just wanted to add I've successfully installed Solaris 10 numerous times on older hardware, like a V240 or SunBlade 2000. It is only with the Ultra 45 that I've had difficulty.
belisarius@usermailcom at 2007-7-6 22:29:33 > top of Java-index,Solaris Operating System,Solaris 10 Features...
# 2

Solved my own problem, but it wasn't obvious so here's the solution for anyone else who has similar problems:

My box was setup to eventually join a network, but I was setting it up without any connection initially. I discovered that the problem was that the GUI would eventually come up, but only after six minutes of waiting at the text-only prompt. I discovered the length by simply waiting in front of the screen, counting the minutes until the GUI popped up.

The only messages I saw were a series of sendmail errors complaining about not being able to discover a fully qualified domain name for the host. I'd seen those in the past on other systems, but they had ultimately been irrelevant on those machines so I ignored them. But just after the last error message in the series, the GUI came up. Deciding that fixing that error might lead to something, I added the FQDN into the hosts file. Reboot and instantanious GUI.

For some reason Solaris 10 prevents the X server from starting until after the sendmail server has started or timed out. Hopefully this will solve someone else's headache.

belisarius@usermailcom at 2007-7-6 22:29:33 > top of Java-index,Solaris Operating System,Solaris 10 Features...
Solaris Operating System
Solaris 10 Features

Solaris Operating System New Topic

Solaris Operating System Hot Topic

Solaris Operating System

All Classified