On Mon, 1 Jul 2002, James wrote:
> > I think you should wait for some feedback from FreeBSD users on this
> > list. I would imagine that someone has seen this before.
>
> Ok, I'll do that. I know stuff like this has been in this list before -- I
> was reading through a lot of them. However, I've never seen a fix to it.
> Either the people figured it out or stopped asking for some other reason.
I suspect that it's not related to the unresolved symbol. The vgahw
module wasn't loaded yet so I'd expect that and other vgahw symbols to
be unresolved at that point.
>
> It's not a driver problem, is it?
I don't think so since it works on Linux. Does your server have
debug info in it? Could you get a gdb backtrace on the core dump? That
may narrow down the problem.
Mark.
_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
