The NC10 story continues at bug 919773.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/810093
Title:
The new (2.6.39+) samsung_laptop kernel module causes serious
backlight flickering - makes the
This bug was fixed in the package linux - 3.0.0-15.25
---
linux (3.0.0-15.25) oneiric-proposed; urgency=low
[Brad Figg]
* Release Tracking Bug
- LP: #910894
[ Upstream Kernel Changes ]
* Revert clockevents: Set noop handler in clockevents_exchange_device()
- LP:
Well, I guess i'll open an new bug. At least Voria's patch/PPPa is
working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/810093
Title:
The new (2.6.39+) samsung_laptop kernel module causes serious
Why was the fix released as this bug has failed verification status?
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/810093
Title:
The new (2.6.39+) samsung_laptop
papukaija: The bug is fixed for the original reporter, therefore _this_
bug is fixed. Your machine must require a different fix, and thus filing
a new bug is the correct course of action.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
papukaija: please post your dmesg output and lsmod output.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/810093
Title:
The new (2.6.39+) samsung_laptop kernel module causes serious
backlight
Thanks for the help. I've also attached the full log files.
dmesg | grep samsung: [ 19.877753] samsung_laptop: found laptop model 'NC10'
lsmod | grep samsung: samsung_laptop 13353 0
** Attachment added: dmesg.txt
** Attachment added: lsmod.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/810093/+attachment/2669931/+files/lsmod.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/810093
Title:
The
** Tags removed: verification-done-oneiric
** Tags added: verification-failed-oneiric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/810093
Title:
The new (2.6.39+) samsung_laptop kernel module
I'm using the the kernel from -proposed and I'm having flickering issues
on nearly every boot on my Samsung NC10. Could you please help me to
debug this issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Cool story.
Stopped reading halfway through because it starts about having to recompile
packages and more of that stuff.
I'm not very tech savvy when it comes to Ubuntu and am not interested in
reading through 64 comments to find out whether or not someone has posted
proper instructions on how
@ImMortallity
the update is in Oneiric proposed.
So 3 steps are needed right now:
*activate the proposed repo
*Install new kernel
*deactivate the proposed repo
Or wait until the patched kernel is in the official updates repo.
--
You received this bug notification because you are a member of
** Branch linked: lp:ubuntu/oneiric-proposed/linux-ti-omap4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/810093
Title:
The new (2.6.39+) samsung_laptop kernel module causes serious
backlight
This bug is awaiting verification that the kernel for Oneiric in
-proposed solves the problem (3.0.0-15.24). Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-oneiric' to 'verification-done-oneiric'.
If verification is not
Hey,
I just installed the new kernel and backlight is working as expected. I just
changed the tags...
** Tags removed: verification-needed-oneiric
** Tags added: verification-done-oneiric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@Seth: I installed linux v.3.0.0-14.23 from -updates and the flickering
went away but I can only set the brightness to 0%, 10% (estimated) and
100% on my Samsung NC10. Should this bug be reopened or should I open a
new bug?
--
You received this bug notification because you are a member of Ubuntu
papukaija:
The patch isn't included in v.3.0.0-14.23. I think best is to wait for
3.0.0-15. You could use the kernel from #55 until new update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/810093
The linux v.3.0.0-14.23 is now in -proposed and its changelog includes
* platform: samsung_laptop: fix samsung brightness min/max
calculations! The proposed kernel is tracked in bug 893213.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
sforshee: It works for me as expected. I hope the patch will be soon in
the oneiric-update repo. :D
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/810093
Title:
The new (2.6.39+) samsung_laptop
sforshee: There is the problem. Take a look at #23. The patch should
patch this problem.
Other possibility is to use my solution from #25 instead of brightness
quirk and #23 patch. This patch is also in vorias ppa.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I pulled in the upstream version of the patch from comment #23 and did
another test build. Please let me know if it fixes the problem, and if
it does I'll work on getting both patches applied to oneiric. Thanks!
I have a good news and a bad news.
Good news:
Backlight changing is for me now working as expected.
Bad News:
Loading the kernel module is changing the backlight when it is loaded
I think the problem is somewhere in the quirk detection. I tried to find
it some time ago and came up with the
Most of the changes in the patch you attached are already applied to
oneiric (although not yet released). We're going to want to take the
versions that are in mainline Linux instead of that one for several
reasons -- first, it makes backporting future upstream bug fixes
simpler; second, the
Adding oneiric nomination, and setting the main task to Fix Released
since these fixes are already present in Precise.
** Changed in: linux (Ubuntu)
Status: Incomplete = Fix Released
** Description changed:
+ == SRU Justification ==
+
+ Impact: Many Samsung notebook models require a
sforshee:
ok thx. Good to see a really annoying bug from 2.6.39 being fixed.
If I have some spare time, I might take another look at the module loading
problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
FlexxxV: The fix for the min/max brightness calculations has been
applied to oneiric via stable updates. I've got a test build I did for
the NF310 that adds the brightness quirk patch; would you mind verifying
that it fixes the issue on your machine? Thanks!
I am really looking forward to a fix. The Samsung N130 netbook is not
really useable right now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/810093
Title:
The new (2.6.39+) samsung_laptop kernel
@polarapfel use the ppa until kernel fix
@all
We should send Greg Kroah-Hartman the patch from #25 (this one is used in the
ppa) as a patch against the vanilla kernel. He is the maintainer. I'm at the
moment too busy.
--
You received this bug notification because you are a member of Ubuntu
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/810093
Title:
The new (2.6.39+) samsung_laptop kernel module causes serious
backlight flickering - makes
FYI ...
Quite a few issues in samsung-laptop were fixed in the version going
into the 3.2 kernel:
http://git.kernel.org/?p=linux/kernel/git/stable/linux-
stable.git;a=blob_plain;f=drivers/platform/x86/samsung-laptop.c;hb=HEAD
Ubuntu 12.04 will be using the 3.2 kernel.
Recently Corentin Chary
Could someone please sent the final patches to Greg KH? Thanks in
advance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/810093
Title:
The new (2.6.39+) samsung_laptop kernel module causes serious
** Tags added: backlight
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/810093
Title:
The new (2.6.39+) samsung_laptop kernel module causes serious
backlight flickering - makes the desktop
@neferty:
On my Samsung N130 Tauno's suggestion didn't either, but the samsung-backlight
package from https://launchpad.net/~voria/+archive/ppa as described in comment
#26 (see also my description in Bug #784523)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Thanks for you input tauno. However this didn't do it on Samsung n130
:-/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/810093
Title:
The new (2.6.39+) samsung_laptop kernel module causes serious
I have Samsung NP-R530 laptop computer, did a clean install of Ubuntu Oneiric
Ocelot a.k.a Ubuntu 11.10 and had the same issue until I added
acpi_backlight=vendor to the kernel parameters. After doing that i ran the
command sudo update-grub and rebooted my machine. Everything seems to be
There are my lsmod outputs:
After unloading the samsung-laptop (backlight doesn't work): lsmod 1.txt
And after logout and login (backlight work): lsmod 2.txt
** Attachment added: lsmod 1.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/810093/+attachment/2573035/+files/lsmod%201.txt
** Attachment added: lsmod 2.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/810093/+attachment/2573036/+files/lsmod%202.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/810093
Title:
I have the Samsung n127 (the system has identified it as the n128), and I found
a workaround:
You must remove the module samsung-laptop in /etc/rc.local:
rmmod samsung-laptop
And restart OS, but brightness/backlight will not work, so you must log out and
again log in... And it all worked!
P.S.
waldemar.yan: I'm pretty sure that something is wrong with your
workaround. This shouldn't work. By unloading the samsung-laptop module
you can't change the backlight without direct hw access. You must have
loaded some (other none default?) module for this. Please post your
lsmod output.
For a
Is this really a regression? Before 2.6.39 There was no backlight
changing. Since 2.6.39 the samsung-laptop module is activated by default
and we have a backlight changing problem.
ketilwaa: I also think that your problem is not related to this bug
report
--
You received this bug notification
I consider this as a regression since the brightness/backlight control
worked perfectly (for the exception of togling the screen on/off but
that's bug 296489) on NC10 in Natty witout flickering.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I also consider this a regression (N110) from natty, the error that
interrupts workflow was not present in natty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/810093
Title:
The new (2.6.39+)
** Tags added: metabug regression-release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/810093
Title:
The new (2.6.39+) samsung_laptop kernel module causes serious
backlight flickering - makes
I received a reply from Greg KH:
I'm traveling at the moment, and can't see the launchpad bug, but glad
to hear that it fixes the issue for you. Hopefully someone forwards the
patch to me, in a format that I can apply it in, so that it gets added
to the main kernel tree :)
--
You received this
Samsung N110 is also effected
Timescale for getting a fix to users?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/810093
Title:
The new (2.6.39+) samsung_laptop kernel module causes serious
This bug is likely to be fixed in upstream first, so please be patient.
You can also use the Fortunato's PPA (ppa:voria/archive - link in
comment 26) to fix this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks papukaija, no impatience; just curiosity (Ok maybe abit of
impatience too lol)
An intermediate solution is of course to disable dim screen to save
power in System Settings - Screen (I've noticed that the BacklightUp +
BacklightDown trigger is also fixed by this).
I will install the PPA
I've marked bugs #776637 #876775 as duplicates. A few people
subscribed to those too (so the problem is probably rather widespread).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/810093
Title:
The
Using a Samsung x125.
I first followed the instructions here:
http://www.voria.org/forum/viewtopic.php?f=3t=821hilit=brightness+flicker
Then I instead used the Voria PPA. The flickering does not happen, but I'm
unable to adjust the backlight with the Fn + arrow keys. Is this expected
behaviour,
I'm sorry, just realized my foul up. I had forgotten to update Grub after
reverting the changes in abovementioned Voria forums. So, now I can adjust the
backlight, but it does not automatically change when (un)plugging power chord.
Sorry to distract anyone.
--
You received this bug
I've now managed to upgrade my sister's N110 to Oneric thanks to the
DKMS module fix, appears to be working 100% correctly, but I may be
missing something ofcourse
@Ketilwaa are you sure that your settings are not to fault here? I don't
think that's related to this bug :)
--
You received this
NF310 is also affected by this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/810093
Title:
The new (2.6.39+) samsung_laptop kernel module causes serious
backlight flickering - makes the
Sorry for the late answer.
I've updated the PPA package, it now includes all the relevant patches and uses
your suggested method to change the brightness.
So far, it works good here.
I've sent an email to Greg Kroah-Hartman. I sent him a link to this bug report,
and asked for his opinion on
I installed the RC9 and the daily 3.1 kernel. For some reason I was unable to
do a normal boot (boot just freezes with new kernel just like in this bug
report: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/856810). So I
testet it in Safe-Mode (modprobe samsung-laptop, echo number
I've tested the patches from Greg Kroah-Hartman git repository on my Samsung
NC10.
They work most of the time, but randomly they fail.
I've written 2 patches that fix the problem and I've already sent them
to Greg. I will attach them here too.
--
You received this bug notification because you
** Patch added: Sometimes, while the function check_for_stepping_quirk()
does its job by setting the new levels of brightness, the screen starts
flashing, and the quirk ends up to be (wrongly) disabled. This happens
randomly and seems to be caused by the number of levels checked; increasing
** Patch removed: Sometimes, while the function check_for_stepping_quirk()
does its job by setting the new levels of brightness, the screen starts
flashing, and the quirk ends up to be (wrongly) disabled. This happens
randomly and seems to be caused by the number of levels checked;
If the module is loaded when the brightness is initially to
level 0, the function check_for_stepping_quirk() fails to detect that quirk
is needed. This is because at level 0 the brightness control behaves in a
different way.
Increasing the brightness level from 0 to 1 before doing the quirk
Sometimes, while the function check_for_stepping_quirk() does its job
by setting the new levels of brightness, the screen starts flashing, and
the quirk ends up to be (wrongly) disabled. This happens randomly and
seems to be caused by the number of levels checked; increasing this
number from 2 to
I can confirm we need a special check for 0 I just tested your patch and
it is working. I can't reproduce bug mentioned in #22 (on Samsung N220),
but it doesn't do anything bad, so I think it should be used.
But there must be a bug in code, because if I load the module the screen
brightness
I tested my Idea and it is just working. All I changed is from original
3.0 kernel samsung-laptop.c is the set_brightness function. I can't
notice any problems with the fast change to min_brightness. I think this
should work on any Samsung Laptop and doesn't require any complicated
quirk check.
** Changed in: linux (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/810093
Title:
The new (2.6.39+) samsung_laptop kernel module causes serious
Nice idea :)
I've tested your solution on my NC10 and it works fine, and I like the
simplicity of the fix.
For anyone interested to try it, I've built a package called 'samsung-
laptop' which contains the patched kernel module in DKMS format, so it
can easily be installed on a running kernel.
The ppa will make testing much easier. good idea!
voria, are you in contact with Greg Kroah-Hartman? Maybe he has some
background infos on Sabi (there isn't any public documentation, is it?).
I think we should also use patch mentioned in #13 because this bug is still
relevant.
--
You received
Set importance to High for Flexxxv since this issue is making any
system with the affected hardware unusable.
** Changed in: linux (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Would it be possible for you to test the latest upstream kernel? It
will allow additional upstream developers to examine the issue. Refer to
https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the
upstream kernel, please remove the 'needs-upstream-testing' tag. This
can be done by
I can confirm this too.
There is some talk about this issue on LKLM. I tried a patch for min max
corrections, but it didn't help. I'll take a look at these patches later:
http://git.kernel.org/?p=linux/kernel/git/gregkh/patches.git;a=tree
--
You received this bug notification because you are a
Hey I got this working :D
I applied:
platform-samsung_laptop-fix-samsung-brightness-min-max-calculations.patch
platform-brightness-quirk-for-samsung-laptop-driver.patch
from:
http://git.kernel.org/?p=linux/kernel/git/gregkh/patches.git;a=tree
and recompiled the modules.
Probatly it is a good Idea
Sry I can't figure out how to add more than one attachment
** Patch added:
platform-samsung_laptop-fix-samsung-brightness-min-max-calculations.patch
and here the binary
** Attachment added: samsung-laptop.ko
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/810093/+attachment/2538168/+files/samsung-laptop.ko
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/810093
Title:
The new (2.6.39+) samsung_laptop kernel module causes serious
backlight flickering - makes the desktop unusable
ok here is the real patch. sry. this is the diff between my patched
samsung-laptop.c and the original samsung-laptop.c. Credits go to Greg
Kroah-Hartman.
** Patch added: samsung-n220-backlight-fix.patch
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/810093
Title:
The new (2.6.39+) samsung_laptop kernel module causes serious
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is
I can confirm that the bug still exists in 3.0.0-12.19
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/810093
Title:
The new
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is
I can confirm that this bug still exists in Kernel 3.0.0-11-generic. The
behaviour is like papukaija said. It is pretty annoying and blacklisting
the module isn't a real workaround, because you won't have any control
over backlight. Only workaround I know is installing
sry, the 3.0.0-11 kernel is of cause the 3.0.0.11.18 kernel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/810093
Title:
The new (2.6.39+) samsung_laptop kernel module causes serious
backlight
Confirmed still occurs on 3.0.0-11-generic #18
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/810093
Title:
The new (2.6.39+)
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is
81 matches
Mail list logo
