[Bug 55311] Since 3.7.1-17.1 radeon has no backlight when using vgaswitcheroo (regression)
bugzilla-daemon at bugzilla.kernel.org
bugzilla-daemon at bugzilla.kernel.org
Mon Oct 28 13:07:07 CET 2013
https://bugzilla.kernel.org/show_bug.cgi?id=55311
--- Comment #74 from Jani Nikula <jani.nikula at intel.com> ---
(In reply to Nikolay Amiantov from comment #73)
> I have hybrid ATI 5650/Intel Ironlake muxed system, and when I switch to
> radeon, backlight stays enabled now (looks like it was fixed by patch from
> that bug), but I can't change in at all, and it is down when I do suspend
> cycle.
> lspci -vv:
> ...
> 00:02.0 VGA compatible controller: Intel Corporation Core Processor
> Integrated Graphics Controller (rev 18) (prog-if 00 [VGA controller])
> Subsystem: Acer Incorporated [ALI] Device 0359
> 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 45
> Region 0: Memory at d8000000 (64-bit, non-prefetchable) [size=4M]
> Region 2: Memory at c0000000 (64-bit, prefetchable) [size=256M]
> Region 4: I/O ports at 4050 [size=8]
> Expansion ROM at <unassigned> [disabled]
> Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
> Address: fee0f00c Data: 4122
> Capabilities: [d0] Power Management version 2
> Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
> Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
> Capabilities: [a4] PCI Advanced Features
> AFCap: TP+ FLR+
> AFCtrl: FLR-
> AFStatus: TP-
> Kernel driver in use: i915
> Kernel modules: i915
> 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
> Madison [Mobility Radeon HD 5650/5750 / 6530M/6550M] (rev ff) (prog-if ff)
> !!! Unknown header type 7f
> Kernel driver in use: radeon
> Kernel modules: radeon
> ...
> ls /sys/class/backlight:
> acpi_video0 acpi_video1 intel_backlight
> Neither of them work. What can I do to help tracing this bug further? Should
> I open another one?
Please open a new bug.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the intel-gfx-bugs
mailing list