This absolutely fixes the problem. Thanks a lot.
On Mon, 9 Sep 2002, Markus Gutschke wrote:
> + in a program. This will also break programs that rely on the
> + old behaviour and expect that dynamically allocated memory via
> + the malloc() family of functions is executable (which it is not)
On Mon, 9 Sep 2002, Mark Vojkovich wrote:
>Any kernel /var/log/messages about the kill.
>
>Does something like "XFree86 -probeonly" even work?
No, -probeonly fails in exactly the same way. But I hit paydirt in the
kernel logs:
Sep 9 18:30:53 [kernel] PAX: terminating task:
/usr/X11R6/b
I would think it wasn't an out-of-memory error. Before running XFree86,
free says:
total used free sharedbuffers cached
Mem:515100 31892 483208 0 2476 17904
-/+ buffers/cache: 11512 503588
Swap: 128484
>It's nowhere near the video drivers at that point. It
> would start doing bus probes right about there.
>
> Maybe "XFree86 -verbose -verbose -verbose" would help?
I'm quite sure I've tried that before, but I'll double check that again
when I get back to my laptop (I'm typing this on a d
That was the console output, but the log is not much more informative. Here
it is:
XFree86 Version 4.2.0 / X Window System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 18 January 2002
If the server is older than 6-12 months, or if your card is
newer than th
I'm using XFree86 4.2.0 on Gentoo on a Pentium 3, and when I startx, the
screen blanks but nothing happens. I've narrowed the problem down to the
XFree86 command, which gives this output:
XFree86 Version 4.2.0 / X Window System
(protocol Version 11, revision 0, vendor release 6600)
Relea
