F16 Nvidia Panning configuration broken since upgrade to xorg.conf via yum

TrickyHarry · #1 10th August 2012, 10:41 AM

I have F16 for my laptop machine, with both Twin-View and Panning on the "laptop screen" enabled and all has well for about 1 year.
1. I performed a "yum update" and I found that xorg,conf - I believe was available as an update, and I accepted it. The Nvidia driver has not been upgraded for a while.
2. I got a new Logitech TrackBall mouse and I wanted to test it out so I rebooted my PC.
- I placed the mouse in a USB 3.0 socket, my USB 2.0 was occupied by my phone.

Since that change my Panning, only configured on the laptop screen, is half-working.
Main laptop screen: 1920x1080 , with panning: 1920x1400

On restart, the PC would not go into graphical mode on the boot console, it hung there. I removed the Logitech mouse from the USB3.0 port and my laptop booted fine. After login:
a. Its the first time that I have noticed the large Nvidia logo have a small RED "beta" label at the bottom of it
b. I found that the Gnome had started in fall-back mode and
c. The Desktop background only covered the "standard" part of the screen and not the
additional lower "panned" part of the screen.
d. The "system Tray" and the external Disks, on my Docking Station all appear at the
bottom of the lower panned area
e. Docky, set to "auto-hide", is activated at the bottom of the "standard" part of the
screen and not the additional lower "panned" part of the screen. This worked
previously prior to upgrade
f. Trying to update the nvidia-settings now produces errors, stating that entries must
have unique names and some entry names are too long and I clicked the auto-repair

Remedies tried:-
1. I removed the xorg.conf entries for the Logitech Trackball mouse and logged out/in - no change
1. Saved the original xorg.conf file and copied over the contents from the xorg-nvidia.conf, and restarted the machine, no change

Not sure what else to do - backout the xorg.conf update ? [How to do this ???]

================================================== ===

