[arrandale] [i915] DELL E6510: blank screen on boot (Intel GPU)

[Francisco Cribari]

I am running Ubuntu Linux 10.04 64 bits on a DELL 6510 notebook with integrated Intel graphics card. The machine only boots in a low-graphics mode. I detected the following error message in the logs:

(EE) intel(0): No kernel modesetting driver detected

I used i915,modeset=0 as a kernel option but I am no longer using. The xorg.config file I am using is

Section "Device"
Identifier "Configured Video Device"
BusID "PCI:0:2:0"
Driver "intel"
Option "AccelMethod" "UXA"
EndSection

Section "Module"
Load "glx"
Load "dri"
Load "extmod"
Load "record"
Load "dbe"
Load "GLcore"
Load "xtrap"
Load "freetype"
EndSection

Section "Monitor"
Identifier "Configured Monitor"
EndSection

Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
DefaultDepth 24
EndSection

Section "DRI"
Mode 0666
EndSection

My kernel is

Linux darwin 2.6.32-23-generic #37-Ubuntu SMP Fri Jun 11 08:03:28 UTC 2010 x86_64 GNU/Linux

The intel driver:

ii xserver-xorg-video-intel 2:2.12.0+git20100628.17884af4-0ubuntu0sarvatt~lucid X.Org X server -- Intel i8xx, i9xx display d
ii xserver-xorg-video-intel-dbg 2:2.12.0+git20100628.17884af4-0ubuntu0sarvatt~lucid X.Org X server -- Intel i8xx, i9xx display d

Any suggestions? Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-23-generic 2.6.32-23.37
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-23-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: cribari 1680 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf6960000 irq 22'
   Mixer name : 'Intel G45 DEVIBX'
   Components : 'HDA:111d76d5,1028040b,00100104 HDA:80862804,80860101,00100000'
   Controls : 22
   Simple ctrls : 13
Date: Wed Jun 30 22:11:48 2010
HibernationDevice: RESUME=UUID=0be7bd77-4b1d-4d52-9714-d179a2f4e4e4
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
MachineType: Dell Inc. Latitude E6510
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-23-generic root=UUID=e54980ae-4e77-4c7d-81f0-7f5c7a599611 ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34.1
SourcePackage: linux
dmi.bios.date: 05/28/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 02K3Y4
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA03:bd05/28/2010:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn02K3Y4:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6510
dmi.product.version: 0001
dmi.sys.vendor: Dell Inc.

[Diego Schulz (dschulzg)]

The problem apparently is in the Intel graphics driver.
Meanwhile I'm using the vesa driver, I had to edit the /etc/default/grub file:

## Original:
## GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
## Now:
GRUB_CMDLINE_LINUX_DEFAULT="quiet nomodeset xforcevesa acpi_osi=Linux"

I'm not sure of the effect of

  acpi_osi=Linux

but I couldn't even boot without nomodeset and xforcevesa options.

[Jeremy Foshee (jeremyfoshee)]

Hi Francisco,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Andrew Klossner (o-launchpad-klossner-org)]

I have the same machine as Francisco, the submitter. I have tested the upstream kernel 2.6.34 and verified that the bug is still present. Then I applied this patch to the upstream kernel:
http://lists.freedesktop.org/archives/intel-gfx/2010-June/007232.html
and verified that it fixes the bug. I recommend that the Ubuntu 10.04 LTS kernel adopt this patch.

[Andrew Klossner (o-launchpad-klossner-org)]

After discussing this with Francisco, I removed the needs-upstream-testing tag.

[Francisco Cribari (cribari)]

I can now boot into X using the following kernel:

cribari@darwin:~$ uname -a
Linux darwin 2.6.35-999-generic #201007081234 SMP Thu Jul 8 11:37:16 UTC 2010 x86_64 GNU/Linux

I am using the kernel options "quiet splash".

I have a problem, though. I get a blank screen after I suspend and resume my notebook.

[Francisco Cribari (cribari)]

I believe the suspend/resume problem is related to this bug:

https://bugs.freedesktop.org/show_bug.cgi?id=28739

[Francisco Cribari (cribari)]

The kernel I am now running is

cribari@darwin:~$ uname -a
Linux darwin 2.6.35-020635rc6-generic #020635rc6 SMP Fri Jul 23 10:08:28 UTC 2010 x86_64 GNU/Linux

I am able to boot into X with this kernel. However, when I boot with the newer linux-image-2.6.35-14-generic, I get a blank screen. I have also tried to boot Ubuntu 10.10 alpha 3 from a CD and got a blank screen.

Suggestions are welcome. Thanks.

[Francisco Cribari (cribari)]

Two additional info:

1) The kernel options I am using are: quiet splash acpi_sleep=s3_bios .

2) I tried to boot from the Ubuntu 10.10 alpha 3 CD and also got a blank screen.

[Matthias Kunst (matthiaskunst)]

I can confirm the bug on a Dell Latitude E6510 with intel integrated graphics and the FullHD display (1920x1080).
With the intel driver the screen stays black instead of showing the plymouth screen with the current 2.6.32 kernel in Lucid
and equally on the kernel images 2.6.35-14 up to 2.6.35-16 from the kernel-ppa.
On the other hand I got the intel driver working with the 2.6.35-12 kernel package from the kernel-ppa ( 2.6.35-12.17~lucid1).
So there seems to be a solution that was removed again in the latest kernel release packages.

[Manuel Carro (mcarro)]

According to this comment it

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/578673/comments/98

the bug disappeared in 2.6.35rc6 but was reintroduced in 2.6.35 final. I am running kernel 2.6.35-020635rc6-generic and I can boot fine into X Windows in a dell latitude e6510 (in 32 bits mode). I can suspend and resume with the acpi_sleep=s3_bios kernel option. But I cannot hibernate (wouln't hibernate - it just gets stuck) and more importantly I cannot connect an external monitor / beamer / projector / etc. This is a big drawback for me; the machine just hangs when xrandr is called with the external monitor attached.

Where did you get the pacakges for kernel 2.6.35-12.17~lucid1? I have been unable to locate them.

Thanks in advance.

[Francisco Cribari (cribari)]

I believe you can get recent kernels from

http://kernel.ubuntu.com/~kernel-ppa/mainline/

<http://kernel.ubuntu.com/~kernel-ppa/mainline/>and also from

http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/

<http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/>I was able to
boot to X up until RC6 but not using the 2.6.35 kernel. I have tried to boot
from CD using 10.10 alpha 3, but I got a blank screen.

I haven't tried to hibernate or to plug in an external monitor. Suspend
works for me w/ with the acpi_sleep=s3_bios kernel option.

I hope they will be able to fix these bugs prior to the 10.10 launch.

On Thu, Aug 19, 2010 at 12:13 PM, Manuel Carro <email address hidden>wrote:

> According to this comment it
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/578673/comments/98
>
> the bug disappeared in 2.6.35rc6 but was reintroduced in 2.6.35 final.
> I am running kernel 2.6.35-020635rc6-generic and I can boot fine into X
> Windows in a dell latitude e6510 (in 32 bits mode). I can suspend and
> resume with the acpi_sleep=s3_bios kernel option. But I cannot
> hibernate (wouln't hibernate - it just gets stuck) and more importantly
> I cannot connect an external monitor / beamer / projector / etc. This
> is a big drawback for me; the machine just hangs when xrandr is called
> with the external monitor attached.
>
> Where did you get the pacakges for kernel 2.6.35-12.17~lucid1? I have
> been unable to locate them.
>
> Thanks in advance.
>
> --
> Computer boots in low-graphics mode (intel graphics card)
> https://bugs.launchpad.net/bugs/600453
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Francisco Cribari-Neto, <email address hidden>,
http://sites.google.com/site/cribari

[Matthias Kunst (matthiaskunst)]

I got 2.6.35-12.17~lucid1 from here:
http://launchpad.net/~kernel-ppa/+archive/ppa.
But it seems it was removed from the ppa later.
I think it is really based on 2.6.35rc6, so it matches the experience of comment 12 as 2.6.35-14 from that ppa came out just after the final 2.6.35-release.

[Francisco Cribari (cribari)]

Kernel 2.6.35-17.23~lucid1 also boots to a blank screen (Ubuntu 10.04 64 bits, DELL Latitude E6510 Intel integrated graphics, processor i7).

[Francisco Cribari (cribari)]

Tried kernel 2.6.35-18.24~lucid1. It also boots to a blank screen. (DELL 6510, i7, Intel GPU.)

[Francisco Cribari (cribari)]

I believe this is the same bug:

https://bugs.freedesktop.org/show_bug.cgi?id=29278

PS. Kernel 2.6.35-19.25~lucid1 also boots to a blank screen.

[Francisco Cribari (cribari)]

Ubuntu 10.10 beta boots (from CD) to a blank screen. Hardware: DELL E6510, core i7, Intel GPU, full HD display.

[Corona (stefaniefauconnier)]

Confirmed on a Dell E6510, i5 with intel integrated graphics.

Francisco, I think you should change the bug title to something along the lines of "E6510: blank screen on boot" because that's what the problem really is about - the low graphics mode is just a workaround. Maybe you could also change the description to be a bit more specific (e.g. the kernel versions that have this bug).

[Francisco Cribari (cribari)]

Corona: I followed your suggestion and changed the bug title. It is disappointing, however, to read:

Importance: Undecided
Assigned to: Unassigned

The kernels that work for me are (i) 2.6.32-02063221.201008271307, and (ii) 2.6.35-020635rc6.

I believe this bug is related to

https://bugs.freedesktop.org/show_bug.cgi?id=29278

Finally, a similar bug that affects the E6410 notebook is

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/561802

Let's hope that a developer notices the bug reported here. It is still present in Ubuntu 10.10 beta. Let's hope it gets fixed before October 10, 2010 (10.10 release).

[Corona (stefaniefauconnier)]

Thanks, Francisco. I added the tags [arrandale] and [i915], I hope the bug will attract more attention this way. If anybody is following this bug report, please comment on your experience.

I believe it's exactly the same bug as the one in https://bugs.freedesktop.org/show_bug.cgi?id=29278 .

For the moment I'm running a modified 2.6.35 kernel. I tweaked it to support the e6510's card reader, and I also fixed the blank screen issue by reverting the patch mentioned here https://bugs.freedesktop.org/show_bug.cgi?id=29278#c5 . Apparently, this is not really a proper fix, but it works and it supports external monitors. For suspend and resume, I use the workaround mentioned here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/578673?comments=all . I'm aware that not all this information is relevant to the issue reported here, but I just wanted to give an overview of issues and possible workarounds.

[Manuel Carro (mcarro)]

@Corona: I'm running a drm-intel kernel (2.6.36-rc2) with the patch you mention reverted. Works fine, including external monitors (in a somewhat brittle way, I would say). Card readers are not a high priority for me now - I go around with a small USB card reader. Suspend works with the acpi_sleep kernel option. My current biggest problem is that I cannot make VirtualBox run reliably.

I did not know 2.6.35 supported external monitors. Which release are you using? I may give it a try.

[Corona (stefaniefauconnier)]

Thanks, Manuel. I don't remember exactly which release my kernel is based on, I just downloaded the drm-intel-next branch of 2.6.35 and gave it a try.

[Manuel Carro (mcarro)]

Corona: can your kernel run VirtualBox?

[Corona (stefaniefauconnier)]

never tried it, sorry.

[crazydave (crazy-dave)]

Same problem here.

I installed with the actual kubuntu desktop alternate CD (32bit) and no problem with the kernel 2.6.32-24-generic #39
But with the next update to the image-kernel 2.6.32-24-generic #42 the screen is blank after reboot.

[Francisco Cribari (cribari)]

Kernel 2.6.35-20.29~lucid1 also boots to a blank screen. Hardware is DELL 6510, core i7, full HD display, Intel integrated graphics, bios A03.

[Chris Halse Rogers (raof)]

Patch series with fixes for E6510 machines has been recently committed to drm-intel-next, starting at http://cgit.freedesktop.org/~ickle/drm-intel/commit/?h=drm-intel-next&id=7eaf5547d0460027b15a297bb15d80bdd600cb41
and finishing http://cgit.freedesktop.org/~ickle/drm-intel/commit/?h=drm-intel-next&id=2c9d97545914cc764786702f361a1f1c9bb8dfa9 .

[aanno (thomas-pasch)]

Vanilla 2.6.36-rc4 (from kernel.org) partly fixes this issue (at least on my machine): After switching to a console and back to X11, display is working as expected. However, I still see nothing on the (virtual) consoles...

Also see http://lwn.net/Articles/404632/

[Francisco Cribari (cribari)]

Kernel 2.6.35-21.30~lucid1 also boots to a blank screen. Hardware is DELL E6510, core i7, full HD display, Intel GPU, bios A03.

[Francisco Cribari (cribari)]

Kernel 2.6.36-997.201009160905 also boots to a blank screen. Hardware is DELL E6510, core i7, full HD display, Intel GPU, bios A03.

[Manuel Carro (mcarro)]

Kernel 2.6.36-rc4 from http://kernel.ubuntu.com/~kernel-ppa/mainline/ works quite well, although sometimes (when the panel is off) one has to switch to the console and then to the graphic display.

[Francisco Cribari (cribari)]

Kernel 2.6.35-22.33~lucid1 also boots to a blank screen. Hardware is DELL E6510, core i7, full HD display, Intel GPU, bios A03.

[Jerone Young (jerone)]

The issue is nauvous driver.

To boot and install add the following to the kernel command line:
nouveau.modeset=0

I have actually spun a special version of 10.04.1 just for E6150. Hope this helps folks out:
http://people.canonical.com/~jerone/special/ottawa-latitude-6510-Nvidia/

[Corona (stefaniefauconnier)]

Are you sure this is for intel gpu's, and not nvidia? Nouveau sounds a lot like nvidia to me, this bug is specific to intel integrated graphics. Nvidia chipsets have other issues I believe.

[Francisco Cribari (cribari)]

Is there any chance that this will be fixed in 10.10 (to be released on October 10)?

[Chris Halse Rogers (raof)]

This issue is specific to E6150 machines with the Intel GPU. E6150 machines with nVidia GPUs may well have different issues.

We're past the final kernel freeze. While there's a slim possibility that it will get into the kernel on the release CDs, more likely is that it'll be fixed in an update.

It would be helpful to test if the kernel from the kernel-team mainline PPA here: http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/current/ works. That should have the above named commits which fix the E6150, at least for the developer :).

[Manuel Carro (mcarro)]

@ #36:

Chris,

what is the relationship between that kernel (http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/current/) and the rc4 and rc5 for Maverick? (v2.6.36-rc4-maverick and v2.6.36-rc5-maverick), both under http://kernel.ubuntu.com/~kernel-ppa/mainline/? I used rc4 for maybe two weeks and rc5 for a couple of days and they work quite well re. the display. They still need to switch to console then back to graphical display occasionally in my case (Dell Latitude E6510, intel i5, integrated Intel with full HD), but they work nicely otherwise. Would I get anything extra from the drm-intel-next variant? Or would I contribute more if I test the drm-intel-next than if I test the v2.6.36-rc5-maverick version?

Thanks!

[Manuel Carro (mcarro)]

A note on #37: somehow v2.6.36-rc5-maverick show a load of 1.7 to 1.9 (given by, e.g., uptime or htop) when nothing special is running and gkrellm does not show special CPU activity. The laptop does not seem to actually be under that load - no special heat and no fans started. Might it be that the kernel is reporting a wrong load? What could be a good place to report this?

[Chris Halse Rogers (raof)]

From what I can tell, the patches I specifically named above have not made it into any of the 2.6.36 rcs yet; as such, it would be useful to test the drm-intel-next kernel.

[John Lenton (chipaca)]

I tested the drm-intel-next kernel and got no X at all; had to add nomodeset at boot and use the vesa driver to get X.
With 2.6.36-020636rc3 I get X after switching to console and back, but no console and the colours on X were "wrong" (32 bits, but 4/4/4 apparently).
Downloading 2.6.36-020636rc5 to try my luck with that :)

