problem installing packages with apt-get

Hi, I have just downloaded bone-debian-8.8-machinekit-armhf-2017-05-21-4gb.img.xz and put it on an SD card. into a BBB.
After getting the network set up I wanted to load some packages. I tried to load emacs with:
sudo apt-get install emacs

but it doesn’t know that package. It seems the repos are not set up, so I tried to do :

sudo apt-get update

and get a lot of error messages :
Err http://deb.debian.org jessie InRelease

Err http://deb.debian.org jessie-updates InRelease

Err http://deb.debian.org jessie/updates InRelease

Err http://deb.machinekit.io jessie InRelease

Err http://repos.rcn-ee.com jessie InRelease

Err http://deb.debian.org jessie Release.gpg
Unable to connect to deb.debian.org:http:
Err http://deb.debian.org jessie-updates Release.gpg
Unable to connect to deb.debian.org:http:
Err http://deb.machinekit.io jessie Release.gpg
Unable to connect to deb.machinekit.io:http:
Err http://repos.rcn-ee.com jessie Release.gpg
Unable to connect to repos.rcn-ee.com:http:
Err http://deb.debian.org jessie/updates Release.gpg
Unable to connect to deb.debian.org:http:
Reading package lists… Done
W: Failed to fetch http://deb.debian.org/debian/dists/jessie/InRelease

W: Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/InRelease

W: Failed to fetch http://deb.debian.org/debian-security/dists/jessie/updates/InRelease

W: Failed to fetch http://deb.machinekit.io/debian/dists/jessie/InRelease

W: Failed to fetch http://repos.rcn-ee.com/debian/dists/jessie/InRelease

W: Failed to fetch http://deb.debian.org/debian/dists/jessie/Release.gpg Unable to connect to deb.debian.org:http:

W: Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/Release.gpg Unable to connect to deb.debian.org:http:

W: Failed to fetch http://deb.debian.org/debian-security/dists/jessie/updates/Release.gpg Unable to connect to deb.debian.org:http:

W: Failed to fetch http://deb.machinekit.io/debian/dists/jessie/Release.gpg Unable to connect to deb.machinekit.io:http:

W: Failed to fetch http://repos.rcn-ee.com/debian/dists/jessie/Release.gpg Unable to connect to repos.rcn-ee.com:http:

Either a really crappy network connection, or maybe something wrong
with the phy?

dmesg | grep phy
dmesg | grep mdio

Regards,

[ 0.000000] Booting Linux on physical CPU 0x0
[ 2.207846] davinci_mdio 4a101000.mdio: detected phy mask fffffffe
[ 2.208305] davinci_mdio: dt: updated phy_id[0] from phy_mask[fffffffe]
[ 2.217055] libphy: 4a101000.mdio: probed
[ 2.217092] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720
[ 2.224728] 47401300.usb-phy supply vcc not found, using dummy regulator
[ 2.229883] 47401b00.usb-phy supply vcc not found, using dummy regulator
[ 19.014748] net eth0: phy found : id is : 0x7c0f1

and :
[ 2.207818] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6
[ 2.207846] davinci_mdio 4a101000.mdio: detected phy mask fffffffe
[ 2.208305] davinci_mdio: dt: updated phy_id[0] from phy_mask[fffffffe]
[ 2.217055] libphy: 4a101000.mdio: probed
[ 2.217092] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720

I’ve been logged into the system over the ethernet with ssh -X for an hour, no problems.
One thing, I disabled connman with this command :
apt remove connman

so that I could set up static IP address and it would leave it alone.

Still trying to see if it is something I did wrong…

Thanks very much,

Jon

Your network is down on the BBB then..

https://wiki.debian.org/NetworkConfiguration

https://www.debian.org/doc/manuals/debian-reference/ch05.en.html

Regards,

But, it is NOT down! I am logged into the Bone from my desktop through the ethernet. I can ssh into other computers from the Bone. Of course, DNS would be the first suspect, but I can ping all the repo servers mentioned in the apt-get errors from the Bone by name. So, DNS is clearly working, too.

Thanks,

Jon

Ah, got it!

In /etc/resolv.conf, I had :
nameserver 127.0.0.1
nameserver 1.2.3.4

I took out the loopback nameserver and put in another real nameserver, and it is now working!
Funny, that didn’t cause a problem with ssh or ping, but apt-get apparently only tried the loopback DNS.

Thanks for the help as always, Robert!!

Jon