ANNOUNCE: Diablo-Turbo first beta available
 

Announce: First beta available
18/03/2011 Update 2:
kernel-dt-sd: adds many bugfixes and optimized bluetooth UART FIFO
ramzswap: fixes startup when there is no swap file
mini-rc: adds workaround for shutdown issue
bluez-utils: new package in DT, adds optimized arm sbc encoder for people using a2dp
dbus: fix for boingomobile

What's this
An effort to improve the user experience in N8x0 running Diablo/Community SSU, by providing a new kernel (and some other related packages) with increased interactivity and new features.

What improvements can you expect
The device will be more responsive, since the cpu time and other resources will be used more fairly.
While using the DSP (playing music with the built-in media player and some others which use it as backend) you can get up to 40% more battery life (but lower speed), or 20% more speed (but less battery life). Advanced-systemui (ASUI) provides a nice UI to change this setting (op_dsp), or you can change it from xterm by typing "echo X >/sys/power/op_dsp". You can read what values can be used and their meaning in /sys/power/op_dsp_range and /sys/power/op_list_info. You can set a default value at boot time by editing /etc/kernel-dt-tunables (OP_DSP variable)
You can set the device to fully boot to desktop if it is off when connected to charger, by editing /etc/kernel-dt-tunables (BOOTREASON variable)
A new touchscreen driver which will produce less false events. It can be tuned by editing /etc/kernel-dt-tunables
Rotation support (you will need to have Community SSU installed)

Downloads (look at the bottom for install instructions):
https://garage.maemo.org/frs/?group_id=2036

The gory details: What you get with each package:

kernel-dt-sd:: The diablo turbo kernel and initfs modules. The installer backups the current running kernel and initfs modules. If you uninstall this package, everything will be restored to the previous state.
This kernel provides the following features and improvements over the stock diablo one:

• Very much improved touchscreen driver: I've found that the touchscreen is prone to lose touchscreen events, may be for aging hardware or for whatever reason, producing penup events. I have improved the touchscreen driver to avoid that problem as much as possible, by adding polled checks when a penup event is about to be produced and when the pen is supposed not to be on the screen. Two new kernel tunables to adjust the touchscreen sensitivity: /sys/devices/platform/*/penup_time (time in ms) and /sys/devices/platform/*/min_pressure (from 1 to 4091). To check if this driver is improving your device, use the touchscreen for a while (i.e. make a drawing), then from a xterm type "dmesg|grep ^TSC"; if you see any messages, then it is working for you.
• High speed mmc patch
• mmcblockX ordering fix patch for internal and external mmc
• usbnet for windows fix
• Rotation support
• From community SSU kernel: FM band selection support for Japan/Europe; DSP framebuffer sharing
• OP_DSP: Under the Diablo/Community SSU kernel, the CPU/DSP frequency is locked at 330/220 MHZ when using the DSP (playing music). DT kernel supports all CPU/DSP frequencies when using the DSP, so you can select if you want the most performance or the most battery life. Provides a new kernel tunable: /sys/power/op_dsp
• Writable /proc/bootreason: provides support for booting on charger feature.
• SWAP_PREFETCH: When the virtual memory subsystem is idle for more than 5 seconds, it will start copying pages from swap into the swapcache while keeping the copy in swap. This means the following: actually, when you use a memory hog, much of the system is swapped out. If you close the memory hog and leave the tablet for a while, when you come back to use it again it will be sluggish because it has to move the pages to memory back from swap. With this feature, when you use the tablet again, it will be very snappy because the needed pages are already in ram, and if what you use is a memory hog, it will be snappy because the pages are already in swap.
• SD Scheduler: The diablo kernel ships the O1 scheduler (official scheduler for 2.6.21 kernel) which fails to provide 100% interactivity all the time. Not only that but it is far far less forgiving of the many userspace applications that do not use extremely high performance userspace programming techniques, locking and thread manipulation (ie just about all games for example).
  The SD scheduler was the favourite replacement scheduler of many people at the time, in particular gamers. It provides fairness at all costs determined by nice level, maintaining as good interactivity as can be allowed within the constraints of strict fairness.
  What does that mean?:
  -- No process will be stalled. For example, under O1 it is easy to stall the watchdog kicker process by swapping. Once it has been stalled for more than 20 s, the tablet will reboot. SD means no more reboots caused by load.
  -- Low latency
  -- Better interactivity
  -- Fair CPU distribution. For example, under O1 mplayer will always skip when playing ogg if you connect to a wifi AP, because it won't get enough cpu to keep the buffer full. Under SD, you can make it to not skip, by adjusting two kernel tunables.
  Provides two new kernel tunables: /proc/sys/kernel/rr_interval and /proc/sys/kernel/interactive
  You can read more about the SD scheduler design here: http://ck.wikia.com/wiki/SD
