![]() |
Re: ANNOUNCE: Diablo-Turbo first beta available
Thanks, maacruz. I want to really thank you.
I love your work. Maybe my device is not faster but more resposive, you are right. But for sure my device is alive again because of you. Again, thanks. I will play with every single "toy" you give to us. P.D.: please, don't take my post like a rant, it wasn't :) |
Re: ANNOUNCE: Diablo-Turbo first beta available
Quote:
Quote:
|
Re: ANNOUNCE: Diablo-Turbo first beta available
Quote:
|
Re: ANNOUNCE: Diablo-Turbo first beta available
Quote:
|
Re: ANNOUNCE: Diablo-Turbo first beta available
Quote:
|
Re: ANNOUNCE: Diablo-Turbo first beta available
Quote:
I had it once on the 800, shutting down through the power button menu. After it failed and rebooted, I used the "long press" method and it turned off fine. Don't know if all this is reproductible though :) |
Re: ANNOUNCE: Diablo-Turbo first beta available
Quote:
|
Re: ANNOUNCE: Diablo-Turbo first beta available
Quote:
|
Re: ANNOUNCE: Diablo-Turbo first beta available
Hei, the update from yesterday works fine on my device. No longer reboots after shutting down. Thanks!
|
Re: ANNOUNCE: Diablo-Turbo first beta available
Hey, all the oldtimers, just want to say hello. HELLO!
Today is weekend, play time! I have bootmenu installed, as well as mmc boot. Would this takes away my bootmenu? Does it do mmc boot too? @maacruz, good job! TIA, bun |
Re: ANNOUNCE: Diablo-Turbo first beta available
Quote:
While I don't have bootmenu, I don't expect any ill effects on it. About mmc boot, that's where I boot from, too. |
Re: ANNOUNCE: Diablo-Turbo first beta available
NEWS: UPDATE 2
There is a new update. The first post has been updated to reflect the changes. Note: If you have downloaded the update's kernel package before this announcement, there was a bug in the installation backup code of that package. If you were updating DT there is no problem, but if you do the first installation, please redownload the kernel package. |
Re: ANNOUNCE: Diablo-Turbo first beta available
Quote:
edited: not osso15-dt but osso15, sorry. Thanks. :cool: |
Re: ANNOUNCE: Diablo-Turbo first beta available
Quote:
|
Re: ANNOUNCE: Diablo-Turbo first beta available
Quote:
Bootmenu works fine as does mmc boot. Definitely breathed new life ( and snappyness) into the N8x0 series. :cool: :D Many Many Thanks to maacruz :D Snoshrk |
Re: ANNOUNCE: Diablo-Turbo first beta available
Quote:
Edit: I have no intention or desire to restore the original kernel. |
Re: ANNOUNCE: Diablo-Turbo first beta available
Quote:
|
Re: ANNOUNCE: Diablo-Turbo first beta available
I have just upgraded the new packages.
Now my N800 can't boot. It starts, video introduction apears, white screen and reboot. It starts, video introduction apears... |
Re: ANNOUNCE: Diablo-Turbo first beta available
Quote:
You can use flasher-3.5 to set the RD-mode flag "no-lifeguard-reset" so that it doesn't reboot when starting up. That's what I did. (The plan was to downgrade but, well, other stuff got in the way...) But make sure you can SSH into it because it turns out that it's hildon-input-method that's crashing so you won't get the OSK |
Re: ANNOUNCE: Diablo-Turbo first beta available
That certainly shouldn't happen.
kernel image is exactly identical to the last test kernel, the kernel modules are rebuilt for this kernel. Try reverting the kernel to the previous release, if the tablet works, try upgrading the kernel again. Just a question, do you have CSSU installed? |
Re: ANNOUNCE: Diablo-Turbo first beta available
Quote:
Quote:
|
Re: ANNOUNCE: Diablo-Turbo first beta available
Quote:
"flasher-3.0 --enable-rd-mode --set-rd-flags no-lifeguard-reset" That will allow your device to fully boot. Then you can have a look at what is crashing (hildon-input-method?) and make changes. Once you have done the changes, you can disable R&D mode |
Re: ANNOUNCE: Diablo-Turbo first beta available
I upgraded both N8x0 oldies over the weekend. The N800 rebooted successfully after the kernel flash, and shutdown without crashing using the ASUI button, so all seemed well.
Will turn it on again tonight, just to make sure :-) |
Re: ANNOUNCE: Diablo-Turbo first beta available
Quote:
|
Re: ANNOUNCE: Diablo-Turbo first beta available
Quote:
(and funny enough, the proverb is the same both in spanish and in english) |
Re: ANNOUNCE: Diablo-Turbo first beta available
...and in French too :-)
|
Re: ANNOUNCE: Diablo-Turbo first beta available
Quote:
I have the old packages just successfully installed. Aplication manager has seen the gps-guard package to upgrade and I have done it. Now I have to download the upgraded packages, right? And the kernel image too, right? Thanks in advance. The omelette will be done by this afternoon! P.D.: I've seen 'zImage' package deleted. There is some reason? Is it better not to install it? |
Re: ANNOUNCE: Diablo-Turbo first beta available
Quote:
Quote:
Quote:
And today we have a nice sunny weather for a picnic in the country. I'll bring in the cider :D :D |
Re: ANNOUNCE: Diablo-Turbo first beta available
Quote:
|
Re: ANNOUNCE: Diablo-Turbo first beta available
Quote:
~$ uname -a Linux noname 2.6.21-omap1#6 PREEMPT Sat Feb 19 10:59:14 CET 2011 armv6l unknown (if for old kernel you mean the community update kernel, that was the first time I installed diablo turbo). |
Re: ANNOUNCE: Diablo-Turbo first beta available
Quote:
Linux noname 2.6.21-omap1 #2 PREEMPT Sun Mar 13 23:29:39 CET 2011 armv6l unknown |
Re: ANNOUNCE: Diablo-Turbo first beta available
I've been following kernel development for a long time. An enhanced, bug fixed kernel is _very_ welcome. Thanks.
> 256 HZ timer: The diablo kernel has a slow 128 HZ timer, > strongly related to the number of task switches the task > scheduler can do. This kernel is configured with a 256 HZ > timer, and additionally the SD scheduler allows a task switch > within a much more shorter time (defined by the rr_interval > tunable). This means that the device will be much more > interactive. Have you checked what changing to a higher HZ value does to power usage? I suspect it increases it a fair amount. If I remember correctly diablo uses the dyntick patchset to reduce this effect, but there are programs that disable dyntick and cause power to be eaten. Its probably worth testing with the lower HZ value - suspect it will not make a great difference to response but should help power... On the scheduler. Have you queried Con about SD vs BFS? A patchset porting a version of BFS to 2.6.21 exists. Depending on what Con suggests, it might be worth trying. There is also a recent patch set from intel that improves the ondemand policy. On my desktop it gives a noticeable reduction in power usage (my UPS is good for longer). If this can be back ported it would be nice. Would you happen to have a git tree with the kernel source you are using available? Thanks Again, Ed |
Re: ANNOUNCE: Diablo-Turbo first beta available
Quote:
Quote:
The timer just provides a timeframe for the scheduler, and the number of tasks switches (within a certain order) only increases the work done very slightly, so when the cpu is at work, the impact is negligible. When the cpu is at rest, the timer generates no interrupts, so no work is done. If a program disables dyntic, it doesn't matter much 128 vs 256, the battery will drain quite fast anyway, the problem is such program. Quote:
Quote:
If it is for current kernels, I doubt it can be ported, at least with a reasonable amount of work. Quote:
|
Re: ANNOUNCE: Diablo-Turbo first beta available
Question about swap memory size. My swap memory size goes to the limit that was set via the control panel but nevers goes back to 0 when no apps are being run. Should the swap memory size go towards 0 when the unit is not running any apps?
|
Re: ANNOUNCE: Diablo-Turbo first beta available
Quote:
|
Re: ANNOUNCE: Diablo-Turbo first beta available
Hi, maacruz.
Yesterday the omelette was done and the picnic at the country was successful. Thanks ;) I have installed all the packages the old and the upgraded ones. With the new bluez-utils package I can pair with my BH-214 headset and it plays for 2-3 seconds aprox. Then it suddenly stops playing. Pairing is still established but no sound trough headset. I'm still testing. |
Re: ANNOUNCE: Diablo-Turbo first beta available
I installed the original DT along with the first update. Then I installed the zimage kernel from 3/9. So, to install the 2nd update do I simply do the following?
1. Download only the "update 2" deb packages to "/media/mmc1/dt" 2. Open a xterm and become root 3. Change to the directory where the packages are (cd /media/mmc1/dt) 4. Install all debs ("dpkg -i *.deb") I just want to make sure before I actually go ahead with it. Please let me know if I am missing any steps. Thanks! |
Re: ANNOUNCE: Diablo-Turbo first beta available
Quote:
|
Re: ANNOUNCE: Diablo-Turbo first beta available
Quote:
Quote:
Ok, but the "Sat Feb 19" one cannot be from the community update (I checked the repository and that was in august 2010), according to the date it must be one of the diablo turbo one. The only diablo turbo kernel package I installed is the "broken" one, and you said that, due to a bug, it didn't really install the kernel. I'm confused now, (more than usual ;)) |
Re: ANNOUNCE: Diablo-Turbo first beta available
> I haven't contacted Con in any way. At the time I couln't find any
> port of BFS to 2.6.21, so if you know one, please provide the link. My error here. The back port was actually from 2.6.31 to 2.6.29. The message, but not the actual patch, said .21.... > What is the effect of that patch? Links? > if it is for current kernels, I doubt it can be ported, at least with a > reasonable amount of work. I allows the ondemand policy to use intermediate frequencies more often instead of just the highest and lowest. > No, just the set of patches already published and the diablo > kernel tar.gz. I play on a kernel tree, and when I'm done with > whatever I'm trying to do I extract a pach and destroy the tree to > start afresh again. Does this have all the patches (nokia's too) for n8x0 included. If not where are the patches from nokia? I'll see if the ondemand stuff can be backported. TIA Ed |
| All times are GMT. The time now is 22:17. |
vBulletin® Version 3.8.8