Re: ANNOUNCE: Diablo-Turbo first beta available
 

NEWS:
After many shutdowns, tests, logs, get the N8x0 emulated in qemu to get a console, patches and kernel rebuilds, I finally located the "reboot at shutdown" bug, hidden in the arm assembler kernel code of the Diablo kernel. It's triggered by preemption at kernel level and its effects are not clear. In addition of shutting down normally, after applying the fix I couldn't reproduce the mce "screen doesn't turn off" issue, so it could be caused by this bug too.
Surprisingly, I also learned that the Diablo kernel is 2.6.21.0+omap with almost no bugfixes, while stable mainline reached 2.6.21.7 before Diablo was discontinued, so while I was at it, I imported all applicable bugfixes from 2.6.21.7, and then some from 2.6.22.x after the 2.6.21 end of line, making a grand total of 62 bugfixes.
The new feature of this kernel is the BT UART FIFO optimization patch, for people using a2dp.
Everyone is encouraged to test this kernel, specially those who use Bluetooth with headsets or for inet/transfers.

New testing kernel: Deleted

Re: ANNOUNCE: Diablo-Turbo first beta available
 

how do we install zimage

Re: ANNOUNCE: Diablo-Turbo first beta available
 

From the device: "fiasco-flasher -f -k /media/mmc1/dt/zImage" (assuming the kernel is in /media/mmc1/dt), then reboot
From your linux pc: "flasher-3.0 -f -k /whereverthekernelis/zImage -b"

from maacruz

Re: ANNOUNCE: Diablo-Turbo first beta available
 

:')

thanks!!!

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I checked after a fresh restart and /dev/ramzswap0 is there. Is there anything I should check for next? Thanks!

Re: ANNOUNCE: Diablo-Turbo first beta available
 

How can I revert to the old kernel ?

Since I installed the new kernel, the device reboots when using the Tear browser, streamripper, etc.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

apt-get remove kernel-dt-sd

Try entering flight mode and then starting tear with a local file or just leave it running with no webpage, does it reboot? Try turning on wifi with no programs running, does it reboot?

I have the watchdog timer disabled so it won't reboot and if I turn on wifi, even briefly, my battery temp jumps 10C in a few minutes and dies in an hour or two with no cpu load.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

With wifi on and no progs running (browserd is disabled) it also reboots, on average once a day.
I affixed the battery with a piece of cardboard at the bottom of the battery (advice of @maacruz, thanks) so it is more firmly placed and is now excluded as a reboot cause.

Can I check that really all parts of the new kernel are installed ? It seems the watchdog timer is still enabled. I installed all 11 files and this procedure seemed to work flawlessly.
But the reboot issue is still there.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I installed the new kernel and no freezes at shutdown since, awesome!

I'm still having the issue with my swap memory though. Everything went fine with my DT install, so I am surprised that no one else seems to have this issue. Anyway, I appreciate the help and suggestions so far. After a fresh restart the /dev/ramzswap0 is there. Any ideas?

Thanks again!

Re: ANNOUNCE: Diablo-Turbo first beta available
 

The init script runs at startup, so the swap memory is activated, but later during the boot swap is turned off.
What setup do you have with respect to swap?

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I'm not totally sure what you mean by "what setup do you have with respect to swap?" I was using ramzez prior to installing DT. I set the swap % in ramzez once and then it kept it and I never really thought about it again until now. If there is somewhere specific I can look at on my N810 let me know and I'll get that info back to you ASAP. Thanks!

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Unit (WiMax version) has been very stable for last 36 hours (it rebooted one time, first time that has ever happen that I am aware of).

Trying to do a shutdown via the advanced-power app will cause a reboot on the first try then on the second it will shutdown. This seems to happen after the unit has been up for a few hours (not all the time). I suspect advanced-power or advanced-backlight or advanced-power-monitor or all of them are conflicting with Diablo-Turbo.

Web pages loads faster, most of the time.

I would recommend this kernel over the last one since I was not able to get that one to work. :)

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Flakey and/or dying batteries will indeed cause reboots. My N810 runs unmodified Diablo, and it still has its original battery, which obviously is getting seriously old in the tooth... lately it started rebooting by itself each time I connect the charger to top it off, which is a typical end-of-life symptom. New but counterfeit units with dodgy specs will also behave like this early on.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I have had the shutdown issue twice on my N810 (not with this new kernel but just with the d-t packages).

These times the power button wasn't working with the "screen won't go off" issue too.

So maybe these issues are relationated???

When that happened advance-power option to shutdown the device just rebooted. Same second time to shutdown with the advance-power menu.

Third time all went fine. Advance-power option could shutdown N810, screen go off allright and device power button worked again.

So I think all these issues are different sides of the same problem.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

This sounds like straight out of The Right Stuff... maacruz is a maemo Hero (yes, with the capital H :-)

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Yeah I have this on a second hand unit i procured. Mugen is on the way.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

If you have enabled a swap file or swap partition in mmc, or you have just ramzswap and nothing else.
Try this:
and tell me if it fixes the problem.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I said so in the new test kernel announce post. You should flash the new test kernel ASAP, only after some time of testing we'll know if both issues are gone.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

This worked!!!! Thanks for all the help with this, I really appreciate it. I guess it doesn't matter much now, but I am just using ramzswap --- no mmc swap partition or swap file. Thanks again!

Re: ANNOUNCE: Diablo-Turbo first beta available
 

The alarm in Clock and Large-statusbar-clock fails to alarm and keeps the display from dimming/sleep. Must reboot to reset unit.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Just FYI : this weekend I applied DT (as described on first page, plus the latest zImage from a couple pages back) to both my N800 and N810.

Both installation went real smoothly. I haven't stress-tested them heavily since, but at least they rebooted fine and seem no worse for wear :-)

Both devices had (slightly different customizations, like Advanced Power, Launcher, Telescope etc. All seem to work as before.

Great job, and thanks for bringing some action to our old tablets ! :-)

Re: ANNOUNCE: Diablo-Turbo first beta available
 

O.K. still not able to switch off the unit by any means. Holding down the power button or selecting 'switch off' only reboots it. If I command 'shutdown now' via the terminal, will only put the unit in a state where the screen goes black until I slide open the keys where I get a white screen, removing the battery is the only way to reset it.

I have done a fresh install without using my old back-up and only a few (total of sixteen) apps installed. The DT install was done by the book, I even made sure that the sysvinit=2.85-22.osso15 was not replaced by the DT sysvinit. Yes I also fiasco-flasher -f -k the DT kernel with zimage.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

What happens if you turn on R&D mode and disable the lifeguard-reset?

EDIT: Isn't the DT sysvinit needed to properly shutdown?

Re: ANNOUNCE: Diablo-Turbo first beta available
 

sorry to be slow but how is that done,

Re: ANNOUNCE: Diablo-Turbo first beta available
 

well was told that the new patch made the DT sysvinit not need because it took care of the shutdown problem

Re: ANNOUNCE: Diablo-Turbo first beta available
 

flasher-3.0-static --enable-rd-mode --set-rd-flags=no-lifeguard-reset -R

Re: ANNOUNCE: Diablo-Turbo first beta available
 

N810-WiMAX-43-7:~# flasher-3.0-static -sh: flasher-3.0-static: not found

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Replace "flasher-3.0-static" with the flasher you use to reflash the tablet.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I have tested shutdown just now again, after a 4 days uptime, and you are right, the shutdown issue is not gone :-(
sysvinit is still needed
Somehow it worked with diablo's sysvinit when I tested the patch.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Thanks, I thought I was doing something wrong. The DT sysvinit fixed the shutdown problem. :D

Re: ANNOUNCE: Diablo-Turbo first beta available
 

You don't run flasher on the tablet itself.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Oh, forgot to ask last time...

One side effect of DT I've seen on both devices is that their respective App Managers now offer me "phantom" updates of packages that are already present, such as :

- last (Nokia) Diablo update
- Community SSU
- webkit-related stuff
- gps-related stuff

Is this because of installing osso-software-version-unlocked ? Or because my poor tablets have led a promiscuous life ? :-)

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Probably because of this. Install osso-software-version-rx{34,44}-unlocked instead depending on what model of NIT you have

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Hi, maacruz.

Just installed new kernel. I will test and tell you.

However my BH-214 bluetooth headset is just the same than before. I mean no a2dp support is added. I supose something else is needed. Do you know what is this "something else"?

Thanks in advance and please keep the great job!

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I have one of each :-)
Will do, thanks !

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Well, after some tests with dt packages plus new kernel there are my results:

1 - I don't see my device to be faster than before in any scenario.

2 - I can't to shutdown properly.

However I want to thank maacruz for the effort on this.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Had a quick go at it this morning on the N810 before taking off.
Uninstalled osso-software-version-unlocked and installed osso-software-version-rx44-unlocked in its place.

Almost all "phantom updates" then disappeared from AppMan, except that it still insisted on updating gpsguard to the same version it already that. I accepted the update, half-expecting some error, but it actually went through and the list is now empty.

So, one problem solved, will do the N800 tonight :-)
Thanks !

Re: ANNOUNCE: Diablo-Turbo first beta available
 

You need the A2DP support package in the A2DP thread. That configures MPlayer to connect to your headset in lieu of using the speakers. You may also find the updated BlueZ packages to be of use or, alternatively, lardman's dsp-sbc (I don't know which is better: ARM opts or utilization of the DSP?)

I'm not maacruz, but what's a forum without discussion? :)

To me, my N800 isn't "faster" but it's certainly a lot more responsive, making it faster in that respect. For example, I'd sometimes tap the screen when it was blank and it would take ~5 seconds to wake up. Now, with Diablo-Turbo, it wakes up pretty much instantly.

Same. While maacruz's mini-rc/sysvinit packages and the newer kernel have reduced the chances of my N800 hanging upon shutdown, it does still happen.

maacruz, do you happen to have the softcursor, bitblit, font and fbcon modules compiled for your kernel? With those modules inserted and fanoush's fb_update_mode, I could at least see the last messages when shutting down before it hangs

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Thanks!


Very true, bro. ;)

Ok. I understand. But I never had these unresponsiveness with my devices so I don't fell it better now.

I didn't talk about hanging device but device just rebooting when I choose "shutdown" on "power-menu-pakage" option.

And I repeat my thanks to maacruz. Yours is a really great job.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Here you'll find dsp-sbc: https://garage.maemo.org/projects/dsp-sbc/
I'll provide in a couple of days arm optimized BlueZ packages to be part of DT.
I think using the DSP would be better, the CPU will be free to do other things and, by choosing the right op_dsp state, you can get significant battery life savings. Of course, only proper testing can provide the answer.

LOL
I'll prove you wrong. There is one scenario where the device is faster by any measure or definition.
Open osso-mediaplayer
Start playing a mp3
Stop playing the mp3
Start playing the mp3
There, you have it, 20% faster in a pure cpu bound task :D
I can also provide a scenario with 40% longer battery life, just play music after 'echo 3 >/sys/power/op_dsp'
Now, except in this scenario, I never promised a faster device (since the cpu is the same and its maximum frequency is 400 MHZ it can't go any faster), but a more responsive one. Unfortunately it is much more difficult to provide an objective measurement for responsiveness.
Yes, it's an old issue. I'll finally provide updated mini-rc packages to workaround it, since I can't reproduce it in qemu.