Re: Problem editing wiki
I tried and its working OK for me as well. Thanks BrendaWang wrote: > > Hi, I am Openmoko Wiki editor, > This problem seems caused by clouldTag extension, now we disabled this > function. > And while I edit wiki, it's OK now . So it fixed. > Please let me know if it OK for you also. > > Brenda > > glownan ??: >> Thanks! >> >> >> Thomas Franck wrote: >> >>> Hi.. >>> >>> >>>> I have a problem editing the wiki. >>>> [...] >>>> Is anyone else experiencing this? >>>> Do you know what can be causing it? >>>> >>> Known problem.. see: >>> http://n2.nabble.com/whitespace-going-missing-on-wikipages-td1479519ef1958.html#a1479519 >>> >>> -- >>> Thomas >>> >>> >>> ___ >>> Openmoko community mailing list >>> community@lists.openmoko.org >>> http://lists.openmoko.org/mailman/listinfo/community >>> >>> >>> >> >> > > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > > -- View this message in context: http://n2.nabble.com/Problem-editing-wiki-tp1499011p1588805.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian -FSO -GPS] No Fix
Yesterday I flashed the latest SHR image and the problem has disappeared, everything is working fine again. I don't know where the problem was as before flashing I was doing an opkg update/upgrade everyday and the issue was still there. ant wrote: > > > My FSO 4.1 is running the fso-gpsd too. > > The only oddity with mine is that it lives on the SD card. I deliberately > kept > everything clean as far as the install goes - I just installed tangoGPS > after > installing FSO 4.1, then when the GPS didn't work I did a opkg > update/upgrade > on 24th and tried it again, then I enabled logging and reported on my > findings. > > Anyone got any pointers ? I'm a bit of a noob with the freerunner though > I've > been sysadmining on Linux for, um, more years than I care to remember :-) > > > On Tuesday 25 November 2008 22:13:08 Julien Cassignol wrote: >> On Tue, Nov 25, 2008 at 10:24 PM, glownan <[EMAIL PROTECTED]> wrote: >> > Hi, I'm using SHR and having the same problem. >> >> SHR latest image was shipped with gpsd instead of fso-gpsd. >> Just opkg remove --force-depends gpsd; opkg install fso-gpsd and it'll >> work. >> >> Future images will be corrected. > > > > -- > > Antony King - 01908 268 901 > Systems Consultant > SolutionTrax Technologies - http://www.solutiontrax.com > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > > -- View this message in context: http://n2.nabble.com/-Debian--FSO--GPS--No-Fix-tp1521077p1584706.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian -FSO -GPS] No Fix
Ummm, Looks like that is not the problem, gpsd is not installed and fso-gpsd is. This is what I got when tried to uninstall/install gpsd/fso-gpsd [EMAIL PROTECTED] ~ $ opkg remove --force-depends gpsd No packages removed. [EMAIL PROTECTED] ~ $ opkg install fso-gpsd Package fso-gpsd (0.7+gitr25+d10a69e11287a8f7a6477ad9c31d53ce18be9a8f-r1.1) installed in root is up to date. Does someone know what the meaning of that "Exception 0x8040 was trapped !" message is? It is received soon after the gps chip is powered on by ogpsd and the almanac data is uploaded to the gps chip. Don't know if it is related to this problem. This is the whole message where it appears 2008.11.25 22:55:46 ogpsdDEBUGDiscarded data not UBX '\n$GPTXT,' 2008.11.25 22:55:46 ogpsdDEBUGDiscarded data not UBX '01,01,00' 2008.11.25 22:55:46 ogpsdDEBUGDiscarded data not UBX ',Excepti' 2008.11.25 22:55:46 ogpsdDEBUGDiscarded data not UBX 'on 0x800' 2008.11.25 22:55:46 ogpsdDEBUGDiscarded data not UBX '00040 wa' 2008.11.25 22:55:46 ogpsdDEBUGDiscarded data not UBX 's trappe' 2008.11.25 22:55:46 ogpsdDEBUGDiscarded data not UBX 'd !*7E\r\n' Julien Cassignol wrote: > > On Tue, Nov 25, 2008 at 10:24 PM, glownan <[EMAIL PROTECTED]> wrote: >> >> Hi, I'm using SHR and having the same problem. > > SHR latest image was shipped with gpsd instead of fso-gpsd. > Just opkg remove --force-depends gpsd; opkg install fso-gpsd and it'll > work. > > Future images will be corrected. > > -- > Julien Cassignol > http://www.ainulindale.net > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > > -- View this message in context: http://n2.nabble.com/-Debian--FSO--GPS--No-Fix-tp1521077p1578627.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian -FSO -GPS] No Fix
Hi, I'm using SHR and having the same problem. Frameworkd logs shows the same
that ant posted. ogpsd is receiving nmea data that is discarding because is
not UBX data, but it looks like the lines are not being properly separated,
is processing the lines by chunks and sometimes joining the end of a line
with the beginning of the next one. Is it the right behavior?
See some parts of the log
...
2008.11.24 14:14:09 ogpsdDEBUGDiscarded data not UBX
'\n$GPRMC,,V,,N*53\r\n$GPVTG,N*30\r\n$GPGGA,,0,00,99.99,,*48\r\n$GPGSA,A'
2008.11.24 14:14:09 ogpsdDEBUGDiscarded data not UBX ',1,,'
2008.11.24 14:14:09 ogpsdDEBUGDiscarded data not UBX
',,,99.99,99.'
2008.11.24 14:14:09 ogpsdDEBUGDiscarded data not UBX
'99,99.99*30\r\n$GPGSV,1,1,00*79\r\n$GPGLL,,V,N*64\r\n$GPZDA,00,00*48\r'
2008.11.24 14:14:10 ogpsdDEBUGDiscarded data not UBX
'\n$GPRMC,,V,,N*53\r\n$GPVTG,N*30\r\n$GPGGA,,0,00,'
2008.11.24 14:14:10 ogpsdDEBUGDiscarded data not UBX
'99.99,,*48\r\n'
...
...
2008.11.24 14:14:17 ogpsdDEBUGDiscarded data not UBX '$GPGSA,A'
2008.11.24 14:14:17 ogpsdDEBUGDiscarded data not UBX ',1,,'
2008.11.24 14:14:17 ogpsdDEBUGDiscarded data not UBX ',,,9'
2008.11.24 14:14:17 ogpsdDEBUGDiscarded data not UBX '9.99,99.'
2008.11.24 14:14:17 ogpsdDEBUGDiscarded data not UBX '99,99.99'
2008.11.24 14:14:17 ogpsdDEBUGDiscarded data not UBX '*30\r\n$GP'
2008.11.24 14:14:17 ogpsdDEBUGDiscarded data not UBX 'GSV,1,1,'
2008.11.24 14:14:17 ogpsdDEBUGDiscarded data not UBX '01,07,,,'
2008.11.24 14:14:17 ogpsdDEBUGDiscarded data not UBX '41*7A\r\n$'
2008.11.24 14:14:17 ogpsdDEBUGDiscarded data not UBX 'GPGLL,,,'
2008.11.24 14:14:17 ogpsdDEBUGDiscarded data not UBX ',,,V,N*6'
2008.11.24 14:14:17 ogpsdDEBUGDiscarded data not UBX '4\r\n$GPZD'
2008.11.24 14:14:17 ogpsdDEBUGDiscarded data not UBX 'A,00'
...
opkg says the version of frameworkd I have installed is
0.8.4.4+gitr758+17c759181713037a6d8e31b96d65245d576c0015-r0.1
ant wrote:
>
>
> I'm using FSO 4.1 , and have a similar problem. Enabling debug on
> framework
> gives messages that suggest it is sending NMEA data when frameworkd is
> expexting UBX data. There's a curious message in the logs - 'exception
> 0x8040 was trapped' .The GPS clearly has power. Here's some of the
> log:
>
>
> Nov 24 14:44:45 om-gta02 user.info 2008.11.24 14:44:45 ogpsdINFO
> enabling
> Nov 24 14:44:45 om-gta02 user.debug 2008.11.24 14:44:45 ogpsdDEBUG
> (writing '1'
> to
> '/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-gps.0/pwron')
> Nov 24 14:44:45 om-gta02 user.debug 2008.11.24 14:44:45 ogpsdDEBUG
> Sending UBX packet of type CFG-SBAS: {'usage': 7, 'scanmode': 0, 'mode':
> 1, 'maxsbas': 3}
> Nov 24 14:44:45 om-gta02 user.debug 2008.11.24 14:44:45 ogpsdDEBUG
> Sending UBX packet of type CFG-PRT: []
>
> followed by some almenac data and then this interesting snippet:
>
>
> Nov 24 14:44:48 om-gta02 user.debug 2008.11.24 14:44:48 ogpsdDEBUG
> Discarded data not UBX '$GPTXT,01,01,02,u-blox '
> Nov 24 14:44:49 om-gta02 user.debug 2008.11.24 14:44:49 ogpsdDEBUG
> Discarded data not UBX 'ag - www.u-blox.com*50\r\n'
> Nov 24 14:44:49 om-gta02 user.debug 2008.11.24 14:44:49 ogpsdDEBUG
> Discarded data not UBX '$GPTXT,01,01,02,ANTARIS ATR062x HW
> 80040001*26\r\n$GPTXT,01,01,02,ROM CORE 5.00Jan 09 20'
> Nov 24 14:44:49 om-gta02 user.debug 2008.11.24 14:44:49 ogpsdDEBUG
> Discarded data not UBX '06 12:00:00*76\r\n'
> Nov 24 14:44:49 om-gta02 user.debug 2008.11.24 14:44:49 ogpsdDEBUG
> Discarded data not UBX '$GPTXT,01,01,02,'
> Nov 24 14:44:49 om-gta02 user.debug 2008.11.24 14:44:49 ogpsdDEBUG
> Discarded data not UBX 'LIC 1EBF'
> Nov 24 14:44:49 om-gta02 user.debug 2008.11.24 14:44:49 ogpsdDEBUG
> Discarded data not UBX '-BD07-E8'
> Nov 24 14:44:49 om-gta02 user.debug 2008.11.24 14:44:49 ogpsdDEBUG
> Discarded data not UBX '3D-6BE1-'
> Nov 24 14:44:49 om-gta02 user.debug 2008.11.24 14:44:49 ogpsdDEBUG
> Discarded data not UBX '0F7A*50\r'
> Nov 24 14:44:49 om-gta02 user.debug 2008.11.24 14:44:49 ogpsdDEBUG
> Discarded data not UBX '\n$GPTXT,'
> Nov 24 14:44:49 om-gta02 user.debug 2008.11.24 14:44:49 ogpsdDEBUG
> Discarded data not UBX '01,01,00'
> Nov 24 14:44:49 om-gta02 user.debug 2008.11.24 14:44:49 ogpsdDEBUG
> Discarded data not UBX ',Excepti'
> Nov 24 14:44:49 om-gta02 user.debug 2008.11.24 14:44:49 ogpsdDEBUG
> Discarded data not UBX 'on 0x800'
> Nov 24 14:44:49 om-gta02 user.debug 2008.11.24 14:44:49 ogpsdDEBUG
> Discarded data not UBX '00040 was trappe'
> Nov 24 14:44:49 om-gta02 user.debug 2008.11.24 14:44:49 ogpsdDEBUG
> Discarded data not UBX 'd !*7E\r\n'
>
>
>
> On Saturday 22 November
Re: Problem editing wiki
Thanks! Thomas Franck wrote: > > Hi.. > >> I have a problem editing the wiki. >> [...] >> Is anyone else experiencing this? >> Do you know what can be causing it? > > Known problem.. see: > http://n2.nabble.com/whitespace-going-missing-on-wikipages-td1479519ef1958.html#a1479519 > > -- > Thomas > > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > > -- View this message in context: http://n2.nabble.com/Problem-editing-wiki-tp1499011p1499109.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Problem editing wiki
Hi all, I have a problem editing the wiki. Every time I try to edit a page the format of all the preformated text (lines starting with a space) is missing, i.e I edit a page, and before modifying anything I click "Show changes" and I can see that all the lines of the page starting with a space are being modified. So I cannot edit any page without messing it. Is anyone else experiencing this? Do you know what can be causing it? p.s. I'm trying it from work and don't know if the proxy has something to do with this, I'll try it later from home. -- View this message in context: http://n2.nabble.com/Problem-editing-wiki-tp1499011p1499011.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Non HID Bluetooth keyboard. Success!
Hi list, I recently bought a bluetooth keyboard that is not HID (I didn't even know there was such a think. I thought all of them used the HID protocol). Then I read on the wiki that http://www.handhelds.org/moin/moin.cgi/kbdd kbdd could be useful for this, but didn't find anyone saying it works. I have tried it and it works for me, so I'll let you know what I did in case someone else wants to use this non standard keyboards. Mine is a http://www.dealextreme.com/details.dx/sku.6443 MSI bk100 (you can find it cheap on ebay) but I think it should work with others as well, as kbdd support several keyboards. 1. I found an ipkg package for kbdd in angstrom so I used it instead of compiling the source. ~#opkg install http://www.angstrom-distribution.org/feeds/2008/ipk/glibc/armv4t/base/kbdd_0.12+svn20061019-r0.1_armv4t.ipk 2. Get the address of the keyboard ~#hcitool scan Scanning ... 00:0F:F6:00:D9:05 BT-FoldableKB 3. Use rfcomm to bind the keyboard ~#rfcomm bind 0 00:0F:F6:00:D9:05 4. Load uinput module ~#modprobe uinput 5. Run passkey-agent in the background ~#passkey-agent 00:0F:F6:00:D9:05 6. Run kbdd in the background (you can specify a different type of keyboard with the -t option, mine works well with btfoldable) ~#kbdd -p /dev/rfcomm0 -t btfoldable & And that's all, you should be able to use your keyboard. I also attach a small script I wrote to connect and disconnect the keyboard, it have to be modified to suit your keyboard. An icon on the desktop to run it is very handy, you just press the connect key of your keyboard and click it to connect, and click it again when you want to disconnect the keyboard. #!/bin/sh # Change this to suit your keyboard. KBADDRESS=00:11:22:33:44:55 KBPIN= KBTYPE=btfoldable RFCOMMPORT=0 KBDDPID=`pidof kbdd` if [ -z "$KBDDPID" ] ; then modprobe uinput rfcomm bind $RFCOMMPORT $KBADDRESS passkey-agent $KBPIN $KBADDRESS & kbdd -p /dev/rfcomm$RFCOMMPORT -t $KBTYPE & else kill $KBDDPID PKAGENTID=`pidof passkey-agent` if [ ! -z "$PKAGENTID" ] ; then kill $PKAGENTID fi rfcomm release $RFCOMMPORT rmmod uinput fi Hope it helps someone. P.S. Make sure bluetooth is enabled, otherwise nothing of this is going to work ;) -- View this message in context: http://n2.nabble.com/Non-HID-Bluetooth-keyboard.-Success%21-tp1496389p1496389.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
