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

Page 5 of 16

« First

< Prev

Next >

Last »

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)

maacruz

2011-03-01 19:40

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by jstokes (Post 957283)

That still uses MPlayer (well, come to think of it, MPlayer "talks" to BlueZ which uses the DSP with dsp-sbc installed). There's no escape!

IMHO http://talk.maemo.org/showpost.php?p...&postcount=304 and http://talk.maemo.org/showpost.php?p...&postcount=354 (referring to http://talk.maemo.org/showpost.php?p...&postcount=350) seem promising

Thanks for pointing this. I'll add those improvements to DT, so people with BT headsets benefits from them.

auouymous

2011-03-01 23:59

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by maacruz (Post 958317)

That is correct. It's a remaining issue I still haven't fixed because... only happens at shutdown and it is really hard to debug since there is no console to dump messages at.

I've shutdown a lot the last week and haven't had any freezes but probably will now that I've said this. Can't you dump the messages to a rotating log file?

https://garage.maemo.org/plugins/scm...ui&view=markup

Line 1148 opens the log and line 400 writes to it. Just change the prefix so you don't overwrite my log file, add a setting to enable the log and have everyone with the shutdown problem enable it and send in their logs after it happens.

sondjata

2011-03-02 01:49

Re: ANNOUNCE: Diablo-Turbo first beta available

i do have the shutdown crash. My install is as of yesterday.

Addison

2011-03-02 15:52

Re: ANNOUNCE: Diablo-Turbo first beta available

This is abso freakin' lutely fabulous!

I'll test MPlayer later and post any noticable changes since I encode my videos beyond what my N800 can usually handle (720x480 *lol*).

So many thanks for this Mac! :swoon:

Addison

2011-03-02 17:58

Re: ANNOUNCE: Diablo-Turbo first beta available

Hey Mac, I've been using this cute little script extensively for quite some time. It always worked 100% of the time.
http://talk.maemo.org/showthread.php?t=70091

Since installing DT now, many times it just goes back to the same screen I was on.

It's almost like my hardware keys are automatically doing a double tap or something.

Can you explain this?

maacruz

2011-03-02 21:35

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by Addison (Post 959052)

There is nothing in DT that would affect X or key mappings, and in fact, I've run a couple of tests with xev first and xbindkeys later and found no repeated key events, as expected.
xbindkeys is very tricky with its xbindkeysrc file format, and any error like a missing/extra space means both scripts get executed at the same time, producing the observed behavior.

By the way, a simpler and cleaner way to achieve the same would be this .xbindkeysrc

Code:

"matchbox-remote -next"

    F7



"matchbox-remote -prev"

    F8

Addison

2011-03-03 08:46

Re: ANNOUNCE: Diablo-Turbo first beta available

Thanks Mac!

I'll try your suggestion and see if that cleans up the behavior.

But yeah, it always, always worked before, every single time.

Now, there are times when I'll have to press the key like 4 times before it actually changes the screen... so something is definitely different now.

Hopefully your new coding for this will take care of the issue since I love going from one app to another in a 10th of a second. :)

onion

2011-03-03 12:33

Re: ANNOUNCE: Diablo-Turbo first beta available

I finally had time to take a proper look at this. Installed today, seems to work fine.
But one bug, one of the postinst scripts, I think it was for the kernel package, complained about missing python. I don't have that installed and the package didn't require it. It did still install fine.

jwernerny

2011-03-03 18:14

Re: ANNOUNCE: Diablo-Turbo first beta available

I finally got around to backing up my N810 and installing DT...

WOW! There is definitely a perceived speed up and increased responsiveness. When run by itself, Canola seems to get through scanning for files much faster. Other applications also seem to start quicker.

I tried running Wesnoth, and it seems to load faster, but getting into the game does not seem much faster. The big change is that now I can do something else while waiting for Wesnoth to load a game instead of looking a an expensive brick.

As a side note, I have been adjusting a few VM related things that seem to also help with DT. Here's the script I use: (Note: I use swap on a dedicated partition on my removable SD card)

Code:

sysctl -w vm.swappiness=25

sysctl -w vm.min_free_kbytes=1024

swapon /dev/mmcblk1p2

swapoff /media/mmc2/.swap

- John

maacruz

2011-03-03 19:26

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by onion (Post 959627)