[John Lenton (chipaca)]

ok, now running 2.6.36-020636rc5-generic, and it's the same as rc3; I have to switch to console and back to get X, console is blank, I have banding on known smooth images, and xrandr output is shot.
xrandr output:

(null)1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm
   1920x1080 60.0*+ 40.0

(plus the normal list of disconnected devices).

An interesting point is that if I connect a monitor to VGA1, I still get no console but I don't need to switch there and back for X to start.

[Jerone Young (jerone)]

I looked at this bug wrong (sorry).

The issue looks to only be on machines with the LG 1920x1080 panel.

We have seen issues on other machines as well with Intel graphics and LG panels.

[John Lenton (chipaca)]

is there a fix/workaround?

[Corona (stefaniefauconnier)]

I tested the kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/current/ on my E6510, core i5, intel gpu. I could hear the gdm drums, but the screen remained black (with the backlight on). Switching to console and back did not solve the issue.

[Manuel Carro (mcarro)]

@#39: I did the same as Corona (#44) and had the same behavior. I downloaded and compiled the sources from git://git.kernel.org/pub/scm/linux/kernel/git/ickle/drm-intel.git . The drm-intel-next branch had the same behavior as the precompile kernel #44 refers to. However, the drm-intel-fixes branch does show the display after switching to the console and back (I am using it now), same as the kernel v2.6.36.rc5-maverick from the ~kernel-ppa pages. It (the drm-intel-fixes) works with an external monitor and seems able to suspend (with the acpi_sleep=s3_bios kernel command line option).

Is there any other test I could do to help testing?

[Manuel Carro (mcarro)]

Re. #45: just tried kernel 2.6.36-997-generic_2.6.36-997.201009231312_i386 from kernel-ppa and it does not show the display on boot; switching to and from console does not help, but the system boots (the drums sound and I can shut it down cleanly).

[Manuel Carro (mcarro)]

The latest drm-intel-fixes (as of yesterday - latest commit is cf9a2f3afc75d41a61cbc91e725b9ce0746c400a from Chris Wilson dated Thu Sep 23 16:17:33 2010 +0100) together with the patch in https://bugs.freedesktop.org/show_bug.cgi?id=29278#c63 seems to solve the Intel Integrated Graphics saga problem: machine boots in X, it suspends, it hibernates (tried just twice but it worked) and resumes. Only thing I noticed is that after some time up (some 12 hours) and some suspensions / hibernations, X Window became slow. Usable but slow: glxears goes basically one order of magnitude slower (450 fps vs. 3800 fps). My 0.02€.

[Manuel Carro (mcarro)]

Re. comment #47: fps were not fps, but fps * 5 (what glxgears writes to the output). I found the cause of the sluggishness was an instance of openoffice. Closing it made the behavior of the graphical display to go back to normal.

[Francisco Cribari (cribari)]

@Manuel

That's great news. Is there a pre-compiled kernel with all the fixes? I've just tried kernel 2.6.36-997.201009231312 (64 bit) but it booted to a blank screen. Thanks again. PS. Would you know if the fixes will make it into the 10.10 final release?

[Manuel Carro (mcarro)]

> That's great news. Is there a pre-compiled kernel with all the fixes?
> I've just tried kernel 2.6.36-997.201009231312 (64 bit) but it booted to
> a blank screen. Thanks again. PS. Would you know if the fixes will make
> it into the 10.10 final release?

Not as far as I know. I have produced .deb but they are 32 bit.
However, except for the need to switch to console (Ctrl+Alt+F1) and back
to graphical display (Ctrl+Alt+F7), the Maverick rc4 and rc5 seem to
work nicely. You can get 32 and 64 bit variants from
http://kernel.ubuntu.com/~kernel-ppa/mainline/ (scroll to the bottom).

[Corona (stefaniefauconnier)]

I tested henk's patch mentioned in this thread (comment 63) https://bugs.freedesktop.org/show_bug.cgi?id=29278#c63 , applied on top of linux-2.6.36-rc5.
It only works for me if I increase the delays to 900ms (500 and 300 don't work, I haven't tried any values between 900 and 500), but it really seems to fix the black screen. I can see the bootloader and the login screen now, and I can resume from suspend. The cardreader is supported by default. I haven't tested VGA output yet but I guess that works, too.

I tried to upload my deb packages to a PPA but I couldn't figure out how to do it, so I'm going to try to add them as an attachment.

[Corona (stefaniefauconnier)]

kernel headers

[Corona (stefaniefauconnier)]

Here's the actual patch for 2.6.36-rc5.

I know uploading the kernel debs is not the proper way to do this, if anyone could upload the packages to their PPA that would be much better, but I don't know how to do it.

[Corona (stefaniefauconnier)]

Sorry for the multiple comments, but I forgot to mention that the .deb packages I uploaded do not install an initrd by default. You should run sudo update-initramfs -c -k 2.6.36-rc5 after installing them, and then edit /boot/grub/grub.cfg accordingly (look for the menuentry 'Ubuntu, with Linux 2.6.36-rc5' and add the line initrd /boot/initrd.img-2.6.36-rc5 before the } ). Hope this helps.

[Francisco Cribari (cribari)]

@Corona

That's great! Have you contacted Henk about the need to increase the delays to 900ms? What did he have to say about that?

[henk (henk1234)]

900ms is a long time, so I doubt if the kernel developers will accept such a delay. On my system, a 300ms delay is enough. Are there other systems which need the 900ms delay?
I've submitted the patch with the 300ms delay upstream. But if we really need the 900ms delay, we could ask the developers nicely to increase the delay :-)

[Corona (stefaniefauconnier)]

