Please be aware of all shipping deadlines before placing your order - we cannot guarantee orders will arrive before Christmas!

Beagle Wifi Adapter
Moderators: adafruit_support_bill, adafruit

Re: Beagle Wifi Adapter

by epexegeses on Thu Jul 05, 2012 10:59 pm

I recently bought the same wifi adapter from adafruit (http://www.adafruit.com/products/814) to work with my beaglebone, but after following the tutorial it cannot connect.

Using the dmesg command on the beaglebone, I get:

Code: Select all | TOGGLE FULL SIZE
root@beaglebone:~# dmesg
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 3.2.18 (koen@dominion) (gcc version 4.5.4 20120305 (prerelease) (GCC) ) #1 Thu Jun 14 23:26:20 CEST 2012
[    0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=50c53c7d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine: am335xevm
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] On node 0 totalpages: 65536
[    0.000000] free_area_init_node: node 0, pgdat c04915a8, node_mem_map c04da000
[    0.000000]   Normal zone: 512 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 65024 pages, LIFO batch:15
[    0.000000] AM335X ES1.0 (sgx neon )
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
[    0.000000] Kernel command line: console=ttyO0,115200n8 run_hardware_tests quiet root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait ip=none
[    0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] allocated 1048576 bytes of page_cgroup
[    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
[    0.000000] Memory: 256MB = 256MB total
[    0.000000] Memory: 253864k/253864k available, 8280k reserved, 0K highmem
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xd0800000 - 0xff000000   ( 744 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
[    0.000000]     modules : 0xbf800000 - 0xc0000000   (   8 MB)
[    0.000000]       .text : 0xc0008000 - 0xc0414418   (4146 kB)
[    0.000000]       .init : 0xc0415000 - 0xc044b000   ( 216 kB)
[    0.000000]       .data : 0xc044c000 - 0xc0491e20   ( 280 kB)
[    0.000000]        .bss : 0xc0491e44 - 0xc04d920c   ( 285 kB)
[    0.000000] NR_IRQS:410 nr_irqs:410 410
[    0.000000] IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
[    0.000000] Total of 128 interrupts on 1 active controller
[    0.000000] OMAP clockevent source: GPTIMER2 at 24000000 Hz
[    0.000000] omap_dm_timer_switch_src: Switching to HW default clocksource(sys_clkin_ck) for timer1, this may impact timekeeping in low power state
[    0.000000] OMAP clocksource: GPTIMER1 at 24000000 Hz
[    0.000000] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956ms
[    0.000000] Console: colour dummy device 80x30
[    0.000175] Calibrating delay loop... 718.02 BogoMIPS (lpj=3590144)
[    0.057177] pid_max: default: 32768 minimum: 301
[    0.057303] Security Framework initialized
[    0.057362] Mount-cache hash table entries: 512
[    0.057699] Initializing cgroup subsys cpuacct
[    0.057735] Initializing cgroup subsys memory
[    0.057768] Initializing cgroup subsys devices
[    0.057780] Initializing cgroup subsys freezer
[    0.057790] Initializing cgroup subsys blkio
[    0.057810] Initializing cgroup subsys perf_event
[    0.057879] CPU: Testing write buffer coherency: ok
[    0.058737] devtmpfs: initialized
[    0.077855] omap_hwmod: gfx: failed to hardreset
[    0.093966] omap_hwmod: pruss: failed to hardreset
[    0.094414] print_constraints: dummy:
[    0.094623] NET: Registered protocol family 16
[    0.095547] OMAP GPIO hardware version 0.1
[    0.096450] omap_mux_init: Add partition: #1: core, flags: 0
[    0.097653]  omap_i2c.1: alias fck already exists
[    0.097955] hw-breakpoint: debug architecture 0x4 unsupported.
[    0.098092]  omap2_mcspi.1: alias fck already exists
[    0.098194]  omap2_mcspi.2: alias fck already exists
[    0.098325]  edma.0: alias fck already exists
[    0.098344]  edma.0: alias fck already exists
[    0.098361]  edma.0: alias fck already exists
[    0.098429] cape: pcm register
[    0.105524] bio: create slab <bio-0> at 0
[    0.106469] SCSI subsystem initialized
[    0.107185] usbcore: registered new interface driver usbfs
[    0.107345] usbcore: registered new interface driver hub
[    0.107486] usbcore: registered new device driver usb
[    0.107599] musb-ti81xx musb-ti81xx: musb0, board_mode=0x13, plat_mode=0x3
[    0.107719] musb-ti81xx musb-ti81xx: musb1, board_mode=0x13, plat_mode=0x1
[    0.108106] omap_i2c omap_i2c.1: bus 1 rev2.4.0 at 100 kHz
[    0.108993] Advanced Linux Sound Architecture Driver Version 1.0.24.
[    0.109458] Switching to clocksource gp timer
[    0.118494] musb-hdrc: version 6.0, ?dma?, otg (peripheral+host)
[    0.118650] musb-hdrc musb-hdrc.0: dma type: pio
[    0.118800] MUSB0 controller's USBSS revision = 4ea20800
[    0.118830] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
[    0.118848] musb-hdrc: MHDRC RTL version 2.0
[    0.118859] musb-hdrc: setup fifo_mode 4
[    0.118887] musb-hdrc: 28/31 max ep, 16384/16384 memory
[    0.119177] musb-hdrc musb-hdrc.0: USB OTG mode controller at d081c000 using PIO, IRQ 18
[    0.119424] musb-hdrc musb-hdrc.1: dma type: pio
[    0.119600] MUSB1 controller's USBSS revision = 4ea20800
[    0.119626] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
[    0.119643] musb-hdrc: MHDRC RTL version 2.0
[    0.119653] musb-hdrc: setup fifo_mode 4
[    0.119679] musb-hdrc: 28/31 max ep, 16384/16384 memory
[    0.119708] musb-hdrc musb-hdrc.1: MUSB HDRC host driver
[    0.119776] musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 1
[    0.119889] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    0.119904] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.119918] usb usb1: Product: MUSB HDRC host driver
[    0.119929] usb usb1: Manufacturer: Linux 3.2.18 musb-hcd
[    0.119940] usb usb1: SerialNumber: musb-hdrc.1
[    0.120492] hub 1-0:1.0: USB hub found
[    0.120516] hub 1-0:1.0: 1 port detected
[    0.120888] musb-hdrc musb-hdrc.1: USB Host mode controller at d081e800 using PIO, IRQ 19
[    0.121245] NET: Registered protocol family 2
[    0.121428] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.121795] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[    0.121953] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
[    0.122047] TCP: Hash tables configured (established 8192 bind 8192)
[    0.122060] TCP reno registered
[    0.122080] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.122104] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.122325] NET: Registered protocol family 1
[    0.122610] RPC: Registered named UNIX socket transport module.
[    0.122623] RPC: Registered udp transport module.
[    0.122632] RPC: Registered tcp transport module.
[    0.122641] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.124137] audit: initializing netlink socket (disabled)
[    0.124185] type=2000 audit(0.110:1): initialized
[    0.134178] VFS: Disk quotas dquot_6.5.2
[    0.134240] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.135226] msgmni has been set to 495
[    0.136079] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[    0.136167] io scheduler noop registered
[    0.136179] io scheduler deadline registered
[    0.136232] io scheduler cfq registered (default)
[    0.137022] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    0.138166] omap_uart.0: ttyO0 at MMIO 0x44e09000 (irq = 72) is a OMAP UART0
[    0.138349] console [ttyO0] enabled
[    0.138760] omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
[    0.139091] omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
[    0.139412] omap_uart.3: ttyO3 at MMIO 0x481a6000 (irq = 44) is a OMAP UART3
[    0.139791] omap_uart.4: ttyO4 at MMIO 0x481a8000 (irq = 45) is a OMAP UART4
[    0.140148] omap_uart.5: ttyO5 at MMIO 0x481aa000 (irq = 46) is a OMAP UART5
[    0.141378] brd: module loaded
[    0.144552] loop: module loaded
[    0.144625] at24 1-0051: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
[    0.199501] No daughter card found
[    0.199549] at24 1-0050: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
[    0.207465] Board name: A335BONE
[    0.207475] Board version: 00A5
[    0.207483] The board is a AM335x Beaglebone.
[    0.208116] tps65217 1-0024: TPS65217 ID 0xf version 1.1
[    0.209878] print_constraints: DCDC1: 900 <--> 1800 mV at 1800 mV
[    0.211638] print_constraints: DCDC2: 900 <--> 3300 mV at 1275 mV
[    0.213365] print_constraints: DCDC3: 900 <--> 1500 mV at 1100 mV
[    0.215091] print_constraints: LDO1: 1000 <--> 3300 mV at 1800 mV
[    0.216834] print_constraints: LDO2: 900 <--> 3300 mV at 3300 mV
[    0.218566] print_constraints: LDO3: 1800 <--> 3300 mV at 3300 mV
[    0.220325] print_constraints: LDO4: 1800 <--> 3300 mV at 3300 mV
[    0.220817] Disabling OPP for 275MHz due to silicon errata
[    0.221126]  omap_i2c.3: alias fck already exists
[    0.221352] omap_i2c omap_i2c.3: bus 3 rev2.4.0 at 100 kHz
[    0.222039]  omap_hsmmc.0: alias fck already exists
[    0.224704] at24 3-0054: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
[    0.279501] BeagleBone cape EEPROM: could not read eeprom at address 0x54
[    0.279551] at24 3-0055: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
[    0.339499] BeagleBone cape EEPROM: could not read eeprom at address 0x55
[    0.339556] at24 3-0056: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
[    0.419498] BeagleBone cape EEPROM: could not read eeprom at address 0x56
[    0.419550] at24 3-0057: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
[    0.499498] BeagleBone cape EEPROM: could not read eeprom at address 0x57
[    0.499512] BeagleBone cape: exporting ADC pins to sysfs
[    0.499795] Beaglebone: initializing onboard LEDs
[    0.499966] BeagleBone cape: exporting SPI pins as spidev
[    0.500246] BeagleBone cape: initializing w1-gpio
[    0.500356] w1-gpio connected to P8_6
[    0.500892] SCSI Media Changer driver v0.25
[    0.501164] CAN device driver interface
[    0.501174] CAN bus driver for Bosch D_CAN controller 1.0
[    0.549509] davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
[    0.549526] davinci_mdio davinci_mdio.0: detected phy mask fffffffe
[    0.550426] davinci_mdio.0: probed
[    0.550444] davinci_mdio davinci_mdio.0: phy[0]: device 0:00, driver SMSC LAN8710/LAN8720
[    0.550629] usbcore: registered new interface driver cdc_acm
[    0.550640] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[    0.550717] usbcore: registered new interface driver usblp
[    0.550784] usbcore: registered new interface driver cdc_wdm
[    0.550845] usbcore: registered new interface driver uas
[    0.550855] Initializing USB Mass Storage driver...
[    0.550963] usbcore: registered new interface driver usb-storage
[    0.550973] USB Mass Storage support registered.
[    0.551060] usbcore: registered new interface driver libusual
[    0.551439] mousedev: PS/2 mouse device common for all mice
[    0.551916] dev addr = cf9cf808
[    0.551927] pdev addr = cf9cf800
[    0.552560] omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc0
[    0.552696] i2c /dev entries driver
[    0.553048] Linux media interface: v0.10
[    0.553115] Linux video capture interface: v2.00
[    0.553152] Driver for 1-wire Dallas network protocol.
[    0.554261] OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
[    0.555632] cpuidle: using governor ladder
[    0.555777] cpuidle: using governor menu
[    0.557574] Registered led device: beaglebone::usr0
[    0.557670] Registered led device: beaglebone::usr1
[    0.557763] Registered led device: beaglebone::usr2
[    0.557857] Registered led device: beaglebone::usr3
[    0.558203] usbcore: registered new interface driver usbhid
[    0.558214] usbhid: USB HID core driver
[    0.559031] usbcore: registered new interface driver snd-usb-audio
[    0.559868] ALSA device list:
[    0.559878]   No soundcards found.
[    0.560211] TCP cubic registered
[    0.560222] Initializing XFRM netlink socket
[    0.560255] NET: Registered protocol family 17
[    0.560309] NET: Registered protocol family 15
[    0.560319] can: controller area network core (rev 20090105 abi 8)
[    0.560408] NET: Registered protocol family 29
[    0.560421] can: raw protocol (rev 20090105)
[    0.560462] Registering the dns_resolver key type
[    0.560512] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
[    0.560533] ThumbEE CPU extension supported.
[    0.560607] mux: Failed to setup hwmod io irq -22
[    0.561268] Power Management for AM33XX family
[    0.561441] Trying to load am335x-pm-firmware.bin (60 secs timeout)
[    0.561563] Copied the M3 firmware to UMEM
[    0.565754] registered taskstats version 1
[    0.566035] Detected MACID=50:56:63:c8:2a:43
[    0.566898] omap_rtc omap_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
[    0.567583] Waiting for root device /dev/mmcblk0p2...
[    0.589551] usb 1-1: new high-speed USB device number 2 using musb-hdrc
[    0.630492] mmc0: host does not support reading read-only switch. assuming write-enable.
[    0.632430] mmc0: new high speed SDHC card at address 1234
[    0.632898] mmcblk0: mmc0:1234 SA04G 3.63 GiB
[    0.634852]  mmcblk0: p1 p2
[    0.673185] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem
[    0.673203] EXT4-fs (mmcblk0p2): write access will be enabled during recovery
[    0.730942] usb 1-1: New USB device found, idVendor=0bda, idProduct=8176
[    0.730962] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    0.730975] usb 1-1: Product: 802.11n WLAN Adapter
[    0.730986] usb 1-1: Manufacturer: 802.11n WLPN Adapter
[    0.730997] usb 1-1: SerialNumber: 00e04c000001
[    9.207202] EXT4-fs (mmcblk0p2): recovery complete
[    9.897689] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    9.897754] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[    9.898860] devtmpfs: mounted
[    9.899179] Freeing init memory: 216K
[   10.271894] NET: Registered protocol family 10
[   10.799811] udevd[58]: starting version 182
[   10.838018] Bluetooth: Core ver 2.16
[   10.838116] NET: Registered protocol family 31
[   10.838128] Bluetooth: HCI device and connection manager initialized
[   10.838145] Bluetooth: HCI socket layer initialized
[   10.838156] Bluetooth: L2CAP socket layer initialized
[   10.838181] Bluetooth: SCO socket layer initialized
[   10.862100] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[   10.947820] NET: Registered protocol family 23
[   10.964508] IrCOMM protocol (Dag Brattli)
[   11.025506] Bluetooth: RFCOMM TTY layer initialized
[   11.025539] Bluetooth: RFCOMM socket layer initialized
[   11.025550] Bluetooth: RFCOMM ver 1.11
[   11.209649] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[   11.839423]  gadget: Mass Storage Function, version: 2009/09/11
[   11.839444]  gadget: Number of LUNs=1
[   11.839462]  lun0: LUN: removable file: /dev/mmcblk0p1
[   11.839580]  gadget: Mass Storage Gadget, version: 2009/09/11
[   11.839600]  gadget: userspace failed to provide iSerialNumber
[   11.839633]  gadget: g_mass_storage ready
[   11.839661] musb-hdrc musb-hdrc.0: MUSB HDRC host driver
[   11.839706] musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 2
[   11.839819] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[   11.839835] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   11.839849] usb usb2: Product: MUSB HDRC host driver
[   11.839860] usb usb2: Manufacturer: Linux 3.2.18 musb-hcd
[   11.839871] usb usb2: SerialNumber: musb-hdrc.0
[   11.840598] hub 2-0:1.0: USB hub found
[   11.840623] hub 2-0:1.0: 1 port detected
[   12.553410] ip_tables: (C) 2000-2006 Netfilter Core Team
[   13.601232] cfg80211: Calling CRDA to update world regulatory domain
[   13.639563]
[   13.639571] CPSW phy found : id is : 0x7c0f1
[   13.640348] PHY 0:01 not found
[   13.655525] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   16.640111] PHY: 0:00 - Link is Up - 100/Full
[   16.640302] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   27.599503] eth0: no IPv6 routers present

