From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 54587] New: Flickering screen on Geforece 4
Date: Thu, 06 Sep 2012 09:00:59 +0000 [thread overview]
Message-ID: <bug-54587-8800@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=54587
Bug #: 54587
Summary: Flickering screen on Geforece 4
Classification: Unclassified
Product: xorg
Version: unspecified
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: critical
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: piip-O5WfVfzUwx8@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
I have Geforce 4 display adapter. I updated Ubuntu from 10.04 LTS to 12.04.01
LTS. I was using proprietary Nvidia driver with 10.04. Now it is no more
supported with 12.04. Also NV driver is not supported. I try to use Nouveau,
but my screen flickers so badly that it is not usable. I am using the same
resolution and refresh rate as with 10.04. I have to continue using 10.04 until
this bug is fixed. I am not alone with this problem. Read this description:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/575092
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2012-09-06 9:00 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 9:00 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-54587-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2012-09-06 17:45 ` [Bug 54587] Flickering screen on Geforece 4 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-07 12:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-07 12:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-07 12:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-07 13:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-07 19:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-08 9:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-08 13:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-09 5:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-09 5:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-09 5:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-09 5:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-09 5:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-09 10:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-09 21:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-10 11:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-10-02 18:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-10-06 11:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-10-07 11:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-05 8:24 ` [Bug 54587] [NV1F] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-08 8:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-08 8:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-08 8:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-08 8:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-08 9:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-08 13:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-08 15:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-08 20:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-09 8:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-09 8:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-09 8:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-10 12:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-10 12:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-17 1:34 ` [Bug 54587] [NV1F] Flickering screen on Geforce 4 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-06-03 4:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-06-03 4:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 8:29 ` 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-54587-8800@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 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.