rpm -qa *\nvidia\* *\kernel\* *xorg*|sort;uname -r;lsmod |grep -e nvidia -e nouveau;cat /etc/X11/xorg.conf
abrt-addon-kerneloops-2.0.7-3.fc16.x86_64
akmod-nvidia-304.32-2.fc16.x86_64
kernel-3.4.4-4.fc16.x86_64
kernel-3.4.6-1.fc16.x86_64
kernel-3.4.7-1.fc16.x86_64
kernel-devel-3.4.4-4.fc16.x86_64
kernel-devel-3.4.6-1.fc16.x86_64
kernel-devel-3.4.7-1.fc16.x86_64
kernel-headers-3.4.7-1.fc16.x86_64
kernel-tools-3.4.7-1.fc16.x86_64
kmod-nvidia-3.4.4-4.fc16.x86_64-304.32-2.fc16.x86_64
kmod-nvidia-3.4.6-1.fc16.x86_64-295.59-1.fc16.5.x86_64
kmod-nvidia-3.4.7-1.fc16.x86_64-304.32-2.fc16.x86_64
libreport-plugin-kerneloops-2.0.10-3.fc16.x86_64
nvidia-settings-1.0-17.fc16.x86_64
nvidia-xconfig-1.0-15.fc16.x86_64
xorg-x11-apps-7.6-2.fc15.x86_64
xorg-x11-drivers-7.4-2.fc15.x86_64
xorg-x11-drv-acecad-1.5.0-2.fc16.x86_64
xorg-x11-drv-aiptek-1.4.1-2.fc16.x86_64
xorg-x11-drv-apm-1.2.3-8.fc16.x86_64
xorg-x11-drv-ast-0.91.10-7.fc16.x86_64
xorg-x11-drv-ati-6.14.3-4.20120201git36c190671.fc16.x86_64
xorg-x11-drv-cirrus-1.3.2-10.fc16.x86_64
xorg-x11-drv-dummy-0.3.4-7.fc16.x86_64
xorg-x11-drv-elographics-1.3.0-2.fc16.x86_64
xorg-x11-drv-evdev-2.6.99.901-7.20120118git9d9c9870c.fc16.x86_64
xorg-x11-drv-fbdev-0.4.2-2.fc16.x86_64
xorg-x11-drv-fpit-1.4.0-2.fc16.x86_64
xorg-x11-drv-glint-1.2.5-2.fc16.x86_64
xorg-x11-drv-hyperpen-1.4.1-2.fc16.x86_64
xorg-x11-drv-i128-1.3.4-9.fc16.x86_64
xorg-x11-drv-i740-1.3.2-9.fc16.x86_64
xorg-x11-drv-intel-2.19.0-3.fc16.x86_64
xorg-x11-drv-keyboard-1.6.0-2.fc16.x86_64
xorg-x11-drv-mach64-6.9.0-2.fc16.x86_64
xorg-x11-drv-mga-1.4.13-8.fc16.x86_64
xorg-x11-drv-mouse-1.7.1-2.fc16.x86_64
xorg-x11-drv-mutouch-1.3.0-2.fc16.x86_64
xorg-x11-drv-nouveau-0.0.16-27.20110720gitb806e3f.fc16.x86_64
xorg-x11-drv-nv-2.1.18-8.fc16.x86_64
xorg-x11-drv-nvidia-304.32-1.fc16.x86_64
xorg-x11-drv-nvidia-libs-304.32-1.fc16.x86_64
xorg-x11-drv-openchrome-0.2.904-16.fc16.x86_64
xorg-x11-drv-penmount-1.5.0-3.fc16.x86_64
xorg-x11-drv-qxl-0.0.21-13.fc16.x86_64
xorg-x11-drv-r128-6.8.1-11.fc16.x86_64
xorg-x11-drv-rendition-4.2.4-7.fc16.x86_64
xorg-x11-drv-s3virge-1.10.4-9.fc16.x86_64
xorg-x11-drv-savage-2.3.3-1.fc16.x86_64
xorg-x11-drv-siliconmotion-1.7.5-2.fc16.x86_64
xorg-x11-drv-sis-0.10.3-7.fc16.x86_64
xorg-x11-drv-sisusb-0.9.4-7.fc16.x86_64
xorg-x11-drv-synaptics-1.5.0-2.fc16.x86_64
xorg-x11-drv-tdfx-1.4.3-9.fc16.x86_64
xorg-x11-drv-trident-1.3.4-7.fc16.x86_64
xorg-x11-drv-v4l-0.2.0-14.fc16.x86_64
xorg-x11-drv-vesa-2.3.0-9.fc16.x86_64
xorg-x11-drv-vmmouse-12.7.0-2.fc16.x86_64
xorg-x11-drv-vmware-11.0.3-6.fc16.x86_64
xorg-x11-drv-void-1.4.0-2.fc16.x86_64
xorg-x11-drv-voodoo-1.2.4-7.fc16.x86_64
xorg-x11-drv-wacom-0.12.0-1.fc16.x86_64
xorg-x11-fonts-100dpi-7.5-4.fc15.noarch
xorg-x11-fonts-ISO8859-1-100dpi-7.5-4.fc15.noarch
xorg-x11-fonts-ISO8859-14-100dpi-7.5-4.fc15.noarch
xorg-x11-fonts-ISO8859-14-75dpi-7.5-4.fc15.noarch
xorg-x11-fonts-ISO8859-15-100dpi-7.5-4.fc15.noarch
xorg-x11-fonts-ISO8859-15-75dpi-7.5-4.fc15.noarch
xorg-x11-fonts-ISO8859-1-75dpi-7.5-4.fc15.noarch
xorg-x11-fonts-misc-7.5-4.fc15.noarch
xorg-x11-fonts-truetype-1.0.2-1.fc16.noarch
xorg-x11-fonts-Type1-7.5-4.fc15.noarch
xorg-x11-font-utils-7.5-6.fc15.x86_64
xorg-x11-proto-devel-7.6-12.fc16.noarch
xorg-x11-resutils-7.5-2.fc15.x86_64
xorg-x11-server-common-1.11.4-3.fc16.x86_64
xorg-x11-server-utils-7.5-7.fc16.x86_64
xorg-x11-server-Xephyr-1.11.4-3.fc16.x86_64
xorg-x11-server-Xorg-1.11.4-3.fc16.x86_64
xorg-x11-utils-7.5-3.fc16.x86_64
xorg-x11-xauth-1.0.6-1.fc16.x86_64
xorg-x11-xinit-1.3.1-1.fc16.x86_64
xorg-x11-xkb-utils-7.5-5.fc16.x86_64
xorg-x11-xtrans-devel-1.2.6-2.fc15.noarch
3.4.7-1.fc16.x86_64
nvidia 11244331 45
i2c_core 33895 3 nvidia,i2c_i801,videodev
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 295.49 (mockbuild@builder1.ovh.rpmfusion.lan) Thu May 3 20:10:18 CEST 2012

# RPM Fusion - nvidia-xorg.conf
#

Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
Option "Xinerama" "0"
EndSection

Section "InputDevice"

# generated from data in "/etc/sysconfig/keyboard"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbLayout" "gb"
Option "XkbModel" "pc105"
EndSection

Section "InputDevice"

# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection

Section "InputClass"
Identifier "Marble Mouse"
Driver "evdev"
MatchProduct "Logitech USB Trackball"
MatchDevicePath "/dev/input/event*"
MatchIsPointer "yes"
Option "ButtonMapping" "1 9 3 4 5 6 7 2 8"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "3"
Option "ZAxisMapping" "4 5"
Option "XAxisMapping" "6 7"
Option "Emulate3Buttons" "false"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Lenovo Group Limited"
HorizSync 56.5 - 67.8
VertRefresh 50.0 - 60.0
EndSection

Section "Device"
Identifier "Videocard0"
Driver "nvidia"
EndSection

Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "Quadro 2000M"
EndSection

Section "Screen"
Identifier "Default Screen"
Device "Videocard0"
Monitor "Monitor0"
EndSection

Section "Screen"

# Removed Option "metamodes" "DFP-0: nvidia-auto-select @1920x1400 +0+0, CRT: nvidia-auto-select +1920+15"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "TwinView" "1"
Option "TwinViewXineramaInfoOrder" "DFP-0"
Option "metamodes" "DFP-0: 1920x1080 @1920x1400 +0+0, CRT: nvidia-auto-select +1920+15; DFP-0: nvidia-auto-select +0+0, CRT: nvidia-auto-select +1920+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection

================================================== =====

#2 10th August 2012, 11:27 AM

Read the manual as there have many changes in 304.xx

ftp://download.nvidia.com/XFree86/Li...304.32/README/

