Re: X 4.0.3 and agpgart

[Sean Quinlan <smq@gmx.co.uk>]

* Jim McCloskey <mcclosk@ling.ucsc.edu> (2001-07-18 22:00):
> I recently up-graded to X 4.0.3 as part of the upgade to debian
> testing. Also kernel version 2.4.5. There were some things to sort
> out, but all seems basically well at this point.
> 
> There's one glitch, though, that I'm still trying to resolve. I have a
> Matrox G400 card and I'm using the mga driver.
> 
> In the XFree86 log, I get this:
> 
> (II) MGA(0): [drm] bpp: 16 depth: 16
> (II) MGA(0): [drm] Sarea 2196+632: 2828
> [drm] failed to load kernel module "mga"
> (0): [drm] drmOpen failed
> (EE) MGA(0): [drm] DRIScreenInit Failed
> 
> and in syslog:
> 
> Jul 18 12:19:17 toraigh kernel: [drm] The mga drm module requires the
>                                 agpgart module to function correctly 
> Jul 18 12:19:17 toraigh kernel: Please load the agpgart module before
>                                 you load the mga module 
> 
> So mga_drm requires the agpgart kernel module.  I have this module in:
> /lib/modules/2.4.5/kernel/drivers/char/agp/
> 
> The device file exists:
> 
>  crw-rw----    1 root     video     10, 175 Jul 18 12:22 agpgart
> 
> But all attempts to load the module fail, with this on the
> command-line:
> 
>  init_module: No such device
> 
> and this in sys.log:
> 
>  kernel: Linux agpgart interface v0.99 (c) Jeff Hartmann
>  kernel: agpgart: Maximum main memory to use for agp memory: 94M
>  kernel: agpgart: unsupported bridge
>  kernel: agpgart: no supported devices found.
> 
> lspci shows:
> 
>  00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 0391 (rev 02)
>  00:01.0 PCI bridge: VIA Technologies, Inc.: Unknown device 8391
>  00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super] (rev 22)
> 
> So I tried:
> 
>  modprobe agpgart agp_try_unsupported=1
> 
> but got the same error messages. Anyone know of a way forward? Thanks,

Sounds like you have the agpgart module, but no support for your
controller.  When you enabled agpgart, you would have needed to
specify the type of agp controller you have (probably VIA in your
case).

Then again, you may have an unsupported chipset, what motherboard do
you have?

Cheers,
Sean

-- 
Sean Quinlan (smq@gmx.co.uk)