From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 14610] New: corrupted nouveau screen output
Date: Thu, 21 Feb 2008 15:42:31 -0800 (PST) [thread overview]
Message-ID: <bug-14610-8800@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=14610
Summary: corrupted nouveau screen output
Product: xorg
Version: 7.3
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: fabian-x5yzbtgCVuVsET1BNAyrpg@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
128 MB GDDR SDRAM; nVIDIA Quadro NVS 140M
03:00.0 Network controller [0280]: Intel Corporation Unknown device [8086:4230]
(rev 61)
Subsystem: Intel Corporation Unknown device [8086:1111]
build nouveau with gentoo-ebuild from here:
http://nouveau.freedesktop.org/wiki/GentooEbuilds?highlight=%28gentoo%29
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2008-02-21 23:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 23:42 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-14610-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2008-02-21 23:43 ` [Bug 14610] corrupted nouveau screen output bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-02-21 23:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-03-07 19:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-03-07 20:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-03-18 4:30 ` 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-14610-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.