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.
SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO
sda: sda1 sda2 < sda5 sda6 sda7 >
sd 0:0:0:0: Attached scsi disk sda
intelfb: Framebuffer driver for Intel(R)
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):
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
Console stays in 80x25 mode.
Console should switch to framebuffer mode.
vesafb works just fine if I just specify vga=0x360
Try loading intelfb after booting with vga=0x360
intelfb: Cannot reserve FB region
(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!
It still happens with Fedora 7 (one of the latest kernels). I haven't upgraded
to 8 on that laptop yet.
Upgraded to F-8, still no change with 18.104.22.168-105.fc8.
Installed F-10snap2 on another laptop, same behaviour.
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:
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:
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.