8086:3582 [i855] X doesn't start with kernel 2.6.32-21 unless passing i915.modeset=1

The latest linux upload included a change to disable KMS on the i855, which your lspci output shows is what you have. So this may be a regression caused by disabling KMS on your system.

Please boot each of the following ways and report the results:

- with the 'splash' option removed from the kernel commandline
- with 'splash' and 'i915.modeset=1' included on the kernel commandline

Thanks for your prompt response Steve.

With "splash" removed the only difference is the lack of a splash screen and it is replaced with the bootup sequence, the laptop still locks up just after where you would expect the splash screen to be.

With "splash" + "i915.modeset=1" in place it boots perfectly and possibly slightly quicker than the 2.6.32-20 kernel.

My only question now is will I have to manually modify grub.cfg each time a kernel or Grub is replaced?

Thanks again.
Michael (k3lt01)

For information on how to permanently set a boot option in your grub config, please see <https://wiki.ubuntu.com/LucidLynx/ReleaseNotes#Working%20around%20bugs%20in%20the%20new%20kernel%20video%20architecture> - the description is written for the opposite case when you need to /disable/ KMS, but you can set the i915.modeset option here to /enable/ KMS just as well.

i am facing the same issue.

i haven't tried the solution posted here but i can use my system with the older kernel and also in the recovery mode and starting x in safe mode looks as good as normal

i was thinking maybe it was a driver issue as i am also not able to play video files in full screen, all of them get stuck... but they play fine if played in the defualt window size, could this also be related to the changes in the new kernel or should i file a new bug report.

also in have not been able to turn on desktop effects since i moved to lucid beta.

hey i checked with both

i915.modeset=1

and

nomodeset

options in the kernel option in grub menu, but nothing seems to be working the only way i can boot into ubuntu with the new kernel is to boot with the safe graphics mode.

nomodeset didn't work, i915.modeset=1 worked but now I can't enable desktop effects. I think I have an onboard intel graphics chip, could that be the problem?

@Riffer

maybe - the following command whould give you the graphics device you have installed on your system:

lspci | grep -i vga

running command "lspci | grep -i vga" gives this output

00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)

which is same to what "k3lt01" has on his/her pc

i have tried all the possible settings with modeset, also i tried to reconfigure x after booting into the safe mode but that utility does not seem to work in lucid. only way i can log in with the latest kernel is to boot into failover x 'safe graphics mode'.

any help would be appreciated.

thnx

I got the same output
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)

madmax try the "i915.modeset=1" , worked for me except it booted into low graphics mode.

I have same problem with the sam Intel chip.
The option i915.modset=1 works

i guess the i915.modeset=1 works for me also but the problem i am facing is that i run into one or two more possible bugs rite after it.

these bugs from what i understand after going through various posts and trying many workarounds posted are present in either "plymouth" or "fsck" or "sysvinit" or "mountall" or all of them and have been reported in Bug #554079 Bug #556372 Bug #554737 Bug #559761.

after trying so many workarounds for various packages i dont know anymore what all exact changes i have made. one of the possible reasons i am facing these bugs together is that i did an upgrade from 9.10 to 10.04 alpha.

the plymouth dependency problem just makes it difficult to fix the problem as trying to remove it results in complete removal of the desktop environment.

i think plymouth should atleast be made optional for headless server systems till all the bugs are combed out.

i have been booting into safe graphics from recovery option in grub and that seems to be the only way to boot into it.

i hope a fresh install fixes these issues.
i will try and post back.

okey i did a fresh install of lucid beta.

only changes i had to make in order to boot successfully into the system with the latest kernel i.e. 2.6.32-21 was to set the option

i915.modeset=1

in the grub menu.

thnx for all the help

btw i also came across this at https://wiki.ubuntu.com/LucidLynx/ReleaseNotes#Working%20around%20bugs%20in%20the%20new%20kernel%20video%20architecture

Intel 8xx X freezes/crashes

The -intel driver fails with X freezes or crashes on certain i8xx hardware. The issue is known upstream but solutions are still under development. For now, to work around the issue, boot with the -vesa video driver. See http://wiki.ubuntu.com/X/Bugs/Lucidi8xxFreezes for further details.

LucidLynx/ReleaseNotes (last edited 2010-04-22 14:21:05 by Mathias Gug)

@ madmax1735: Max my friend, Steve Langasek pointed that link out 6 days ago in this very bug report. He posted it because I asked if I would have to set it each time a new kernel was installed or Grub was updated.

Glad to see things working for you now.

