From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 56340] [Ubuntu 10.04.4 LTS 32-bit] Severe instability of VIA Technologies Apollo MVP3 chipset and NVIDIA RIVA TNT2 M64 graphics
Date: Sat, 17 Nov 2012 05:45:58 +0000 [thread overview]
Message-ID: <bug-56340-8800-G6jezhgkKB@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-56340-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 848 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=56340
--- Comment #11 from Robert Hancock <hancockrwd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
Most likely in 2X mode some of the data transfers to/from the card are getting
corrupted somehow, causing the GPU to not respond as expected and causing the
lockup detection.
I believe that for AGP problems on VIA chipsets, some people had luck with
playing with the "AGP Driving Value" setting in the BIOS, if you have such an
option you can try using different settings for this. (As I recall, most AGP
chipsets would handle this setting automatically but the crappy VIA AGP
implementation used a BIOS setting which sometimes required the user to enter a
different value in the hope it would get the card to work properly.)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1767 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2012-11-17 5:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 4:21 [Bug 56340] New: [Ubuntu 10.04.4 LTS 32-bit] Severe instability of VIA Technologies Apollo MVP3 chipset and NVIDIA RIVA TNT2 M64 graphics bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-56340-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2012-10-24 4:22 ` [Bug 56340] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-10-24 4:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-10-24 4:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-10-26 14:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-05 4:06 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-05 4:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-05 11:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-14 2:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-16 1:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-16 8:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-17 3:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-17 5:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2012-11-17 7:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-21 5:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-21 5:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-21 5:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-21 5:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-21 5:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-25 15:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-25 15:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-23 15:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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=bug-56340-8800-G6jezhgkKB@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox