Hi,
On 24 Jan 2005, at 19:41, rodrigo ahumada wrote:
On Mon, 24 Jan 2005 19:19:59 +0000 Chris Boot <[EMAIL PROTECTED]> wrote:
(i know that it's not exactly the same problem, but can help...)
If I change the driver from 'nvidia' to 'vesa' everything works fine, except I obviously can't configure TV and it's slow.
lspci -v output for my card: 0000:01:00.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX 4000 AGP 8x] (rev c1) (prog-if 00 [VGA]) Flags: bus master, 66Mhz, medium devsel, latency 248, IRQ 201 Memory at dc000000 (32-bit, non-prefetchable) Memory at d0000000 (32-bit, prefetchable) [size=128M] Capabilities: [60] Power Management version 2 Capabilities: [44] AGP version 3.0
Every time I start X using the nvidia driver the kernel says: agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0. agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
in the README of official drivers says that nvidia has conflicts with agpgart and nvagp,
when i was using ubuntu, when nvidia,agpgart & nvagp loaded, the whole system hanged after a second startx.
right now in gentoo i got agpgart loaded but it seems being not used and have no problems:
"To use the Linux AGPGART module, it will need to be compiled with
your kernel, either statically linked in, or built as a module.
NVIDIA AGP support cannot be used if AGPGART is loaded in the kernel.
It is recommended that you compile AGPGART as a module and make sure that
it is not loaded when trying to use NVIDIA AGP."
there's some options for nvidia all in the README, so you can try with the official drivers:
Option "NvAGP" "integer"
Configure AGP support. Integer argument can be one of:
0 : disable agp
1 : use NVIDIA's internal AGP support, if possible
2 : use AGPGART, if possible
3 : use any agp support (try AGPGART, then NVIDIA's AGP)
Please note that NVIDIA's internal AGP support cannot
work if AGPGART is either statically compiled into your
kernel or is built as a module, but loaded into your
kernel (some distributions load AGPGART into the kernel
at boot up). Default: 3 (the default was 1 until after
1.0-1251).
I must admit I haven't tried with NvAGP, but that seems unlikely since it isn't a crashing problem, rather just what seems like either a bug or configuration problem. I'm edging towards the bug option, especially since the 1.0.6111 drivers seem to work fine at the moment. If you think otherwise I'll give it a go!
Thanks, Chris
-- Chris Boot [EMAIL PROTECTED] http://www.bootc.net/
-- [email protected] mailing list
