[FSO] Wifi in M5 no longer functioning
Dylan Semler
dylan.semler at gmail.com
Thu Feb 5 04:52:24 CET 2009
On Wed, Feb 4, 2009 at 4:51 AM, Andy Green <andy at openmoko.com> 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.510000] s3c2440-sdi s3c2440-sdi: running at 0kHz (requested:
0kHz).
[21474827.510000] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested:
195kHz).
[21474827.510000] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested:
195kHz).
[21474827.520000] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested:
195kHz).
[21474827.520000] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested:
195kHz).
[21474827.545000] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested:
195kHz).
[21474827.560000] mmc0: queuing CIS tuple 0x01 length 3
[21474827.580000] 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.650000] BMI Get Target Info: Exit (ver: 0x20000059 type: 0x1)
[21474828.725000] AR6000 Reg Code = 0x40000060
[21474833.405000] ar6000_ioctl_giwscan(): data length 0
[21474836.360000] AR6000 Reg Code = 0x80000348
[ 4.585000] eth0: no IPv6 routers present
[ 4.890000] channel hint set to 2437
[ 4.905000] AR6000 disconnected
[ 4.965000] AR6000 connected event on freq 2437 with bssid <my AP MAC
address> listenInterval=100, beaconInterval = 100, beaconIeLen = 22
assocReqLen=59 assocRespLen =59
[ 4.965000] Network: Infrastructure
> # iwconfig
root at om-gta02:~# iwconfig
lo no wireless extensions.
usb0 no wireless extensions.
pan0 no wireless extensions.
eth0 AR6000 802.11g ESSID:<my ESSID>
Mode:Managed Frequency:2.437 GHz Access Point: <my AP MAC
address>
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
>
root at om-gta02:~# iwlist eth0 scan
eth0 Scan completed :
Cell 01 - Address: <my AP MAC address>
ESSID:<my 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=30140100000fac020100000fac020100000fac020c00
Extra:wmm_ie=dd180050f2020101800003a4000027a4000042435e0062322f00
>
> 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
>
root at om-gta02:~# lsmod
Module Size Used by
bnep 12800 2
sco 10444 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_pcm 76364 2 snd_soc_s3c24xx,snd_soc_core
snd_timer 21052 1 snd_pcm
snd_page_alloc 6504 1 snd_pcm
snd 50788 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_ether 39604 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
>
>
root at 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 MULTICAST MTU:1500 Metric:1
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1 errors:0 dropped:0 overruns:0 frame:0
TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:104 (104.0 B) TX bytes:104 (104.0 B)
pan0 Link encap:Ethernet HWaddr AA:92:6C:B1:E1:A9
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
usb0 Link encap:Ethernet HWaddr 6E:F1:73:29:F6:4E
inet addr:192.168.0.202 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::6cf1:73ff:fe29:f64e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:638 errors:0 dropped:0 overruns:0 frame:0
TX packets:510 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:46204 (45.1 KiB) TX bytes:154823 (151.1 KiB)
It seems to look like it's connected, but I still can't ping google, the AP,
or access the internet.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openmoko.org/pipermail/support/attachments/20090204/5cbab8f1/attachment-0001.htm
More information about the support
mailing list