• Virtual memory kernel tasks run at the effective priority of the running task
• Files too big to fit into pagecache are put at the tail of the inactive list to minimize harm to the pagecache. New kernel tunable /proc/sys/vm/tail_largefiles
• Voluntary kernel preemption: in non-preempted kernels, when a task calls the kernel, it can't be interrupted untill the call returns. This means that, sometimes, a low priority task can block for a long time more important tasks. A voluntary preempted kernel adds some points where the task can be interrupted even when in a kernel call, allowing other tasks to do their job.
• 256 HZ timer: The diablo kernel has a slow 128 HZ timer, strongly related to the number of task switches the task scheduler can do. This kernel is configured with a 256 HZ timer, and additionally the SD scheduler allows a task switch within a much more shorter time (defined by the rr_interval tunable). This means that the device will be much more interactive.
• Improved Bluetooth UART FIFO: Reduces cpu usage when using bluetooth devices.
• Many bugfixes from kernel mainline

ramzswap-dt: The Diablo-Turbo kernel swap module. Provides swap space as compressed ram, greatly increasing interactivity for a small amount of ram. For those using it, replaces ramzez-init, and has several improvements over old ramzez-init (more efficient use of ram and cpu, returns memory to the OS when it is no longer used, allows use of backing swap file).
Swap size can be configured by editing /etc/default/ramzswap, or with ramzez gui application. Swap size is 96 MB by default. It is recommended to use a traditional swap file of about 32 MB, just in case the ramzswap partition fills (doesn't happen often).

dt-init-scripts: Provides a startup script to adjust kernel tunables and provides support for fully booting when pluggin in the charger. Configured by editing /etc/kernel-sd-tunables. Also, fixes initfs linuxrc so ext3 rootfs partitions are mounted as such at boot and not as ext2. If uninstalled will restore initfs linuxrc script to its previous state.

mini-rc: Support for dt-init-scripts at shutdown, so booting on charger configuration changes are properly written to initfs when shutting down or rebooting.

dbus, dbus-1-utils, libdbus: Bugfixes: provides proper support for eavesdropping. A must for developers.

gconf2, libgconf2: Bugfixes. DBus eavesdropping exposed a nasty bug in libgconf2, this package fixes it along several other bugs and optimizations.

sysvinit: killall5 freezes itself under the SD kernel, so shutdown/reboot scripts hang and the device reboots when the watchdog triggers. This package fixes that allowing proper shutdown/reboot to happen.

gpsdriver-guard: This one has been available in extras-devel since a while. It is a fix to prevent the N810 gps driver from growing indefinitely eating all available memory.

bluez-utils: This package has an optimized arm sbc encoder, reducing greatly cpu usage and thereby increasing battery life for people using a2dp bluetooth devices.

NOTES:

• The backups are held in /usr/share/Diablo-Turbo/backups and take a bit of space. You should have at least 8 MB of free rootfs space (4 MB if running in mmc) before installing the kernel.
• The osso-software-version-rx?? (??=34 for N800, 44 for N810, 48 for N810-WiMax) package (Diablo and Community SSUs) locks dbus, gconf2 and minirc versions. To avoid any problem with apt-get or the gui installer you should install osso-software-version-rx??-unlocked
• For now, I have tested installation only with dpkg. Any issue with GUI installer will be supported later, but not at this stage.
• kernel and kernel modules sources haven't been properly packaged for autobuilding and manual patching and building is required. While I manage to create simple deb source packages, I'm a rpm guy and I'm lost with the debian build system (and to be sincere, don't like it at all). I need help to build a proper kernel source package.

Known issues:

• If you're running your system from mmc, the recommended filesystem is ext3. If you have ext2, it is recommended to convert to ext3; DT has a issue at shutdown where it sometimes hangs at the killall5 stage, so when it happens the filesystem is not unmounted before shutdown, and ext2 has issues if it is not unmounted before shutdown. Latest testing kernel seems to definitely fix the shutdown issue.
• There is a race in some driver which occasionally crashes the kthread, causing the hardware keys to stop responding; for me it is about twice a month. I'm trying to locate the culprit.

How to install:
(Updated instructions thanks to ggoebel)
Pre-requisites:
rootsh: http://wiki.maemo.org/Root_access

Optional Pre-requisites: CSSU installed on top of latest Diablo firmware, Advanced systemui
Updating Firmware: http://wiki.maemo.org/Updating_the_firmware
CSSU: http://wiki.maemo.org/Diablo_Community_Project
ASUI:http://talk.maemo.org/showthread.php?t=63292