I assumed python was a Diablo requirement :-/, I'll add that as a dependency in the next kernel release.
Well, python is used to adjust the backup kernel image size, so your zImage backup is the whole mtd1 flash device. That wouldn't have to be bad by itself, except for a few hundred KB lost, but if what I've read about the development of 0xFFFF is correct, writing an image the same size of the mtd device will cause troubles. You better cut the size of /usr/share/Diablo-Turbo/backup/zImage-backup or you risk a reflash if you uninstall kernel-dt-sd.
Install python and then, as root:

Code:

echo -e 'import struct\n\

f=open("'"/usr/share/Diablo-Turbo/backup/zImage-backup"'","r+")\n\

f.seek(0x2C)\n\

l=struct.unpack("i",f.read(4))[0]\n\

f.seek(0)\n\

f.truncate(l)\n\

f.close()'|python -

Addison

2011-03-04 01:13

Re: ANNOUNCE: Diablo-Turbo first beta available

Yessssssh. :)

Please add Python in your next build so I can reflash my tablet without worries.

I always get so confused on how to install that junk.

Addison

2011-03-04 05:10

Re: ANNOUNCE: Diablo-Turbo first beta available

Okay Mac.

I changed that script to say F7 and F8 instead. No change.

Yeah, it's still being such an unbearable turd with me.

Just having Tear and DialCentral, there have been times where it takes me 8 clicks on the button before it actually changes apps.

Like say I'm using Tear, button clicky, then I'll see a peek of the Dial Central screen but it will land back on Tear.

It's now been like this over and over again since using DT.

