I am having a heck of a time getting X to run on a 
Digital AlphaStation 200 4/233.  I've tried rebuilding the
kernel a bunch of ways, and still get

tart# xinit

unable to get frame buffer info: Inappropriate ioctl for device
unable to get frame buffer info: Inappropriate ioctl for device
unable to get frame buffer info: Inappropriate ioctl for device
unable to get frame buffer info: Inappropriate ioctl for device
unable to get frame buffer info: Inappropriate ioctl for device

Fatal server error:
no screens found
X connection to :0.0 broken (explicit kill or server shutdown).
tart# 

(yes, the machine name is tart.  someone got croissant already).

Each of the "unable to get frame buffer info" messages above
refer to a wsconsole device.  One of them has login running.

The latest kernel attempt is the GENERIC kernel plus

#
#  Options for X
#
options         XSERVER, UCONSOLE               # xserver option necessary for X
options         WSDISPLAY_COMPAT_PCVT           # emulate some ioctls
options         WSDISPLAY_COMPAT_SYSCONS        # emulate some ioctls
options         WSDISPLAY_COMPAT_USL         # VT handling
options         WSDISPLAY_COMPAT_RAWKBD         # can get raw scancodes  

I looked through the wsconsole ioctl code, and it looks like
this should be all it needs.  The following call trace might be
informative ...

  1135 XalphaNetBSD CALL  access(0x12039a8ff,0x6)
  1135 XalphaNetBSD NAMI  "/dev/ttyE2"
  1135 XalphaNetBSD RET   access 0
  1135 XalphaNetBSD CALL  open(0x12039a8ff,0x2,0)
  1135 XalphaNetBSD NAMI  "/dev/ttyE2"
  1135 XalphaNetBSD RET   open 6  
  1135 XalphaNetBSD CALL  ioctl(0x6,_IOR('W',0x40,0x4),0x1fffff488)
  1135 XalphaNetBSD RET   ioctl 0  
  1135 XalphaNetBSD CALL  ioctl(0x6,_IOR('W',0x41,0x10),0x1fffff478)
  1135 XalphaNetBSD RET   ioctl -1 errno 25 Inappropriate ioctl for device

This maps to 

#define WSDISPLAYIO_GINFO       _IOR('W', 65, struct wsdisplay_fbinfo)

I made a brief stab at debugging the kernel by setting a breakpoint on
the underlying code invoked by this ioctl, but that caused the system
to seize.  I suspect that debugging wsconsole while using wsconsole
might not work too well :)

I did a three-month search of the port-alpha archive by title, but didn't
see anything that looked liked it applied.

Does this look familiar to anyone?  

This is on NetBSD 1.4.1.

        - Steve

---
Steve Moulton        SNMP Research, Inc            voice: +1 423 573 1434
Software Engineer    3001 Kimberlin Heights Rd.    fax: +1 423 573 9197
moulton@snmp.com     Knoxville, TN 37920-9716      http://www.int.snmp.com