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 -- Intelfb completely b0rken https://bugs.launchpad.net/bugs/147606 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
