Re: apt-get; gstreamer-dev; pkg-config has no installation candidate -- addon
I can't completely exclude that I used an older version of the installer-script, since I have two version: maemo-scratchbox-install_3.0.sh or maemo-scratchbox-install_3.1.sh Is there a way to determine which installer scripts have been used after the installation of the scratchbox? But I used this one for sure: maemo-sdk-nokia-binaries_3.2.sh Johannes [EMAIL PROTECTED] wrote on 13/12/2007 06:14:14 PM: 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 thisbehaviour? 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 anotherpackage. 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 ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: N810 Resets
Hi, ext Alex Iliadis wrote: Hi Eero, On Thursday 13 December 2007 10:16:09 am you wrote: 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. Reflashing doesn't do anything to the MMCs (whether it's the N810 internal one of something that user can change). You can format it from the file manager or from Desktop after connecting the USB cable. In Chinook the MMC is mounted as read-only if it's corrupted. However if something in system is accessing it incessantly, it's possible that this can cause some instability. Btw. As everybody knows, the MicroSoft FAT file system used on the memory cards wasn't designed to be robust. If you unplug the USB cable without safely remove step, remove MMC otherwise when it's being written, take battery out when device is on or device HW (not SW) watchdog reboots it, the MMC FAT filesystem will get corrupted. (These aren't a problem with the internal JFFS2 filesystem) - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Having problems getting build enviroment set up (Chinook)
Hi, ext William Hope wrote: 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? So calls like this don't produce .o files: 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 What if you call it with -v from the command line: g++ -v -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -c -o sio.o sio.cpp - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Having problems getting build enviroment set up (Chinook)
ext William Hope wrote: 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 wonder what kind of articles/books/docs have you been reading? The SDK installation scripts and guides can be found in maemo.org: http://maemo.org/development/sdks/maemo_4_0_chinook_sdk.html [sbox-SDK_BETA_X86: ~/prgms/ppim/trunk] make That is not the default target name of a Chinook SDK. Are you sure your environment is set up properly? The SDK installer scripts should take care of this for you if you choose to run them. It's also possible to install things manually as described in the INSTALL.txt found from the link above. Cheers, Juha -- Juha Kallioinen JID: [EMAIL PROTECTED] ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Kismet on N800 stops running after 1-2 minutes
I believe it has to do with the wireless driver not working properly in monitoring mode. There are workarounds for it but they require some sort of scripting. Also the wireless driver corrupts packets in monitor mode so you may get inaccurate results sometimes. Thanks, Alex On Thursday 13 December 2007 08:24:12 pm Jaeyeon Jung wrote: 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 ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: N810 Resets
Hi, I think there was a bit of a confusion here, I was using the pre-bundled internal card shipped with the device with the default filesystem (jffs2). (No added MMC card) Anyway the problem has been solved. As you had originally suggested there was a peak point at which my application was trying to use 195MB of memory and that's when the reboot of the device occurred. I fixed that by manually controlling pythons garbage collector to force it to free memory. Thanks, Alex On Friday 14 December 2007 06:20:01 am you wrote: Hi, ext Alex Iliadis wrote: Hi Eero, On Thursday 13 December 2007 10:16:09 am you wrote: 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. Reflashing doesn't do anything to the MMCs (whether it's the N810 internal one of something that user can change). You can format it from the file manager or from Desktop after connecting the USB cable. In Chinook the MMC is mounted as read-only if it's corrupted. However if something in system is accessing it incessantly, it's possible that this can cause some instability. Btw. As everybody knows, the MicroSoft FAT file system used on the memory cards wasn't designed to be robust. If you unplug the USB cable without safely remove step, remove MMC otherwise when it's being written, take battery out when device is on or device HW (not SW) watchdog reboots it, the MMC FAT filesystem will get corrupted. (These aren't a problem with the internal JFFS2 filesystem) - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Kismet on N800 stops running after 1-2 minutes
That is a wireless driver error (probably has nothing to do with auto-search), and because the driver is closed source, Dragorn can't fix it. I've found putting the device into offline mode (so that the UI stops trying to manage it by connecting, disconnecting, searching for stuff, sending beacons, etc), then trying a few times will usually get it working. If I see it stops working, I quit and start it again. Oddly enough if I try enough times it will work, while on my 770 it seems to work every time. Hope this helps! Ryan Alex Iliadis wrote: I believe it has to do with the wireless driver not working properly in monitoring mode. There are workarounds for it but they require some sort of scripting. Also the wireless driver corrupts packets in monitor mode so you may get inaccurate results sometimes. Thanks, Alex On Thursday 13 December 2007 08:24:12 pm Jaeyeon Jung wrote: 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 -- Ryan Pavlik AbiWord Win32 Platform Maintainer, Art Lead: www.abisource.com AbiWord Community Outreach Project: www.cleardefinition.com/oss/abi/blog/ Optimism is the father that leads to achievement. -- Helen Keller The folder structure in a modern Linux distribution such as Ubuntu was largely inspired by the original UNIX foundations that were created by men with large beards and sensible jumpers. -- Jono Bacon, The Ubuntu Guide ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Kismet on N800 stops running after 1-2 minutes
That's not it, the main problem is not that the device stops receiving packets, it's the corruption of the packet content it does. As a note you can control power management by issuing: iwconfig wlan0 power off -Alex On Friday 14 December 2007 11:15:51 am Michael Wiktowy wrote: On Dec 13, 2007 8:24 PM, Jaeyeon Jung [EMAIL PROTECTED] wrote: 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). As I understand it, this is more of an issue with the power-saving features of the tablet. In monitor mode, the OS doesn't think that the wireless chip is being used so it puts it to sleep. I believe that keeping it plugged into the charger while you scan works. Not an ideal work-around but might be enough for what you want to do. /Mike ___ 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: Kismet on N800 stops running after 1-2 minutes
On Dec 13, 2007 8:24 PM, Jaeyeon Jung [EMAIL PROTECTED] wrote: 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). As I understand it, this is more of an issue with the power-saving features of the tablet. In monitor mode, the OS doesn't think that the wireless chip is being used so it puts it to sleep. I believe that keeping it plugged into the charger while you scan works. Not an ideal work-around but might be enough for what you want to do. /Mike ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Seeking advice about how to cross-compile 'modest' for bora
I'm trying to build the 'modest' email client for OS2007 (bora). I feel like I'm missing something really fundamental here, like whether there is a useful APT repository for this purpose or not. I downloaded the modest source from their svn repository, and it looks straightforward except that debian/control has a list of build-deps as long as your arm. Unfortunately I can't find any of them, as I don't know what repositories to look in. My root image contains the following pitiful /etc/apt/sources.list: deb http://repository.maemo.org/ bora free non-free deb-src http://repository.maemo.org/ bora free What repositories to I need to add in order to be able to run dpkg-buildpackage on the sources? I'm sure there must be useful repositories at garage.maemo.org, but I don't know where. (If it makes a difference I am running under scratchbox2 using the Code Sourcery toolchain.) Norman ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Seeking advice about how to cross-compile 'modest' for bora
O Venres 14/12/2007 ás 14:51, Norman Ramsey dicía... I downloaded the modest source from their svn repository, and it looks straightforward except that debian/control has a list of build-deps as long as your arm. Have you tried with debian/control.maemo-bora ? -- Alberto García González http://people.igalia.com/berto/ ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Starting Media Player by clicking a button
Hi guys, I have this really dumb problem, but I can´t get my head around it. My program should do the following: - When a button is pressed, a specific playlist (audio)-file should be opened in the media player. Sure, the first part is to add a callback for the buttons, but how do I open the file (and with it the media player. It should do the same as a double click on the file would)? Is it even possible to do do it this way? I would be unbelievable grateful for ideas, tips or hints. I´m kinda at my wits end. So long, V ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Kismet on N800 stops running after 1-2 minutes
On Fri, Dec 14, 2007 at 11:10:45AM -0500, Alex Iliadis wrote: That's not it, the main problem is not that the device stops receiving packets, it's the corruption of the packet content it does. As a note you can control power management by issuing: iwconfig wlan0 power off The original packet corruption issue was that the driver reported all frames, even those with invalid FCS checksums. However, since the driver also provides valid FCS data, this was fixed by adding checksum validation to Kismet to throw out frames. This is enabled on the nokia packet sources in Kismet. The dropping dead, and other issues, are part of why I never released an official Kismet package. Having just got an 810, I'm inspired again to look at it (and was just working on adding navkit support in to use the 810 builtin gps, actually) - are you saying there is another packet corruption issue which is time-based? Something that might *look* like corruption (to users and to kismet itself) would be if something else changes the interface back to managed mode - then it'll be sending 802.3 frames on an interface opened with some 802.11 linktype variant (prism2avs if I recall?) I'd be very interested in being able to turn off the wlan connection manager programatically, ie throw the device into offline mode and reconfigure the wifi for rfmon inside kismet, then reactive the state when it's done - but haven't found anything, yet, on how to do so. With OS2008 having better OTG host mode support, I'm also considering building the common USB drivers as a package so that you can use kismet with a USB wireless card and avoid the issues with the binary drivers. Obviously something like the alfa 500mW usb card won't work with the low-power OTG chipset, but the handful of USB nics I've got handy at least enumerated properly. -m -- Mike Kershaw/Dragorn [EMAIL PROTECTED] GPG Fingerprint: 3546 89DF 3C9D ED80 3381 A661 D7B2 8822 738B BDB1 A baby seal walks into a club... pgpyBwg3tjb7v.pgp Description: PGP signature ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Kismet on N800 stops running after 1-2 minutes
Hi, one question Ryan, does it mean Kismet ported to OS2006 (Nokia 770) by Cezary can be still run and there is gpsd package available for OS2006 too ? Frankly speaking I was not successful to install the proper OS2006 gpsd package yet. I am going to make some city maps for wifi hotspots using kismet. Thanks. Darius Ryan Pavlik [EMAIL PROTECTED] wrote: That is a wireless driver error (probably has nothing to do with auto-search), and because the driver is closed source, Dragorn can't fix it. I've found putting the device into offline mode (so that the UI stops trying to manage it by connecting, disconnecting, searching for stuff, sending beacons, etc), then trying a few times will usually get it working. If I see it stops working, I quit and start it again. Oddly enough if I try enough times it will work, while on my 770 it seems to work every time. Hope this helps! Ryan Alex Iliadis wrote: I believe it has to do with the wireless driver not working properly in monitoring mode. There are workarounds for it but they require some sort of scripting. Also the wireless driver corrupts packets in monitor mode so you may get inaccurate results sometimes. Thanks, Alex On Thursday 13 December 2007 08:24:12 pm Jaeyeon Jung wrote: 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 -- Ryan Pavlik AbiWord Win32 Platform Maintainer, Art Lead: www.abisource.com AbiWord Community Outreach Project: www.cleardefinition.com/oss/abi/blog/ Optimism is the father that leads to achievement. -- Helen Keller The folder structure in a modern Linux distribution such as Ubuntu was largely inspired by the original UNIX foundations that were created by men with large beards and sensible jumpers. -- Jono Bacon, The Ubuntu Guide ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers Send instant messages to your online friends http://uk.messenger.yahoo.com ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
How to port SDIO stack to N800/ N810 OSs ?
Kind request to developers from Nokia. Is there any chance to port SDIO stack to N800/N810 OSs in near future ? I am dreaming using internal SDIO gps card in N800 one day. CF gps card works fine in some PDAs. from http://sourceforge.net/projects/sdio-linux/ The SDIO-Linux project provides an open source SDIO-stack. The stack comes complete with drivers for the Host and Bus controllers, SD/MMC memory cards, SDIO-bluetooth and Atheros WLAN driver. Darius Send instant messages to your online friends http://uk.messenger.yahoo.com ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
