failed to get i915 symbols, graphics turbo disabled error on boot

[raif1]

What I did.

As the previous post, in /etc/modprobe.d/blacklist.conf, add the line "blacklist intel_ips"

and edit /etc/rc.local , just before line exit 0, add the line "modprobe intel_ips".

When I reboot, the message about turbo graphics disabled was gone, and when I do lsmod | grep intel_ips, the module intel_ips is loaded.

So, the question remains, does this mean the turbo graphics is enabled ?

[greybot]

I have a core i3 processor in my laptop and also get this message. According to the spec of the processor it doesn't support turbo mode, whereas the i5 and i7 do, which would warrant the warning that it isn't enabled. However some people on here are encountering the error with i5 processors, which means this still needs fixing.

[ivt13]

Long time reader, first time poster.

I'm using a Lenovo X201 w/ Core i5, Ubuntu 10.10

Initially I was running 10.04 and did the upgrade. That gave me the problem described in this thread. I also could not have any "eye candy."

What I did was I reinstalled 10.10 completely (reformat etc) and now I have all the visual effects enabled. I still get that error message sometimes, but its not such a big problem anymore.

I hope that helps.

[greybot]

Can anyone confirm if this bug is still present with first version of 2.6.38 kernel?

[nils-79]

Hi,

there are a plenty of other problems related to this intel graphic card.
One of those is - for example - a bug in the linux kernel which makes
dual head impossible. I tried different versions of the linux kernel 2.6.37 (even
in the rc state) to get dual head working.

It sounds strange but after installing the latest stable kernel 2.6.37
booting into X is sometimes possible, sometimes not. In the worst case
I have to reboot my machine several times until the X server is displayed.

However, after installing the latest stable kernel the error message
(failed to get ...) still exists. Anyway, the dual head problem is solved
and I'm now going to install the latest GIT kernel on my laptop.

As far as I know they implemented some changes in the 2.6.38 kernel
related to this graphic chipset. Due to a slow internet link,
dowloading the kernel sources will take a while

I'll post my results on here. Let's pray that some of these bugs are fixed ... ... ,
it's so time consuming to troubleshoot these kind of problems.

Nils

[nils-79]

I compiled the new 2.6.38 rc2 kernel .... and .... problem does still exist.
It seems some drivers from intel are missing to enable graphic turbo.

However ... it seems the x-server is more stable while running the new kernel.
I booted several times and no problems regarding performance or stability
could be detected.

[JeanVW14]

+1 for the prob.. Had to reinstall to get 3d graphics enabled and it's working now, but still have the 'i915' and 'turbo failed' at boot, which is in oversized crappy plaintext (?!?)

Is this just a 'hurry up and wait' for the kernel to fix it?

[ralzes]

i was cheking this post and it seems to be post along time ago... is already a solution for this problem? i install kubuntu 10.10 and delete all trace of windows... tried to enter by doing the nomodeset but i can´t change the blacklist thing... i´m noob on al this thing, can anyone explain to me how can i do that without seen anithing more than the root? help please! (sorry i´m not an english natural speaker.. =S)

[kongstad]

@ralzes:

Open a terminal and type this:

sudo sh -c "echo blacklist intel_ips >> /etc/modprobe.d/blacklist.conf"

You will be asked for your password, enter it, and you have fixed the blacklist file

The sudo command executes the following shell with root permissions.

This should remove the error on startup.

If you want more control then use this command:

gksudo gedit /etc/modprobe.d/blacklist.conf

This opens the file in the text editor with root permissions.

Then add
blacklist intel_ips
tot he end of the file

[wujastyk]

But does blacklisting intel_ips allow Turbo mode. I think not. Nor does the i915 graphics driver seem to work. The blacklisting of intel_ips avoids the error message, but doesn't solve the problem.

Or am I wrong?

Dominik