Bug 737108 - Backlight on Samsung N127 laptop blinks after update to kernel-2.6.40.3
Summary: Backlight on Samsung N127 laptop blinks after update to kernel-2.6.40.3
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: i686
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-09 16:11 UTC by Kirin Yuri
Modified: 2011-11-17 23:28 UTC (History)
7 users (show)

Fixed In Version: kernel-2.6.41.1-1.fc15
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-17 23:28:36 UTC


Attachments (Terms of Use)

Description Kirin Yuri 2011-09-09 16:11:32 UTC
Description of problem:
After update to kernel-2.6.40.3-0.fc15.i686 a backlight of my laptop Samsung N127 starts to blink after authorization in KDM. Difference between nice-working kernel-2.6.40-4.fc15.i686 and kernel-2.6.40.3-0.fc15.i686 is samsung_laptop kernel module. /var/log/messages is full off:
"samsung_laptop: SABI set command 0x01 failed with completion flag 0xaa and data 0xff"

Version-Release number of selected component (if applicable):
kernel-2.6.40.4-5.fc15.i686
kernel-2.6.40.3-0.fc15.i686

How reproducible:
Every boot.

Steps to Reproduce:
1. Get Samsung N127 laptop
2. Install Fedora 15 and update kernel to kernel-2.6.40.3
3. Install KDE and log into KDM.
  
Actual results:
Backlight starts to blink few times in a second. After a some time it stops, but starts again after manual brightness regulation.

Expected results:
Backlight not blinks.

Comment 1 Tomasz Chmielewski 2011-09-13 12:16:42 UTC
I see exactly the same behaviour (blinking) on Samsung N130.

Comment 2 Chuck Ebbert 2011-09-14 10:05:51 UTC
The fix for this seems to have fallen into a black hole:

https://lkml.org/lkml/2011/4/20/1
https://lkml.org/lkml/2011/5/11/548

Comment 3 Chuck Ebbert 2011-10-25 01:39:16 UTC
See:
https://bugzilla.redhat.com/show_bug.cgi?id=747560#c3

for some possible workarounds.

Comment 4 Chuck Ebbert 2011-10-25 02:42:18 UTC
Patch from comment 2 has been applied to the f15 kernel and should be in the next update (probably 2.6.40.8).

Comment 5 Fedora Update System 2011-10-27 14:12:40 UTC
kernel-2.6.40.8-2.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/kernel-2.6.40.8-2.fc15

Comment 6 Fedora Update System 2011-10-30 00:35:25 UTC
Package kernel-2.6.40.8-2.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing kernel-2.6.40.8-2.fc15'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2011-15108
then log in and leave karma (feedback).

Comment 7 Yann Droneaud 2011-10-31 15:31:21 UTC
(In reply to comment #6)
> Package kernel-2.6.40.8-2.fc15
> * should fix your issue,

It doesn't fix flickering problem reported in bug 747560 (on Samsung n210).

Comment 8 Fedora Update System 2011-11-01 19:58:51 UTC
kernel-2.6.40.8-4.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/kernel-2.6.40.8-4.fc15

Comment 9 Tomasz Chmielewski 2011-11-01 20:28:52 UTC
BTW, was this pushed to the upstream kernel (the coming 3.2-rc*, or is there already perhaps)?

Comment 10 Josh Boyer 2011-11-02 16:15:56 UTC
(In reply to comment #9)
> BTW, was this pushed to the upstream kernel (the coming 3.2-rc*, or is there
> already perhaps)?

Yes, it's in Linus' tree already.

Comment 11 Fedora Update System 2011-11-12 00:07:55 UTC
kernel-2.6.41.1-1.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/kernel-2.6.41.1-1.fc15

Comment 12 Fedora Update System 2011-11-17 23:28:36 UTC
kernel-2.6.41.1-1.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.


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