Linux On My Samsung

Here's mine. some notes:

-completely disabled compiz to reduce cpu usage and increase battery life. Installed a work-around for the one compiz thing I really wanted to keep ("negative" : can be done with the command "xcalib -i -a").

-customized menu and removed many unnecessary items.

-i've ...

that setup looks nice. On my NC10, I falsely believed that only using one taskbar was better, and that the taskbar should be as narrow as possible (so that most of the screen can be used).

However, it makes navigation of the menus very difficult. I might try a larger setup from now on.

I hope they fix this wake-up kernel bug.

However, in going back to ubuntu 8.10 (before the hr_timer wakeup kernel bug), I was hardly able to get the wakeups to be significantly lower than 9.03 or 9.10, probably due to other inefficiencies.

If you disable hyperthreading in the bios, it cuts the ...

Someone in the bug report said that disabling Hyperthreading in bios reduces the number of wakeups per sec, and I confirmed this works.

While there seems to be only slight change in hrtimer_start_range_ns wakeups, my total wakeups were cut in half

before: 20 wakeups per sec, interval: 10 sec ...

The problem is also in Jaunty. Install "powertop" though synaptics, then run "sudo powertop" to see for yourself.

You'll see that this process causes 70% of wake-ups. This may explain why Ubuntu's battery life is bad compared to windows, despite massive tweaking.

also, powertop suggests to do ...

If you use "powertop", you will see that this one process is responsible for constant wakeups:
hrtimer_start_range_ns
(and other processes associated with "tick_sched_timer" and "hrtimer_wakeup"

There is a bug report here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/373245


It is ...

I've been toying with these settings for months to try to figure out the optimal setting for the NC10 and my PC habits.

It should spin-down often, not only to protect the battery, but to protect data from being lost if the computer is knocked while the HD is spinning (which technically should ...

I noticed that the CPU Frequency Scaling monitor --if added twice (one to monitor cpu0, the other to monitor cpu1 via preferences) -- is actually allowing you to assign frequency settings independent of each other.

i.e. I set CPU0 to 800 mHz, and leave cpu1 "on demand". Running programs, I see ...

After reading ubuntuforums, I decided with fresh re-install (using the ubuntu remix version- I figure it has a few additional boot/power tweaks with it).

Installation went OK. Booted up, and switched to the more "classic" desktop (rather than the iphone-looking interface).

After running the ...

I have to say the Ubuntu repository, hotfixes, scripts, all work terrific.

With all of this already set up and running on 8.10, what is the best way to go to 9.04? I originally wasn't, but looking at the features and boot times, I changed my mind.

will upgrading work, or is it better to do a ...

I've twice ran into trouble with compiz plugins (Ubuntu 8.10) on my Samsung NC10 which have forced me to completely remove and re-install compiz. In one case (Magnifier), I was unable to even get the shell to appear, and had to go into repair mode. We should probably compile a list of various ...

OK problem solved: it all had to do with my xorg.conf.

even though I had commented out the touchpad options, something in there was preventing syndaemon/synclient from working properly. I had kept the xorg.conf mostly the same (from the nc10 ubuntu wiki), because removing too much would cause low ...

syndaemon in shell is fine... it even displays "enable" and "disable" depending on if I'm typing in another window. it just doesn't actually disable the trackpad. I commented out a few more lines under my xorg.conf in synaptics with no luck. I'm going to look through my .fdi to see if there's ...

'synclient -l' shows the options, etc. I am running the syndaemon as I did before I ran the repository updates (it previously worked). I re-did the syndaemon in sessions manager.
if I type 'syndaemon -i 1 -d' in terminal, nothing happens, and the touchpad is still active while typing.

re ...

that doesn't seem to work. (there originally wasn't a shmconfig.fdi there, so i made one). there was a preferences.fdi in that folder, and i added the lines in there too, with no luck. when I had shmconfig turned on in the xorg.conf earlier, it also didn't work. also putting it in the 11-x11 ...