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: Fri, 16 Nov 2012 08:11:37 +0000 [thread overview]
Message-ID: <bug-56340-8800-M7WeY5dsQq@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-56340-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2126 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=56340
--- Comment #9 from mypersonalmailbox1-O5WfVfzUwx8@public.gmane.org ---
(In reply to comment #7)
Hi Robert,
A few more things I wanted to add.
I believe I updated the BIOS to the last version I was able to obtain from FIC.
FIC has now put their BIOS image behind a password protected FTP site so I no
longer have access to it.
I believe Version JE439 is the last version BIOS they released, and I got it
off their site a few years ago.
The BIOS itself is dated from Year 2000.
I also believe I have changed some of the BIOS settings related to AGP for this
mainboard, but it has made no difference in terms of freeze behavior.
Again, this is a strange problem considering that some NVIDIA RIVA TNT2 64
cards do work fine with the FIC VA-503+ mainboard, but the VisionTek one in
particular doesn't work well (Also, the Dell pulled one doesn't work well,
either.).
Actually, I should also add that I remember seeing an error message
that said something like this with the VisionTek RIVA TNT2 64 graphics card
right before a freeze,
"GPU crash: switching to ShadowFB instead"
What does this type of an error message mean?
I will try to obtain a kern.log file that confirms this error message.
Regards,
fpgahardwareengineer
> (In reply to comment #5)
> > Regarding the reason for the freeze, I can think of the following.
> >
> > - Is Nouveau is accessing the VGA BIOS of the card during boot, and the VGA
> > BIOS is a little buggy?
> > - Does the VGA BIOS's initialization code configuring RIVA TNT2 64 in a
> > certain way that contributes to the freeze with Apollo MVP3 chipset?
>
> I would suspect the latter - these old VIA AGP implementations were
> notoriously unstable and problematic even in Windows and it's not unlikely
> that different BIOS versions may configure the card differently (AGP 2X/4X,
> AGP fast writes on/off, etc.)
>
> You can also try updating the motherboard BIOS and try playing with any
> AGP-related BIOS settings to see if they change the situation.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3216 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-16 8:11 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 [this message]
2012-11-17 3:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-17 5:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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-M7WeY5dsQq@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