Works on Ubuntu Karmic started

[voria]

I'm starting to work on ubuntu karmic, and I've added the first packages on the repository.
To use them, you have to add these lines to your /etc/apt/sources.list:

Code: Select all

deb http://ppa.launchpad.net/voria/ppa/ubuntu karmic main 
deb-src http://ppa.launchpad.net/voria/ppa/ubuntu karmic main

Here is a list of current packages, I'll keep it updated while adding new ones:

- acpi-support
- nc10-backlight
- nc10-backlight-2.6.31-10
- nc10-scripts
- usplash-theme-ubuntu
- xserver-xorg-input-synaptics

acpi-support enables laptop-mode by default.
nc10-backlight-2.6.31-10 provides backlight support for kernel 2.6.31-10 with KMS enabled.
nc10-backlight depends from and installs always the nc10-backlight for the latest available kernel. So, just install this one.
nc10-scripts installs the usual nc10 scripts. xbacklight does not work anymore with KMS enabled kernels, so I've reworked the FN-F5 script.
usplash-theme-ubuntu fixes progress bar position for 1024x600 resolution.
xserver-xorg-input-synaptics installs the latest available synaptics touchpad driver, which has the ability to configure vertical and horizontal sensitivities automatically. It installs a custom .fdi configuration file too.

Testing feedbacks are welcome.

[gatos]

Is Karmic reasonable stable at the moment to work as normal and do some testing as well, or not?
Problem is that my girlfriend has fallen in love with my NC10 and is always using it. If it becomes unstable she is going to moan non stop that I destroyed the computer .

I really want to try Karmic, but....

[voria]

I'm using it for a while now with no problems.
But there is lot of work on it in this period, a lot of new packages are added every day and breakage can always happen.

If you want to avoid any possible problem, then stick with jaunty.
However, you can always install it on another partition...

[biniou]

There is a way to make the brightness work. For that, you have to add "nomodeset" to the end of your kernel line in Grub.cfg
There is the same problem with the last Fedora which use KMS too.

I use your Jaunty repository and it's working perfectly.

[voria]

There is a way to make the brightness work. For that, you have to add "nomodeset" to the end of your kernel line in Grub.cfg
There is the same problem with the last Fedora which use KMS too.

Yes, that's the solution I'm using with kernel 2.6.31 for jaunty on my repository: disable KMS by default.

In karmic instead I prefer to keep KMS enabled and to install a kernel module (contained in the 'nc10-backlight' package) which enables the backlight control.
If you are using karmic and my repository, please try reenabling KMS and installing the above package.

[biniou]

Well, thanks because I tried and it works great even with KMS!
On the other hand, I think the touchpad is more sensitive horizontaly than verticaly but maybe I'm wrong or that's normal because of 16/9 :-p

Anyway, again a big thank you for all your great work!

PS: and again, sorry for my english lol

[voria]

Yes, it's normal.
With kernel >= 2.6.31 and synaptics driver >= 1.1.3 the sensitivity is automatically detected, based on aspect ratio.

PS: I've updated the 'nc10-scripts' package. Now bluetooth can be toggled.

[marks]

Do you plan to try and get the nc10-backlight package (and possibly the scripts as well) included in main at any time? It's great work that you're doing but it would be really good if everything could work "right" from the standard repositories.

[voria]

I have never considered that option, mostly because I look at my packages more as a temporary "hack" while waiting for a real solution to the problems.

For instance, I think there should be a better and more generic way to disable wireless: removing/inserting the module to disable/enable it (the way my scripts work) works for now but it cannot be a definitive solution to the problem.

Same thing about the nc10-backlight: the module included in that package is somewhat an hack (more info here) while waiting for a real support from the intel video driver or kernel or anything else.

[marks]

Right, I see. Well if GregKH is dealing with the backlight driver then I suspect it is only a matter of time before it ends up in the main kernel tree. I see your point about the wireless RFKILL switch, it really should map through to a command and not require the removal of the module and the rest of the scripts are quite specific.

[voria]

New 'nc10-scripts' on the repository, for karmic.
The main addition is the support for KDE (kubuntu) hotkeys and notification popups.

[magick]

From the changelog of the 2.9.0 intel driver

* Add support for BACKLIGHT property when using kernel modesetting
(KMS). This allows backlight adjustment with programs such as
"xbacklight -set <percentage>" or "xrandr --set BACKLIGHT <value>".

This should make your "hack" with the kernel module obsolete, shouldn't it?

BTW: Thanks for your work, my new NC10 wouldn't be so much fun under karmic without your little tweaks :-)

[voria]

No, that fix does not work for our netbook, the 'nc10-backlight' package is needed yet.

PS: Welcome to the forum

[magick]

I deinstalled your kernel module und reinstalled xbacklight. Then i set
xbacklight --set 30
and the screen dimmed.

Kernel is 2.6.31.14
driver is 2.9.0

Am i misinterpretating something?

[voria]

To completely remove the backlight module from my repository, you have to uninstall both the 'nc10-backlight' and 'nc10-backlight-2.6.31-14' packages. Then you have to reboot. Also, are you sure you have KMS enabled?