Download Diablo Turbo zImage and *.deb files from:
https://garage.maemo.org/frs/?group_id=2036
(don't download files under the sources or obsolete headers)

Create directory /media/mmc1/dt (your external SDHC card)
move all saved dt files to this location

[Verify you have at least 8 MB free]
Open filemanager, press the info button or file->details

[become root:]
start utilities, xterm
> sudo gainroot

[Repository extras-devel or CSSU repository must be enabled to install this]
(where ?? substitute 34 for N800, 44 for N810, 48 for N810-wimax)
> dpkg -r osso-software-version-rx??
> apt-get install osso-software-version-rx??-unlocked
> cd /media/mmc1/dt

[now to install all debs expect an error about sysvinit when you execute the following...]
> dpkg -i *.deb

[work around the aforementioned error by installing sysvinit again]
> dpkg -i sysvinit_2.85-22.osso15-dt1_armel.deb

[optionally, upgrade to the testing kernel]
> fiasco-flasher -f -k zImage

reboot

start utilities, xterm
> uname -a
[you should see the following...]
Linux noname 2.6.21-omap1 #2 PREEMPT [build date] armv6l unknown

Re: ANNOUNCE: Diablo-Turbo first beta available
 

thsnks, just installed the beta debs without any issue and it has made my N810 a lot more responsive.

for general web browing using microb. it seems to be nearly as fast as my N900.

well done, much appreciated.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Ususaly I set 165 mhz when I listen music, does it mean now it will be always 400 mhz if I listen music?

P.S. Thans for your work, going to try it now!

Re: ANNOUNCE: Diablo-Turbo first beta available
 

It doesn't matter what frequency you set, it is always 333 MHZ. Now you have the choice of 333 or 400.
400 is useful for mp4 video playing with osso media player, where the dsp decodes sound and the cpu decodes video.
You can configure what frequency you want by editing /etc/kernel-dt-tunables and running "/etc/init.d/kernel-tunables restart"

PS: I have found a small issue with the ramzswap package. It seems it runs too early at startup and the ramzswap swap device is unmounted at the time the swap file is activated. As a workaround, run "/etc/init.d/ramzswap start" after booting. Tomorrow I will provide a fixed package.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Is it possible to add ipv6 support?

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Are you saying the only way to change the frequency is by editing /etc/kernel-dt-tunables, that it is set at 333MHZ no matter if the unit is idle or not? If so will that have an effect on the battery charge?

Thanks for all your effort!

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I'm willing to test the N800 screen driver.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I think he said, in the other thread, that when the DSP is active the cpu can't exceed 333MHz but this patch allows the cpu to reach 400MHz but the DSP has to be clocked slower than it would if the cpu was at 333MHz. So I'm guessing it has no effect on battery.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Quick update: New ramzswap-0.5.5-2 package available fixes the boot order issue. Download and install. No need to reboot.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Diablo always had that :-)

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Will we see this pushed via SSU once it gets a proper shakedown?

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I am going to diagree with you. Default Diablo frequency is 400, it was clocked to it in OS 2008. And in OS 2007 we had a 333 mhz, that's right.
And OS always change frequency to 165 if it not in use or if tablet don't need all processor power.
By the way, I just checked: tablet goes to 165 mhz without any problems automatically.

And I have this error during the instalation ramzes:

bla bla bla (seems to be alright)
Inserting kernel modules!
No value set for `/apps/ramzez/disksize'
insmod: can't open '/lib/modules/current/xvmalloc.ko': No such file or directory
insmod: can't open '/lib/modules/current/ramzswap.ko': No such file or directory
swapon:can't start '/dev/ramzswap0': No such file or directory
:confused:

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Ok thanks. I will try it now.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

It depends on if the DSP is in use. In OS2007, yes, it was always at 333 MHz regardless of the state of the DSP.

In OS2008, it depends. With the default OP Mode set by OS2008, when the DSP is not in use (i.e. you don't have Media Player running), then the frequency is 400 MHz; however, if the DSP is in use, the CPU will go down to 400 MHz while the DSP goes up to 133 MHz. The OP Mode is really a fancy way of prioritising one over the other: you can modify the kernel to set a different OP Mode in which the DSP will run at half its speed (~66 MHz) while the CPU can still run at 400 MHz. The OP Mode patch allows you to change it on the fly, without having to recompile a new kernel each time. Igor explains one is prioritised over the other in this post: http://www.mail-archive.com/maemo-de.../msg13383.html

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Suggestion: change /etc/init.d/ramzswap to use MODPATH=/lib/modules/$(uname -r)?

Re: ANNOUNCE: Diablo-Turbo first beta available
 

When the DSP is active the CPU is set at 333 MHZ and the DSP at 220 MHZ, no more, no less, no matter if the unit is idle or not, it is a hardware design issue, so this happens no matter the kernel. This patch allows to set the CPU at 400 MHZ at the cost of setting the DSP at 133 MHZ.
When the DSP is not in use, the governor can change the CPU frecuency.
Regarding effect on battery, the CPU takes more power than the DSP, so the 400/133 setting shortens battery life (about 25% less) wrt the 333/220 setting.
Except when playing videos, where you get about the same battery life, but smoother playback.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Oh sh*t. That happens for having installed the modules package and making asumptions about the default directory layout.
Thanks for spotting it. I'll fix it in a moment.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Quick update: available ramzswap-0.5.5-3 package. Fixes modules path in startup script.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I received an error while installing, but my N810 already feels faster, really faster. Thanks.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

By the way: I had to enable Extras-Devel in order to install osso-software-version-unlocked.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Looks like mini-rc wasn't correctly installed.
Try installing mini-rc_0.2.11-1_all.deb package again ("dpkg -i mini-rc_0.2.11-1_all.deb")

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Thanks!
Now after "Inserting kernel modules!" I have "No value set for `/apps/ramzez/disksize'

Is it ok?

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Me too.

Maacruz: I will try installing the package separately.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

It worked. After installing mini-rc_0.2.11-1_all.deb I installed sysvinit_2.85-22.osso15-dt1_armel.deb with no errors.

Thanks.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

That's fine, it just means you haven't configured the ramzswap size and it will use the default.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

It is ok. This message comes from the compatibility with the old ramzez gui application.
I guess I should silence it so it doesn't bother people.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

@maacruz
i have a n800, i can do testing..

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Are you sure? I have an application that is capable of ipv6 on a regular machine, but which errors out "this protocol is not supported" when it tries to connect using an ipv6 interface on n810 as well as n900.

Link to that application (mosquitto) is in my sig.
I had to fix the code to not use ipv6 if it gave errors.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Kernel IPv6 support is there on the N8x0s, just not enabled by default. See /usr/bin/osso-ipv6-enable.sh / /usr/bin/osso-ipv6-disable.sh, though in most cases a simple "insmod /mnt/initfs/lib/modules/2.6.21-omap1/ipv6.ko" will do.

For some reason they removed it in Fremantle, go figure.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Thanks lma. If the ipv6 driver is stable, then this means I just enable it in the mosquitto postinit scripts!

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Running much more quickly here.
Thanks for all the work.
Willing to test the n800 screen driver also.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Actually I didn't noticed any changes... Things work as slow as usual...

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Hey, some action for our old N8x0ses again, thanks maacruz !
Of cours this happens just as I am away from home for a week, I will give it a try on the 810 when I get back... I also have a 800 lying around if you need more testers :)

