"Failed to restore crtc configuration: -22" on i915

Bug #404421 reported by dwmattisoncv on 2009-07-25
78
This bug affects 14 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Unassigned

Bug Description

With Ubuntu 9.10/karmic on Samsung Q1U which have a VGA output, Xorg doesn't start:

[drm:intelfb_restore] *ERROR* Failed to restore crtc configuration: -22

Workaround:
Add i915.modeset=0 to the kernel cmdline args

dwmattisoncv (dwmattisoncv) wrote :
dwmattisoncv (dwmattisoncv) wrote :
dwmattisoncv (dwmattisoncv) wrote :
Lloyd Miller (millerlf) wrote :

I get this same message on MSI 945GM3 motherboard.

[drm:intelfb_restore] *ERROR* Failed to restore crtc configuration: -22

lspci gives:
00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)

I have a Samsung Syncmaster 700b CRT attached.

CPU is Intel Pentium D 920.

I was trying to boot the Kubuntu karmic AMD64 desktop CD Alpha 4.

I can login text mode if you need log files.

It all works fine for ubuntu 8.04.3 that I am using now.

CyrusCT (cyrusct) wrote :

I also have this problem, but I'm using a Samsung Q1 Ultra.

I get the problem when I upgrade to Karmic 9.10 from regular ubuntu, from ubuntu netbook remix 9.04, and from xubuntu 9.04 32-bit versions in each case. I also get the problem when trying to do a fresh install of Karmic 9.10 with Wubi, even if I specify safe graphics mode during the first run. I have noticed this with alpha 4 and alpha 5. I can't remeber if alpha 3 worked or not, but I did not have this problem with alpha 1 or alpha 2.

Loïc Minier (lool) wrote :

I have the same issue on Samsung Q1U on today's karmic daily

affects: ubuntu → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: New → Confirmed
Loïc Minier (lool) wrote :

Found a patch googling for this bug:
http://patchwork.kernel.org/patch/43807/

Seems to apply to the karmic linux tree still.

Loïc Minier (lool) wrote :

I built this kernel with the patch on top of the karmic source package; can anybody test it? I cant easily install it myself nor put it in a live environment since the kernel aufs driver oopses for me with a rw path

thanks!

Papfox (paul-stimpsonfamily) wrote :

I'm seeing the same problem on an IBM/Lenovo Thinkcentre M52 (Model 9210-KGB) small form factor desktop with an LG L1800P monitor attached to a Belkin 4-port ps/2 KVM.

Original description: Based on 9210-D1U: Intel® Pentium® 4 Processor 630 with HT Technology, 512MB, 80GB 7200RPM S-ATA HDD, PCI/PCIe Small Form Factor (2x3), Intel Graphics Media Accelerator 950, 16x DVD-ROM, Intel Gigabit Ethernet, POV.

It says the GPU is an Intel 950 but Karmic identifies it as an 82945 so I think I see a pattern forming.

I don't know if it's relevant but I have got a problem with Jaunty on this machine too. It worked fine when I installed it but now (after a full set of updates) it comes up offering me low graphics mode saying that there are no modes available then says display :0 is busy and has to open a display on :1.

Loïc Minier (lool) on 2009-10-24
tags: added: regression-release
description: updated
description: updated
Sensiva (sensiva) wrote :

I tried Release Candidate amd64 and I see the same message.

My PC is Dell Desktop Optiplex 755 Core2duo 2.6Ghz 8GB RAM Intel 82Q35 VGA chipset
I couldn't drop to single user mode to collect any info, and recovery mode shows the text on screen messed up randomly

Sensiva (sensiva) wrote :

I tried the workaround mentioned in the first post

"Add i915.modeset=0 to the kernel cmdline args"

The msg disappeared , yet Xorg didn't start, and the monitor went to sleep mode, pressing CTRL+ALT+DEL rebooted the system, I saw upstart msgs of unmounting and stopping services ...etc which means it was still up, but there was no video

Sensiva (sensiva) wrote :

I tried daily build of AlternativeCD 27th of Oct. the same error came up and repeated for 5 seconds and then Xorg started with full acceleration, but didn't detect all my screen resolutions, only 800x600@60Hz. I am using Hewlett Packard Monitor 20inch model : hp p 1230.

manu (eallaud-gmail) wrote :

I have a similar problem with a G33: boot begins normally and at some point it is in text mode and (I think) flickers a lot with the error message: failed to restore crtc configuration -22. I was able to switch between text consoles (I could see the ttyX and login prompt briefly) and finally by playing between consoles it finally decided to start xorg (it might be completely unrelated though).
I attach the dmesg if it can help.

manu (eallaud-gmail) wrote :

