Intelfb completely b0rken

Addendum: Trying VESA gives the following:

peter@klapprechner~> dmesg|grep fb
[ 0.000000] Kernel command line: root=/dev/sda3 ro video=vesafb splash vga=0x31b

[CPU stuff]

[ 1.364000] vesafb: framebuffer at 0xd0000000, mapped to 0xf8880000, using 7872k, total 7872k
[ 1.364000] vesafb: mode is 1280x1024x32, linelength=5120, pages=0
[ 1.364000] vesafb: protected mode interface info at 00ff:44f0
[ 1.364000] vesafb: scrolling: redraw
[ 1.364000] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[ 1.364000] fb0: VESA VGA frame buffer device

leaving me with a garbled console as well.

Bootup with hires splash looks OK, but no console at all.

Same problem on 845G. 80x25 is horrible. Please fix this ASAP.

After a long testing session I managed to enable intelfb at boot time. These are the requirements:

1. remove intelfb from /etc/modprobe.d/blacklist-framebuffer
2. add fbcon to /etc/initramfs-tools/modules
3. add intel_agp and intelfb into /etc/initramfs-tools/modules, in THIS order (because intelfb is missing the dependency to intel_agp)
4. do NOT add vesafb to /etc/initramfs-tools/modules, remove it if it is there. vesafb tends to pre-empt intelfb
5. Add these two options to your kernel loading (grub) : video=intelfb vga=0x317, in THIS order (this is mentionned in kernel Documentation/fb/intelfb.txt).
6. rebuild initramfs image using update-initramfs

Any other combination missing only ONE of these requirements (I tried many of them) is likely to give one of the following results:
- blank tty screens
- ugly resolution, corrupted as soon as X is started
- cryptic "cannot acquire agp" kernel messages
- in the best cases, vesafb running

It seems intelfb developers do REALLY want to avoid users testing their code.

Useful debugging tips:
- dmesg | grep fb
- cd newdir; zcat /boot/initrd.img-2.6.22-14-generic | cpio -i

Related:
- intel console framebuffer (i810fb or intelfb) does not work
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=398948
- Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/129910
- vesafb sets the refresh rate too high for some LCDs
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/127168

In some configurations it is even needed to blacklist vesafb. vesafb pre-empts/disturbs intelfb.

I stop using intelfb since it tends to freezes hibernate/resume. Hitting the keyboard tends to unfreeze but it's not really convenient. vesafb hibernates fine (gutsy 2.6.22-14-generic)

Still, people not interested by hibernation or simply wanting to test intelfb should have their life made much easier.

Ignore my above comment about intelfb and hibernate. Intelfb hibernates fine. The hibernate issue was unrelated to intelfb. Sorry for the noise.

Thank you for taking the time to report this bug and helping to make Ubuntu better. The Hardy Heron Alpha series was recently released. Alpha2 and subsequent releases contain an updated version of the kernel. You can download and try the new Hardy Heron Alpha release from http://cdimage.ubuntu.com/releases/hardy/ . Please note that Alpha3 will be released within the next day or two so you may want to wait. You should be able to then test the new kernel via the LiveCD. If you can, please verify if this bug still exists or not and report back your results. General information regarding the release can also be found here: http://www.ubuntu.com/testing/ .

I've opened a new task against the actively developed kernel and am closing the task against linux-source-2.6.22. Thanks!

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

I have similar problems in Kubuntu intrepid:

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu intrepid (development branch)
Release: 8.10
Codename: intrepid
$ uname -a
Linux galar3 2.6.27-3-generic #1 SMP Wed Sep 10 16:02:00 UTC 2008 i686 GNU/Linux

The graphics card is an Intel 965GM; the relevant part of lscpi is as follows:

00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03)

Booting with "video=intelfb:mode=1280x800-16@60,accel,hwcursor" as suggested in the intelfb documentation gives the following:

$ dmesg | grep intelfb
Sep 13 01:04:45 galar3 kernel: [ 1.887112] intelfb: Framebuffer driver for Intel(R) 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets
Sep 13 01:04:45 kernel: [ 1.887177] intelfb: Version 0.9.5
Sep 13 01:04:45 kernel: [ 1.887274] intelfb 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Sep 13 01:04:45 kernel: [ 1.887330] intelfb: 00:02.0: Intel(R) 965GM, aperture size 256MB, stolen memory 7932kB
Sep 13 01:04:45 kernel: [ 1.887392] intelfb: cannot acquire agp

Loading the intelfb module after boot up gives the following:

$ sudo rmmod intelfb
$ sudo modprobe intelfb mode=1280x800-16 accel=1 hwcursor=1
Sep 13 01:46:14 galar3 kernel: [ 729.428154] intelfb: Framebuffer driver for Intel(R) 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets
Sep 13 01:46:14 kernel: [ 729.428171] intelfb: Version 0.9.5
Sep 13 01:46:14 kernel: [ 729.428269] intelfb: 00:02.0: Intel(R) 965GM, aperture size 256MB, stolen memory 7932kB
Sep 13 01:46:14 kernel: [ 729.436525] intelfb: Non-CRT device is enabled ( LVDS port ). Disabling mode switching.
Sep 13 01:46:14 kernel: [ 729.436552] intelfb: Video mode must be programmed at boot time.

Also, the uvesafb fails miserably, trying "video=uvesafb:1280x800-16@60" at boot gives " uvesafb: Unknown parameter `mode'". modinfo uvesafb gives the correct parameter name as "mode_option", so next boot is with "video=uvesafb:mode_option=1280x800-16@60"; which gives:

Sep 13 02:22:24 kernel: [ 6.896009] uvesafb: Getting VBE info block failed (eax=0x4f00, err=1)
Sep 13 02:22:24 kernel: [ 6.896063] uvesafb: vbe_init() failed with -22
Sep 13 02:22:24 kernel: [ 6.896113] uvesafb: probe of uvesafb.0 failed with error -22

Also, the helper v86d is in the initram used by this kernel:

$ zcat /boot/initrd.img-2.6.27-3-generic | cpio -t | grep v86d
sbin/v86d

If any more information is required I'd be happy to provide it.

This says all !
(please read what you post...) :

Sep 13 01:46:14 kernel: [ 729.436525] intelfb: Non-CRT device is enabled ( LVDS port ). Disabling mode switching.
Sep 13 01:46:14 kernel: [ 729.436552] intelfb: Video mode must be programmed at boot time.

1. intelfb can not currently switch video modes on non-CRT devices (id est on laptop screens)
2. so, you have to fix the desired video mode into your video-card bios

Ben: that's wrong (please read what other people posts...) :

Austriaco did two attempts.

The first attempt was to load the configuration from grub, by using the module loaded into the initramfs.
In that case he didn't get this kind of message. He had another kind of error (cannot acquire agp)

The second attempt was to change the configuration on the fly. In that case he got the message: "Video mode must be programmed at boot time." .... but this is almost known behaviour (it also happens with vesafb), and it has nothing to do video-card bios settings.

cheers

Unfortunately it seems this bug is still an issue. Can you confirm this issue exists with the most recent Jaunty Jackalope 9.04 release - http://www.ubuntu.com/news/ubuntu-9.04-desktop . Please let us know your results. Thanks.

Kernel modestting is now available in Karmic Koala, it fixes your issue as I was blaming intelfb as well. KMS makes it irrelevant.

On Sunday 07 June 2009 23:42:19 luke.varnadore wrote:
> Kernel modestting is now available in Karmic Koala, it fixes your issue
> as I was blaming intelfb as well. KMS makes it irrelevant.

Intel has made itself irrelevant for me. KMS works fine on my new T60p with a
FireGL V5200.

Closing per last sets of comments.

Not sure if this is the same issue still or something new(wer).

When I try to boot the Kubuntu Karmic alpha 4 AMD64 desktop CD I get a text mode login screen. It had simple graphics up for the blue progress bar but can't seem to regain graphics mode. After a minute it sez:

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

I have a MSI 945GM3 motherboard. lspci shows:

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

It works on ubuntu 8.10 ok (running it now). I think it fails also on 9.04.