Another with problems getting 10.04 RC to boot properly.

damon@damon-laptop:~$ lspci | grep -i vga
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)

In order to get 10.04 RC to boot and start X I have been manually selecting the previous kernel (2.6.31-20) at boot.

However if I use the following kernel option (posted above - thanks!) I can get 2.6.32-21 (default kernel) to boot :

i915.modeset=1

Hope this gets resolved before 10.04 Final is released.

@ k3lt01 yes i know, but the reason i pointed that page out again is because the driver related info is at very end and i believe like many others i completely missed it when i saw that page for the first time.

i would like to point out that i am still facing problems with the video. sometimes a video plays fine but at other times system completely locks up with a black screen and nothing works and i cant even log into other tty's (pressing Cltr+Alt+'F1/F2/F3)

from what i have read this has something to do with the memory allocations.

i havent checked if system is accessible through ssh at those times as i had papers to submit. i will check once if the crash happens again.

p.s sorry for the late reply but i was on winxp for sometime due to paper as open office refused to open my .doc files

good news good people

after the recent driver upgrade in lucid, everything works fine with intel 855GM
videos do not make system crash anymore as well as desktop effects can be enabled now.

:)

but the "i915.modeset=1" has still to be enabled in the grub boot options for the latest kernel.

10.04 LTS Live CD do not boot without i915.modeset=1

lspci | grep -i vga
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)

@ yannis, While I didn't use the LiveCD I did a clean install on Saturday with the AlternateCD, and also the MiniCD (I have 2 separate systems on 1 laptop) and they were ok. Maybe you could try with the AlternateCD.

Had the same problem. My Acer TravelMate 662 laptop (Intel 855GM) refused to boot with Lucid. Adding boot option i915.modeset=1 fixed this problem.

Afterwards I was experiencing X crashes when playing videos with totem.

Installing the mainline kernel 2.6.33.3 provided by Ubuntu finally fixed all my problems, even the X crashes:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.33.3-lucid/

Laptop: Acer TravelMate 290 (292LCi to be more specific).
Graphics: VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device

I was (and still am) really disappointed that the 10.04 LTS (Lucid Lynx) Live CD does not work beyond the first installation screen (with keyboard and human icon at the bottom), after which it just goes blank, aptly named "the purple screen of death" in the forums. This is the first time an Ubuntu (Stable Release) Live CD does not work 'as downloaded' for me.

I was able to workaround, following the instructions of Solution 2 at http://www.ubuntugeek.com/how-to-fix-ubuntu-10-04-lts-lucid-blank-screen-at-startup.html i.e. with adding "i915.modeset=0 xforcevesa" to the startup command and after that the Live CD performed as would be expected.

I am unsure about upgrading now. This would be from 8.04 LTS (Hardy Heron). Are there any plans for a repaired Live CD?

Laptop Dell D400 latitude
Graphics Card VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)

I upgraded from V9.10 and hit this graphics card problem.

Needed to use the boot option i915.modeset=1 to get the graphics working - without this had the black screen problem mentioned earlier in the post. Still have problems playing videos but that is not a big problem for me.

Laptop: Acer TravelMate 290 (292LCi to be more specific).
Graphics: VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device
Kernel: 2.6.32-22

Progress report:
I have now successfully upgraded from Hardy. I followed the instructions for Workaround A at https://wiki.ubuntu.com/X/Bugs/Lucidi8xxFreezes and Lucid boots fine now, but playing videos causes an X freeze and Desktop effects can not be enabled. (One time selecting desktop effects caused a funny error: after a bit of flickering the screen went back to normal, but all letters in menus were no longer from the latin character set, but some unknown set (could have been Thai as far as I can say, but maybe just a random mix). However, judging from the lengths of words it was still in the English language setting and I was able to recognise the logout option. Logging out and in again put everything back to normal. Unfortunately, I cannot reproduce the bug.)

Following Steve's instructions, i.e. permanently setting the boot option "i915.modeset=1" in the /boot/grub/menu.lst, gives exactly the same result.

X freezes whenever I start a video (e.g. using the example-content video "UbuntuIsHumen.ogv" with Totem Movie Player, but also with a random .avi and xine). Flash videos with Firefox are fine. Movie Plazer with sound files also works fine.

@Christine: Have you tried installing the mainline kernel? This fixed my video playback problems.

You can find the kernel here:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.33.3-lucid/

@ Peter: Actually, today's update (sorry, don't know which package) fixed things with Totem Movie Player, but xine was still reporting segmentation faults, so I installed the mainline kernel and, indeed, it completely fixed the video problems. Thanks for pointing that out again!

