Re: ANNOUNCE: Diablo-Turbo first beta available
 

That date looks right, should be the "update 2" dt kernel.

"Nokia-N800-43-7" is just the hostname. It's set from the contents of /etc/hostname at boot time, and has nothing to do with (and is useless for identifying) the OS version. The CSSU doesn't change it either, that would be evil since some people prefer to set it to something else, or enter it in DHCP server configurations etc.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

It happens to me sometimes, but I think it always happened at boot, the times I checked syslog/dmesg showed nothing, and the last time I checked for /dev/ramzswap0 and it was there, and swapon worked just fine.
I guess that for some reason (may be some af-* script) it gets umounted.
I'll move the rc script to start later in the boot process to see if that fixes it.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Here its start order is S20, but I don't reboot very often. I also don't use ASUI (nothing against it, just never got around to trying it) either, not sure if its scripts and ramzez's have any unintended interractions.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Last DT kernel was 13mar2011 so you have it installed correctly.


Let me know the new levels if you change and release.


I don't think he meant ASUI was causing problems, just that swap disappeared and no longer showed in ASUI.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

i have no idea.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

i am getting a fair number of forced reboots lately. Not sure if it is my battery that is going bad (causing a certain power management system to crash, thanks Nokia), or if it is Opera that is causing something (usually what is running when it happens).

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Do /proc/bootreason & /var/lib/dsme/stats/lifeguard_resets point to anything specific?

When I had that it was always rebooting within a minute or two of plugging in, and never when not on the charger.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Will try to remember checking next time i get one.

Edit: had a look just for a lark (and as a reference point).

bootreason shows: 32wd to

when it comes to lifeguard_reset, i am guessing that the line with a * at the end is the one that was the most recent trigger.

if that's the case, then it was /usr/sbin/dsp_dld that cause the most resent reset event.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

That's
(not 'resets')

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Both can exist, lifeguard_restarts shows processes that died for whatever reason and were restarted by dsme, while lifeguard_resets shows processes that made dsme trigger a complete reboot.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Speaking of lifeguard_restarts, I just had a look at mine and saw:

I guess this is caused by gpsdriver_guard. This is mostly a cosmetic issue, but perhaps it could restart gpsdriver with dsmetool (or even /etc/init.d/gpsdriver) instead of just killing it?

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I have 5,052 lifeguard_resets due to bme_RX-34. And that's just counting since I last reformatted the thing.

Thanks, Nokia. I'm never buying anything you make ever again.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Yikes, that's a bit excessive! I didn't even know the bme bug was also affecting the N800 (mine's still wearing the battery that came with it back in 2007, and while it doesn't last too long it doesn't spontaneously reboot).

Warning: untested and might lead to reboot loop requiring reflash: it might be worth trying changing /mnt/initfs/linuxrc to start it with "dsmetool -t" instead of "-r".

Re: ANNOUNCE: Diablo-Turbo first beta available
 

LOL, that's nothing compared to my /usr/bin/gpsdriver/ 1808 *
Yes, it is caused by gpsdriver_guard, but I prefer just to use kill and let dsme do its job. While dsmetool could be an option, using the init.d script would be bloat.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I already had to replace mine about last year's summer for the same reason.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

hi,

I have installed DT on top of CSSU. It all seems fine - thanks for making this available.

I have found just one problem. I use Truecrypt 6.0a from here:

https://sites.google.com/a/securix.net/www/truecrypt52

It was working fine before installing DT, but now hangs after I enter the password to open a TC file. I'm pretty sure this is due to Fuse.

As you can see, there's a Fuse DEB on that site, which I had to install to get TC working, and I think that's what's been broken. I have installed the updated Fuse module that you supplied for DT, but that made no difference.

Any suggestions?

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Make sure you don't have the old fuse module hanging around. The same happened to me with sshfs: I built the new module, installed it and it still hung, wondered why until I saw the old module was still there and was loaded instead of mine. Once I removed it everything was fine.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I did uninstall the 2.7.3 Fuse deb that I had installed from Securix's site, using the Application Manager, but then TC complained that it couldn't find Fuse at all, even after installing your kernel module.

I'm guessing that you mean I need to remove the other fuse.ko file? Could you please explain how I do this?

Re: ANNOUNCE: Diablo-Turbo first beta available
 

All fixed. I found /usr/lib/fuse/fuse.ko and removed that, but after rebooting and trying TC again it complained that I needed to 'modprobe fuse', which I tried; that complained about a modprobe file, I can't remember which off-hand (possibly modprobe.dep).

So then I created a sym-link from /usr/lib/fuse/fuse.ko to your new fuse.ko file, rebooted and it's all fine. Thanks again for your help.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Sorry for interruption. There is an ongoing debate on the future of the maemo.org. I thought you might want to check it out.