Does this mean the beaglebone does not detect the wifi adaptor?

I get the same results as Fatbits when I check the wifi adaptor on Ubuntu and Windows.
Ubuntu 12.04: Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN
Windows 7: Realtek RTL8188CU Wireless LAN 802.11n USB 2.0 Network Adapter

Also, the wifi adaptor's LED lights up when plugged into my computer, but it almost never lights up on my beaglebone. I am using a 5V 2000mA power supply from adafruit as well.

I may be stating the obvious, but the under technical details of wifi adaptor in the adafruit store it says its a "RTl8192cu Chipset".
Were we shippped the wrong chipset by mistake?
epexegeses
 
Posts: 1
Joined: Thu Jun 21, 2012 11:56 am

Re: Beagle Wifi Adapter

by LeZappy on Fri Jul 06, 2012 6:23 pm

I can also confirm that my Adafruit beaglebone wifi adapter (purchased on June 21st) is an RTL8188CU adapter. From windows:

Image

However, while I was able to get mine to work with the Angstrom "Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.05-beaglebone-2012.06.18.img.xz" distribution (I had to adjust /etc/wpa_supplicant.conf), it's unreliable:

  • The adapter doesn't always associate with the access point at bootup. Nothing will make the adapter associate, except by rebooting.

  • It'll typically stop working after some time, ranging from a few seconds to hours (the longest was around 5 1/2 hours). It generally dies within a few minutes, though. There's nothing in dmesg, and ifconfig and iwconfig look fine (an IP address is still assigned, and the adapter still appears to be associated). However, bringing the interface down results in an "interface not configured" error. Trying to bring the interface up fails (iwconfig still shows association, but ifconfig now shows an unconfigured interface). Nothing will make the adapter work again, except by rebooting.
