All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Grzesiek Sójka" <pld-t9zbU3WrWHI@public.gmane.org>
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: AMD768 & GeForce5200: nouveau bug??
Date: Mon, 27 Sep 2010 10:44:47 +0200	[thread overview]
Message-ID: <4CA0597F.80109@pfu.pl> (raw)
In-Reply-To: <8739syrins.fsf-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org>

On 09/24/10 22:27, Francisco Jerez wrote:
> Grzesiek Sójka<pld-t9zbU3WrWHI@public.gmane.org>  writes:
>
>> Hi there,
>>
>> 	Im using ASUS A7M266-D mainboard based on AMD768 chipset and Nvidia
>> GeForce FX5200 dual DVI graphics adapter. I'm forced to switch from
>> binary Nvidia drivers to nouveau but the problem is that nouveau.ko
>> would not load with AGP support turned on. Is it a nouveau/kernel bug??
>> 	To build the kernel I used the kernel tree downloaded from the nouveau
>> repository about a week ago. The dmesg output with/without the AGP
>> support you can find at:
>> http://yen.ipipan.waw.pl/~gs159090/tmp/withAGP.txt.gz
>> http://yen.ipipan.waw.pl/~gs159090/tmp/withoutAGP.txt.gz
>> And here is lspci -vv output
>> http://yen.ipipan.waw.pl/~gs159090/tmp/lspci-vv.txt.gz
>>
>> Thanks in advance for any help.
>
> That looks like a bug in the amdk7 agp driver, can you give this patch a
> try?
The patch from Francisco Jerez works fine for me so I was wondering what 
to do next. It would be nice to apply it to the official kernel tree. 
Should I open a bug?? Write to someone??

      parent reply	other threads:[~2010-09-27  8:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-24 14:37 AMD768 & GeForce5200: nouveau bug?? Grzesiek Sójka
     [not found] ` <4C9CB7B2.3010401-t9zbU3WrWHI@public.gmane.org>
2010-09-24 20:27   ` Francisco Jerez
     [not found]     ` <8739syrins.fsf-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org>
2010-09-27  8:44       ` Grzesiek Sójka [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CA0597F.80109@pfu.pl \
    --to=pld-t9zbu3wrwhi@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.