agaw@ircso.Corp.Sun.COM (Anthony T.K. Gaw, Conslutant) (04/25/91)
I've been pulling out my hair to build a runnable X11 R4 server from the mit distribution on a Sun3/260 (bwtwo framebuffer) with sunos 4.1.1. When I try to start the server with "xinit", I get: ======================================================================== Getting interface configuration: Operation not supported on socket SunOpenFrameBuffer: inappropriate ioctl for device Fatal server bug! no screens found XIO: fatal IO error 32 (broken pipe on X server "(null)". After 0 requests (0 known processed with 0 events remaining) The connection was probably broken by server shutting down or kill client ======================================================================== I've installed all 18 X11 R4 patches; tried removing all unused framebuffers in /dev (i.e. /dev/cg*) ; & tried using gcc among other stuff. There seems to be multiple probs here. The first error line seems to be in mit/server/os/4.2bsd/access.c. The second in mit/server/ddx/sun/sunInit.c. I was able to solve the "SunOpenFrameBuffer" problem. But idunno about the rest. Can anyone help? Tony Gaw (consultant) Internet: Anthony.Gaw@Corp.Sun.COM
mwette@csi.jpl.nasa.gov (Matt Wette) (04/25/91)
In article <3944@jethro.Corp.Sun.COM>, agaw@ircso.Corp.Sun.COM (Anthony T.K. Gaw, Conslutant) writes: |> I've been pulling out my hair to build a runnable X11 R4 server |> from the mit distribution on a Sun3/260 |> (bwtwo framebuffer) with sunos 4.1.1. When I try to start the server |> with "xinit", I get: |> |> ======================================================================== |> |> Getting interface configuration: Operation not supported on socket |> |> SunOpenFrameBuffer: inappropriate ioctl for device |> |> |> Fatal server bug! |> no screens found |> |> XIO: fatal IO error 32 (broken pipe on X server "(null)". |> After 0 requests (0 known processed with 0 events remaining) |> The connection was probably broken by server shutting down |> or kill client |> |> ======================================================================== I was happy to see someone ran into the same problems I had. I couldn't even get constype to work when compiled with gcc! It always returned 'tty'. My 'fix' was to do mv /usr/local/lib/gcc-cpp /usr/local/lib/gcc-cpp.. ln -s /usr/lib /usr/local/lib/gcc-cpp This seemed to fix many problems. Matt -- _________________________________________________________________ Matthew R. Wette | Jet Propulsion Laboratory, 198-326 mwette@csi.jpl.nasa.gov | 4800 Oak Grove Dr, Pasadena,CA 91109 -----------------------------------------------------------------
mouse@lightning.mcrcim.mcgill.EDU (der Mouse) (05/04/91)
> I've been pulling out my hair to build a runnable X11 R4 server from > the mit distribution on a Sun3/260 (bwtwo framebuffer) with sunos > 4.1.1. When I try to start the server with "xinit", I get: > ======================================================================== > Getting interface configuration: Operation not supported on socket > SunOpenFrameBuffer: inappropriate ioctl for device > Fatal server bug! > no screens found This looks a great deal like the gcc fixincludes problem. You say > I've installed all 18 X11 R4 patches; tried removing all unused > framebuffers in /dev (i.e. /dev/cg*) ; & tried using gcc among other > stuff. but you don't say whether you tried *not* using gcc. Try building the server with cc (of course, delete all the .o files first). If that works, your problem is likely the fixincludes problem. See the FAQ, question 51; I can mail it to you if you want. (The problem is that all ioctl() calls compiled with gcc are failing.) der Mouse old: mcgill-vision!mouse new: mouse@larry.mcrcim.mcgill.edu
mwette@csi.jpl.nasa.gov (Matt Wette) (05/06/91)
In article <9105032222.AA03383@lightning.McRCIM.McGill.EDU>, mouse@lightning.mcrcim.mcgill.EDU (der Mouse) writes: |> > I've been pulling out my hair to build a runnable X11 R4 server from |> > the mit distribution on a Sun3/260 (bwtwo framebuffer) with sunos |> > 4.1.1. When I try to start the server with "xinit", I get: |> |> > ======================================================================== |> |> > Getting interface configuration: Operation not supported on socket |> |> > SunOpenFrameBuffer: inappropriate ioctl for device |> |> |> > Fatal server bug! |> > no screens found |> |> This looks a great deal like the gcc fixincludes problem. You say |> der Mouse I don't think this is a fixincludes problem. I compiled X11R4 upto patch level 14 (I think) on SunOS 4.0.3c (on Sun 3/60) with gcc-1.37.1 (did run fixincludes). X ran fine. I recently compiled X11R4 upto patch level 18 on SunOS 4.1.1 (on Sun 3/60) with gcc-1.39 (did run fixincludes). X did *not* run and gave the errors mentioned above. In fact, I got suspicious when constype (mit/server/ddx/sun/constype) didn't give the correct answer (it gave me "tty" instead of "gx"). So I compiled constype with cc and got the correct response. Then I compiled it with first doing a "ln -s /lib/cpp /usr/local/lib/gcc-cpp". Presto. It worked. Something seems to be wrong with either gcc-1.39's cpp or with fixincludes, I would guess. Matt -- _________________________________________________________________ Matthew R. Wette | Jet Propulsion Laboratory, 198-326 mwette@csi.jpl.nasa.gov | 4800 Oak Grove Dr, Pasadena,CA 91109 -----------------------------------------------------------------
mouse@lightning.mcrcim.mcgill.EDU (der Mouse) (05/07/91)
>>> Getting interface configuration: Operation not supported on socket >>> SunOpenFrameBuffer: inappropriate ioctl for device >>> Fatal server bug! >>> no screens found >> This looks a great deal like the gcc fixincludes problem. > I don't think this is a fixincludes problem. > I compiled X11R4 upto patch level 14 (I think) on SunOS 4.0.3c (on > Sun 3/60) with gcc-1.37.1 (did run fixincludes). X ran fine. > I recently compiled X11R4 upto patch level 18 on SunOS 4.1.1 (on Sun > 3/60) with gcc-1.39 (did run fixincludes). X did *not* run and gave > the errors mentioned above. In fact, I got suspicious when constype > (mit/server/ddx/sun/constype) didn't give the correct answer (it gave > me "tty" instead of "gx"). So I compiled constype with cc and got > the correct response. Then I compiled it with first doing a "ln -s > /lib/cpp /usr/local/lib/gcc-cpp". Presto. It worked. Something > seems to be wrong with either gcc-1.39's cpp or with fixincludes, I > would guess. Yeah, it still looks to me like the fixincludes problem. The difference between gcc's cpp and /lib/cpp is that gcc's is an ANSI cpp and doesn't substitute macro arguments within character constants in the replacement text, whereas /lib/cpp is a Reiser-style cpp and does. This causes (almost[%]) all ioctls to compile to wrong value, so of course they all fail. As for "did run fixincludes", well, I think it probably didn't work. Try the short test from question 80 of the recently-posted FAQ. Perhaps fixincludes doesn't deal with 4.1.1 correctly, perhaps 1.39's fixincludes is broken, perhaps something else is wrong. But if you can't get the short test to work, there's really no hope of getting X to behave. [%] "almost" all because an ioctl whose subsystem-selection character matches the macro argument name (usually x) will come out with the correct value in spite of ANSI-vs-Reiser semantics. der Mouse old: mcgill-vision!mouse new: mouse@larry.mcrcim.mcgill.edu