I'll try finding another (different) adapter to test.

Edit: Yes, I am using the external 2A power supply.
LeZappy
 
Posts: 5
Joined: Wed Mar 16, 2011 3:56 am

Re: Beagle Wifi Adapter

by LeZappy on Sat Jul 07, 2012 2:59 am

When the adapter doesn't associate at bootup, there is sometimes (but not always) crud in dmesg -- basically, the adapter associates and then disconnects:

Code: Select all | TOGGLE FULL SIZE
[    9.258789] usbcore: registered new interface driver rtl8192cu
[    9.314300] rtl8192cu: MAC auto ON okay!
[    9.336456] rtl8192cu: Tx queue select: 0x05
[    9.337860] rtl8192c_common: Loading firmware file rtlwifi/rtl8192cufw.bin
[   10.002990] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   15.314392] wlan0: authenticate with 11:22:33:44:55:66 (try 1)
[   15.391204] wlan0: authenticated
[   15.392517] wlan0: associate with 11:22:33:44:55:66 (try 1)
[   15.582885] wlan0: associate with 11:22:33:44:55:66 (try 2)
[   15.658447] wlan0: RX AssocResp from 11:22:33:44:55:66 (capab=0x411 status=0 aid=3)
[   15.658447] wlan0: associated
[   15.675140] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   25.695892] wlan0: disassociating from 11:22:33:44:55:66 by local choice (reason=3)
[   25.711212] cfg80211: Calling CRDA for country: US
[   25.724182] wlan0: deauthenticating from 11:22:33:44:55:66 by local choice (reason=3)
[   26.402740] wlan0: no IPv6 routers present
[   26.531066] wlan0: authenticate with 11:22:33:44:55:66 (try 1)
[   26.722778] wlan0: authenticate with 11:22:33:44:55:66 (try 2)
[   26.922760] wlan0: authenticate with 11:22:33:44:55:66 (try 3)
[   27.122772] wlan0: authentication with 11:22:33:44:55:66 timed out

