* Michael Wood -- Tuesday 29 May 2001 14:32:

> > The respective section from /var/log/XFree.0.log when plex86
> > wasn't run before is:
[...]
> >   (II) TDFX(0): Softbooting the board succeeded.
 
> Why do you say that?  The message says it succeeded!

Yes, and that's why I wrote: "... when plex86 wasn't run before ..."
This is the desired behaviour, that I mentioned only for comparison.



> > CPU:       Intel 80686; 266MHz; UP
> > RAM:       350M
> > System:    Linux 2.4.5                <--- new
> 
> What version of Linux *does* it work with for you?  i.e. have
> you tried it with Linux 2.4.4?

When I first posted the bug report, I had tried it with 2.4.4. Now
with 2.4.5 I get exactly the same crash. I'm not aware of any
kernel version, where it worked. But I hadn't tried for a very
long time, so I cannot say if the bug was introduced with a certain
version.


> > X-Server:  XFree86 4.0.3
> 
> plex86 works for me (haven't tested it extensively, though) on
> XFree86 3 and Linux 2.4.4.

No XFree86 3 installed here, just 4.0.3.



> > Graphics:  TDFX Voodoo 3 3000
> > Plex86:    CVS/HEAD as of today
> > Compiler:  gcc 2.95.2 (on SuSE 7.1)
> 
> I'm also using a different compiler.  I've used egcs 2.91.66 on
> RH 6.2 and gcc 2.96-69 on RH 7.0.

The compiler that I used is considered stable, unlike the one from
RH 7.0.



> It could probably be one of a number of things...  A bug in the
> plex86 kernel module, a bug in XFree86 4.0.3, a bug in Linux
> 2.4.5, a bug in gcc 2.95.2...  As to how to narrow it down, you
> could try changing things one at a time and see what
> combinations cause the problem.

Yes, that's what I'm doing since a while. I just won't install another
kernel or X-server. But I could imagine to compile XFree by myself
and insert some debug messages. But compiling XFree isn't exactly
what I would call 'fun'.   ;-) 



> You could also try compiling everything with no optimisations.
> Hope these suggestions help to narrow things down a little.

Yes, thanks. I'm still not out of ideas ...  :-)

m.

Reply via email to