For me, 300 ms and 500 ms didn't work, so I increased the delays to a very long time like 900 ms to see if it would help at all. It works now and I'm happy with it, but maybe 600ms would have been enough.
I'm also interested in finding out if other people have the same results with this patch.

[Francisco Cribari (cribari)]

@Henk + @Corona

I'd be glad to give it a try, but I wouldn't be a able to compile a kernel (my knowledge of Linux does not go that far). If there is a compiled 64 bit kernel (.deb), I can install it and try it. My hardware is DELL 6510, Intel GPU, core i7, full HD display, bios A03.

PS. Will this fix make into the 10.10 release?

[henk (henk1234)]

Here's a precompiled 64 bit version of 2.6.36-rc5 with the patch with the 300ms delay. Not all drivers are compiled in, so maybe some drivers are missing, but you can use it to test the display.

[henk (henk1234)]

Same 64 bit kernel, but now with the 900ms patch.

[Francisco Cribari (cribari)]

@Henk

I installed the first one (300ms), but I got a kernel panic message at boot:

[ 0.747467] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

I forgot to mention that my machine has a solid hard drive (SDD). Could that be the problem?

Please, let me know how to proceed. Thank you.

[Francisco Cribari (cribari)]

Here is the output of mount on my machine

cribari@darwin:~/Downloads$ mount
/dev/sda1 on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
none on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
none on /dev type devtmpfs (rw,mode=0755)
none on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
none on /dev/shm type tmpfs (rw,nosuid,nodev)
none on /var/run type tmpfs (rw,nosuid,mode=0755)
none on /var/lock type tmpfs (rw,noexec,nosuid,nodev)
none on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
gvfs-fuse-daemon on /home/cribari/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=cribari)

[Francisco Cribari (cribari)]

Also: kernels 2.6.36-997.201009271317 (from drm-intel-next) and 2.6.32-25.44 boot to a blank screen.

[Christian-hd (christian-hd)]

User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.10) Gecko/20100914 SUSE/3.6.10-0.3.1 Firefox/3.6.10

After upgrading from kernel 2.6.34-12.3 (that comes on the installation disk) to a newer kernel (2.6.34.7-0.3.1) via online update I only get a blank screen after booting (system boots "normally" though). Only when using nomodeset as kernel parameter screen is working properly. Went back and forth between kernels and result is reproducable each time.
Harware is DELL E6510 with Intel Ironlake graphics adapter.

Reproducible: Always

Steps to Reproduce:
1.Upgrade to new kernel via online update
2. reboot -> blank display
3. Use nomodeset as kernel parameter -> display comes back

[Francisco Cribari (cribari)]

Kernel 2.6.35-02063507.201009290909 boots to a blank screen.

Kernel 2.6.36-020636rc6.201009291126 boots to a blank screen, but I can get to X with CTRL+ALT+F1 followed by CTRL+ALT+F7 (just like with rc5).

Hardware: DELL 6510, Intel GPU, full HD display, core i7, bios A03.

[Manuel Carro (mcarro)]

@Corona (#57), @ henk

I have been successfully running drm-intel-next with Henk's patch and Henk's delay. It's been rock solid for the last few days. I suppose that the timing differences come from different hardware and the speed of the components, but I do not know which pieces would affect that. Henk (and others), which information do you think could be interesting to determine which delay to apply for each configuration? Would the output of lshw / lspci help?

Cheers!

[Francisco Cribari (cribari)]

Kernel 2.6.35-02063507.201009290909 boots to a blank screen.

Kernel 2.6.36-020636rc6.201009291126 boots to a blank screen, but I can get to X with CTRL+ALT+F1 followed by CTRL+ALT+F7 (just like with rc5).

Hardware: DELL 6510, Intel GPU, full HD display, core i7, bios A03.

[Sndirsch (sndirsch)]

This is related to Bug #608300. eDP support has been fixed in the kernel updates 2.6.34.4/2.6.34.7 - at least for other laptops like

- HP Elitebook 2540p (Swatch)
- HP Elitebook <something> (Omega)

I found a related upstream bug:

  https://bugs.freedesktop.org/show_bug.cgi?id=29278

[Francisco Cribari (cribari)]

Ubuntu 10.10 beta 2 boots (from CD) to a blank screen.

[Francisco Cribari (cribari)]

1) Will Henk's patch be in Ubuntu 10.10 (to be released on October 10)?

2) Will Henk's patch be in kernel 2.6.36?

3) Is there a drm-intel-next compiled kernel that includes Henk's patch?

[John Lenton (chipaca)]

On Sat, Oct 02, 2010 at 10:58:59AM -0000, Francisco Cribari wrote:
> 3) Is there a drm-intel-next compiled kernel that includes Henk's patch?

drm-intel-next head already includes something similar to that
patch. Alas it does not work for me, so something else broke it
(2.6.36-rc5 with that patch works for me, drm-intel-next head does
not).

[Francisco Cribari (cribari)]

@John Lenton

Kernel 2.6.36-997.201010021122 from drm-intel-next (October 2nd, 2010) does not work for me: blank screen at boot.

[Francisco Cribari (cribari)]

Kernel 2.6.36-997.201010050908 also boots to a blank screen on my DELL 6510 Intel GPU.

Will there be a standard (64bit) compiled kernel that includes Henk's patch?

[Francisco Cribari (cribari)]

Ubuntu 10.10 RC boots (from CD) to a blank screen.

Would anyone be able to tell us what DELL E6510 owners should expect? Will there be a patched kernel? When? Is there any chance that version 10.10 (to be released in a few days) will work on 6510 (Intel GPU) hardware?

[Corona (stefaniefauconnier)]

Francisco, I don't think anything will happen until significant progress is made upstream. Henk's patch works very well for me, but it is not considered as a proper solution so I don't think we will see it in Maverick. You can follow the upstream bug report here: https://bugs.freedesktop.org/show_bug.cgi?id=29278 .

The most recent working kernel is this one I think: http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.35-rc5-maverick/ VGA output works and there is no blank screen on boot, but you need a workaround to get suspend working. I don't remember the actual bug report with this workaround, but I think it's not very difficult to find.

Still, I think it's a shame that there is so little attention for this bug, especially when compared with the e6410. What puzzles me most of all is that the E6510 is apparently Ubuntu certified: http://webapps.ubuntu.com/certification/hardware/201009-6534/ . Canonical says that only the Lucid OEM version has been tested, I wonder where we can find it...

[Corona (stefaniefauconnier)]

I just saw that this bug was not even nominated for Maverick, this should have happened a long time ago. I just nominated it, but the feature freeze was a while ago so I don't think this will make any difference anymore. So Francisco, remember to nominate your bugs for upcoming releases.

[Francisco Cribari (cribari)]

@Corona

Thanks. This was the first and only bug I ever reported. I am not an advanced user. I knew nothing about nominating a bug (I still don't know what that means, to be quite honest), that's why I did not do it. Thanks for nominating this bug. If you find out more about this bug and possible fixes and patches, please share the information with us.

[Francisco Cribari (cribari)]

Kernel 2.6.36-020636rc7.201010070908 (released today) also boots to a blank screen. I get to X by pressing CTRL+ALT+F1 and then CTRL+ALT+F7.

[Ari Asril (jasbutut)]

Hi! I got this bug too on my Acer Aspire 4147Z with Intel P6000 and Intel HD Graphics. I installed maverick daily build and at reboot it went to blank screen. Read on all of the posts here then I installed linux-image-2.6.35-020635rc5 kernel, now my notebook can boot to X.
I really appreciate this workaround, it is awesome. This show me the power of community. Please post if you want me to do some test on my notebook, i am a newbie but i will be really happy to contribute.

[Francisco Cribari (cribari)]

@Ari

At boot (and sometimes after suspend/resume), do you need to press CTRL+ALT+F1 and then CTRL+ALT+F7 to get to X?

[Ari Asril (jasbutut)]

@Fransisco

So far I haven't got that problem, since I only use it for few hours. I'll post here if something is happened later.

[devsk (funtoos)]

The sleep patch on top of rc7 solved it for me (I finally see my boot, VTs are available, external monitor works, suspend/resume works(tried few cycles)). I had spent so many hour fighting the external monitor issue prior to hitting this bug, its not even funny. Thanks henk!

[Francisco Cribari (cribari)]

Ubuntu Linux 10.10 (released today, Oct 10) also boots to a blank screen.

[Bonk (ajh-foi)]

Ubuntu Linux 10.10 boots into blank screen on Dell Latitude E4310 as well (for 2.6.35 kernel). The problem exists in the latest version of 2.6.33 as well. Downgrading to 2.6.32 fixes the problem partly. I can however not connect external VGA displays (both internal and external screen goes black).

[vdoshi (vdoshi79)]

I'm having the same problem with Dell Latitude E4310 and Ubuntu 10.10. I've tried installing all the current updates, but the laptop screen still does not work. I'm currently using the machine with an external monitor (VGA). I tried running Ubuntu 10.04, and that worked, but when I install the updates for that, the laptop screen went dead again. I'm back on 10.10 now with the external monitor.

[giovanni bono (strumentale)]

Same with a Latitude E6510 (i3, intel gpu, fhd display) that shipped with Ubuntu (9.10) from Dell. The same happens with other distributions of course. But patching a vanilla 2.6.36-rc6 kernel with:

https://bugs.freedesktop.org/attachment.cgi?id=38868

solves --at least temporarily-- the problem.

[Francisco Cribari (cribari)]

Kernel 2.6.36-rc8 (released today) boots to a blank screen. I can only get to X by pressing CTRL+ALT+F1 and then CTRL+ALT+F7.

[David Kanenwisher (d-kanen)]

I have the same setup as giovanni bono(Latitude E6510, i3, intel gpu, fhd display) and was able to get ubuntu 10.10 working by upgrading my kernal to 2.6.36-rc6 with the patch as he suggested.

@giovanni bono Thanks!

[Francisco Cribari (cribari)]

Kernel 2.6.36-997.201010190908 (from drm-intel-next, released today) also boots to a blank screen.

[KiberGus (kibergus)]

I have vostro 3300. Internal screen works fine, but VGA exit does not. 2.6.36-997.201010190908 solved the problem partially: VGA exit works (but image ripples hard) but I can see only mouse cursor on black screen. KDE floods stderr with
Failed to submit batch buffer, expect rendering corruption or even a frozen display: Resource temporarily unavailable.

[Francisco Cribari (cribari)]

A pragmatic question: Is there hope?

[Corona (stefaniefauconnier)]

You should ask that in the upstream bug report, this issue is not going to be resolved by Ubuntu or Canonical devs. As far as I can see people are still trying to write and test patches.

[Dejan (dejan-rodiger)]

I have the same problem with EliteBook 8440p with Intel graphic card. Laptop's Seiko monitor (DP1 according to xrandr) sometimes works and sometimes only VGA1 monitor works even both are defined. Does someone have config files where is this defined during boot and where after login. Is it only /etc/gdm/Init/Default and ~/.config/monitor.xml ?

[Christian Demoustier (cdemoustier)]

My DELL Latitude E6510 was working fine with Ubuntu 10.04, until there was a minor kernel upgrade from which the display went black at boot.

I can't find precisely the exact kernel package version which introduced the bug but I can remember there was a change in kernel mode setting for intel chipset.

Currently my laptop is working with kernel : 2.6.32-23, and is not working anymore (black screen on boot) with later kernel packages (including Ubuntu 10.10).

[Dries Van Dyck (vandyck-dries)]

I had the same experience as Christian with my E6510 with integrated intel gpu: I first installed Ubuntu 10.04 which worked fine, applied the updates and rebooted to a blank screen (with backlight if I remember correctly). Strangely enough, booting with the original kernel which worked fine before yielded also a blank screen.

I tried ubuntu 10.10 afterwards: the install CD gave a blank screen but using the nomodeset boot option I could install graphically but first boot resulted again in a blank screen. I tried several boot options (including nomodeset) without success.

I do not understand why the working graphics configuration *during* install is not used and can not be replicated *after* install.

A full description of my experience can be found here:
http://ubuntuforums.org/showthread.php?p=9989861#post9989861

[FredWst (fredgeoffroy)]

Hello,

I've also a E6510 core i7 Intel HD.
Black screen on boot with maverick.

To get screen working i do this:

Attach vga display wait a few second remove it.

And screen is ok !

Regards

[Francisco Cribari (cribari)]

Kernel linux-image-2.6.37-020637rc1-generic also boots to a blank screen. Using this kernel, I *cannot* get to X by pressing CTRL+ALT+F1 followed by CTRL+ALT+F7 (unlike the 2.6.36 kernels).

Hardware: DELL Latitude E6510, Intel integrated graphics, core i7, full HD display.

[Francisco Cribari (cribari)]

There seems to be some sort of regression. See https://bugs.freedesktop.org/show_bug.cgi?id=29278 .

[baben (herr-lefrog)]

I've tried Kernel 2.6.36-997
It's still not working for me.

I'm using Kernel 2.6.36-020636rc7 which works sometimes but most times it still boots to a blank screen.
If I plug in an external monitor I'm able to get the picture on the integrated display.

[baben (herr-lefrog)]

Dell Latitude E6410ATG
Ubuntu 10.10 Kernel 2.6.36-020636rc7

messages while booting:

[1.400196] mmc0: Unknown controller version (2). You may experience problems.
[7.763346] intel ips 0000:00:1f.6: failed to get i915 symbols, graphics turbo disabled

[Francisco Cribari (cribari)]

Kernels 2.6.37-020637rc2.201011160905 (2.6.37 RC2) and 2.6.37-997.201011150905 (from drm-intel-next) boot to a blank screen. In both cases, I *cannot* get to X using CTRL+ALT+F1 followed by CTRL+ALT+F7.

Hardware: DELL Latitude E6510, Intel GPU, core i7, full HD display (1920 x 1080).

[Dejan (dejan-rodiger)]

Hi All,

I think getting picture on the laptop's display is fundamental. If I need to do a presentation, which is done with laptops, I would need the possibility to use external display or projector.

With Maverick and laptops with Intel graphic card this is almost impossible to do.

1. Start laptop where laptop will display anything (except backlight), is in every 4-5 boot ups
2. If I get display in the end, if I switch it off, I will not get it back (except back light).
3. Using Fn-F4 (switch display keys), is working in one way. Buy switching off laptops display ;-)
4. Connecting external display, sometimes doesn't work, because it will not switch it on, or it will switch laptops display off.