Likely a software issue, but I'm still digging.

Edit: also, after a while, this gets spewed into dmesg:

Code: Select all | TOGGLE FULL SIZE
[  240.132812] INFO: task kworker/0:1:20 blocked for more than 120 seconds.
[  240.139801] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  360.142791] INFO: task kworker/0:1:20 blocked for more than 120 seconds.
[  360.149780] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  480.152801] INFO: task kworker/0:1:20 blocked for more than 120 seconds.
[  480.159820] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  480.168060] INFO: task wpa_supplicant:183 blocked for more than 120 seconds.
[  480.175415] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  600.182800] INFO: task kworker/0:1:20 blocked for more than 120 seconds.
[  600.189819] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  600.198059] INFO: task wpa_supplicant:183 blocked for more than 120 seconds.
[  600.205444] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  720.212799] INFO: task kworker/0:1:20 blocked for more than 120 seconds.
[  720.219818] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  720.228088] INFO: task wpa_supplicant:183 blocked for more than 120 seconds.
[  720.235473] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

At this point, ifconfig will hang if run, and rebooting via "reboot" will also hang. Time to hit reset.
LeZappy
 
Posts: 5
Joined: Wed Mar 16, 2011 3:56 am

Re: Beagle Wifi Adapter

by eradicatore on Sat Jul 07, 2012 8:27 am

