Bug 234382 - intelfb cannot be used for local flat panel (laptop)
Summary: intelfb cannot be used for local flat panel (laptop)
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 10
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Brian Brock
Depends On:
Blocks: 427887
TreeView+ depends on / blocked
Reported: 2007-03-28 19:57 UTC by Dominik 'Rathann' Mierzejewski
Modified: 2009-12-18 05:54 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-12-18 05:54:59 UTC
Type: ---

Attachments (Terms of Use)

Description Dominik 'Rathann' Mierzejewski 2007-03-28 19:57:45 UTC
Description of problem:
I'd like to use intelfb instead of vesafb for a big console.
After adding MODULES=intelfb to /etc/sysconfig/mkinitrd as suggested on
#fedora-devel and rebuilding the initrd I thought it would just work.
It didn't. I tried adding video=intelfb:mode=1280x800 no change.
Kernel output:

SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO
or FUA
 sda: sda1 sda2 < sda5 sda6 sda7 >
sd 0:0:0:0: Attached scsi disk sda
intelfb: Framebuffer driver for Intel(R)
830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM chipsets
intelfb: Version 0.9.4
ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 17
intelfb: 00:02.0: Intel(R) 945GM, aperture size 256MB, stolen memory 7932kB
intelfb: Non-CRT device is enabled ( LVDS port ).  Disabling mode switching.
intelfb: Video mode must be programmed at boot time.
kjournald starting.  Commit interval 5 seconds

My guess is that unless it's compiled-in, the proper mode won't get initialized.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. echo MODULES=intelfb >> /etc/sysconfig/mkinitrd
2. mkinitrd /boot/initrd.new `uname -r`
3. edit /etc/grub.conf to use the new initrd
4. reboot

Actual results:
Console stays in 80x25 mode.

Expected results:
Console should switch to framebuffer mode.

Additional info:
vesafb works just fine if I just specify vga=0x360

Comment 1 Chuck Ebbert 2007-03-28 20:16:14 UTC
Try loading intelfb after booting with vga=0x360

Comment 2 Dominik 'Rathann' Mierzejewski 2007-03-28 22:11:42 UTC

intelfb: Cannot reserve FB region

Comment 3 Jon Stanley 2008-01-08 01:53:25 UTC
(This is a mass-update to all current FC6 kernel bugs in NEW state)


I'm reviewing this bug list as part of the kernel bug triage project, an attempt
to isolate current bugs in the Fedora kernel.


I am CC'ing myself to this bug, however this version of Fedora is no longer

Please attempt to reproduce this bug with a current version of Fedora (presently
Fedora 8). If the bug no longer exists, please close the bug or I'll do so in a
few days if there is no further information lodged.

Thanks for using Fedora!

Comment 4 Dominik 'Rathann' Mierzejewski 2008-01-08 16:46:50 UTC
It still happens with Fedora 7 (one of the latest kernels). I haven't upgraded
to 8 on that laptop yet.

Comment 5 Dominik 'Rathann' Mierzejewski 2008-01-17 11:06:41 UTC
Upgraded to F-8, still no change with

Comment 6 Dominik 'Rathann' Mierzejewski 2008-11-03 20:03:20 UTC
Installed F-10snap2 on another laptop, same behaviour.

Comment 7 Bug Zapper 2008-11-26 01:53:08 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:

Comment 8 Bug Zapper 2009-11-18 12:19:02 UTC
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 9 Bug Zapper 2009-12-18 05:54:59 UTC
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.