On Fri, Dec 01, 2000 at 09:22:22PM -0600, Peter Samuelson wrote:
>
> [Jamie Manley]
> > Yes, modversions was enabled. Should that be affecting the build of
> > the kernel proper?
>
> The bug you ran into is that MODVERSIONS messes up the
> 'get_module_symbol' function, which is a sort of "optio
[Jamie Manley]
> Yes, modversions was enabled. Should that be affecting the build of
> the kernel proper?
The bug you ran into is that MODVERSIONS messes up the
'get_module_symbol' function, which is a sort of "optional dependency"
mechanism used by a few modules such as DRI (in this case: DRI
On Fri, Dec 01, 2000 at 02:52:11PM +, John Levon wrote:
> > [drm] The mga drm module requires the agpgart module to function correctly
> > Please load the agpgart module before you load the mga module
> >
> > Although XFree86 seems to be happy enough loading the dri and drm
> > modules.
> >
On Fri, 1 Dec 2000 14:52:11 + (GMT),
John Levon <[EMAIL PROTECTED]> wrote:
>Probably you have modversions enabled (CONFIG_MODVERSION=y). Disable that
>and try again, or build as modules. 2.4 fixed this problem in the proper
>way, but I don't know what's going to happen about 2.2 ...
I have s
On Wed, 29 Nov 2000, Jamie Manley wrote:
> Finally got around to trying the 2.2.18pre series and the agp/drm
> backport and noticed something odd at bootup. Here's an extract from
> dmesg:
>
> Linux agpgart interface v0.99 (c) Jeff Hartmann
> agpgart: Maximum main memory to use for agp memory:
Finally got around to trying the 2.2.18pre series and the agp/drm
backport and noticed something odd at bootup. Here's an extract from
dmesg:
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 440M
agpgart: Detected Intel 440BX chipset
agpgart: AG
6 matches
Mail list logo