Hi, I just ordered a wifi adapter as well, and it looks like I'm in the exact same situation as you. Note that if you plug in the adapter AFTER bootup, you can more easily see what messages are related to the wifi adapter I think in dmesg. Here is what I get:

Code: Select all | TOGGLE FULL SIZE
[  207.619504] usb 1-1: new high-speed USB device number 2 using musb-hdrc
[  207.760793] usb 1-1: New USB device found, idVendor=0bda, idProduct=8176
[  207.760812] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  207.760826] usb 1-1: Product: 802.11n WLAN Adapter
[  207.760837] usb 1-1: Manufacturer: Realtek
[  207.760847] usb 1-1: SerialNumber: 00e04c000001
[  207.819746] cfg80211: Calling CRDA to update world regulatory domain
[  207.947932] rtl8192cu: MAC address: XX:XX:XX:XX:XX:XX
[  207.947965] rtl8192cu: Board Type 0
[  207.958249] rtlwifi: rx_max_size 15360, rx_urb_num 8, in_ep 1
[  207.976886] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
[  207.977877] usbcore: registered new interface driver rtl8192cu



Note that when I first got this dongle, it did light up the led when plugged into beaglebone during the initial few hours of me trying to get this all to work. For some reason lately though it no longer lights up the dongle led when I plug it in to the beaglebone. It will light up and blink the dongle LED when I plug into my windows 7 machine, so something odd is up.

