SOLVED: Re: problem starting X on linux-m68k

[Mike Lockwood <mike@voodoomonkey.com>]

In case anyone searching the archives has the same problem:

I upgraded my kernel to the latest 2.2.6 CVS snapshot, but that didn't
fix the problem.  Switching to the newer kernel did clear up a number of
console display problems though.

So I upgraded to the 3.3.3.1 XF68_FBDev from ftp.xfree86.org.  That X
server reported a configuration error instead of segfaulting.  It turned
out my XF86Config was misconfigured, but the X server that comes with
Slink crashes instead of reporting the error.

Now I am running X on my Quadra 700 at 8bpp at 832x624.  I have
WindowMaker installed so I am happy :-)

Thanks to the linux-m68k developers that made this possible.

Mike

Michael Schmitz wrote:
> 
> Mike Lockwood wrote:
> > > There has to be another error message (the PEX font stuff is an endianness
> > > problem IIRC and by no means fatal). Please post the fukk output of
> > > startx.
> > (**) FBDev: Using default frame buffer video mode
> > (--) FBDev: Frame buffer device: Macintosh
> > (--) FBDev: Video memory: 507K
> > (--) FBDev: Type 0 type_aux 0 bits_per_pixel 1
> > (--) FBDev: No virtual desktop
> > (--) FBDev: Using mfb driver
> > PEXExtensionInit: Couldn't open default PEX font file  Roman_M
> > Fatal server error:
> > Caught signal 11.  Server aborting
>          ^^^^^^^^^^
> 
> That's it: segmentation fault for the X server.
> Try a 2.2.6 kernel; I've no idea why that segfault happens but it's been a
> persistent problem in 2.0.36 for some people. (So far, I've not been able
> to even figure out anything in common among the reports on crashing X
> servers. And I've not had the problem myself.)
> 
>         Michael