Re: ANNOUNCE: Diablo-Turbo first beta available
 

There is a new test kernel with a new stability fix.

You can find it at the downloads page (Last DT test kernel): https://garage.maemo.org/frs/?group_id=2036

As usual, flash directly using "flasher-3.0 -f -k zImage -R" from your pc, or "fiasco-flasher -f -k zImage" from your tablet (and reboot when done)

Re: ANNOUNCE: Diablo-Turbo first beta available
 

the Last DT test kernel seem to be dated 2011-02-16 23:30, is that correct or has the date not been updated yet? :confused:

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I just forgot to change the date :rolleyes: Updated now.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

No problem with the new test kernel, what was the new stability fix?

Re: ANNOUNCE: Diablo-Turbo first beta available
 

ARM VFP state can be corrupted during VFP exception handling when PREEMPT is enabled, it appears to occur during VFP exception handling when a task causes a VFP exception which is handled via VFP_bounce and is then preempted by yet another task which in turn causes yet another VFP exception. So to prevent this problem preemption is disabled while handling VFP exceptions.
Got it from omap branch git, committed on 1 apr 2009
From the time I've been testing it, I'd say it fixes completely the shutdown issue.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

fuse modules in extras-devel are incompatible with the DT kernel.
I have added a recompiled fuse module package under "Optional packages" in the download page.
You'll need it if you use fuse filesystems (sshfs for example), or have installed maemo-pc-connectivity (it is a dependency)

Re: ANNOUNCE: Diablo-Turbo first beta available
 

What is "VFP"?

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I don´t know if this fix a bug with the clock alarm app but the alarm now works. The clock alarm app on my unit would not work if the unit was off (like the N800) but now it works after the upgrade to the new test kernel. :cool:

I'm stuck - was Re: ANNOUNCE: Diablo-Turbo first beta available
 

Unit is N800, I'm ok with cli stuff but know more about cp/m than linux.

Some time ago I did whatever it took to get it to boot from an SD card. That took quite a bit of reading and typing and I got it almost completely correct (only problem is it won't do a default boot after 15 sec, just waits forever for me to press a key, but that's ok).

Then I went away from this forum and just used the thing, is fine.

Came back here and there is whoohoo, new stuff.

So I want the turbo kernel and rotation support and all that.

First step seems to be (after downloading all the debs) to install oss-software-version-rx34-unlocked.

apt-get tells me it can't due to a conflict with osso-software-version-variant.

So I'm stuck; help please...

Further questions:

I'm updating a kernel - where does that live? On the sd card, or in the n800 internal flash? Do I have to do anything special to make sure the turbo kernel is what is loaded when it boots from the sd card?

I have a bunch of stuff on the same card that it boots from - will installing the turbo kernal etcetera remove all that?

Sometimes the n800 burps or reboots or something and it goes back to the plain vanilla desktop that I had before I got it to boot from the sd card; I presume that somehow it is getting confused and (re-)booting from there - is that right, is it indicative of a problem, how can I fix it?

Wishlist: hardware hack to put a 3 megapixel camera in place of the 300k one.

Re: I'm stuck - was Re: ANNOUNCE: Diablo-Turbo first beta available
 

CP/M instead of *nix? I'm speechless...

If you want rotation support you need to have CSSU installed first. Have you installed it already?

Please paste here the console output of apt-get install

The internal flash is divided into 4 partitions. 1st one contains the lock password, R&D flags, which partition to boot from, and other data. 2nd one contains the kernel. 3rd one contains initfs, a small filesystem used when booting, here is where you installed the bootmenu. 4th one contains the main OS partition, this one is used only if you have selected to boot from internal flash.
Since the kernel is the first thing loaded at boot, it'll use the same kernel no matter where you boot from.

Not at all.

It indicates a problem with bootmenu.
If you always boot from the sd card and just use the internal flash as backup, you can uninstall bootmenu and configure the tablet to boot from sd first and flash second. Then, to boot from internal flash, you just pull out the sd card before turning on the device.
:D

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I remember there was rotation long before cssu existed as an idea. Are you thinking of N900?

Re: ANNOUNCE: Diablo-Turbo first beta available
 

The CSSU is the simplest way to install rotation support on the N8x0's. It existed before, but became "standard" with the CSSU.

Re: I'm stuck - was Re: ANNOUNCE: Diablo-Turbo first beta available
 

------------
If you want rotation support you need to have CSSU installed first. Have you installed it already?
-------------
No. What drew my attention initially was the neato power-button-menu, then I read a bit about the ssu, and then the turbo kernel, and I thought that would be the first thing to do. Can't do that? Ok, what's step one then.
----------------
Please paste here the console output of apt-get install
--------------
Ok:

/home/user # apt-get install osso-software-version-rx34-unlocked
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run ‘apt-get -f install’ to correct these:
The following packages have unmet dependencies.
osso-software-version-rx34: Conflicts: osso-software-version-variant
osso-software-version-rx34-unlocked: Conflicts: osso-software-version-variant
pygtkeditor: Depends: python2.5-pygtksourceview but it is not going to be installed
E: Unmet dependencies. Try ‘apt-get -f install’ with no packages (or specify a solution).
/home/user #

( I did apt-get -f install after the first time apt-get suggested it, this output is from after the -f install command)
----------------
The internal flash is divided into 4 partitions. 1st one contains the lock password, R&D flags, which partition to boot from, and other data. 2nd one contains the kernel. 3rd one contains initfs, a small filesystem used when booting, here is where you installed the bootmenu. 4th one contains the main OS partition, this one is used only if you have selected to boot from internal flash.
Since the kernel is the first thing loaded at boot, it'll use the same kernel no matter where you boot from.
-----------
Got that, all makes sense now.

(this forum quoting thing is funny, it only does one level deep quotes it seems, oh well)

(in re my question about booting issues...)
--------------
It indicates a problem with bootmenu.
If you always boot from the sd card and just use the internal flash as backup, you can uninstall bootmenu and configure the tablet to boot from sd first and flash second. Then, to boot from internal flash, you just pull out the sd card before turning on the device.
--------------
Ok, I'll dig around and see if I can figure out how to fix that.

Thanks, and do keep going...

Re: I'm stuck - was Re: ANNOUNCE: Diablo-Turbo first beta available
 

Step one: install CSSU
Step two: install DT
Step three: install Advanced-systemui and Telescope
We'll address this once you have successfully installed CSSU

As you can see, it can do nested levels.

Re: I'm stuck - was Re: ANNOUNCE: Diablo-Turbo first beta available
 

Ok I got the CSSU installed, still getting the conflict with osso-software-version-variant when I try to install the unlocked version.

Did apt-get -f install and no change.

Just checked and extras-devel is enabled.

What now?

Re: I'm stuck - was Re: ANNOUNCE: Diablo-Turbo first beta available
 

try apt-get -bd-install

Re: I'm stuck - was Re: ANNOUNCE: Diablo-Turbo first beta available
 

Just to be sure, let's check the variant you have installed.
It should be osso-software-version-rx34
Then, uninstall the package using dpkg and install the unlocked one with apt-get
The CSSU repository must be enabled

Re: I'm stuck - was Re: ANNOUNCE: Diablo-Turbo first beta available
 

That gets me
dpkg-query: need an action option

Re: I'm stuck - was Re: ANNOUNCE: Diablo-Turbo first beta available
 

And dpkg-query -L osso-software-version-* gets me

Package 'osso-software-version-*' is not installed.

I have package-view on this thing; it says I have rx34, so will proceed with the next two steps...

Re: I'm stuck - was Re: ANNOUNCE: Diablo-Turbo first beta available
 

All good, now on to systemui and telescope.

Thanks very much.

Did I say thankyou?

THANKS.

Re: I'm stuck - was Re: ANNOUNCE: Diablo-Turbo first beta available
 

Those are easy.
apt-get install telescope
apt-get install advanced-systemui
Then go to the control panel and enable the asui battery applet.
Doesn't your device look better now? :D

Re: I'm stuck - was Re: ANNOUNCE: Diablo-Turbo first beta available
 

Yes mutch

but

There is now a small problem with Videocamera.

When I start it, it does not get past the "starting camera" stage (unless it times out to standby) until I tap somewhere above the screen in the grey area where the "Videocamera" text is. When I do that, the settings/about/close menu drops down. Another tap gets rid of the menu and shows the camera image(s), with a blanked-out square where the menu was.

More details:

The initial "starting camera" message appears in a white-line frame, which after a short pause to is shifted up about 10 pixels, loosing the top and right lines of the frame and leaving a grey line on the bottom where the bottom white line of the frame was.

If I wait until the app says the camera is on standby and then tap on the little white box it shows me ("tap <box> to activate") almost the same thing happens - "starting camera" in white-line frame, no images BUT there's no upward shift - the top and right lines of the frame do however disappear.

If I wait and do it a second then it does wake up and show images correctly.

In all cases tapping "record" shows a full-screen and it starts recording as it should.