I have a similar problem with a G33: boot begins normally and at some point it is in text mode and (I think) flickers a lot with the error message: failed to restore crtc configuration -22. I was able to switch between text consoles (I could see the ttyX and login prompt briefly) and finally by playing between consoles it finally decided to start xorg (it might be completely unrelated though).
I attach the dmesg if it can help.

I first noticed it on a Samsung Q1 Ultra when trying to upgrade a Wubi
9.04 install to a 9.10 alpha. I figured the problem would be fixed by
the final release, but I am having this problem with a fresh Wubi 9.10
install. After usplash, the screen keeps flashing with

[drm:intelfb_restore] *ERROR* Failed to restore crtc configuration: -22

until inactivity makes the screen go blank.

I would like to apply the i915.modeset=0 workaround.

Can you please indicate how, and where to enter the workaround?

I tried pressing the <e> key in grub, and adding a new line with
"i915.modeset=0" and then using <Ctrl> + <x> key combination to boot,
but I'm still getting the problem, so apparently this does not cause
grub to pass the command to the kernel.

Can someone please tell me where I went wrong and what I should be doing
differently?

Many thanks,

Chris

Loïc Minier wrote:
> ** Tags added: regression-release
>
> ** Description changed:
>
> Updated the system to Ubuntu karmic (9.10), now XWindows will not start
> and I get the error:
>
> [drm:intelfb_restore] *ERROR* Failed to restore crtc configuration: -22
>
> Did a search for this error on google and I cannot find anything online
> to fix the problem.
> +
> + Workaround:
> + Add i915.modeset=0 to the kernel cmdline args
>
> ** Description changed:
>
> - Updated the system to Ubuntu karmic (9.10), now XWindows will not start
> - and I get the error:
> + With Ubuntu 9.10/karmic on Samsung Q1U which have a VGA output, Xorg
> + doesn't start:
>
> [drm:intelfb_restore] *ERROR* Failed to restore crtc configuration: -22
>
> - Did a search for this error on google and I cannot find anything online
> - to fix the problem.
> -
> Workaround:
> Add i915.modeset=0 to the kernel cmdline args
>
>

Loïc Minier (lool) wrote :

In the GRUB menu ('e' to edit the entry on boot), add the flag I mention to the linux kernel cmdline, that is where you see "splash quiet".

On your system, edit /boo/grub/menu.lst and read the instructions. If you're using GRUB 2 (unlikely), see /etc/default/grub instead.

Sensiva (sensiva) wrote :

the kernel line in grub.cfg should look like this
linux /boot/vmlinuz-2.6.31-14-generic root=UUID=9f9d42ff-xxxx-xxxx-adc1-afe1axxx1e4a i915.modeset=0 ro splash

and in menu.lst
kernel /boot/vmlinuz-2.6.31-14-generic root=UUID=9f9d42ff-xxxx-xxxx-adc1-afe1axxx1e4a i915.modeset=0 ro splash

CyrusCT (cyrusct) wrote :

Thank you, thank you, thank you!

I was finally able to finish startup.

In the GRUB 2 menu, I pressed the <e> key to edit, used the arrow keys
to move the cursor to the line that ended with "quiet splash" and
changed it to end with "i915.modeset=0 quiet splash" then pressed the
<Ctrl> + <x> key combination to boot.

To make the changes persistent, I modified /etc/default/grub

by changing the line:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

to:

GRUB_CMDLINE_LINUX_DEFAULT="i915.modeset=0 quiet splash"

then saved and ran the command "sudo update-grub" to implement the changes.

Thanks again,

Chris

Loïc Minier wrote:
> In the GRUB menu ('e' to edit the entry on boot), add the flag I mention
> to the linux kernel cmdline, that is where you see "splash quiet".
>
> On your system, edit /boo/grub/menu.lst and read the instructions. If
> you're using GRUB 2 (unlikely), see /etc/default/grub instead.
>
>

Changed in linux (Ubuntu):
status: Confirmed → Triaged
MortenFT (mortenft) wrote :

I'm getting the same error when trying to install Ubuntu 9.10 - it happens on the desktop and the netbook remix edition.

I am trying to test ubuntu from a USB stick, and I have never done it before. Therefore, what you guys have written here is completely unintelligable for me. I know my way around computers, just not Linux/Ubuntu - so, if anyone could walk me through this step-by-step I would very much appreciate it.

Thx
MortenFT

Loïc Minier (lool) wrote :

@MorfenFT: on a live USB key, type the i915.modeset=0 on the kernel cmdline which you can edit with F6 on the first menu (after choosing language)

ulugeyik (durduran) wrote :

I have the same exact problem on Samsung Q1U using netbook remix, 9.10. i915.modeset=0 on the kernel cmdline works with live USB.

Andy Whitcroft (apw) wrote :

Has anyone been able to test the kernel which Loic posted in comment #9 ? Any reports on that kernel would be very helpful.

AnSc (spam2-anschitech) wrote :

