[LGA 1155 motherboards] Multi-Monitor does NOT work when 1 monitor uses Intel GPU and another monitor uses Nvidia GPU -- (Sandy Bridge & Ivy Bridge iGPU)

John Reiser jreiser at bitwagon.com
Wed Jun 13 18:19:08 UTC 2012


I have an ASUS P8Z68-V/GEN3 main board which can run the Intel HD3000
graphics which is builtin, using a i5 Sandy Bridge CPU.  The box also
has an nVidia GeForce GT 430 card (PCI 10de:0de1 rev a1).
I usually run only one monitor (from the nVidia card), but I decided
to experiment.

The American Megatrends BIOS (version 0301 [original; now old]) has
System Agent Configuration options Initiate [Initial] Graphic Adapter,
and iGPU Multi-monitor.  I set iGPU as the initial monitor, and
iGPU Multi-monitor to Enabled, and connect two monitors: one to the
VGA port of the Intel graphics, one to the VGA port of the nVidia card.
Upon reboot, then both LCD monitors turn on their backlights.
The monitor connected to the Intel VGA port gets the BIOS and GRUB
displays, and becomes the normal monitor.  The monitor connected to the
nVidia VGA port gets no normal display, and after a few seconds the
hardware in the monitor detects "No display" and turns itself off.

The F-17 Gnome3 desktop System Settings > Displays detects only the display
that is connected to the Intel VGA port.  xrandr also shows only the
ports that are associated with the builtin Intel hardware.
/var/log/Xorg.0.log shows only the monitor with the normal display.
Only the VGA ports seem to be active in this two-monitor attempt.
Using anything other than VGA ports (both cards have DVI and HDMI ports, too;
both monitors have VGA and DVI connectors) produces no display on any non-VGA
connection.

One monitor (6 years old; 1280x1024) reports EDID info, the other does not
(9 years old; 1024x768.)  Interchanging monitor<->"card" connections
has no observed effect on behavior.

So, it seems to me that this setup "fails multi-monitor usage"
in the manner that Malcolm Turmel describes.
My box has no other operating system installed, so I cannot say
anything about whether multi-monitor works with any other operating system.

syslog (/var/log/messages) detects the Intel graphics hardware as:
Jun 13 10:24:49 f17e64 kernel: [    1.020600] agpgart-intel 0000:00:00.0: Intel Sandybridge Chipset
Jun 13 10:24:49 f17e64 kernel: [    1.020698] agpgart-intel 0000:00:00.0: detected gtt size: 2097152K total, 262144K mappable
Jun 13 10:24:49 f17e64 kernel: [    1.021529] agpgart-intel 0000:00:00.0: detected 65536K stolen memory
Jun 13 10:24:49 f17e64 kernel: [    1.021610] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xc0000000
Jun 13 10:24:49 f17e64 kernel: [    2.494960] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver
Jun 13 10:24:49 f17e64 kernel: [    2.495798] fbcon: inteldrmfb (fb0) is primary device
Jun 13 10:24:49 f17e64 kernel: [    2.660097] fb0: inteldrmfb frame buffer device
Jun 13 10:24:49 f17e64 kernel: [   11.189735] hda_intel: Disabling MSI