Poops. :(

lma	2011-03-04 10:50

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by maacruz (Post 959897)

I assumed python was a Diablo requirement :-/, I'll add that as a dependency in the next kernel release.

Or just do the truncation with stuff present in the base install like perl:

Code:

open(Z, "+</usr/share/Diablo-Turbo/backup/zImage-backup") &&

sysseek(Z, 0x2C, 0) &&

sysread(Z, $l, 4) &&

truncate(Z, unpack("L", $l)) &&

close(Z);

(season with appopriate error handling to taste).

jmart

2011-03-05 13:39

Re: ANNOUNCE: Diablo-Turbo first beta available

In xterm when i type 'free' should i see my swap memory? I set my memory to use in the ramzez GUI to 25%, after installing DT, but I see 0 in xterm when I type 'free'.

I'm still getting the restart at shutdown error on a consistent basis. If there is anything I can do to help troubleshoot it please let me know --- although I am not the most savvy user (obviously), I would be glad to try and help.

Thanks!

elliott

2011-03-07 09:43

Re: ANNOUNCE: Diablo-Turbo first beta available

I installed this today and it has been working great, the tablet is much more responsive and is not crashing when under heavy load.

Everything seems to be great except I can no longer mount my NFS shares. Wizard Mounter sometimes says everything went fine, sometimes it locks. Doing it from the console doesn't work either, it just seems to hang. Even when Wizard Mounter says everything is fine the mount never shows up.

wnd	2011-03-07 10:21

Re: DT trouble

This is as vague as a problem report can be, so here goes nothing. I've been running the SD kernel on my N810 since the first version with working WPA2 version with little trouble. Today, however, was quite different: the screen wouldn't blank.

On my way to work this morning, I used my N810 to run Anki, just as I usually do. My device automatically logged in to WLAN in the tram, just as it usually does. When I got to work I was in a hurry to test some things online. Instead of having my device connect automatically to our office WLAN, I opened connection dialog and accidentally chose BT connection. I quickly disconnected and connected to WLAN instead. Something clearly went wrong as I didn't receive any DNS server IPs. I tried to switch back to BT connection but this also failed. Connection problems like this are nothing uncommon, so I routinely rebooted. After rebooting everything was back to normal -- or so I thought.

After finishing things I needed to check I started working on things I get paid to work on. After a few minutes I noticed that display of my device was still on. I SSHd to the device and checked if there was anything interesting in kernel log. Nope. I restarted systemui to see if that helped. Nope. I tried running advanced-systemui to see if that helped. Nope. I went to control panel to see if adjusting screen brightness worked. Yup, that worked, but ambient light sensor would only dim the screen. I rebooted again (twice) and noticed that while the screen backlight was not turned off, screen updates would not take place after leaving the device idle for awhile. This was easy to spot by having top running on SSHd connection and load applet running in status bar, as the two would show different data. Running out of ideas, I uninstalled DT and rebooted with community SSU kernel to see if /that/ helped. Indeed, that solved the display issue.

This is odd. Apart from initial issued and "delayed" screen updates after turning on the display, I have had minimal trouble with DT SD kernel -- until today. Today this problem caught me completely off-guard, and I have no idea what is going on. As there was absolutely nothing in kernel log, I have nothing to go on with.

I will switch back to DT kernel when I can, but since I have to be able to depend on my device for next ~ten days, it'll have to wait.

maacruz

2011-03-07 12:26

Re: DT trouble

Quote:

Originally Posted by wnd (Post 962368)

This is as vague as a problem report can be, so here goes nothing. I've been running the SD kernel on my N810 since the first version with working WPA2 version with little trouble. Today, however, was quite different: the screen wouldn't blank.

....
After a few minutes I noticed that display of my device was still on. I SSHd to the device and checked if there was anything interesting in kernel log. Nope. I restarted systemui to see if that helped. Nope. I tried running advanced-systemui to see if that helped. Nope....

mce is the culprit, some bug in there, but since it is Nokia "added value" closed source... And yes, it is annoying when it happens.
Restarting mce ("/etc/init.d/mce restart") solves the issue.

P.S: I'm a bit quiet lately because I'm working in the kernel again, trying to fix the shutdown issue that, as I said, it is really hard to debug without a console.

wnd	2011-03-07 12:42

Re: DT trouble

Quote:

Originally Posted by maacruz (Post 962423)

mce is the culprit, some bug in there, but since it is Nokia "added value" closed source... And yes, it is annoying when it happens.
Restarting mce ("/etc/init.d/mce restart") solves the issue.

Thanks, I'll try to keep that in mind. Still, I find it a little strange that restarting the whole system didn't do the trick (unless mce was b0rken at system start already).

maacruz

2011-03-07 12:43

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by elliott (Post 962345)

NFS depends on kernel modules, and the kernel modules you have probably aren't compatible with the DT kernel.
You need the following modules built for the DT kernel: sunrpc.ko, lockd.ko, nfs.ko
I'll provide them later.

maacruz

2011-03-07 12:47

Re: DT trouble

Quote:

Originally Posted by wnd (Post 962434)

Thanks, I'll try to keep that in mind. Still, I find it a little strange that restarting the whole system didn't do the trick (unless mce was b0rken at system start already).

It looks like some race condition. It seems to happen only at startup, I guess because the high system load.

maacruz

2011-03-07 12:55

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by jmart (Post 961200)

In xterm when i type 'free' should i see my swap memory? I set my memory to use in the ramzez GUI to 25%, after installing DT, but I see 0 in xterm when I type 'free'.

Yes, you should see it. "cat /proc/swaps" should show all your swap devices and you should see /dev/ramzswap0 there, "ls /dev/ramz*" should show the ramzswap device entry, and "cat /proc/ramzswap" the usage stats.
If it is not there, try restarting it from xterm as root ("/etc/init.d/ramzswap restart")

Straycat

2011-03-07 12:57

Re: ANNOUNCE: Diablo-Turbo first beta available

I have gotten same "screen won't blank" thing a few days ago.

In my case I suspect about high load scenario. The device freezes and I reboot it. Then it happened.

Restarting once won't solve it. Nor restarting twice. Restarting third time do the trick.

Sorry for bad english.

maacruz

2011-03-07 13:07

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by lma (Post 960408)

Or just do the truncation with stuff present in the base install like perl:

Code:

open(Z, "+</usr/share/Diablo-Turbo/backup/zImage-backup") &&

sysseek(Z, 0x2C, 0) &&

sysread(Z, $l, 4) &&

truncate(Z, unpack("L", $l)) &&

close(Z);

(season with appopriate error handling to taste).

I do not do perl, too arcane for me to learn, but I'll happyly use your code snippet.
While you're at it, why don't you add the equivalent of "if filesize(Z)<$l: exit(1)" before truncate?

skatebiker

2011-03-08 09:08

Re: ANNOUNCE: Diablo-Turbo first beta available

Looks good, I'll try.

But a few questions:

uninstalling can just be done by

Code:

dpkg -r *.deb

?

in the folder where the debs exist.

And does the sysvinit fix the spontaneous reboot issue ?

wnd	2011-03-08 09:54

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by skatebiker (Post 963013)

uninstalling

When uninstalling, dpkg takes package names, not filesnames. Also, it's better to use apt-get when possible as unlik dpkg, it also takes care of package dependencies. If you want to remove just the kernel, use the following. This command will automatically uninstall ramzswap-dt (and probably dt-init-scripts).

Code:

apt-get remove kernel-dt-sd

Uninstalling the other packages -- or actually reverting to old versions -- isn't trivial but certainly doable. However, it's not neccessarily recommended. :-)

