On Mon, 31 May 2021 08:09:54 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user Patrick Bolton
<[email protected]> wrote:
>I am having problems with wifi dongles with the pocketbeagle.
You've pasted a novel of logs, but nowhere do you state exactly what
"problems" means?
>
>I have two dongles:
>1) Edimax EW-7811Un:
>EDIMAX - Wireless Adapters - N150 - N150 Wi-Fi Nano USB Adapter, Ideal for
>Raspberry Pi
><https://www.edimax.com/edimax/merchandise/merchandise_detail/data/edimax/global/wireless_adapters_n150/ew-7811un/>
>
>2) tp-link TL-WN725N V3
>TL-WN725N | 150Mbps Wireless N Nano USB Adapter | TP-Link
><https://www.tp-link.com/us/home-networking/usb-adapter/tl-wn725n/>
Have you read
https://static.tp-link.com/2018/201812/20181207/Installation%20Guide%20for%20Linux.pdf
(Granted, the OS/kernel specified in the R-Pi section is antique, but the
rest /might/ apply).
>
>I have tried them in two configurations:
>1) I cut a usb-a female cable and wired it to the PB in accordance with:
>https://i1.wp.com/www.teachmemicro.com/wp-content/uploads/2018/03/pocketbeagle-usb-type-a.jpg?w=590&ssl=1
>2) 2-port usb hub from tindie
>2/4-port USB 2.0 HUB Cape for PocketBeagle from microwavemont on Tindie
><https://www.tindie.com/products/microwavemont/24-port-usb-20-hub-cape-for-pocketbeagle/>
>
>Voltage Readings
>Pin Function USB Power 5V 0.8A HUB 5V
>8A power supply
How are you powering the Beagle and hub? Note that USB 2.0 standard is
that only 0.5A is available (and often needs a powered hub to get that). If
the beagle is being powered from a USB connection, you will have much less
current available for any devices connected to it, as the Beagle itself
requires some fraction of the available power (it's why Beagle Bone Black
is recommended to use a barrel connector rather than USB when flashing the
eMMC). A 5V 8A supply is not doing much unless you've wired directly to the
hub 5V source (or P1-1
Since the WiFi adapter runs a micro-radio, you likely need a higher
current just for it, so powering from the USB into the Beagle may not be
viable. I know R-Pi boards with WiFi operate off a USB connection, but that
is not a data connection -- just a specialized power mode which modern hubs
can recognize and provide a touch more current.
>Image:
>https://debian.beagleboard.org/images/bone-debian-10.3-iot-armhf-2020-04-06-4gb.img.xz
>2) apt update
>3) apt upgrade
>4) init 6
Pardon, but why the "init 6" (especially as Debian has adopted the
systemd start up, deprecating "init" mode).
>2) tp-link driver update
>Download for TL-WN725N | TP-Link
><https://www.tp-link.com/us/support/download/tl-wn725n/>
>
Okay -- you've probably read the referenced PDF then, as the downloads
are source needing to be compiled. But I note
"4. This is a beta version; unknown bugs may still exist. The formal
version is coming soon."
and that was three years ago... Only the Mac version has seen updates newer
than the Linux beta. The beta is also only "tested" up to kernel 4.4.3, and
recent Beagle images are on what, 4.19.x
https://wiki.debian.org/WiFi (possibly a bit dated)
"""
Currently there are only a few modern wifi chipsets readily available that
work with free software systems. For USB wifi devices this list includes
the Realtek RTL8187B chipset (802.11G) and the Atheros AR9170 chipset
(802.11N). For Mini PCIe all cards with an Atheros chipset are supported.
"""
"""
Edimax EW-7811Un
USB adapter
1 (9,[nPP],[B]), 1 (NOOBS,2015,[B]), 1 (2013,[B]), 1 (2016,[B]), 1 (2014),
1 (ARMv6,[B])
For a guide see multiple in the Amazon reviews. There seems to be a problem
with this dongle's range.
"""
"""
Device
Confirmed
Drawbacks/Comments
Guide
TP-Link TL WN821N
(./)
- The original code of the driver is copyrighted and later contributors
don't know by whom.
The driver download does not contain license information.
(Most C files are licensed under GNU General Public License (GPL), version
2.)
- Only works when disabling random MAC addresses.
1. Update: sudo apt-get update && apt-get upgrade && && apt-get
dist-upgrade and reboot if you updated the kernel
2. Connect the device. lsusb should show 2357:0107
3. Install required packages: sudo apt-get install gcc-6 git
build-essential
4. Get the latest driver from ?GitHub and install it:
git clone https://github.com/jeremyb31/rtl8192eu-linux-driver.git
cd rtl8192eu-linux-driver
sudo make
sudo make install
5. Reboot and check that the kernel module is loaded by running: lsmod
6. Use your network-interface to connect to the WLAN. You could use the
pre-installed NetworkManager for that.
(7.) Edit NetworkManager.conf as root: sudo kate
/etc/NetworkManager/NetworkManager.conf
Append the following:
[device]
wifi.scan-rand-mac-address=no
Save and run: /etc/init.d/network-manager restart
"""
>root@beaglebone:/var/lib/cloud9# lsusb
>Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
You seem to have two hubs recognized... A BBB with a USB<>Ethernet
adapter shows
debian@beaglebone:~$ lsusb
Bus 001 Device 002: ID 0b95:7720 ASIX Electronics Corp. AX88772
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>[ 1.408301] musb-hdrc musb-hdrc.1: VBUS_ERROR in a_wait_vrise (81,
><SessEnd), retry #2, port1 00000104
>[ 1.560680] musb-hdrc musb-hdrc.1: VBUS_ERROR in a_wait_vrise (81,
><SessEnd), retry #3, port1 00000104
>[ 1.713116] musb-hdrc musb-hdrc.1: VBUS_ERROR in a_wait_vrise (80,
><SessEnd), retry #3, port1 0008010c
Those might be of concern. Some error in the bus voltage level? You
reported 0V? But if you were jumpered to the 5V supply (next pin over), you
should not be seeing 0V at all. Recheck your cable -- do you have
continuity between those pins (with the cable off the Beagle)?
>[ 54.973221] pvrsrvkm: loading out-of-tree module taints kernel.
>[ 55.299383] [drm] Initialized pvr 1.17.4948957 20110701 for 56000000.sgx
>on minor 0
Doesn't show on my BBB
My USB<>Ethernet adapter resulted in the following added lines.
[ 73.127404] asix 1-1:1.0 eth1: register 'asix' at usb-musb-hdrc.1-1,
ASIX AX88772 USB 2.0 Ethernet, 00:50:b6:5c:90:84
[ 73.132673] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 73.140009] usbcore: registered new interface driver asix
[ 74.799226] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[ 74.810926] asix 1-1:1.0 eth1: link up, 100Mbps, full-duplex, lpa 0xCDE1
[ 142.980128] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 147.594945] usb 1-1: USB disconnect, device number 2
[ 147.595336] asix 1-1:1.0 eth1: unregister 'asix' usb-musb-hdrc.1-1, ASIX
AX88772 USB 2.0 Ethernet
--
Dennis L Bieber
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/hp1abgpigk1a7c5jckl7nooa1nsq652a9u%404ax.com.
