It's in the libvbe.a module. We'll probably need to see the
/var/log/XFree86.0.log to say more about why that's not resolved.
It's usually because the driver didn't request that it be loaded,
or if it crashes before then for some reason you often see messages
about unresolved symbols when the server is aborting.
Mark.
On Thu, 12 Jun 2003, Jason Kim wrote:
> Thank you ...
>
> No I didn't modify this symbol.. This symbol is "vbeFree".
>
> I didn't touch anything about Savage device driver, but savage_driver.o module can't
> resolve the vbeFree symbol anymore... T.T
>
> jason
>
> ----- Original Message -----
> From: "Mark Vojkovich" <[EMAIL PROTECTED]>
> To: "Jason Kim" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Thursday, June 12, 2003 9:34 PM
> Subject: Re: Symbol unresolved problems..
>
>
> > Do you have a specific example?
> >
> > Are these symbols in your modifications? You can't call
> > anything you like from within an XFree86 module. They don't,
> > for instance, link against libc. There are only specific
> > functions you can call - ones exported by the core server.
> >
> > Mark.
> >
> > On Thu, 12 Jun 2003, Jason Kim wrote:
> >
> > > Hi...
> > > I modified xfree 4.3.? and successfuly compiled and installed it. When I start
> > > X, I got some messages like "Symbol xxxxx in module xxxxx is not resolved".
> > >
> > > What is the main reason of these problems? What cause it?
> > >
> > > thank you..
> > >
> >
> > _______________________________________________
> > Devel mailing list
> > [EMAIL PROTECTED]
> > http://XFree86.Org/mailman/listinfo/devel
> _______________________________________________
> Devel mailing list
> [EMAIL PROTECTED]
> http://XFree86.Org/mailman/listinfo/devel
>
_______________________________________________
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