skatebiker

2011-03-08 11:34

Re: ANNOUNCE: Diablo-Turbo first beta available

No, when all goes right I do not want to revert.
I just ask it in case it goes wrong. My N810 works fine except the spontaneous reboots sometimes more than once a day. And as bonus it is faster.

I'll try.

jmart

2011-03-08 16:57

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by maacruz (Post 962449)

restarting from xterm as root worked, when I typed free I then saw my swap memory. However, after restarting my N810 I am back to 0 swap memory until I restart ramzswap in xterm again. Any ideas? Thanks again!

skatebiker

2011-03-08 20:06

Re: ANNOUNCE: Diablo-Turbo first beta available

The installing worked flawlessly. But running uname -r returns 2.6.21 is that OK ?
I see further no differences and the reboot issue is NOT resolved: two hours after the update the device rebooted spontaneously (Tear browser was running).

Did I something wrong ?

UPDATE: After half an hour it rebooted AGAIN, while Tear browsers was running.
Is this a problem in the tear browser ?

UPDATE2: After another 30 minutes (starting Firefox / Fennec , surfing a bit and closed it) it rebooted again (3rd time) !

So this patch does not help at all.

maacruz

2011-03-08 23:52

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by jmart (Post 963299)

Check that the /etc/rc2.d/S??ramzswap link is there.

maacruz

2011-03-08 23:56

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by skatebiker (Post 963433)

The installing worked flawlessly. But running uname -r returns 2.6.21 is that OK ?

Yes

Quote:

I see further no differences and the reboot issue is NOT resolved: two hours after the update the device rebooted spontaneously (Tear browser was running).

Did I something wrong ?

UPDATE: After half an hour it rebooted AGAIN, while Tear browsers was running.
Is this a problem in the tear browser ?

UPDATE2: After another 30 minutes (starting Firefox / Fennec , surfing a bit and closed it) it rebooted again (3rd time) !

So this patch does not help at all.

No, this patch doesn't solve issues with faulty hardware or old batteries, I never promised such a thing.

jmart

2011-03-09 01:00

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by maacruz (Post 963584)

Check that the /etc/rc2.d/S??ramzswap link is there.

The /etc/rc2.d/S31ramzswap file is there.

skatebiker

2011-03-09 07:52

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by maacruz (Post 963587)

Yes

No, this patch doesn't solve issues with faulty hardware or old batteries, I never promised such a thing.

Faulty hardware ?
Old batteries ?

The battery is renewed 6 months ago and how do you think I have 'faulty hardware' ?
It is the same unmodded N810 as I bought it in Sept 2008.

And I do not assume that you promised a proper working it is just a question.

maacruz

2011-03-09 08:17

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by skatebiker (Post 963813)

Faulty hardware ?
Old batteries ?

The two main causes for spontaneus reboots

Quote:

The battery is renewed 6 months ago and how do you think I have 'faulty hardware' ?
It is the same unmodded N810 as I bought it in Sept 2008.

I think it is a hardware fault, either the battery or the device, because you refer spontaneous reboots, independently of the software.
Now, about your new battery.... it is a real Nokia one or another brand, Mugen in particular?

lma	2011-03-09 10:35

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by maacruz (Post 962456)

I do not do perl, too arcane for me to learn, but I'll happyly use your code snippet.
While you're at it, why don't you add the equivalent of "if filesize(Z)<$l: exit(1)" before truncate?

Just for the hell of it, I had a go at doing it in a shell script, using only what's provided by busybox and without "cheating" by using other interpreters like awk, sed etc. It turned out to be surprisingly tricky to get the 32bit int in decimal format without having something like od(1), but here goes anyway:

Code:

#!/bin/sh



dd if=zImage-backup of=l skip=44 count=4 bs=1

b=$(echo $(echo -n '0000' | cmp -l l | cut -c3-5))

read a b c d <<EOF

$b

EOF

rm l



eval $(printf "l=\$(( (((0$d \* 256 + 0$c) \* 256 + 0$b) \* 256 + 0$a) ))")



s=$(echo $(ls -l zImage-backup) | cut -f5 -d" ")

if [ "$s" -gt "$l" ] ; then

        dd if=zImage-backup bs=$l count=1 of=zImage-backup.new && \

        mv -f zImage-backup.new zImage-backup

fi

Improvements welcome ;-)

skatebiker

2011-03-09 11:10

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by maacruz (Post 963828)

The two main causes for spontaneus reboots

I think it is a hardware fault, either the battery or the device, because you refer spontaneous reboots, independently of the software.
Now, about your new battery.... it is a real Nokia one or another brand, Mugen in particular?

The battery is an original Nokia one ordered via eBay.
The only possible hardware fauly might be the MMC1 card which is a 3rd party Micro SD card in a Mini adapter. Can that be qa problem ?
I did not alter anything in the hardware other than replacing the battery and entering an external SD into it. And I never dropped it or spilled water onto it.

In earlier posts I read that the spontaneous reboots were because of a firmware bug which triggers the watchdog inadvertently. And with the better handling of events / watchdog in your improved kernel I hoped this problem would be solved. Now this is not the case then it can be a hardware problem.

maacruz

2011-03-09 12:13

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by skatebiker (Post 963924)

The battery is an original Nokia one ordered via eBay.

Ebay, uhmmm, I wouldn't be very sure it is really Nokia. Well, may be the problem is the same as with Mugen ones, loose contacts. Put a piece of thick paper or cardboard at the battery's bottom, so it is hold tight against the device's battery contacts.

Quote:

The only possible hardware fauly might be the MMC1 card which is a 3rd party Micro SD card in a Mini adapter. Can that be qa problem ?

It could be possible, but I think it's unlikely. I'd bet on the battery.

Quote:

In earlier posts I read that the spontaneous reboots were because of a firmware bug which triggers the watchdog inadvertently. And with the better handling of events / watchdog in your improved kernel I hoped this problem would be solved. Now this is not the case then it can be a hardware problem.

Not the watchdog, it is bme what triggers the reboot, and usually happens with old/weak batteries. The watchdog only triggers if the device hangs or becomes so busy that the watchdog isn't refreshed in 20 seconds.
My kernel makes unlikely the later by distributing the cpu more evenly.

maacruz

2011-03-09 12:20

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by lma (Post 963898)

Code:

#!/bin/sh



dd if=zImage-backup of=l skip=44 count=4 bs=1

b=$(echo $(echo -n '0000' | cmp -l l | cut -c3-5))

read a b c d <<EOF

$b

EOF

rm l



eval $(printf "l=\$(( (((0$d \* 256 + 0$c) \* 256 + 0$b) \* 256 + 0$a) ))")



s=$(echo $(ls -l zImage-backup) | cut -f5 -d" ")

if [ "$s" -gt "$l" ] ; then

        dd if=zImage-backup bs=$l count=1 of=zImage-backup.new && \

        mv -f zImage-backup.new zImage-backup

fi

Improvements welcome ;-)

LOL :D :D
Looks like it was inspired by the robodevil, straight from the robohell :D :D
I had my own way with hellish shell scripting when I implemented amarok's 1.4 replaygain plugin in bash. Never again :D :D :D

jmart

2011-03-09 15:07

Re: ANNOUNCE: Diablo-Turbo first beta available

Any suggestions on why my ramzswap doesn't seem to be working properly would be appreciated. I think it's an important part of DT and I would like to get it working, but it's a little beyond my scope.

/etc/init.d/ramzswap restart in xterm as root worked, when I typed free I then saw my swap memory. However, after restarting my N810 I am back to 0 swap memory -- until I restart ramzswap in xterm again

Thanks!

maacruz

2011-03-09 15:31

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by jmart (Post 964065)

Please, check if after a fresh restart the /dev/ramzswap0 device is there.

auouymous

2011-03-09 15:34

Re: ANNOUNCE: Diablo-Turbo first beta available

@ skatebiker
Try passing --enable-rd-mode --set-rd-flags=no-lifeguard-reset -R to the flasher and see if your device stops rebooting. This won't reflash, it just turns on R&D mode and disables the the watchdog reset.

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

Page 5 of 16

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

vBulletin® Version 3.8.8