On Thu, 14 Mar 2019 13:10:24 -0700 (PDT), Sardar Vayghannezgad
<sardar.svn@gmail.com> declaimed the
following:
However -- the following
Machinekit with Debian Stretch on the BeagleBone Black - Machine Koder
claims to be instructions for setting up MachineKit on Debian 9 Stretch --
starting from the recent standard (flashable) OS image.
I had come across the link you mentioned, and I knew it is more recent
than the one I have on BBB now, but I found many people referring to
debian-machinekit-8.7
<Beagleboard:BeagleBoneBlack Debian - eLinux.org; as
the latest, best, least-in-need-of-modification image out there, and so I
opted that.
For a pre-built system, that may be best, but since I'm not familiar
with what is in it, I can't say. The other link is designed to start with a
regular working up-to-date Debian and build MachineKit onto it -- and for
debugging your situation, it helps to start from a known working
configuration. That is: start with flashing (you'll have to follow the
instructions to turn that image into a flasher) that image -- then making
sure IT has full network connectivity. Preferably without using Internet
Connection Sharing -- your problems could be that ICS is not providing
gateway and name-server information to the BBB.
Typing hostnamectl, when no mSD card is inside the BBB, gives me :
machinekit@beaglebone:~$ hostnamectl
Static hostname: beaglebone
Icon name: computer
Machine ID: f4ee2c0f817c4a6e91d28c4d1c48a642
Boot ID: 928edadc13894c9e815ac34f9fffabc7
Operating System: Debian GNU/Linux 8 (jessie)
Kernel: Linux 3.8.13-xenomai-r83
Architecture: arm
I thought this already means I have flashed onto eMMC. Am I wrong?
It shows something, but there are multiple ways to get a changed kernel
without getting the rest...
By connecting, I meant pinging, actually. Isn't that connecting? Although I
cannot "browse" and, in layman's terms, see anything from the net on the
puTTY window (!), but it IS connected to give out such data:
machinekit@beaglebone:~$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=116 time=29.5 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=116 time=27.1 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=116 time=26.6 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=116 time=37.0 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=116 time=59.8 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=116 time=28.3 ms
And, yes, I'm doing this by commanding
This is direct IP# pinging of the Google provided name-server. But it
is not pinging "google.com" by name. As another response indicates, you may
not have a working name-server to translate names into IP#s
debian@beaglebone:~$ cat /etc/resolv.conf
# Generated by Connection Manager
search attlocal.net attlocal.net
nameserver 192.168.1.254
nameserver 2600:1700:e630:890::1
nameserver 2600:1700:e630:890::1
debian@beaglebone:~$
{Again, I am NOT using USB Internet Connection Sharing -- I have a CAT-5
cable directly connected to my router [well, technically, to an 8-port
switch that connects to the router]. Note that this file states it is
created during the connection}
sudo /sbin/route add default gw 192.168.7.1
I got this from here
<https://ofitselfso.com/BeagleNotes/HowToConnectBeagleboneBlackToTheInternetViaUSB.php>
and here
<https://www.digikey.com/en/maker/blogs/how-to-connect-a-beaglebone-black-to-the-internet-using-usb>
.
A proper system shouldn't need manual routing (and/or nameserver)
changes.
debian@beaglebone:~$ sudo /sbin/route
[sudo] password for debian:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
default dsldevice.attlo 0.0.0.0 UG 0 0 0
eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
eth0
dsldevice.attlo 0.0.0.0 255.255.255.255 UH 0 0 0
eth0
192.168.6.0 0.0.0.0 255.255.255.252 U 0 0 0
usb1
192.168.7.0 0.0.0.0 255.255.255.252 U 0 0 0
usb0
debian@beaglebone:~$
Even if not as a drive, shouldn't BBB be ever listed somewhere on my device
manager page. People out there have reported to have seen this, under
"ports" or "other devices" at least.
I'm using a stock Debian (the "latest image" page) which does create
that pseudo "drive"... Device manager shows I have:
Disk drives
Linux File-Stor Gadget USB Device
Network Adapters
Linux USB Ethernet/RNDIS Gadget
Portable devices
BEAGLEBONE
Ports
Gadget Serial (COM7) flagged as no driver installed warning
USB Serial Device (COM8)
{Just removed COM7 -- we'll see if it comes back in the future}
E.
What does the network info show? From Windows command line:
How can I check that? (I'm starting feeling like a time traveler from some
200 year ago! Is this something I should know?!!)
Yes -- you should know how to open a Windows command line -- or
PowerShell command line if you want to learn PowerShell <G>.
<right-click>Start\Run cmd
{though Win10 has it under
Start\Windows System\Command Prompt
I have a permanent short-cut for it, so it opens with my customized size
and font; the application is found in
%windir%\system32\cmd.exe
}
As I showed, on Windows, the command for network stuff is ipconfig, not
ifconfig.
did you do a
sudo apt-get update
Even doing so, gives :
machinekit@beaglebone:~$ sudo apt-get update
Err http://deb.machinekit.io jessie InRelease
Err http://security.debian.org jessie/updates InRelease
Which reinforces the concept that you do not have either a valid
name-server, or you do not have full network connectivity.
W: Failed to fetch http://deb.machinekit.io/debian/dists/jessie/Release.gpg
Could not resolve 'deb.machinekit.io'
And that indicates name-server problems
This, I hope, already means a step forward.