On Mon, 1 Jan 2001, SATO Kazumi wrote:

> > Is there some special magic that's needed to get Xhpc running on the Z50i?
> > 
> > I'm using the a -current kernel as of yesterday, with the 1.5-release 
> > userland, and I get a null pointer error.  For some reason, the machine
> > seems to lock up, too.
> > 
> > Do I need to rebuild X with -current?
> 
> For my mistake, hpcfb.c rev1.28 enable experimental wscons multi
> screens supports.
> But Xhpc dosn't support wscons multi screens environment.
> 
> Xhpc core dump in this case, and leave console in WSDISPLAYIO_MODE_MAPPED state.
> So it seem to lock up. 
> It may recover by ioctl(fd_of_ttyE0, WSDISPLATIO_SMODE, WSDISPLAYIO_MODE_EMUL).
> 
> Try run Xhpc with "-dev /dev/ttyE0" or set XDEVICE environment "/dev/ttyE0"
> in the envionment.
> 
> I re-disable wscons multi screens supoorts in hpcfb.c rev1.29.
> 
> If it is not OK in above situation, I have no idea. 

Thanks!  I didn't have some of the WSDISPLAY options set in my kernel config
file.  Once I added the options set in GENERIC X started up just fine,
[modulo the pointer device issue]

	-castor