Re: USB networking with Ubuntu 9.04
Bingo. Thanks A LOT!
Is it possible to update the Wiki with that one. I think this will be a
great help to the whole community
Cheers
Tony
2009/10/7 Cristian Gómez cristianp...@gmail.com
Hi, What I do to connect the FreeRunner to the PC is running this script
[1] that I've made with the things listed on the wiki. To run it just type
sudo sh usb_networking.sh.
I used it on Arch Linux and Ubuntu and I think it works on every distro as
well. Any changes, suggestions are welcome. Currently it's on spanish.
Note: The script is configured for SHR so it uses the eth1 interface not
the usb0
[1] http://www.mediafire.com/download.php?zm0gtz2tyjq
/***
* Don't Worry...Be Linux
* Cristian Gómez Alvarez
* Ingeniero en Sistemas y Computación
* Universidad de Caldas
* Comunidad de Software Libre Manizales
* IEEE/WIE Student Member
* Linux User #463617
* Mi Blog: http://cristianpark.sehablalinux.com/
/
2009/10/6 Matthias Huber matthias.hu...@wollishausen.de
Tony Berth schrieb:
On Tue, Oct 6, 2009 at 10:00 PM, Frederik Sdun
frederik.s...@googlemail.com wrote:
* Tony Berth tonybe...@googlemail.com [06.10.2009 18:06]:
followed as described in:
http://wiki.openmoko.org/wiki/USB_Networking
-
Ubuntu 9.04 - the Jaunty Jackalope -- udev
One can see /etc/udev/rules.d that a device plugged in on USB will
be
called eth1. Go to system-Administration-Network and add the
parameters
for eth1 static ip, address 192.168.0.200 mask 255.255.255.192 add
your
default gateway. Thats is all.
Tested with Qi bootloader aka official MAC address of the Freerunner
: on
Android Koolu beta 7
Carig Philippines --frank 14:11, 17 June 2009 (UTC)
--
and eth1 gets assigned the proper IP address. I can connect to Neo
but
from there I don't have any connection to the 'outside'. Please
notice
that resolv.conf has the correct Opendns IPs!
Actually I should face the same problem as described in:
http://lists.openmoko.org/nabble.html#nabble-td3119750
but the postings there weren't of any help :(
Thanks
Tony
I used the config you can find in [0] and it works.
[0]
http://wiki.openmoko.org/wiki/USB_Networking#Debian.2C_Ubuntu_and_others
___
but this one 'ties' it in usb0 although it connects as eth1! How can this
work?
I also used the following entries in /etc/network/interfaces:
#freerunner3
allow-hotplug eth1
iface eth1 inet static
address 192.168.0.200
netmask 255.255.255.0
network 192.168.0.0
up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
up echo 1 /proc/sys/net/ipv4/ip_forward
up iptables -P FORWARD ACCEPT
down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
and didn't work! Openmoko wasn't able to get an IP address at all!
get ip adress ? dont understand this.
but i had to add this two lines to my /etc/ufw/ufw.conf
ufw allow from 192.168.0.202
ufw allow to 192.168.0.202
another trial with iptables needs to load some modules too:
#!/bin/sh
MOKO=192.168.0.202
echo 1 /proc/sys/net/ipv4/ip_forward
modprobe ipt_MASQUERADE
iptables -I FORWARD -j ACCEPT -d ${MOKO}/32
iptables -I FORWARD -j ACCEPT -s ${MOKO}/32
iptables -I POSTROUTING -t nat -j MASQUERADE -s ${MOKO}/32
--
Mit freundlichen Grüssen
Matthias Huber
Kohlstattstr. 14
86459 Wollishausen
Tel: 08238-7998
LPI000181125
___
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
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-U / All?] Illume Keyboard in Landscape
If someone can tell me an easy command for restarting the wrench, I could add it to omnewrotate (as an option). Rui On Tue, Oct 06, 2009 at 10:34:59PM -0400, Joshua Judson Rosen wrote: Stroller strol...@stellar.eclipse.co.uk writes: On 7 Oct 2009, at 00:26, undrwater wrote: ... Sorry, I read ALL these explanations as saying exactly the same thing, just in different ways. Perhaps you could clarify how they differ? Hm. I read: Problem 1: illume keyboard in landscape mode does not show (the keyboard itself doesn't show, only the prediction window and keyboard selector) Problem 2: qwerty button is hidden in shelf gadget and requires 2 taps to bring it up I posted problem 1, I think you understood problem 2. Am I right? Item 2 (I find that a problem, too) is discussed in this thread because it's necessary to go through this procedure to overcome problem 1. In this thread this pair of actions was originally described by Sebastian Krzyszkowiak in his post of 3 October 2009 14:55:51 BST. Joshua Judson Rosen's post of 3 October 2009 19:04:36 BST (I don't understand what you guys are talking about) may indicate that he doesn't suffer from problem 2. This is my experience: If the screen is already in landscape mode when the keyboard pops up, then the keyboaprd appears perfectly fine. Only if the keyboard is already shown prior to rotating the display, then it doesn't show properly when the display arrives in landscape mode. In this second case, the only steps required to fix the keyboard is to hide and then show it by: 0] Lowering the shelf and tapping qwerty (to hide the keyboard). 1] Lowering the shelf and tapping qwerty again (to re-show the keyboard). This does /not/ involve the `wrench', or changing any settings. The word none is not involved, nor is the word default. And, again: if the screen is rotated into landscape mode prior to the keyboard becoming visible, this procedure is not even necessary as the keyboard `just works'. Contrariwise, situation that I read Sebastian, Petr, et al. describing is: The keyboard does not appear properly in landscape mode, regardless of whether the display is rotated before or after the keyboard appears. If the screen is already in landscape mode when the keyboard pops up, the keyboard does *not* appear correctly. To make the keyboard appear properly in landscape mode, *this* following procedure must be repeated each time the screen is rotated: 0] Lower the shelf and tap the `wrench' icon. 2] Select Keyboard in the menu that appears. 3] Select the None radiobutton in the screen that appears. 4] Select the Default radiobutton (in the same screen, which remains until the Close button is pressed). [And, since I haven't actually seen /this/ scenario myself, I'm assuming that the following step is also needed:] 5] If the keyboard is not showing now, lower the shelf and tap qwerty to show it. The two situations (and procedures) look *remarkably* different to me. If this is unclear, I can probably post a video demonstrating my experience -- Don't be afraid to ask (Lf.((Lx.xx) (Lr.f(rr. ___ 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
Re: I buy FreeRunner on Europe
there is topic: Neo Freerunner + Debug board for Sale - Sweden posted 10 hours ago on the support list by Ingvaldur Sigurjonsson i...@telia.com Hi Selling my Neo Freerunner together with Debug board for 2000:- SEK or 195 €. All the standard stuff is included except the pen, went lost. Free shipping within Sweden. If you're in the Stockholm area, we can meet for a demo. Ingi /me is awaiting his commission :) 2009/10/7 Cristian Gómez cristianp...@gmail.com Hi guys, I've seen some posts offering used FreeRunner's on Europe but I don't if any of the offers is available right now. I have a friend on France who's interested on buying a FR hopefully on France or other European country where the sheep taxes are none or cheaper than from US. Thanks for you attention /*** * Don't Worry...Be Linux * Cristian Gómez Alvarez * Ingeniero en Sistemas y Computación * Universidad de Caldas * Comunidad de Software Libre Manizales * IEEE/WIE Student Member * Linux User #463617 * Mi Blog: http://cristianpark.sehablalinux.com/ / ___ 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
Re: USB networking with Ubuntu 9.04
Tony Berth schrieb:
Bingo. Thanks A LOT!
Is it possible to update the Wiki with that one. I think this will be
a great help to the whole community
if you would tell me wich of / or both tricks did it on your system ?
but i had to add this two lines to my /etc/ufw/ufw.conf
ufw allow from 192.168.0.202
ufw allow to 192.168.0.202
another trial with iptables needs to load some modules too:
#!/bin/sh
MOKO=192.168.0.202
echo 1 /proc/sys/net/ipv4/ip_forward
modprobe ipt_MASQUERADE
iptables -I FORWARD -j ACCEPT -d ${MOKO}/32
iptables -I FORWARD -j ACCEPT -s ${MOKO}/32
iptables -I POSTROUTING -t nat -j MASQUERADE -s ${MOKO}/32
--
Mit freundlichen Grüssen
Matthias Huber
Kohlstattstr. 14
86459 Wollishausen
Tel: 08238-7998
LPI000181125
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-U / All?] Illume Keyboard in Landscape
On Wednesday 07 October 2009 09:06:34 Rui Miguel Silva Seabra wrote: If someone can tell me an easy command for restarting the wrench, I could add it to omnewrotate (as an option). +1, that would be cool -- Adolph J. Vogel BEng(Hons) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: I buy FreeRunner on Europe
Hi, For a brand new one, in France you can contact Bearstech, they are the official reseller for France i believe. But Pulster (in DE) might be cheaper. Also, it might be worth having a look at eBay. -- View this message in context: http://n2.nabble.com/I-buy-FreeRunner-on-Europe-tp3779584p3780386.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
1024#
Hello. I've been wondering if all the freerunners are affected by bug #1024? I've got 2.6 one. And if not, how can I determine if mine is affected? Thanks a lot for any help and sorry for a nub question =) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: 1024#
Hi, On Wed, Oct 7, 2009 at 10:50 AM, Ivan Shirokov ivanshirok...@gmail.com wrote: I've been wondering if all the freerunners are affected by bug #1024? I've been wondering the same thing... It would seem that the extra current draw in suspend would affect all FRs, so having a #1024 fix-party would be a good idea in any case (?). Christ van Willegen -- 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: 1024#
On Wednesday 07 October 2009 10:57:02 Christ van Willegen wrote: Hi, On Wed, Oct 7, 2009 at 10:50 AM, Ivan Shirokov ivanshirok...@gmail.com wrote: I've been wondering if all the freerunners are affected by bug #1024? No, not all FR are affected, AFAIK I've been wondering the same thing... It would seem that the extra current draw in suspend would affect all FRs, so having a #1024 fix-party would be a good idea in any case (?). #1024 is not causing extra current drain, but the software solution to this bug: Not allowing Calypso entering deep sleep mode. You can check if your FR is suffering from #1024 editting /etc/frameworkd.conf and changing ti_calypso_deep_sleep = never to ti_calypso_deep_sleep = always then restarting framework: /etc/init.d/frameworkd restart After doing so, if your FR suffers from this bug, your modem will continuously register/unregister from GSM network when suspended, and you will lose calls On my case, it was nearly impossible to call FR when suspended + calypso deep sleep. But not all FR suffer from this bug. You should try it after fixing it. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: 1024#
On Wednesday 07 October 2009 10:57:02 Christ van Willegen wrote: Hi, A very good post about #1024: http://neofundas.blogspot.com/2009/09/1024-hardware-fixdeep-sleep.html ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: 1024#
On Wednesday 07 October 2009, Christ van Willegen wrote: Hi, On Wed, Oct 7, 2009 at 10:50 AM, Ivan Shirokov ivanshirok...@gmail.com wrote: I've been wondering if all the freerunners are affected by bug #1024? I've been wondering the same thing... It would seem that the extra current draw in suspend would affect all FRs, so having a #1024 fix-party would be a good idea in any case (?). All are potentially affected as they all have nominally the same capacitor value. Not all of them actually suffer from it though, probably due to component variation. Dieter found that on his he could start the problem by heating the chip by a few degrees, and stop it by letting it cool. Depending on how lucky you are you may have #1024 always, never, or only when the phone's in your pocket. There are two sources of extra current draw: recamping and not being in deep sleep mode. Recamping is the symptom of #1024 so is only an issue on phones suffering from it. Deep sleep mode is a config option in /etc/frameworkd.conf so if you don't suffer from #1024 you can always use deep sleep mode. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: 1024#
Hi, I've read the earlier-mentioned blog post, and have checked on IRC as well. #1024-fixed devices have a smaller current drain. Battery time can rise from 70h to 140h, even with deep_sleep=always already in the config file. Christ van Willegen ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: 1024#
David Garabana Barro a écrit : On Wednesday 07 October 2009 10:57:02 Christ van Willegen wrote: Hi, On Wed, Oct 7, 2009 at 10:50 AM, Ivan Shirokov ivanshirok...@gmail.com wrote: I've been wondering if all the freerunners are affected by bug #1024? No, not all FR are affected, AFAIK I've been wondering the same thing... It would seem that the extra current draw in suspend would affect all FRs, so having a #1024 fix-party would be a good idea in any case (?). #1024 is not causing extra current drain, but the software solution to this bug: Not allowing Calypso entering deep sleep mode. You can check if your FR is suffering from #1024 editting /etc/frameworkd.conf and changing ti_calypso_deep_sleep = never to ti_calypso_deep_sleep = always then restarting framework: /etc/init.d/frameworkd restart After doing so, if your FR suffers from this bug, your modem will continuously register/unregister from GSM network when suspended, and you will lose calls On my case, it was nearly impossible to call FR when suspended + calypso deep sleep. But not all FR suffer from this bug. You should try it after fixing it. Most of GTA02-A5/A6 have this bug. Once TI_CALYPSO_DEEP_SLEEP set to always, you can check with a little script done by KaZEr (see bleow) Launch it on screen, and redirect output to a file. If you have something like [2009-09-09 12:36:09.189663] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:36:15.088936] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:38:10.442808] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:38:13.020126] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:40:25.772918] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:40:28.620096] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:41:17.557676] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:41:20.404582] Signal : cid=3BB3, lac=0D48 Then you have the bug (trying to connect to GSM every second!) regards AstHrO Here's KaZeR's script : -- #!/usr/bin/python import dbus import dbus.glib import gobject import datetime def onNetworkStatus(status ): print '[%s] Signal : cid=%s, lac=%s' % (datetime.datetime.now(),status['cid'],status['lac'] ) bus = dbus.SystemBus(); bus.add_signal_receiver( onNetworkStatus, Status, org.freesmartphone.GSM.Network, org.freesmartphone.ogsmd, /org/freesmartphone/GSM/Device ) gobject.threads_init() dbus.glib.init_threads() main_loop = gobject.MainLoop() main_loop.run() -- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: 1024#
Thanks a lot. I'll give it a try =) On Wed, Oct 7, 2009 at 1:36 PM, Thomas HOCEDEZ thomas.hoce...@free.fr wrote: David Garabana Barro a écrit : On Wednesday 07 October 2009 10:57:02 Christ van Willegen wrote: Hi, On Wed, Oct 7, 2009 at 10:50 AM, Ivan Shirokov ivanshirok...@gmail.com wrote: I've been wondering if all the freerunners are affected by bug #1024? No, not all FR are affected, AFAIK I've been wondering the same thing... It would seem that the extra current draw in suspend would affect all FRs, so having a #1024 fix-party would be a good idea in any case (?). #1024 is not causing extra current drain, but the software solution to this bug: Not allowing Calypso entering deep sleep mode. You can check if your FR is suffering from #1024 editting /etc/frameworkd.conf and changing ti_calypso_deep_sleep = never to ti_calypso_deep_sleep = always then restarting framework: /etc/init.d/frameworkd restart After doing so, if your FR suffers from this bug, your modem will continuously register/unregister from GSM network when suspended, and you will lose calls On my case, it was nearly impossible to call FR when suspended + calypso deep sleep. But not all FR suffer from this bug. You should try it after fixing it. Most of GTA02-A5/A6 have this bug. Once TI_CALYPSO_DEEP_SLEEP set to always, you can check with a little script done by KaZEr (see bleow) Launch it on screen, and redirect output to a file. If you have something like [2009-09-09 12:36:09.189663] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:36:15.088936] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:38:10.442808] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:38:13.020126] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:40:25.772918] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:40:28.620096] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:41:17.557676] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:41:20.404582] Signal : cid=3BB3, lac=0D48 Then you have the bug (trying to connect to GSM every second!) regards AstHrO Here's KaZeR's script : -- #!/usr/bin/python import dbus import dbus.glib import gobject import datetime def onNetworkStatus(status ): print '[%s] Signal : cid=%s, lac=%s' % (datetime.datetime.now(),status['cid'],status['lac'] ) bus = dbus.SystemBus(); bus.add_signal_receiver( onNetworkStatus, Status, org.freesmartphone.GSM.Network, org.freesmartphone.ogsmd, /org/freesmartphone/GSM/Device ) gobject.threads_init() dbus.glib.init_threads() main_loop = gobject.MainLoop() main_loop.run() -- ___ 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
Re: Universal Remote for CE/HA? (openmoko)
On Friday 02 October 2009, Jed wrote: I glued a infrared led into the aux key for this purpose. Did someone already try to compile lirc for the FR? My attempt to just 'bitbake' it failed (missing kernel configuration). Hmmm, wonder if some of the other hand-held platforms do have IR? Surely there's at least one device?! Lets see there's: Android devices, Maemo devices, Axim x5xx (kinda), any others? Last crack ;-) Does anyone know of any OSS supported devices that do have IR integrated? Wifi would get most use in my intended application but IR would be handy! According to one review [1] the n900 has IR, and there's a universal remote app for it [2]. We'll have to wait and see exactly how open it is though. [1] http://my-simbian.com/other/preview_n900.php [2] http://irreco.garage.maemo.org/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Increasing GPS accuracy with EGNOS
I'll try to check it too. I'll let you know. Mickael Al Johnson a écrit : On Monday 05 October 2009, Joseph Reeves wrote: This is probably worth checking to see what is actually happening when in Europe, Someone tell me what command to run on what distro and I'll let you all know... If it was going to be that easy I'd have done it myself ;-) AFAIK there isn't a simple ubx utility that would allow us to send parameters to the GPS and watch for the returning messages, so adding a few lines to ogpsd is probably the easiest approach. For anyone who knows their way around ogpsd and ubx it should be quick and easy ;-) I'm not that person, so if I get round to it it may take a little longer... 2009/10/5 Al Johnson openm...@mazikeen.demon.co.uk: On Sunday 04 October 2009, Erik Lundin wrote: Good news, indeed. Does the Neo FreeRunner support EGNOS signals? Both the hardware and software? http://www.u-blox.com/en/download-center.html?task=view.downloadcid=83 According to this the Antaris 4 is capable of using WAAS, EGNOS and MSAS, collectively known as SBAS, and the signal is received through the GPS antenna. By default it is enabled, with one search channel, although this can be configured through the ubx protocol. The status can also be shown in ubx messages. This is probably worth checking to see what is actually happening when in Europe, as when it was written EGNOS was in test mode, and its use was disabled by default. It is unclear whether this was because of a 'test mode' flag in the signal or hardcoding in the firmware. ___ 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 ___ 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
no wifi
hi everyone, about a year ago , someone wrote in that he had found a way to same more energy from the battry by disabling the wifi, and added 2-3 commands that do that. i executed those commands, and now i want to re-enable the wifi again. anyone could know what settings i changed?(silly me live in a mess and don't remember). thanks. flecktor _ Hotmail: Trusted email with powerful SPAM protection. http://clk.atdmt.com/GBL/go/177141665/direct/01/___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: 1024#
On Wednesday 07 October 2009, Christ van Willegen wrote: Hi, I've read the earlier-mentioned blog post, and have checked on IRC as well. #1024-fixed devices have a smaller current drain. Battery time can rise from 70h to 140h, even with deep_sleep=always already in the config file. From the blog post: DocScrutinizer-with sleep=4 you either get 140h, or problems on recamping when out in the cold. In other words if you set deep_sleep=always you will either see the full battery life, or you will get recamping, which will reduce battery life. Fixed devices see more battery life after the fix than before because they suffered from recamping before the fix. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Increasing GPS accuracy with EGNOS
On Mon, Oct 5, 2009 at 9:02 PM, Al Johnson openm...@mazikeen.demon.co.uk wrote: On Sunday 04 October 2009, Erik Lundin wrote: Good news, indeed. Does the Neo FreeRunner support EGNOS signals? Both the hardware and software? http://www.u-blox.com/en/download-center.html?task=view.downloadcid=83 According to this the Antaris 4 is capable of using WAAS, EGNOS and MSAS, collectively known as SBAS, and the signal is received through the GPS antenna. By default it is enabled, with one search channel, although this can be configured through the ubx protocol. The status can also be shown in ubx messages. This is probably worth checking to see what is actually happening when in Europe, as when it was written EGNOS was in test mode, and its use was disabled by default. It is unclear whether this was because of a 'test mode' flag in the signal or hardcoding in the firmware. Other GPS receivers seem to have switched over automatically - http://www.openstreetmap.org/user/kevjs1982/diary/8160 . ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: no wifi
* flecktor nahu...@cs.bgu.ac.il [07.10.2009 11:51]: hi everyone, about a year ago , someone wrote in that he had found a way to same more energy from the battry by disabling the wifi, and added 2-3 commands that do that. i executed those commands, and now i want to re-enable the wifi again. anyone could know what settings i changed?(silly me live in a mess and don't remember). thanks. flecktor -- Hotmail: Trusted email with powerful SPAM protection. Sign up now. Could you post those commands? Frederik ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- IRC: playya @ Freenode, Gimpnet xmpp: pla...@draugr.de signature.asc Description: Digital signature ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR] new package: theremin (alfa version warning)
Aapo Rantalainen wrote: I packaged maemo-theremin[1] on freerunner SHR-U. It is nice musical tool but unfortunately it is just little bit too slowly to work smoothly. Anybody has any ideas how to get it working little bit faster? Package: http://www.opkg.org/package_287.html Info http://wiki.openmoko.org/wiki/Theremin -Aapo Rantalainen [1] http://theremin.garage.maemo.org/ Thanks a lot for the package. I think I found a solution to get it working a little bit better? First, I used the timbre Clarinet. Result is better than with the other timbers (SINE + ADSR, Plcuked String, Trombone). Then, I modified the Exec line in the .desktop file Exec=DISPLAY=:0.0 theremin renice -n 19 -p $! I don't understand why the DISPLAY=:0.0 makes the difference but it does. A video: http://www.youtube.com/watch?v=dVGIUSmP1rE -- Valéry ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
QtMoko v14
Hi, i have just uploaded QtMoko v14 debian images. QtMoko is stable distribution for based on Debian and Qtopia. It can be downloaded from here: http://activationrecord.net/radekp/qtmoko/download/ For more information see: http://qtmoko.org/ http://activationrecord.net/radekp/qtmoko/ http://activationrecord.net/radekp/qtmoko/screenshots/ Changes from previous version: * Fixed alarm * Maybe fixed loosing some incoming SMS * Updated kernel to latest andy-tracking As you can see there are not many changes. The main purpose of this release is to have version with working alarm and i would like to get some feedback about missing SMS bug. I cant reproduce it with this image (now i can even receive the concatenated SMS). So if you hit the SMS issue with this image, please let me know. Most valuable is way how to reproduce it and also AT log would be nice. If you are GPRS user then make sure you always fill username and password (even with some dummy values). So enjoy the images and thanks everybody who helped with this release. Cheers Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: 1024#
On Wednesday 07 Oct 2009 10:36:01 Thomas HOCEDEZ wrote: David Garabana Barro a écrit : If you have something like [2009-09-09 12:36:09.189663] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:36:15.088936] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:38:10.442808] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:38:13.020126] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:40:25.772918] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:40:28.620096] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:41:17.557676] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:41:20.404582] Signal : cid=3BB3, lac=0D48 Then you have the bug (trying to connect to GSM every second!) What would be considered a normal rate of connections? solar.george signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR] new package: theremin (alfa version warning)
On Wed, Oct 7, 2009 at 2:16 PM, Valery Febvre vfeb...@easter-eggs.com wrote: A video: http://www.youtube.com/watch?v=dVGIUSmP1rE WOW, you're an awesome player! Some real-world theremin videos. I would so much like to try one.. http://www.youtube.com/watch?v=xcTPRjiCs6sfeature=related http://www.youtube.com/watch?v=e6bSRcRAhncfeature=related http://www.youtube.com/user/ooo6#play/uploads/1/Bkp9bDGDd1w http://www.youtube.com/user/ooo6#play/uploads/6/mW0B1sipLBI r -- | risto h. kurppa | risto at kurppa dot fi | http://risto.kurppa.fi ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: 1024#
George Brooke a écrit : On Wednesday 07 Oct 2009 10:36:01 Thomas HOCEDEZ wrote: David Garabana Barro a écrit : If you have something like [2009-09-09 12:36:09.189663] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:36:15.088936] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:38:10.442808] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:38:13.020126] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:40:25.772918] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:40:28.620096] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:41:17.557676] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:41:20.404582] Signal : cid=3BB3, lac=0D48 Then you have the bug (trying to connect to GSM every second!) What would be considered a normal rate of connections? solar.george Once I fixed mine, I couldn't see any line ! I have to let the script run, then turning off on GSM through the preferences. This way I saw only one line. I can only say that there is no good rate, but there is a bad rate : multiple connections per second. Hope this helps. AstHrO ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: 1024#
On Wednesday 07 October 2009, George Brooke wrote: On Wednesday 07 Oct 2009 10:36:01 Thomas HOCEDEZ wrote: David Garabana Barro a écrit : If you have something like [2009-09-09 12:36:09.189663] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:36:15.088936] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:38:10.442808] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:38:13.020126] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:40:25.772918] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:40:28.620096] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:41:17.557676] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:41:20.404582] Signal : cid=3BB3, lac=0D48 Then you have the bug (trying to connect to GSM every second!) What would be considered a normal rate of connections? Under normal circumstances you would only see these messages with a change of cell, so cid would be different. The only time I know of that you might legitimately see repeated reconnection to the same cell is if you've got very low signal and it's the only cell visible. I get intermittent reconnection problems where the gap between reconnections is between 15s and several hours. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR] new package: theremin (alfa version warning)
Hi Aapo, Cool project. But seeing this I wonder - wouldn't it even be a better idea to use the accelerometers instead of the touchscreen? Or even use both: accelerometers for the pitch and touchscreen for the amplitude - like the original theremin :) Just my 2ct, Andreas Aapo Rantalainen wrote: I packaged maemo-theremin[1] on freerunner SHR-U. It is nice musical tool but unfortunately it is just little bit too slowly to work smoothly. Anybody has any ideas how to get it working little bit faster? Package: http://www.opkg.org/package_287.html Info http://wiki.openmoko.org/wiki/Theremin -Aapo Rantalainen [1] http://theremin.garage.maemo.org/ ___ 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
Re: [SHR] new package: theremin (alfa version warning)
Hi Andreas, Cool project. But seeing this I wonder - wouldn't it even be a better idea to use the accelerometers instead of the touchscreen? Or even use both: accelerometers for the pitch and touchscreen for the amplitude - like the original theremin :) Nice idea. This is originally made for N810 and it doesn't have accelerometers. But when N900 (with accelerometers) really comes maybe upstream is interested in this idea. -Aapo Rantalainen ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-U / All?] Illume Keyboard in Landscape
On 7 Oct 2009, at 03:34, Joshua Judson Rosen wrote: ... In this second case, the only steps required to fix the keyboard is to hide and then show it by: 0] Lowering the shelf and tapping qwerty (to hide the keyboard). 1] Lowering the shelf and tapping qwerty again (to re-show the keyboard). This does /not/ involve the `wrench', or changing any settings. ... Ok, excuse me. I am a new user and had been pressing at the wrench (or at least, trying to) to lower the shelf. With some experimentation I see that pressing anywhere in the shelf lowers it. My apologies, and thank you for the clear explanation, Stroller. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR] new package: theremin (alfa version warning)
On Wed, Oct 7, 2009 at 1:16 PM, Valery Febvre vfeb...@easter-eggs.com wrote: Aapo Rantalainen wrote: I packaged maemo-theremin[1] on freerunner SHR-U. I hear nothing else, just noise (zzZZZzz, brrrZZZrr) coming out of the speaker...:-( Any idea? Laszlo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Universal Remote for CE/HA? (openmoko)
I glued a infrared led into the aux key for this purpose. Did someone already try to compile lirc for the FR? My attempt to just 'bitbake' it failed (missing kernel configuration). Hmmm, wonder if some of the other hand-held platforms do have IR? Surely there's at least one device?! Lets see there's: Android devices, Maemo devices, Axim x5xx (kinda), any others? Last crack ;-) Does anyone know of any OSS supported devices that do have IR integrated? Wifi would get most use in my intended application but IR would be handy! According to one review [1] the n900 has IR, and there's a universal remote app for it [2]. We'll have to wait and see exactly how open it is though. [1] http://my-simbian.com/other/preview_n900.php [2] http://irreco.garage.maemo.org/ Awesome, thanks for pointing that out Al! This looks like the hand-held for me if my axim x50v doesn't work out! Cheers, Jed ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Increasing GPS accuracy with EGNOS
Christian wrote:
Al Johnson schrieb:
On Sunday 04 October 2009, Erik Lundin wrote:
Good news, indeed. Does the Neo FreeRunner support EGNOS signals? Both
the hardware and software?
http://www.u-blox.com/en/download-center.html?task=view.downloadcid=83
According to this the Antaris 4 is capable of using WAAS, EGNOS and MSAS,
collectively known as SBAS, and the signal is received through the GPS
antenna. By default it is enabled, with one search channel, although this
can
be configured through the ubx protocol. The status can also be shown in ubx
messages. This is probably worth checking to see what is actually happening
when in Europe, as when it was written EGNOS was in test mode, and its use
was
disabled by default. It is unclear whether this was because of a 'test mode'
flag in the signal or hardcoding in the firmware.
I found this in the source of ogpsd on my Freerunner:
def initializeDevice( self ):
# Use high sensitivity mode
#self.send(CFG-RXM, 2, {gps_mode : 2, lp_mode : 0})
# Enable use of SBAS (even in testmode)
self.send(CFG-SBAS, 8, {mode : 1, usage : 7, maxsbas : 3,
scanmode : 0})
So it seems that SBAS has always been enabled even in test mode. Does
anybody know where we can get information if sbas is really active and
used by the chip?
The comment is wrong, the mode value of 1 means that it uses SBAS but
not if its in test mode. The comment is a left over from the time the
value was 3, but then the whole line was commented out.
You can get SBAS status messages if you set it in the debug interface with:
mdbus -s org.freesmartphone.ogpsd /org/freedesktop/Gypsy
org.freesmartphone.GPS.UBX.SetDebugFilter NAV-SBAS True
and then listen to the signals with:
mdbus -l -s rg.freesmartphone.ogpsd /org/freedesktop/Gypsy
Look for DebugPacket signals.
I tried it for other signals, didn't have time yet to test if it works
for NAV-SBAS.
Baruch
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: 1024#
On Wednesday 07 October 2009 04:36:01 Thomas HOCEDEZ wrote: David Garabana Barro a écrit : On Wednesday 07 October 2009 10:57:02 Christ van Willegen wrote: Hi, On Wed, Oct 7, 2009 at 10:50 AM, Ivan Shirokov ivanshirok...@gmail.com wrote: I've been wondering if all the freerunners are affected by bug #1024? No, not all FR are affected, AFAIK I've been wondering the same thing... It would seem that the extra current draw in suspend would affect all FRs, so having a #1024 fix-party would be a good idea in any case (?). #1024 is not causing extra current drain, but the software solution to this bug: Not allowing Calypso entering deep sleep mode. You can check if your FR is suffering from #1024 editting /etc/frameworkd.conf and changing ti_calypso_deep_sleep = never to ti_calypso_deep_sleep = always then restarting framework: /etc/init.d/frameworkd restart After doing so, if your FR suffers from this bug, your modem will continuously register/unregister from GSM network when suspended, and you will lose calls On my case, it was nearly impossible to call FR when suspended + calypso deep sleep. But not all FR suffer from this bug. You should try it after fixing it. Most of GTA02-A5/A6 have this bug. Once TI_CALYPSO_DEEP_SLEEP set to always, you can check with a little script done by KaZEr (see bleow) Launch it on screen, and redirect output to a file. If you have something like [2009-09-09 12:36:09.189663] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:36:15.088936] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:38:10.442808] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:38:13.020126] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:40:25.772918] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:40:28.620096] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:41:17.557676] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:41:20.404582] Signal : cid=3BB3, lac=0D48 Then you have the bug (trying to connect to GSM every second!) regards AstHrO Here's KaZeR's script : -- #!/usr/bin/python import dbus import dbus.glib import gobject import datetime def onNetworkStatus(status ): print '[%s] Signal : cid=%s, lac=%s' % (datetime.datetime.now(),status['cid'],status['lac'] ) bus = dbus.SystemBus(); bus.add_signal_receiver( onNetworkStatus, Status, org.freesmartphone.GSM.Network, org.freesmartphone.ogsmd, /org/freesmartphone/GSM/Device ) gobject.threads_init() dbus.glib.init_threads() main_loop = gobject.MainLoop() main_loop.run() -- I am trying to run the script and I get: r...@om-gta02 ~ $ deep-sleep-check.py dsc.log File /usr/bin/deep-sleep-check.py, line 9 print '[%s] Signal : cid=%s, lac=%s' % ^ SyntaxError: invalid syntax I am not familiar with Python, so, can someone help me to fix this? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB networking with Ubuntu 9.04
On Wed, Oct 7, 2009 at 10:27 AM, Matthias Huber
matthias.hu...@wollishausen.de wrote:
Tony Berth schrieb:
Bingo. Thanks A LOT!
Is it possible to update the Wiki with that one. I think this will be a
great help to the whole community
if you would tell me wich of / or both tricks did it on your system ?
but i had to add this two lines to my /etc/ufw/ufw.conf
ufw allow from 192.168.0.202
ufw allow to 192.168.0.202
another trial with iptables needs to load some modules too:
#!/bin/sh
MOKO=192.168.0.202
echo 1 /proc/sys/net/ipv4/ip_forward
modprobe ipt_MASQUERADE
iptables -I FORWARD -j ACCEPT -d ${MOKO}/32
iptables -I FORWARD -j ACCEPT -s ${MOKO}/32
iptables -I POSTROUTING -t nat -j MASQUERADE -s ${MOKO}/32
what works was the script Cristian Gomez included in his reply!
Just for the records, the first time I run that script it does assign the
192.168.0.200 IP to eth1 but can't ping/access 192.168.0.202! Then:
- I disconnect Openmoko
- connect it again
- re-run the script and voila the connection is there!
Thanks
Tony
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
cellhunter uploading traces (78.47.116.33)
is 78.47.116.33 not alive any more? When I try to upload n offline log I don't get any access any more! Thanks Tony ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: 1024#
Mikhail, This should all be on one line: print '[%s] Signal : cid=%s, lac=%s' % (datetime.datetime.now(),status['cid'],status['lac'] ) Eric Mikhail Umorin wrote: On Wednesday 07 October 2009 04:36:01 Thomas HOCEDEZ wrote: David Garabana Barro a écrit : On Wednesday 07 October 2009 10:57:02 Christ van Willegen wrote: Hi, On Wed, Oct 7, 2009 at 10:50 AM, Ivan Shirokov ivanshirok...@gmail.com wrote: I've been wondering if all the freerunners are affected by bug #1024? No, not all FR are affected, AFAIK I've been wondering the same thing... It would seem that the extra current draw in suspend would affect all FRs, so having a #1024 fix-party would be a good idea in any case (?). #1024 is not causing extra current drain, but the software solution to this bug: Not allowing Calypso entering deep sleep mode. You can check if your FR is suffering from #1024 editting /etc/frameworkd.conf and changing ti_calypso_deep_sleep = never to ti_calypso_deep_sleep = always then restarting framework: /etc/init.d/frameworkd restart After doing so, if your FR suffers from this bug, your modem will continuously register/unregister from GSM network when suspended, and you will lose calls On my case, it was nearly impossible to call FR when suspended + calypso deep sleep. But not all FR suffer from this bug. You should try it after fixing it. Most of GTA02-A5/A6 have this bug. Once TI_CALYPSO_DEEP_SLEEP set to always, you can check with a little script done by KaZEr (see bleow) Launch it on screen, and redirect output to a file. If you have something like [2009-09-09 12:36:09.189663] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:36:15.088936] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:38:10.442808] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:38:13.020126] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:40:25.772918] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:40:28.620096] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:41:17.557676] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:41:20.404582] Signal : cid=3BB3, lac=0D48 Then you have the bug (trying to connect to GSM every second!) regards AstHrO Here's KaZeR's script : -- #!/usr/bin/python import dbus import dbus.glib import gobject import datetime def onNetworkStatus(status ): print '[%s] Signal : cid=%s, lac=%s' % (datetime.datetime.now(),status['cid'],status['lac'] ) bus = dbus.SystemBus(); bus.add_signal_receiver( onNetworkStatus, Status, org.freesmartphone.GSM.Network, org.freesmartphone.ogsmd, /org/freesmartphone/GSM/Device ) gobject.threads_init() dbus.glib.init_threads() main_loop = gobject.MainLoop() main_loop.run() -- I am trying to run the script and I get: r...@om-gta02 ~ $ deep-sleep-check.py dsc.log File /usr/bin/deep-sleep-check.py, line 9 print '[%s] Signal : cid=%s, lac=%s' % ^ SyntaxError: invalid syntax I am not familiar with Python, so, can someone help me to fix this? ___ 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
Re: cellhunter uploading traces (78.47.116.33)
The new address is: http://ch.omoco.de/cellhunter/In order to make cellhunter work again you should upgrade to version 0.5.0___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: cellhunter uploading traces (78.47.116.33)
On Wed, 7 Oct 2009 20:34:54 +0200 (MEST) Lars Hennig n...@el-hennig.de (LH) wrote: MessageThe new address is: http://ch.omoco.de/cellhunter/ In order to make cellhunter work again you should upgrade to version 0.5.0 but this will not convert already existing log file. you must run this before: sed -i -e 's/78.47.116.33\/~hole/ch.omoco.de/' cellhunter_offline.log Petr ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: 1024#
On Wednesday 07 October 2009 13:23:48 Eric Olson wrote: Mikhail, This should all be on one line: print '[%s] Signal : cid=%s, lac=%s' % (datetime.datetime.now(),status['cid'],status['lac'] ) Eric Thanks, that worked. I even warmed up the phone with a heating pad and ran the script for a couple of minutes (with deep sleep = always, of course) -- and no lines in the log file! I got A6, so, I guess, I am lucky! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GSM roaming question
On Wed, Sep 30, 2009 at 12:48:14AM +0100, Al Johnson wrote: Automatic mode means the gsm firmware is in control of which network it registers to. This should be the home network if available, or any other allowed network if not. There is an AT command to list the order of preference for picking other networks, but I don't remember what it is, or whether it is provided by the SIM. It's not something you should normally need to touch though. it's the preferred operator list, stored on the SIM, and typically you can even edit that file on the sim card (i.e. the filesystem permissions of the SIM's internal FS permit modifications). Motorola EZX phones or very old siemens S2/S3/S6/S10 have the feature to add/remove entries to the preferred operator list. I agree, in normal operation you should never have to care about these. -- - Harald Welte lafo...@gnumonks.org http://laforge.gnumonks.org/ Privacy in residential applications is a desirable marketing option. (ETSI EN 300 175-7 Ch. A6) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v14
Hi! I really like QtMoko and V14 is an improvement! Every time a new version arrives I provide the Freerunner Community in the Netherlands with an alternative download on http://www.openmobile.nl/ openmobile.nl (this site is in Dutch). I also changes some basic things to the standard QtMoko version: * I create an sdCard installer (Android alike, by flashing qi, rootfs, kernel) * I add some packages (pkg-fso-keyring vim ntpdate nfs-common mtd-utils flite) * I add a working version of Navit (under QX), with speech (flite) with an working map (Benelux) on the sdCard under the MapsNavit folder * I change the defaults of the fstab (swap on 2nd partition of sdCard), nfs-mount to host (192.168.1.200) /media/jffs2 Maybe this is handy for the rest of the community too? Take a look at the latest (V14) installer-image: http://www.openmobile.nl/pages/downloads.php#qtm14 QtMoko V14 Installer Image and let me know if this is something you all like or if there need to be some changes. -- View this message in context: http://n2.nabble.com/QtMoko-v14-tp3781291p3784396.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: HOWTO: Sharing SHR-U GPRS to *buntu laptop
2009/9/26 Michael Lauer mic...@vanille-media.de: Alternatively, use org.freesmartphone.Network.StartConnectionSharingWithInterface usb0 and find a dhcp server running on the FR with everything else preconfigured. I'm having a couple of problems with this: $ mdbus -s org.freesmartphone.Network.StartConnectionSharingWithInterface usb0 Service name not found and how would you turn it off again? Regards Jeff ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Broken Freerunner.. CPU stall messages.. repairable?
I still think that its somehow connected with kernel, at least: [21474549.35] INFO: RCU detected CPU 0 stall (t=4294909870/2000 jiffies) [21474549.35] [c002dcac] (dump_stack+0x0/0x14) from [c0073ec8] (__rcu_pending+0x80/0x21c) [21474549.35] [c0073e48] (__rcu_pending+0x0/0x21c) from [c007407c] (rcu_pending+0x18/0x50) [21474549.35] r7:001e r6:c781c020 r5: r4: [21474549.35] [c0074064] (rcu_pending+0x0/0x50) from [c004e0e4] (update_process_times+0x40/0x64) [21474549.35] [c004e0a4] (update_process_times+0x0/0x64) from [c002d378] (timer_tick+0xec/0x114) [21474549.35] r6: r5: r4:c0370eb4 [21474549.35] [c002d28c] (timer_tick+0x0/0x114) from [c0039338] (s3c2410_timer_interrupt+0x10/0x18) [21474549.35] r5: r4:c036e374 [21474549.35] [c0039328] (s3c2410_timer_interrupt+0x0/0x18) from [c0071728] (handle_IRQ_event+0x2c/0x68) [21474549.35] [c00716fc] (handle_IRQ_event+0x0/0x68) from [c0073244] (handle_edge_irq+0x124/0x174) [21474549.35] r7:c03720d4 r6:c036e374 r5:001e r4:c03720a0 [21474549.35] [c0073120] (handle_edge_irq+0x0/0x174) from [c0029054] (__exception_text_start+0x54/0x6c) [21474549.35] r7:0002 r6:4000 r5: r4:001e [21474549.35] [c0029000] (__exception_text_start+0x0/0x6c) from [c00299d8] (__irq_svc+0x38/0xc8) [21474549.35] Exception stack(0xc781fa90 to 0xc781fad8) [21474549.35] fa80: c910 c7a6a794 01bc 9d378a3c [21474549.35] faa0: c2cdce47 c7a6ae94 c79a6ec0 0008 c797d000 c7937000 0003 c781fafc [21474549.35] fac0: 3e4b3a6e c781fad8 a27f9276 c0149efc 2013 [21474549.35] r5:f400 r4: [21474549.35] [c01b7920] (s3c2440_nand_read_buf+0x0/0x64) from [c01b1460] (nand_read_page_raw+0x24/0x40) [21474549.35] r6:a696 r5:c797d000 r4:c797d0d0 [21474549.35] [c01b143c] (nand_read_page_raw+0x0/0x40) from [c01b14bc] (nand_read_page_swecc+0x40/0x120) [21474549.35] r5:c797d0d0 r4:0800 [21474549.35] [c01b147c] (nand_read_page_swecc+0x0/0x120) from [c01b4560] (nand_do_read_ops+0x20c/0x410) [21474549.35] [c01b4354] (nand_do_read_ops+0x0/0x410) from [c01b4b08] (nand_read+0x94/0xb8) [21474549.35] [c01b4a74] (nand_read+0x0/0xb8) from [c01a4b98] (part_read+0xa0/0xd4) [21474549.35] [c01a4af8] (part_read+0x0/0xd4) from [c0120e34] (jffs2_flash_read+0x84/0x248) [21474549.35] r7: r6:049e096c r5:049e00e0 r4:c781fc8c [21474549.35] [c0120db0] (jffs2_flash_read+0x0/0x248) from [c011a65c] (jffs2_fill_scan_buf+0x2c/0x4c) [21474549.35] [c011a630] (jffs2_fill_scan_buf+0x0/0x4c) from [c011ac30] (jffs2_scan_medium+0x5b4/0x1568) [21474549.35] r4:0ae5 [21474549.35] [c011a67c] (jffs2_scan_medium+0x0/0x1568) from [c011dc04] (jffs2_do_mount_fs+0x18c/0x584) [21474549.35] [c011da78] (jffs2_do_mount_fs+0x0/0x584) from [c011ff34] (jffs2_do_fill_super+0x134/0x21c) [21474549.35] [c011fe00] (jffs2_do_fill_super+0x0/0x21c) from [c0120618] (jffs2_fill_super+0xc8/0x104) [21474549.35] r7: r6:0001 r5:c7a01800 r4:c7a01400 [21474549.35] [c0120550] (jffs2_fill_super+0x0/0x104) from [c01a3ec8] (get_sb_mtd_aux+0x60/0xc4) [21474549.35] r7: r6:8000 r5:c7a01800 r4:c7a01800 [21474549.35] [c01a3e68] (get_sb_mtd_aux+0x0/0xc4) from [c01a3f8c] (get_sb_mtd_nr+0x60/0x70) [21474549.35] [c01a3f2c] (get_sb_mtd_nr+0x0/0x70) from [c01a40cc] (get_sb_mtd+0x130/0x18c) [21474549.35] r7:8000 r6:c0375d28 r5:c79e7000 r4:01f6 [21474549.35] [c01a3f9c] (get_sb_mtd+0x0/0x18c) from [c0120320] (jffs2_get_sb+0x24/0x30) [21474549.35] [c01202fc] (jffs2_get_sb+0x0/0x30) from [c00a0aa4] (vfs_kern_mount+0x58/0xac) [21474549.35] [c00a0a4c] (vfs_kern_mount+0x0/0xac) from [c00a0b58] (do_kern_mount+0x40/0xdc) [21474549.35] r8:c0375d28 r7:c79f3000 r6: r5:c79e7000 r4:8000 [21474549.35] [c00a0b18] (do_kern_mount+0x0/0xdc) from [c00b5970] (do_mount+0x65c/0x6cc) [21474549.35] r8:c79f3000 r7:c79e6000 r6:c79e7000 r5: r4: [21474549.35] [c00b5314] (do_mount+0x0/0x6cc) from [c00b5a70] (sys_mount+0x90/0xdc) [21474549.35] [c00b59e0] (sys_mount+0x0/0xdc) from [c0008ddc] (mount_block_root+0xf8/0x2ac) [21474549.35] r7:c7938000 r6: r5:c7938006 r4:c7938000 [21474549.35] [c0008ce4] (mount_block_root+0x0/0x2ac) from [c0008fe4] (mount_root+0x54/0x6c) [21474549.35] [c0008f90] (mount_root+0x0/0x6c) from [c0009178] (prepare_namespace+0x17c/0x1e0) [21474549.35] r5:c002683c r4:c0390f64 [21474549.35] [c0008ffc] (prepare_namespace+0x0/0x1e0) from [c000877c] (kernel_init+0xb0/0xd8) [21474549.35] r5:c0025274 r4:c0390f58 [21474549.35] [c00086cc] (kernel_init+0x0/0xd8) from [c0046dfc] (do_exit+0x0/0x6b0) [21474549.35] r5: r4: doesn't looks good ___ Openmoko community mailing list community@lists.openmoko.org
Re: 1024#
On Wed, 2009-10-07 at 11:36 +0200, Thomas HOCEDEZ wrote: David Garabana Barro a écrit : On Wednesday 07 October 2009 10:57:02 Christ van Willegen wrote: Hi, On Wed, Oct 7, 2009 at 10:50 AM, Ivan Shirokov ivanshirok...@gmail.com wrote: I've been wondering if all the freerunners are affected by bug #1024? No, not all FR are affected, AFAIK I've been wondering the same thing... It would seem that the extra current draw in suspend would affect all FRs, so having a #1024 fix-party would be a good idea in any case (?). #1024 is not causing extra current drain, but the software solution to this bug: Not allowing Calypso entering deep sleep mode. You can check if your FR is suffering from #1024 editting /etc/frameworkd.conf and changing ti_calypso_deep_sleep = never to ti_calypso_deep_sleep = always then restarting framework: /etc/init.d/frameworkd restart After doing so, if your FR suffers from this bug, your modem will continuously register/unregister from GSM network when suspended, and you will lose calls ... On my A5 I find never gives noticeably poorer battery life, and often wakes from suspend at random times. The phone also seems a lot less rteliable with reboots need to get a working system again. BillK more crashes than normal (things not working/stop working) and o ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB networking with Ubuntu 9.04
Hi Tony, thanks for giving a try to the script. I'm glad it helped you. I
just create a sub-section on the wiki page [1] where I put the script to
help others to get connected easily.
Cheers
[1] http://wiki.openmoko.org/wiki/USB_Networking#Connection_Script
/***
* Don't Worry...Be Linux
* Cristian Gómez Alvarez
* Ingeniero en Sistemas y Computación
* Universidad de Caldas
* Comunidad de Software Libre Manizales
* IEEE/WIE Student Member
* Linux User #463617
* Mi Blog: http://cristianpark.sehablalinux.com/
/
2009/10/7 Tony Berth tonybe...@googlemail.com
On Wed, Oct 7, 2009 at 10:27 AM, Matthias Huber
matthias.hu...@wollishausen.de wrote:
Tony Berth schrieb:
Bingo. Thanks A LOT!
Is it possible to update the Wiki with that one. I think this will be a
great help to the whole community
if you would tell me wich of / or both tricks did it on your system ?
but i had to add this two lines to my /etc/ufw/ufw.conf
ufw allow from 192.168.0.202
ufw allow to 192.168.0.202
another trial with iptables needs to load some modules too:
#!/bin/sh
MOKO=192.168.0.202
echo 1 /proc/sys/net/ipv4/ip_forward
modprobe ipt_MASQUERADE
iptables -I FORWARD -j ACCEPT -d ${MOKO}/32
iptables -I FORWARD -j ACCEPT -s ${MOKO}/32
iptables -I POSTROUTING -t nat -j MASQUERADE -s ${MOKO}/32
what works was the script Cristian Gomez included in his reply!
Just for the records, the first time I run that script it does assign the
192.168.0.200 IP to eth1 but can't ping/access 192.168.0.202! Then:
- I disconnect Openmoko
- connect it again
- re-run the script and voila the connection is there!
Thanks
Tony
___
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
Re: 1024#
On Thu, Oct 8, 2009 at 2:02 AM, W.Kenworthy bi...@iinet.net.au wrote: more crashes than normal (things not working/stop working) and o Apparently your phone crashed right in the middle if this reply! :-) Christ van Willegen -- 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