Unfortunately, I still have problems using an external monitor, but that might be a quite unrelated bug. I can switch the external monitor on, but not off, and inevitably things crash/freeze when I'm changing Monitor settings.

There was a kernel update today, but I still can't get my system to boot into X.

Neither of these kernels work for me without the "i915.modeset=1" kernel option:

2.6.32-21
2.6.32-22

I had to update to a mainline kernel to get my system to boot properly without having to resort to kernel options.

Currently using 2.6.34-020634rc6-generic

Laptop: Acer TravelMate 290 (292LCi)
Graphics: VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device
Kernel: 2.6.33-02063303-generic

When I start System -> Administration -> "System Testing" everything seems normal for about 5 seconds (i.e. window pops up, tells me it's starting the hardware test and the progress bar moves) and then X freezes.

This one worked for me:
 http://ubuntu-tutorials.com/2010/05/06/ubuntu-10-04-lucid-blank-screen-at-startup-workaround/

had to use i915.modset=0

however my card is not intel 855.
lspci shows:
00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)

I think people are assuming that the original bug is the same as, what appears to me anyway, other bugs with regards to playing videos. I also have the video bug but doubt very much that it is related to the kms booting bug.

finally, i can get rid of that bug…

Laptop : dell inspiron 510m (old one ^^ )

symptoms : neither last 2 kernels, nor the live-cd could boot.

patch : add the i915.modeset=1 in grub command line ; or GRUB_CMDLINE_LINUX_DEFAULT="i915.modeset=1" in /etc/default/grub ( then update-grub required )

plymouth broken.

it works on rhel 6 beta.

why?

tyan s7025
nvidia gtx285 (primary)
ati 5850
hp 3065 display (2560x1600)

nouveau crashes (oops) during boot.

no plymouth.

had to manually add "nomodeset" to boot options to get a working X.

----

adding nvidia drivers do not help.

-----

this broken even in the installer.

how?

I'd just like to add that my Dell x300 machine starts up perfectly (it didn't before), now that I've added i915.modeset=1, just like the original bug report says.

Yeah, it's a boring "me too". But I wanted to weigh in since other bug reports hint that KMS was disabled when it was assumed that a few lucid alpha testers that wanted modeset=0 represented a majority. So this is to balancing the scales :)

00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)

Oh, and super thanks for the great work, all of you!

Dear all,

my bug #580909 has been marked as duplicate, but there is a slight difference: my computer works out-of-the-box until 2.6.32-21 (included), and requires i915.modeset=1 only for 2.6.32-22 .

regards

Just a follow-up on comment #33.

After a few minutes running with modeset=1, xorg crashed, and I'm back to the vesa driver. I've added my xorg.log, in the hope that it may be useful.

On Mon, May 24, 2010 at 7:39 PM, YannUbuntu <email address hidden> wrote:

> Dear all,
>
> my bug #580909 has been marked as duplicate, but there is a slight
> difference: my computer works out-of-the-box until 2.6.32-21 (included),
> and requires i915.modeset=1 only for 2.6.32-22 .
>

According to your bug report, you can boot into 2.6.31-21, which is not the
same as 2.6.32-21. So you are indeed affected by this bug as-is. A common
mistake, no need to worry about it (I missed it at first too).

On Mon, May 24, 2010 at 7:47 PM, Håvard Gulldahl <email address hidden>wrote:

> Just a follow-up on comment #33.
>
> After a few minutes running with modeset=1, xorg crashed, and I'm back
> to the vesa driver. I've added my xorg.log, in the hope that it may be
> useful.

This is indeed the reason why the devs decided to blacklist KMS for the
Lucid release. For workarounds, see this wiki page [1] (ignore Workaround A
in your case obviously). You can follow the progress of the bug you
mentioned above here [2] (please don't post "me too" comments there; the
correct way to "me too" a bug is to edit the "Does this bug affect you too?"
line below the title. This way the affect size can be easily quantified and
also affects the Bug Heat without congesting the comments section).

[1]: https://wiki.ubuntu.com/X/Bugs/Lucidi8xxFreezes
<https://wiki.ubuntu.com/X/Bugs/Lucidi8xxFreezes>[2]:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/541511

