Bug 483860 - System boots with backlight off
Summary: System boots with backlight off
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 9
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-02-03 23:07 UTC by Ian Romanick
Modified: 2009-07-14 15:54 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-07-14 15:54:23 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ian Romanick 2009-02-03 23:07:42 UTC
Description of problem:

When using Fedora distro kernels, the system boots with the backlight off.  Moreover, the xrandr program is unable to change the backlight brightness.  That is 'xrandr --output LVDS --set BACKLIGHT 20' has no effect.  This *ONLY* happens with the distro kernels.  If I build a kernel from kernel.org or anholt's drm-intel-next kernel, the backlight functions correctly.

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

kernel-2.6.27.12-78.2.8.fc9.x86_64 (but happens with other F9 kernels as well)
xorg-x11-drv-i810-2.5.0-3.fc11.x86_64

How reproducible:

Every time I accidentally boot with a Fedora distro kernel instead of a kernel.org kernel that I built.

Steps to Reproduce:
1. Install distro kernel
2. Boot system
3.
  
Actual results:

Backlight off, unable to adjust.

Expected results:

Backlight on, able to adjust.

Additional info:

The system in question is a Panasonic Toughbook CF-Y7.  The video chipset is:

00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller])
        Subsystem: Matsushita Electric Industrial Co., Ltd. Unknown device 8338
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 16
        Region 0: Memory at fc000000 (64-bit, non-prefetchable) [size=1M]
        Region 2: Memory at 90000000 (64-bit, prefetchable) [size=256M]
        Region 4: I/O ports at 1800 [size=8]
        Capabilities: <access denied>
        Kernel modules: i915, intelfb

Comment 1 Bug Zapper 2009-06-10 03:31:57 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  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 '9'.

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 9'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 9 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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Bug Zapper 2009-07-14 15:54:23 UTC
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 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.