I use TwinView on my laptop to drive two Samsung SyncMaster EX2220s (one DVI, one VGA). After updating to any driver after 275.09.07, the graphics card (GeForce 8400M G) recognizes all the displays, but removes the digital display. [ 14926.917] (--) NVIDIA(0): Connected display device(s) on GeForce 8400M G at PCI:1:0:0 [ 14926.917] (--) NVIDIA(0): Samsung SMEX2220 (CRT-0) [ 14926.917] (--) NVIDIA(0): Nvidia Default Flat Panel (DFP-0) [ 14926.917] (--) NVIDIA(0): Samsung SMEX2220 (DFP-1) [ 14926.917] (--) NVIDIA(0): Samsung SMEX2220 (CRT-0): 400.0 MHz maximum pixel clock [ 14926.917] (--) NVIDIA(0): Nvidia Default Flat Panel (DFP-0): 330.0 MHz maximum pixel [ 14926.917] (--) NVIDIA(0): clock [ 14926.917] (--) NVIDIA(0): Nvidia Default Flat Panel (DFP-0): Internal Dual Link LVDS [ 14926.917] (--) NVIDIA(0): Samsung SMEX2220 (DFP-1): 165.0 MHz maximum pixel clock [ 14926.917] (--) NVIDIA(0): Samsung SMEX2220 (DFP-1): Internal Single Link TMDS [ 14926.922] (**) NVIDIA(0): TwinView enabled [ 14926.922] (II) NVIDIA(0): Display Devices found referenced in MetaMode: CRT-0, DFP-0, [ 14926.922] (II) NVIDIA(0): DFP-1 [ 14926.922] (WW) NVIDIA(0): There are only 2 heads available, trimming display device list [ 14926.922] (WW) NVIDIA(0): from "CRT-0, DFP-0, DFP-1" to "CRT-0, DFP-0". Reproducible: Always Steps to Reproduce: 1. configure xorg-server as attached 2. upgrade nvidia-drivers 3. place bagel-bites in toaster-oven 4. start xorg-server or xdm 5. consume bagel-bites in consulation for lack of additional screen Actual Results: TwinView will only actually recognize the internal LCD (DFP-0), and the external VGA (CRT-0). Expected Results: TwinView recognizes the internal LCD (DFP-0), external LCD (DFP-1), and the external VGA (CRT-0). I'll be filing a bug report with nVidia, but I figured other people are probably running into, or will run into, the same problem. I was able to download an old copy of the 275.09.07 ebuild from cvs, which seems to be a workaround until nVidia fixes the bugs with the new drivers (hopefully).
Created attachment 309681 [details] xorg.conf
Created attachment 309683 [details] emerge --info
Your config is saying there's DFP-1 but the driver sees it as DFP-0 and that there's no DFP-1 so it removes DFP-1 from being available. You probably need to clean up your config to something like... Option "TwinView" "1" Option "TwinViewXineramaInfoOrder" "DFP-0" Option "metamodes" "CRT-0: nvidia-auto-select +1920+0, DFP-0: nvidia-auto-select +0+0" Which I believe is what you're trying to do where your right hand monitor is your main monitor and your desktop extends onto the left hand side. Either way, you can probably run nvidia-xconfig and have it redo your configs for you.
I haven't tried using nvidia-xconfig quite yet, but I think DFP-0 is actually the laptop's LCD screen. I filed a bug report with nVidia, but I haven't heard anything back. I'm still using the deleted ebuild for version 275.09.07 (which has dependencies on older versions of xorg). If cleaning up xorg.conf doesn't work, do you think nouveau might be worth a shot?
Have you fixed your xorg.conf yet? Switching to nouveau over this is like changing banks cause you can't remember your PIN # and don't want to go in and ask them to reset it.
(In reply to comment #5) > Have you fixed your xorg.conf yet? Switching to nouveau over this is like > changing banks cause you can't remember your PIN # and don't want to go in > and ask them to reset it. I apologize for the delay (I've been in the middle of a move across the country). I was able to get the driver to recognize DFP-0, and utilize it in TwinView. However, the driver enumerates DFP-0 as the laptop's LCD screen, instead of the monitor connected via DVI. So, I can get TwinView to work now, but it only works with the laptop screen and one of the two Samsung monitors. I had to disassemble my desk, but I should be putting everything back together in the next couple weeks or so. I would be able to test more at that point, but I'm kind of stuck on my laptop for a while.
>=x11-drivers/nvidia-drivers-302.17 resolves this issue
