apt-get; gstreamer-dev; pkg-config has no installation candidate
* summary: gstreamer-dev cannot be installed due to package dependency to pkg-config. But pkg-config has no installation candidate * Hi, I would like to built a gstreamer-plugin for the N800 from source. Therefore I need gstreamer-dev installed. I'm running scratchbox 1.0.7 on a debian host. * This command works fine: apt-get install gstreamer0.10-tools gstreamer0.10-plugins-base gstreamer0.10-plugins-good * This does not: apt-get install libgstreamer-plugins-base0.10-dev = Message: ... pkg-config but it is not installable == apt-get install pkg-config log start --- [sbox-testtarget: ~/gst-mpsdec-plugin] apt-get install pkg-config Reading Package Lists... Done Building Dependency Tree... Done Package pkg-config is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package pkg-config has no installation candidate log end --- Package pkg-config has no installation candidate ... But Why? Am I missing a repository? sources.list of scratchbox --- deb http://repository.maemo.org/ bora free non-free deb http://repository.maemo.org/extras bora free non-free sources.list of scratchbox end --- Thanks! Johannes ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: N810 Resets
ext Alex Iliadis [EMAIL PROTECTED] writes: After running again my code and introducing a small delay factor, I noticed the following warning in ksyslogd saved logfile: WARNING: prism_softmac_frame_tx_done() returned an empty frame That happens all the time, I just have recently added warning for this. You can ignore it for now, it does not cause any crashes. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: gpsd in OS2007 HE
Bug is invalid agaist he, because problem really is in gpsd. But that's fine to hear that so many people are using HE2007. - Joni On Wed, 12 Dec 2007, Julius Luukko wrote: Alex DAMIAN kirjoitti: Hello, I found that the gpsd supplied in OS2007 HE (osso-gpsd-0.8) would crash with Illegal instruction fault when launching (as in gpsd -N /dev/rfcomm0 from command line). I downloaded the code from OS2008 version, changed a bit so it could compile against libdbus-1-2 instead of libdbus-1-3, and created the OS2007 install package that could be found here: http://sandel.homeip.net/debs/osso-gpsd_1.0-23_armel.deb This works ok on my OS2007 HE. Cheers, Alex Hello Alex, I noticed that too and I made a bug report of it: https://garage.maemo.org/tracker/index.php?func=detailaid=1735group_id=164atid=681 It is easier to use the OS2007 version of osso-gpsd_0.8 and compile it for gregale since no changes are needed at all. I haven't got a suitable place to put the .deb, though. Best regards, Julius ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: gpsd in OS2007 HE
Or not in gpsd. Really it is feature of 770. Illegal instructions are caused by vfp compiled binary. 770 has no vfp and vfp-compiled code runs faster in some cases on n8(0/1)0. Thats why it is used in some cases. microb is good example. I think best solution would be to create own he2007-debian-repo and compile or ask someone to compile and put tested-non-vfp-compiled stuff there. - Joni On Thu, 13 Dec 2007, Joni Valtanen wrote: Bug is invalid agaist he, because problem really is in gpsd. But that's fine to hear that so many people are using HE2007. - Joni On Wed, 12 Dec 2007, Julius Luukko wrote: Alex DAMIAN kirjoitti: Hello, I found that the gpsd supplied in OS2007 HE (osso-gpsd-0.8) would crash with Illegal instruction fault when launching (as in gpsd -N /dev/rfcomm0 from command line). I downloaded the code from OS2008 version, changed a bit so it could compile against libdbus-1-2 instead of libdbus-1-3, and created the OS2007 install package that could be found here: http://sandel.homeip.net/debs/osso-gpsd_1.0-23_armel.deb This works ok on my OS2007 HE. Cheers, Alex Hello Alex, I noticed that too and I made a bug report of it: https://garage.maemo.org/tracker/index.php?func=detailaid=1735group_id=164atid=681 It is easier to use the OS2007 version of osso-gpsd_0.8 and compile it for gregale since no changes are needed at all. I haven't got a suitable place to put the .deb, though. Best regards, Julius ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: gpsd in OS2007 HE
I think best solution would be to create own he2007-debian-repo and compile or ask someone to compile and put tested-non-vfp-compiled stuff there. Or maybe a special repo for vfp-compiled stuff instead, since the vast majority of maemo software isn't? -- Tak does not require that we think of Him, only that we think. --Grag Bashfullsson http://www.gnu.org/philosophy/shouldbefree.html ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: N810 Resets
On Thursday 13 December 2007 02:25:58 am you wrote: Hi, ext Alex Iliadis wrote: Yeah, it's running as root, but it's a python script. After running top to monitor it's memory usage it was ranging from 35-55MB. How much memory it was using just before the device booted? (By consuming all memory root process can make the device so slow that HW watchdog reboots it.) It has to run as root since I do low level things with the interfaces. I wrote a script that monitored memory usage of the application and it seemed within bounds ranging from 28-57mb. I also extended the swap drive by the maximum and from what I've noticed in the free output the memory mapped space hasn't been utilized by it. (0mb used) Let me know if you need any further details. If running your script as normal user doesn't help (e.g. from xterminal), You could install syslog and give the information just before the device reboots. I.e. after the reboot search for the last Bootup reason: message from syslog and go up from that until you see where the kernel starts and check what happens at that time). This is prior Bootup: Dec 13 09:36:18 Nokia-N810-42-18 kernel: [1.085937] Disabling unused clock uart3_fck Dec 13 09:36:18 Nokia-N810-42-18 kernel: [1.085937] Disabling unused clock uart3_ick Dec 13 09:36:18 Nokia-N810-42-18 kernel: [1.085937] Disabling unused clock uart2_fck Dec 13 09:36:18 Nokia-N810-42-18 kernel: [1.085937] Disabling unused clock uart2_ick Dec 13 09:36:18 Nokia-N810-42-18 kernel: [1.085937] Disabling unused clock gpt12_fck Dec 13 09:36:18 Nokia-N810-42-18 kernel: [1.085937] Disabling unused clock gpt12_ick Dec 13 09:36:18 Nokia-N810-42-18 kernel: [1.085937] Disabling unused clock gpt11_fck Dec 13 09:36:18 Nokia-N810-42-18 kernel: [1.093750] Disabling unused clock gpt11_ick Dec 13 09:36:18 Nokia-N810-42-18 kernel: [1.093750] Disabling unused clock gpt10_fck Dec 13 09:36:18 Nokia-N810-42-18 kernel: [1.093750] Disabling unused clock gpt10_ick Dec 13 09:36:18 Nokia-N810-42-18 kernel: [1.093750] Disabling unused clock gpt9_fck Dec 13 09:36:18 Nokia-N810-42-18 kernel: [1.093750] Disabling unused clock gpt9_ick Dec 13 09:36:18 Nokia-N810-42-18 kernel: [1.093750] Disabling unused clock gpt8_fck Dec 13 09:36:18 Nokia-N810-42-18 kernel: [1.093750] Disabling unused clock gpt8_ick Dec 13 09:36:18 Nokia-N810-42-18 kernel: [1.093750] Disabling unused clock gpt7_fck Dec 13 09:36:18 Nokia-N810-42-18 kernel: [1.093750] Disabling unused clock gpt7_ick Dec 13 09:36:18 Nokia-N810-42-18 kernel: [1.093750] Disabling unused clock gpt6_fck Dec 13 09:36:18 Nokia-N810-42-18 kernel: [1.093750] Disabling unused clock gpt6_ick Dec 13 09:36:18 Nokia-N810-42-18 kernel: [1.093750] Disabling unused clock gpt5_fck Dec 13 09:36:18 Nokia-N810-42-18 kernel: [1.093750] Disabling unused clock gpt5_ick Dec 13 09:36:18 Nokia-N810-42-18 kernel: [1.093750] Disabling unused clock gpt4_fck Dec 13 09:36:18 Nokia-N810-42-18 kernel: [1.093750] Disabling unused clock gpt4_ick Dec 13 09:36:18 Nokia-N810-42-18 kernel: [1.093750] Disabling unused clock gpt3_fck Dec 13 09:36:18 Nokia-N810-42-18 kernel: [1.093750] Disabling unused clock gpt3_ick Dec 13 09:36:18 Nokia-N810-42-18 kernel: [1.093750] Disabling unused clock gpt2_fck Dec 13 09:36:18 Nokia-N810-42-18 kernel: [1.093750] Disabling unused clock gpt2_ick Dec 13 09:36:18 Nokia-N810-42-18 kernel: [1.093750] Disabling unused clock dss2_fck Dec 13 09:36:18 Nokia-N810-42-18 kernel: [1.093750] Bootup reason: 32wd_to I scrolled a bit further down though and I noticed the following: Dec 13 09:36:20 Nokia-N810-42-18 kernel: [ 18.375000] menelaus 1-0072: Shutting off 'VIO' Dec 13 09:36:20 Nokia-N810-42-18 kernel: [ 18.390625] menelaus 1-0072: Shutting off 'VMEM' Dec 13 09:36:20 Nokia-N810-42-18 kernel: [ 18.531250] attempt to access beyond end of device Dec 13 09:36:20 Nokia-N810-42-18 kernel: [ 18.531250] mmcblk0: rw=0, want=4013848, limit=3932160 Dec 13 09:36:20 Nokia-N810-42-18 kernel: [ 18.531250] Buffer I/O error on device mmcblk0p1, logical block 501728 Dec 13 09:36:20 Nokia-N810-42-18 kernel: [ 18.531250] attempt to access beyond end of device Dec 13 09:36:20 Nokia-N810-42-18 kernel: [ 18.531250] mmcblk0: rw=0, want=4013848, limit=3932160 Dec 13 09:36:20 Nokia-N810-42-18 kernel: [ 18.531250] Buffer I/O error on device mmcblk0p1, logical block 501728 Dec 13 09:36:20 Nokia-N810-42-18 kernel: [ 18.531250] attempt to access beyond end of device Dec 13 09:36:20 Nokia-N810-42-18 kernel: [ 18.531250] mmcblk0: rw=0, want=4014080, limit=3932160 Dec 13 09:36:20 Nokia-N810-42-18 kernel: [ 18.531250] Buffer I/O error on device mmcblk0p1, logical block 501757 Dec 13 09:36:20 Nokia-N810-42-18 kernel: [ 18.531250] attempt to access beyond end of device Dec 13 09:36:20 Nokia-N810-42-18 kernel: [ 18.531250] mmcblk0: rw=0, want=4014080,
Re: N810 Resets
Hi, ext Alex Iliadis wrote: On Thursday 13 December 2007 02:25:58 am you wrote: ext Alex Iliadis wrote: I scrolled a bit further down though and I noticed the following: Dec 13 09:36:20 Nokia-N810-42-18 kernel: [ 18.531250] mmcblk0: rw=0, want=4013848, limit=3932160 Dec 13 09:36:20 Nokia-N810-42-18 kernel: [ 18.531250] Buffer I/O error on device mmcblk0p1, logical block 501728 Dec 13 09:36:20 Nokia-N810-42-18 kernel: [ 18.531250] attempt to access beyond end of device Does the reboot happen if you remove the MMC? There was earlier some case where an application infinitely reading corrupted MMC FAT file system could sometimes cause kernel panic, but that should have been fixed for N810 Chinook. - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: N810 Resets
Hi Eero, On Thursday 13 December 2007 10:16:09 am you wrote: Hi, ext Alex Iliadis wrote: On Thursday 13 December 2007 02:25:58 am you wrote: ext Alex Iliadis wrote: I scrolled a bit further down though and I noticed the following: Dec 13 09:36:20 Nokia-N810-42-18 kernel: [ 18.531250] mmcblk0: rw=0, want=4013848, limit=3932160 Dec 13 09:36:20 Nokia-N810-42-18 kernel: [ 18.531250] Buffer I/O error on device mmcblk0p1, logical block 501728 Dec 13 09:36:20 Nokia-N810-42-18 kernel: [ 18.531250] attempt to access beyond end of device Does the reboot happen if you remove the MMC? There was earlier some case where an application infinitely reading corrupted MMC FAT file system could sometimes cause kernel panic, but that should have been fixed for N810 Chinook. I think it's an internal one bundled with the device. (I haven't connected any in the slot) Not sure why it's displayed as mmc, but I'm guessing the linux kernel identifies it as one? Maybe somehow it got corrupted and that's what's causing the problems? I'll try to do a clean flash of the system and re-run the application and let you know of the result. -Alex - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: N810 Resets
I did a fresh install and I noticed that those messages appear anyway in every boot I do, be it recovering from a hw watchdog reboot or not. Unfortunately the problem seems to persist even after a clean install the device reboots when the application utilizes a lot of resources. I did notice however that the whole device became unresponsive, at that point my application was using 195MB of memory which was triggering a disk mapping since it had exceeded the physical memory limit. I guess it boils down into limiting the amount of memory python could use from the system since I've got no control over the memory allocation that the interpreter does. Thanks, Alex On Thursday 13 December 2007 10:16:09 am you wrote: Hi, ext Alex Iliadis wrote: On Thursday 13 December 2007 02:25:58 am you wrote: ext Alex Iliadis wrote: I scrolled a bit further down though and I noticed the following: Dec 13 09:36:20 Nokia-N810-42-18 kernel: [ 18.531250] mmcblk0: rw=0, want=4013848, limit=3932160 Dec 13 09:36:20 Nokia-N810-42-18 kernel: [ 18.531250] Buffer I/O error on device mmcblk0p1, logical block 501728 Dec 13 09:36:20 Nokia-N810-42-18 kernel: [ 18.531250] attempt to access beyond end of device Does the reboot happen if you remove the MMC? There was earlier some case where an application infinitely reading corrupted MMC FAT file system could sometimes cause kernel panic, but that should have been fixed for N810 Chinook. - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
ANN: LightMediaScanner 0.1
Hi folks, INdT just released our media scanner as LGPL: http://lms.garage.maemo.org/ Lightweight media scanner meant to be used in not-so-powerful devices, like embedded systems or old machines. Provides an optimized way to recursively scan directories, handling the parser in a child process, avoiding breaks of the main process when parsers break (quite common with such bad libs and tags). Parsers are plugins in the form of shared objects, so it's easy to add new without having to recompiling the scanner. The scanner will use SQLite3 to store file-mtime association, avoiding parsing files that are already up-to-date. This SQLite connection and the file id within the master table 'files' are handled to plugins for relationship with other tables. I wrote it to be stable and avoid crashes on the main process, that's why it uses two processes. This can slow things down a bit, but worth the stability. In future I plan to provide an unsafe version that does it all in the same process. We also provide python bindings and some parser plugins: - jpeg - id3lib (needs to be rewritten without dependency on this library, which is not that good as we wished) - ogg - m3u - pls - video-dummy (does no parse of files at all, just register based on known file extensions). You requested for an open source Canola, ok, we were unable to release everything, but at least some bits we're contributing back, expect more soon. :-) -- Gustavo Sverzut Barbieri -- Jabber: [EMAIL PROTECTED] MSN: [EMAIL PROTECTED] ICQ#: 17249123 Skype: gsbarbieri Mobile: +55 (81) 9927 0010 ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: ANN: LightMediaScanner 0.1
Hi Barbieri, Do you have performance tests about lms? I not found something related on this page. -- Allan Bezerra On Dec 13, 2007 12:32 PM, Gustavo Sverzut Barbieri [EMAIL PROTECTED] wrote: Hi folks, INdT just released our media scanner as LGPL: http://lms.garage.maemo.org/ Lightweight media scanner meant to be used in not-so-powerful devices, like embedded systems or old machines. Provides an optimized way to recursively scan directories, handling the parser in a child process, avoiding breaks of the main process when parsers break (quite common with such bad libs and tags). Parsers are plugins in the form of shared objects, so it's easy to add new without having to recompiling the scanner. The scanner will use SQLite3 to store file-mtime association, avoiding parsing files that are already up-to-date. This SQLite connection and the file id within the master table 'files' are handled to plugins for relationship with other tables. I wrote it to be stable and avoid crashes on the main process, that's why it uses two processes. This can slow things down a bit, but worth the stability. In future I plan to provide an unsafe version that does it all in the same process. We also provide python bindings and some parser plugins: - jpeg - id3lib (needs to be rewritten without dependency on this library, which is not that good as we wished) - ogg - m3u - pls - video-dummy (does no parse of files at all, just register based on known file extensions). You requested for an open source Canola, ok, we were unable to release everything, but at least some bits we're contributing back, expect more soon. :-) -- Gustavo Sverzut Barbieri -- Jabber: [EMAIL PROTECTED] MSN: [EMAIL PROTECTED] ICQ#: 17249123 Skype: gsbarbieri Mobile: +55 (81) 9927 0010 ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: apt-get; gstreamer-dev; pkg-config has no installation candidate -- addon
addon: executable pkg-config indeed exists and is linked to the host-system. I solved this problem, by faking a pkg-config package (empty packages with pkg-config-description) and installed it via 'dpkg -i'. Then 'apt-get install libgstreamer-plugins-base0.10-dev' worked and I compiled my gstreamer-plugin now! Looks like this is actually a bug in the installer-script (should pkg-config be installed via a virtual empty package?) This had been an issue before in Jan 2007, it seems: http://www.gossamer-threads.com/lists/maemo/developers/14191 Any comments? Does nobody use gstreamer-dev? Can anyone confirm this behaviour? Johannes [EMAIL PROTECTED] wrote on 13/12/2007 09:56:42 AM: * summary: gstreamer-dev cannot be installed due to package dependency to pkg-config. But pkg-config has no installation candidate * Hi, I would like to built a gstreamer-plugin for the N800 from source. Therefore I need gstreamer-dev installed. I'm running scratchbox 1.0.7 on a debian host. * This command works fine: apt-get install gstreamer0.10-tools gstreamer0.10-plugins-base gstreamer0.10-plugins-good * This does not: apt-get install libgstreamer-plugins-base0.10-dev = Message: ... pkg-config but it is not installable == apt-get install pkg-config log start --- [sbox-testtarget: ~/gst-mpsdec-plugin] apt-get install pkg-config Reading Package Lists... Done Building Dependency Tree... Done Package pkg-config is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package pkg-config has no installation candidate log end --- Package pkg-config has no installation candidate ... But Why? Am I missing a repository? sources.list of scratchbox --- deb http://repository.maemo.org/ bora free non-free deb http://repository.maemo.org/extras bora free non-free sources.list of scratchbox end --- Thanks! Johannes ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: web based local application GUIs
Hi guys, Actually this problem indeed happened. and that was a bad thing to have closed (the scanner configuration etc) So we did solve the right way this time: no cross scanning, watch only user specified folders, uses a lot less memory, It's open source (in garage) and of course there's no more the configuration daemon that also gave us nightmares. The bad thing was to be closed, and work on simultaneos projects. About the CPU time, apart from the bug, in a bunch of test that we did it, when we turned off text scrolling our consumption was almost identical of the media player. So actually 2 devices fully powered playing a huge playlist in loop, the canola one died only a couple of minutes after the other. So just to clarify that was nothing but a BUG, like the thousand crashes we got just by playing media files in those first OSes. BR Marcelo On Nov 26, 2007 10:53 PM, Igor Stoppa [EMAIL PROTECTED] wrote: On Mon, 2007-11-26 at 15:31 -0500, ext Jesse Guardiani wrote: Let's please try to avoid stop energy in this thread. http://www.userland.com/whatIsStopEnergy Nice link. But I don't think it applies here. I _did_ propose an alternative. Of course you are free to ignore it, but your energy would be better spent if directed toward something useful. I'm just trying to help you avoid ending up in a Canola-like situation where, after you have delivered your nice application, somebody complains that the battery lasts nothing, we check what could be and then we find out that it's Canola sucking current all the time. On demand sounds great in theory, but let's think about it for a second: How do you start on-demand a web app? (HTTPD daemon) How do you play the next track when the current track finishes playing? (Kagu daemon, or FastCGI Kagu daemon + HTTPD daemon) Yes, that's the intrinsic problem of using an http-based approach. You rely on the http daemon being nice. Kagu is used very similar to a daemon. It runs as long as you're playing music. And if that's all you use an n800 for then it's always running. It might even be in the background if you're taking notes or browsing the web. The difference is that it has a GUI right now. I'd like to make that portion optional to save some memory/CPU when you aren't using it. I'd also like to make startup time faster, and I'd like to make a web frontend for it. Then you have to make sure that it will have 0% CPU residency, otherwise you'll be stealing playback time from your use-case. And you'll be taking memory no matter what, but hopefully not too much. Also, if you choose this approach, it is worth mentioning it in the release notes of your application, so that users don't get the false impression that your sw is harmless to battery life. No, I don't mean an always on daemon. I mean an on-demand daemon. A background process that runs when you need it and doesn't when you don't. I'm not a userland guy, but for what i remember, dbus should be able to start for you services that are not running, and dbus is _already_ running all the time. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? -- Cheers, Igor Igor Stoppa [EMAIL PROTECTED] (Nokia Multimedia - CP - OSSO / Helsinki, Finland) ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
ANN: rootsh -- alternative to becomeroot
Hi Rootsh is a command that installs at /usr/bin/rootsh and is setuid root by debian package postinst script. Usage: rootsh [[-a arg0] command [args...]] Without command it runs $SHELL, or /bin/sh unless $SHELL defined. improvements over becomeroot * Does not edit any files (/etc/sudoers), uninstall just removes /usr/bin/rootsh * Can run command directly with root privileges * Just needs 'r' 'o' tab enter to run on xterm window Dangerous tool it is, but powerful in capable hands (keep security in mind when using this tool). Sources and armel debian package available at http://www.iki.fi/too/sw/maemo/rootsh/ Tested on 770 and N800, OS2006 and OS2007 Examples: $ rootsh $ rootsh id $ rootsh -a hello sh -c 'echo $0' Tomi ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Having problems getting build enviroment set up (Chinook)
I'm having a problem getting the build tools properly configured. I've read various online articles/books/docs and I have a start. The problem is that it doesn't compile anything. Below is output directory structure. I can't really concentrate on developing until I can simplify builds. I know it's not invoking the compiler as some of the files have errors. If I compile by hand, then it doesn't 'attempt' to compile them. Can anyone help? Point me to a better place to ask? TIA, Bill I reconfigure with the following: autoreconf; ./configure Output of make: [sbox-SDK_BETA_X86: ~/prgms/ppim/trunk] make make all-recursive make[1]: Entering directory `/home/wehope/prgms/ppim/trunk' Making all in src make[2]: Entering directory `/home/wehope/prgms/ppim/trunk/src' make[3]: Entering directory `/home/wehope/prgms/ppim/trunk/src' source='pPim.cpp' object='pPim.o' libtool=no \ depfile='.deps/pPim.Po' tmpdepfile='.deps/pPim.TPo' \ depmode=none /bin/sh ../config/depcomp \ g++ -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -c -o pPimString.o pPimString.cpp source='pPimTime.cpp' object=' pPimTime.o' libtool=no \ depfile='.deps/pPimTime.Po' tmpdepfile='.deps/pPimTime.TPo' \ depmode=none /bin/sh ../config/depcomp \ g++ -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -c -o pPimTime.o pPimTime.cpp source='ppim.cpp' object='ppim.o' libtool=no \ depfile='.deps/ppim.Po' tmpdepfile='.deps/ppim.TPo' \ depmode=none /bin/sh ../config/depcomp \ g++ -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -c -o ppim.o ppim.cpp source='refList.cpp' object='refList.o' libtool=no \ depfile='.deps/refList.Po' tmpdepfile='.deps/refList.TPo' \ depmode=none /bin/sh ../config/depcomp \ g++ -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -c -o refList.o refList.cpp source='sio.cpp' object='sio.o' libtool=no \ depfile='.deps/sio.Po' tmpdepfile='.deps/sio.TPo' \ depmode=none /bin/sh ../config/depcomp \ g++ -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -c -o sio.o sio.cpp g++ -g -O2 -o ppim pPim.o pPimTime.o ppim.o refList.o sio.o sbox-i686-linux-g++: pPimString.o: No such file or directory sbox-i686-linux-g++: pPimTime.o: No such file or directory sbox-i686-linux-g++: ppim.o: No such file or directory sbox-i686-linux-g++: refList.o: No such file or directory sbox-i686-linux-g++: sio.o: No such file or directory sbox-i686-linux-g++: no input files make[3]: *** [ppim] Error 1 make[3]: Leaving directory `/home/wehope/prgms/ppim/trunk/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/wehope/prgms/ppim/trunk/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/wehope/prgms/ppim/trunk' make: *** [all] Error 2 Snippet of make -d output: Considering target file `pPimTime.o'. File `pPimTime.o' does not exist. Looking for an implicit rule for `pPimTime.o'. Trying pattern rule with stem `pPimTime'. Trying implicit prerequisite `pPimTime.cpp'. Found an implicit rule for `pPimTime.o'. Considering target file `pPimTime.cpp'. Looking for an implicit rule for `pPimTime.cpp'. Trying pattern rule with stem `pPimTime.cpp'. Trying implicit prerequisite `pPimTime.cpp,v'. Trying pattern rule with stem `pPimTime.cpp'. Trying implicit prerequisite `RCS/pPimTime.cpp,v'. Trying pattern rule with stem `pPimTime.cpp'. Trying implicit prerequisite `RCS/pPimTime.cpp'. Trying pattern rule with stem `pPimTime.cpp'. Trying implicit prerequisite `s.pPimTime.cpp'. Trying pattern rule with stem `pPimTime.cpp'. Trying implicit prerequisite `SCCS/s.pPimTime.cpp'. No implicit rule found for `pPimTime.cpp'. Finished prerequisites of target file `pPimTime.cpp'. No need to remake target `pPimTime.cpp'. Finished prerequisites of target file `pPimTime.o'. Must remake target `pPimTime.o'. source='pPimTime.cpp' object='pPimTime.o' libtool=no \ depfile=' .deps/pPimTime.Po' tmpdepfile='.deps/pPimTime.TPo' \ depmode=none /bin/sh ../config/depcomp \ g++ -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -c -o pPimTime.o pPimTime.cpp Putting child 0x080831e0 (pPimTime.o) PID 14700 on the chain. Live child 0x080831e0 (pPimTime.o ) PID 14700 Got a SIGCHLD; 1 unreaped children. Reaping winning child 0x080831e0 PID 14700 Removing child 0x080831e0 PID 14700 from chain. Successfully remade target file `pPimTime.o'. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Kismet on N800 stops running after 1-2 minutes
Found that others also encountered a similar problem and as someone suggested, I increased the automatic connection search interval (to 60 minutes) and crossed my fingers. Unfortunately, that doesn't fix the problem. Any other suggestions? Basically, Kismet runs fine for a couple of minutes and the packet counter stops increasing (the application is still running and the elapsed time is updated but basically sniffing stops working). jYj ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