Re: ANNOUNCE: Diablo-Turbo first beta available
 

The cpu is the same, you can't change how fast it works, just how it is used :cool:: reduce slow mmc usage (swap module), do something useful while idle (swap_prefetch), do not starve processes and listen more to the user (sd scheduler), do not spam dbus (gconf2), do not allow unbound memory leaks (gpsdriver-guard)......

Re: ANNOUNCE: Diablo-Turbo first beta available
 

@n9ots, maluka, rlinfati:
N800 testing kernel with new touchscreen driver: deleted
Please, flash this kernel and test
1) Touchscreen works (it should)
2) Use the touchscreen heavily for a couple of minutes, make some drawing, then open a xterm and type: "dmesg|grep TSC". If it shows any message, then the driver is improving your touchscreen.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Not quite :)

Tapping the screen causes the N800 to freeze and the watchdog to kick in. This happens when tapping the screen during bootup (the blue bar at the bottom has gone a 1/4 of the way) or during the Nokia hands screen. As I have my cursor enabled at this point, tapping the screen does cause the pointer to move but my N800 to freeze straight after.

The reason why I haven't put my name down for "official" testing is because my N800's touchscreen is already quite damaged (the lower-right quadrant of the screen, for example, is totally unusable) EDIT: Just to clarify, I'm not saying this because I don't trust your work but because I wouldn't be able to give you accurate results because of my touchscreen's state. I'll happily flash any kernel you post up, but I just don't know if any results produced from my N800 would be of any use :)

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I can also confirm that the n800 touchscreen driver crashes after the first touch, The kernel is otherwise stable but as soon as I touch the screen it will crash. Thanks for the other stuff though it worked fine.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

He! Found a typo, and you know, typo==kernel crash by null pointer dereferencing :D
They are already of much use, at least regarding kernel crashes :D

Ok, here we go again.
New test zImage for N800: deleted
Fixed the typo. Let's hope this time it works, no guarantees though!
Thanks to all testers!

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Touchscreen works!

Here's what I get from a couple of minutes' use:
Nokia-N800-43-7:~# dmesg|grep TSC
[ 0.843750] #0: OMAP24xx EAC with codec TSC2301

Thanks!