I did compile and install the latest version of connman (1.2) since I'm using the 6/18 beagle bone angstrom distro and it comes intalled with 0.79 which as someone pointed out seems to have removed the "Passphrase" connman service field?? I'm very confused by this, since the connman release notes don't mention what took it's place.

Anyway, I'm still stuck, and one thing I would like to be able to do is to "test" out this wifi setup without having to remove ethernet every time I want to see if my config is correct. As someone noted on this board other places (and also in the tutorial now) you can't have both wifi and ethernet connected. But for me without ethernet I lose my login and ability to debug through ssh. Anyone know how to use the connman test tools to just verify the config?
eradicatore
 
Posts: 2
Joined: Wed Sep 08, 2010 8:54 am

Re: Beagle Wifi Adapter

by LeZappy on Sat Jul 07, 2012 10:41 pm

eradicatore wrote:Note that when I first got this dongle, it did light up the led when plugged into beaglebone during the initial few hours of me trying to get this all to work. For some reason lately though it no longer lights up the dongle led when I plug it in to the beaglebone. It will light up and blink the dongle LED when I plug into my windows 7 machine, so something odd is up.

Yeah, I'm seeing all sorts of weird intermittent issues. Right now, I can only get the adapter to work after cycling power -- a reset or reboot no longer works (I'm no longer sure if it ever did). Sometimes, I even have to do a reboot or two after cycling power before it'll work. This is starting to smell like an uninitialized variable somewhere, or perhaps an incomplete initialization.

I'm still using the default but ancient connman 0.79. I should try 1.2 to see if that's any better.

For debugging, you can still use the USB serial console, which is what I use. However, you've got to be careful, as the wifi driver appears to occasionally cause some commands (like ifconfig and iwconfig) to hang such that neither job control nor SIGINT work (also, once these commands start to hang, the reboot command will also hang). Fortunately, you can kill these hung commands via -9, but that requires a shell prompt; using something like screen(1) is recommended.
LeZappy
 
Posts: 5
Joined: Wed Mar 16, 2011 3:56 am

Re: Beagle Wifi Adapter

by tgalonso on Sun Jul 08, 2012 10:34 am

I am in the same boat. Has anybody tried to use the latest angstrom release with any success?
tgalonso
tgalonso
 
Posts: 18
Joined: Thu Jun 21, 2012 11:45 am

Re: Beagle Wifi Adapter

by FatBits on Mon Jul 09, 2012 7:53 pm

I haven't had a chance to try it with the BeagleBone yet, but my "RTL8192CU" adapter from Amazon showed up and it too identifies as a RTL8188CU in Ubuntu. I'm beginning to wonder if it's even possible to get a real RTL8192CU adapter? In any case, I now have quite a handsome collection of WiFi adapters. I was lucky enough to get my hands on one of the as yet unreleased Arduino WiFi shields, so for now I will go back to Arduino with my tail between my legs. And may give the BeagleBone another try in a week or two when I have more time. Will keep my eye on this thread for any progress made by others. Please share if you make progress / find a solution. Thanks all!
FatBits
 
