maemo.org - Talk - ANNOUNCE: Diablo-Turbo first beta available

Page 15 of 16

« First

< Prev

Next >

Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)

- OS2008 / Maemo 4 / Chinook - Diablo (https://talk.maemo.org/forumdisplay.php?f=29)

- - ANNOUNCE: Diablo-Turbo first beta available (https://talk.maemo.org/showthread.php?t=69740)

buurmas

2011-12-12 18:09

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by tso (Post 1136578)

So your not using Advanced System UI, Buurmas?

That's right. I've delayed installing ASUI for this very reason -- to try to better isolate this problem.

Quote:

Originally Posted by maacruz (Post 1136638)

Try restarting systemui after restarting mce

Doing "systemui" or "systemui restart" from the terminal gives me an error message. But see below:

Quote:

Originally Posted by Addison (Post 1136639)

I don't think that I have ever experienced the non-dimming bug, but I have lost the power button a few times.

Try this instead next time to avoid rebooting.

sudo /etc/init.d/mce restart

Ahhhh... sudo make a sandwich. That did it. Call me stupid if you like. I'm going to add sudo to my Personal Menu item as well. Thanks all!

Addison

2011-12-12 18:26

Re: ANNOUNCE: Diablo-Turbo first beta available

^ You're a goof.

Thanks for the chuckle. :)

tso	2011-12-12 19:18

Re: ANNOUNCE: Diablo-Turbo first beta available

Ah yes, that. I recall noticing that MCE behaved differently depending on being restarted via user rights or root rights. And it was very damn subtle about it.

Still, that the dimming issue shows up for someone not using ASUI seems to indicate a turbo issue.

And on that note, i have not had the dimming issue the last couple of times my N800 have been booted using the charger and then entered the maemo desktop by way of a power button long press. Then again, i use ASUI.

auouymous

2011-12-12 20:47

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by buurmas (Post 1136555)

In these times, restarting mce has solved the screen dimming problem, but the power button still doesn't pull up the system ui menu. I have to reboot to get that back.

Have you ever had ASUI installed? The dimming problem was thought to be an issue between alarmd and ASUI which persists even if you revert back to SystemUI.

I know ASUI is incorrectly dismissing alarms because the interface I found was wrong and I also know that ASUI is telling alarmd that the system is booted up even when in the charging runlevel. Both of these problems have been fixed but haven't been tested and released yet.

This changes everything if you have never used ASUI as it becomes a problem between alarmd and DT which might be harder to find. Anyone out there have a device not running DT and experiencing the alarmd problem with ASUI?

buurmas

2011-12-13 13:20

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by auouymous (Post 1136799)

Have you ever had ASUI installed? The dimming problem was thought to be an issue between alarmd and ASUI which persists even if you revert back to SystemUI.

I have certainly never had ASUI running on my machine. I'm pretty sure that I didn't start trying to install it & then stopped. (I'm just trying to be careful in my answer b/c I've thought about installing it many times.)

I have also had times where the alarm went off five minutes after it was supposed to, which is kind of odd. I think it only did that after installing DT. I've also had times where I've awakened on my own to find the alarm dialog sitting open but without making any alarm sound, although I am not certain that this wasn't because of my volume setting.

maacruz

2011-12-13 17:28

Re: ANNOUNCE: Diablo-Turbo first beta available

It is a mce bug.
mce sends a signal to systemui when the power button is pressed, then systemui shows the power menu button. Also, mce is responsible for dimming, and mce is related to alarmd.
I've suffered this issue before installing ASUI, and I have done may be a hundred tests trying to find a workaround or a fix before finally giving up.
Since mce has nothing to do with the kernel, it is not caused by the kernel (or otherwise many programs would crash or exhibit other symptoms).
It is caused by a race condition (http://en.wikipedia.org/wiki/Race_condition) in mce, probably related to gconf. The relation of the kernel here is that, for the different timing caused by the different schedulers, this mce bug is exposed when using other schedulers than O1.
How do I know that?
I saw it appear with the first alpha kernels, with both CFS and the SD schedulers, preemption or not. So it happens with two different schedulers, and the only thing affected by a scheduler is timing.
With the new gconf packages (which also have increased performance) it disappeared for me.
So yes, DT may expose this bug, and I can do nothing to fix it, short of rewriting the whole mce thing because it is closed source.

buurmas

2011-12-13 19:30

Re: ANNOUNCE: Diablo-Turbo first beta available

Well, that seems to put everything into perspective. Thanks, maacruz, for the additional detail into what I assume you have been telling us for some time now.

Quote:

Originally Posted by maacruz (Post 1137109)

With the new gconf packages (which also have increased performance) it disappeared for me.

Which packages are those? Is it an option for the rest of us to install them to fix this problem?

maacruz

2011-12-13 20:36

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by buurmas (Post 1137164)

Well, that seems to put everything into perspective. Thanks, maacruz, for the additional detail into what I assume you have been telling us for some time now.

Which packages are those? Is it an option for the rest of us to install them to fix this problem?

gconf2_2.16.0-1osso15_armel.deb and libgconf2-6_2.16.0-1osso15_armel.deb
You already should have them installed just by following the first post instructions.
Since very few people has noticed this issue, I guess the probability of it happening may be increased by some other package, although I can't discard some other possible influence

auouymous

2011-12-13 20:50

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by maacruz (Post 1137109)

So who has this problem and wants to try installing powerlaunch and only enabling its MCE replacement? We don't have to rewrite MCE when powerlaunch already does that, just need to fill in any incomplete areas. I can fork the MCE service into its own package if it fixes the problem and works well enough.

I should have some free time in the next week or two to finish up the current batch of ASUI fixes and will then play around with powerlaunch's MCE if no one else has. Although it would be better if someone who has the problem frequently tested powerlaunch's MCE since I have only ever had alarmd running when performing tests and can't properly test it under real world conditions.

Addison

2011-12-14 00:28

Re: ANNOUNCE: Diablo-Turbo first beta available

Would I have to drop ASUI to be a tester for this?

I really like everything you have done with it and would rather keep this if possible. :)

auouymous

2011-12-14 00:47

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by Addison (Post 1137260)

Would I have to drop ASUI to be a tester for this?

No, it can be tested with SystemUI or ASUI. You just need the DT kernel and alarmd. But you (Addison) can't test it. You have scripts that start and stop mce, and this would break your scripts. Changing mce to powered in your scripts would also be a bad idea since powered will restart mce when you stop it and stop mce when you start it. Sorry.

With ASUI:

Code:

apt-get install powerlaunch

/etc/init.d/powerlaunch stop

/etc/init.d/osso-systemui stop

update-rc.d -f powerlaunch remove

With SystemUI:

Code:

apt-get install powerlaunch

/etc/init.d/powerlaunch stop

update-rc.d -f powerlaunch remove

Execute those commands as root and you should now have powered instead of MCE. Let me know if anything stops working and if it fixes the dimming and power button issues.

Addison

2011-12-14 01:32

Re: ANNOUNCE: Diablo-Turbo first beta available

Yeah, I stop MCE quite often so that I can have full use with the Escape, Menu, and Home hardware keys for gaming and stuff.

Poopers. Wish I could help.

auouymous

2011-12-14 01:36

Re: ANNOUNCE: Diablo-Turbo first beta available

Okay, so powered won't replace MCE in its current state. There are some locking issues with it on my n810. And it won't devlock either.

If you installed it run the following to get rid of it:

Code:

apt-get remove powerlaunch

dpkg -P powerlaunch

And if you use ASUI run:

Code:

/etc/init.d/osso-systemui stop

I'll try to fork it and fix the issues later on.

buurmas

2011-12-14 18:49

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by auouymous (Post 1137277)

I'll try to fork it and fix the issues later on.

Many thanks, auouymous. I will offer to test your work (particularly since it sounds like it can be readily uninstalled without reflashing in case of a problem).

earksiinni

2012-01-09 00:56

Re: ANNOUNCE: Diablo-Turbo first beta available

How did I not know about this before???? Thanks a lot, these updates are really fantastic! I can't believe Nokia didn't implement them before they shipped the tablets, especially the scheduler. Had the N800 been shipped as responsive as it is with Diablo Turbo, Nokia might not have been sold off to Microsoft...

maacruz

2012-01-09 08:41

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by earksiinni (Post 1147669)

You lived last year in a cave? :D

efeertugrul

2012-02-12 13:28

Re: ANNOUNCE: Diablo-Turbo first beta available

Hi there.
I am a newbie. My uncle gave me his n800 (he doesn't use it any more). My question is: Is it a stable version?

auouymous

2012-02-12 13:52

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by efeertugrul (Post 1163922)

Hi there.
I am a newbie. My uncle gave me his n800 (he doesn't use it any more). My question is: Is it a stable version?

There are work arounds for all instabilities. :)

efeertugrul

2012-02-14 18:45

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by auouymous (Post 1163936)

There are work arounds for all instabilities. :)

I fear. Because i can't trust my self. If i do exactly as the first post can i be succesful?

auouymous

2012-02-15 04:28

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by efeertugrul (Post 1165066)

I fear. Because i can't trust my self. If i do exactly as the first post can i be succesful?

I don't use alarmd or anything that requires special kernel modules so DT kernel works perfect and makes my device so much better. You may experience problems with the screen not turning off after boot if you use alarms but there is a script you can run each time it happens to fix it.

jutley

2012-04-23 13:22

Re: ANNOUNCE: Diablo-Turbo first beta available

i really want to install this but need some help which files precicly do i need to download for install?

auouymous

2012-04-23 13:39

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by jutley (Post 1196349)

i really want to install this but need some help which files precicly do i need to download for install?

The first post has precise instructions, don't attempt to install without reading the entire first post.

jutley

2012-04-27 13:41

Re: ANNOUNCE: Diablo-Turbo first beta available

I can do this I can do this I read the whole post and going for it.

jutley

2012-04-27 14:52

Re: ANNOUNCE: Diablo-Turbo first beta available

I get e: couldn't find package osso-software-vershion-rx44-unlocked

I have extras devel enabled and cssu repo stable.

I am stuck now it won't install apt get rx44 couldn't findit help

lma	2012-04-27 18:03

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by jutley (Post 1198235)

I get e: couldn't find package osso-software-vershion-rx44-unlocked

Looks like a typo, try without the "h".

jutley

2012-04-27 22:39

Re: ANNOUNCE: Diablo-Turbo first beta available

Ok all done and worked thank you it indeed was a typo on my end.

efeertugrul

2012-04-29 17:26

Re: ANNOUNCE: Diablo-Turbo first beta available

can you help me. I tried to install.
everything went fine but "cd /media/mmc1/dt"
it says /bin/sh: cd: can't cd to /media/mmc1/dt

maacruz

2012-04-29 19:03

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by efeertugrul (Post 1199135)

can you help me. I tried to install.
everything went fine but "cd /media/mmc1/dt"
it says /bin/sh: cd: can't cd to /media/mmc1/dt

Follow the install instructions to the letter:

Quote:

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

You can create the directory with the file manager (create a new folder in the external SHDC card and name it "dt").
Then proceed from here.

drautzburg

2012-05-25 17:06

Re: ANNOUNCE: Diablo-Turbo first beta available

Just installed DT and everything looks fine. Just one question:

what are the files in /usr/share/Diablo-Turbo/initfs-modules good for? They seem to be newer than the ones in /mnt/initfs

drautzburg

2012-05-25 18:09

Re: ANNOUNCE: Diablo-Turbo first beta available

Oh I see, those files end up in /mnt/initfs/lib/modules/2.6.21-omap1.

The strange thing is that /mnt/initfs/lib/modules/current is a symlink which points to /lib/modules/2.6.21-omap1 and /lib/modules/current also points there. These three locations seem to contain older versions (on my n810)

I remember vaguely that I once messed with the symlinks. Can someone please look up what these symlinks should look like. I am worried I am loading the wrong modules.

maacruz

2012-05-26 16:12

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by drautzburg (Post 1212475)

I remember vaguely that I once messed with the symlinks. Can someone please look up what these symlinks should look like. I am worried I am loading the wrong modules.

You're not. Don't mess with the symlinks.

buurmas

2012-05-29 14:30

Re: ANNOUNCE: Diablo-Turbo first beta available

Minor new factoid about the alarm problem. Last night I set the alarm before I went to bed. Later that night, our young one cried and I woke up and noticed that my screen was on. (I have an aging battery and sometimes when I'm charging my N810 overnight I get spontaneous reboots. I'm guessing that's what happened.) I ran the "restart MCE" script (described elsewhere in this thread) and went back to sleep. I woke up an hour after my alarm was supposed to go off. I tapped the screen of my N810 and then the alarm went off. The alarm said 6:20 even though it was clearly 7:10 now. Somehow the system wasn't properly monitoring when to fire the alarm.

To make a long story short, the apparent take-away: don't run "restart MCE" before your alarm goes off.

auouymous

2012-05-29 20:45

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by buurmas (Post 1214409)

I woke up an hour after my alarm was supposed to go off. I tapped the screen of my N810 and then the alarm went off. The alarm said 6:20 even though it was clearly 7:10 now. Somehow the system wasn't properly monitoring when to fire the alarm.

Was it ASUI's alarm screen that said 6:20?

drautzburg

2012-11-24 13:21

Re: ANNOUNCE: Diablo-Turbo first beta available

cifs.ko

Where do I find the correct version of cifs.ko. The one posted in the garage only seems to work with the "Last DT test kernel" zImage but not with kernel-dt-sd_2.6.21-3_all.deb. Or is the "Last DT test kernel" zImage the one to use anyways?

uname

As a side note, what should kernel-dt-sd_2.6.21-3_all.deb report in uname -a? I recall I saw a "... #2 ..." and the "last zImage" reported "... #3 ...". Is this correct? I was thinking the the number after the "#" corresponds to the number after the hyphen in the .deb.

maacruz

2012-12-01 17:57

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by drautzburg (Post 1297871)

It has been so long I don't remember which kernel build I used to build cifs.ko, probably the last one. Since it is an standalone module, use it with whatever version it works.
Regarding the differences between the zImage in the deb and the standalone zImage, there are almost none except for a few lines in the touchscreen driver.

Quote:

uname

As a side note, what should kernel-dt-sd_2.6.21-3_all.deb report in uname -a? I recall I saw a "... #2 ..." and the "last zImage" reported "... #3 ...". Is this correct? I was thinking the the number after the "#" corresponds to the number after the hyphen in the .deb.

Both versions report the same build number in uname, differing by date.

Addison

2013-01-09 09:58

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

You can configure what frequency you want by editing /etc/kernel-dt-tunables and running "/etc/init.d/kernel-tunables restart"

I don't have either one of these two files.

I'm booting from MMC2.

[1|user@Nokia-N800-43-7|~]uname -a

Linux Nokia-N800-43-7 2.6.21-omap1 #1 PREEMPT Wed Sep 21 22:48:31 CEST 2011 armv6l unknown

Any ideas on this?

Addison

2013-01-10 06:22

Re: ANNOUNCE: Diablo-Turbo first beta available

One other thing... I seem to be having some issues with Modest as of today.

Before, Modest would suddenly stop working like maybe once a month or so.

It now has stopped on me 4 or 5 times already just within the past 24 hours.

This is the script I use to start it back up again.

Code:

gconftool-2 --type bool --set /apps/modest/accounts/AccountID/enabled True

gconftool-2 --type int --set /apps/modest/update_interval 1

gconftool-2 --type boolean --set /apps/modest/auto_update True

/usr/bin/modest

I really like having one minute check intervals but is there something here that doesn't sit well with Diablo Turbo?

Thanks. :)

maacruz

2013-01-14 09:48

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by Addison (Post 1312660)

Do you have dt-init-scripts installed (in mmc2)?

maacruz

2013-01-14 09:53

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by Addison (Post 1313106)

Code:

gconftool-2 --type bool --set /apps/modest/accounts/AccountID/enabled True

gconftool-2 --type int --set /apps/modest/update_interval 1

gconftool-2 --type boolean --set /apps/modest/auto_update True

/usr/bin/modest

I really like having one minute check intervals but is there something here that doesn't sit well with Diablo Turbo?

Thanks. :)

I don't see how it could be related.
Did you reboot and the problem persists?

Addison

2013-01-14 09:57

Re: ANNOUNCE: Diablo-Turbo first beta available

Hey Mac.

I installed the following without any errors.

dbus_1.0.2-0osso16_armel
dbus-1-utils_1.0.2-0osso16_armel
kernel-dt-sd_2.6.21-3_all
libdbus-1-3_1.0.2-0osso16_armel
mini-rc_0.2.11-3_all
ramzswap-dt_0.5.5-5_armel
zImage

By the way, watching YouTube videos as they download is such a super huge improvement than before this.

Your upgrades really work. :)

All times are GMT. The time now is 21:55.

Page 15 of 16

« First

< Prev

Next >

Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8