Go Back   nV News Forums > Linux Support Forums > NVIDIA Linux

Newegg Daily Deals

Reply
 
Thread Tools
Old 11-14-06, 11:24 AM   #1
MonkFish
Registered User
 
Join Date: Apr 2006
Posts: 27
Question [SOLVED - kind of] Twinview fails + missing 'wfb' module

Greetings all

Recently updated my installation and hit a frustrating problem. Previously I have had working a stable twinview configuration across two 1600x1200 DFP monitors with Xorg 7.1. Following the new update, however, the desktop is displayed on only one monitor.

There are two problems which are obvious in the log file, but I have no idea how to fix.

Problem 1: A missing module named 'WFB'. Cannot find this beastie in either the usual documentation nor Google
Problem 2: The Xorg log indicates that, although two flat panels are detected and their resolutions are correctly determined at 1600x1200, the combined virtual screen space is still 1600x1200 rather than the correct 3200x1200

I've attached Xorg.0.log from the current non-working config, Xorg.1.log from the previous working config and, of course, nvidia-bug-report.log.

Any help gratefully received.

MF

(P.S.: I note nvidia-bug-report.sh has included an old /var/log/XFree86.0.log - ignore this, 'tis from my olden XFree/ATI days. I've since seen the light, obviously )
Attached Files
File Type: log nvidia-bug-report.log (138.5 KB, 112 views)
File Type: log Xorg.0.log (26.4 KB, 104 views)
File Type: log Xorg.1.log (30.3 KB, 104 views)

Last edited by MonkFish; 11-20-06 at 08:08 AM.
MonkFish is offline   Reply With Quote
Old 11-14-06, 12:10 PM   #2
netllama
NVIDIA Corporation
 
Join Date: Dec 2004
Posts: 8,763
Default Re: Twinview fails + missing 'wfb' module

This might be your problem:
(WW) NVIDIA(0): Cannot find size of first mode for Iiyama PLE511S (DFP-0);

If you request a 1600x1200 Mode, does that have any impact?

Thanks,
Lonni
netllama is offline   Reply With Quote
Old 11-14-06, 02:03 PM   #3
majoridiot
Registered User
 
Join Date: Aug 2006
Posts: 18
Default Re: Twinview fails + missing 'wfb' module

could you post a copies of both the previously working and new non-functional xorg.conf? it would help.
majoridiot is offline   Reply With Quote
Old 11-14-06, 06:15 PM   #4
MonkFish
Registered User
 
Join Date: Apr 2006
Posts: 27
Default Re: Twinview fails + missing 'wfb' module

Quote:
Originally Posted by netllama
This might be your problem:
(WW) NVIDIA(0): Cannot find size of first mode for Iiyama PLE511S (DFP-0);

If you request a 1600x1200 Mode, does that have any impact?

Thanks,
Lonni
I did specifically request the 1600x1200 mode (I think!) in the xorg.conf file:

Option "MetaModes" "1600x1200,1600x1200"

Is this correct?

Additionally, you may see that in the old Xorg.1.log file, the size of the mode for DFP-0 was found:

Xorg.1.log
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0): "1600x1200,1600x1200"
(II) NVIDIA(0): Virtual screen size determined to be 3200 x 1200
(--) NVIDIA(0): DPI set to (99, 98); computed from "UseEdidDpi" X config

as opposed to the error in the 'new' Xorg.0.log

Xorg.0.log
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0): "1600x1200,1600x1200"
(II) NVIDIA(0): Virtual screen size determined to be 1600 x 1200
(WW) NVIDIA(0): Cannot find size of first mode for Iiyama PLE511S (DFP-0);
(WW) NVIDIA(0): cannot compute DPI from Iiyama PLE511S (DFP-0)'s EDID.
(==) NVIDIA(0): DPI set to (75, 75); computed from built-in default
MonkFish is offline   Reply With Quote
Old 11-14-06, 06:23 PM   #5
MonkFish
Registered User
 
Join Date: Apr 2006
Posts: 27
Default Re: Twinview fails + missing 'wfb' module

Quote:
Originally Posted by majoridiot
could you post a copies of both the previously working and new non-functional xorg.conf? it would help.
As it happens, I have not changed xorg.conf whatsoever. But, in any event, here it is:

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (root@localhost) Mon Feb 6 22:33:41 GMT 2006