I had the same problems (X doesn't start unless i915.modeset=1 & system crash when playing a video with VLC) with a Samsung X05 and an Acer Travelmate 4001LMi.

The first problem was solved this way (in both computers):

 - start with Live CD and i915.modeset=1, install the system, not reset at the end and do:

   - Menu System > Administration > Disk Utility, mount the disk in which we have installed the system,

   $ cd /media/<tab>/etc/default
   $ sudo cp grub grub.bak
   $ sudo pico grub

   - GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.modeset=1"

   $ cd /media/<tab>/boot/grub
   $ sudo cp grub.cfg grub.cfg.bak
   $ sudo pico grub.cfg

   - look for 'quiet splash' and add "i915.modeset=1" at the end (without quotes).

 - reset without CD,
 - update system,
 - update grub:

   $ sudo update-grub

 - reset & done!

The second problem was fixed by upgrading the kernel like explained in:

 - https://wiki.ubuntu.com/X/Bugs/Lucidi8xxFreezes

Another problem with the Acer Travelmate is that it doesn't shut down completely, which is an issue related with another bug.

Hope this could help someone.

Second problem was solved that way in both computers also.

I recently used the latest version of Puppy linux(5.0.1) and encountered the same problem, and got throught by using 'i915.modeset=0' in the boot parameters. So this appears to be a bug in the new kernel source itself.

Marking the Puppy Linux branch as invalid since it is a different bug. This is a bug in UMS (hence i915.modeset=1 workaround), whereas the Puppy Linux bug seems to be a bug in KMS (hence the i915.modeset=0 workaround).

I could boot on live-session (but my mouse did not appear on the screen) with a live-CD of Ubuntu 10.10 beta, so looks like this bug has been solved for me (for my specs see my bug #580909).

@YannUbuntu: Details regarding the missing mouse cursor in 10.10 Beta can be found in Bug #614176.

Solved for me too!

I think my problem is relevant to this. Currently on Lenny 10.04, works out of the box fine on my 855M but updated to backport kernel 2.6.32 to get my wireless card working. Right after I login in from gdm, my desktop image loads, then I get a beep (and a kernel oops, messages attached) and X just stops, with no disk activity. Selecting the old kernel from GRUB works fine. I also tried compiling 2.6.36-rc3 and gives the same problem.

I guess the only difference in my case is that passing i915.modeset=0 or nomodeset seems to make no difference.

    00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
    00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)

Xorg log if it's of any use:

Ed Kyo,

Your bug is a different one. Please file a new bug report using "ubuntu-bug
linux". Thank you.

Apologies, will do.

@Stenten:: I used the 'i915.modeset=0' workaround in Ubuntu because 'i915.modset=1' in the boot parameters wasn't successful. So, I can't be sure whether the Puppy bug is a different one. Correct me if I am wrong. Explanations anyone??

I wonder if anyone tried using the mainline kernel-2.6.32.x and see if it has the bug, or is it the Ubuntu modifications that caused it.

editing the grub menu to include "i915.modeset=1" for the latest ubuntu kernel version "linux-image-2.6.32-24-generic 2.6.32-24.43" still works for me. :)

also i tried the mainline kernel version "2.6.33-02063303-generic 2.6.33-02063303" a while ago (few months) and that's the one i have been using since then. this one boots fine without including "i915.modeset=1" in the grub boot configuration.

hope they are able to fix this in maverick

They already fixed it in Maverick! As of now I am using the Maverick backported kernel(2.6.35-19)! Haven't got any problems so far; works better than 2.6.33 with the `i915.modeset=1 or 0` parameter. I run most games on highest graphics mode.(with the previous kernel doing so would cause the games to cras) So
 just get the Maverick kernel and enjoy Ubuntu!

Maverick is not a LTS. But i agree in that it works now :)

k3lt01, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11.1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

As far I am concerned, I am not competent enough to proeed with these tests.

This bug was reported nearly 3.5 years ago. 10.04 has reached EOL. It was the only version of Ubuntu I had the problem with. I haven't used Ubuntu since 11.10 so I do not know what the newer versions are like with regards to this bug (if it has come back or not). Just as a side note, after leaving Ubuntu for Linux Mint LMDE and then moving to Debian Stable (Lenny, Squeeze and now Wheezy along with running Testing and Sid) I used Squeeze for its entire Stable life and used it while it was testing as well and it never had this problem at all.

It seems to me that this was a bug in Ubuntu (and derivatives) and not in Debian so unless there is a very good reason for Ubuntu to still be using 2.6.32 I won't be testing this after such a time frame has passed by. It seems a pity that it takes 3.5 years to enquire if it has been fixed (especially when posts above from 3.5 years ago show what needed to be done).

I changed for Mint14 last february, now using Mint15.

I thought this bug had been closed.

k3lt01, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/566379/comments/56 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.