TrickyHarry · #3 10th August 2012, 04:49 PM

Hi Yellowman,

This was working yesterday ....

I also lost my sound today and I had to fix this by:-
http://forums.fedoraforum.org/showthread.php?t=281515

Which required:-
Add the following lines to /etc/modprobe.d/snd-hda-intel.conf

options snd-hda-intel model=3stack
options snd-hda-intel enable_msi=1

--> that was also working yesterday ... Anyway I have restored sound to the F16 installation ...

Any other comments to check ... it seems that panning is broken in the Nvidia configuration ...

#4 10th August 2012, 06:07 PM

Quote:

Originally Posted by TrickyHarry

Hi Yellowman,

This was working yesterday ....

I also lost my sound today and I had to fix this by:-
http://forums.fedoraforum.org/showthread.php?t=281515

Which required:-
Add the following lines to /etc/modprobe.d/snd-hda-intel.conf

options snd-hda-intel model=3stack
options snd-hda-intel enable_msi=1

--> that was also working yesterday ... Anyway I have restored sound to the F16 installation ...

Any other comments to check ... it seems that panning is broken in the Nvidia configuration ...

No....................

PabloTwo · #5 10th August 2012, 06:36 PM

Quote:

Option "TwinViewXineramaInfoOrder" "DFP-0"

I'm using 304.32 on F16.x86_64 and using nvidia-settings to query available options, the one listed above in your xorg.conf file doesn't seem to exist. There is only "TwinView" and "XineramaInfoOrder".

I don't know if that has anything to do with your issue, but it just caught my attention.

TrickyHarry · #6 14th August 2012, 12:35 AM

Quote:

Option "TwinViewXineramaInfoOrder" "DFP-0"

I tried your suggestion of :-
Option "XineramaInfoOrder" "DFP-0"

Since then, my Terminal crashed, Docky would not run and I have put back in the line, still with issues .... not sure why but does not seem that the system is running normally ...

NeuroKillswitch · #7 14th August 2012, 12:44 AM

Did you try nvidia-xconfig or nvidia-settings?

TrickyHarry · #8 14th August 2012, 12:45 AM

I have rebooted the machine and in Gnome, I have:-
a. System tray at 1920x1400
b. Docky at 1920x1080
c. Wall Paper covering 1920x1080

I have login with Cinnamon and I have:-
a. System tray at 1920x1400
b. Cinnamon, Bottom Menu at 1920x1400 [Full menu]
c. Wall Paper covering 1920x1080
d. I ran up Docky and it auto-hides at 1920x1080

This is now quite interesting ....

NeuroKillswitch · #9 14th August 2012, 01:13 AM

Try commenting this section in your xorg.conf (while X is down)

Section "Device"
Identifier "Videocard0"
Driver "nvidia"
EndSection

and restart X.

TrickyHarry · #10 14th August 2012, 10:48 AM

Quote:

Originally Posted by NeuroKillswitch

Try commenting this section in your xorg.conf (while X is down)

Section "Device"
Identifier "Videocard0"
Driver "nvidia"
EndSection

and restart X.

Thanks for your input, it is appreciated....

That snip of code the contents of the /etc/X11/nvidia-xorg.conf
I have overwritten that piece of code on the xorg.conf and on restart, it works
-- The base is stable and works fine.
-- The issue arises when I start to add the two additions: Twin-View and Panning

I have used nvidia-settings since FC13 through FC16 [current version] and it worked perfectly up until last week - around 2+ years

Using the nvidia-settings to set the screen attributes in the xorg.conf is failing by its own parser when writing the value config file. The part of the nvidia-setting that writes the file detects an error and asks if it should auto-fix - yes ... I cannot comment further.

The nvidia-settings utility extends the base xorg.conf file, I think - well some process, and populates it will the other stanzas - all of it used to be correct.

1. The panning is completely broken, as it seems to be providing sufficient information for certain applications but not sufficient for others - or something is corrupted somewhere ....

2. After locking the desktop at night and in the morning, unlocking it, my TwinView screens have switched their "logical" Left and Right sides.
- last night screen 1 to screen 2 was a left to right mouse movement, this morning its a right to left movement to move from screen 1 to screen 2 AND both screens have panning defined.

In summary, something has changed, and the documentation in the notes that was supplied by YellowMan and Leigh is now not complete.

/README/configtwinview.html - Chapter 13:-
======================

A MetaMode string can be further modified with a "Panning Domain" specification; e.g.,

"1024x768 @1600x1200, 800x600 @1600x1200"

A panning domain is the area in which a display device's viewport will be panned to follow the mouse. Panning actually happens on two levels with MetaModes: first, an individual display device's viewport will be panned within its panning domain, as long as the viewport is contained by the bounding box of the MetaMode. Once the mouse leaves the bounding box of the MetaMode, the entire MetaMode (i.e., all display devices) will be panned to follow the mouse within the virtual screen, unless the "PanAllDisplays" X configuration option is disabled. Note that individual display devices' panning domains default to being clamped to the position of the display devices' viewports, thus the default behavior is just that viewports remain "locked" together and only perform the second type of panning.

The most beneficial use of panning domains is probably to eliminate dead areas -- regions of the virtual screen that are inaccessible due to display devices with different resolutions. For example:

"1600x1200, 1024x768"

produces an inaccessible region below the 1024x768 display. Specifying a panning domain for the second display device:

