Bug 109421 - kudzu doesn't make my dual monitor work (1 agp + 1 pci video card)
Summary: kudzu doesn't make my dual monitor work (1 agp + 1 pci video card)
Alias: None
Product: Fedora
Classification: Fedora
Component: kudzu   
(Show other bugs)
Version: 1
Hardware: athlon Linux
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2003-11-07 18:09 UTC by lupus
Modified: 2014-03-17 02:40 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-11-07 23:34:10 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description lupus 2003-11-07 18:09:44 UTC
Description of problem:
I got 2 video adapters: a PCI (S3 Trio64V2 (generic)) with Compaq
151FS  and a AGP (nvidia geforce 3) with ImageQuest Q910

kudzu configures XF86Config only for my S3 Trio64V2 but finds on
startup the S3 and the Geforce 3.

The funny thing is that when I startup my Xfree86, the Geforce 3 gets
loaded with the description of the S3 and with the VESA driver of the S3. 

Can't this be solved by adding both cards to XF86Config and by adding
PCI:0:8:0 to the S3 and PCI:1:0:0 to the Geforce 3. And is it possible
to probe both monitors attached to the cards.

Version-Release number of selected component (if applicable):

How reproducible:
remove /etc/X11/XF86Config and /etc/sysconfig/hwconf and reboot
kudzu will find both cards and ask if I want them configured.
I say yes to both

Steps to Reproduce:
1.Boot Fedora with 2 cards 1 pci + 1 agp
Actual results:
1 monitor used in X with wrong X driver (VESA) and monitor ImageQuest 910.

Expected results:
2 monitors used in X. Geforce 3 with NV driver and ImageQuest 910
monitor. S3 with VESA driver and Compaq 151FS.

Additional info:

# XFree86 4 configuration created by redhat-config-xfree86

Section "ServerLayout"
	Identifier     "Default Layout"
	Screen      0  "Screen0" 0 0
	InputDevice    "Mouse0" "CorePointer"
	InputDevice    "Keyboard0" "CoreKeyboard"
	InputDevice    "DevInputMice" "AlwaysCore"

Section "Files"
# RgbPath is 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 (they are concatenated together)
# By default, Red Hat 6.0 and later now use a font server independent of
# the X server to render fonts.

	RgbPath      "/usr/X11R6/lib/X11/rgb"
	FontPath     "unix/:7100"

Section "Module"
	Load  "dbe"
	Load  "extmod"
	Load  "fbdevhw"
	Load  "glx"
	Load  "record"
	Load  "freetype"
	Load  "type1"

Section "InputDevice"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
#	Option	"Xleds"		"1 2 3"

# To disable the XKEYBOARD extension, uncomment XkbDisable.
#	Option	"XkbDisable"

# 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"	"pc102"
# 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"
# Or if you just want both to be control, use:
#	Option	"XkbOptions"	"ctrl:nocaps"
	Identifier  "Keyboard0"
	Driver      "keyboard"
	Option	    "XkbRules" "xfree86"
	Option	    "XkbModel" "pc105"
	Option	    "XkbLayout" "be"

Section "InputDevice"
	Identifier  "Mouse0"
	Driver      "mouse"
	Option	    "Protocol" "IMPS/2"
	Option	    "Device" "/dev/psaux"
	Option	    "ZAxisMapping" "4 5"
	Option	    "Emulate3Buttons" "no"

Section "InputDevice"
# If the normal CorePointer mouse is not a USB mouse then
# this input device can be used in AlwaysCore mode to let you
# also use USB mice at the same time.
	Identifier  "DevInputMice"
	Driver      "mouse"
	Option	    "Protocol" "IMPS/2"
	Option	    "Device" "/dev/input/mice"
	Option	    "ZAxisMapping" "4 5"
	Option	    "Emulate3Buttons" "no"

Section "Monitor"
	Identifier   "Monitor0"
	VendorName   "Monitor Vendor"
	ModelName    "ImageQuest Q910"
	DisplaySize  360	270
	HorizSync    30.0 - 110.0
	VertRefresh  50.0 - 150.0
	Option	    "dpms"

Section "Device"
	Identifier  "Videocard0"
	Driver      "vesa"
	VendorName  "Videocard vendor"
	BoardName   "S3 Trio64V2 (generic)"

Section "Screen"
	Identifier "Screen0"
	Device     "Videocard0"
	Monitor    "Monitor0"
	DefaultDepth     16
	SubSection "Display"
		Depth     16
		Modes    "800x600" "640x480"

Section "DRI"
	Group        0
	Mode         0666

Comment 1 Bill Nottingham 2003-11-07 23:34:10 UTC
kudzu has no multihead support at the moment.

Note You need to log in before you can comment on or make changes to this bug.