search

tunahansahiner / easy-slow-down-manager

Automatically exported from code.google.com/p/easy-slow-down-manager
0 stars 0 forks source link

Kernel 2.6.35-24 backlight flickering #7

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
After installing Ubuntu kernel 2.6.35-24 (and overcoming the problems mentioned 
in easy-slow-down-manager bug #6) there remains a strange problem. When the 
system itself tries to change the backlight brightness (e.g. dim the display 
while idling, open the lid, ...) it starts flickering (i.e. lowering 
brightness, then raising brightness, then lowering brightness, ...) - see 
http://www.voria.org/forum/viewtopic.php?p=4465#p4465 . At least, N150, N210, 
N230 and NF310 are affected. 

What steps will reproduce the problem?
http://www.voria.org/forum/viewtopic.php?p=4554#p4554
E.g.: Type in a terminal window: sleep 1; xset s activate

What is the expected output? What do you see instead?
Display backlight is starting to flicker instead of being correctly adjusted.

What version of the product are you using? On what operating system?
Ubuntu 2.6.35-24

Please provide any additional information below.
Workaround: http://www.voria.org/forum/viewtopic.php?p=4557#p4557

Original issue reported on code.google.com by drakehig...@googlemail.com on 15 Jan 2011 at 12:01

GoogleCodeExporter commented 9 years ago 
Since I cannot reproduce this issue on my X360, I need some more information.
0) Install the latest version of easy-slow-down-manager (0.13.7)
1) Try booting with additional option samsung_backlight.use_sabi=0 and check, 
if the issue is gone
2) Try booting with additional option samsung_backlight.debug=1,
then kill gnome-power-manager and start it with --verbose option:
$ killall gnome-power-manager
$ gnome-power-manager --verbose >gpm.log
3) Try to reproduce the issue
4) save filtered dmesg output
$ dmesg | grep -i brightness >sbd.log
Please, attach these files (gpm.log,sbd.log) to this issue.
5) Try booting with additional option samsung_backlight.sabi_delay=100
This will slow down brightness changes; check, if the issue is gone

Original comment by SergeyK...@gmail.com on 24 Jan 2011 at 6:17

GoogleCodeExporter commented 9 years ago 
I'm using a NF310:
0) Done.
1) Bug seems to be gone due to broken brightness steps. There are 8 brightness 
steps in GPM (0-7) but only 0 and 1 seem to work. This means: Setting the 
brightness to 2,3,... has the same effect as setting it to 1.
3) Successfully reproduced. :(
5) That slows down the flickering but it's there.
Thanks so far. :)

Original comment by drakehig...@googlemail.com on 24 Jan 2011 at 11:18

Attachments:

GoogleCodeExporter commented 9 years ago 
Could you repeat step 1) with the new driver and try to reproduce the bug?
gpm.log says that you've pressed brightness up and brightness down keys 
multiple times, is it correct?
did you make sbd.log directly after reproducing the bug (I do not see much 
flickering from logs)

Original comment by SergeyK...@gmail.com on 26 Jan 2011 at 7:42

GoogleCodeExporter commented 9 years ago 
> Could you repeat step 1) with the new driver and try to reproduce the bug?
All brightness steps are working now and the flickering is gone!

>gpm.log says that you've pressed brightness up and brightness down keys 
multiple times, is it correct?
No. I launched gnome-power-manager and the next thing I did was pressing CTRL+C 
after a few seconds of flickering.

> did you make sbd.log directly after reproducing the bug (I do not see much 
flickering from logs)
Yes, I think it starts at 80.171689 (lowers the brightnes 3->2->1 and then 
flickers 1->2->1->2->...).

Original comment by drakehig...@googlemail.com on 26 Jan 2011 at 9:52

GoogleCodeExporter commented 9 years ago 
Hello,

Just for add some info, I have experimented the same problem with a samsung 
n150, Linux Mint Debian Edition and kernel 2.6.38-2.

Thanks for your fab work!

Original comment by run...@gmail.com on 11 Apr 2011 at 5:19

GoogleCodeExporter commented 9 years ago 
I got the problem too with an identical system to contact 5. Any news yet?

Original comment by HenrySev...@gmail.com on 29 May 2011 at 7:47

GoogleCodeExporter commented 9 years ago 
My Logs without changing sabi_delay. Didn't press any key, just start GPM, wait 
for flicker (some seconds), kill gpm.

Original comment by HenrySev...@gmail.com on 31 May 2011 at 6:13

Attachments: