I don’t seem to get decent speed on the beagleplay ethernet and wifi
I used speedtest-cli to test the speed
For ethernet I get at best around 220M
On Debian 11 I get 630.47 M with speedtest-cli and 930M with xfinity test online
On the beagleplay firefox is so darn slow that the online speedtest stalls.
Firefox on the beagleplay is basically useless, is there a way to fix that?
On wifi I rarely get better than 60M, more in the range of 20-40M
If I have wifi and ethernet connected I can’t ssh on either one, sometimes I can ssh on one of them but not the other.
michel@michel:~$ ssh debian@10.0.0.226
kex_exchange_identification: read: Connection reset by peer
Connection reset by 10.0.0.226 port 22
What is SoftAp0 for ? It is not accessible from within the local network
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.0.0.165 netmask 255.255.255.0 broadcast 10.0.0.255
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.0.0.226 netmask 255.255.255.0 broadcast 10.0.0.255
Michel Catudal
Remove the snap version and install the ESR addition.
I have not spent much time on the factory image, so this is what is an issue on a metal box machine and other arm SBC.
They are pretty rude and decide to update and what ever else in the background. Also make sure you have all the “fine print” stuff unchecked. Don’t take this the wrong way, telemetry and snap is fine if you have a very light workload on an metal box machine these arm boards with limited resources are choked down.
Not sure how you are set up, when you speed test use an internet modem that is not connected to the internet and go box to box with both using that modem with nothing else connected. Since you are having trouble use the same model modem that you are using live.
That is the only way you will get useful data. Not sure if you are using the right speed test software, the one we use, cannot recall exactly but seem to believe it was inet or something close.
I am kind of new at Debian. In the past I’ve used Yocto, Archlinux, Gentoo and Funtoo. Lately I’ve been using more Gentoo than Funtoo because they dropped 32 bit support.
Tonight I tried to install the TI SDK for am62x and it complained that it only support Ubuntu 18.04 which I have no intention of installing. I may have to use docker if yocto doesn’t work on Debian 11. I thought that since Ubuntu is a modified debian that I should be able to run the TI Yoctos without having to use docker.
I want to use this board mostly as a CAN board. I designed a little board that has a driver for the on board CAN and a second CAN with a MCP2517FD. I managed to get a few MCP2517FD which are being obsoleted by Microchip for the MCP2518FD but you can’t get them unless you are a big company. It is just an upgrade, it is supposed to use less current. I may use the board to communicate with a BeagleFreedom at some time in the future.
I didn’t think about snap, usually I install on computers for my brothers and my wife because that gives me less work for maintenance but that ain’t for me. On all the installations snap is the first thing I remove. I think that it is a moronic approach, we stay out of windows because it is too bloated and then why duplicate this nonsense on Linux!!!
Once I have my design done it will have to communicate with the PC. Since I am no longer tied with a non compete clause I could sell my CAN boards. Similar boards are way overpriced so I see an opportunity. Usually the connection is thru USB. I am looking for a connection thru wifi.
I figured out that SoftAp0 stuff is basically a wifi server.
I will likely use Poky or a stripped down Arago. TI put too much crap in their yocto.
It will be a lot faster than xorg which seems awful slow, it doesn’t seem to support the EGL from TI, am I right on that?
On the TI website they say that you have to use version 4 to get xorg support, that is 2015-2016 stuff. J1939 support is only working correctly with Kernel 5.1x and greater.
My modem connection is fast, close to 1G, I am not sure why the connection is much slower with that board. It won’t matter that much for what I want to use the board.
Michel Catudal
Are you referring to the TI/Yocto build, if that is the case I can provide you with the list of dependencies that will let you build on 20.04. They have some old 32 bit stuff that will obviously break if you need it for BBB.
The standard SDK installs on 22.04 and so does CCS. My workstation has an Nvidia A2000 and that is only stable on Ubuntu 22.04 so 20.04 and 18 were not an option. Been running the AM62 EVM board and not having problems on 22.04.
Yes, that is perfect solution for end users that are not doing what we do.
That is what I found out too, TI made a gigantic mess trying to make everyone wear a size 12 shoe.
Do have a dedicated build server on Ubuntu 20.04 running kirkstone LTS, it would not work on a 22.04 server so had to go backwards. My problem is getting up to speed on both CCS and Yocto at about the same time. Tons of stale docs and sifting out current content is adding to the delay.
Found a couple sources for AM62X based boards so I feel strongly this is a good direction to be heading. Worth spending the time on getting up to speed on it.
Myself, I would look at PCAP data and know for fact what is going on with that. Make sure no one on your network is using Tor or any “server less” network like LimeWire and Skype. They will turn your fast internet connection in a dripping faucet when they sponge your bandwidth for an exit node or relay.
| foxsquirrel
April 10 |
MichelC:
Tonight I tried to install the TI SDK for am62x and it complained that it only support Ubuntu 18.04
Are you referring to the TI/Yocto build, if that is the case I can provide you with the list of dependencies that will let you build on 20.04. They have some old 32 bit stuff that will obviously break if you need it for BBB.
The standard SDK installs on 22.04 and so does CCS. My workstation has an Nvidia A2000 and that is only stable on Ubuntu 22.04 so 20.04 and 18 were not an option. Been running the AM62 EVM board and not having problems on 22.04.
I don’t have Ubuntu on my computer. I have funtoo, gentoo, arch linux and Debian 11.
Despite what TI says I think that it may compile on Debian 11.
Since it is not a very old yocto as the one I have at work that may not be a problem.
The issues I had before had to do with the 32 bit packages had to do with changes in Ubuntu 18.04. It only works on Ubuntu 16.04
If I have issues I will let you know if I don’t find a solution.
Myself, I would look at PCAP data and know for fact what is going on with that. Make sure no one on your network is using Tor or any “server less” network like LimeWire and Skype. They will turn your fast internet connection in a dripping faucet when they sponge your bandwidth for an exit node or relay.
This board is the only one I have speed issue with so far. I haven’t checked to see if I have the same issue with the Beaglebone AI-64
The annoying part on this board is that the second CAN is used as a SPI port so I have to add an extra device to get my second CAN
I uses a similar arm64 processor as RPI 3 A53
The beaglebone AI-64 is a bit more powerfull with the A73 and some DSP
I haven’t worked with DSP since 1983 when I did a voice recognition system for GM, I used a TMS32010 which was the first DSP TI made.
It has evolved a lot since. I used a DSP on my Beagleboard X15 but haven’t personnaly written any code for it.
The cellular phone I supported with it looked a lot different than today’s cellular phones.
1 Like
Try this and lets see what is running.
$ pstree
Here is one of our AI64’s
$ pstree
systemd─┬─4*[agetty]
├─apache2─┬─apache2
│ ├─apache2───18*[{apache2}]
│ └─4*[apache2───2*[{apache2}]]
├─avahi-daemon───avahi-daemon
├─containerd───8*[{containerd}]
├─cron
├─dbus-daemon
├─dockerd───9*[{dockerd}]
├─htcacheclean
├─mariadbd───7*[{mariadbd}]
├─node─┬─node───10*[{node}]
│ └─10*[{node}]
├─node-red───10*[{node-red}]
├─ntpd───{ntpd}
├─packagekitd───2*[{packagekitd}]
├─polkitd───2*[{polkitd}]
├─rsyslogd───3*[{rsyslogd}]
├─rtkit-daemon───2*[{rtkit-daemon}]
├─sshd─┬─sshd───sshd───bash───top
│ ├─sshd───sshd───bash
│ └─sshd───sshd───bash───pstree
├─systemd─┬─(sd-pam)
│ ├─dbus-daemon
│ ├─pipewire─┬─pipewire-media-───{pipewire-media-}
│ │ └─{pipewire}
│ └─pulseaudio───{pulseaudio}
├─systemd-journal
├─systemd-logind
├─systemd-network
├─systemd-resolve
├─systemd-udevd
├─unattended-upgr───{unattended-upgr}
└─wpa_supplicant
Also look at
$ top
and do this and look for duplicate network management tools/ not the same. Only need one running.
$ ps -e