After update twinview no longer recognizes SAMSUNG LCD

Bug #270058 reported by Providence SALUMU M.
2
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers-177 (Ubuntu)
Invalid
Undecided
Unassigned
Declined for Intrepid by Steve Beattie

Bug Description

- Monitor : SAMSUNG LCD LE40R8
- Graphics Card : GeForce 8400M G
- kernel 2.6.27-3-generic
- xsever-xorg 1:7.4~2ubuntu1 (intrepid)

Updated from nvidia-graphics-drivers-177 (177.70-0ubuntu1) to nvidia-graphics-drivers-177 (177.70-0ubuntu2), now nvidia-settings can no longer detect SAMSUNG LCD LE40R8 monitor from AGP port. It now only displays CRT-0 and max resolution is 640x480 while it used to be 1280x800.

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 03)
     Subsystem: Samsung Electronics Co Ltd Device [144d:c510]
01:00.0 VGA compatible controller [0300]: nVidia Corporation GeForce 8400M G [10de:0428] (rev a1)
     Subsystem: Samsung Electronics Co Ltd Device [144d:c510]

Revision history for this message
Providence SALUMU M. (providence-salumu) wrote :

I checked against a DELL Monitor today, TwinView seems to not definitely be working any more :(

Revision history for this message
Providence SALUMU M. (providence-salumu) wrote :

Just checked against today's update to nvidia-177.76, much more modes are available (1024x768 @60Hz, 800x600 @ 60Hz, ...) but the SAMSUNG Monitor still doesn't display anything.
Again, No EDID is detected (/var/log/Xorg.0.log) and the monitor stays blank. Turning on the monitor for the first time flashes PC screen for about 0.1 sec and then displays "No input signal".

Revision history for this message
Bryce Harrington (bryce) wrote :

Hi providence-salumu,

Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log file from after reproducing this issue. If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.

Changed in nvidia-graphics-drivers-177:
status: New → Incomplete
Revision history for this message
Providence SALUMU M. (providence-salumu) wrote :

Hi Bryce,

I attach the files you requested. I have to say that reinstalling old versions of linux (ubuntu) does not solve my problem, neither does using an nvidia-177.73 driver.
I'm wondering now if it is not an electronic problem related to my nvidia video card. Maybe some of its components are down? But how can I tell?

I have also noticed another weird behaviour: when I turn on the computer, sometime the computer crashes (two blinking led), sometimes the gdm fails to start (low resolution problem) and I have to reboot the computer many times before the gdm finally stabilizes.

Thank you for any help

Revision history for this message
Providence SALUMU M. (providence-salumu) wrote :
Revision history for this message
Providence SALUMU M. (providence-salumu) wrote :

I forgot to add that I'm using a Samsung Q45 laptop.

Revision history for this message
Steve Beattie (sbeattie) wrote :

Marking back as new since the original reporter has provided the requested information.

Changed in nvidia-graphics-drivers-177:
status: Incomplete → New
Bryce Harrington (bryce)
Changed in nvidia-graphics-drivers-177:
status: New → Confirmed
Bryce Harrington (bryce)
description: updated
Revision history for this message
Bryce Harrington (bryce) wrote :

[This is an automated message]

In Jaunty (9.04), we are dropping the nvidia-graphics-drivers-177 package, which
is now superseded by then nvidia-graphics-drivers-180 package.

  http://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180

To transition your bug into the new package, we need your help. Please do the following:

 a. Verify the bug occurs in Jaunty with the -180 driver
     (ISOs: http://cdimage.ubuntu.com/releases/jaunty/)
 b. If you haven't already, please include in the bug:
     * Your /var/log/Xorg.0.log
     * Your /etc/X11/xorg.conf
     * The output of `lspci -vvnn`
     * Steps to reproduce the issue
 c. Under Affects, click the down arrow to the left of 'nvidia-graphics-drivers-177'
 d. Edit the Package to change 'nvidia-graphics-drivers-177' to 'nvidia-graphics-drivers-180'
 e. Click Save Changes

Thank you!

[We'll expire the remaining -177 bugs in a month or so.]

Revision history for this message
Bryce Harrington (bryce) wrote :

[This is an automated message]

In Jaunty (9.04) we have dropped the nvidia-graphics-driver-177 package, as
it is superseded by nvidia-graphics-drivers-180.

Because of this, we are closing this bug as expired.

You are encouraged to file your -nvidia bug reports against the
nvidia-graphics-drivers-180 package. Please be aware that because this
is a proprietary graphics driver, the amount of bug support we can
provide at the distro level is very limited.

Changed in nvidia-graphics-drivers-177:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.