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

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)

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.

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. :(

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).

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!

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.

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.

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.

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).

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.

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.