Hello, The dmesg for the boot is this: http://pastebin.com/aXJQiprL
The dmesg when the flashing started to occur: http://pastebin.com/GkRcpK80 I kept the config a simple as possible. No bumblebee, just LVDS1 and DP1 without adaptors. my Xorg.0.log is this: http://pastebin.com/2vK37TNr Thanks! -rsd 2013/12/10 Jani Nikula <jani.nik...@linux.intel.com> > On Mon, 09 Dec 2013, Raul Dias <r...@dias.com.br> wrote: > > Hello, > > > > I have a Dell L502x which have a optimus Graphic Pack: > > > > 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core > > Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA > > controller]) > > Subsystem: Dell Device 050e > > Flags: bus master, fast devsel, latency 0, IRQ 51 > > Memory at f1400000 (64-bit, non-prefetchable) [size=4M] > > Memory at e0000000 (64-bit, prefetchable) [size=256M] > > I/O ports at 4000 [size=64] > > Expansion ROM at <unassigned> [disabled] > > Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- > > Capabilities: [d0] Power Management version 2 > > Capabilities: [a4] PCI Advanced Features > > Kernel driver in use: i915 > > > > > > Using driver: > > 2.99.905+git20131023.b70390b4 > > > > When I use a DELL U2713HM Monitor on the DisplayPort, it will flash > blank > > for 5 seconds in a 10 minutes interval. > > The monitor is at 2560x1440 (60hz). > > > > This is not ideal, but I can live with. > > > > > > The big problem is when using bumblebee with intel-virtual-output -b. > > > > In this case the monitor will enter in energy save state instead. > > > > The only way back is to turn it off and on with xrandr: > > > > xrandr --output DP1 --off > > xrandr --output DP1 --auto > > > > The odd thing is if I use instead a Mini DisplayPort adapter to a Dual > DVI > > output, this problem will not happen. > > > > The downside of this solution is that I will need to add a new mode at > 41hz > > with: > > > > xrandr --newmode "2560x1440_41" 162.00 2560 2608 2640 2720 1440 > > 1443 1448 1468 +hsync +vsync > > > > > > So, What I am looking at is the source of the problem: > > > > If the source of the problem is the driver, which debug information > should > > I provide? > > Please provide dmesg with drm.debug=0xe module parameter from early boot > to the problem. If the problem takes a long time to reproduce, you can > provide two dmesgs, one from early boot and another covering the > problem. > > BR, > Jani. > > > > > > Or is it a problem with the DP of the monitor? > > > > Or a problem with the Display Card? > > > > Or should I lower the frequency in the DisplayPort (as with the DVI)? > > > > > > thanks > > -rsd > > _______________________________________________ > > Intel-gfx mailing list > > Intel-gfx@lists.freedesktop.org > > http://lists.freedesktop.org/mailman/listinfo/intel-gfx > > -- > Jani Nikula, Intel Open Source Technology Center >
_______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
