@papukaija:
no, the 'samsung-laptop' package available on my PPA has no specific fixes for
NC10.
It's built from the latest sources taken from iksaif's git repository:
https://github.com/iksaif/samsung-laptop-dkms
Since iksaif is now the maintainer of the samsung-laptop module, his
changes will
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
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'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
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 situation with the brightness control is a complete mess at the moment and
it's getting very annoying.
Unfortunately, I only have a Samsung NC10 and the brightness control here is
working out-of-the-box, with no need to use the samsung-backlight kernel
module, and I'm unable to investigate
Public bug reported:
Binary package hint: pm-utils
The current intel-audio-powersave hook shipped with pm-utils-1.4.1 is broken.
Attached a patch that fixes it.
** Affects: pm-utils (Ubuntu)
Importance: Undecided
Status: New
--
pm-utils ships a broken intel-audio-powersave hook
** Patch added: fix_intel-audio-powersave_hook.patch
https://bugs.launchpad.net/bugs/657884/+attachment/1682573/+files/fix_intel-audio-powersave_hook.patch
--
pm-utils ships a broken intel-audio-powersave hook
https://bugs.launchpad.net/bugs/657884
You received this bug notification because
If this can be of any help, many users have reported the problem is
fixed by applying this patch to the kernel:
http://marc.info/?l=linux-idem=122724081603679w=2
If anyone wants to try it, a kernel is available on my PPA:
https://launchpad.net/~voria/+archive/ppa
--
ata exception and hang
Exactly the same behaviour here as Hans Bakker, on a Samsung NC10
netbook.
--
Monitor brightness can not be controlled by hotkeys
https://bugs.launchpad.net/bugs/500613
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase in ubuntu.
--
Sorry for the late answer, but I was no more subscribed to this bug.
You can find fixed kernel and udev packages on my repository (link below), for
both karmic and lucid.
They fix the FN keys release on these samsung models:
N120, N128, N130, N140, N148/N208, NB30, N150/N210/N220, N220, N310,
That's really odd.
Are the Fn+up and Fn+down keys recognized by using the 'xev' command line
utility?
--
Samsung N120 Brightness controls don't work (Jaunty+Karmic)
https://bugs.launchpad.net/bugs/429351
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I've built a new package for karmic, containing the needed kernel module
for the realtek 8192e wireless card.
It's called 'samsung-wireless' and it's available on my testing ppa:
https://launchpad.net/~voria/+archive/archive/
Some users have reported it's working good on Samsung N130/N140, it
To enable the FN keys, you need to edit the file
'/lib/udev/rules.d/95-keymap.rules', search for the string 'NC10', then
add your model to the list of Samsung models.
In other words, modify the line:
ENV{DMI_VENDOR}==[sS][aA][mM][sS][uU][nN][gG]*,
I've built a .deb package for the latest stable kernel, containing the
kernel module written by Greg Kroah-Hartman (http://github.com/gregkh
/samsung-backlight), which enables backlight control on various Samsung
netbooks, when KMS is enabled.
It's called 'nc10-backlight' and it's available on my
Here it is.
It applies correctly to the package version '0.10.25-2ubuntu1.1', after all the
other patches in 'debian/patches/'.
** Attachment added: Fix subtitles autoload in gst-plugins-base0.10
(0.10.25-2ubuntu1.1)
http://launchpadlibrarian.net/36527470/protect-subtitle-elements.patch
--
Public bug reported:
Binary package hint: debhelper
When building a package, if 'debian/package.upstart' and
'debian/package.default' both exist, 'debian/package.default' is ignored and
not installed.
The attached patch fixes this problem.
ProblemType: Bug
Architecture: amd64
Date: Mon Nov 30
** Attachment added:
fix-package.default-installation-when-package.upstart-exists.patch
http://launchpadlibrarian.net/36256024/fix-package.default-installation-when-package.upstart-exists.patch
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/36256025/Dependencies.txt
The problem exists even in the latest debhelper (version 7.4.8)
available in Debian Sid, so I filed a bug on the debian bug tracking
system too:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558782
** Bug watch added: Debian Bug tracker #558782
This bug has been fixed upstream with release 7.4.9.
Please backport it to karmic.
** Changed in: debhelper (Ubuntu)
Status: New = Fix Released
** Changed in: debhelper (Ubuntu)
Status: Fix Released = Fix Committed
--
dh_installinit does not install 'package.default' if
I've build a new 'gst-plugins-base0.10' package which includes the (adapted)
upstream patch.
It's based on version '0.10.25-2ubuntu1' (not the proposed
'0.10.25-2ubuntu1.1'), and it's available on my testing PPA:
https://launchpad.net/~voria/+archive/archive
--
Totem hangs while loading a
Updating the NC10 bios to version 11CA fixes the problem.
Alternatively, you can use an additional kernel module which enables the
backlight control when KMS is enabled.
More info at: http://github.com/gregkh/samsung-backlight
I've packaged it for karmic, it's available on my repository 'PPA for
The kernel on my NC10 repository is not optimized in any way, it's just
a backport to jaunty of the latest kernel available for karmic.
--
Samsung NC10 fails suspend/Resume tests
https://bugs.launchpad.net/bugs/340014
You received this bug notification because you are a member of Ubuntu
Bugs,
Done.
http://bugzilla.gnome.org/show_bug.cgi?id=582587
** Bug watch added: GNOME Bug Tracker #582587
http://bugzilla.gnome.org/show_bug.cgi?id=582587
--
Ctl-Alt-L does not lock screen immediately after startup
https://bugs.launchpad.net/bugs/354792
You received this bug notification because
I have modified the '90-Add-guarded-brightness-stepping-functions' patch in
order to get 12 levels of brightness adjustment, and changed the formulas used
to calculate the next step for decreasing/increasing brightness in order to get
constant steps.
It seems to work good on Samsung NC10.
Public bug reported:
In Intrepid I was used to enable the autologin feature in gdm, then add the
'gnome-screensaver-command --lock' in Startup Applications to lock the screen
immediately after login. This way I was ready to work just inserting my user
password. Furthermore, when I started up
** Attachment added: screensaver_startup_timeout_customizable.patch
http://launchpadlibrarian.net/25994427/screensaver_startup_timeout_customizable.patch
--
Add a gconf key for setting the time delay before to start 'gnome-screensaver'
at session startup
Looking at the code in 'gpm-brightness.c', it seems that xrandr is
preferred over hal when both are available. I don't know why but there
is certainly a good reason if it's so.
--
Brightness control is slow and not costant with
90-Add-guarded-brightness-stepping-functions.patch
No, it's manually set. It was set to 24 in the original patch, I changed it to
12 to get bigger steps.
IMHO this is not a good solution, because a fixed value is not good for
everyone, as you stated.
However, I just modified the original patch, I don't know if there is a more
generic way to set
It seems that hal support is not always available. For example, 'lshal' does
not report any UDI for backlight on Samsung NC10. Apart from that, it would be
a bad idea to use hal in gpm xrandr functions.
Looking at the code, there are two distinct way to set brightness, xrandr and
hal.
--
It seems that hal support is not always available. For example 'lshal' does not
report any UDI for backlight on Samsung NC10. Apart from that, it's a bad idea
to use hal in xrandr functions.
As I said in a previous comment xrandr is preferred over hal when both are
available, and hal support
The issue is caused by a recent change in gnome-settings-daemon that adds a 30
sec delay for starting gnome-screensaver. This is the reason for it (directly
from source code):
/*
* We'll start the screensaver after a delay so it doesn't
* compete with other processes
36 matches
Mail list logo
