nforce2 and agpgart
I'm having trouble getting agpgart support to work with an nforce2 chipset. Is this supported on any kernels? I'm running a Redhat 7.1 system with Redhat's 2.4.9-21 kernel.
Signature · 11 lines
Carl D. Blake Director of Engineering Boeckeler Instruments, Inc. 4650 S. Butterfield Dr. Tucson, AZ 85714 Phone: 520-745-0001 FAX: 520-745-0004 email: [email protected] .com
Quoted 3 lines · Carl D. Blake
I'm having trouble getting agpgart support to work with an nforce2 chipset. Is this supported on any kernels? I'm running a Redhat 7.1 system with Redhat's 2.4.9-21 kernel.
Try to use a newer kernel from Redhat, because that kernel was around looong before nforce was released. IIRC support for nforce2 was added around 2.4.19
Signature · 5 lines
For future reference - don't anybody else try to send patches as vi
scripts, please. Yes, it's manly, but let's face it, so is
bungee-jumping with the cord tied to your testicles.
-- LinusQuoted 9 lines · Bongani Hlope
Quoted 3 lines · Carl D. Blake
I'm having trouble getting agpgart support to work with an nforce2 chipset. Is this supported on any kernels? I'm running a Redhat 7.1 system with Redhat's 2.4.9-21 kernel.
Try to use a newer kernel from Redhat, because that kernel was around looong before nforce was released. IIRC support for nforce2 was added around 2.4.19
I just upgraded to the 2.4.18 kernel provided by Redhat and it didn't make any difference. The message I get in dmesg is:
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: unsupported bridge
agpgart: no supported devices found.
You suggested trying 2.4.19, so I downloaded kernel 2.4.20 from kernel.org and compared its agp code (drivers/char/agp) with the code in 2.4.18. There are a few differences - such as supporting AMD 8151 - but nothing that indicates improved support for agpgart on the nforce2 chipset. The changelog for 2.4.20 indicated some added support for the nforce2 chipset, but that seems to be support for the audio and network portions of the chipset, not agp. I was able to incorporate the audio changes manually for kernel 2.4.18 by using Nvidia's patches, but I can't get agp to work.
Any other suggestions? Thanks for your help.
Quoted 6 lines
Signature · 5 lines
For future reference - don't anybody else try to send patches as vi scripts, please. Yes, it's manly, but let's face it, so is bungee-jumping with the cord tied to your testicles. -- Linus
Signature · 11 lines
Carl D. Blake Director of Engineering Boeckeler Instruments, Inc. 4650 S. Butterfield Dr. Tucson, AZ 85714 Phone: 520-745-0001 FAX: 520-745-0004 email: [email protected] .com
Quoted 29 lines · Carl D. Blake
Quoted 9 lines · Bongani Hlope
Quoted 3 lines · Carl D. Blake
I'm having trouble getting agpgart support to work with an nforce2 chipset. Is this supported on any kernels? I'm running a Redhat 7.1 system with Redhat's 2.4.9-21 kernel.
Try to use a newer kernel from Redhat, because that kernel was around looong before nforce was released. IIRC support for nforce2 was added around 2.4.19
I just upgraded to the 2.4.18 kernel provided by Redhat and it didn't make any difference. The message I get in dmesg is:
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: unsupported bridge
agpgart: no supported devices found.You suggested trying 2.4.19, so I downloaded kernel 2.4.20 from kernel.org and compared its agp code (
drivers/char/agp) with the code in 2.4.18. There are a few differences - such as supporting AMD 8151 - but nothing that indicates improved support for agpgart on the nforce2 chipset. The changelog for 2.4.20 indicated some added support for the nforce2 chipset, but that seems to be support for the audio and network portions of the chipset, not agp. I was able to incorporate the audio changes manually for kernel 2.4.18 by using Nvidia's patches, but I can't get agp to work.
Quoted 1 line
Any other suggestions? Thanks for your help.
Disclaimer at the bottom. ;)
It was once posted on this list that the NForce is similar to some existing hardware. hence the sound driver uses the Intel i810 audio driver. I guess if you can search through the archive you might find that discussion. If you do find it and _are_ clued-up enough, then you can look at drivers/char/agp/agpgart_be.c approximately line 3900 they start defining which drivers to use for which bus.
So you need to
1. Find the id for the AGP bus for the NForce and define it in agp.h (lspci should do the trick IIRC on my PC 00:01.0 is the agp bus)
2. Find out which hardware the bus is similar to, then add the support for the NForce using the setup for that driver
e.g.
agp.h
add
#ifndef PCI_DEVICE_ID_NVIDIA_NFORCORCE_2 //I'm not sure about the
naming standard
#define PCI_DEVICE_ID_NVIDIA_NFORCORCE_2 0x(Hex value from lspci)
#endif
the in agpgart_be.c
add (for example lets say the bus is similar to Intel's i860 agp bus then)
#ifdef CONFIG_AGP_INTEL
...
{ PCI_DEVICE_ID_NVIDIA_NFORCORCE_2,
PCI_VENDOR_ID_NVIDIA,
INTEL_I860,
"NVidia",
"NForce2",
intel_860_setup },....
#endif /* CONFIG_AGP_INTEL */
DISCLAIMER : I do not know anything about the agp code, except for what I have read when trying to find a solution for you. The examples above are from what my eyes came across at 1:00 am without prio knowledge to the agp code. So if you implement these examples you do it at you own (and maybe your pets) risk. The examples come with.... you should now how the rest goes ;)
Signature · 5 lines
For future reference - don't anybody else try to send patches as vi
scripts, please. Yes, it's manly, but let's face it, so is
bungee-jumping with the cord tied to your testicles.
-- LinusOn Mon, 2002-12-23 at 16:19, Bongani Hlope wrote:
...snip...
Quoted 8 lines
It was once posted on this list that the NForce is similar to some existing hardware. hence the sound driver uses the Intel i810 audio driver. I guess if you can search through the archive you might find that discussion. If you do find it and _are_ clued-up enough, then you can look at
drivers/char/agp/agpgart_be.capproximately line 3900 they start defining which drivers to use for which bus.
This sounds like a possibility. However, I cannot find any discussion about what hardware the nforce2 chipset is similar to. I just need to know if the agp portion of the chipset is similar to something else. Can anybody point to that information? From what I can determine the device that is used is the host bridge.
Quoted 46 lines
So you need to
1. Find the id for the AGP bus for the NForce and define it inagp.h(lspci should do the trick IIRC on my PC 00:01.0 is the agp bus)
2. Find out which hardware the bus is similar to, then add the support for the NForce using the setup for that driver
e.g.
agp.hadd
#ifndefPCI_DEVICE_ID_NVIDIA_NFORCORCE_2//I'm not sure about the
naming standard
#definePCI_DEVICE_ID_NVIDIA_NFORCORCE_20x(Hex value from lspci)
#endifthe in
agpgart_be.cadd (for example lets say the bus is similar to Intel's i860 agp bus then)
#ifdef
CONFIG_AGP_INTEL
...{
PCI_DEVICE_ID_NVIDIA_NFORCORCE_2,PCI_VENDOR_ID_NVIDIA, INTEL_I860, "NVidia", "NForce2", intel_860_setup },....
#endif /*CONFIG_AGP_INTEL*/DISCLAIMER : I do not know anything about the agp code, except for what I have read when trying to find a solution for you. The examples above are from what my eyes came across at 1:00 am without prio knowledge to the agp code. So if you implement these examples you do it at you own (and maybe your pets) risk. The examples come with.... you should now how the rest goes ;)
Signature · 5 lines
For future reference - don't anybody else try to send patches as vi scripts, please. Yes, it's manly, but let's face it, so is bungee-jumping with the cord tied to your testicles. -- Linus
Signature · 11 lines
Carl D. Blake Director of Engineering Boeckeler Instruments, Inc. 4650 S. Butterfield Dr. Tucson, AZ 85714 Phone: 520-745-0001 FAX: 520-745-0004 email: [email protected] .com
Carl,
Are you using the onboard IDE controller for your hard disk? If so, please check to see if DMA is enabled or not.
Jeff
----- Original Message -----
From: "Carl D. Blake" <[email protected]>
To: <[email protected]>
Sent: Monday, December 23, 2002 2:40 PM
Subject: Re: nforce2 and agpgart
Quoted 55 lines · Bongani Hlope
Quoted 9 lines · Carl D. Blake
Quoted 3 lines
I'm having trouble getting agpgart support to work with an nforce2 chipset. Is this supported on any kernels? I'm running a Redhat 7.1 system with Redhat's 2.4.9-21 kernel.
Try to use a newer kernel from Redhat, because that kernel was around looong before nforce was released. IIRC support for nforce2 was added around 2.4.19
I just upgraded to the 2.4.18 kernel provided by Redhat and it didn't make any difference. The message I get in dmesg is:
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: unsupported bridge
agpgart: no supported devices found.You suggested trying 2.4.19, so I downloaded kernel 2.4.20 from kernel.org and compared its agp code (
drivers/char/agp) with the code in 2.4.18. There are a few differences - such as supporting AMD 8151 - but nothing that indicates improved support for agpgart on the nforce2 chipset. The changelog for 2.4.20 indicated some added support for the nforce2 chipset, but that seems to be support for the audio and network portions of the chipset, not agp. I was able to incorporate the audio changes manually for kernel 2.4.18 by using Nvidia's patches, but I can't get agp to work.Any other suggestions? Thanks for your help.
Quoted 6 lines
--
For future reference - don't anybody else try to send patches as vi scripts, please. Yes, it's manly, but let's face it, so is bungee-jumping with the cord tied to your testicles.-- Linus
--
Carl D. Blake
Director of Engineering
Boeckeler Instruments, Inc.
4650 S. Butterfield Dr.
Tucson, AZ 85714Phone: 520-745-0001
FAX: 520-745-0004
email: [email protected].com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Quoted 7 lines · Jeff Nguyen
Carl,
Are you using the onboard IDE controller for your hard disk? If so, please check to see if DMA is enabled or not.
Jeff
I am using the onboard IDE controller and DMA is enabled.
Quoted 68 lines
----- Original Message -----
From: "Carl D. Blake" <[email protected]>
To: <[email protected]>
Sent: Monday, December 23, 2002 2:40 PM
Subject: Re: nforce2 and agpgartQuoted 47 lines · Bongani Hlope
Quoted 9 lines · Carl D. Blake
Quoted 3 lines
I'm having trouble getting agpgart support to work with an nforce2 chipset. Is this supported on any kernels? I'm running a Redhat 7.1 system with Redhat's 2.4.9-21 kernel.
Try to use a newer kernel from Redhat, because that kernel was around looong before nforce was released. IIRC support for nforce2 was added around 2.4.19
I just upgraded to the 2.4.18 kernel provided by Redhat and it didn't make any difference. The message I get in dmesg is:
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: unsupported bridge
agpgart: no supported devices found.You suggested trying 2.4.19, so I downloaded kernel 2.4.20 from kernel.org and compared its agp code (
drivers/char/agp) with the code in 2.4.18. There are a few differences - such as supporting AMD 8151 - but nothing that indicates improved support for agpgart on the nforce2 chipset. The changelog for 2.4.20 indicated some added support for the nforce2 chipset, but that seems to be support for the audio and network portions of the chipset, not agp. I was able to incorporate the audio changes manually for kernel 2.4.18 by using Nvidia's patches, but I can't get agp to work.Any other suggestions? Thanks for your help.
Quoted 6 lines
--
For future reference - don't anybody else try to send patches as vi scripts, please. Yes, it's manly, but let's face it, so is bungee-jumping with the cord tied to your testicles.-- Linus
--
Carl D. Blake
Director of Engineering
Boeckeler Instruments, Inc.
4650 S. Butterfield Dr.
Tucson, AZ 85714Phone: 520-745-0001
FAX: 520-745-0004
email: [email protected]Quoted 8 lines
.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Signature · 11 lines
Carl D. Blake Director of Engineering Boeckeler Instruments, Inc. 4650 S. Butterfield Dr. Tucson, AZ 85714 Phone: 520-745-0001 FAX: 520-745-0004 email: [email protected] .com
A message that is not in the archive (sent off-list or not yet received): 1040928705.6372.27.camel@vulcan
A message that is not in the archive (sent off-list or not yet received): 086101c2ad18$46fea8b0$6502a8c0@jeff
Quoted 3 lines · Jeff Nguyen
That's strange because my Red Hat kernel did not enable DMA. Did you have to run hdparam to change the IDE setting?
Yes, I had to run hdparm to setup the IDE hard drive for maximum performance.
Quoted 110 lines
Jeff
----- Original Message -----
From: "Carl D. Blake" <[email protected]>
To: "Jeff Nguyen" <[email protected]>
Sent: Thursday, December 26, 2002 10:51 AM
Subject: Re: nforce2 and agpgartQuoted 22 lines · Jeff Nguyen
Quoted 7 lines
Carl,
Are you using the onboard IDE controller for your hard disk? If so, please check to see if DMA is enabled or not.
Jeff
I am using the onboard IDE controller and DMA is enabled.
Quoted 11 lines
----- Original Message -----
From: "Carl D. Blake" <[email protected]>
To: <[email protected]>
Sent: Monday, December 23, 2002 2:40 PM
Subject: Re: nforce2 and agpgartQuoted 4 lines · Bongani Hlope
Quoted 3 lines · Carl D. Blake
Quoted 2 lines
I'm having trouble getting agpgart support to work with an nforce2 chipset. Is this supported on any kernels? I'm running a Redhat
7.1
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line
system with Redhat's 2.4.9-21 kernel.
Try to use a newer kernel from Redhat, because that kernel was
around
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
looong before nforce was released. IIRC support for nforce2 was
added
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 2 lines
around 2.4.19
I just upgraded to the 2.4.18 kernel provided by Redhat and it didn't make any difference. The message I get in dmesg is:
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: unsupported bridge
agpgart: no supported devices found.You suggested trying 2.4.19, so I downloaded kernel 2.4.20 from kernel.org and compared its agp code (
drivers/char/agp) with the codein
Quoted 1 line
Quoted 1 line
Quoted 1 line
2.4.18. There are a few differences - such as supporting AMD 8151 -
but
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
nothing that indicates improved support for agpgart on the nforce2 chipset. The changelog for 2.4.20 indicated some added support for
the
Quoted 1 line
Quoted 1 line
Quoted 1 line
nforce2 chipset, but that seems to be support for the audio and
network
Quoted 18 lines
Quoted 18 lines
Quoted 18 lines
portions of the chipset, not agp. I was able to incorporate the audio changes manually for kernel 2.4.18 by using Nvidia's patches, but I can't get agp to work.
Any other suggestions? Thanks for your help.
Quoted 6 lines
--
For future reference - don't anybody else try to send patches as vi scripts, please. Yes, it's manly, but let's face it, so is bungee-jumping with the cord tied to your testicles.-- Linus
--
Carl D. Blake
Director of Engineering
Boeckeler Instruments, Inc.
4650 S. Butterfield Dr.
Tucson, AZ 85714Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Phone: 520-745-0001
FAX: 520-745-0004
email: [email protected].com
-
To unsubscribe from this list: send the line "unsubscribelinux-kernel" in
Quoted 7 lines
Quoted 7 lines
Quoted 4 lines
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"in
Quoted 16 lines
Quoted 3 lines
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/--
Carl D. Blake
Director of Engineering
Boeckeler Instruments, Inc.
4650 S. Butterfield Dr.
Tucson, AZ 85714Phone: 520-745-0001
FAX: 520-745-0004
email: [email protected].com
Signature · 11 lines
Carl D. Blake Director of Engineering Boeckeler Instruments, Inc. 4650 S. Butterfield Dr. Tucson, AZ 85714 Phone: 520-745-0001 FAX: 520-745-0004 email: [email protected] .com