# File generated by xorgconfig.
#
# Copyright 2004 The X.Org Foundation
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
#
# Except as contained in this notice, the name of The X.Org Foundation shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from
# The X.Org Foundation.
#
# ************************************************** ********************
# Refer to the xorg.conf(5x) man page for details about the format of
# this file.
# ************************************************** ********************
# ************************************************** ********************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# ************************************************** ********************
#
# ************************************************** ********************
# Files section. This allows default font and rgb paths to be set
# ************************************************** ********************
# ************************************************** ********************
# Server flags section.
# ************************************************** ********************
# ************************************************** ********************
# Input devices
# ************************************************** ********************
# ************************************************** ********************
# Core keyboard's InputDevice section
# ************************************************** ********************
# ************************************************** ********************
# Core Pointer's InputDevice section
# ************************************************** ********************
# ************************************************** ********************
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the xorg.conf man page for a description of the options.
# ************************************************** ********************
#
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# ************************************************** ********************
# Monitor section
# ************************************************** ********************
# Any number of monitor sections may be present
# ************************************************** ********************
# Graphics device section
# ************************************************** ********************
# ************************************************** ********************
# Screen sections
# ************************************************** ********************
# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
# ************************************************** ********************
# ServerLayout sections.
# ************************************************** ********************
# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.
# Section "DRI"
# Mode 0666
# EndSection

Section "ServerLayout"

# The Identifier line must be present
# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.
# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".
Identifier "Simple Layout"
Screen "Screen 0" 0 0
# Screen "Screen 1" RightOf "Screen 0"
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection

Section "Files"

# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
#
# The module search path. The default path is shown here.
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/Type1/"
FontPath "/usr/share/fonts/CID/"
FontPath "/usr/share/fonts/75dpi/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/Speedo/"
FontPath "/usr/share/fonts/TrueType/"
FontPath "/usr/share/fonts/freefont/"
EndSection

Section "Module"

# This loads the DBE extension module.
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
# This loads the font modules
# Load "dri"
# Load "dbe" # Double buffer extension
Load "extmod"
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
Load "type1"
# Load "speedo"
Load "freetype"
# Load "xtt"
# This loads the GLX module
Load "glx"
# Load "i2c"
# Load "bitmap"
# Load "ddc"
# Load "int10"
# This loads the DRI module
EndSection

Section "InputDevice"

# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.
# Option "Protocol" "Xqueue"
# Option "Xleds" "1 2 3"
# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# These are the default XKB settings for Xorg
# Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Identifier "Keyboard1"
Driver "kbd"
Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
Option "XkbModel" "pc105"
Option "XkbLayout" "gb"
EndSection

Section "InputDevice"

# Identifier and driver
# Option "Resolution" "256"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
# Option "Protocol" "Xqueue"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"
# ChordMiddle is an option for some 3-button Logitech mice
# Option "ChordMiddle"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "PS/2"
Option "Device" "/dev/psaux"
# Mouse-speed setting for PS/2 mouse.
EndSection

Section "Monitor"
Identifier "mon0"
HorizSync 31.5 - 82.0
VertRefresh 60.0 - 60.0
Option "DPMS" "true"
EndSection

Section "Device"
Identifier "nvid0"
Driver "nvidia"
VendorName "nVidia Corporation"
BoardName "geForce 7800 GS"
BusID "PCI:1:0:0"
Screen 0
# Option "AllowGLXWithComposite" "true"
EndSection

Section "Screen"
Identifier "Screen 0"
Device "nvid0"
Monitor "mon0"
DefaultDepth 24
Option "RenderAccel" "true"
Option "NvAGP" "3"
# Option "NoLogo" "true"
Option "AllowDDCCI" "true"
Option "Coolbits" "1"
Option "HWcursor" "true"
Option "AddARGBGLXVisuals" "true"

Option "Twinview"
Option "MetaModes" "1600x1200,1600x1200"
Option "TwinviewOrientation" "RightOf"
Option "UseEdidDpi" "TRUE"
# Option "DPI" "96x96"
Option "SecondMonitorHorizSync" "UseEdidFreqs"
Option "SecondMonitorVertRefresh" "UseEdidFreqs"
# Option "ConnectedMonitor" "DFP,DFP"
EndSection

Section "Extensions"
Option "Composite" "true"
EndSection

#Section "DRI"
# Group 0
# Mode 0666
#EndSection
MonkFish is offline   Reply With Quote
Old 11-14-06, 06:35 PM   #6
netllama
NVIDIA Corporation
 
Join Date: Dec 2004
Posts: 8,763
Default Re: Twinview fails + missing 'wfb' module

Metamodes are not Modes. You should try adding a Modes entry to the Screen section which explicitly requests a 1600x1200 mode.
netllama is offline   Reply With Quote
Old 11-14-06, 07:05 PM   #7
MonkFish
Registered User
 
Join Date: Apr 2006
Posts: 27
Default Re: Twinview fails + missing 'wfb' module

Quote:
Originally Posted by netllama
Metamodes are not Modes. You should try adding a Modes entry to the Screen section which explicitly requests a 1600x1200 mode.
OK - should I not be requesting, though, 3200x1200 rather than 1600x1200?

