Bug 700847

Not for me on my Dell Latitude E6420 :(

If I remove "nomodeset", when X tries to start, the screen turns blank, but it never comes back.

If I leave "nomodeset" in place, X appears, but after I unsuspend from RAM, the backlight never turns on, so I have to reboot blindly.

Either way, this doesn't work for me.

Here's my card's lspci -vv:

00:02.0 VGA compatible controller: Intel Corporation Device 0126 (rev 09) (prog-if 00 [VGA controller])
        Subsystem: Dell Device 0493
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 47
        Region 0: Memory at e1400000 (64-bit, non-prefetchable) [size=4M]
        Region 2: Memory at d0000000 (64-bit, prefetchable) [size=256M]
        Region 4: I/O ports at 4000 [size=64]
        Expansion ROM at <unassigned> [disabled]
        Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
                Address: fee00000  Data: 4099
        Capabilities: [d0] Power Management version 2
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [a4] PCI Advanced Features
                AFCap: TP+ FLR+
                AFCtrl: FLR-
                AFStatus: TP-
        Kernel modules: i915

I guess this is pretty much the same as mentioned earlier in the bug.

I've also tried i915.modeset=1 and i915.modeset=0 in case "nomodeset" was wrong for me, or something. As you might expect "i915.modeset=0" behaves just like "nomodeset", and the other one behaves just as if I had removed "nomodeset" from the command line.

The results were identical.

I've tried 2.6.38.2-9.fc15.i686.PAE from Fedora 15 Beta.

The results are similar, except for the following:

With i915.modeset=1, X does start, with the results visible in the attachment. I couldn't create an image of what happens after a suspend. The backlight turns on, and many red pixel flicker in the left-most column of the display. So, it's still completely useless.

With i915.modeset=0, it behaves exactly as before, i.e. X works fine, except for DRI and XVideo, but the backlight doesn't come back on after a suspend.

Created attachment 496231 [details]
"screen shot" showing the state of the display with i915.modeset=1

Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please add drm.debug=0x04 to the kernel command line, restart computer, and attach

* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log)
* output of the dmesg command, and
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Created attachment 497469 [details]
dmesg after drm.debug=0x04

2 lines removed to sanitise the log

Created attachment 497470 [details]
Xorg.0.log

Current Xorg.log

Created attachment 497472 [details]
messages file

sanitised - replaced username and domain

also xorg.conf is not being used

Created attachment 497781 [details]
Dell-Latitude-E6420-dmesg.out

Moved to kernel 2.6.39-0.rc5.git5.0.fc16.i686.PAE and it works no better. Here are the requested attachments.

Created attachment 497782 [details]
Dell-Latitude-E6420-messages.log

Created attachment 497783 [details]
Dell-Latitude-E6420-Xorg.0.log

Oh, I have only the following xorg.conf.d snippets:

# This file is autogenerated by system-setup-keyboard. Any 
# modifications will be lost.

Section "InputClass"
	Identifier	"system-setup-keyboard"
	MatchIsKeyboard	"on"
	Option		"XkbModel"	"pc105+inet"
	Option		"XkbLayout"	"us"
#	Option		"XkbVariant"	"(null)"
	Option		"XkbOptions"	"terminate:ctrl_alt_bksp,"
EndSection
Section "ServerFlags"
	Option "DontVTSwitch" "false"
EndSection
# Section "InputClass"
#     Identifier "force touchpad"
#     MatchProduct "PS/2 Generic Mouse"
#     Driver "synaptics"
# EndSection

So nothing display-related.

I got it to work by installing some Fedora 15 beta rpms:

xorg-x11-server-Xorg-1.10.1-14.fc15.i686
xorg-x11-drv-intel-2.14.0-6.fc15.i686
mesa-dri-drivers-7.11-0.9.20110509.0.fc15.i686
mesa-libGL-7.11-0.9.20110509.0.fc15.i686
mesa-libGLU-7.11-0.9.20110509.0.fc15.i686
xorg-x11-drv-mouse-1.6.99.901-2.fc15.i686
xorg-x11-drv-keyboard-1.5.99.901-2.fc15.i686
xorg-x11-drv-evdev-2.6.0-3.fc15.i686
xorg-x11-drv-synaptics-1.4.0.901-1.fc15.i686
kernel-PAE-2.6.38.6-26.rc1.fc15.i686
kernel-PAE-devel-2.6.38.6-26.rc1.fc15.i686

Hi Gabriel,

i have the same issue with my dell E6420, fedora 15 installed with basic driver only. 

00:02.0 VGA compatible controller: Intel Corporation Device 0126 (rev 09) (prog-
if 00 [VGA controller])
	Subsystem: Dell Device 0493

[root@localhost ~]# cat /etc/X11/xorg.conf
Section "Device"
	Identifier "Videocard0"
	Driver "vesa"
EndSection


when i connect with external monitor not able to detect.


In same model i installed FC16 that perfectly work no need to install with basic driver.

How i can resolve this issue in fedora 15.

current kernel 2.6.38.6-26.rc1.fc15.i686.PAE 

All above mentioned rpm already their, still external monitor/lcd not work.

Rgds,
Raman