Re: [FSO] Wifi in M5 no longer functioning
On Thu, Feb 5, 2009 at 11:10 AM, arne anka wrote: > > What about eth0? > > inet6 addr: fe80::212:cfff:fe8f:3391/64 > > same thing basically, though probably not assigned by avahi but something > random (do you use ipv6 at home? does the fr kernel support ipv6 at all?) > > I just checked. I'm running dd-wrt v24 rc5 which doesn't seem to have working IPv6.[1] [1]http://www.dd-wrt.com/wiki/index.php/IPv6 ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Wifi in M5 no longer functioning
On Thu, Feb 5, 2009 at 5:56 AM, Al Johnson wrote: > 'SetResourcePolicy WiFi enabled' tells FSO to power up the WiFi irrespective > of whether any apps have issued 'RequestResource WiFi'. Before I do this I > have no eth0 available. Yeah, but it seems to also configure eth0 because after I SetResourcePolicy, If I do ifup eth0 right away I get "ifup: interface eth0 already configured" To get dhcp working I would often have to do: > > ifup eth0 > ifdown eth0 > ifup eth0 > I know what you're talking about, I definitely had to do this with past images as well. However, with M5, there's still no luck with the second ifup eth0. > > On the second ifup the association often completes a little quicker so dhcp > has a chance of completing before timeout. Another method is to manually > start > dhcp after the first ifup using something like: > > udhcpc -i eth0 > > Yeah, this suffers the same fate is ifup, ifdown, ifup. It's good to know if I revert to an older image. > This assumes wpa_supplicant is making the association fine. You can check > that > with wpa_cli which accepts a 'help' command to tell you what other options > it > has. > > This has worked for me on everything I've tried since 2007.2, but I've not > tried it on the recent SHR or MS5 yet. SHR, and probably MS5, have the > added > complication of connman running. This tries to manage the network > connections, > but at least for usb0 it is overridden by the ifup and ifdown commands. > Assuming connman actually works, the other option would be to use the > connman > dbus interface to set the network parameters. Don't ask me how though ;-) > > I'll poke at this when I have more time after the weekend. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Wifi in M5 no longer functioning
On Thu, Feb 5, 2009 at 4:26 AM, arne anka wrote: > > eth0:avah Link encap:Ethernet HWaddr 00:12:CF:8F:33:91 > > inet addr:169.254.6.255 Bcast:169.254.255.255 > > > It seems to look like it's connected > > nope. it's not. > the ip address shown is a generic one, assigned by avahi in absence of a > real one. > What about eth0? inet6 addr: fe80::212:cfff:fe8f:3391/64 > i don't know, what you did to obtain an association with tha ap and an ip > subsequnetly, but iwlist scan is not giong to o that. > I didn't do anything, it was all the framework : ) Dylan ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Wifi in M5 no longer functioning
On Thu, Feb 5, 2009 at 3:09 AM, Andy Green wrote: > Somebody in the thread at some point said: > | It seems to look like it's connected, but I still can't ping google, the > | AP, or access the internet. > > usb0 is up too. I use usb to ssh into the phone. > > But, the missing info is your routing table > > route -n > r...@om-gta02:~# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 192.168.0.0 0.0.0.0 255.255.255.0 U 0 00 usb0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 00 eth0 0.0.0.0 192.168.0.200 0.0.0.0 UG0 00 usb0 > > Will the PC you are connected to act as gateway on the USB Ethernet > connection? Or is the only way out to the Internet through WLAN? I haven't done anything to setup access to the internet via usb (just ssh) so I imagine right now there's only WLAN. Unless GPRS gets configured automatically in M5. > > Can you ping even if you don't try to use DNS? No. No luck with 192.168.1.1 > > What network range does the AP subnet use... 192.168.0.x again? > 192.168.1.x So I'm unclear whether you're supposed to ifup eth0 after SetResourcePolicy WiFi enabled. When I try right away it says r...@om-gta02:~# ifup eth0 ifup: interface eth0 already configured r...@om-gta02:~# ifdown eth0 cat: can't open '/var/run/udhcpc.eth0.pid': No such file or directory ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Wifi in M5 no longer functioning
On Wed, Feb 4, 2009 at 7:47 AM, Al Johnson wrote: > I often get the above even with a working wpa_supplicant.conf because the > dhcp > discover starts being sent immediately, not after association, so dhcp > times > out before association is complete. Bringing the interface down then > immediately up again will often get association faster, so the last dhcp > request succeeds. > > Do you mean, after SetResourcePolicy WiFi enabled, you can do ifdown eth0, ifup eth0, and it works? Or do you cycle the SetResourcePolicy WiFi? Neither seems to work for me. Dylan ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Wifi in M5 no longer functioning
On Wed, Feb 4, 2009 at 4:38 AM, Michael 'Mickey' Lauer wrote: > Am Wednesday 04 February 2009 10:08:37 schrieb Dylan Semler: > > > > I don't _think_ it's a configuration issue, as my setup hasn't changed > > since M4 and I'm using the same config files. > > I'm afraid the new kernel broke something then. Can you try an older one to > make sure? > > Using the kernel from M4.1 (2.6.24+r10 from Nov 18th), I can access the internet with SetResourcePolicy WiFi enabled and then ifup eth0. The next kernel image available in the testing and unstable repositories is 2.5.28-oe1 from Jan 12th. This kernel exhibits the same problems as the M5 kernel. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Wifi in M5 no longer functioning
On Wed, Feb 4, 2009 at 4:51 AM, Andy Green wrote: > > What's dmesg have to say about all this excitement? > After SetResourcePolicy Wifi enable I get the following new lines in dmesg: [21474827.275000] s3c2440-sdi s3c2440-sdi: host detect has no irq available [21474827.275000] mapped channel 0 to 0 [21474827.295000] s3c2440-sdi s3c2440-sdi: powered down. [21474827.295000] s3c2440-sdi s3c2440-sdi: initialisation done. [21474827.51] s3c2440-sdi s3c2440-sdi: running at 0kHz (requested: 0kHz). [21474827.51] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested: 195kHz). [21474827.51] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested: 195kHz). [21474827.52] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested: 195kHz). [21474827.52] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested: 195kHz). [21474827.545000] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested: 195kHz). [21474827.56] mmc0: queuing CIS tuple 0x01 length 3 [21474827.58] mmc0: queuing CIS tuple 0x1a length 5 [21474827.595000] mmc0: queuing CIS tuple 0x1b length 8 [21474827.595000] s3c2440-sdi s3c2440-sdi: running at 25000kHz (requested: 25000kHz). [21474827.595000] s3c2440-sdi s3c2440-sdi: running at 25000kHz (requested: 25000kHz). [21474827.605000] mmc0: queuing CIS tuple 0x80 length 1 [21474827.605000] mmc0: queuing CIS tuple 0x81 length 1 [21474827.605000] mmc0: queuing CIS tuple 0x82 length 1 [21474827.605000] mmc0: new SDIO card at address 0001 [21474828.65] BMI Get Target Info: Exit (ver: 0x2059 type: 0x1) [21474828.725000] AR6000 Reg Code = 0x4060 [21474833.405000] ar6000_ioctl_giwscan(): data length 0 [21474836.36] AR6000 Reg Code = 0x8348 [4.585000] eth0: no IPv6 routers present [4.89] channel hint set to 2437 [4.905000] AR6000 disconnected [4.965000] AR6000 connected event on freq 2437 with bssid listenInterval=100, beaconInterval = 100, beaconIeLen = 22 assocReqLen=59 assocRespLen =59 [4.965000] Network: Infrastructure > # iwconfig r...@om-gta02:~# iwconfig lono wireless extensions. usb0 no wireless extensions. pan0 no wireless extensions. eth0 AR6000 802.11g ESSID: Mode:Managed Frequency:2.437 GHz Access Point: Bit Rate=65.535 Mb/s Tx-Power=0 dBm Sensitivity=0/3 Retry:on Encryption key:off Power Management:off Link Quality:0/94 Signal level:-95 dBm Noise level:-96 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > # iwlist eth0 scan > r...@om-gta02:~# iwlist eth0 scan eth0 Scan completed : Cell 01 - Address: ESSID: Mode:Master Frequency:2.437 GHz (Channel 0) Quality=42/94 Signal level=-53 dBm Noise level=-95 dBm Encryption key:on Extra:bcn_int=100 Extra:rsn_ie=3014010fac02010fac02010fac020c00 Extra:wmm_ie=dd180050f202010183a427a442435e0062322f00 > > Since the previous Jan 5th basis I understood the kernel had, there are > relatively few patches. The main change is WLAN driver is now in modules. > > # lsmod > r...@om-gta02:~# lsmod Module Size Used by bnep 12800 2 sco10444 2 snd_soc_neo1973_gta02_wm8753 8552 0 snd_soc_s3c24xx_i2s 3896 1 snd_soc_neo1973_gta02_wm8753 snd_soc_s3c24xx 4424 1 snd_soc_neo1973_gta02_wm8753 snd_soc_wm8753 33384 1 snd_soc_neo1973_gta02_wm8753 snd_soc_core 34360 3 snd_soc_neo1973_gta02_wm8753,snd_soc_s3c24xx,snd_soc_wm8753 snd_pcm76364 2 snd_soc_s3c24xx,snd_soc_core snd_timer 21052 1 snd_pcm snd_page_alloc 6504 1 snd_pcm snd50788 5 snd_soc_neo1973_gta02_wm8753,snd_soc_wm8753,snd_soc_core,snd_pcm,snd_timer rfcomm 37320 4 ipv6 265884 14 hidp 14664 0 l2cap 21456 13 bnep,rfcomm,hidp g_ether39604 0 btusb 11952 0 bluetooth 60408 10 bnep,sco,rfcomm,hidp,l2cap,btusb ohci_hcd 28564 0 s3c2410_wdt 8984 0 > > I guess check eth0 is still assigned to WLAN with > > # ifconfig -a > > r...@om-gta02:~# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:12:CF:8F:33:91 inet6 addr: fe80::212:cfff:fe8f:3391/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:125 errors:0 dropped:0 overruns:0 frame:0 TX packets:40 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:144316 (140.9 KiB) TX bytes:4497 (4.3 KiB) eth0:avah Link encap:Ethernet HWaddr 00:12:CF:8F:33:91 inet addr:169.254.6.255 Bcast:169.254.255.255 Mask:255.255.0.0 UP BROADCAST RUNNING MULTICAS
Re: [FSO] Wifi in M5 no longer functioning
On Wed, Feb 4, 2009 at 1:40 AM, Michael 'Mickey' Lauer wrote: > > That's correct behaviour due to auto-release. Please read the usage > introduction at http://docs.freesmartphone.org/usage-intro.html > > If you can't stay on the bus, use SetResourcePolicy. > > My bad, I hadn't read far enough before to catch the note about mdbus at the bottom. I've set the policy to enabled, but still having troubles r...@om-gta02:~# mdbus -s org.freesmartphone.ousaged /org/freesmartphone/Usage org.freesmartphone.Usage.SetResourcePolicy WiFi enabled r...@om-gta02:~# mdbus -s org.freesmartphone.ousaged /org/freesmartphone/Usage org.freesmartphone.Usage.GetResourceState WiFi True r...@om-gta02:~# ifup eth0 WPA: Configuring Interface ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported udhcpc (v1.13.2) started run-parts: /etc/udhcpc.d/00avahi-autoipd exited with code 1 Sending discover... Sending discover... Sending discover... No lease, failing I don't _think_ it's a configuration issue, as my setup hasn't changed since M4 and I'm using the same config files. Really all I'm wanting to do is enable wifi so I can opkg some packages from the command line, etc. Am I going at this the wrong way? Dylan ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Wifi in M5 no longer functioning
On Tue, Feb 3, 2009 at 8:20 PM, Michael 'Mickey' Lauer wrote: > Am Wednesday 04 February 2009 02:55:25 schrieb Dylan Semler: > > It seems that my prior FSO wifi configuration no longer works with M5. > > Did you request WiFi with the Usage API? > > I guess I did not. Now I run r...@om-gta02:~# mdbus -s org.freesmartphone.ousaged /org/freesmartphone/Usage org.freesmartphone.Usage.RequestResource WiFi r...@om-gta02:~# mdbus -s org.freesmartphone.ousaged /org/freesmartphone/Usage org.freesmartphone.Usage.GetResourceState WiFi False r...@om-gta02:~# After RequestResource WiFi, the freerunner shows up on my router's list of connected wifi devices. Does RequestResource not only turn on the radio, but also try to connect (and thus, ifup eth0 would not be necessary)? If it does it must be failing in my case. Dylan ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
[FSO] Wifi in M5 no longer functioning
It seems that my prior FSO wifi configuration no longer works with M5.
r...@om-gta02:~# ifup eth0
WPA: Configuring Interface
ioctl[SIOCGIFFLAGS]: No such device
Could not get interface 'eth0' flags
ioctl[SIOCSIWPMKSA]: No such device
ioctl[SIOCSIWMODE]: No such device
Could not configure driver to use managed mode
ioctl[SIOCGIWRANGE]: No such device
ioctl[SIOCGIFINDEX]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 7 value 0x0 - Failed to disable WPA in the driver.
ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 5 value 0x0 - ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAP]: No such device
ioctl[SIOCGIFFLAGS]: No such device
wpa_supplicant: /usr/sbin/wpa_supplicant daemon failed to start
FAILED
ifconfig: SIOCGIFFLAGS: No such device
eth0 No such device
ifconfig: SIOCGIFFLAGS: No such device
I'm using WPA2 configured as follows:
# cat /etc/wpa_supplicant/cat wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
# WPA2:
network={
ssid=
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=TKIP CCMP
psk=
priority=50
}
And I've added the line: "wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf"
beneith the line "iface eth0 inet dhcp" in /etc/network/interfaces.
This configuration has worked for all other distributions thus far. Is
something different this time around?
Dylan
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] GPRS not functioning in M3
On Thu, Sep 18, 2008 at 5:40 AM, Michael 'Mickey' Lauer <[EMAIL PROTECTED] > wrote: > Am Thursday 18 September 2008 03:05:01 schrieb Dylan Semler: > > Has anyone else had their GPRS stop working since flashing FSO M3. It > was > > working for me in M2. I've filed a bug about it[1] but no action so far. > > > > [1] http://trac.freesmartphone.org/ticket/140 > > I see this line here: > > ogsmd.pdp INFO configuring ppp for user 'x' w/ password 'x' > > I doubt that's correct for T-Mobile. Please try again with "" for user and > password. MS2 did not care for user and password settings, MS3 does care :) > > I updated the mdbus command to: mdbus -s $BUSNAME $OBJECTPATH $METHODNAME $APN "" "" but I appear to have the same result. -- Dylan Type faster. Use Dvorak: http://dvzine.org ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
[FSO] GPRS not functioning in M3
Has anyone else had their GPRS stop working since flashing FSO M3. It was working for me in M2. I've filed a bug about it[1] but no action so far. [1] http://trac.freesmartphone.org/ticket/140 -- Dylan Type faster. Use Dvorak: http://dvzine.org ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: FSO and GPRS; still no dice
I sent this response just to Mickey on accident; resending to the whole list: On Thu, Aug 21, 2008 at 6:53 AM, Michael 'Mickey' Lauer <[EMAIL PROTECTED] > wrote: > Am Donnerstag 21 August 2008 06:59:08 schrieb Dylan Semler: > > OK, looks like I had improperly flashed the kernel the first time. I > > reflashed it and now all of the log and dmesg errors go away. However > I'm > > still getting the same dbus signals and cannot connect via GPRS. > > Please post the output of 'logread -f' while attempting a connection. > Aug 22 16:59:11 om-gta02 local0.info /usr/sbin/gsm0710muxd[1407]: gsm0710muxd.c:693:c_alloc_channel(): Connecting /dev/pts/5 to virtual channel 4 for ogsmd.gprs on /dev/ttySAC0 Aug 22 16:59:11 om-gta02 daemon.notice pppd[2871]: pppd 2.4.3 started by root, uid 0 Aug 22 16:59:12 om-gta02 local2.info chat[2875]: abort on (BUSY) Aug 22 16:59:12 om-gta02 local2.info chat[2875]: abort on (DELAYED) Aug 22 16:59:12 om-gta02 local2.info chat[2875]: abort on (ERROR) Aug 22 16:59:12 om-gta02 local2.info chat[2875]: abort on (NO ANSWER) Aug 22 16:59:12 om-gta02 local2.info chat[2875]: abort on (NO CARRIER) Aug 22 16:59:12 om-gta02 local2.info chat[2875]: abort on (NO DIALTONE) Aug 22 16:59:12 om-gta02 local2.info chat[2875]: abort on (RINGING) Aug 22 16:59:12 om-gta02 local2.info chat[2875]: abort on (VOICE) Aug 22 16:59:12 om-gta02 local2.info chat[2875]: timeout set to 3 seconds Aug 22 16:59:12 om-gta02 local2.info chat[2875]: send (ATZ^M) Aug 22 16:59:12 om-gta02 local0.warn /usr/sbin/gsm0710muxd[1407]: gsm0710muxd.c:569:pseudo_device_read(): Write to a channel which wasn't acked to be open. Aug 22 16:59:12 om-gta02 local0.info /usr/sbin/gsm0710muxd[1407]: gsm0710muxd.c:1410:extract_frames(): Logical channel 4 opened Aug 22 16:59:12 om-gta02 local2.info chat[2875]: expect (OK) Aug 22 16:59:12 om-gta02 local2.info chat[2875]: ^M Aug 22 16:59:12 om-gta02 local2.info chat[2875]: OK Aug 22 16:59:12 om-gta02 local2.info chat[2875]: -- got it Aug 22 16:59:12 om-gta02 local2.info chat[2875]: send (ATE0^M) Aug 22 16:59:12 om-gta02 local2.info chat[2875]: expect (OK) Aug 22 16:59:12 om-gta02 local2.info chat[2875]: ^M Aug 22 16:59:12 om-gta02 local2.info chat[2875]: ^M Aug 22 16:59:12 om-gta02 local2.info chat[2875]: OK Aug 22 16:59:12 om-gta02 local2.info chat[2875]: -- got it Aug 22 16:59:12 om-gta02 local2.info chat[2875]: send (AT+CMEE=2^M) Aug 22 16:59:12 om-gta02 local2.info chat[2875]: expect (OK) Aug 22 16:59:12 om-gta02 local2.info chat[2875]: ^M Aug 22 16:59:12 om-gta02 local2.info chat[2875]: ^M Aug 22 16:59:12 om-gta02 local2.info chat[2875]: OK Aug 22 16:59:12 om-gta02 local2.info chat[2875]: -- got it Aug 22 16:59:12 om-gta02 local2.info chat[2875]: send (AT+CPIN?^M) Aug 22 16:59:12 om-gta02 local2.info chat[2875]: expect (READY) Aug 22 16:59:12 om-gta02 local2.info chat[2875]: ^M Aug 22 16:59:12 om-gta02 local2.info chat[2875]: ^M Aug 22 16:59:12 om-gta02 local2.info chat[2875]: +CPIN: READY Aug 22 16:59:12 om-gta02 local2.info chat[2875]: -- got it Aug 22 16:59:12 om-gta02 local2.info chat[2875]: send () Aug 22 16:59:12 om-gta02 local2.info chat[2875]: expect (OK) Aug 22 16:59:12 om-gta02 local2.info chat[2875]: ^M Aug 22 16:59:12 om-gta02 local2.info chat[2875]: ^M Aug 22 16:59:12 om-gta02 local2.info chat[2875]: OK Aug 22 16:59:12 om-gta02 local2.info chat[2875]: -- got it Aug 22 16:59:12 om-gta02 local2.info chat[2875]: send (AT+CGDCONT=1,"IP"," wap.voicestream.com"^M) Aug 22 16:59:13 om-gta02 local2.info chat[2875]: timeout set to 180 seconds Aug 22 16:59:13 om-gta02 local2.info chat[2875]: expect (OK) Aug 22 16:59:13 om-gta02 local2.info chat[2875]: ^M Aug 22 16:59:13 om-gta02 local2.info chat[2875]: ^M Aug 22 16:59:13 om-gta02 local2.info chat[2875]: OK Aug 22 16:59:13 om-gta02 local2.info chat[2875]: -- got it Aug 22 16:59:13 om-gta02 local2.info chat[2875]: send (ATD*99#^M) Aug 22 16:59:13 om-gta02 local2.info chat[2875]: expect (CONNECT) Aug 22 16:59:13 om-gta02 local2.info chat[2875]: ^M Aug 22 16:59:13 om-gta02 local2.info chat[2875]: ^M Aug 22 16:59:13 om-gta02 local2.info chat[2875]: CONNECT Aug 22 16:59:13 om-gta02 local2.info chat[2875]: -- got it Aug 22 16:59:13 om-gta02 local2.info chat[2875]: send (\d) Aug 22 16:59:14 om-gta02 daemon.info pppd[2871]: Serial connection established. Aug 22 16:59:14 om-gta02 daemon.debug pppd[2871]: using channel 2 Aug 22 16:59:14 om-gta02 daemon.info pppd[2871]: Using interface ppp0 Aug 22 16:59:14 om-gta02 daemon.notice pppd[2871]: Connect: ppp0 <--> /dev/pts/5 Aug 22 16:59:15 om-gta02 daemon.warn pppd[2871]: Warning - secret file /etc/ppp/pap-secrets has world and/or group access Aug 22 16:59:15 om-gta02 daemon.debug pppd[2871]: sent [LCP ConfReq id=0x1 ] Aug 22 16:59:15 om-gta02 daemon.debug pppd[2871]: rcvd [LCP ConfRej id=0x1 ] Aug 22 16:59:15 om-gta02 daemon.debug pppd[2871]: sent [LCP ConfReq id=0x2 ] Aug 22 16:59:15 om-gta02 d
Re: FSO and GPRS; still no dice
On Wed, Aug 20, 2008 at 11:37 PM, Dylan Semler <[EMAIL PROTECTED]>wrote: > On Wed, Aug 20, 2008 at 11:23 PM, Timo Juhani Lindfors < > [EMAIL PROTECTED]> wrote: > >> Hi, >> >> "Dylan Semler" <[EMAIL PROTECTED]> writes: >> > Aug 22 08:08:14 om-gta02 daemon.notice modprobe: FATAL: Error inserting >> > ppp_generic (/lib/modules/2.6.24/kernel/drivers/net/ppp_generic.ko): >> Unknown >> > symbol in module, or unknown parameter (see dmesg) >> >> Which kernel are you using? Are you sure the modules are compiled for >> that particular kernel? > > > I'm using the kernel that is made available by the FSO buildhost: > > http://shr.bearstech.com/fso-testing/images/neo1973/uImage-om-gta92-latest.bin > > > >> What does plain "modprobe ppp_generic" print >> to stdout and dmesg? >> >> > modprobe ppp_generic produces the same message to stdout: > FATAL: Error inserting ppp_generic > (/lib/modules/2.6.24/kernel/drivers/net/ppp_generic.ko): Unknown symbol in > module, or unknown parameter (see dmesg) > > dmesg reports: > ppp_generic: Unknown symbol mutex_lock > > OK, looks like I had improperly flashed the kernel the first time. I reflashed it and now all of the log and dmesg errors go away. However I'm still getting the same dbus signals and cannot connect via GPRS. -- Dylan Type faster. Use Dvorak: http://dvzine.org ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: FSO and GPRS; still no dice
On Wed, Aug 20, 2008 at 11:23 PM, Timo Juhani Lindfors <[EMAIL PROTECTED] > wrote: > Hi, > > "Dylan Semler" <[EMAIL PROTECTED]> writes: > > Aug 22 08:08:14 om-gta02 daemon.notice modprobe: FATAL: Error inserting > > ppp_generic (/lib/modules/2.6.24/kernel/drivers/net/ppp_generic.ko): > Unknown > > symbol in module, or unknown parameter (see dmesg) > > Which kernel are you using? Are you sure the modules are compiled for > that particular kernel? I'm using the kernel that is made available by the FSO buildhost: http://shr.bearstech.com/fso-testing/images/neo1973/uImage-om-gta92-latest.bin > What does plain "modprobe ppp_generic" print > to stdout and dmesg? > > modprobe ppp_generic produces the same message to stdout: FATAL: Error inserting ppp_generic (/lib/modules/2.6.24/kernel/drivers/net/ppp_generic.ko): Unknown symbol in module, or unknown parameter (see dmesg) dmesg reports: ppp_generic: Unknown symbol mutex_lock -- Dylan Type faster. Use Dvorak: http://dvzine.org ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
FSO and GPRS; still no dice
There have been some posts on the community list about people having success
with FSO and GPRS using scripts from the wiki[1]. I seem to be having less
luck. I'm running a fresh install of FSO from today's build (20080820).
I run the following dbus command to try to activate GPRS:
# mdbus -s org.freesmartphone.frameworkd /org/freesmartphone/GSM/Device
org.freesmartphone.GSM.PDP.ActivateContext wap.voicestream.com x x
Using mdbus -s -l I observe the following GSM signals (among other noise):
[SIGNAL]org.freesmartphone.GSM.PDP.ContextStatusfrom :1.3
/org/freesmartphone/GSM/Device
(dbus.Int32(1), dbus.String(u'outgoing'), dbus.Dictionary({},
signature=dbus.Signature('sv')))
--
[SIGNAL]org.freesmartphone.GSM.PDP.ContextStatusfrom :1.3
/org/freesmartphone/GSM/Device
(dbus.Int32(1), dbus.String(u'release'), dbus.Dictionary({},
signature=dbus.Signature('sv')))
At the same time logread -f reports some serious problems with pppd:
Aug 22 08:08:14 om-gta02 local0.info /usr/sbin/gsm0710muxd[1425]:
gsm0710muxd.c:693:c_alloc_channel(): Connecting /dev/pts/15 to virtual
channel 12 for ogsmd.gprs on /dev/ttySAC0
Aug 22 08:08:14 om-gta02 local0.info /usr/sbin/gsm0710muxd[1425]:
gsm0710muxd.c:1410:extract_frames(): Logical channel 12 opened
Aug 22 08:08:14 om-gta02 user.warn kernel: [ 5910.195000] ppp_generic:
Unknown symbol mutex_lock
Aug 22 08:08:14 om-gta02 daemon.notice modprobe: FATAL: Error inserting
ppp_generic (/lib/modules/2.6.24/kernel/drivers/net/ppp_generic.ko): Unknown
symbol in module, or unknown parameter (see dmesg)
Aug 22 08:08:15 om-gta02 daemon.err pppd[2069]: This system lacks kernel
support for PPP. This could be because the PPP kernel module could not be
loaded, or because PPP was not included in the kernel configuration. If PPP
was included as a module, try `/sbin/modprobe
Aug 22 08:08:15 om-gta02 daemon.info avahi-daemon[1340]: Interface usb0.IPv4
no longer relevant for mDNS.
Aug 22 08:08:15 om-gta02 daemon.info avahi-daemon[1340]: Leaving mDNS
multicast group on interface usb0.IPv4 with address 192.168.0.202.
Aug 22 08:08:15 om-gta02 daemon.info avahi-daemon[1340]: Withdrawing address
record for 192.168.0.202 on usb0.
Aug 22 08:08:16 om-gta02 daemon.info avahi-daemon[1340]: Joining mDNS
multicast group on interface usb0.IPv4 with address 192.168.0.202.
Aug 22 08:08:16 om-gta02 daemon.info avahi-daemon[1340]: New relevant
interface usb0.IPv4 for mDNS.
Aug 22 08:08:16 om-gta02 daemon.info avahi-daemon[1340]: Registering new
address record for 192.168.0.202 on usb0.IPv4.
Aug 22 08:08:16 om-gta02 user.notice root: Checking for WLAN association...
Aug 22 08:08:16 om-gta02 user.notice root: Found association!
If pppd is truely the culprit, it's puzzling why GPRS is working on others'
freerunners and not mine.
[1]http://wiki.openmoko.org/wiki/GPRS_FSO
--
Dylan
Type faster. Use Dvorak:
http://dvzine.org
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
Re: Remove GTK themeing from ASU
On Wed, Aug 20, 2008 at 12:27 AM, Russell Sears <[EMAIL PROTECTED]>wrote: > Dylan Semler wrote: > > FSO at times seems a lot more usable than ASU because it doesn't have any > of > > the old 2007.2 orange themeing. In ASU it tends to oversize the icons > and > > cause them fit poorly in toolbars and such (see the terminal and > tangoGPS). > > Is there any way for a user to remove the orage gtk+ theme from ASU? > > You can probably just move /etc/gtk-2.0/gtkrc to a different location to > kill off the theme, but it might break some gtk app icons, etc. > > Alternatively, you can set the button sizes to something reasonable by > adding this to the bottom of that file (two lines): > > gtk-toolbar-style = GTK_TOOLBAR_ICONS > gtk-icon-sizes = > "gtk-button=32,32:gtk-small-toolbar=16,16:gtk-large-toolbar=24,24" > Thanks for the response, stock ASU doesn't have an /etc/gtk-2.0/gtkrc file. Maybe I'll wait for the bug Steven reported to be resolved. -- Dylan Type faster. Use Dvorak: http://dvzine.org ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Remove GTK themeing from ASU
FSO at times seems a lot more usable than ASU because it doesn't have any of the old 2007.2 orange themeing. In ASU it tends to oversize the icons and cause them fit poorly in toolbars and such (see the terminal and tangoGPS). Is there any way for a user to remove the orage gtk+ theme from ASU? Dylan ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
2008.8 - unable to unmount SD card because it's in use
On a freshly booted 2008.8 Freerunner, I can't unmount the SD card because it says it's busy. Anyone know what is accessing the card? -- Dylan Type faster. Use Dvorak: http://dvzine.org ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
2008.8 - minimo's failed dependency
Anyone know why we don't have the most updated version of this library in 2008.8? # opkg install minimo_0.02\+cvs20070626-r0_armv4t.ipk Installing minimo (1:0.02+cvs20070626-r0) to root... Collected errors: * ERROR: Cannot satisfy the following dependencies for minimo: * libfreetype6 (>= 2.3.6) * # opkg install libfreetype6 Package libfreetype6 (2.3.5-r2) installed in root is up to date. I assume it was in all the other releases because I didn't have any problems installing minimo on them: -- Dylan Type faster. Use Dvorak: http://dvzine.org ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Non-descript subject lines (was 2008.8 - issue)
On Fri, Aug 8, 2008 at 10:32 AM, Dylan Semler <[EMAIL PROTECTED]>wrote: > On Fri, Aug 8, 2008 at 8:21 AM, William Kenworthy <[EMAIL PROTECTED]>wrote: > >> How do you type something like "apm" into the terminal application? - oh >> how I *HATE* predictive text :( >> >> Is there a way to kill it? >> > > By the way, "2008.2 - Issue" is a /horrible/ subject name. Try to be > descriptive so that > > a) people can find these conversations later when searching the archives > b) people can decide which emails to read > > Can you imagine If everyone sent emails with subjects like that? > > Bah! Sorry, I didn't see sparky's original thread that listed the multiple issues he was having. That is slightly less of an offence, but I'd still suggest changing the subject name when replying/focusing on a single issue. -- Dylan Type faster. Use Dvorak: http://dvzine.org ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Non-descript subject lines (was 2008.8 - issue)
On Fri, Aug 8, 2008 at 8:21 AM, William Kenworthy <[EMAIL PROTECTED]>wrote: > How do you type something like "apm" into the terminal application? - oh > how I *HATE* predictive text :( > > Is there a way to kill it? > By the way, "2008.2 - Issue" is a /horrible/ subject name. Try to be descriptive so that a) people can find these conversations later when searching the archives b) people can decide which emails to read Can you imagine If everyone sent emails with subjects like that? -- Dylan Type faster. Use Dvorak: http://dvzine.org ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: FSO Wifi - can ping but cannot download
On Mon, Aug 4, 2008 at 11:33 PM, Asheesh Laroia <[EMAIL PROTECTED]> wrote: > > Are you, by any chance, connected to the Internet over DSL? > > Sorry, I connect through cable -- Dylan Type faster. Use Dvorak: http://dvzine.org ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: FSO Wifi - can ping but cannot download
On Mon, Aug 4, 2008 at 5:46 AM, Cesar Eduardo Barros <[EMAIL PROTECTED]>wrote: > Andy Green escreveu: > > Sounds specific to tcp transport, ping is ICMP and DNS usually UDP. > > Maybe connect to a local Linux box and run tcpdump on there to study > > what it sees from the connection action. > > No, it's not "ping and DNS do not use TCP". It's "ping and DNS and TCP > SYN are small packets, data transfer is large packets", i.e. PMTU > blackhole. I've seen that thing happen way too many times, and the > workaround is almost always a MSS clamp (which is an ugly but > unfortunately necessary hack). > > Well internet is working now, I'm still not sure what was wrong though. I got a bit of help about MSS clamp[1] and tried the following commands from my router: # nvram set ppp_mtu=1492 # nvram commit # reboot upon reboot of the router I verified that it worked: # nvram show | grep mtu pptpd_client_mtu=1450 mtu_enable=0 size: 25395 bytes (7373 left) pptpd_client_srvmtu=1450 wan_mtu=1500 ppp_mtu=1492 but internet still didn't work. I then started stabbing in the dark, trying nvram set wan_mtu=1492 and nvram set mtu_enable=1. Those changes didn't seem to take hold (according to nvram show) so I set them back to 1500 and 0 and rebooted. When the router came back online the internet was working on my Freerunner. I then set ppp_mtu=1500 to verify that that was the issue, and my Freerunner still worked. So now I'm not hacking an MSS clamp and the internet seems to be working. Maybe the router just needed to be restarted a few times. Thanks for all of your help. [1] http://forum.openwrt.org/viewtopic.php?id=5662 -- Dylan Type faster. Use Dvorak: http://dvzine.org ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: FSO Wifi - can ping but cannot download
On Mon, Aug 4, 2008 at 11:40 AM, macebre <[EMAIL PROTECTED]> wrote: > hi had the same problem with the ASU image. Another (second or > third?) "udhcpc" in the Terminal did it for me. > Thanks for the suggestion but that didn't work -- Dylan Type faster. Use Dvorak: http://dvzine.org ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: FSO Wifi - can ping but cannot download
On Mon, Aug 4, 2008 at 6:18 AM, Andy Green <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Somebody in the thread at some point said: > | Andy Green escreveu: > |> Somebody in the thread at some point said: > |> | I've configured WiFi on a fresh FSO image the same way I had on a > 2008.2 > |> | image--by creating a wpa_supplicant.conf file and editing > |> | /etc/network/interfaces. This configuration worked on the 2008.2 > image > |> | but when I try implementing it on an FSO image, I cannot download > |> | anything. I can ping sites and when using wget, I can connect to > them, > |> | but downloading never commences. It's not a DNS issue because ping > and > |> | wget seem to be able to resolve correctly. Any thoughts? > |> > |> Sounds specific to tcp transport, ping is ICMP and DNS usually UDP. > |> Maybe connect to a local Linux box and run tcpdump on there to study > |> what it sees from the connection action. > | > | No, it's not "ping and DNS do not use TCP". It's "ping and DNS and TCP > | SYN are small packets, data transfer is large packets", i.e. PMTU > | blackhole. I've seen that thing happen way too many times, and the > | workaround is almost always a MSS clamp (which is an ugly but > | unfortunately necessary hack). > > Well, he says it worked on some other image. > > The guy can test this by seeing if he has any bulk transfer with local > machines on his side of his router. > > He can also mess with his ping payload size and confirm if that controls > the issue... > > # ping -s 4096 192.168.0.1 > PING 192.168.0.1 (192.168.0.1) 4096(4124) bytes of data. > 4104 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=5.36 ms > I can wget files hosted on the local side of the router, cannot wget anything external. ping -s 4096 192.168.1.1 still works. -- Dylan Type faster. Use Dvorak: http://dvzine.org ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: FSO Wifi - can ping but cannot download
On Sun, Aug 3, 2008 at 10:16 PM, Dylan Semler <[EMAIL PROTECTED]>wrote: > I've configured WiFi on a fresh FSO image the same way I had on a 2008.2 > image--by creating a wpa_supplicant.conf file and editing > /etc/network/interfaces. This configuration worked on the 2008.2 image but > when I try implementing it on an FSO image, I cannot download anything. I > can ping sites and when using wget, I can connect to them, but downloading > never commences. It's not a DNS issue because ping and wget seem to be able > to resolve correctly. Any thoughts? > Of course by 2008.2 I mean 2007.2. -- Dylan Type faster. Use Dvorak: http://dvzine.org ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
FSO Wifi - can ping but cannot download
I've configured WiFi on a fresh FSO image the same way I had on a 2008.2 image--by creating a wpa_supplicant.conf file and editing /etc/network/interfaces. This configuration worked on the 2008.2 image but when I try implementing it on an FSO image, I cannot download anything. I can ping sites and when using wget, I can connect to them, but downloading never commences. It's not a DNS issue because ping and wget seem to be able to resolve correctly. Any thoughts? -- Dylan Type faster. Use Dvorak: http://dvzine.org ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Freerunner (GTK2007.2) has suddenly become unbootable
On Mon, Jul 28, 2008 at 11:52 PM, casaubon <[EMAIL PROTECTED]> wrote: > Dylan Semler wrote: > > > > My guess is opkg isn't updating the kernel properly. > > -- > > Dylan > > > > Yeah, I suppose this was my first reboot since the update. Very > aggravating. > The phone has every indication of being bricked: > > http://wiki.openmoko.org/wiki/Bricked > > I cannot get a USB connection to the device, or I'd try flashing it. Plus, > the phone tends to shut itself off if left unattended in uboot. Is there a > way to restore the factory image that is internal to the phone? It should be impossible to brick the Freerunner without a debug board. I've been able to reflash by following the instructions: http://wiki.openmoko.org/wiki/Flashing_the_Neo_FreeRunner#Flashing_the_Kernel -- Dylan Type faster. Use Dvorak: http://dvzine.org ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Freerunner (GTK2007.2) has suddenly become unbootable
On Mon, Jul 28, 2008 at 6:38 PM, casaubon <[EMAIL PROTECTED]> wrote: > > Hi, all. > > I went to pick up my FR to make a call earlier, and the screen locker > responded *really, really* slowly. Desktop was equally slow in response. I > powered down (gracefully, it seemed to me) using the power settings menu, > but the device refuses to boot again (it can't get past the mokologo > splash). I'm in a similar situation, though I haven't tried anything in u-boot. This happened when I opkg updated the system tonight from a 20080722 image (which appears to be the most recent available image on the buildhost). I've had this problem after updating both ASU and 2007.2 images. Also, I received the following error on each rootfs while opkg updating: [snip] Configuring kernel update-alternatives: Linking //boot/uImage to uImage-2.6.24 Configuring kernel-2.6.24 Configuring kernel-image-2.6.24 Upgrading Kernel in Flash DO NOT stop this process Erasing 128 Kibyte @ 7e -- 98 % complete. open input file: No such file or directory [snip] My guess is opkg isn't updating the kernel properly. -- Dylan Type faster. Use Dvorak: http://dvzine.org ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: /var/log?
On Thu, Jul 17, 2008 at 12:56 AM, doron <[EMAIL PROTECTED]> wrote: > > Hi Dylan, > > > take a look at /etc/syslog.conf. the default configuration destination is > to write to buffer but you can change to file or to log server. > > > I am using my laptop as the log server to my Neo, and it's work fine foe > me. > > > That did it, thanks -- Dylan Type faster. Use Dvorak: http://dvzine.org ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
/var/log?
I'm trying to get gprs working on my FreeRunner. Many people have suggested checking the logs to troubleshoot, but the only thing in /var/log is a file called "wtmp" and it appears to be a binary file. I have also seen people point to log files in /tmp, but all I have there is a pulse-root folder and an x.log file. I'm running a 2007.2 image from yesterday July 15th 2008. -- Dylan Type faster. Use Dvorak: http://dvzine.org ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
