AGPGART problems with VIA KX133 chipsets under 2.2.18/2.4.0

AGPGART problems with VIA KX133 chipsets under 2.2.18/2.4.0

[Michael Guntsche]

Hello all,

While playing around with the agpgart module I noticed the following strange
behaviour.

The hardware in question is an Asus K7V with the KX133 chipset and has been
tested on both 2.4.0 and 2.2.18 kernels.

The output below is just from insmod,rmmod,insmod agpgart without starting
X.

insmod agpgart for the first time:
Jan 22 23:17:10 deepblue kernel: Linux agpgart interface v0.99 (c) Jeff
Hartmann
Jan 22 23:17:10 deepblue kernel: agpgart: Maximum main memory to use for agp
memory: 204M
Jan 22 23:17:10 deepblue kernel: agpgart: Detected Via Apollo Pro chipset
Jan 22 23:17:10 deepblue kernel: agpgart: AGP aperture is 64M @ 0xe4000000
                                                                  ^-------

rmmod, insmod agpgart:
Jan 22 23:17:16 deepblue kernel: Linux agpgart interface v0.99 (c) Jeff
Hartmann
Jan 22 23:17:16 deepblue kernel: agpgart: Maximum main memory to use for agp
memory: 204M
Jan 22 23:17:16 deepblue kernel: agpgart: Detected Via Apollo Pro chipset
Jan 22 23:17:16 deepblue kernel: agpgart: AGP aperture is 64M @ 0x4000000
                                                                  ^------
Apparently AGP isnt working afterwards.
Someone know what might be causing this?


If you need more information or a want me to help debug this issue further
dont hestitate to tell me.

Since Im not subscribed to the list, please CC any replies to me directly.




Cheers,
Mike


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: AGPGART problems with VIA KX133 chipsets under 2.2.18/2.4.0

[Jeff Hartmann]

[-- Attachment #1: Type: text/plain, Size: 1863 bytes --]

Michael Guntsche wrote:

> Hello all,
> 
> While playing around with the agpgart module I noticed the following strange
> behaviour.
> 
> The hardware in question is an Asus K7V with the KX133 chipset and has been
> tested on both 2.4.0 and 2.2.18 kernels.
> 
> The output below is just from insmod,rmmod,insmod agpgart without starting
> X.
> 
> insmod agpgart for the first time:
> Jan 22 23:17:10 deepblue kernel: Linux agpgart interface v0.99 (c) Jeff
> Hartmann
> Jan 22 23:17:10 deepblue kernel: agpgart: Maximum main memory to use for agp
> memory: 204M
> Jan 22 23:17:10 deepblue kernel: agpgart: Detected Via Apollo Pro chipset
> Jan 22 23:17:10 deepblue kernel: agpgart: AGP aperture is 64M @ 0xe4000000
>                                                                   ^-------
> 
> rmmod, insmod agpgart:
> Jan 22 23:17:16 deepblue kernel: Linux agpgart interface v0.99 (c) Jeff
> Hartmann
> Jan 22 23:17:16 deepblue kernel: agpgart: Maximum main memory to use for agp
> memory: 204M
> Jan 22 23:17:16 deepblue kernel: agpgart: Detected Via Apollo Pro chipset
> Jan 22 23:17:16 deepblue kernel: agpgart: AGP aperture is 64M @ 0x4000000
>                                                                   ^------
> Apparently AGP isnt working afterwards.
> Someone know what might be causing this?
> 
> 
> If you need more information or a want me to help debug this issue further
> dont hestitate to tell me.
> 
> Since Im not subscribed to the list, please CC any replies to me directly.
> 
> 
> 
> 
> Cheers,
> Mike
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/

Can you try this patch and tell me if it fixes the problem (against 2.4.0)?

Apply the patch when in the directory drivers/char/agp.

-Jeff

[-- Attachment #2: via_try_this.diff --]
[-- Type: text/plain, Size: 364 bytes --]

--- agpgart_be.c~	Fri Dec 29 15:07:21 2000
+++ agpgart_be.c	Tue Jan 23 09:45:49 2001
@@ -1384,7 +1384,9 @@
 	aper_size_info_8 *previous_size;
 
 	previous_size = A_SIZE_8(agp_bridge.previous_size);
+#if 0
 	pci_write_config_dword(agp_bridge.dev, VIA_ATTBASE, 0);
+#endif
 	pci_write_config_byte(agp_bridge.dev, VIA_APSIZE,
 			      previous_size->size_value);
 }

Re: AGPGART problems with VIA KX133 chipsets under 2.2.18/2.4.0

[Wayne Whitney]

In mailing-lists.linux-kernel, you wrote:

>Michael Guntsche wrote:
>
>> While playing around with the agpgart module I noticed the following strange
>> behaviour.
>> 
>> The hardware in question is an Asus K7V with the KX133 chipset and has been
>> tested on both 2.4.0 and 2.2.18 kernels.
>
>Can you try this patch and tell me if it fixes the problem (against 2.4.0)?
>
>--- agpgart_be.c~	Fri Dec 29 15:07:21 2000
>+++ agpgart_be.c	Tue Jan 23 09:45:49 2001
>@@ -1384,7 +1384,9 @@
> 	aper_size_info_8 *previous_size;
> 
> 	previous_size = A_SIZE_8(agp_bridge.previous_size);
>+#if 0
> 	pci_write_config_dword(agp_bridge.dev, VIA_ATTBASE, 0);
>+#endif
> 	pci_write_config_byte(agp_bridge.dev, VIA_APSIZE,
> 			      previous_size->size_value);
> }