http://talk.maemo.org/showthread.php?p=1069052

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Thanks for the heads up

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Ok, I need your help to decide if the last zImage kernel is good or not.
How many of you are running the last zImage testing kernel?
Do you have any issue?
How long is your uptime?

If you have installed the last zImage, please answer.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

@maacruz, any thoughts on maemo.org end-of-life?

Re: ANNOUNCE: Diablo-Turbo first beta available
 

How would I know? I don't remember when I installed or what I downloaded. There are no version numbers shown on the download page. I know how to check uname:
My point is, "the last" is not useful. A version number is useful.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

You have the last deb package (Mar 13), there was a zImage released in May that is "the last" kernel.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

And I would know that... how? There are no dates on the files at the garage page, and posting number 1 shows a MARCH update.

I repeat: a version number is useful. "Latest" is not.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

By comparing the date in the uname output you posted with the dates on the files page.

Linux Nokia-N800-23-14 2.6.21-omap1 #2 PREEMPT Sun Mar 13 23:29:39 CET 2011 armv6l unknown

Last DT test kernel 2011-05-16 03:00

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Running it for a month, works great, only one issue (might not be the kernel): every once in a while, after powering on my n800, screen won't go into power save but stays lit no matter how long I wait. Reboot solves the problem, but after the next reboot or shutdown problem usually happens again.

Don't have long uptimes because I often run it until battery is totally empty :)

Keep up the good work.

Siniša

Re: ANNOUNCE: Diablo-Turbo first beta available
 

auouymous told you how, use the release/build dates.
I can't use version numbers because the kernel image version number is fixed for compatibility reasons (closed source kernel modules), and the deb version number is a package version number, while testing kernels have no package.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Do you have ASUI or use alarms? If you don't use alarms you can try turning off the alarmd service so it doesn't start at boot. It is most likely a problem with ASUI's interaction with alarmd, assuming you have both running.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Yes, I am running ASUI, but not using alarms (using FlipClock for waking up, don't know if that counts?).

Yesterday did an "upgrade to latest testing version", but did not reboot N800 afterwards, so I don't know if that helped, but will see these days...

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I don't know if flipclock uses alarmd or not. You could try unchecking and stopping alarmd in asui-settings:Services and then set a test alarm in flipclock to see if it still works.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I am going on a vacation tomorrow, so will have plenty of time to experiment, and won't need waking up on time :) so will try turning off alarmd.

Btw, my n800 rebooted for no reason this morning :( while I was sleeping. When I woke up, uptime was 21 minutes

Re: ANNOUNCE: Diablo-Turbo first beta available
 

old battery perhaps? There is a known bug in the BME that results in a crash on sudden voltage drops (or something like that). And a BME crash results in a instant lifeguard initiated reboot.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I have it for a month or two. Usually while connected to charger.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I have another issue which might be related to the fuse.ko one solved earlier. I have a script that does insmod cifs.ko and then mount.cifs so I can connect to my router's hard drive (similar to the sequence described here: http://wiki.maemo.org/Accessing_Windows_CIFS though from memory I'm using files supplied by Qole).

However, with Diablo-Turbo installed I get a complaint that cifs.ko is already loaded (which appears to be true) and the mount.cifs command produces a seg fault.

Any thoughts on replacements for these files, or other methods of doing things? Wizard Mounter doesn't work for this particular router drive.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

It is not related to fuse.ko, since cifs is a diferent kernel module, but the problem is the same.
The solution should be the same, using a cifs.ko module built for the DT kernel.
I'll build one tomorrow if I possible.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Yes, sorry, that's what I meant by 'related to'. A new cifs.ko would be great, thank you. Do you think there are any other kernel modules that might be necessary with the N810 in the future?

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I'm with alexc in that I have had some issues with fuse, cifs, and nfs modules after installing diablo turbo. Really I usually drop files and such on to my n800 from a linux pc not the other way around so I have not noticed the problem till now. The other day I ran some old scripts to sshfs to my home server and they failed with a call for me to modprobe fuse. I made sure I was up to date on all the diablo turbo stuff and I couldn't find any old fuse modules laying around but I honestly don't know where to look. Unfortunately modprobe resulted in this:

I may have screwed this (modprobe) up else where but it seems like I should at least be able to get the fuse module loaded with insmod. . . If it matters it looks like I'm running the March 13th kernel.

Otherwise I am enjoying diablo turbo.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

DT fuse module is /lib/modules/2.6.21-omap1/extra/fuse.ko
If you have any other fuse module you should remove it.
modprobe doesn't work in diablo because it lacks depmod, so there is no modules.dep database (to save space I guess)