I did not test the kernel.
But I can confirm the problem.
My PC is a Lenovo ThinkCentre M55 with a "Intel Q965/Q963 Express Chipset Family" graphic processor (reported by windows).
9.04 did fine with this PC but since the update to 9.10 the maschine is useless with Ubuntu.
I am very disappointed and am considering changing to an other distribution.
Even the LiveCDs do not run(32 bit and 64 bit version tested).

AnSc (spam2-anschitech) wrote :

Today I did test the kernel.
Did make no difference (my installation of 9.10 came with kernel 2.6.31-14...).

AnSc (spam2-anschitech) wrote :

Attached is a Xorg log. It seems to me, that the driver can't detect the monitor that is connected to the DVI port of my graphics card.
Btw: I think in 9.04 I had the problem that the monitor was not detected (properly). But I could set it to the right resolution via xrandr.

Same problem on a Samsung Q1 ultra, after upgrading from 9.04 to 9.10 (yep, maybe I should have waited). i915.modeset=0 did NOT work for me.

But adding nomodeset into the boot options worked. This disables Kernel Mode Setting, i.e. video mode switching from the kernel. Clearly the KMS is still rough. I had also problems with another GM945 based laptop (external monitor could not be turned on). At least the X11 in 9.10 still works without KMS (not true for the latest ppa xorg-edgers!).

AnSc (spam2-anschitech) wrote :

I also tried the nomodeset as a boot option but that did NOT work for me.
I wonder why the monitor and/or graphics card is not detected properly.
When I run ddcprobe on the console the graphics card and the monitor is identified (see attached file).

Tyler Crenshaw (tdcrenshaw) wrote :

add vga=792 to the kernel setting line.
also see <a href="https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/467841">Bug #467841</a>

AnSc (spam2-anschitech) wrote :

Adding vga=792 to the boot options did make no difference. Problem _not_ solved.

The mentioned bug #467841 contains a patch in comment #14 from manu (https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/467841/comments/14).

How could I test this patch?
Did anyone test this patch?

manu (eallaud-gmail) wrote :

Well if you know how to compile and prepare a compiled kernel to be booted with grub I can send you another patch to try out.

AnSc (spam2-anschitech) wrote :

I tried and build the kernel according to that documentation http://www.howtoforge.com/kernel_compilation_ubuntu.
After booting that kernel I got the same errors(flickering screen, failed to restore... messages).
So that did not solve my problem.

AnSc (spam2-anschitech) wrote :

Today I installed a AMD HD4350 graphics card in my system.
The X started and showed a screen. The driver also reports the monitor correctly.
So I guess the problem is with the xserver-xorg-video-intel driver that does not detect the monitor correctly.

Could any one say where this would be better reported?

tags: added: karmic
kelchy (kelchy) wrote :

i also experienced this on an MSI Wind Nettop.
was able to boot usb installer by appending both vga=792 and i915.modeset=0
i have tried using modeset alone, doesn't work, so i tried both.
maybe vga=792 alone is sufficient, but haven't tried it yet.

Reynold Joseph (rnldpj) wrote :

I too have encountered the same problem in my desktop PC running Kubuntu 9.10 ,
 everything was working fine and suddenly on one day I got the error saying
"failed to restore crtc configuration -22" and then drove me to the console login .

When I tried to boot using an Ubuntu 9.10 live CD , then also the same error appears , but now I'm not even getting the console login, instead the error appears on all consoles ........

I'm getting the GUI login when the "safe graphics mode" is selected in Ubuntu 9.10 live CD .

There is no /dev/fb0 (framebuffer device) in my system when running in the "safe graphics mode" ...........

The error might be caused due to some erroneous "/etc/X11/xorg.conf" file .

Reynold Joseph (rnldpj) wrote :

I've encountered a similar error problem on Ubuntu 9.04 and it got solved when the
acpi was turned on in the mother board settings....

Ramaddan (ramaddan) wrote :

Hi,

I have the same problem with intel i810, and get the "failed to restore crtc configuration -22" errors as well as having to go into safe graphic mode.

Just downloaded 9.10 after a 2 year hiatus, thought I would give this version a try, but upon install onto a Samsung Q1 Ultra, I get this error. [drm:intelfb_restore] *ERROR* Failed to restore crtc configuration: -22

Is there anybody who can give me STEP BY STEP instructions on how to fix this?

Loïc Minier (lool) wrote :

@Jason: from a live CD, type F6 on the boot screen to select advanced options, change the kernel cmdline to add i915.modeset=0 after "--", so if it was e.g.:
... boot=casper --
change it to:
... boot=casper -- i915.modeset=0

that should be preserved upon install

I don't have a keyboard. I am installing this on a Samsung Q1 Ultra and it does not have the function keys.