"1600x1200, 1024x768 @1024x1200"

provides access to that dead area by allowing you to pan the 1024x768 viewport up and down in the 1024x1200 panning domain.

Offsets can be used in conjunction with panning domains to position the panning domains in the virtual screen space (note that the offset describes the panning domain, and only affects the viewport in that the viewport must be contained within the panning domain). For example, the following describes two modes, each with a panning domain width of 1900 pixels, and the second display is positioned below the first:

"1600x1200 @1900x1200 +0+0, 1024x768 @1900x768 +0+1200"

Because it is often unclear which mode within a MetaMode will be used on each display device, mode descriptions within a MetaMode can be prepended with a display device name. For example:

"CRT-0: 1600x1200, DFP-0: 1024x768"

======================
My current xorg.conf, originally with just 1 stanza from the nvidia-xorg.conf base definition:-
======================
cat /etc/X11/xorg.conf
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 295.49 (mockbuild@builder1.ovh.rpmfusion.lan) Thu May 3 20:10:18 CEST 2012

# RPM Fusion - nvidia-xorg.conf
#

Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
Option "Xinerama" "0"
EndSection

Section "InputDevice"

# generated from data in "/etc/sysconfig/keyboard"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbLayout" "gb"
Option "XkbModel" "pc105"
EndSection

Section "InputDevice"

# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Lenovo Group Limited"
HorizSync 56.5 - 67.8
VertRefresh 50.0 - 60.0
EndSection

Section "Device"
Identifier "Videocard0"
Driver "nvidia"
EndSection

Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "Quadro 2000M"
EndSection

Section "Screen"
Identifier "Default Screen"
Device "Videocard0"
Monitor "Monitor0"
EndSection

Section "Screen"

# Removed Option "metamodes" "DFP-0: 1920x1080 +0+0, CRT: 1680x1050 +1920+0"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "TwinView" "1"
Option "TwinViewXineramaInfoOrder" "DFP-0"
# Option "XineramaInfoOrder" "DFP-0"
Option "metamodes" "DFP-0: 1920x1080 @1920x1400 +0+0, CRT: 1680x1050 +1920+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
======================

---------- Post added at 10:48 AM ---------- Previous post was at 10:38 AM ----------

I would like to change the title of this thread from xorg.conf being changed by yum to xorg-x11-??? being changed and has now broken panning.

This is now confirmed and was stated by Leigh in a separate post.

TrickyHarry · #11 21st August 2012, 09:27 PM

Previous Thread:-
F16 Nvidia Panning configuration broken since upgrade to xorg.conf via yum
http://forums.fedoraforum.org/showth...=1#post1597242

New thread created because thread title was incorrect and I was not able to correct it.

After upgrade to 295.59 on Fedora 16, my panned area had some undesirable characteristics:-

The desktop background no longer covered the panned area
Some applications did not recognise the extended area as usable - Docky
Turning the CRT off/on would sometimes disable panning
The nvidia-settings utility would not manage the merging of new settings to the xorg.conf file

I had configured the following:-
a. Twinview over laptop screen and external CRT Display [1920x1080 + 1780x1050]
b. Setup panning only on the laptop screen to extend the screen from 1920x1080 to 1920x1400

The issues seen are compared to the previously correct working of panning since first using Fedora 16, about 7 months ago

Open applications can be :-
a. Moved to the newly define panned area
b. Application windows can be re-sized to occupy the newly define panned area
- with a Docky menu triggered when the mouse crosses into the panned area

Issues:-
a. The Docky menu would camp at the end of the main area and not at the end of the panned area - menus are now appearing in the "middle" of the screen.
b. Newly detected USB disk devices would appear at the lower of the panned area
c. System tray and bin would appear at the lower of the panned area
d. I have replaced the current xorg.conf with the minimalist nvidia-xorg.conf, then configured panning using the nvidia-settings utility
========================================

I have since upgraded the kernel and the nvidia driver on Aug-21 and the situation has been "normalised" to most of the applications do not recognise the defined panning area

New configuration: 304.37

grep nvidia /var/log/yum.log | grep drv-nvidia-libs

Feb 18 22:36:40 Installed: 1:xorg-x11-drv-nvidia-libs-290.10-1.fc16.x86_64
Apr 02 13:32:18 Updated: 1:xorg-x11-drv-nvidia-libs-295.33-3.fc16.x86_64
Apr 16 23:43:02 Updated: 1:xorg-x11-drv-nvidia-libs-295.40-1.fc16.x86_64
May 05 02:50:17 Updated: 1:xorg-x11-drv-nvidia-libs-295.49-1.fc16.x86_64
May 23 11:45:58 Updated: 1:xorg-x11-drv-nvidia-libs-295.49-2.fc16.x86_64
May 29 21:54:04 Updated: 1:xorg-x11-drv-nvidia-libs-295.53-1.fc16.x86_64
Jun 14 23:27:42 Updated: 1:xorg-x11-drv-nvidia-libs-295.59-1.fc16.x86_64
--------- start of issues -----
Aug 09 14:07:13 Updated: 1:xorg-x11-drv-nvidia-libs-304.32-1.fc16.x86_64
Aug 21 03:31:47 Updated: 1:xorg-x11-drv-nvidia-libs-304.37-1.fc16.x86_64

a. Docky does not recognise the defined panned area
b. Newly discovered devices are now displayed at the start of the defined panned area and not at the end
c. The system tray now does not recognise the newly defined panned area
d. The desktop background does not cover the newly defined panned area
e. On login the panned area is correctly defined on the laptop screen - on recovery from sleep or extended screen saver activity either both displays have the same panned area OR neither have the panned area
f. Defining the pan area in the nvidia-settings tool and then attempting to apply, causes both screens to blink and flash for about 10 seconds and then fail to apply the panned area, but the xorg.conf has the panned area defined correctly
g. Logoff, then login correctly defines the panned area on the laptop, but it now suffers from the same issues

====================================
rpm -qa *\nvidia\* *\kernel\* *xorg*|sort;uname -r;lsmod |grep -e nvidia -e nouveau;cat /etc/X11/xorg.conf;grep nvidia /var/log/yum.log
====================================

abrt-addon-kerneloops-2.0.7-3.fc16.x86_64
akmod-nvidia-304.37-1.fc16.x86_64
kernel-3.4.6-1.fc16.x86_64
kernel-3.4.7-1.fc16.x86_64
kernel-3.4.9-1.fc16.x86_64
kernel-devel-3.4.6-1.fc16.x86_64
kernel-devel-3.4.7-1.fc16.x86_64
kernel-devel-3.4.9-1.fc16.x86_64
kernel-headers-3.4.9-1.fc16.x86_64
kernel-tools-3.4.9-1.fc16.x86_64
kmod-nvidia-3.4.6-1.fc16.x86_64-304.37-1.fc16.x86_64
kmod-nvidia-3.4.7-1.fc16.x86_64-304.37-1.fc16.x86_64
kmod-nvidia-3.4.9-1.fc16.x86_64-304.37-1.fc16.x86_64
libreport-plugin-kerneloops-2.0.10-3.fc16.x86_64
nvidia-settings-1.0-20.fc16.x86_64
nvidia-xconfig-1.0-18.fc16.x86_64
xorg-x11-apps-7.6-2.fc15.x86_64
xorg-x11-drivers-7.4-2.fc15.x86_64
xorg-x11-drv-acecad-1.5.0-2.fc16.x86_64
xorg-x11-drv-aiptek-1.4.1-2.fc16.x86_64
xorg-x11-drv-apm-1.2.3-8.fc16.x86_64
xorg-x11-drv-ast-0.91.10-7.fc16.x86_64
xorg-x11-drv-ati-6.14.3-4.20120201git36c190671.fc16.x86_64
xorg-x11-drv-cirrus-1.3.2-10.fc16.x86_64
xorg-x11-drv-dummy-0.3.4-7.fc16.x86_64
xorg-x11-drv-elographics-1.3.0-2.fc16.x86_64
xorg-x11-drv-evdev-2.6.99.901-7.20120118git9d9c9870c.fc16.x86_64
xorg-x11-drv-fbdev-0.4.2-2.fc16.x86_64
xorg-x11-drv-fpit-1.4.0-2.fc16.x86_64
xorg-x11-drv-glint-1.2.5-2.fc16.x86_64
xorg-x11-drv-hyperpen-1.4.1-2.fc16.x86_64
xorg-x11-drv-i128-1.3.4-9.fc16.x86_64
xorg-x11-drv-i740-1.3.2-9.fc16.x86_64
xorg-x11-drv-intel-2.19.0-3.fc16.x86_64
xorg-x11-drv-keyboard-1.6.0-2.fc16.x86_64
xorg-x11-drv-mach64-6.9.0-2.fc16.x86_64
xorg-x11-drv-mga-1.4.13-8.fc16.x86_64
xorg-x11-drv-mouse-1.7.1-2.fc16.x86_64
xorg-x11-drv-mutouch-1.3.0-2.fc16.x86_64
xorg-x11-drv-nouveau-0.0.16-27.20110720gitb806e3f.fc16.x86_64
xorg-x11-drv-nv-2.1.18-8.fc16.x86_64
xorg-x11-drv-nvidia-304.37-1.fc16.x86_64
xorg-x11-drv-nvidia-libs-304.37-1.fc16.x86_64
xorg-x11-drv-openchrome-0.2.904-16.fc16.x86_64
xorg-x11-drv-penmount-1.5.0-3.fc16.x86_64
xorg-x11-drv-qxl-0.0.21-13.fc16.x86_64
xorg-x11-drv-r128-6.8.1-11.fc16.x86_64
xorg-x11-drv-rendition-4.2.4-7.fc16.x86_64
xorg-x11-drv-s3virge-1.10.4-9.fc16.x86_64
xorg-x11-drv-savage-2.3.3-1.fc16.x86_64
xorg-x11-drv-siliconmotion-1.7.5-2.fc16.x86_64
xorg-x11-drv-sis-0.10.3-7.fc16.x86_64
xorg-x11-drv-sisusb-0.9.4-7.fc16.x86_64
xorg-x11-drv-synaptics-1.5.0-2.fc16.x86_64
xorg-x11-drv-tdfx-1.4.3-9.fc16.x86_64
xorg-x11-drv-trident-1.3.4-7.fc16.x86_64
xorg-x11-drv-v4l-0.2.0-14.fc16.x86_64
xorg-x11-drv-vesa-2.3.0-9.fc16.x86_64
xorg-x11-drv-vmmouse-12.7.0-2.fc16.x86_64
xorg-x11-drv-vmware-11.0.3-6.fc16.x86_64
xorg-x11-drv-void-1.4.0-2.fc16.x86_64
xorg-x11-drv-voodoo-1.2.4-7.fc16.x86_64
xorg-x11-drv-wacom-0.12.0-1.fc16.x86_64
xorg-x11-fonts-100dpi-7.5-4.fc15.noarch
xorg-x11-fonts-ISO8859-1-100dpi-7.5-4.fc15.noarch
xorg-x11-fonts-ISO8859-14-100dpi-7.5-4.fc15.noarch
xorg-x11-fonts-ISO8859-14-75dpi-7.5-4.fc15.noarch
xorg-x11-fonts-ISO8859-15-100dpi-7.5-4.fc15.noarch
xorg-x11-fonts-ISO8859-15-75dpi-7.5-4.fc15.noarch
xorg-x11-fonts-ISO8859-1-75dpi-7.5-4.fc15.noarch
xorg-x11-fonts-misc-7.5-4.fc15.noarch
xorg-x11-fonts-truetype-1.0.2-1.fc16.noarch
xorg-x11-fonts-Type1-7.5-4.fc15.noarch
xorg-x11-font-utils-7.5-6.fc15.x86_64
xorg-x11-proto-devel-7.6-12.fc16.noarch
xorg-x11-resutils-7.5-2.fc15.x86_64
xorg-x11-server-common-1.11.4-3.fc16.x86_64
xorg-x11-server-utils-7.5-7.fc16.x86_64
xorg-x11-server-Xephyr-1.11.4-3.fc16.x86_64
xorg-x11-server-Xorg-1.11.4-3.fc16.x86_64
xorg-x11-utils-7.5-3.fc16.x86_64
xorg-x11-xauth-1.0.6-1.fc16.x86_64
xorg-x11-xinit-1.3.1-1.fc16.x86_64
xorg-x11-xkb-utils-7.5-5.fc16.x86_64
xorg-x11-xtrans-devel-1.2.6-2.fc15.noarch
3.4.9-1.fc16.x86_64
nvidia 11244439 57
i2c_core 33895 3 nvidia,videodev,i2c_i801
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 304.37 (mockbuild@builder1.ovh.rpmfusion.lan) Tue Aug 14 06:37:18 CEST 2012

