** Changed in: nouveau
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/539730
Title:
[G72M] Screen corruption when using KMS. Dell Latitude D620 / Quadro
NVS
** Changed in: nouveau
Importance: Medium = Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/539730
Title:
[G72M] Screen corruption when using KMS. Dell Latitude D620 / Quadro
NVS
** Branch linked: lp:ubuntu/linux-mvl-dove
--
[G72M] Screen corruption when using KMS. Dell Latitude D620 / Quadro NVS
110M/GeForce Go 7300
https://bugs.launchpad.net/bugs/539730
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Branch linked: lp:ubuntu/linux-ec2
--
[G72M] Screen corruption when using KMS. Dell Latitude D620 / Quadro NVS
110M/GeForce Go 7300
https://bugs.launchpad.net/bugs/539730
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: linux (Ubuntu)
Status: Triaged = In Progress
** Changed in: linux (Ubuntu)
Status: In Progress = Fix Committed
** Changed in: linux (Ubuntu)
Milestone: ubuntu-10.04-beta-2 = ubuntu-10.04
--
[G72M] Screen corruption when using KMS. Dell Latitude D620 / Quadro
This bug was fixed in the package linux - 2.6.32-21.31
---
linux (2.6.32-21.31) lucid; urgency=low
[ Andy Whitcroft ]
* allow modules.builtin to be optional
* d-i: add mpt2sas to the message-modules udeb
- LP: #530361
[ Christopher James Halse Rogers ]
* SAUCE:
@Scott -- I have pulled this back to the lucid kernel, could you test
these ones and report back here:
http://people.canonical.com/~apw/lp539730-lucid/
--
[G72M] Screen corruption when using KMS. Dell Latitude D620 / Quadro NVS
110M/GeForce Go 7300
https://bugs.launchpad.net/bugs/539730
On Thu, 2010-04-08 at 11:52 +, Andy Whitcroft wrote:
@Scott -- I have pulled this back to the lucid kernel, could you test
these ones and report back here:
http://people.canonical.com/~apw/lp539730-lucid/
Worked fine once I purged the tendrils of xorg-edgers from the system
Scott
On Tue, 2010-04-06 at 14:12 +, Scott James Remnant wrote:
On Tue, 2010-03-30 at 22:52 +, Chris Halse Rogers wrote:
This now has a commit upstream:
http://cgit.freedesktop.org/nouveau/linux-2.6/commit/?id=8af36117e23bc36c34d0d25484f7b9de021b51bc
This commit is in the
On Tue, 2010-03-30 at 22:52 +, Chris Halse Rogers wrote:
This now has a commit upstream:
http://cgit.freedesktop.org/nouveau/linux-2.6/commit/?id=8af36117e23bc36c34d0d25484f7b9de021b51bc
This commit is in the linux-backports-modules-nouveau package in xorg-
edgers that will be built
This now has a commit upstream:
http://cgit.freedesktop.org/nouveau/linux-2.6/commit/?id=8af36117e23bc36c34d0d25484f7b9de021b51bc
This commit is in the linux-backports-modules-nouveau package in xorg-
edgers that will be built soon; Scott, would it be possible for you to
test that the packages in
I'm trying to live boot beta1 of Lucid on a similar D620. Both the
amd64 and i386 desktop CDs give me same results. X is using the wrong
scan rates so I am unable to use the system.
The system works fine with Interpid i386 and Karmic amd64 (Live and
installed).
Is this the same issue?
--
Not sure whether it's related, but I've got a PC with a GeForce GT220, which
shows the following behavior on 10.04 Alpha 3:
1. During boot, output is sent both to VGA and DVI
2. after modprobe nouveau, or after starting up X, output is sent only to DVI.
While usable output is sent to DVI,
On Fri, 2010-03-19 at 14:14 +, AlainKnaff wrote:
The full lspci id of the card is:
02:00.0 VGA compatible controller: nVidia Corporation GT216 [GeForce GT 220]
(rev a2)
You have a different card, so you have a different bug.
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
[G72M]
** Changed in: xserver-xorg-video-nouveau (Ubuntu)
Status: New = Confirmed
--
[G72M] Screen corruption when using KMS. Dell Latitude D620 / Quadro NVS
110M/GeForce Go 7300
https://bugs.launchpad.net/bugs/539730
You received this bug notification because you are a member of Ubuntu
Bugs,
I have a very similar problem. When trying to boot Lucid post alpha 3, the
display shuts down after start of a boot, and turns on after a wile with
corrupted screen (desktop wallpaper mashed up with other colors), and I don't
hear the login sound, and can't see and use mouse or panels,
Here is the xorg.log while in vesa.
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/41118880/Xorg.0.log
--
[G72M] Screen corruption when using KMS. Dell Latitude D620 / Quadro NVS
110M/GeForce Go 7300
https://bugs.launchpad.net/bugs/539730
You received this bug notification
lspci -vvnn
** Attachment added: lspci.txt
http://launchpadlibrarian.net/41118941/lspci.txt
--
[G72M] Screen corruption when using KMS. Dell Latitude D620 / Quadro NVS
110M/GeForce Go 7300
https://bugs.launchpad.net/bugs/539730
You received this bug notification because you are a member of
dmesg
** Attachment added: dmesg.txt
http://launchpadlibrarian.net/41118949/dmesg.txt
--
[G72M] Screen corruption when using KMS. Dell Latitude D620 / Quadro NVS
110M/GeForce Go 7300
https://bugs.launchpad.net/bugs/539730
You received this bug notification because you are a member of
correction : I can see the mouse withe modest=1, but can't move it.
--
[G72M] Screen corruption when using KMS. Dell Latitude D620 / Quadro NVS
110M/GeForce Go 7300
https://bugs.launchpad.net/bugs/539730
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On Wed, 2010-03-17 at 12:26 +, Ivan Katanović wrote:
System with vesa loaded. The laptop is Acer Extensa 5635G with Nvidia G 105M.
Since the card isn't identical, this may be a different bug with the
same symptoms
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
[G72M] Screen
** Changed in: xserver-xorg-video-nouveau (Ubuntu)
Importance: Undecided = High
--
[G72M] Screen corruption when using KMS. Dell Latitude D620 / Quadro NVS
110M/GeForce Go 7300
https://bugs.launchpad.net/bugs/539730
You received this bug notification because you are a member of Ubuntu
Bugs,
** Bug watch added: freedesktop.org Bugzilla #27152
https://bugs.freedesktop.org/show_bug.cgi?id=27152
** Also affects: nouveau via
https://bugs.freedesktop.org/show_bug.cgi?id=27152
Importance: Unknown
Status: Unknown
--
[G72M] Screen corruption when using KMS. Dell Latitude
** Changed in: nouveau
Status: Unknown = Confirmed
--
[G72M] Screen corruption when using KMS. Dell Latitude D620 / Quadro NVS
110M/GeForce Go 7300
https://bugs.launchpad.net/bugs/539730
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Summary changed:
- Nothing useful on screen. Dell Latitude D620. nVidia Corporation G72M
[Quadro NVS 110M/GeForce Go 7300]
+ [G72M] Screen corruption when using KMS. Dell Latitude D620 / Quadro NVS
110M/GeForce Go 7300
--
[G72M] Screen corruption when using KMS. Dell Latitude D620 /
I don't think X is hung at all; here's the ps output, everything looks
normal
And here's what X is doing:
r...@mario:~# cat /proc/1000/wchan
poll_schedule_timeout
** Attachment added: ps output while in that state
http://launchpadlibrarian.net/41045660/ps.log
--
[G72M] Screen corruption
Here's a photo of what plymouth renders to the framebuffer. This is
supposed to be the ubuntu logo mid-way on a purple screen.
Odd how the explosion of white (which could be the logo) is rotated 90
degrees, then offset midway up the screen.
If you applied the same logic to the other photo, the
With modeset=0 it looks like it's falling back to -vesa, which explains
the wrong resolution (since it is not doing any modesetting in that
case, just using VESA defaults.)
--
[G72M] Screen corruption when using KMS. Dell Latitude D620 / Quadro NVS
110M/GeForce Go 7300
Bryce asked for the xrandr --verbose output while in -vesa
Screen 0: minimum 800 x 600, current 1024 x 768, maximum 1024 x 768
default connected 1024x768+0+0 (0x108) normal (normal) 0mm x 0mm
Identifier: 0x107
Timestamp: 15051
Subpixel: unknown
Clones:
This chunk at the end of the Xorg.0.log looks interesting:
(II) NOUVEAU(0): EDID vendor LPL, prod id 224
(II) NOUVEAU(0): DDCModeFromDetailedTiming: 1440x900 Warning: We only handle
separate sync.
(II) NOUVEAU(0): Printing DDC gathered Modelines:
(II) NOUVEAU(0): Modeline 1440x900x0.0 88.89
default connected 1024x768+0+0 (0x108) normal (normal) 0mm x 0mm
Hmm, normally it would have the proper dimensions. That it's showing
0mm x 0mm is quite interesting. The Xorg.0.log has correct info so not
sure why xrandr would be seeing it as 0. Something smells wrong here.
--
[G72M] Screen
This is ssh'd in while the corruption is on screen - not sure if that's
right or not
r...@mario:~# DISPLAY=:0 get-edid | parse-edid
get-edid: get-edid version 2.0.0
Performing real mode VBE call
Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
parse-edid: parse-edid version 2.0.0
Confirming that switching from the -generic-pae kernel to just -generic
makes no difference
--
[G72M] Screen corruption when using KMS. Dell Latitude D620 / Quadro NVS
110M/GeForce Go 7300
https://bugs.launchpad.net/bugs/539730
You received this bug notification because you are a member of
mjg59 says that -vesa just doesn't have edid hooked up, thus the 0mm x
0mm. False alarm.
VBE call failed Rats.
Anyway, my guess is that something's wrong with your EDID, but without
being able to actually see it I can't be sure. It could just be a
general modesetting issue, or even just some
r...@mario:~# parse-edid /sys/class/drm//card0-LVDS-1/edid
parse-edid: parse-edid version 2.0.0
parse-edid: EDID checksum passed.
# EDID version 1 revision 3
Section Monitor
# Block type: 2:0 3:fe
# Block type: 2:0 3:fe
Identifier LPL:e000
VendorName LPL
r...@mario:~# cat /sys/class/drm//card0-LVDS-1/modes
1440x900
1152x864
1024x768
800x600
640x480
720x400
640x400
640x350
r...@mario:~# cat /sys/class/drm//card0-LVDS-1/status
connected
--
[G72M] Screen corruption when using KMS. Dell Latitude D620 / Quadro NVS
110M/GeForce Go 7300
airlied suggested dmesg from a boot with modeset=1 would be useful, here
it is
** Attachment added: dmesg from boot with mode setting
http://launchpadlibrarian.net/41056030/dmesg.log
--
[G72M] Screen corruption when using KMS. Dell Latitude D620 / Quadro NVS
110M/GeForce Go 7300
dmesg without vga16fb joining the party
** Attachment added: demsg
http://launchpadlibrarian.net/41056521/dmesg.log
--
[G72M] Screen corruption when using KMS. Dell Latitude D620 / Quadro NVS
110M/GeForce Go 7300
https://bugs.launchpad.net/bugs/539730
You received this bug notification
mjg59 The gradual whiting out means that the LVDS isn't being driven correctly
Might be worth dumping your video bios as well
He may want the scripts
mjg59 dd if=/dev/mem of=video.bios bs=65536 count=1 skip=12
** Attachment added: video.bios
http://launchpadlibrarian.net/41058076/video.bios
mmiotrace of nvidia-glx
** Attachment added: nvidia-glx_trace
http://launchpadlibrarian.net/41072914/nvidia-glx_trace
--
[G72M] Screen corruption when using KMS. Dell Latitude D620 / Quadro NVS
110M/GeForce Go 7300
https://bugs.launchpad.net/bugs/539730
You received this bug notification
40 matches
Mail list logo