Posts: 4
Joined: Sat Aug 06, 2011 9:15 am

Re: Beagle Wifi Adapter

by LeZappy on Tue Jul 10, 2012 5:34 am

Argh, my "rtl8192cu" adapter from Amazon also identifies as rtl8188cu. Foo. The beagleboard recognizes it, but I can't get it to work.

However, I can get the Adafruit adapter to work, if only for a moment. I've tried both the original Angstrom distribution that shipped with the beagleboard, and the latest version -- both work intermittently. :( I, too, am going to take a break, and perhaps get back to it on the weekend.
LeZappy
 
Posts: 5
Joined: Wed Mar 16, 2011 3:56 am

Re: Beagle Wifi Adapter

by tgalonso on Wed Jul 11, 2012 10:02 am

@Adafruit which version of Angstrom where you running when you did the wifi tutorial?
tgalonso
 
Posts: 18
Joined: Thu Jun 21, 2012 11:45 am

Re: Beagle Wifi Adapter

by mennochio on Wed Jul 11, 2012 3:26 pm

Over the 6 weeks I have had my WiFi adapter I have had the same problems described by others. It was recognized the first time I plugged it in and the led illuminated. Since then it rarely gets recognized and the led never illuminates. For the last month or so I have been using it on my Windows 7 64 bit laptop and it has performed flawlessly. The led is continuously illuminated and, in fact, it maintains lock with my router even better than the device built into my laptop. As others have said, it shows up in Device Mgr as an RTL8188CU.

Here is the interesting thing: In reviewing the DMESG listing I captured when the device was plugged into my BeagleBoard I noticed that it was reported as an rtl8192cu (!). I know it is the same device that Windows reports as an RTL8188CU by comparing the MAC ID, which I assume is hardwired into the device itself. So it seems the question of which chipset is in the adapter may be even more complicated than meets the eye.

The adapter works so well in my laptop that I have just left it there. :)

mennochio
 
Posts: 7
Joined: Sat Apr 14, 2012 3:14 pm

Re: Beagle Wifi Adapter

by mennochio on Thu Jul 12, 2012 5:11 pm

I just noticed that I said "BeagleBoard" in my post yesterday. I meant to say "BeagleBone". :oops:

mennochio
 
Posts: 7
Joined: Sat Apr 14, 2012 3:14 pm

Re: Beagle Wifi Adapter

by middleton on Thu Jul 12, 2012 11:05 pm

I am having the same issue. Just got my Beaglebone a week ago and tried the adapter tonight. I installed the drives in the tutorial but no luck. Mine was not even recognized the first time I plugged it in. Not sure what to do next. Maybe try Debian on the Beaglebone. Or I can always try it in the RPI. I get mine tomorrow!
middleton
 
Posts: 5
Joined: Thu Jul 12, 2012 9:43 pm

Re: Beagle Wifi Adapter

by tgalonso on Tue Jul 17, 2012 10:19 pm

Has anybody tried to use Conman 1.2? Did it work?
Tgalonso
tgalonso
 
Posts: 18
Joined: Thu Jun 21, 2012 11:45 am

Re: Beagle Wifi Adapter

by dougkirk on Fri Jul 20, 2012 12:56 am

This post https://plus.google.com/105557068601771362265/posts/93rBVxskh9G helped a lot.

Particularly the part about running 'opkg upgrade'. I made a tmp directory under /home/root, and then 'opkg -t /home/root/tmp upgrade' to upgrade the software on the bone. Then you can delete the tmp directory. I found that without using a specified tmp path it would fill up /tmp and crash the upgrade.

After I did that, and of course removed the ethernet cable from it and reboot (with the Wifi adapter in), it just worked. (I'd already done the install of the firmware and the configuration step).
dougkirk
 
Posts: 2
Joined: Tue Jul 20, 2010 9:08 am

Re: Beagle Wifi Adapter

by engineerbynight on Fri Jul 20, 2012 7:49 am

I'm having the same troubles as everyone else... my screen after "dmesg" doesn't look like what it should (according to tutorial), and the "ifconfig wlan0" command doesn't report anything promising.

I do have the recommended AC adapter plugged in while doing this.

I also have the same results when plugging it into windows machine: RTL8188CU.

Has anyone figure anything out with this?
engineerbynight
 
Posts: 4
Joined: Thu Jul 19, 2012 9:48 am