----- Original Message ----
From: Loïc Minier <email address hidden>
To: <email address hidden>
Sent: Sun, February 28, 2010 12:21:44 PM
Subject: [Bug 404421] Re: "Failed to restore crtc configuration: -22" on i915

@Jason: from a live CD, type F6 on the boot screen to select advanced options, change the kernel cmdline to add i915.modeset=0 after "--", so if it was e.g.:
... boot=casper --
change it to:
... boot=casper -- i915.modeset=0

that should be preserved upon install

--
"Failed to restore crtc configuration: -22" on i915
https://bugs.launchpad.net/bugs/404421
You received this bug notification because you are a direct subscriber
of the bug.

Status in “linux” package in Ubuntu: Triaged

Bug description:
With Ubuntu 9.10/karmic on Samsung Q1U which have a VGA output, Xorg doesn't start:

[drm:intelfb_restore] *ERROR* Failed to restore crtc configuration: -22

Workaround:
Add i915.modeset=0 to the kernel cmdline args

To unsubscribe from this bug, go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/404421/+subscribe

Loïc Minier (lool) wrote :

Connect an USB keyboard, or if you're booting from USB, edit syslinux.cfg, the options should be on the append line.

I'm booting from USB. In Windows, I opened the USB drive, then I opened the syslinux folder, the oped the file syslinux.cfg with notepad, and what is written is exactly as follows:

include menu.cfg
default vesamenu.c32
prompt 0
timeout 300
gfxboot bootlogo

So where do I enter that "boot=casper -- i915.modeset=0" part?

So I made a little more progress.

In that syslinux folder, there is a file called text.cfg. I opened that file with notepad, and found some lines which looked similar to what you described. In the first 2 instances where I saw the "boot=casper", I highlighted the "casper" part and pasted "casper -- i915.modeset=0" and then saved the file. (Just to note, only the Fedora LiveUSB creator worked https://help.ubuntu.com/community/Installation/FromUSBStick . Other USB programs produced what seemed like an identical set of files on my USB, including the USB creator included in the .iso itself, but only the Fedora one makes this work for me.)

And this almost worked. I booted once again from the USB, chose the 2nd option, which was to install (first option was to just run the system off of the USB), and it progressed fully through the installation procedure, all the way through to the final reboot, upon which I was prompted to remove the USB. I did, and the system booted from what I had installed on the hard drive. But during the boot process, the same problem. The change was not maintained in the installation.

Now, I am running just the live USB, and will try the installation option from the Ubuntu desktop itself instead of the installation directly from the USB. I will post again if doing it this way will work.

But if that does not work, please tell me where I can find that text.cfg file on the fully installed system. This way, I could run from the USB, and then browse through the files on the hard drive and edit the file that way.

Nope, that didn't work. But progress as I can at least get it to run from the USB, however extremely slowly.

So what next?

Loïc Minier (lool) wrote :

I think the args from the boot cmdline are supposed to be copied on the installed system, either the ones before "--" or the ones afterwards.

The installed system probably uses grub2 which you can configure in /etc/default/grub; run update-grub to update the /boot/grub/grub.cfg generated file

Didn't see anything that looked relevant in the grub.cfg :-(

Well, I think I have to throw in the towel on this one. It's pretty frustrating. On the one hand, the UI in Ubuntu is far superior to that found in Windows or Mac for that matter. On the other hand, each time I try to switch to some Linux distro....each and every single time issues like this come up forcing me to stay with Windows :-( If it's not the touchscreen, it's the fingerprint reader, and if not that then it's the 3G GSM connectivity, if not that something else. How is it that the guys at Microsoft can at least get their system to work?

I'm not happy to stay with Windows, but I spent the entire weekend trying to get this f'ing thing installed and no dice:-(

Thank you for your help, but I think this is a hopeless battle. Once this PC dies off, I'm getting a Mac.

:-)

OK, OK, I made a bit more progress. I found the following https://help.ubuntu.com/community/Grub2 , which tells me to edit the grub options, I should hold down the shift key from the time I start the system until the time the grub command line appears. And I did this using the system installed on the hard drive which wouldn't go before.

So it did as pictured in that website, and I highlighted the first option on the list shown, and pressed the e key which took me to a screen to edit text or options for that item.

After the "ro quiet splash" I added "i915.modeset=0", or in other words, after my addition, that part looked like "ro quiet splash i915.modeset=0" .

Then, I pressed control x which booted the system.....and it worked. But, I must do this each time I start up the system. So how do I get this to be permanent?

So apparently some critical part of this computers graphics processing power has been hamstrung by this workaround. Sure, it boots, but it is so slow the system is essentially impossible to use.

Loïc Minier (lool) wrote :

To make it the default, edit /etc/default/grub and add the options to GRUB_CMDLINE_LINUX_DEFAULT= and GRUB_CMDLINE_LINUX= then run update-grub.

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers