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

Page 13 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)

alexc

2011-09-05 21:18

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by salinmooch (Post 1081500)

I'm with alexc in that I have had some issues with fuse, cifs, and nfs modules after installing diablo turbo. Really I usually drop files and such on to my n800 from a linux pc not the other way around so I have not noticed the problem till now. The other day I ran some old scripts to sshfs to my home server and they failed with a call for me to modprobe fuse. I made sure I was up to date on all the diablo turbo stuff and I couldn't find any old fuse modules laying around but I honestly don't know where to look. Unfortunately modprobe resulted in this:

Code:

# modprobe fuse

modprobe: cannot parse modules.dep

Code:

insmod /lib/modules/2.6.21-omap1/fuse.ko 

insmod: cannot insert '/lib/modules/2.6.21-omap1/fuse.ko': Unknown symbol in module (-1): No such file or directory

I may have screwed this (modprobe) up else where but it seems like I should at least be able to get the fuse module loaded with insmod. . . If it matters it looks like I'm running the March 13th kernel.

Otherwise I am enjoying diablo turbo.

If you check my posts a page or so back on this thread, you'll see how to fix the fuse problem (deleting the original fuse.ko and making a sym-link to the new one). Once rebooted, this works fine.

maacruz, if you're able to build that new cifs.ko module you mentioned (and perhaps an nfs one for salinmooch too), I'd be very grateful.

maacruz

2011-09-05 21:42

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by alexc (Post 1082499)

maacruz, if you're able to build that new cifs.ko module you mentioned (and perhaps an nfs one for salinmooch too), I'd be very grateful.

I've added them under "Optional packages" in the DT download page https://garage.maemo.org/frs/?group_id=2036
You'll have to copy them by hand, sorry for not building a proper package.

alexc

2011-09-05 23:58

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by maacruz (Post 1082511)

I've added them under "Optional packages" in the DT download page https://garage.maemo.org/frs/?group_id=2036
You'll have to copy them by hand, sorry for not building a proper package.

That's great, thanks. I can confirm that the cifs.ko one works fine when connecting to my router's drive. I don't have any way of testing the others yet, but I'll keep them in case I ever do.

One question, out of curiosity: the cifs.ko module is about 10 times larger than the original file. Is there a particular reason for that? No criticism, I'm just trying to expand my knowledge.

salinmooch

2011-09-06 05:38

Re: ANNOUNCE: Diablo-Turbo first beta available

I'm still stuck on finding the right fuse module. As alexc suggested I went back and linked /lib/modules/2.6.21-omap1/extra/fuse.ko to /usr/lib/fuse/fuse.ko and rebooted

Still no luck using sshfs - it fails on trying to loading the module. I looked around and have not found any other fuse modules that could be screwing things up. I tried an insmod on /lib/modules/2.6.21-omap1/extra/fuse.ko and get this same error:

Code:

insmod: cannot insert 'fuse.ko': Unknown symbol in module (-1): No such file or directory

For kicks I rmmod the nfs module and added it with insmod just fine. Does fuse require a dependency I need to load first? Where else should I look for old fuse modules to get rid of them?

Thanks for your help.

jstokes

2011-09-06 11:43

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by alexc (Post 1082575)

One question, out of curiosity: the cifs.ko module is about 10 times larger than the original file. Is there a particular reason for that? No criticism, I'm just trying to expand my knowledge.

Purely a guess, but maybe the module is unstripped and still has its debugging symbols? file will be able to verify/disprove this.

@salinmooch
No offense, but does that module actually exist in /lib/...? IIRC ln lets you create links to non-existant files and you'd be getting a different error if another module needed to be loaded

maacruz

2011-09-06 18:45

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by jstokes (Post 1082793)

Purely a guess, but maybe the module is unstripped and still has its debugging symbols? file will be able to verify/disprove this.

Upps, that's right. I forgot to strip it.
Reuploaded all modules with debugging symbols properly stripped.

maacruz

2011-09-06 18:55

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by salinmooch (Post 1082637)

I'm still stuck on finding the right fuse module. As alexc suggested I went back and linked /lib/modules/2.6.21-omap1/extra/fuse.ko to /usr/lib/fuse/fuse.ko and rebooted

That's right for alexc setup, and wrong for nobody.

Quote:

Still no luck using sshfs - it fails on trying to loading the module. I looked around and have not found any other fuse modules that could be screwing things up. I tried an insmod on /lib/modules/2.6.21-omap1/extra/fuse.ko and get this same error:

Are you sure the DT fuse module package is installed?
"dpkg -l fuse-modules-rx-34" will confirm if it is installed.
I'm using this module with the package fuse-utils-2.7.2-1maemo7 from extras-devel, it contains the init.d to load the module and works with no problem.

Quote:

For kicks I rmmod the nfs module and added it with insmod just fine. Does fuse require a dependency I need to load first?

No.

Quote:

Where else should I look for old fuse modules to get rid of them?

"find /lib/modules -name 'fuse.ko'" will find any fuse module

alexc

2011-09-07 02:46

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by maacruz (Post 1083002)

Upps, that's right. I forgot to strip it.
Reuploaded all modules with debugging symbols properly stripped.

Thanks. Tested again and the new cifs.ko works fine.

siny	2011-09-07 18:50

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by auouymous (Post 1074524)

Do you have ASUI or use alarms? If you don't use alarms you can try turning off the alarmd service so it doesn't start at boot. It is most likely a problem with ASUI's interaction with alarmd, assuming you have both running.

OK, I got back from my vacation :(

After I turned off Alarmd, my FliClock stopped waking me up, so it is using Alarmd (it even says so after I change wake-up time, but I did't look at that message before).

Also after turning off Alarmd and rebooting, screen goes blank OK, and after enabling Alarmd again screen would not turn off.

For now I will leave Alarmd off (and use my radio-controlled clock for wake up), and try to upgrade ASUI from time to time...

luca	2011-09-16 17:16

Re: ANNOUNCE: Diablo-Turbo first beta available

I don't think it's related to diablo turbo, but since here's where the last few n800 experts hang around, I'll ask here ;)
Today, while browsing with tear and switching windows with telescope, my n800 froze and rebooted, then it entered a reboot loop (every time it showed the hands it flashed the led and rebooted).
I used flasher to disable the lifeguard reset and I managed to boot the tablet, but now there's no sound at all (not even the greeting nokia tune).
No suspicious messages in dmesg (apart from a "JFFS2 warning: (940) jffs2_sum_write_sumnode: Not enough space for summary, padsize = -23").
Any idea?

Edit: re-enabled the lifeguard reset and the reboot loop is back. I think it's related to the missing sound.

auouymous

2011-09-16 18:07

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by luca (Post 1089647)

I used flasher to disable the lifeguard reset and I managed to boot the tablet, but now there's no sound at all (not even the greeting nokia tune).

Do you have ASUI installed? If so, you could open the services section in asui-settings and see if any of the sound services aren't running but should be (checked). Incorrect start orders can cause services to fail to start and result in a reboot loop. The maemo-control-services app incorrectly starts services at 20 (any of them) after you toggle them off and back on.

Required services can't be unchecked so you could safely uncheck every service in asui-settings and see if a reboot without lifeguard works. Rechecking the services you want will restore them to the correct orders they were installed with.

If you don't have ASUI installed and don't want to use it then you could install it and use its service manager to revert back to systemui. That way you could continue using its service manager and its MCE settings interface without using ASUI.

lma	2011-09-16 18:20

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by luca (Post 1089647)

Today, while browsing with tear and switching windows with telescope, my n800 froze and rebooted, then it entered a reboot loop (every time it showed the hands it flashed the led and rebooted).
I used flasher to disable the lifeguard reset and I managed to boot the tablet, but now there's no sound at all (not even the greeting nokia tune).

/var/lib/dsme/stats/lifeguard_resets should indicate which service is misbehaving. Syslog might provide hints too.

Quote:

No suspicious messages in dmesg (apart from a "JFFS2 warning: (940) jffs2_sum_write_sumnode: Not enough space for summary, padsize = -23").

That's probably unrelated (I get it all the time), but check that you have free space anyway.

luca	2011-09-16 18:24

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by auouymous (Post 1089664)

Incorrect start orders can cause services to fail to start and result in a reboot loop. The maemo-control-services app incorrectly starts services at 20 (any of them) after you toggle them off and back on.

Thank you, that was it. I moved multimediad and mediaplayer-daemon from 20 to 27 (I probably disabled/enabled them and never rebooted) and now the sound is back (and I could re-enable the lifeguard reset).
I knew I was right when I said that the experts are here :D

auouymous

2011-09-16 21:06

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by luca (Post 1089672)

I moved multimediad and mediaplayer-daemon from 20 to 27

Stock order for those services are:
mediaplayer-daemon S99 in 234 and K01 in 0156
multimediad S25 in 2345 and K75 in 016

Hard to read when the tab size is not 4 but here are all of the stock orders:
https://garage.maemo.org/plugins/scm...ui&view=markup

tso	2011-09-17 07:43

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by lma (Post 1089669)

That's probably unrelated (I get it all the time), but check that you have free space anyway.

Running out of storage (or at least getting below 10MB free) seems capable of creating all kinds of subtle issues (like writes being silently discarded).

maacruz

2011-09-17 20:34

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by tso (Post 1089964)

Running out of storage (or at least getting below 10MB free) seems capable of creating all kinds of subtle issues (like writes being silently discarded).

And files truncated to 0 size

tso	2011-09-18 11:59

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by maacruz (Post 1090477)

And files truncated to 0 size

Yeiks! (10 character limits "ftw")

maacruz

2011-09-18 18:27

Re: ANNOUNCE: Diablo-Turbo first beta available

Btw, after looong testing I have decided that the latest testing kernel from may is not good.
It fixed the shutdown issue but caused a spontaneous reboot about every week
So, the update 2 kernel package from march (kernel-dt-sd_2.6.21-3_all.deb) is the recommended kernel.
If you do not remember what kernel you have installed, look at the date in the output of "uname -a". This date is Sun Mar 13 23:29:39 CET 2011 in the recommended kernel.
If you have the kernel dated May, just reinstall the kernel-dt-sd_2.6.21-3_all.deb package ("dpkg -i kernel-dt-sd_2.6.21-3_all.deb")

jmart

2011-09-20 12:15

Re: ANNOUNCE: Diablo-Turbo first beta available

Hi Maacruz,

I'm running the kernel from May. I haven't noticed the reboot issue, but I'm currently only getting around 6 days use on a charge (it really depends on usage) and then I shutdown to swap-out the battery with a fully charged one anyway. Since loading the May kernel though I haven't had one instance of the shutdown issue, so I am somewhat reluctant to rollback to the March kernel if that means I could start experiencing the shutdown issue again. Is there any other reason why I wouldn't want to stay on the May kernel? I'll try and start tracking my uptime a little more carefully to see if the restart issue is affecting me and I'm not aware of it. Overall I have been completely happy with the May kernel.

Thanks!!

maacruz

2011-09-20 18:56

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by jmart (Post 1092482)

If that's your pattern of usage and the kernel hasn't showed any problem for you, then by all means keep it.
My usage pattern is to never turn off or reboot, and 5-6 days was my usual uptime before a reboot happened, but since I asked very few people answered so I acted based on my own data. It well could be an aging hardware problem in my N810; time will tell.Since I rolled back to the march kernel I had a reboot, yesterday, after 15 days of uptime.

Addison

2011-09-20 19:29

Re: ANNOUNCE: Diablo-Turbo first beta available

This probably has been asked before, sorry, but does it matter what order one installs these .debs?

auouymous

2011-09-20 19:52

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by Addison (Post 1092767)

This probably has been asked before, sorry, but does it matter what order one installs these .debs?

Bottom of the first post in this thread...

Edit: Read every word in the first post...

maacruz

2011-09-20 21:37

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by auouymous (Post 1092782)

Quote:

Originally Posted by Addison (Post 1092767)

This probably has been asked before, sorry, but does it matter what order one installs these .debs?

Bottom of the first post in this thread...

Edit: Read every word in the first post...

Well, you can skip the large technical explanation of DT kernel features over the stock kernel if you wish, but follow the installation instructions to the letter

Addison

2011-09-21 02:26

Re: ANNOUNCE: Diablo-Turbo first beta available

Easiest install ever.

Thank you Mac. :)

momcilo

2011-09-21 08:05

Re: ANNOUNCE: Diablo-Turbo first beta available

I've just installed DT for the first time (well my n810 is functional again now), and I am speechless.
I knew it should be more responsive, but never guessed it would work so good.

Good work!

maacruz

2011-09-21 21:13

Re: ANNOUNCE: Diablo-Turbo first beta available

ANNOUNCE:
New testing kernel available.

The last testing kernel caused reboots probably because it had some experimental debugging code to try to catch the bad driver which crashed kthread sometimes, and such code probably ended causing more problems when the bug triggered.
The openwrt kernel patches have inspired me to make some minor changes related to preemption and irq locking in the touchscreen and retu drivers, which are among the suspicious of causing the kthread crash. Those changes are completely safe, and in the worst case, won't do anything, but in the best case the kthread crash may be fixed.

So, this new testing kernel has the patch to fix the shutdown issue, and the newly patched drivers.
I'm running it right now and it is completely safe, the worst that can happen is that kthread crashes once about a week to some months. But if you guys expect me to do all the testing, it'll be months again before I can take a decision. If the new patches have a positive impact, it can take even longer, just think, if one of those drivers caused the crash and now it is fixed, but it isn't the only one driver causing the crash.. it will take much longer to crash.
A symptom of the kthread crash is that the hardware keys stop working.

PLEASE INSTALL THIS KERNEL AND REPORT UPTIME AND CRASHES (IF ANY)

Addison

2011-09-21 21:19

Re: ANNOUNCE: Diablo-Turbo first beta available

Where can I pick this up at Mac?

https://garage.maemo.org/frs/?group_id=2036
doesn't show anything new.

maacruz

2011-09-21 21:36

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by Addison (Post 1093487)

Where can I pick this up at Mac?

https://garage.maemo.org/frs/?group_id=2036
doesn't show anything new.

I forgot to update the publication date. Fixed.
The zImage is new, go ahead and download it. Flash it from PC using flasher or from the tablet with fiasco-flasher (see first post instructions)

Addison

2011-09-21 21:51

Re: ANNOUNCE: Diablo-Turbo first beta available

Okay. After reading your first post here 3 times, I'm not seeing anything about using flasher for PC or fiasco-flasher to install your zimage thingy.

Care to point me at the post on this? :)

maacruz

2011-09-21 22:11

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by Addison (Post 1093512)

Okay. After reading your first post here 3 times, I'm not seeing anything about using flasher for PC or fiasco-flasher to install your zimage thingy.

Care to point me at the post on this? :)

If you read carefully again near the end of the first post, you'll see
"fiasco-flasher -f -k zImage"
About flasher-3.0 you are supposed to already know how to use it :) , anyway, it follows the same pattern
"flasher-3.0 -f -R -k zImage"
as root in your linux PC console/xterm

lma	2011-09-22 11:14

Re: ANNOUNCE: Diablo-Turbo first beta available

This isn't DT's fault, but after installing on my new(ish) RX48 I see this weirdness:

Code:

Nokia-N810-WiMAX-43-7:/usr/share/Diablo-Turbo/backup# df .

Filesystem           1k-blocks      Used Available Use% Mounted on

rootfs                  255488    249480      6008  98% /

Nokia-N810-WiMAX-43-7:/usr/share/Diablo-Turbo/backup# ls -l zImage-backup 

-rw-r--r--    1 root     root    926102833 Sep 22 08:52 zImage-backup

Nokia-N810-WiMAX-43-7:/usr/share/Diablo-Turbo/backup# du zImage-backup 

904398        zImage-backup

any ideas that can explain it that do not involve JFFS2 corruption?

Edit: Ah, found it, bug in the perl snippet in the post-install script - the truncate call unpacks the already-unpacked value and gets a bogus result. The resulting file is sparse, and du reports its size correctly but only until the next reboot.

maacruz

2011-09-22 17:05

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by lma (Post 1093853)

This isn't DT's fault, but after installing on my new(ish) RX48 I see this weirdness:

Code:

Nokia-N810-WiMAX-43-7:/usr/share/Diablo-Turbo/backup# df .

Filesystem           1k-blocks      Used Available Use% Mounted on

rootfs                  255488    249480      6008  98% /

Nokia-N810-WiMAX-43-7:/usr/share/Diablo-Turbo/backup# ls -l zImage-backup 

-rw-r--r--    1 root     root    926102833 Sep 22 08:52 zImage-backup

Nokia-N810-WiMAX-43-7:/usr/share/Diablo-Turbo/backup# du zImage-backup 

904398        zImage-backup

Aw! Sh*t!
Now everybody whose first DT kernel is kernel-dt-sd_2.6.21-3 has a corrupt zImage backup.
Well, they don't have any reason to uninstall the DT kernel, do they? :D
And if they do, just reflashing a good zImage after uninstalling will fix the problem.

lma	2011-09-23 04:16

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by maacruz (Post 1094034)

Aw! Sh*t!
Now everybody whose first DT kernel is kernel-dt-sd_2.6.21-3 has a corrupt zImage backup.

Well, it's still a beta right? ;-)

At least the ones that are larger than 2MiB should be safe to truncate and write back to /dev/mtd2, and most truncated ones should still contain the version string so the right version could be fetched from somewhere else.

maacruz

2011-09-25 13:17

Re: ANNOUNCE: Diablo-Turbo first beta available

Announce: maemo-pan update (extras-devel)

I have found that maemo-pan stopped working with DT due to a too simple string processing of dbus-send output in the /usr/lib/maemo-pan/pan-control script.

I have uploaded a new release (1.0.2) of maemo-pan to extras-devel to fix this issue. This new release works with both old Diablo and DT.

tso	2011-09-25 18:38

Re: ANNOUNCE: Diablo-Turbo first beta available

either asui or maemo-pan got a bug. When ASUI attempts to disconnect a PAN connection it appears to do so but the connection stays active.

auouymous

2011-09-25 19:07

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by tso (Post 1096099)

either asui or maemo-pan got a bug. When ASUI attempts to disconnect a PAN connection it appears to do so but the connection stays active.

I don't have a cell phone so someone else will need to figure this out. ASUI only listens for a disconnect signal and if PAN isn't sending it...

tso	2011-09-25 19:34

Re: ANNOUNCE: Diablo-Turbo first beta available

from what i can tell, maemo-pan listen for a connect and disconnect on a dummy connection and then do the actual connection management behind the scene.

I guess ASUI fails to send a expected signal, and so the actual disconnect is not triggered.

this because the maemo connection manager triggers the correct behavior.

maacruz

2011-09-25 20:38

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by auouymous (Post 1096127)

I don't have a cell phone so someone else will need to figure this out. ASUI only listens for a disconnect signal and if PAN isn't sending it...

maemo-pan doesn't send any signal when disconnecting.
In fact, pan-daemon listens to system bus for the "dummy" IAP status change signals, and then runs the pan-control script with start/stop as argument. This scripts handles all connecting and disconnecting through dbus method calls to bluez, but the bluetooth connection can also break for being out of range, and in this case, the IAP remains "dummy".
If ASUI needs any signal, we can tweak the script, but I'm not sure how to handle the "out of range" situation.

auouymous

2011-09-25 21:17

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by maacruz (Post 1096230)

If ASUI needs any signal, we can tweak the script, but I'm not sure how to handle the "out of range" situation.

Or tell me what needs to be done in ASUI to support it as is.

lma	2011-09-26 05:30

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by maacruz (Post 1093482)

PLEASE INSTALL THIS KERNEL AND REPORT UPTIME AND CRASHES (IF ANY)

Woke up this morning to find the device had rebooted during the night. Uptime was about 4 days, /proc/bootreason says sw_rst, but syslogd had stopped logging due to 99% full rootfs :-(

All times are GMT. The time now is 22:02.

Page 13 of 16

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

vBulletin® Version 3.8.8