[comp.windows.x] X11R4 startup problems on Sun3

henryc@cs.umr.edu (Henry Clark) (07/31/90)

I'm having troubles starting X11R4 on a Sun 3 running SunOS 4.0.3.
After typing startx or xinit, the server returns the following
messages:

Getting interface configuration: Operation not supported on socket
sunOpenFrameBuffer: Inappropriate ioctl for device
sunOpenFrameBuffer: Inappropriate ioctl for device

Fatal server bug!
no screens found
/usr/userb/u1/henryc/.xserverrc: 16572 Abort - core dumped

I've created all the device files I could find, but the problem
persists.  I've applied all patches through patch 14.  Any ideas 
(via e-mail, I can't read it all :-)) would be appreciated.

Thanks,
Henry
henryc@cs.umr.edu

mouse@LARRY.MCRCIM.MCGILL.EDU (08/10/90)

> I'm having troubles starting X11R4 on a Sun 3 running SunOS 4.0.3.
> After typing startx or xinit, the server returns the following
> messages:

> Getting interface configuration: Operation not supported on socket
> sunOpenFrameBuffer: Inappropriate ioctl for device
> sunOpenFrameBuffer: Inappropriate ioctl for device

> Fatal server bug!
> no screens found
> /usr/userb/u1/henryc/.xserverrc: 16572 Abort - core dumped

Almost certainly, you used gcc to build the server, but your gcc's
fixincludes script was not run or is broken, or perhaps the generated
include files have been damaged afterwards.  This sort of behavior is
characteristic of this problem.

To check, create a little file ("foo.c", say) containing

#include <sys/ioctl.h>
SIOCGIFCONF

run it through cc -E and gcc -E, and compare the last couple of lines
of output.  You will probably see 'x' in the gcc output where the cc
output has an 'i'.  If this is true, the fixincludes problem has struck
again.  If this test fails, there's not much hope for getting the
server running until your gcc's include files are fixed.

					der Mouse

			old: mcgill-vision!mouse
			new: mouse@larry.mcrcim.mcgill.edu