It this a window-priority-thing?

Re: I'm stuck - was Re: ANNOUNCE: Diablo-Turbo first beta available
 

Yes, it is a bug in X window compositing, which has been enabled by telescope.
As workaround you can start the camera app with the following command line:
The dbus-send command will cause a small empty notification in the tray, and that will remap the window.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I've just finished wading through all 43 pages in this Diablo Turbo thread. First off, thank you maacruz! I've just updated my first n800 to DT. The user interface is noticeably more responsive. And many folks have expressed their thanks for fixing numerous bugs related to freezing, crashing, and reboots. Thank you maacruz!

Next up... is a rehash of the original instructions for folks wondering if they missed something important between the 1st and last pages of this thread :-) Most of the discussion in this thread was related to folks not following the directions, troubleshooting bugs which were eventually fixed, or discussing work arounds for off topic or loosely connected subjects. If you follow the following, you should be fine... [caveat emptor, backups are golden, and the usual disclaimers...]

How to install:
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

enjoy...

Re: ANNOUNCE: Diablo-Turbo first beta available
 

@ggoebel:
Thanks for your refreshing rehash. Much easier to understand than mine.
With your permission, I'll put them in the first post

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Sure. Rehashing things is considerably easier than making them happen in the first place. Thank you!

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Thanks for the summary. However, the zImage file is downloaded and not mentioned again. What happens with it?

Re: ANNOUNCE: Diablo-Turbo first beta available
 

You can optionally flash it to update the kernel to the last testing release. See the updated first post.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I would tweak the instructions a bit more to make it clear that
1) zimage is optional before instructing to download
2) gps-driverguard.deb is not needed for N800 before instructing to download

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Anyone else noticing ramzswap taking a nosedive from time to time?

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Not here (current uptime 69 days), but my setup may be different:

/proc/version:

Linux version 2.6.21-omap1 (miguel@linux) (gcc version 3.4.4 (release) (CodeSourcery ARM 2005q3-2)) #23 PREEMPT Sun Jan 16 13:38:22 CET 2011

(I know I should upgrade at some point) I think my current modules were hand-built from the latest compcache + maacruz's patches, but I can't find the build dir in my scratchbox right now. In any case, they're:

/proc/ramzswap:
DiskSize: 131072 kB
NumReads: 139966
NumWrites: 61123
FailedReads: 0
FailedWrites: 0
InvalidIO: 0
NotifyFree: 15626
ZeroPages: 698
GoodCompress: 80 %
NoCompress: 4 %
PagesStored: 24130
PagesUsed: 7716
OrigDataSize: 96520 kB
ComprDataSize: 29204 kB
MemUsedTotal: 30864 kB

(insmod'ed with disksize_kb=131072 memlimit_kb=32768)

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I have, and I have disabled it from starting up.

I noticed that when running two or more large apps (i.e. canola, navit), while ramzswap was running, would see my n810 "bog-down" (get real slow) for several seconds. When I disabled ramzswap ("swapoff /dev/ramzswap0"), removed the kernel module ("rmmod ramzswap") and went back to using a dedicated partition for my swap space, things would run much more smoothly and consistently, even if slightly slower.

- John

Re: ANNOUNCE: Diablo-Turbo first beta available
 

What do you mean by "nosedive"?
Slowdown?

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Sorry, either crash or otherwise shut down.

I have sadly never caught it in the act, because my best indicator is that ASUI stops showing the orange long press indicator on the memory use readout.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Well, I just installed (or think I did) the CSSU and Diablo-Turbo.

When I enter , however, I get:

Was I supposed to actually get "noname" as part of the string (and not get "Nokia-N800-43-7"), or did I get to the new Diablo Turbo correctly?

The 43-7 in that string seems a bit surprising since "About Product" from the control panel says "Version: 5.2010.33-1". (5.2008.43-7 was the code for my pre-CSSU OS.)

The only oddity during installation was that I did not get an error about sysvinit on the main installation; I went ahead anyway and entered , which did produce an error (which I ignored).

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Did you download all debs, including "Previous release" ones?

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Sounds like you were using ramzswap only. That won't hold much data (especially with the default config) and so you can run out of virtual memory much earlier, causing the symptoms you describe. Canola and navit (is that stable these days btw?) probably store non-compressible data (images/sounds) which makes the situation worse.

IMO you really do need the swap file as well, just with a lower priority so that the compcache swap is used first while it has any space left.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Does it happen often enough that running syslogd would be useful?

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Good guess! Nope, I omitted those. I'll do it again tomorrow with those included. Thanks!