Thanks!
MonkFish is offline   Reply With Quote
Old 11-14-06, 07:06 PM   #8
netllama
NVIDIA Corporation
 
Join Date: Dec 2004
Posts: 8,763
Default Re: Twinview fails + missing 'wfb' module

No, you want 1600x1200, unless your DFP is capable of 3200x1200.
netllama is offline   Reply With Quote

Old 11-14-06, 07:18 PM   #9
MonkFish
Registered User
 
Join Date: Apr 2006
Posts: 27
Default Re: Twinview fails + missing 'wfb' module

Quote:
Originally Posted by netllama
No, you want 1600x1200, unless your DFP is capable of 3200x1200.
Excuse my stupidity, but would you clarify for me: I have two DFPs, each at 1600x1200. But only one screen section. Are you suggesting that I simply place a single 1600x1200 entry in this?
MonkFish is offline   Reply With Quote
Old 11-14-06, 07:53 PM   #10
netllama
NVIDIA Corporation
 
Join Date: Dec 2004
Posts: 8,763
Default Re: Twinview fails + missing 'wfb' module

Correct, the Modes line belongs in the Screen section. Alternatively, you could purge your current xorg.conf and simply run:
nvidia-xconfig -a --twinview

Thanks,
Lonni
netllama is offline   Reply With Quote
Old 11-15-06, 12:53 AM   #11
longshot
Registered User
 
Join Date: Jun 2006
Posts: 17
Default Re: Twinview fails + missing 'wfb' module

I was having a similar problem, but now things are working.

Previously, one of the monitor's edid seemed to be corrupted like yours


(--) NVIDIA(0): Connected display device(s) on GeForce 6600 GT at PCI:3:0:0:
(--) NVIDIA(0): HP 7650 (CRT-0)
(--) NVIDIA(0): @@@ (CRT-1)
(--) NVIDIA(0): HP 7650 (CRT-0): 400.0 MHz maximum pixel clock
(--) NVIDIA(0): @@@ (CRT-1): 400.0 MHz maximum pixel clock
...
(II) NVIDIA(0): Virtual screen size determined to be 1600 x 1200


Now with things working I get

(--) NVIDIA(0): Connected display device(s) on GeForce 6600 GT at PCI:3:0:0:
(--) NVIDIA(0): HP 7650 (CRT-0)
(--) NVIDIA(0): HP 7650 (CRT-1)
(--) NVIDIA(0): HP 7650 (CRT-0): 400.0 MHz maximum pixel clock
(--) NVIDIA(0): HP 7650 (CRT-1): 400.0 MHz maximum pixel clock
...
(II) NVIDIA(0): Virtual screen size determined to be 3200 x 1200


In investigating the problem I tried a lot of different things, including backing down through several driver versions (9742, 9629, 8776), changing settings in xorg.conf, checking physical connections etc.

I have a suspicion the problem may have been due to the physical connection not engaging the ddc pins properly ... but cant reproduce. On the dvi-vga adapter if I have it right the ddc pins are short ones next to the blade and when the connector is not screwed in they may not connect properly/intermittently.

However, I still had the problem even when I turned off use of edids
Option "UseEdidFreqs" "false"
although I just noticed I didnt set
# Option "ModeValidation" "NoEdidModes"

Anyhow, I'm now using the edids but with MetaModes to give resolutions (specifically 1600x1200), otherwise a lower resolution gets selected. All my Modes are commented out, so they dont seem to be required.
longshot is offline   Reply With Quote
Old 11-15-06, 12:31 PM   #12
MonkFish
Registered User
 
Join Date: Apr 2006
Posts: 27
Default Re: Twinview fails + missing 'wfb' module

I inserted a mode section, containing just

SubSection "Display"
Depth 24
Modes "1600x1200"
EndSubSection

And guess what? The screen-that-did-not-work now shows a display at ... 1280x1024 - not 1600x1200!!!

As they say, ooo-eerrr. Additionally, that very strange (no-one has commented on it thus far) "Missing wfb module" issue remains.

WTF is WFB?
MonkFish is offline   Reply With Quote
Reply


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


Similar Threads
Thread Thread Starter Forum Replies Last Post
X Failed to load NVdriver c00lr4c3r NVIDIA Linux 13 10-22-02 02:44 PM
Glx mrbig1344 NVIDIA Linux 7 09-30-02 07:45 AM
Error messages... HELP!!!! Imperito NVIDIA Linux 3 09-24-02 11:46 PM
GForce drivers installed...but dont work tomfullery NVIDIA Linux 6 09-22-02 09:23 AM
Need help to get the X to work on my Acer TravelMate 630 knchee NVIDIA Linux 16 09-19-02 11:16 PM

All times are GMT -5. The time now is 11:41 AM.


Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.