What is possibly wrong is that internal display is DP1 and not VGA1, meaning that external display is VGA1.

This should be first priority bug. Or please tell us if there is some workaround.

Thanks
Dejan

[Francisco Cribari (cribari)]

Would anyone be able to let us know what to expect as far as this bug fix is concerned? I know that some people are working on it, but are the progresses made so far substantial? Is there much left to be done? What are the odds that there will a fully functional mainline kernel (as far as this bug is concerned) in the next couple of months? Thanks in advance.

[Corona (stefaniefauconnier)]

As I mentioned before, all progress for this bug depends entirely on work done upstream, so as long there is no definitive fix there nothing can happen for Ubuntu. You can ask your question here https://bugs.freedesktop.org/show_bug.cgi?id=29278 .

Dejan, you can find a couple of patches in that bug report if you are familiar with kernel compilation. If not, you can follow these guidelines https://wiki.ubuntu.com/KernelTeam/GitKernelBuild , they worked for me.

[Andy Whitcroft (apw)]

Reviewing the upstream bug there seem to be a number of patches floating around that are needed in combination to make this work. I believe that all of the ones mentioned were in v2.6.37-rc2 which would mean that they are in the latest Natty kernel. If those of you who are affected could test that kernel. Probabally the easiest way would be to boot the current LIVE CD images which can be found at the URL below:

    http://cdimage.ubuntu.com/daily-live/current/

Please report any testing back here. Thanks!

[Richard Duivenvoorde (rduivenvoorde)]

Andy, tried it. Still a black screen on a E6510 with intel HD (for full hardwarelist see https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/648335)

I used the vanilla iso (http://cdimage.ubuntu.com/daily-live/current/natty-desktop-i386.iso) there.
But there is something with enlarging a timeout also isn't it in the http://bugs.freedesktop.org/show_bug.cgi?id=29278 bug report also.

It's really a pitty. I thought to buy an Intel-integrated graphics card because of the good hardware compatibility of Intel and Ubuntu :-(

[Jason Meridth (jmeridth)]

Same issues: black scree on E6510 with intel HD. Can't believe this hasn't been fixed.

[henk (henk1234)]

The patch from https://bugs.freedesktop.org/attachment.cgi?id=38868 has been accepted upstream (see: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=27d64339a8d8465484286a2da93f5f6c36be5c3d) So why not apply it to the Maverick kernel?

[Francisco Cribari (cribari)]

linux-image-2.6.37-020637rc3-generic boots to a blank screen. Switching to a VT and back does *not* get me to X.

[Francisco Cribari (cribari)]

Kernel 2.6.37-6.17~lucid1 (from PPA) boots to a blank screen. Switching to a VT and back does not help.

[John-B-G (giovanni-rutgers)]

The Display work fine (after some work) with 9.10 on 2.6.31-22-server

With 10.10 (and 10.4 as well as with a recent fedora and a debian) it is blank: however attaching a vesa screen and detaching it (possible more than once) the screen comes up and everything is ok (as remarked above by another user). I can also get to a command screen (no X) with the option nomodset at boot (as suggested above), but X cannot be started.

I recompiled the kernel using 2.6.31-generic; but it did not even boot

The problem is (as already pointed out) that the intel module is not correct (why is it in 9.10?)

[Andy Whitcroft (apw)]

@henk -- because the fix listed there is in the kernels tested by Francisco which did _not_ fix the issue for him so they are not likely to fix the issue.

[Andy Whitcroft (apw)]

I also note that the upstream bug does not come to any firm conclusions other than the patches which are already commited and in the current Natty kernels.

[Francisco Cribari (cribari)]

Kernel 2.6.37-7.18~lucid2 (from PPA) boots to a blank screen. Switching to a VT and back does NOT help.

(PS. I am quite discouraged by this bug. This is by far the worst experience I've had w/ Linux.)

[Corona (stefaniefauconnier)]

@andy: the patches mentioned by henk do work, but for some laptops it is necessary to increase the delays. francisco did not test that as far as I can see.

[Francisco Cribari (cribari)]

@Corona I've been testing most mainline kernels. None works on my machine (DELL 6510, core i7, Intel GPU, full HD display, SDD). With 2.6.36 kernels I can at least get to X by switching to a VT and back, but that does not seem work on 2.6.37 kernels. Unfortunately, I am not able to compile kernels + patches. My knowledge of Linux does not go that far. I am really hoping for a compiled kernel (64 bits) that works on my machine.

[Manuel Carro (mcarro)]

Dear all,

I have a couple of ubuntu 2.6.36 kernels which I have been testing for some weeks now and which work ok on an e6510 (including external displays and suspend/resume). I have compiled them for i386, but I should be able to compile 64 bit versions as well. I would like to make them available widely. I was thinking of a ppa in launchpad, but I do not know what is the procedure to get and account there, or if this is really the best place to leave them. Any hints / recommendations?

Cheers!

[Francisco Cribari (cribari)]

1) Kernel 2.6.37-999.201012030905 (64 bit) boots to a blank screen. Switching to a VT and back does not help.

2) Ubuntu 11.04 alpha 1 (64 bit) boots (from CD) to a blank screen.

[Chewie (hannes-woelfler)]

Hi
I tested with Kubuntu 10.10 and different kernel out of mainline and inter-drm-next on Dell Latitude E6510 Core I5 intel gpu. I even had to use an external Monitor in order to bring the installer up and running.

After unsuccesfully testing arround in 10.10 i installed 11.04 today with better results.
Installer (still 10.10 installer) worked only with external monitor.
After Installation I changed /etc/defaults/grub to xforcevesa nomodeset noagp and after update-grub it worked for me.
Kernel is 2.6.37-7generic no problems up to now !

[Dejan (dejan-rodiger)]

Chewie,

does this mean that xforcevesa, nomodeset, noagp are setting X.org to use vesa? Does compiz works?
Does Ubuntu recognize when you connect external monitor or projector? In 10.10, when I connected external monitor, I had to run xrandr and then I would get display on external monitor, but no display on my internal LCD (blank screen).

Thanks

[Chewie (hannes-woelfler)]

Hi Dejan
The kernel parameters below initiate the internal lcd and enalbe x in a way
that you can use the laptop.
I started over in vesa mode with desktop effects enabled -> got window
decoration working and stuff but only in low quality and very slow.
External monitors are also not working at the moment.
cheers
Chewie

2010/12/6 Dejan <email address hidden>

