Re: [OpenWrt-Devel] [OpenWrt-Users] Linksys WRT150N wireless supported in 10.03.1?
On 02/12/2012 09:10 PM, Aaron Z wrote: On 02/02/2012 4:52:09 PM, Hauke Mehrtens wrote: On 01/28/2012 06:55 AM, Aaron Z wrote: When I run killall -9 hostapd then wifi I get told: Configuration file: /var/run/hostapd-phy0.conf and Using interface wlan0 with hwaddr MACADDRESS and ssid 'OpenWrt'wifi is still rejecting connections. When I run killall -9 hostapd; /usr/sbin/hostapd -dd /var/run/hostapd-phy0.conf /tmp/hostapd.log it works right away. This behavior is strange it could be that debugging activates some needed code path, hostapd just works after the second start or that there are timing issues. Could you run hostapd just with -d and without -d and report what happens in these cases? Sorry for the delay. Its been busy around here. I ran killall -9 hostapd; /usr/sbin/hostapd -d /var/run/hostapd-phy0.conf /tmp/hostapd.log I was able to connect and go online. The log is attached as hostapd -d.txt (4 KB). I then rebooted the WAP and ran killall -9 hostapd; /usr/sbin/hostapd /var/run/hostapd-phy0.conf /tmp/hostapd.log I was able to connect and go online. The logfile was blank, so I didn't attach it. I tried connecting before running the commands and was rejected both times. Thanks Aaron Z Hi Aaron Z, have you set up a build environment? If so please try the attached patch ( just place it under package/mac80211/patches/) and build b43 with debug enabled. I had some problems with n-phy device on bcma as well and it was fixed with this patch. If the problem still exists please post the output of dmesg after the first boot. Hauke From cd6e7f84fa813c48f608f95152f020c842cc8e5a Mon Sep 17 00:00:00 2001 From: Hauke Mehrtens ha...@hauke-m.de Date: Sat, 18 Feb 2012 22:21:01 +0100 Subject: [PATCH 202/202] b43: do not use msleep(1) in b43_radio_init2056_post With msleep(1) I get a Data bus error and with usleep_range(1500, 2000) it works. I udelay(1000) also works, but usleep_range(1000, 1500) does not work. The timer documentation says you should not use msleep for values 20. Signed-off-by: Hauke Mehrtens ha...@hauke-m.de --- drivers/net/wireless/b43/phy_n.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) --- a/drivers/net/wireless/b43/phy_n.c +++ b/drivers/net/wireless/b43/phy_n.c @@ -661,7 +661,7 @@ static void b43_radio_init2056_post(stru b43_radio_set(dev, B2056_SYN_COM_CTRL, 0xB); b43_radio_set(dev, B2056_SYN_COM_PU, 0x2); b43_radio_set(dev, B2056_SYN_COM_RESET, 0x2); - msleep(1); + udelay(1000); b43_radio_mask(dev, B2056_SYN_COM_RESET, ~0x2); b43_radio_mask(dev, B2056_SYN_PLL_MAST2, ~0xFC); b43_radio_mask(dev, B2056_SYN_RCCAL_CTRL0, ~0x1); ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [OpenWrt-Users] Linksys WRT150N wireless supported in 10.03.1?
On 02/02/2012 4:52:09 PM, Hauke Mehrtens wrote: On 01/28/2012 06:55 AM, Aaron Z wrote: When I run killall -9 hostapd then wifi I get told: Configuration file: /var/run/hostapd-phy0.conf and Using interface wlan0 with hwaddr MACADDRESS and ssid 'OpenWrt'wifi is still rejecting connections. When I run killall -9 hostapd; /usr/sbin/hostapd -dd /var/run/hostapd-phy0.conf /tmp/hostapd.log it works right away. This behavior is strange it could be that debugging activates some needed code path, hostapd just works after the second start or that there are timing issues. Could you run hostapd just with -d and without -d and report what happens in these cases? Sorry for the delay. Its been busy around here. I ran killall -9 hostapd; /usr/sbin/hostapd -d /var/run/hostapd-phy0.conf /tmp/hostapd.log I was able to connect and go online. The log is attached as hostapd -d.txt (4 KB). I then rebooted the WAP and ran killall -9 hostapd; /usr/sbin/hostapd /var/run/hostapd-phy0.conf /tmp/hostapd.log I was able to connect and go online. The logfile was blank, so I didn't attach it. I tried connecting before running the commands and was rejected both times. Thanks Aaron Zrandom: Trying to read entropy from /dev/random Configuration file: /var/run/hostapd-phy0.conf nl80211: interface wlan0 in phy phy0 nl80211: Set mode ifindex 6 iftype 2 (STATION) nl80211: Failed to set interface 6 to mode 2: -16 (Device or resource busy) nl80211: Interface already in requested mode - ignore error netlink: Operstate: linkmode=1, operstate=5 nl80211: Using driver-based off-channel TX nl80211: Interface wlan0 is in bridge br-lan nl80211: Add own interface ifindex 5 nl80211: Add own interface ifindex 6 nl80211: Set mode ifindex 6 iftype 3 (AP) nl80211: Create interface iftype 6 (MONITOR) Failed to create interface mon.wlan0: -23 (Too many open files in system) Try to remove and re-create mon.wlan0 nl80211: Remove interface ifindex=7 nl80211: Create interface iftype 6 (MONITOR) nl80211: New interface mon.wlan0 created: ifindex=8 nl80211: Add own interface ifindex 8 BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits) nl80211: Regulatory information - country=00 nl80211: 2402-2472 @ 40 MHz nl80211: 2457-2482 @ 20 MHz nl80211: 2474-2494 @ 20 MHz nl80211: 5170-5250 @ 40 MHz nl80211: 5735-5835 @ 40 MHz nl80211: Added 802.11b mode based on 802.11g information Completing interface initialization Mode: IEEE 802.11g Channel: 11 Frequency: 2462 MHz nl80211: Set freq 2462 (ht_enabled=0 sec_channel_offset=0) RATE[0] rate=10 flags=0x1 RATE[1] rate=20 flags=0x1 RATE[2] rate=55 flags=0x1 RATE[3] rate=110 flags=0x1 RATE[4] rate=60 flags=0x0 RATE[5] rate=90 flags=0x0 RATE[6] rate=120 flags=0x0 RATE[7] rate=180 flags=0x0 RATE[8] rate=240 flags=0x0 RATE[9] rate=360 flags=0x0 RATE[10] rate=480 flags=0x0 RATE[11] rate=540 flags=0x0 Flushing old station entries Deauthenticate all stations wpa_driver_nl80211_set_key: ifindex=6 alg=0 addr=(nil) key_idx=0 set_tx=0 seq_len=0 key_len=0 wpa_driver_nl80211_set_key: ifindex=6 alg=0 addr=(nil) key_idx=1 set_tx=0 seq_len=0 key_len=0 wpa_driver_nl80211_set_key: ifindex=6 alg=0 addr=(nil) key_idx=2 set_tx=0 seq_len=0 key_len=0 wpa_driver_nl80211_set_key: ifindex=6 alg=0 addr=(nil) key_idx=3 set_tx=0 seq_len=0 key_len=0 Using interface wlan0 with hwaddr 00:88:88:88:00:2a and ssid 'OpenWrt' Using existing control interface directory. ctrl_iface bind(PF_UNIX) failed: Address already in use ctrl_iface exists, but does not allow connections - assuming it was leftover from forced program termination Successfully replaced leftover ctrl_iface socket '/var/run/hostapd-phy0/wlan0' nl80211: Set beacon (beacon_set=0) wpa_driver_nl80211_set_operstate: operstate 0-1 (UP) netlink: Operstate: linkmode=-1, operstate=6 wlan0: Setup of interface done. RTM_NEWLINK: operstate=1 ifi_flags=0x11003 ([UP][LOWER_UP]) netlink: Operstate: linkmode=-1, operstate=6 RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added Unknown event 5 nl80211: Add ifindex 5 for bridge br-lan nl80211: Add own interface ifindex 5 RTM_NEWLINK: operstate=1 ifi_flags=0x11003 ([UP][LOWER_UP]) netlink: Operstate: linkmode=-1, operstate=6 RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added Unknown event 5 RTM_NEWLINK: operstate=1 ifi_flags=0x1002 () nl80211: Ignore interface down event since interface wlan0 is up RTM_NEWLINK: operstate=1 ifi_flags=0x1002 () nl80211: Ignore interface down event since interface wlan0 is up RTM_NEWLINK: operstate=1 ifi_flags=0x1002 () nl80211: Ignore interface down event since interface wlan0 is up RTM_NEWLINK: operstate=1 ifi_flags=0x1002 () nl80211: Ignore interface down event since interface wlan0 is up nl80211: Ignore event for foreign ifindex 7 nl80211: Ignore dellink event for foreign ifindex 7 RTM_NEWLINK: operstate=1 ifi_flags=0x1002 () nl80211: Ignore interface down event since interface mon.wlan0 is up RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP]) RTM_NEWLINK, IFLA_IFNAME: Interface 'mon.wlan0'
Re: [OpenWrt-Devel] [OpenWrt-Users] Linksys WRT150N wireless supported in 10.03.1?
Hi Aaron, On 01/28/2012 06:55 AM, Aaron Z wrote: Thanks for looking at my logs. I just installed the trunk that was compiled today (r29915, thanks to whoever ran that build) and SSH seems to be behaving, so my SSH issues may have just been a fluke. I got an other report of SSH not working correctly so there seams to be something wrong. Wireless still fails at boot until I run the wifi debugging command as shown below. I tried running just wifi and even though both commands claim to use /var/run/hostapd-phy0.conf for the config, something is different. When I run killall -9 hostapd then wifi I get told: Configuration file: /var/run/hostapd-phy0.conf and Using interface wlan0 with hwaddr MACADDRESS and ssid 'OpenWrt'wifi is still rejecting connections. When I run killall -9 hostapd; /usr/sbin/hostapd -dd /var/run/hostapd-phy0.conf /tmp/hostapd.log it works right away. This behavior is strange it could be that debugging activates some needed code path, hostapd just works after the second start or that there are timing issues. Could you run hostapd just with -d and without -d and report what happens in these cases? One oddity, I see what may be an extraneous entry in ifconfig called mon.wlan0: Before the debug piece above: mon.wlan0 Link encap:UNSPEC HWaddr 00-88-88-88-00-2A-00-00-00-00-00-00-00-00-00-00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:402 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:38292 (37.3 KiB) TX bytes:0 (0.0 B) wlan0 Link encap:Ethernet HWaddr 00:18:F8:D7:BB:35 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:10 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:0 (0.0 B) TX bytes:1516 (1.4 KiB) After: mon.wlan0 Link encap:UNSPEC HWaddr 00-88-88-88-00-2A-00-00-00-00-00-00-00-00-00-00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:136 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:13650 (13.3 KiB) TX bytes:0 (0.0 B) wlan0 Link encap:Ethernet HWaddr 00:88:88:88:00:2A UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:64 errors:0 dropped:0 overruns:0 frame:0 TX packets:119 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:7058 (6.8 KiB) TX bytes:15905 (15.5 KiB) Should mon.wlan0 be there? mon.wlan0 is created by hostapd and is needed in AP mode. Why do the errors all go away? Thanks Aaron Z - Original Message - From: Hauke Mehrtens ha...@hauke-m.de To: Aaron Z aar...@pls-net.org Cc: OpenWrt Development List openwrt-devel@lists.openwrt.org Sent: Monday, January 23, 2012 4:38:16 PM Subject: Re: [OpenWrt-Users] Linksys WRT150N wireless supported in 10.03.1? Hi Aaron, thanks for the detailed report. With a quick look I was unable to see anything suspicious in the logs. I will try to reproduce your problems on one of my devices. Hauke On 01/22/2012 07:49 PM, Aaron Z wrote: Got the wireless to work today. I followed the directions at http://wiki.openwrt.org/doc/devel/debugging and ran killall -9 hostapd; /usr/sbin/hostapd -dd /var/run/hostapd-phy0.conf /tmp/hostapd.log from a SSH session, then tried to connect. Before I ran it, I would get a connection failed message as soon as I tried to connect. After I ran the above command, it failed once, then connected on the 2nd try. That log is attatched as WiFiLog1.txt. I rebooted by pulling the power cable (I am fairly certain that the reboot command worked in 10.03.1, but cannot say for certain) and I tried connecting to the wifi again. I got a connection failed message as soon as I tried to connect. After I ran the aforementioned command, I was able to connect immediately on the first try. That log is attached as WiFiLog2.txt. Is there a more effective and/or less intrusive way to log this data? I looked in /tmp/log, but the only things I see are lastlog and wtmp both of which are 0 byte files that claim to have been created on 1/1/1970. SSH and SCP both worked fine under 10.03.1. No lockups or reconnects that I remember. Package installation also worked. I was able to install the pciutils package without any drama. Let me know if I can provide any more data to help. Thanks Aaron Z - Original Message - From: Hauke Mehrtens ha...@hauke-m.de To: Aaron Z aar...@pls-net.org Cc: OpenWrt Development List openwrt-devel@lists.openwrt.org Sent: Sunday, January 22, 2012 8:16:52 AM Subject: Re: [OpenWrt-Users] Linksys WRT150N wireless supported in 10.03.1? Hi Aaron, On
Re: [OpenWrt-Devel] [OpenWrt-Users] Linksys WRT150N wireless supported in 10.03.1?
Thanks for looking at my logs. I just installed the trunk that was compiled today (r29915, thanks to whoever ran that build) and SSH seems to be behaving, so my SSH issues may have just been a fluke. Wireless still fails at boot until I run the wifi debugging command as shown below. I tried running just wifi and even though both commands claim to use /var/run/hostapd-phy0.conf for the config, something is different. When I run killall -9 hostapd then wifi I get told: Configuration file: /var/run/hostapd-phy0.conf and Using interface wlan0 with hwaddr MACADDRESS and ssid 'OpenWrt'wifi is still rejecting connections. When I run killall -9 hostapd; /usr/sbin/hostapd -dd /var/run/hostapd-phy0.conf /tmp/hostapd.log it works right away. One oddity, I see what may be an extraneous entry in ifconfig called mon.wlan0: Before the debug piece above: mon.wlan0 Link encap:UNSPEC HWaddr 00-88-88-88-00-2A-00-00-00-00-00-00-00-00-00-00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:402 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:38292 (37.3 KiB) TX bytes:0 (0.0 B) wlan0 Link encap:Ethernet HWaddr 00:18:F8:D7:BB:35 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:10 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:0 (0.0 B) TX bytes:1516 (1.4 KiB) After: mon.wlan0 Link encap:UNSPEC HWaddr 00-88-88-88-00-2A-00-00-00-00-00-00-00-00-00-00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:136 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:13650 (13.3 KiB) TX bytes:0 (0.0 B) wlan0 Link encap:Ethernet HWaddr 00:88:88:88:00:2A UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:64 errors:0 dropped:0 overruns:0 frame:0 TX packets:119 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:7058 (6.8 KiB) TX bytes:15905 (15.5 KiB) Should mon.wlan0 be there? Why do the errors all go away? Thanks Aaron Z - Original Message - From: Hauke Mehrtens ha...@hauke-m.de To: Aaron Z aar...@pls-net.org Cc: OpenWrt Development List openwrt-devel@lists.openwrt.org Sent: Monday, January 23, 2012 4:38:16 PM Subject: Re: [OpenWrt-Users] Linksys WRT150N wireless supported in 10.03.1? Hi Aaron, thanks for the detailed report. With a quick look I was unable to see anything suspicious in the logs. I will try to reproduce your problems on one of my devices. Hauke On 01/22/2012 07:49 PM, Aaron Z wrote: Got the wireless to work today. I followed the directions at http://wiki.openwrt.org/doc/devel/debugging and ran killall -9 hostapd; /usr/sbin/hostapd -dd /var/run/hostapd-phy0.conf /tmp/hostapd.log from a SSH session, then tried to connect. Before I ran it, I would get a connection failed message as soon as I tried to connect. After I ran the above command, it failed once, then connected on the 2nd try. That log is attatched as WiFiLog1.txt. I rebooted by pulling the power cable (I am fairly certain that the reboot command worked in 10.03.1, but cannot say for certain) and I tried connecting to the wifi again. I got a connection failed message as soon as I tried to connect. After I ran the aforementioned command, I was able to connect immediately on the first try. That log is attached as WiFiLog2.txt. Is there a more effective and/or less intrusive way to log this data? I looked in /tmp/log, but the only things I see are lastlog and wtmp both of which are 0 byte files that claim to have been created on 1/1/1970. SSH and SCP both worked fine under 10.03.1. No lockups or reconnects that I remember. Package installation also worked. I was able to install the pciutils package without any drama. Let me know if I can provide any more data to help. Thanks Aaron Z - Original Message - From: Hauke Mehrtens ha...@hauke-m.de To: Aaron Z aar...@pls-net.org Cc: OpenWrt Development List openwrt-devel@lists.openwrt.org Sent: Sunday, January 22, 2012 8:16:52 AM Subject: Re: [OpenWrt-Users] Linksys WRT150N wireless supported in 10.03.1? Hi Aaron, On 01/22/2012 04:54 AM, Aaron Z wrote: Resending as I used the wrong from address last time and it bounced. hmm at least I got your mails. It loaded and booted, but I am seeing some oddities. Not sure if these are related to being bleeding edge or what, but they are noticeable: The patch did what it was supposed to and I will merge it into trunk and Backfire branch. The other problems seam to be related to some other
Re: [OpenWrt-Devel] [OpenWrt-Users] Linksys WRT150N wireless supported in 10.03.1?
Hi Aaron, thanks for the detailed report. With a quick look I was unable to see anything suspicious in the logs. I will try to reproduce your problems on one of my devices. Hauke On 01/22/2012 07:49 PM, Aaron Z wrote: Got the wireless to work today. I followed the directions at http://wiki.openwrt.org/doc/devel/debugging and ran killall -9 hostapd; /usr/sbin/hostapd -dd /var/run/hostapd-phy0.conf /tmp/hostapd.log from a SSH session, then tried to connect. Before I ran it, I would get a connection failed message as soon as I tried to connect. After I ran the above command, it failed once, then connected on the 2nd try. That log is attatched as WiFiLog1.txt. I rebooted by pulling the power cable (I am fairly certain that the reboot command worked in 10.03.1, but cannot say for certain) and I tried connecting to the wifi again. I got a connection failed message as soon as I tried to connect. After I ran the aforementioned command, I was able to connect immediately on the first try. That log is attached as WiFiLog2.txt. Is there a more effective and/or less intrusive way to log this data? I looked in /tmp/log, but the only things I see are lastlog and wtmp both of which are 0 byte files that claim to have been created on 1/1/1970. SSH and SCP both worked fine under 10.03.1. No lockups or reconnects that I remember. Package installation also worked. I was able to install the pciutils package without any drama. Let me know if I can provide any more data to help. Thanks Aaron Z - Original Message - From: Hauke Mehrtens ha...@hauke-m.de To: Aaron Z aar...@pls-net.org Cc: OpenWrt Development List openwrt-devel@lists.openwrt.org Sent: Sunday, January 22, 2012 8:16:52 AM Subject: Re: [OpenWrt-Users] Linksys WRT150N wireless supported in 10.03.1? Hi Aaron, On 01/22/2012 04:54 AM, Aaron Z wrote: Resending as I used the wrong from address last time and it bounced. hmm at least I got your mails. It loaded and booted, but I am seeing some oddities. Not sure if these are related to being bleeding edge or what, but they are noticeable: The patch did what it was supposed to and I will merge it into trunk and Backfire branch. The other problems seam to be related to some other problems with trunk or with the wifi never used before. 1. luci (the web interface) times out and never loads The image I gave you did not contain luci so it will not load. 2. Installing packages does not seem to be working. When I run opkg update it gets to Inflating http://downloads.openwrt.org/snapshots/trunk/brcm47xx/packages/Packages.gz; then locks up my SSH session and I have to reconnect The image is a self build from trunk so with installing packages you could run into problems. But this problem is strange. 3. The reboot command does not seem to do anything (as determined by watching the LEDs and the response to ping). Did this work with 10.03.1? 4. It seems that ssh and scp lock up and force me to re-login frequently. No idea what it is related to, but it seems to do it every few minutes. Did this work with 10.03.1? 5. I see the OpenWrt wireless network after enabling the wireless, but I cannot connect to it (fails right away). When I run connection diagnostics, Windows 7 tells me Wireless association to this network failed. Windows did not receive any response from the wireless router or accesspoint Do you see anything interesting in the log regarding wifi while trying to connect? 6. The Wireless LED on the WAP does not turn on Probably something is wrong in the wireless driver. There is a know issue with the wireless chip used in your device, but I do not know, if you are seeing this issue or if it is already fixed: BCM4321: some cards do not work in DMA mode (PIO is needed). Attached are: 1. dmesg2.txt (15.5 KB, the output of dmesg) The log looks good to me at least OpenWrt finds your wifi and does not panic. ;-) 2. nvram2.txt (11.8 KB, the output of nvram show) 3. wireless2.txt (330 B, the contents of /var/config/wireless) Aaron Z I asked for the serial in the case the changes in the patch are causing a kernel panic and the device does not boot any more, so that you were able to recover or debug the issue, but it looks like it is not needed. But be aware that the normal serial port of a PC uses 12V and the serial TTL port of most embedded devices are using 3.3V Hauke ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [OpenWrt-Users] Linksys WRT150N wireless supported in 10.03.1?
Hi Aaron, On 01/22/2012 04:54 AM, Aaron Z wrote: Resending as I used the wrong from address last time and it bounced. hmm at least I got your mails. It loaded and booted, but I am seeing some oddities. Not sure if these are related to being bleeding edge or what, but they are noticeable: The patch did what it was supposed to and I will merge it into trunk and Backfire branch. The other problems seam to be related to some other problems with trunk or with the wifi never used before. 1. luci (the web interface) times out and never loads The image I gave you did not contain luci so it will not load. 2. Installing packages does not seem to be working. When I run opkg update it gets to Inflating http://downloads.openwrt.org/snapshots/trunk/brcm47xx/packages/Packages.gz; then locks up my SSH session and I have to reconnect The image is a self build from trunk so with installing packages you could run into problems. But this problem is strange. 3. The reboot command does not seem to do anything (as determined by watching the LEDs and the response to ping). Did this work with 10.03.1? 4. It seems that ssh and scp lock up and force me to re-login frequently. No idea what it is related to, but it seems to do it every few minutes. Did this work with 10.03.1? 5. I see the OpenWrt wireless network after enabling the wireless, but I cannot connect to it (fails right away). When I run connection diagnostics, Windows 7 tells me Wireless association to this network failed. Windows did not receive any response from the wireless router or accesspoint Do you see anything interesting in the log regarding wifi while trying to connect? 6. The Wireless LED on the WAP does not turn on Probably something is wrong in the wireless driver. There is a know issue with the wireless chip used in your device, but I do not know, if you are seeing this issue or if it is already fixed: BCM4321: some cards do not work in DMA mode (PIO is needed). Attached are: 1. dmesg2.txt (15.5 KB, the output of dmesg) The log looks good to me at least OpenWrt finds your wifi and does not panic. ;-) 2. nvram2.txt (11.8 KB, the output of nvram show) 3. wireless2.txt (330 B, the contents of /var/config/wireless) Aaron Z I asked for the serial in the case the changes in the patch are causing a kernel panic and the device does not boot any more, so that you were able to recover or debug the issue, but it looks like it is not needed. But be aware that the normal serial port of a PC uses 12V and the serial TTL port of most embedded devices are using 3.3V Hauke ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [OpenWrt-Users] Linksys WRT150N wireless supported in 10.03.1?
Got the wireless to work today. I followed the directions at http://wiki.openwrt.org/doc/devel/debugging and ran killall -9 hostapd; /usr/sbin/hostapd -dd /var/run/hostapd-phy0.conf /tmp/hostapd.log from a SSH session, then tried to connect. Before I ran it, I would get a connection failed message as soon as I tried to connect. After I ran the above command, it failed once, then connected on the 2nd try. That log is attatched as WiFiLog1.txt. I rebooted by pulling the power cable (I am fairly certain that the reboot command worked in 10.03.1, but cannot say for certain) and I tried connecting to the wifi again. I got a connection failed message as soon as I tried to connect. After I ran the aforementioned command, I was able to connect immediately on the first try. That log is attached as WiFiLog2.txt. Is there a more effective and/or less intrusive way to log this data? I looked in /tmp/log, but the only things I see are lastlog and wtmp both of which are 0 byte files that claim to have been created on 1/1/1970. SSH and SCP both worked fine under 10.03.1. No lockups or reconnects that I remember. Package installation also worked. I was able to install the pciutils package without any drama. Let me know if I can provide any more data to help. Thanks Aaron Z - Original Message - From: Hauke Mehrtens ha...@hauke-m.de To: Aaron Z aar...@pls-net.org Cc: OpenWrt Development List openwrt-devel@lists.openwrt.org Sent: Sunday, January 22, 2012 8:16:52 AM Subject: Re: [OpenWrt-Users] Linksys WRT150N wireless supported in 10.03.1? Hi Aaron, On 01/22/2012 04:54 AM, Aaron Z wrote: Resending as I used the wrong from address last time and it bounced. hmm at least I got your mails. It loaded and booted, but I am seeing some oddities. Not sure if these are related to being bleeding edge or what, but they are noticeable: The patch did what it was supposed to and I will merge it into trunk and Backfire branch. The other problems seam to be related to some other problems with trunk or with the wifi never used before. 1. luci (the web interface) times out and never loads The image I gave you did not contain luci so it will not load. 2. Installing packages does not seem to be working. When I run opkg update it gets to Inflating http://downloads.openwrt.org/snapshots/trunk/brcm47xx/packages/Packages.gz; then locks up my SSH session and I have to reconnect The image is a self build from trunk so with installing packages you could run into problems. But this problem is strange. 3. The reboot command does not seem to do anything (as determined by watching the LEDs and the response to ping). Did this work with 10.03.1? 4. It seems that ssh and scp lock up and force me to re-login frequently. No idea what it is related to, but it seems to do it every few minutes. Did this work with 10.03.1? 5. I see the OpenWrt wireless network after enabling the wireless, but I cannot connect to it (fails right away). When I run connection diagnostics, Windows 7 tells me Wireless association to this network failed. Windows did not receive any response from the wireless router or accesspoint Do you see anything interesting in the log regarding wifi while trying to connect? 6. The Wireless LED on the WAP does not turn on Probably something is wrong in the wireless driver. There is a know issue with the wireless chip used in your device, but I do not know, if you are seeing this issue or if it is already fixed: BCM4321: some cards do not work in DMA mode (PIO is needed). Attached are: 1. dmesg2.txt (15.5 KB, the output of dmesg) The log looks good to me at least OpenWrt finds your wifi and does not panic. ;-) 2. nvram2.txt (11.8 KB, the output of nvram show) 3. wireless2.txt (330 B, the contents of /var/config/wireless) Aaron Z I asked for the serial in the case the changes in the patch are causing a kernel panic and the device does not boot any more, so that you were able to recover or debug the issue, but it looks like it is not needed. But be aware that the normal serial port of a PC uses 12V and the serial TTL port of most embedded devices are using 3.3V Hauke root@OpenWrt:~# killall -9 hostapd; /usr/sbin/hostapd -dd /var/run/hostapd-phy0.conf /tmp/hostapd.log #/tmp/hostapd.log random: Trying to read entropy from /dev/random Configuration file: /var/run/hostapd-phy0.conf nl80211: interface wlan0 in phy phy0 nl80211: Set mode ifindex 6 iftype 2 (STATION) nl80211: Failed to set interface 6 to mode 2: -16 (Device or resource busy) nl80211: Interface already in requested mode - ignore error netlink: Operstate: linkmode=1, operstate=5 nl80211: Using driver-based off-channel TX nl80211: Interface wlan0 is in bridge br-lan nl80211: Add own interface ifindex 5 nl80211: Add own interface ifindex 6 nl80211: Set mode ifindex 6 iftype 3 (AP) nl80211: Create interface iftype 6 (MONITOR) Failed to create interface
Re: [OpenWrt-Devel] [OpenWrt-Users] Linksys WRT150N wireless supported in 10.03.1?
2012/1/22 Hauke Mehrtens ha...@hauke-m.de: 6. The Wireless LED on the WAP does not turn on Probably something is wrong in the wireless driver. There is a know issue with the wireless chip used in your device, but I do not know, if you are seeing this issue or if it is already fixed: BCM4321: some cards do not work in DMA mode (PIO is needed). It was fixed almost half a year ago by: ssb: fix DMA translation for some specific boards b43: fix DMA on some bugged hardware Not sure about the LED problem. -- Rafał ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
