Page 4 of 6
Re: HOWTO: NC10 scripts
Posted: 10 Nov 2009, 15:33
by shaunmenzies
Update:
Managed to get all the function keys working on the n310 by
1) Install 2.6.32 kernal then add the following line to /etc/rc.local
echo 130,131,132,134,136,137,177,179,247,249 > /sys/devices/platform/i8042/serio0/force_release
This forces the missing Fn key to produce key_release events. (I believe the 11 bios fixes this for NC10 but the same bios is not available for N310)
2) Then I edited /lib/udev/rules.d/95-keymap.rules and after the 'LABEL="keyboard_vendorcheck"' section I added |*N310*| to the Samsung vendor line that already contained |*NC10*| and |*NC20*|
3) Installed the NC-10 scripts detailed in this topic.
4) Installed CompizConfig and enabled the commands applet
5) Configured Fn+key keybindings to the NC-10 script commands
Now ALL MY FN BUTTONS WORK!!!!!
Thanks, Shaun.
ALL MY FUNCTION KEYS ARE NOW WORKING!!!!
Re: HOWTO: NC10 scripts
Posted: 11 Nov 2009, 20:49
by voria
New 'nc10-scripts' on repository.
There are interesting additions this time: now all the customizable options have been moved in '/etc/default/nc10-scripts', so there is no need to manually edit the scripts anymore. For instance, if your wireless card uses a different kernel module, just set it in the configuration file.
Also, there is a new option now, LAST_STATUS_RESTORE which, if enabled, it restores the current status for all devices after a system suspend/hibernate/reboot cycle. This means that if you disable the bluetooth and then shutdown the pc, the bluetooth will be already off at the next boot.
Re: HOWTO: NC10 scripts
Posted: 17 Nov 2009, 12:59
by voria
New version on repository. Changelog:
Code: Select all
nc10-scripts (4.0~ppa3~nc10~karmic) karmic; urgency=low
* Keep devices status between package updates.
* Add a new command, 'nc10 status', to show all devices status.
Re: HOWTO: NC10 scripts
Posted: 23 Nov 2009, 11:17
by voria
New version on repository. Changelog:
Code: Select all
nc10-scripts (4.0~ppa4~nc10~karmic) karmic; urgency=low
* Make the scripts work in gdm login window too.
* Add new options in /etc/default/nc10-scripts to control devices
autosuspend.
* Set webcam and bluetooth autosuspend to auto when enabling them.
* Set default values for all options in /usr/lib/nc10 if configuration
file cannot be found.
Re: HOWTO: NC10 scripts
Posted: 23 Nov 2009, 20:37
by miplou
Fn + up/down and scrolling area on touchpad don't work since today's updates (nc10-scripts, xorg-driver-synaptic and kernel)...
Re: HOWTO: NC10 scripts
Posted: 23 Nov 2009, 22:07
by voria
I've just uploaded the 'nc10-backlight' for the new kernel on the repo, it will be available in a few hours.
Concerning the touchpad, go on 'System'->'Preferences'->'Mouse' and enable scrolling (it's not enabled anymore by default).
Re: HOWTO: NC10 scripts
Posted: 24 Nov 2009, 00:29
by miplou
Many thanks !!!
Re: HOWTO: NC10 scripts
Posted: 25 Nov 2009, 15:56
by voria
New version on repository. Changelog:
Code: Select all
nc10-scripts (4.0~ppa5~nc10~karmic) karmic; urgency=low
* Use iwconfig commands to toggle wireless rfkill, instead
of module removal.
* Webcam and bluetooth kernel modules are always the same,
so there is no need for options in /etc/default/nc10-scripts.
* Add bash-completion support for all the scripts.
Re: HOWTO: NC10 scripts
Posted: 29 Nov 2009, 15:38
by voria
New version on repository. Changelog:
Code: Select all
nc10-scripts (4.0~ppa6~nc10~karmic) karmic; urgency=low
* Add back the module removal method for toggling wireless,
along with the new iwconfig method.
* Add a new option in '/etc/default/nc10-scripts' to select
which method to use.
Re: HOWTO: NC10 scripts
Posted: 30 Nov 2009, 14:32
by voria
New version. Changelog:
Code: Select all
nc10-scripts (5.0~ppa1~nc10~karmic) karmic; urgency=low
* Migrate to debhelper build system.
Using debhelper for package building, any change done by the user in the configuration file (/etc/default/nc10-scripts) is preserved between package updates.
Re: HOWTO: NC10 scripts
Posted: 30 Nov 2009, 14:41
by marshmn
voRia wrote:New version. Changelog:
Using debhelper for package building, any change done by the user in the configuration file (/etc/default/nc10-scripts) is preserved between package updates.
Ah, that's cool, I had been thinking of asking you about that
Matt
Re: HOWTO: NC10 scripts
Posted: 12 Dec 2009, 18:39
by Python
german translation cpuperf.sh:
Code: Select all
de*)
popup_title="Prozessor"
cpu_temp="Temperatur:"
cpu_freq="Frequenz:"
cpu_governor="Modus:"
governor_powersave="Energie sparen"
governor_ondemand="Auf Abruf"
governor_conservative="Zurückhaltend"
governor_performance="Leistung"
governor_userspace="Benutzerdefiniert"
;;
Re: HOWTO: NC10 scripts
Posted: 12 Dec 2009, 20:19
by voria
Added. Thank you for the translation.
Re: HOWTO: NC10 scripts
Posted: 03 Jan 2010, 11:10
by jmg74fr
Hi,
And first many thanks to you Voria
! (I've done a little donation to proove I do appreciate your great work...)
I've activated your repository (for Karmic, since I use Ubuntu 9.10). nc10scripts work fine :-)
But you talk about "wmswitcher" and "hal-info" for example in other treads of this forum. I don't find them (I just see debhelper, nc10-backlight*, nc10-scripts, voria-ppa-keyring & xserver-xorg-input-synaptics ; only these last 3 are installed) in the repository list (menu System / Admin / Synaptic).
They seem to be available only in Jaunty version : on
https://launchpad.net/~voria/+archive/ppa/+packages I see more packages for Jaunty than for Karmic, and I don't know how to get them.
Thank you !
Re: HOWTO: NC10 scripts
Posted: 03 Jan 2010, 15:24
by voria
Welcome to the forum and thank you very much for the donation, it's really appreciated!
With Jaunty there were a lot of fixes needed to have everything working properly; fortunately most of them have been fixed by default with Karmic. This is the reason why on the repository there are a few packages for Karmic, compared to the number of packages for Jaunty.
jmg74fr wrote:But you talk about "wmswitcher" and "hal-info" for example in other treads of this forum.
"hal-info" is not needed anymore, because the HAL subsystem is going to disappear in the future Ubuntu versions, and the process is already started with Karmic.
Concerning the "wmswitcher" script, I'm considering to re-add it to the 'nc10-scripts' package. After all, it's a script that can be useful from time to time.