# RPM Fusion - nvidia-xorg.conf
#

Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
Option "Xinerama" "0"
EndSection

Section "InputDevice"
# generated from data in "/etc/sysconfig/keyboard"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbLayout" "gb"
Option "XkbModel" "pc105"
EndSection

Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Lenovo Group Limited"
HorizSync 56.5 - 67.8
VertRefresh 50.0 - 60.0
EndSection

Section "Device"
Identifier "Videocard0"
Driver "nvidia"
EndSection

Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "Quadro 2000M"
EndSection

Section "Screen"
Identifier "Default Screen"
Device "Videocard0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "Stereo" "0"
Option "nvidiaXineramaInfoOrder" "DFP-0"
Option "metamodes" "DFP-0: nvidia-auto-select @1920x1400 +0+0, CRT: nvidia-auto-select +1920+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection

TrickyHarry · #12 21st August 2012, 09:32 PM

I have updated the current thread by adding additional information in a new thread with a more appropriate thread title:-

http://forums.fedoraforum.org/showth...03#post1598603
F16 Nvidia Panning configuration broken since upgrade of driver to 295.59

==> this may also be in-correct as the issues may be related to 304.32 +

TrickyHarry · #13 21st August 2012, 09:42 PM

Nvidia related installations via yum:-

=======================
Feb 18 22:36:33 Installed: nvidia-settings-1.0-13.fc16.x86_64
Feb 18 22:36:34 Installed: nvidia-xconfig-1.0-11.fc16.x86_64
Feb 18 22:36:40 Installed: 1:xorg-x11-drv-nvidia-libs-290.10-1.fc16.x86_64
Feb 18 22:36:42 Installed: 1:xorg-x11-drv-nvidia-290.10-1.fc16.x86_64
Feb 18 22:36:42 Installed: 1:akmod-nvidia-290.10-1.fc16.4.x86_64
Feb 19 02:16:37 Installed: 1:xorg-x11-drv-nvidia-290.10-1.fc16.x86_64
Feb 19 02:17:17 Installed: 1:akmod-nvidia-290.10-1.fc16.4.x86_64
Feb 19 04:16:59 Updated: 1:kmod-nvidia-3.2.6-3.fc16.x86_64-290.10-1.fc16.14.x86_64
Feb 28 01:02:37 Updated: 1:kmod-nvidia-3.2.7-1.fc16.x86_64-290.10-1.fc16.15.x86_64
Mar 08 10:22:06 Erased: 1:kmod-nvidia-3.1.0-7.fc16.x86_64-290.10-1.fc16.4.x86_64
Mar 12 19:24:23 Updated: 1:kmod-nvidia-3.2.9-1.fc16.x86_64-290.10-1.fc16.17.x86_64
Mar 12 19:24:41 Erased: 1:kmod-nvidia-3.2.6-3.fc16.x86_64-290.10-1.fc16.14.x86_64
Mar 12 19:30:21 Updated: 1:kmod-nvidia-3.2.9-2.fc16.x86_64-290.10-1.fc16.18.x86_64
Mar 30 08:43:56 Erased: 1:kmod-nvidia-3.2.7-1.fc16.x86_64-290.10-1.fc16.15.x86_64
Mar 30 09:53:35 Updated: 1:akmod-nvidia-290.10-2.fc16.2.x86_64
Apr 02 12:58:00 Installed: 1:akmod-nvidia-290.10-2.fc16.2.x86_64
Apr 02 13:32:10 Updated: nvidia-settings-1.0-15.fc16.x86_64
Apr 02 13:32:12 Updated: nvidia-xconfig-1.0-13.fc16.x86_64
Apr 02 13:32:14 Updated: 1:kmod-nvidia-3.3.0-4.fc16.x86_64-295.33-2.fc16.x86_64
Apr 02 13:32:18 Updated: 1:xorg-x11-drv-nvidia-libs-295.33-3.fc16.x86_64
Apr 02 13:32:19 Updated: 1:xorg-x11-drv-nvidia-295.33-3.fc16.x86_64
Apr 02 13:32:20 Updated: 1:akmod-nvidia-295.33-2.fc16.x86_64
Apr 02 13:33:21 Erased: 1:kmod-nvidia-3.2.9-1.fc16.x86_64-290.10-2.fc16.2.x86_64
Apr 02 13:53:55 Updated: 1:kmod-nvidia-3.3.0-8.fc16.x86_64-295.33-2.fc16.1.x86_64
Apr 09 16:08:00 Erased: 1:kmod-nvidia-3.2.9-2.fc16.x86_64-290.10-1.fc16.18.x86_64
Apr 09 18:38:50 Updated: 1:kmod-nvidia-3.3.1-3.fc16.x86_64-295.33-2.fc16.3.x86_64
Apr 14 16:41:42 Erased: 1:kmod-nvidia-3.3.0-4.fc16.x86_64-295.33-2.fc16.x86_64
Apr 16 23:42:56 Updated: nvidia-xconfig-1.0-14.fc16.x86_64
Apr 16 23:42:56 Updated: nvidia-settings-1.0-16.fc16.x86_64
Apr 16 23:42:57 Updated: 1:akmod-nvidia-295.40-2.fc16.x86_64
Apr 16 23:43:02 Updated: 1:xorg-x11-drv-nvidia-libs-295.40-1.fc16.x86_64
Apr 16 23:43:03 Updated: 1:xorg-x11-drv-nvidia-295.40-1.fc16.x86_64
Apr 16 23:43:18 Updated: 1:kmod-nvidia-3.3.1-5.fc16.x86_64-295.40-2.fc16.x86_64
Apr 19 22:36:29 Erased: 1:kmod-nvidia-3.3.0-8.fc16.x86_64-295.33-2.fc16.1.x86_64
Apr 20 00:53:42 Updated: 1:kmod-nvidia-3.3.2-1.fc16.x86_64-295.40-2.fc16.1.x86_64
Apr 26 02:31:57 Erased: 1:kmod-nvidia-3.3.1-3.fc16.x86_64-295.33-2.fc16.3.x86_64
Apr 30 01:59:18 Updated: 1:kmod-nvidia-3.3.2-6.fc16.x86_64-295.40-2.fc16.2.x86_64
May 05 02:50:09 Updated: nvidia-settings-1.0-17.fc16.x86_64
May 05 02:50:13 Updated: nvidia-xconfig-1.0-15.fc16.x86_64
May 05 02:50:17 Updated: 1:xorg-x11-drv-nvidia-libs-295.49-1.fc16.x86_64
May 05 02:50:17 Updated: 1:akmod-nvidia-295.49-1.fc16.x86_64
May 05 02:50:19 Updated: 1:xorg-x11-drv-nvidia-295.49-1.fc16.x86_64
May 05 02:51:50 Erased: 1:kmod-nvidia-3.3.1-5.fc16.x86_64-295.40-2.fc16.x86_64
May 18 09:10:31 Erased: 1:kmod-nvidia-3.3.2-1.fc16.x86_64-295.40-2.fc16.1.x86_64
May 18 20:01:55 Updated: 1:kmod-nvidia-3.3.5-2.fc16.x86_64-295.49-1.fc16.2.x86_64
May 23 11:45:51 Updated: 1:akmod-nvidia-295.49-1.fc16.3.x86_64
May 23 11:45:53 Updated: 1:xorg-x11-drv-nvidia-295.49-2.fc16.x86_64
May 23 11:45:58 Updated: 1:xorg-x11-drv-nvidia-libs-295.49-2.fc16.x86_64
May 23 11:46:22 Erased: 1:kmod-nvidia-3.3.2-6.fc16.x86_64-295.49-1.fc16.x86_64
May 29 10:12:56 Erased: 1:kmod-nvidia-3.3.4-1.fc16.x86_64-295.49-1.fc16.x86_64
May 29 21:54:01 Updated: 1:akmod-nvidia-295.53-1.fc16.1.x86_64
May 29 21:54:04 Updated: 1:xorg-x11-drv-nvidia-libs-295.53-1.fc16.x86_64
May 29 21:54:05 Updated: 1:xorg-x11-drv-nvidia-295.53-1.fc16.x86_64
May 29 21:54:29 Updated: 1:kmod-nvidia-3.3.7-1.fc16.x86_64-295.53-1.fc16.1.x86_64
May 29 21:54:44 Updated: 1:kmod-nvidia-3.3.6-3.fc16.x86_64-295.53-1.fc16.x86_64
Jun 14 23:27:42 Updated: 1:xorg-x11-drv-nvidia-libs-295.59-1.fc16.x86_64
Jun 14 23:27:45 Updated: 1:xorg-x11-drv-nvidia-295.59-1.fc16.x86_64
Jun 14 23:27:45 Updated: 1:akmod-nvidia-295.59-1.fc16.x86_64
Jun 14 23:28:17 Erased: 1:kmod-nvidia-3.3.5-2.fc16.x86_64-295.49-1.fc16.3.x86_64
Jun 21 00:11:43 Erased: 1:kmod-nvidia-3.3.6-3.fc16.x86_64-295.53-1.fc16.x86_64
Jun 21 23:47:30 Updated: 1:kmod-nvidia-3.4.2-1.fc16.x86_64-295.59-1.fc16.1.x86_64
Jul 12 20:50:22 Erased: 1:kmod-nvidia-3.3.7-1.fc16.x86_64-295.59-1.fc16.x86_64
Jul 17 16:04:00 Updated: 1:kmod-nvidia-3.4.4-4.fc16.x86_64-295.59-1.fc16.3.x86_64
Jul 30 21:45:35 Erased: 1:kmod-nvidia-3.3.8-1.fc16.x86_64-295.59-1.fc16.x86_64
Jul 30 23:44:42 Updated: 1:kmod-nvidia-3.4.6-1.fc16.x86_64-295.59-1.fc16.5.x86_64
Aug 07 10:22:17 Erased: 1:kmod-nvidia-3.4.2-1.fc16.x86_64-295.59-1.fc16.1.x86_64
Aug 09 14:07:08 Updated: 1:kmod-nvidia-3.4.7-1.fc16.x86_64-304.32-2.fc16.x86_64
Aug 09 14:07:13 Updated: 1:xorg-x11-drv-nvidia-libs-304.32-1.fc16.x86_64
Aug 09 14:07:15 Updated: 1:xorg-x11-drv-nvidia-304.32-1.fc16.x86_64
Aug 09 14:07:39 Updated: 1:akmod-nvidia-304.32-2.fc16.x86_64
Aug 15 23:45:26 Updated: nvidia-settings-1.0-19.fc16.x86_64
Aug 15 23:45:44 Updated: nvidia-xconfig-1.0-17.fc16.x86_64
Aug 21 03:31:32 Updated: nvidia-settings-1.0-20.fc16.x86_64
Aug 21 03:31:42 Updated: nvidia-xconfig-1.0-18.fc16.x86_64
Aug 21 03:31:47 Updated: 1:xorg-x11-drv-nvidia-libs-304.37-1.fc16.x86_64
Aug 21 03:31:49 Updated: 1:xorg-x11-drv-nvidia-304.37-1.fc16.x86_64
Aug 21 03:31:51 Updated: 1:kmod-nvidia-3.4.7-1.fc16.x86_64-304.37-1.fc16.x86_64
Aug 21 03:32:39 Updated: 1:akmod-nvidia-304.37-1.fc16.x86_64
Aug 21 03:34:00 Erased: 1:kmod-nvidia-3.4.4-4.fc16.x86_64-304.32-2.fc16.x86_64

