From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 27952] New: Screen garbled with GeForce 6150 Force 430
Date: Tue, 14 Aug 2012 15:56:22 +0000 (UTC) [thread overview]
Message-ID: <bug-27952-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=27952
Summary: Screen garbled with GeForce 6150 Force 430
Product: Drivers
Version: 2.5
Platform: All
OS/Version: Linux
Tree: Mainline
Status: RESOLVED
Severity: high
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri@kernel-bugs.osdl.org
ReportedBy: Larry.Finger@lwfinger.net
CC: alan@lxorguk.ukuu.org.uk
Regression: No
Alan <alan@lxorguk.ukuu.org.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |alan@lxorguk.ukuu.org.uk
Resolution| |OBSOLETE
Created an attachment (id=45702)
--> (https://bugzilla.kernel.org/attachment.cgi?id=45702)
Dmesg output with nouveau enabled
With kernel 2.6.38-rc2-Linus-00324-g70d1f36 (and earlier), running without a
"nomodeset" option in the boot line results in a screen that appears to be
sheared. From the colors, etc., it appears to be nearly correct.
The lspci -nnkx output for the device is:
00:0d.0 VGA compatible controller [0300]: nVidia Corporation C61 [GeForce
6150SE nForce 430] [10de:03d0] (rev a2)
Subsystem: Micro-Star International Co., Ltd. Device [1462:7309]
00: de 10 d0 03 07 00 b0 00 a2 00 00 03 00 00 00 00
10: 00 00 00 de 0c 00 00 c0 00 00 00 00 04 00 00 dd
20: 00 00 00 00 00 00 00 00 00 00 00 00 62 14 09 73
30: 00 00 e4 df 48 00 00 00 00 00 00 00 0a 01 00 00
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
reply other threads:[~2012-08-14 15:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-27952-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.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