> Chewie,
>
> does this mean that xforcevesa, nomodeset, noagp are setting X.org to use
> vesa? Does compiz works?
> Does Ubuntu recognize when you connect external monitor or projector? In
> 10.10, when I connected external monitor, I had to run xrandr and then I
> would get display on external monitor, but no display on my internal LCD
> (blank screen).
>
> Thanks
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/600453
>
> Title:
> [arrandale] [i915] DELL E6510: blank screen on boot (Intel GPU)
>
> Status in “linux” package in Ubuntu:
> Confirmed
> Status in “linux” source package in Natty:
> Confirmed
> Status in “linux” package in Fedora:
> Unknown
> Status in “linux” package in openSUSE:
> Confirmed
>
> Bug description:
> I am running Ubuntu Linux 10.04 64 bits on a DELL 6510 notebook with
> integrated Intel graphics card. The machine only boots in a low-graphics
> mode. I detected the following error message in the logs:
>
> (EE) intel(0): No kernel modesetting driver detected
>
> I used i915,modeset=0 as a kernel option but I am no longer using. The
> xorg.config file I am using is
>
> Section "Device"
> Identifier "Configured Video Device"
> BusID "PCI:0:2:0"
> Driver "intel"
> Option "AccelMethod" "UXA"
> EndSection
>
> Section "Module"
> Load "glx"
> Load "dri"
> Load "extmod"
> Load "record"
> Load "dbe"
> Load "GLcore"
> Load "xtrap"
> Load "freetype"
> EndSection
>
> Section "Monitor"
> Identifier "Configured Monitor"
> EndSection
>
> Section "Screen"
> Identifier "Default Screen"
> Monitor "Configured Monitor"
> Device "Configured Video Device"
> DefaultDepth 24
> EndSection
>
> Section "DRI"
> Mode 0666
> EndSection
>
> My kernel is
>
> Linux darwin 2.6.32-23-generic #37-Ubuntu SMP Fri Jun 11 08:03:28 UTC 2010
> x86_64 GNU/Linux
>
> The intel driver:
>
> ii xserver-xorg-video-intel
> 2:2.12.0+git20100628.17884af4-0ubuntu0sarvatt~lucid
> X.Org X server -- Intel i8xx, i9xx display d
> ii xserver-xorg-video-intel-dbg
> 2:2.12.0+git20100628.17884af4-0ubuntu0sarvatt~lucid
> X.Org X server -- Intel i8xx, i9xx display d
>
> Any suggestions? Thanks.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 10.04
> Package: linux-image-2.6.32-23-generic 2.6.32-23.37
> Regression: No
> Reproducible: Yes
> ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
> Uname: Linux 2.6.32-23-generic x86_64
> AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
> Architecture: amd64
> ArecordDevices:
> **** List of CAPTURE Hardware Devices ****
> card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
> Subdevices: 2/2
> Subdevice #0: subdevice #0
> Subdevice #1: subdevice #1
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: cr...

[Dejan (dejan-rodiger)]

Hi,

Just a tip.
To enable VGA1 on boot (which is a problem for projectors that are not detected) you can put:
"video=VGA1:e" in /etc/default/grub
or video=VGA1:1024x768@60

for example:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash display=VGA1:e"

After you safe this file you need to run "sudo update-grub"

Info from here: https://wiki.ubuntu.com/X/KernelModeSetting/

display=VGA1:d - disables VGA1 on boot

[Francisco Cribari (cribari)]

Kernel 2.6.37 RC5 boots to a blank screen. Switching to a VT and back does not help.

[henk (henk1234)]

@Francisco. Can you please try this patch for 2.6.37-rc5?

--- drivers/gpu/drm/i915/intel_display.c
+++ drivers/gpu/drm/i915/intel_display.c
@@ -2081,8 +2081,8 @@
 /* For PCH output, training FDI link */
 if (IS_GEN6(dev))
  gen6_fdi_link_train(crtc);
- else
- ironlake_fdi_link_train(crtc);
+// else
+// ironlake_fdi_link_train(crtc);

 /* enable PCH DPLL */
 reg = PCH_DPLL(pipe);

[Francisco Cribari (cribari)]

@henk I do not know how to apply patches to kernels and then compile them. I am not much more than a newbie. Is there a patched compiled 64 bit kernel? If so, I can give it a try. Please, let me know.

[henk (henk1234)]

patched 2.6.37-rc5 kernel deb for x86_64

[Francisco Cribari (cribari)]

@henk I installed the .deb packaged and rebooted the notebook. I got the following error message:

[ 2.845548] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 2.845610] Pid 1. comm: swapper Not tainted 2.6.37-rc5 #2

and then some trace messages.

My notebook has a solid 256 MB hard drive. Could that be source of the problem?

[Francisco Cribari (cribari)]

@henk I mean, 256 GB.

[henk (henk1234)]

That could be the source of the problem. I only compiled in the modules I need for my system. Unfortunately, I don't know what kernel option I need to support your SSD.

[Andy Whitcroft (apw)]

There is a fix in the very latest Natty kernel which may help with this, fixing an initialisation issue for a number of Intel chipsets. Could those affected please test and report back here.

[Francisco Cribari (cribari)]

@Andy Which kernel exactly? Thanks for the info.

[Francisco Cribari (cribari)]

Kernel 2.6.37-997.201012101342 (from drm-intel-next) boots to a blank screen. Switching to a VT and back does not help.

Kernel 2.6.36-02063602.201012101121 boots to a blank screen. I can get to X by switching to a VT and back.

[John Lenton (chipaca)]

what I've got in natty is linux-image-2.6.37-8-generic, version 2.6.37-8.21, and no luck. Still the same: HD panel doesn't work, but external monitor does; suspend/resume doesn't help. Still using the patched 2.6.36-rc5 that was provided above.

[Francisco Cribari (cribari)]

Kernel 2.6.37-9.22~lucid1 boots to a blank screen. Switching to a VT and back does not help.

[Steve Conklin (sconklin)]

2.6.37-9.22~lucid1 is the latest maverick kernel, in lucid backports. The patches that Chris mentions in comment #27 have been applied to that kernel, and the problem persists. It doesn't make much sense to worry about backporting patches to Lucid and Maverick until we find something that works on Natty, so we're still in need of a fix.

There could also be more than one issue at play here, making it more difficult to find a fix.

[Francisco Cribari (cribari)]

linux-image-2.6.37-020637rc6-generic boots to a blank screen. Switching to VT and back does not help.

[Andy Whitcroft (apw)]

@Francisco -- when booting if you edit the grub command line and change the 'set gfxpayload=$linux_gfx_mode' to 'set gfxpayload=text' and then boot, do you get any further?

[Francisco Cribari (cribari)]

@Andy No, unfortunately not. I booted with

quiet splash acpi_sleep=s3_bios set gfxpayload=text

(kernel 2.6.37 RC6) but no X (switching to a VT and back dit not help).

[Francisco Cribari (cribari)]

linux-image-2.6.37-020637rc7-generic (released today) boots to a blank screen. Switching to a VT and back does not help.

Is there hope?

[Loïc Giraldi (loic-giraldi)]

I have a brand new HP G62 A55SF with an I3 330M and no nvidia or ati graphic card.

After a fresh xubuntu install with an alternate CD (i could not with the live one) i got a blank screen just after an error message, something like "failed to get i915 symbol".

I could solve the problem with the "acpi=off" option for grub. I've found the solution in a fedora forum
http://forums.fedora-fr.org/viewtopic.php?id=50063

[Urschl (bigurschl)]

same Problem on 2.6.37-020637rc8

[Remko Bolt (remko-cluebox)]

I installed "Linux Mint Debian 201009-Gnome" which uses kernel "linux-image-2.6.32-5-686" version 2.6.32-15. This kernel works fine. When I upgrade to 2.6.32-29 things break...

Hope this information helps, greetings,

Remko

[Francisco Cribari (cribari)]

It seems that substantial progress has been made today (January 5, 2011); see https://bugs.freedesktop.org/show_bug.cgi?id=29278 .

[Corona (stefaniefauconnier)]

Yup, all the testers have reported that the issue is fixed in edp-fixes-2. Fixes will land in 2.6.37.x so stay tuned.
Apparently the black screen on boot and the suspend issues are totally fixed. External monitors also work, but with a couple of glitches, but new bugs have to be opened for those.

I havent' tried the new fixes myself yet, I'm at a conference right now with my netbook. As soon as I get home next week I'll check them on my E6510 and report back here.

[Francisco Cribari (cribari)]

I've just tried kernel 2.6.37-997.201101081429 (from drm-intel-next) and it boots to a blank screen. Switching to a VT and back does not help. In the build.log file we read:

commit fbf4b94f7d01550799ff7669c65ebb0c053e015c
Author: Jesse Barnes <email address hidden>
Date: Fri Jan 7 10:24:43 2011 -0800

    drm/i915: make FDI interrupt info debug only

    It's normal to receive one or two of these during mode setting activity,
    so just make the output debug only. We can change this in the future if
    we ever make our training sequences interrupt driven and properly handle
    the various types of interrupts.

[Richard Duivenvoorde (rduivenvoorde)]

I tried git://git.kernel.org/pub/scm/linux/kernel/git/ickle/drm-intel.git yesterday without success

clean compile on 10.10, no further (timeout) patches applied.

E6510 Intel HD, bios A06 now, rest of hardware see: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/648335

please let me know if there is something I should try out

[Corona (stefaniefauconnier)]

ehm it might take a bit longer than 1 day before fixes get merged into the main branches of drm-intel or drm-intel-next.
if you want to try out the fixes you have to checkout the edp-fixes2 branch from jesse's tree, or ickle's drm-intel-next staging branch (I believe), just follow the instructions here https://bugs.freedesktop.org/show_bug.cgi?id=29278 (last 30 posts or so).

[Oliver Herold (oliver-akephalos)]

The problem is far from fixed with the release of 2.6.37 : https://bugzilla.kernel.org/show_bug.cgi?id=22872

[henk (henk1234)]

The issue is fixed in ickles drm-intel-staging branch:
git clone -b drm-intel-staging git://git.kernel.org/pub/scm/linux/kernel/git/ickle/drm-intel.git

[cassianoleal (cassianoleal)]

I tried the drm-intel-staging kernel.
It did fix the blank screen problem, but when X starts, the computer freezes. It's so quick that even Xorg.log is empty (zero sized).

[Steven (svanpoeck)]

Hi,

I installed the Natty kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.37-natty/ but my DELL E6510 laptop's display is erroneously detected as a Epson Seiko Corporation 15"@1600x900, so I had to revert back to the official maverick kernel.

Adding acpi=off to the kernel options was to no avail...

uname -a
Linux rd-25 2.6.35-24-generic #42-Ubuntu SMP Thu Dec 2 02:41:37 UTC 2010 x86_64 GNU/Linux

lspci
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02)
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02)
00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit Network Connection (rev 05)
00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05)
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 05)
00:1c.2 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 3 (rev 05)
00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 4 (rev 05)
00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5)
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 05)
00:1f.2 RAID bus controller: Intel Corporation Mobile 82801 SATA RAID Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05)
00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 05)
02:00.0 Network controller: Intel Corporation Centrino Advanced-N 6200 (rev 35)
03:00.0 CardBus bridge: Ricoh Co Ltd Device e476 (rev 02)
03:00.1 SD Host controller: Ricoh Co Ltd Device e822 (rev 03)
03:00.4 FireWire (IEEE 1394): Ricoh Co Ltd Device e832 (rev 03)

BR,
Steven

[Francisco Cribari (cribari)]