=======================

---------- Post added at 09:33 PM ---------- Previous post was at 09:29 PM ----------

==> this may also be in-correct as the issues may be related to Nvidia Driver 304.32+ and not 295.59

---------- Post added at 09:41 PM ---------- Previous post was at 09:33 PM ----------

uname -a ; rpm -qa 'kernel*' --queryformat "%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n"|sort
Linux naipaulpc 3.4.9-1.fc16.x86_64 #1 SMP Wed Aug 15 20:45:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
kernel-3.4.6-1.fc16.x86_64
kernel-3.4.7-1.fc16.x86_64
kernel-3.4.9-1.fc16.x86_64
kernel-devel-3.4.6-1.fc16.x86_64
kernel-devel-3.4.7-1.fc16.x86_64
kernel-devel-3.4.9-1.fc16.x86_64
kernel-headers-3.4.9-1.fc16.x86_64
kernel-tools-3.4.9-1.fc16.x86_64

---------- Post added at 09:42 PM ---------- Previous post was at 09:41 PM ----------

uname -a ; rpm -qa 'kernel*' --queryformat "%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n"|sort
Linux naipaulpc 3.4.9-1.fc16.x86_64 #1 SMP Wed Aug 15 20:45:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
kernel-3.4.6-1.fc16.x86_64
kernel-3.4.7-1.fc16.x86_64
kernel-3.4.9-1.fc16.x86_64
kernel-devel-3.4.6-1.fc16.x86_64
kernel-devel-3.4.7-1.fc16.x86_64
kernel-devel-3.4.9-1.fc16.x86_64
kernel-headers-3.4.9-1.fc16.x86_64
kernel-tools-3.4.9-1.fc16.x86_64

***Dan*** · #14 21st August 2012, 09:59 PM

*Sigh!*

Threads merged. One at a time per customer, per subject.

TrickyHarry · #15 21st August 2012, 11:40 PM

Sorry, I did not see your note, but I did notice that my 2nd thread disappeared ....