Any update on this? I am having the similar errors when running opkg
update on my beaglebone. (wget: bad address 'feeds.angstrom- distribution.org')
A ping to feeds.angstrom-distribution.org works fine (~200ms).
Hello, i have a beaglebone since yesterday.
No problems in the repository, but I had to make some commands for
make it work in my linux (a console only linux).
First, if the connection is with usb-ethernet gateway, in the console
I must put:
# eject /dev/sdb <---storage device of beaglebone
After this command the usb device of the usb-ethernet gateway emerges
and I can put a ip to the usb.
Next I can ssh to the device, and there is no resolver ni
/etc/resolv.conf, and no gateway in the ip's.
So to make it work:
# cat "nameserver 8.8.8.8" >> /etc/resolv.conf
# route add default gw 192.168.7.1
These changes are lost when I reset the board, I think it must be the
avahi daemon that rewrite the resolv.conf. The gateway also defaults
to nothing although it's written in /etc/network/interfaces, i suppose
it's also the avahi.
OK, I manually changed the DNS server by editing the /etc/resolv.conf
file to have the line nameserver 208.67.222.222. After this, I am able
to successfully run opkg update and opkg upgrade.
Can you reach the outside world? Have you tried pinging google.com? If not then your network is incorrectly setup and needs fixing before you can start using opkg with online repositories.
If you put an entry in /etc/resolv.conf before you run the upgrade you should be able to keep DNS functionality during the upgrade.
However, don't restart connman once it crashes unless you are using a serial connection. It resets the Ethernet interface when it starts and you will lose your ssh connection.
I don't know why it crashes during the upgrade - only that it does crash. And it doesn't always crash either.
Until that's fixed it's probably better not to do opkg update/upgrade unless you are sure what you are doing. If you've done lots of customizations I can see why it's preferential not to reflash - I've been down this road - but for now the upgrade is pretty tricky and its easy to render your installation unbootable. At that point you have to reflash anyway.
Seems like even touching the resolv.conf doesn’t allow the DNS functionality when i tried to run this with a new board. If anyone has any ideas, would be greatly appreciated.
It seems to be working without the bad address error now (my BBB is still upgrading). **NOTE: THIS IS A HACK, you should remove the line afterwards from /etc/hosts
For clarity here is the lines in my /etc/hosts files
root@beaglebone:~# cd /etc
root@beaglebone:/etc# vi hosts
root@beaglebone:/etc# cat hosts
127.0.0.1 localhost.localdomain localhost
140.211.169.179 feeds.angstrom-distribution.org
…however, my opkg update & opkg upgrade ended with this…
WARNING: could not open /lib/modules/3.8.13/modules.order: No such file or directory
WARNING: could not open /lib/modules/3.8.13/modules.builtin: No such file or directory
WARNING: could not open /lib/modules/3.8.13/modules.order: No such file or directory
WARNING: could not open /lib/modules/3.8.13/modules.builtin: No such file or directory
Not sure if this is a problem…I will ignore it for now…
thx!
frenchy
Hi, Could I receive some advice about updating the BBB with opkg update. I reflashed the eMMc with Cloud9 GNOME Image 2013.09.04. The OS is Angstrom v2012.12 (Core edition), Built from branch: angstrom-staging-yocto1.3. I am receiving the following error: Example of error without modifying the hosts file
I followed the /etc/host fix, still had a problem. Checked disk space using “df -k” and saw that /tmp was full. opkg had run and failed a few times and written some temp files and filled it up. Cleared a few files out of /tmp and voila, “opkg update” worked ok.
Hi there, I just encountered the same issue and had the same wget error response after trying the suggested /etc/hosts fix then running opkg update. Did you ever find a solution to this?