*ERROR* Cannot initialize the agpgart module.

I am getting the above message in 2.5.51, 52, and 52+bk current. Pci info follows:

oscar# lspci -vv
00:00.0 Host bridge: VIA Technologies, Inc. VT82C598 [Apollo MVP3] (rev 04)

        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR+
        Latency: 16
        Region 0: Memory at e0000000 (32-bit, prefetchable) [size=64M]
        Capabilities: [a0] AGP version 1.0
                Status: RQ=7 SBA+ 64bit- FW- Rate=x1,x2
                Command: RQ=0 SBA- AGP- 64bit- FW- Rate=<none>

with a mga G400

01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 04) (prog-if 00 [VGA])
Subsystem: Matrox Graphics, Inc. Millennium G400 MAX/Dual Head 32Mb
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64 (4000ns min, 8000ns max), cache line size 08
Interrupt: pin A routed to IRQ 11
Region 0: Memory at e8000000 (32-bit, prefetchable) [size=32M]
Region 1: Memory at e4000000 (32-bit, non-prefetchable) [size=16K]
Region 2: Memory at e5000000 (32-bit, non-prefetchable) [size=8M]
Expansion ROM at <unassigned> [disabled] [size=64K]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [f0] AGP version 2.0
Status: RQ=31 SBA+ 64bit- FW- Rate=x1,x2
Command: RQ=31 SBA+ AGP+ 64bit- FW- Rate=x1

What else would help to debug this? The drm error above is all I find in the logs...

TIA
Ed Tomlinson

Replying to Ed Tomlinson:

If you mount devfs somewhere you also don't find misc/agpgart inside ? :)))

And nothing about agp aperture in dmesg?

Paul P 'Stingray' Komkoff 'Greatest' Jr /// (icq)23200764 /// (http)stingr.net
  When you're invisible, the only one really watching you is you (my keychain)

Not normally. If I modprobe via-agp modprobe segfaults (a Rusty's bug), but via_agp and agpgart get loaded (note that - changed to _ when the module is loaded - it has dash in file in the directory). Doing it this time gets an oops (52bk as of last night):

Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected VIA MVP3 chipset

Unable to handle kernel paging request at virtual address e0db9080
 printing eip:
e0db9080
*pde = 1ed12067
*pte = 00000000
Oops: 0000
CPU:    0
EIP:    0060:[<e0db9080>]    Not tainted
EFLAGS: 00010297

EIP is at 0xe0db9080
eax: 00000000 ebx: c15d5800 ecx: c0291b68 edx: 00000282
esi: 00000000 edi: c15d584c ebp: c15d5800 esp: d93e5f08
ds: 0068 es: 0068 ss: 0068
Process modprobe (pid: 19122, threadinfo=d93e4000 task=df09aca0)

Stack: e0de816f c15d5800 c15d5800 e0dc81a1 c15d5800 e0dc84a8 c019f5c8 
c15d5800
       e0dcd2ac c15d584c e0dc84a8 ffffffed e0dc84a8 e0dc8480 c01ac0af 
c15d584c
       c15d584c c15d5854 c02bd934 c01ac183 c15d584c e0dc84a8 c02bd840 
e0dc83b8
Call Trace:
 [<e0de816f>] agp_register_driver+0x27/0x9c [agpgart]
 [<e0dc81a1>] agp_via_probe+0x35/0x3c [via_agp]
 [<e0dc84a8>] agp_via_pci_driver+0x28/0xa0 [via_agp]
 [<c019f5c8>] pci_device_probe+0x40/0x5c
 [<e0dcd2ac>] agp_via_pci_table+0x0/0x38 [via_agp]
 [<e0dc84a8>] agp_via_pci_driver+0x28/0xa0 [via_agp]
 [<e0dc84a8>] agp_via_pci_driver+0x28/0xa0 [via_agp]
 [<e0dc8480>] agp_via_pci_driver+0x0/0xa0 [via_agp]
 [<c01ac0af>] bus_match+0x37/0x6c
 [<c01ac183>] driver_attach+0x37/0x60
 [<e0dc84a8>] agp_via_pci_driver+0x28/0xa0 [via_agp]
 [<e0dc83b8>] __module_pci_device_size+0x10/0x18 [via_agp]
 [<e0dc84a8>] agp_via_pci_driver+0x28/0xa0 [via_agp]
 [<c01ac44c>] bus_add_driver+0xa4/0xc4
 [<e0dc84a8>] agp_via_pci_driver+0x28/0xa0 [via_agp]
 [<e0dc84c8>] agp_via_pci_driver+0x48/0xa0 [via_agp]
 [<c01ac83c>] driver_register+0x34/0x38
 [<e0dc84a8>] agp_via_pci_driver+0x28/0xa0 [via_agp]
 [<c019f6c2>] pci_register_driver+0x42/0x50
 [<e0dc84a8>] agp_via_pci_driver+0x28/0xa0 [via_agp]
 [<e0dcd1af>] agp_via_init+0xb/0x44 [via_agp]
 [<e0dc8480>] agp_via_pci_driver+0x0/0xa0 [via_agp]
 [<c0125752>] sys_init_module+0x116/0x1a4
 [<c0108937>] syscall_call+0x7/0xb

Code:  Bad EIP value.

The module load occured after X was started.

Ed Tomlinson

[snip]

I get a very similar oops, but with amd_k7_agp (2.5.52-mm2). I'm not bk-savvy as yet, but if pointed at a diff, would be happy to verify it.

Matt

On Fri, 20 Dec 2002, Matt Bernstein wrote:

| On Dec 17 Ed Tomlinson wrote:
|
| >Not normally.  If I modprobe via-agp modprobe segfaults (a Rusty's bug),
| >but via_agp and agpgart get loaded (note that - changed to _ when the module
| >is loaded - it has dash in file in the directory).  Doing it this time gets
| >an oops (52bk as of last night):
| [snip]
|
| I get a very similar oops, but with amd_k7_agp (2.5.52-mm2). I'm not
| bk-savvy as yet, but if pointed at a diff, would be happy to verify it.

2.5.zz kernel diff snapshots (from bk) are available at
http://www.kernel.org/pub/linux/kernel/v2.5/snapshots/
e.g., latest is:
http://www.kernel.org/pub/linux/kernel/v2.5/snapshots/patch-2.5.52-bk4.bz2

~Randy

Latest AGP bits aren't in Linus tree yet. A few more bits to nail down, and then I'll ask him to pull again.

Dave

| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

There are a bunch of pending fixes at bk://linux-dj.bkbits.net/agpgart, but nothing that should be relevant to this problem.
Are you using agpgart as modules? Which ones loaded ?
I've a feeling agpgart.ko loaded here, but not via-agp.ko

What needs to happen is when agpgart.ko is loaded, all the chipset drivers also get pulled in as dependancies. Since the new module stuff went in, I'm not sure how this works, if it works at all.[1]

Dave

[1] I'm yet another developer who has had a rough time with the new modules stuff. I'll try it again soon.

| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs