|
2011-08-23
, 10:19
|
Posts: 875 |
Thanked: 918 times |
Joined on Sep 2010
|
#472
|
|
2011-08-24
, 08:35
|
Posts: 4 |
Thanked: 1 time |
Joined on Aug 2008
|
#473
|
I don't know if flipclock uses alarmd or not. You could try unchecking and stopping alarmd in asui-settings:Services and then set a test alarm in flipclock to see if it still works.
|
2011-08-24
, 20:47
|
|
Posts: 4,783 |
Thanked: 1,253 times |
Joined on Aug 2007
@ norway
|
#474
|
|
2011-08-25
, 08:14
|
Posts: 151 |
Thanked: 93 times |
Joined on Sep 2009
@ sofia, bulgaria
|
#475
|
|
2011-08-26
, 22:20
|
Posts: 21 |
Thanked: 18 times |
Joined on Aug 2011
|
#476
|
|
2011-08-27
, 20:01
|
Posts: 1,101 |
Thanked: 1,184 times |
Joined on Aug 2008
@ Spain
|
#477
|
I have another issue which might be related to the fuse.ko one solved earlier. I have a script that does insmod cifs.ko and then mount.cifs so I can connect to my router's hard drive (similar to the sequence described here: http://wiki.maemo.org/Accessing_Windows_CIFS though from memory I'm using files supplied by Qole).
However, with Diablo-Turbo installed I get a complaint that cifs.ko is already loaded (which appears to be true) and the mount.cifs command produces a seg fault.
Any thoughts on replacements for these files, or other methods of doing things? Wizard Mounter doesn't work for this particular router drive.
|
2011-08-27
, 23:35
|
Posts: 21 |
Thanked: 18 times |
Joined on Aug 2011
|
#478
|
|
2011-09-04
, 05:57
|
|
Posts: 39 |
Thanked: 26 times |
Joined on Mar 2008
@ On the wasatch front, UT USA
|
#479
|
It is not related to fuse.ko, since cifs is a diferent kernel module, but the problem is the same.
The solution should be the same, using a cifs.ko module built for the DT kernel.
I'll build one tomorrow if I possible.
# modprobe fuse modprobe: cannot parse modules.dep
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
|
2011-09-04
, 10:35
|
Posts: 1,101 |
Thanked: 1,184 times |
Joined on Aug 2008
@ Spain
|
#480
|
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.depI 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.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
Otherwise I am enjoying diablo turbo.
Yesterday did an "upgrade to latest testing version", but did not reboot N800 afterwards, so I don't know if that helped, but will see these days...