FS#42549 - [nvidia-340xx] 340.46 wrong number of screens detected

Attached to Project: Arch Linux
Opened by Gianluca Pettinello (gianluca.pettinello) - Saturday, 25 October 2014, 11:31 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Saturday, 28 February 2015, 14:11 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

After installing, the display stretches as if there are two screens for the display.
nvidia-settings reports 3 screens
System: Sony Vaio F11B4E nvidia gt 330m
Going to nvidia 304xx series solves the issue.

First fix was to set explicitly one screen in /etc/X11/xorg.conf.d
But not possible to have dual screen any more

Additional info:
* package version(s)
nvidia-340xx nvidia-340xx-utils nvidia-340xx-libgl

* config and/or log files etc.


Steps to reproduce:
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Saturday, 28 February 2015, 14:11 GMT
Reason for closing:  Upstream
Additional comments about closing:  Nothing we can do about this as far as I can see.
Comment by Sven-Hendrik Haase (Svenstaro) - Monday, 27 October 2014, 06:08 GMT
Sorry, but I'm not really sure how I can help here with packaging. Isn't this more of an upstream bug?
Comment by Mark (markanubis) - Monday, 27 October 2014, 13:48 GMT
Well, I pretty much have the same problem as Gianluca has reported, I have a F127FX Vaio, with the same graphic card (01:00.0 VGA compatible controller: NVIDIA Corporation GT216M [GeForce GT 330M] (rev a2)), going to nvidia 304xx solve the problem too. Since nvidia had drop support for this graphic card in nvidia package, a moved to 340xx and I use dual screen (VGA + LVDS (the notebook monitor)), but when i first boot with this package the VGA do not even work, only black screen, because the monitor (ACER AL2016W) is set to 1920x1080 and it support until 1680x1050 (as reported in xrandr). i tried to change its resolution by adding a custom one in xrandr like this guy in the 1# post https://bbs.archlinux.org/viewtopic.php?id=114933, it adds the new custom resolution but when i tried to assign it to VGA this error appears " X Error of failed request: BadMatch (invalid parameter attributes) ". By the way, if i only use my notebook monitor it work just fine but when i see what display is plugged with xrandr it says that HDMI, VGA and LVDS is connected, and i was only using LVDS without any cable connected to the notebook.
I hope this help you guys. For now, i will be using the 304xx its working 100% for me here too.
Comment by Jean-Patrick Simard (jpsimard) - Sunday, 09 November 2014, 22:15 GMT
I would like to state that I have tried installing the 340.58 driver on my Vaio VPCF13UXF with the ".run" file from Nvidia. The problem persists, so this does appear to be an upstream problem, perhaps directly related to Vaio architecture? I will try to write a bug report some time tomorrow. Would it be useful to write back the results of my communications on this thread? In any case, both the 304 driver and Nouveau work just fine.

Edit: perhaps if we all log a bug report, they would have more information and solve this faster...
Comment by Jean-Patrick Simard (jpsimard) - Monday, 10 November 2014, 12:05 GMT
So you guys know, they have opened a bug #200054141

Edit: and I have given the link to this thread...
Comment by Sven-Hendrik Haase (Svenstaro) - Thursday, 20 November 2014, 16:58 GMT
Has this been resolved in the current version?
Comment by Jean-Patrick Simard (jpsimard) - Thursday, 20 November 2014, 17:14 GMT
Not on my system. As I have stated, I tried with 340.58 bin file from Nvidia, same problems. I would think at least one revision will be necessary.
Comment by Sven-Hendrik Haase (Svenstaro) - Thursday, 20 November 2014, 17:31 GMT
There does not appear to be anything to be done from the packaging side of things. Unless you disagree, I'm going to close this as upstream. No use tracking a bug we have no chance of even fixing ourselves.

Loading...