syslog detects the nVidia hardware as:
Jun 13 10:24:49 f17e64 kernel: [    1.501442] [drm] Initialized drm 1.1.0 20060810
Jun 13 10:24:49 f17e64 kernel: [    1.507444] [drm] nouveau 0000:01:00.0: Detected an NVc0 generation card (0x0c1080a1)
Jun 13 10:24:49 f17e64 kernel: [    1.513098] [drm] nouveau 0000:01:00.0: Attempting to load BIOS image from PRAMIN
Jun 13 10:24:49 f17e64 kernel: [    1.522820] [drm] nouveau 0000:01:00.0: ... BIOS signature not found
Jun 13 10:24:49 f17e64 kernel: [    1.522822] [drm] nouveau 0000:01:00.0: Attempting to load BIOS image from PROM
Jun 13 10:24:49 f17e64 kernel: [    1.821809] [drm] nouveau 0000:01:00.0: ... appears to be valid
Jun 13 10:24:49 f17e64 kernel: [    1.821811] [drm] nouveau 0000:01:00.0: BIT BIOS found
Jun 13 10:24:49 f17e64 kernel: [    1.821813] [drm] nouveau 0000:01:00.0: Bios version 70.08.29.00
Jun 13 10:24:49 f17e64 kernel: [    1.821815] [drm] nouveau 0000:01:00.0: TMDS table version 2.0
Jun 13 10:24:49 f17e64 kernel: [    1.822011] [drm] nouveau 0000:01:00.0: MXM: no VBIOS data, nothing to do
Jun 13 10:24:49 f17e64 kernel: [    1.822013] [drm] nouveau 0000:01:00.0: DCB version 4.0
Jun 13 10:24:49 f17e64 kernel: [    1.822015] [drm] nouveau 0000:01:00.0: DCB outp 00: 01000302 00020030
Jun 13 10:24:49 f17e64 kernel: [    1.822016] [drm] nouveau 0000:01:00.0: DCB outp 01: 02000300 00000000
Jun 13 10:24:49 f17e64 kernel: [    1.822017] [drm] nouveau 0000:01:00.0: DCB outp 02: 04011310 00020020
Jun 13 10:24:49 f17e64 kernel: [    1.822019] [drm] nouveau 0000:01:00.0: DCB outp 03: 02022362 00020010
Jun 13 10:24:49 f17e64 kernel: [    1.822020] [drm] nouveau 0000:01:00.0: DCB conn 00: 00001030
Jun 13 10:24:49 f17e64 kernel: [    1.822021] [drm] nouveau 0000:01:00.0: DCB conn 01: 00000100
Jun 13 10:24:49 f17e64 kernel: [    1.822022] [drm] nouveau 0000:01:00.0: DCB conn 02: 00002261
Jun 13 10:24:49 f17e64 kernel: [    1.822036] [drm] nouveau 0000:01:00.0: Adaptor not initialised, running VBIOS init tables.
Jun 13 10:24:49 f17e64 kernel: [    1.822037] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 0 at offset 0x6BB6
Jun 13 10:24:49 f17e64 kernel: [    1.882705] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 1 at offset 0x71FC
Jun 13 10:24:49 f17e64 kernel: [    1.909746] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 2 at offset 0x8391
Jun 13 10:24:49 f17e64 kernel: [    1.909753] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 3 at offset 0x8395
Jun 13 10:24:49 f17e64 kernel: [    1.909807] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 4 at offset 0x847D
Jun 13 10:24:49 f17e64 kernel: [    1.909809] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table at offset 0x84E2
Jun 13 10:24:49 f17e64 kernel: [    1.954104] [drm] nouveau 0000:01:00.0: 3 available performance level(s)
Jun 13 10:24:49 f17e64 kernel: [    1.954107] [drm] nouveau 0000:01:00.0: 0: core 50MHz shader 101MHz memory 135MHz timing 0 voltage 880mV
Jun 13 10:24:49 f17e64 kernel: [    1.954109] [drm] nouveau 0000:01:00.0: 1: core 405MHz shader 810MHz memory 324MHz timing 1 voltage 900mV
Jun 13 10:24:49 f17e64 kernel: [    1.954112] [drm] nouveau 0000:01:00.0: 3: core 700MHz shader 1400MHz memory 600MHz timing 3 voltage 1080mV
Jun 13 10:24:49 f17e64 kernel: [    1.954188] [drm] nouveau 0000:01:00.0: c: core 405MHz shader 810MHz memory 324MHz voltage 900mV
Jun 13 10:24:49 f17e64 kernel: [    1.956084] [drm] nouveau 0000:01:00.0: Detected 1024MiB VRAM
Jun 13 10:24:49 f17e64 kernel: [    1.957868] [drm] nouveau 0000:01:00.0: 512 MiB GART (aperture)
Jun 13 10:24:49 f17e64 kernel: [    1.965067] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
Jun 13 10:24:49 f17e64 kernel: [    1.965068] [drm] No driver support for vblank timestamp query.
Jun 13 10:24:49 f17e64 kernel: [    1.965126] [drm] nouveau 0000:01:00.0: ACPI backlight interface available, not registering our own
Jun 13 10:24:49 f17e64 kernel: [    2.109037] [drm] nouveau 0000:01:00.0: allocated 1024x768 fb: 0x1a0000, bo ffff880424ed7000
Jun 13 10:24:49 f17e64 kernel: [    2.109136] [drm] Initialized nouveau 0.0.16 20090420 for 0000:01:00.0 on minor 0
Jun 13 10:24:49 f17e64 kernel: [    2.207643] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
Jun 13 10:24:49 f17e64 kernel: [    2.207645] [drm] Driver supports precise vblank timestamp query.
Jun 13 10:24:49 f17e64 kernel: [    2.298122] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
Jun 13 10:24:49 f17e64 kernel: [    2.661763] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 1
Jun 13 10:26:33 f17e64 kernel: [  117.645376] [drm] nouveau 0000:01:00.0: DDC responded, but no EDID for HDMI-A-1

-- 


More information about the devel mailing list