Page 4 of 6

Re: Backlight doesn't work with latest Maverick kernel

Posted: 03 Feb 2011, 22:28
by Drake
Yes, it works on my NF310. Try to uninstall samsung-tools (it has an dependency on an old version of easy-slow-down-manager) and install the new easy-slow-down-manager.
No news. ;)

Re: Backlight doesn't work with latest Maverick kernel

Posted: 04 Feb 2011, 23:27
by spino
Drake wrote:Yes, it works on my NF310. Try to uninstall samsung-tools (it has an dependency on an old version of easy-slow-down-manager) and install the new easy-slow-down-manager.
No news. ;)
lucky you :)

still no results here (n150) - even with the new driver, even uninstalling samsung-tools...
on a side note, i can scientifically stop the flickering by hitting a menu, any menu - and only that does it.

Re: Backlight doesn't work with latest Maverick kernel

Posted: 04 Feb 2011, 23:37
by voria
I've uploaded the latest version of 'easy-slow-down-manager' and 'samsung-backlight' packages on the repository. Please install them and follow the instructions in this bug report:

http://code.google.com/p/easy-slow-down ... etail?id=7

If any issue post on that bug report, so that the project's developers can hopefully fix all the problems.

Re: Backlight doesn't work with latest Maverick kernel

Posted: 05 Feb 2011, 17:31
by brian747
how to install this new samsung easy slow manager?
tks...

Re: Backlight doesn't work with latest Maverick kernel

Posted: 06 Feb 2011, 13:46
by Drake
brian747 wrote:how to install this new samsung easy slow manager?
tks...
The update manager should get the new packages and install them. Did you try that?

Re: Backlight doesn't work with latest Maverick kernel

Posted: 06 Feb 2011, 16:51
by brian747
my upload manager don't report this new packages... why?

Re: Backlight doesn't work with latest Maverick kernel

Posted: 06 Feb 2011, 19:43
by Drake
I don't know. ;)
You should propably open a new thread for questions about that.

Re: Backlight doesn't work with latest Maverick kernel

Posted: 07 Feb 2011, 02:37
by samo615
This seems to be a popular topic and I too have this frustration.. but guess what.. the backlight doesn't seem to work for sh*t on any OS except Windows XP/7 x86 with all the software loaded. I personally have moved on from worrying about this. I set it while booting up and prefer the brightest level. Peace!

Re: Backlight doesn't work with latest Maverick kernel

Posted: 07 Feb 2011, 12:18
by rrsodl
Hello all,

I have also been trying to fix this problem on my new Samsung NC10 Plus - which under the bonnet is just a N150 :D

I'm running Ubuntu (full version - not the netbook version) - Maverick 10.10 Kernel 2.6.35-25-generic
GNOME 2.32.0
Samsung Tools 1.3.2 - I guess that is the latest version since I installed it only yesterday night.

The command I use to install the packages was

Code: Select all

sudo apt-get install samsung-tools samsung-backlight easy-slow-down-manager
I then found in this thread the bit of information "acpi_backlight=vendor"

I could now change the brightness level - thanks for that :D

However, I soon noticed the flickering problem..... it seems like something was trying to reduce brightness and another process trying to put it back on. I could overcome this by simply visiting another workspace

I then tried what "NANDERS" posted, disabling the dim the screen option when idle from power management.

...... and so far that seems to have done the trick. No more issues.

So I have not tried the latest workaround suggested by "ignasiogarcia" but I wanted to leave here this information for those that are still looking for a solution to the problem and also those who are working on a solution.

Re: Backlight doesn't work with latest Maverick kernel

Posted: 07 Feb 2011, 22:17
by rrsodl
I think I spoke too soon :D the flickering came back after I put the netbook to hybernate.


I have now applied the workaround suggested by ignaciogarcia and hopefully the problem doesn't come back.

My thanks to anyone that has contributed with ideas and solutions.

Re: Backlight doesn't work with latest Maverick kernel

Posted: 09 Feb 2011, 10:36
by rrsodl
I'm afraid the workaround did not solve the problem for me. Has anyone had any luck with the workaround so far?

What the workaround did for me though is to "solve" the suspend issue. I don't seem to have the same problem I had before applying the changes.

Any other suggestions to fix the backlight issue?

Thanks in advance

Re: Backlight doesn't work with latest Maverick kernel

Posted: 09 Feb 2011, 10:44
by gradatz
As I wrote above, the workaround works quite well so far for me.
The flickering typically occurs if I boot with the power cable unplugged and I plug it in later on. Then, manually adjusting the brightness with the brightness keys most of the time produces the flickering effect.

This can easily be resolved by unplugging and re-plugging the power cable again ;)

I did not try the suspend/resume solution so far, because I have other issues with resume as well (the GPRS modem connection very often fails after resume).

Re: Backlight doesn't work with latest Maverick kernel

Posted: 10 Feb 2011, 19:08
by rrsodl
Well, I'm glad that the workaround works for you.

It's definitely a problem with the power management. While I use the netbook never a problem but if I leave for a few minutes the power management function kicks off and the problem appears.

There is a new update today, from voria.... has anybody applied this update yet?

Re: Backlight doesn't work with latest Maverick kernel

Posted: 12 Feb 2011, 00:29
by .dawn
hey guys,
unfortunately none of these workarounds or the updates by voria work for my n220 with 10.10 installed. :( cannot change brightness with fn-keys, only by console, the same with the hibernation mode...
any new ideas or new upcoming updates concerning 10.10? :)

Re: Backlight doesn't work with latest Maverick kernel

Posted: 12 Feb 2011, 12:48
by rrsodl
No idea on any upgrades, sorry.

I wonder how different is your netbook or if this workaround / fix is intended for that model. If it is then can you trace back your steps and make sure you have applied the workaround correctly.

I have expanded the length of time before my netbook goes into suspend mode in power management and that seems to make things better - that confirms to me the problem lies with the power management function