I run Ubuntu Linux 10.04 64 bit. Today I installed linux-image-2.6.38-020638rc1-generic . It boots, however, to a blank screen. Switching to a VT and back does not help.

[Francisco Cribari (cribari)]

Bad news: See #279 in https://bugs.freedesktop.org/show_bug.cgi?id=29278 .

[Tom Ellis (tellis)]

Actually, looks like this is fixed upstream now.

The issues with suspend are a separate problem.

Can anyone test this using the kernels described in the upstream bug?

[Francisco Cribari (cribari)]

Today I installed kernel 2.6.38-997.201101241227 from drm-intel-next. It boots to X. However: 1) suspend and resume does not work, 2) when I try to reboot or shut down by clicking on the appropriate menu option it merely logs me out.

[Corona (stefaniefauconnier)]

The basic problem reported here has indeed been fixed, drm-intel-next now succesfully boots to X. Resuming from suspend is broken for me, too, I haven't tried the shutdown menu options yet though.

I filed these bug reports, reporting the resuming from suspend problems and the flicker I experience during boot.
https://bugs.freedesktop.org/show_bug.cgi?id=33439
https://bugs.freedesktop.org/show_bug.cgi?id=33442

The flicker seems to be mostly solved by 2 patches which (accidentally) did not find their way to drm-intel-next. Resuming from suspend seems to be a different issue which is not solved yet.

[Francisco Cribari (cribari)]

In System -> Preferences -> Power Management the only option that shows up in the field "When laptop lid is closed" is "Blank screen". That is, "Suspend" and "Hibernate" do not even show up. I tried both with and without the files 99video and 98video-quirk-db-handler in /usr/lib/pm-utils/sleep.d/ .

[Michael Lustfield (michaellustfield)]

I just wanted to mention that with v2.6.38-rc2 my issue with a blank screen seems to have gone away. I still don't have control over brightness controls but the blank screen issue reported in this bug report has been corrected for me.

[Dejan (dejan-rodiger)]

Hi,

I confirm Michael's note. On 2.6.38 rc2 from ubuntu kernel ppa, I boot to gdm login screen everytime, while I needed 5-10 reboots with 2.6.35 for this to work.
I am using HP Elitebook 8440p with Intel graphic card.

[Andy Whitcroft (apw)]

So we now have an official v2.6.38-rc2 kernel in the archive (2.6.38-1.28), if those of you affected by this could confirm whether the issue is resolved by that kernel that would be very helpful. Please report back here. Thanks!

[Chewie (hannes-woelfler)]

Hi Andi
Can you give us a short hint where to download ?

2011/2/2 Andy Whitcroft <email address hidden>

> So we now have an official v2.6.38-rc2 kernel in the archive
> (2.6.38-1.28), if those of you affected by this could confirm whether
> the issue is resolved by that kernel that would be very helpful. Please
> report back here. Thanks!
>

[Laurent Bigonville (bigon)]

Not working for me, external display is working but internal is not.

linux-image-2.6.38-1-generic 2.6.38-1.28

[Michael Lustfield (michaellustfield)]

On Wed, 02 Feb 2011 14:17:38 -0000
Andy Whitcroft <email address hidden> wrote:

> So we now have an official v2.6.38-rc2 kernel in the archive
> (2.6.38-1.28), if those of you affected by this could confirm whether
> the issue is resolved by that kernel that would be very helpful. Please
> report back here. Thanks!
>
> ** Changed in: linux (Ubuntu Natty)
> Status: Confirmed => Incomplete
>

It's working fantastic for me. However, as a note of caution, v2.6.38-rc3
delivered some breaking for me. Seems to be just a little regression that will
probably be resolved in -rc4.

I still have issues with backlight control, which is of course irrelevant to
this bug; just mentioning it.

[Richard Duivenvoorde (rduivenvoorde)]

Just tried the the Natty daily from http://cdimage.ubuntu.com/daily-live/current/ telling me it's running 2.6.38-1.28

Not working for me with E6510 HD 1920x1080 (see https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/648335 for hardware info). I can use external display, but laptop display stays black.

[Dejan (dejan-rodiger)]

For me, 2.6.38-rc2 and rc3 from http://kernel.ubuntu.com/~kernel-ppa/mainline/
is working OK for me. I get screens on both monitors (internal and external), or only internal if I don't have external monitor connected. I have HP Elitebook 8440p with Intel graphic card.

But I have also installed git Intel driver from this ppa: https://launchpad.net/~glasen/+archive/intel-driver and x-updates from here https://launchpad.net/~ubuntu-x-swat/+archive/x-updates

This changed how xrandr see internal display. It is no longer DP1, it is eDP1 now, and external is VGA1.

[Francisco Cribari (cribari)]

I installed kernel 2.6.38 RC3 from http://kernel.ubuntu.com/~kernel-ppa/mainline/ but it booted to a blank screen. The kernel that w
orks for me is

cribari@darwin:~$ uname -a
Linux darwin 2.6.38-997-generic #201102020913 SMP Wed Feb 2 09:15:24 UTC 2011 x86_64 GNU/Linux

It is from drm-intel-next .

Hardware is DELL Latitude E6510, Intel GPU, Intel i7, full HD (1920 x 1080).

[Chewie (hannes-woelfler)]

Same here, installed RC3 as proposed -> only external display was working ->
using DELL E6510 in Docking Station the external DVI Monitor was on HDMI3.
Internal display remained black.
Up to now my solution works with Linux ucl03371 2.6.37-12-generic #26-Ubuntu
SMP Wed Jan 5 18:42:49 UTC 2011 i686 i686 i386 GNU/Linux on a up to date
patched Kubuntu 11.04

[Francisco Cribari (cribari)]

Kernel 2.6.38-1.27~lucid1 from https://launchpad.net/~kernel-ppa/+archive/ppa boots to a blank screen. Switching to a VT and back does not help. Hardware: DELL 6510, Intel GPU, i7, 8 GB RAM, full HD.

[Francisco Cribari (cribari)]

Today I installed

linux-image-2.6.38-997-generic_2.6.38-997.201102081238_amd64.deb

It boots to X, but it restarts X after a few minutes of use. I had to revert back to

linux-image-2.6.38-997-generic_2.6.38-997.201102020913_amd64.deb

Hardware: DELL 6510, i7, Intel GPU, full HD.

[Francisco Cribari (cribari)]

Kernel 2.6.38 RC4 boots to a blank screen on my DELL 6510 (which runs on Ubuntu 10.04).

[Michael Lustfield (michaellustfield)]

On Thu, 10 Feb 2011 21:46:05 -0000
Francisco Cribari <email address hidden> wrote:

> Kernel 2.6.38 RC4 boots to a blank screen on my DELL 6510 (which runs on
> Ubuntu 10.04).

Same here. RC3 and RC4 don't work for me but RC2 works great.
I'm getting to the point of 'grr' with this issue. I'm guessing they've been
making a lot of changes around this area of the kernel but I haven't looked
into it much yet.

[Andy Whitcroft (apw)]

Ok that is interesting. Some reports here that when the LVDS is black, that an external monitor is enabled. For those who found -rc3/-rc4 are black could you try testing with the image Francisco was using the 2011-02-08-natty version from the link below. I do not expect this to be stable, I am looking to see if the screen initialised correctly:

    http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/

Instructions for installing are here:

    https://wiki.ubuntu.com/Kernel/MainlineBuilds

[John Lenton (chipaca)]

On Fri, 11 Feb 2011 15:12:06 -0000, Andy Whitcroft <email address hidden> wrote:
> Ok that is interesting. Some reports here that when the LVDS is black,
> that an external monitor is enabled. For those who found -rc3/-rc4 are
> black could you try testing with the image Francisco was using the
> 2011-02-08-natty version from the link below. I do not expect this to
> be stable, I am looking to see if the screen initialised correctly:
>
> http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/

I get a blank screen with that also; so far of the ones I've tried the
only one that has worked is 2.6.36-rc5 with the 900ms delay patch.

[Laurent Bigonville (bigon)]

WORKFORME on natty with

Linux eldamar.bigon.be 2.6.38-997-generic #201102081238 SMP Tue Feb 8 12:41:16 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

E6510, core i5, FullHD

[hleong (excel28)]

Laurent Bigonville - can you give details on what works? With or without external monitor? With or without docking station?

[Laurent Bigonville (bigon)]

Hi,

Oups indeed I forgot to specify that.

It's with the internal display, I've no dock or external display to test with

[Timo Jyrinki (timo-jyrinki)]

This is still broken with E6510 with both mainline and Ubuntu kernels. I got the information from Intel developer that they got some regression report about the eDP patches, so they didn't send the patches to Linus yet. Therefore the fix will be in only in 2.6.39 kernel (or http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/current/).

Since this is rather severe problem, and from what I've seen the eDP patches were tested in many iterations and not possibly the last one, I'd suggest keeping this on radar as a patch to be backported to natty's 2.6.38, considering Dell is one of Canonical's key partners for Ubuntu.

[John Lenton (chipaca)]

On Tue, 15 Feb 2011 06:28:36 -0000, Timo Jyrinki <email address hidden> wrote:
> This is still broken with E6510 with both mainline and Ubuntu kernels. I
> got the information from Intel developer that they got some regression
> report about the eDP patches, so they didn't send the patches to Linus
> yet. Therefore the fix will be in only in 2.6.39 kernel (or
> http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/current/).
>
> Since this is rather severe problem, and from what I've seen the eDP
> patches were tested in many iterations and not possibly the last one,
> I'd suggest keeping this on radar as a patch to be backported to natty's
> 2.6.38, considering Dell is one of Canonical's key partners for Ubuntu.

I can confirm that the image I downloaded yesterday from
http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/current/
that is linux-image-2.6.38-997-generic_2.6.38-997.201102120912_i386.deb
is the one that works best for me so far: I've finally stopped using
2.6.36-rc5 with the 900ms patch. X comes up fine, the full HD panel
works (and it's even dithered correctly!), and suspend/resume works
also.

[Nischal Rao (rao-nischal)]

The kernel linux-image-2.6.38-997-generic_2.6.38-997.201102120912_i386.deb from http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/current/ doesn't work with external displays. When connected to external monitor, the laptop screen goes blank. Simultaneous access is not working.

[Manuel Carro (manuelcarro)]

Nischa,

there is information and attempts to patch it at https://bugs.freedesktop.org//show_bug.cgi?id=34116

Cheers!

[Nischal Rao (rao-nischal)]

Hi Manuel,

I am a newbie and I don't know how to revert the 2 patches. Can you please tell me how to do it? Or would the fix come up in perhaps the next drm-intel-next?

Thanks in advance

[Manuel Carro (manuelcarro)]

Nischal,

$ git revert <commit-identifier>

inside the drm-intel sources (after switching to the drm-intel-next branch) does the trick. After that you can compile and install the kernel.

I do not know whether / when this precise patch will make it into drm-intel (and eventually into mainline). I suppose that some time to let other people try it is necessary.

[Timo Jyrinki (timo-jyrinki)]

The bug #561802 test kernel's patch "skip FDI/PCH enabling backported to 2.6.38-rc4" fixes the black screen on boot for two _E6510_ users here as well, in addition to one E6410 user.

[Andy Whitcroft (apw)]

As mentioned in comment #184 people are getting good results with kernels prepared for that bug, to repeat what I said on that bug:

In the upstream bug Jesse provides a 2.6.38 based backport of an upstream fix. I have pulled this into a Natty kernel. Could those of you affected by the black screen on boot try the kernels below and report back here. The kernels are at the URL below:

    http://people.canonical.com/~apw/lp561802-natty/

Please report back here. Thanks.

[hleong (excel28)]

I installed the x86_64 deb packages from #185, and I can confirm that it works... with some issues with VirtualBox.

I had VirtualBox installed, so it actually gave me errors. I went to the VirtualBox site and noticed that there was a 4.0.4 (I had 4.0.2) update that was updated today, so I updated the 4.0.4 package (sudo apt-get upgrade virtualbox-4.0). But by doing so, it wanted me to install an updated 2.6.38-4 kernel, which I accepted. After it was done upgrading, it rebooted to a blank screen (because it wasn't the 2.6.38-4.31~lp561802v201102162013 version). So I rebooted to an old version that I know works, then I installed the kernel listed in #185 (which during the process it said it was 'downgrading'). I rebooted and everything works now (no blank screen and virtualbox 4.0.4 works).

I have not tested with external monitor or docking station. I will try to do that later.

I'm on KDE (Kubuntu), and when I change the brightness, it something funny, like it will go down in brightness, then up a little.

Note: once I rebooted with the #185 version, apt-get wants me to upgrade to the 2.6.38-4 kernel, which I know it won't work, so i'll just ignore for now.

[Christian Demoustier (cdemoustier)]

I downloaded and installed kernel "linux-image-2.6.38-4-generic_2.6.38-4.31~lp561802v201102162013_amd64.deb" from link in #185.

It boots normally my Ubuntu 10.04 (lucid) with internal LCD panel. I don't have an external display to test with. It seems to be blinking twice at boot but after that display is working.

[Magnus Sandin (muk)]

Tested AMD64 kernel from comment #185 with Dell E6510, Core i5, Full HD.

* Internal LCD works.
* External monitor connected with HDMI/Display Port works.
* External monitor connected with VGA -> NOT Tested.
* Suspend/Resume does not suspend properly, wakes up as soon as it is suspended, however no crashes.

Have a similar problem with brightness as in comment #186. When reducing back light one step, it first reduces one step and after like 500ms it reduces another step...

[hleong (excel28)]

#185 works with docking station =D

[Nischal Rao (rao-nischal)]

Tried the i386 kernel of comment #185 and would like to confirm that:

1. Boot works fine.
2. Suspend / resume works fine.
3. Works great when connected external display.
4. No problem at all using virtualbox 4.0.2

Looks like all problems with E6510 has finally been fixed. :)

[Chewie (hannes-woelfler)]

I would also like to thank you and report everything working OK.
My system is a DELL E6510 with updated Kubuntu 11.04
Running the suggested Kernel from #185 solved the problem for me.

External Monitors are working too as they did with former versions of
Kubuntu.

My system is connected to a DELL docking station.
Internal LCD is @ eDP1 ->
external Monitor via DVI is @HDMI3

No problems during Kernel installation.
Desktop Effects also working -> but at poor performance.

Overall it is a huge step into the right direction -> thank all of you for
your great work making linux useful :)
regards
Chewie

2011/2/18 Nischal Rao <email address hidden>

> Tried the i386 kernel of comment #185 and would like to confirm that:
>
> 1. Boot works fine.
> 2. Suspend / resume works fine.
> 3. Works great when connected external display.
> 4. No problem at all using virtualbox 4.0.2
>
> Looks like all problems with E6510 has finally been fixed. :)
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/600453
>
> Title:
> [arrandale] [i915] DELL E6510: blank screen on boot (Intel GPU)
>
> Status in “linux” package in Ubuntu:
> Incomplete
> Status in “linux” source package in Lucid:
> Triaged
> Status in “linux” source package in Maverick:
> Triaged
> Status in “linux” source package in Natty:
> Incomplete
> Status in “linux” package in Fedora:
> Fix Released
> Status in “linux” package in openSUSE:
> Confirmed
>
> Bug description:
> I am running Ubuntu Linux 10.04 64 bits on a DELL 6510 notebook with
> integrated Intel graphics card. The machine only boots in a low-
> graphics mode. I detected the following error message in the logs:
>
> (EE) intel(0): No kernel modesetting driver detected
>
> I used i915,modeset=0 as a kernel option but I am no longer using. The
> xorg.config file I am using is
>
> Section "Device"
> Identifier "Configured Video Device"
> BusID "PCI:0:2:0"
> Driver "intel"
> Option "AccelMethod" "UXA"
> EndSection
>
> Section "Module"
> Load "glx"
> Load "dri"
> Load "extmod"
> Load "record"
> Load "dbe"
> Load "GLcore"
> Load "xtrap"
> Load "freetype"
> EndSection
>
> Section "Monitor"
> Identifier "Configured Monitor"
> EndSection
>
> Section "Screen"
> Identifier "Default Screen"
> Monitor "Configured Monitor"
> Device "Configured Video Device"
> DefaultDepth 24
> EndSection
>
> Section "DRI"
> Mode 0666
> EndSection
>
> My kernel is
>
> Linux darwin 2.6.32-23-generic #37-Ubuntu SMP Fri Jun 11 08:03:28 UTC
> 2010 x86_64 GNU/Linux
>
> The intel driver:
>
> ii xserver-xorg-video-intel
> 2:2.12.0+git20100628.17884af4-0ubuntu0sarvatt~lucid
> X.Org X server -- Intel i8xx, i9xx display d
> ii xserver-xorg-video-intel-dbg
> 2:2.12.0+git20100628.17884af4-0ubuntu0sarvatt~lucid
> X.Org X server -- Intel i8xx, i9xx display d
>
> Any suggestions? Thanks.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 10.04
> Package: linux-image-2.6.32-23-generic 2.6.32-23.37
> Regression: No
> Reproducible: Yes
> ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
> Uname: Linux 2.6.32-23-generic x86_64
> AlsaVers...

[Andy Whitcroft (apw)]

For those seeing oddities with brightness I think we have an unrelated issue recently in userspace affecting brightness. I am going to get a new bug started for that once I figure out which component to blame.

[Andy Whitcroft (apw)]

Ok the commit tested here is now scheduled for application to 2.6.38, in the meantime I am pulling it into the Natty kerenel and it should be in the next upload. Fix Committed. Thanks all for your testing.

[Alfe (alfeberlin)]

After testing now for a second day, no stability issues (X crashes) to report (which is a great relief!).

One issue found: I suspended at work with a second monitor attached, then unplugged the second monitor, went home, tried to resume without a second monitor, got a black screen with backlight. Switching to other consoles worked, but switching back to X just restored the black screen. So I could kill and restart my X from another console, so rebooting wasn't necessary, but of course the session was lost.

