fbraab@leuze-owen.de (Fritz B. Raab) (03/09/90)
Hello, could anyone help me ?
I installed V11R4 on our Sun 3/260 including fixes 1 and 2 for the core.
When I want to run xinit I always get Error messages like this:
Getting interface configuration: Operation not supported on socket
sunOpenFrameBuffer: Inappropriate ioctl for device
sunOpenFrameBuffer: Inappropriate ioctl for device
sunOpenFrameBuffer: Inappropriate ioctl for device
sunOpenFrameBuffer: Inappropriate ioctl for device
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 a server shutdown or KillClient.
and contype always only reports tty.
The /dev/bwtwo0 and /dev/fb are installed and we run a 1600*1280 mono screen.
Whats wrong ?
Greetings, Fritz
(-: Fritz B. Raab | email: fbraab@leuze-owen.de :-)
(-: Leuze electronic, Abt. TDV | old: ..uunet!unido!leuze!fbraab :-)
(-: In der Braike 1 | fbraab@leuze.uucp :-)
(-: D7311 Owen / Teck W.Germany | voice: +49 7021 573185 fax: 573200 :-)mouse@LARRY.MCRCIM.MCGILL.EDU (der Mouse) (03/11/90)
> Hello, could anyone help me ? > I installed V11R4 on our Sun 3/260 including fixes 1 and 2 for the > core. When I want to run xinit I always get Error messages like > this: > Getting interface configuration: Operation not supported on socket > sunOpenFrameBuffer: Inappropriate ioctl for device > sunOpenFrameBuffer: Inappropriate ioctl for device > sunOpenFrameBuffer: Inappropriate ioctl for device > sunOpenFrameBuffer: Inappropriate ioctl for device > sunOpenFrameBuffer: Inappropriate ioctl for device > Whats wrong ? You don't say enough to be sure, but here's my guess: you built the server with gcc 1.37. Gcc 1.37 has a broken fixincludes script (or so I'm told by the person who maintains gcc here), and as a result all ioctls pass the wrong value to the kernel. Here's a quick experiment to see whether this is the problem: Put this in a file, say x.c: #include <sys/ioctl.h> main(){foo(SIOCGIFCONF);} Now run "cc -E x.c | tail -1" and "gcc -E x.c | tail -1". They should produce essentially the same output (whitespace differences can be ignored). If the gcc output has 'x' where the cc output has some other letter in quotes ('i', I think it should be), your gcc's fixincludes script is broken (or wasn't run, or wasn't run correctly, or the gcc include files have been trashed, or something of the sort). der Mouse old: mcgill-vision!mouse new: mouse@larry.mcrcim.mcgill.edu