I have the same hardware as Michael Guntsche, and this patch fixes the
problem for me.

Cheers, Wayne
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: [Dri-devel] Re: AGPGART problems with VIA KX133 chipsets under 2.2.18/2.4.0

[Markus Hadwiger]

Michael Guntsche wrote:
> > While playing around with the agpgart module I noticed the following strange
> > behaviour.
> >
> > The hardware in question is an Asus K7V with the KX133 chipset and has been
> > tested on both 2.4.0 and 2.2.18 kernels.

Jeff Hartmann wrote:
> Can you try this patch and tell me if it fixes the problem (against 2.4.0)?

I tried it out on a VIA Apollo Pro 133A system (Pentium III)
and it seems to work. Previously, I had the same problem as Michael
and only got agpgart to work by temporarily hard-coding the correct
aperture base address in agpgart_be.c.

Thanks,
Markus
--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: [Dri-devel] Re: AGPGART problems with VIA KX133 chipsets under 2.2.18/2.4.0

[Jeff Hartmann]

Markus Hadwiger wrote:

> Michael Guntsche wrote:
> 
>>> While playing around with the agpgart module I noticed the following strange
>>> behaviour.
>>> 
>>> The hardware in question is an Asus K7V with the KX133 chipset and has been
>>> tested on both 2.4.0 and 2.2.18 kernels.
>> 
> 
> Jeff Hartmann wrote:
> 
>> Can you try this patch and tell me if it fixes the problem (against 2.4.0)?
> 
> 
> I tried it out on a VIA Apollo Pro 133A system (Pentium III)
> and it seems to work. Previously, I had the same problem as Michael
> and only got agpgart to work by temporarily hard-coding the correct
> aperture base address in agpgart_be.c.
> 
> Thanks,
> Markus
> --
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/

All the VIA chipsets are pretty much the same so this should fix the 
problem on everyone's system.  I'll send a proper patch to Linus later 
today.

-Jeff

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: AGPGART problems with VIA KX133 chipsets under 2.2.18/2.4.0

[Bob_Tracy]

Congratulations to all involved in fixing the subject problem.  With
the 2.4.1 kernel, I can now actually use agpgart with my GeForce2 MX
on a Tyan S1590S motherboard.  Just thought someone might appreciate
another data point, because prior to 2.4.1 I had to leave out agpgart
support :-(.

--Bob
rct@frus.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/