I can prevent running into this problem by either unplugging the second monitor (and quickly reconfiguring the X for single-display) before suspending or maybe (didn't test this) by attaching another second monitor before resuming, so there is a workaround.

Cheers, Alfe

[John Lenton (chipaca)]

On Fri, 18 Feb 2011 10:20:39 -0000, Alfe <email address hidden> wrote:
> After testing now for a second day, no stability issues (X crashes) to
> report (which is a great relief!).
>
> One issue found: I suspended at work with a second monitor attached,
> then unplugged the second monitor, went home, tried to resume without a
> second monitor, got a black screen with backlight. Switching to other
> consoles worked, but switching back to X just restored the black screen.
> So I could kill and restart my X from another console, so rebooting
> wasn't necessary, but of course the session was lost.
>
> I can prevent running into this problem by either unplugging the second
> monitor (and quickly reconfiguring the X for single-display) before
> suspending or maybe (didn't test this) by attaching another second
> monitor before resuming, so there is a workaround.

did you try hitting the 'change monitor' button (or whatever it's
called; Fn+F8 on my e6510) in X?

[Manuel Carro (manuelcarro)]

Alfe,

besides Fn+F8, as suggested, changing the brightness may also do the trick (it worked for me in other kernels). In my e6510 it is Fn+arrow up to change brightness. Fn+arrow left (to activate / deactivate automatic brightness adjustment) may also work.

[Alfe (alfeberlin)]

John, I am not sure whether I also tried Fn-F8 (which has a laptop/screen icon on it) (p=70%). I'm also not sure whether I tried it more than once (p=10%). Sorry for being so vague; I just tried everything which came to mind. Also closing and opening the lid didn't help.

Manuel, I did not try brightness changes; nice idea :-)

I also found out that Windows-P in my configuration does something with my displays (turning them or something like that), maybe that can help as well.

I just tried to reproduce the problem reported in #194 but couldn't (tried it twice just now). The laptop screen always refreshed properly after resuming from suspend without the second monitor. I will try to reproduce the problem again in the next time and if I manage, I will try your suggestions and report back here. But maybe the problem was due to something else.

Cheers, Alfe

[Sbrabec-novell (sbrabec-novell)]

I have the same problem in openSUSE 11.4 Milestone 5 with Dell Optiplex 980 with two dual head graphic cards.

Symptoms: Grub appears, then initial kernel splash, then screen goes to sleep. Finally X screen appears after several seconds. Ctrl+Alt+F1 causes screen freeze (X display is still visible, but does not react), pressing Ctrl+Alt+F7 returns back.

Summary: Console does not work. Grub, initial kernel splash and X works.

I can provide hwinfo.

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux - 2.6.38-5.32

---------------
linux (2.6.38-5.32) natty; urgency=low

  [ Andy Whitcroft ]

  * rebase to mainline 6f576d57f1fa0d6026b495d8746d56d949989161
  * [Config] updateconfigs following rebase to v2.6.38-rc6
  * [Config] enable CONFIG_DMAR
    - LP: #552311

  [ Upstream Kernel Changes ]

  * drm/i915: skip FDI & PCH enabling for DP_A
    - LP: #561802, #600453, #681877

  [ Major Kernel Changes ]

  * rebase from v2.6.38-rc5 to v2.6.38-rc6
    - LP: #718402
    - LP: #719524
    - LP: #721126
    - LP: #719691
    - LP: #722689
    - LP: #722310
 -- Andy Whitcroft <email address hidden> Tue, 22 Feb 2011 13:28:39 +0000

[Bart Staal (bart.staal)]

I also have a E6510 with these problems (on maverick). I tried the #185 kernel (just installed on maverick) and this solves all the problems. Is there any chance this fixes will be backported to 10.10? Or is it safe to run this kernel (which is meant for Natty)?

[Chewie (hannes-woelfler)]

Hi all
I am running the Bugfix from #185 for some days now ..
During this time I had two major system crashes related with our problem
here:
See dmesg output:

[36261.219478] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer
elapsed... GPU hung
[36261.221592] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request
returns -11 (awaiting 10239609 at 10239591, next 10239626)
[36261.232508] dell-wmi: Received unknown WMI event (0x11)
[36261.728908] dell-wmi: Received unknown WMI event (0x11)
[36263.449835] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer
elapsed... GPU hung
[36263.449869] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request
returns -11 (awaiting 10239627 at 10239591, next 10239637)
[36263.450249] [drm:i915_reset] *ERROR* GPU hanging too fast, declaring
wedged!
[36263.450255] [drm:i915_reset] *ERROR* Failed to reset chip.
[36264.946873] Xorg[1012]: segfault at 0 ip 080a4182 sp bfcaae5c error 4 in
Xorg[8048000+1ab000]

This resulted in black screen and I had to reboot.
uname -a
Linux ucl03371 2.6.38-4-generic #31~lp561802v201102162013 SMP Wed Feb 16
20:16:02 UTC 2011 i686 i686 i386 GNU/Linux
 dpkg -l | grep intel
ii intel-gpu-tools
1.0.2+git20100324-0ubuntu1 tools for debugging the Intel
graphics driver
ii libdrm-intel1
2.4.23-1ubuntu3 Userspace interface to
intel-specific kernel DRM services -- runtime
ii xserver-xorg-video-intel
2:2.14.0-1ubuntu9 X.Org X server -- Intel i8xx,
i9xx display driver

regards
Chewie

[hleong (excel28)]

I've noticed something interesting with the brightness. I pushed Fn+Left arrow (disable/enable auto brightness) by accident and now I noticed that I don't see the weird brightness. Maybe this is causing the issue?

uname -a
Linux mobuntu6510 2.6.38-5-generic #32~lucid1-Ubuntu SMP Tue Feb 22 18:11:26 UTC 2011 x86_64 GNU/Linux

[Michael Bell (bellmr)]

Hello, I've been tracking this bug for a while but haven't tried testing anything until now. I've installed the x64 kernel from #185 on my E6510 (Full HD & intel graphics) over Maverick and it does not appear to work for me unless I add the option i915.modeset=0 to the kernel options at boot as before. If I do not do this and leave the default kernel options, it boots to a text login and shows the message:

[ 13.039854] intel ips 0000:00:1f.6: failed to get i915 symbols, graphics turbo disabled

Now, I'm not terribly experienced with this sort of thing, so I may have done something wrong.

uname -a
Linux mrbell-e6510 2.6.38-4-generic #31~lp561802v201102162013 SMP Wed Feb 16 20:31:41 UTC 2011 x86_64 GNU/Linux

[Steven (svanpoeck)]

Same as comment #203 here on a DELL Latitude E6510 with resolution 1600x900 x64 kernel.

I rolled back to the standard kernel, which BTW, functions "correctly" despite the "failed to get i915 symbols, graphics turbo disabled" message: Wakeup after suspend always results in black screen, most of the times when I close the lid without locking the screen is does the same, even if I specified that closing lid should just black screen, not suspend.

Sometimes when plugging out/in on a docking station with an external monitor, it all goes black too.

No other options than hard reboot 4secs on Power button

Steven

[Michael Bell (bellmr)]

As an update to #203, I've installed 11.04 alpha 3 (2.6.38-5-generic) a few hours ago and so far things seem to be working great. Boot is good, suspend/resume works. I haven't tried the external monitor yet.

[Seth Forshee (sforshee)]

I backported the fix from natty to maverick (along with several other things required by the fix). I've posted kernel builds at

http://people.canonical.com/~sforshee/lp681877/

The backport was a little tricky, so I'm not really sure whether it is completely correct or if there's any chance of getting this into a maverick SRU due to the amount of changes required. Testing is appreciated. Please report results back here.

[Alfe (alfeberlin)]

Seth, I installed your kernel on Ubuntu 10.10, Dell Latitude E6510 with Intel graphics 1920x1080.

Unfortunately, neither standalone nor with a second monitor attached did the main screen light up after mode switch during booting. The second monitor worked fine. It's attached via a docking station and a display port cable.

There is a slight chance that I failed in choosing your kernel when booting; installation of the debs provided by you told me that this would mean upgrading an installed package, so I figured that now my installed 2.6.35-28 was going to be upgraded. This kernel (35-28) then I chose on boot-time, though the grub menu did not display any of your complicated version number suffixes, resulting from the detailed patch level stuff.

I' love to run further tests because I'd like to step down from the upstream 2.6.38 patch I'm using currently as this prevents me from using a VMware installation (some different trouble) and doesn't seem too stable as a whole.

Alfe

[Seth Forshee (sforshee)]

@Alfe, thanks for testing. You can check whether or not you're using the test kernel kernel by running 'cat /proc/version_signature' in a terminal. With the test kernel the output should have ~lp681877v201114131625 at the end, whereas a stock kernel would not.

[Alfe (alfeberlin)]

Seth, I checked using your instruction. I was testing the kernel you provided; so this is bad news :-/

[Seth Forshee (sforshee)]

@Alfe, thanks for checking. I'll double-check my backport for mistakes, but there may be other changes that are also needed to fix this problem for maverick.

[Mark Russell (marrusl)]

@Seth, do you expect this would be the same with the E6410? You also posted the same kernel to Bug #561802 so I'm guessing we would expect the same results. But if it would help to get confirmation I can ask a customer to give it a go. Otherwise, I'll just wait for the next proposed fix. Thanks!

In general I have my doubts about backporting/SRUing this... I'm worried that part of the resolution is in the natty kernel and part is in the natty X stack.

[Seth Forshee (sforshee)]

@Mark:

I posted to all three bugs that the changelog indicates are fixed by the backported patch. I wouldn't be surprised at all if other changes were part of the resolution, even if the X stack isn't involved, as related parts of the kernel driver have seen very significant change between maverick and natty. Note though that comments #200 and #201 on bug #561802 indicate that using a natty kernel with maverick fixes the problem on the E6410, which would contradict the idea that a fix to the X stack is needed.

It would be helpful to have testing on an E6410 if possible, but I'm not very hopeful of it working since it didn't help with the E6510.

[Haker-MSL (matis-l)]

Hello,

The same problem for:

eMachines e525.

On splashscreen everything seems to load OK, but screen is very dark and I cannot see anything - but system is loaded OK. When I clcik "CTRL+ALT+DEL" i see windows with menu to Shutdown/Reboot - but it's very dark, almost invisible. After 30 seconds system shutdown perfectly. With nomodeset everything seems to be OK, but with KWIN 3D efects KDE hangs randomly. I can provide lspci, hwinfo etc.

Greetings

[Haker-MSL (matis-l)]

Sorry I forgot to write that for me problem exists after kernel update on 11.3 and even on Live CD in 11.4 and 11.2 Mileston 5.

I don't know if this issue is relative, or I should create a new one.

greetings

[Stéphane Rouges (stephane-rouges)]

Hi,
Seems that the bug is back with kernel 3.0.15... :-\
Stéphane

[Francisco Cribari (cribari)]

Yes, the problem is back with kernel 3.0.0-15. Blank screen at boot.

[Masseuro (aurelien-masfrand)]

back -_-

[Chewie (hannes-woelfler)]

i can also confirm that the bug is back again after the latest update to 3.0.15..

[marcstraemke (marcstraemke)]

Having the Same Issue (E6510) with 3.0.15, Display does not turn on if booted in Docking Station with Lid closed.

If the lid is open at boot time and closed at display manager login screen it works.

[Manuel Carro (mcarro)]

Ubuntu kernel 3.2.0-15-generic (compiled from sources following http://blog.avirtualhome.com/2012/01/13/compile-linux-kernel-3-2-for-ubuntu-11-10/) boots with graphics (and they seem to be snappier, but this may be just my impression). However, when it resumes after suspension the screen remains blank, and it does not seem to hibernate properly.

I have a del 6550 with an ironlake chip (IIRC).

[John Lenton (chipaca)]

On Wed, 08 Feb 2012 21:35:39 -0000, Manuel Carro <email address hidden> wrote:
> Ubuntu kernel 3.2.0-15-generic (compiled from sources following
> http://blog.avirtualhome.com/2012/01/13/compile-linux-kernel-3-2-for-
> ubuntu-11-10/) boots with graphics (and they seem to be snappier, but
> this may be just my impression). However, when it resumes after
> suspension the screen remains blank, and it does not seem to hibernate
> properly.

manuel, that sounds very much like bug 902657.

[Manuel Carro (mcarro)]

Hi. Ubuntu kernel 3.0.0-14 works for me whild 3.0.0-15 already fails to start the graphic system. Is there a public git / svn / whatever with the Ubuntu kernel (and instructions to compile) so that I can try to bissect the problem?

Thanks everyone.

[Manuel Carro (mcarro)]

Hi. Kernel 3.0.0-16 works for me.

[Doros Eracledes (d-eracledes)]

changing to GRUB_CMDLINE_LINUX_DEFAULT="quiet acpi_osi=Linux" did the job for me.

 I'm running Ubuntu 11.10 amd64 on an HP 2540p EliteBook.

$ sudo lspci -v -s 00:02.0
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller])
        Subsystem: Hewlett-Packard Company Device 7008
        Flags: bus master, fast devsel, latency 0, IRQ 45
        Memory at d0000000 (64-bit, non-prefetchable) [size=4M]
        Memory at c0000000 (64-bit, prefetchable) [size=256M]
        I/O ports at 5058 [size=8]
        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
        Kernel modules: i915

[JC Hulce (soaringsky)]

This bug affects Ubuntu 10.10, Maverick Meerkat. Maverick has reached end-of-life and is no longer supported, so I am closing the bugtask for Maverick. Please upgrade to a newer version of Ubuntu.
More information here: https://lists.ubuntu.com/archives/ubuntu-announce/2012-April/000158.html

[Jeffm-9 (jeffm-9)]

With the coming release of openSUSE 12.2, openSUSE kernel developers are focusing their efforts there. Reports against openSUSE 11.4 and prior will not get the attention needed to resolve them before openSUSE 12.2 is release and openSUSE 11.4 becomes unmaintained.

Please re-test with openSUSE 12.1 or openSUSE RC2+ and re-open with an updated Product if you still encounter your issue.

We apologize for this issue not getting the attention it deserves but we are focusing our resources in the area where they will have the most impact for our users. We're working hard to make openSUSE 12.2 the best openSUSE release yet!

[Rolf Leggewie (r0lf)]

lucid has seen the end of its life and is no longer receiving any updates. Marking the lucid task for this ticket as "Won't Fix".