I just got a BeagleBone but I am a bit confused with the distro...
isn't it coming with the same Angstrom Linux shipped in BeagleBoards
I've done the following:
# opkg update
# opkg upgrade
# opkg install python-pyftpdlib kernel-module-cdc-acm
Unknown package 'python-pyftpdlib'.
Unknown package 'kernel-module-cdc-acm'.
* opkg_install_cmd: Cannot install package python-pyftpdlib.
* opkg_install_cmd: Cannot install package kernel-module-cdc-acm.
These two packages install correctly in the BeagleBoard...
Do I need to fiddle with some settings for package repositories?
Thanks for any hint,
I've been trying to figure this out myself, but I'll tell you what
little I know....
At this point, there are a lot of kernel modules that aren't yet
available for the Beaglebone. New ones are becoming available over
time, so I think the problem is primarily a backlog of development
work to be done. More advanced users have been generating kernel
modules from source on their own, but I'm not at all familiar with
The missing python package appears to be a case where a package that
was available for previous Angstrom version, 2011.03, isn't (yet)
available for the current version, 2012.01. You can tell what
versions a package is available by looking at the Package Browser web
page, in this case http://www.angstrom-distribution.org/repo/?pkgname=python-pyftpdlib.
(Incidentally, the latest Beagleboard images are 2012.01 -- the python
package is unavailable on those Beagleboard images too, so in this
case it isn't just a Beaglebone thing.)
I don't know whether its possible to point opkg at the 2011.03
repositories. I suspect this is generally not advisable, since a lot
has changed in the core set of packages (connmgr, systemd, etc.), but
that's purely a guess on my part. For Python libraries, it is usually
possible to install them without using opkg, either by running
easy_install (from python-setuptools) or by downloading the Python
source and following the installation instructions.
thanks for your explanation!
It make sense, it maybe just a matter of time then for kernel
and good to know that there is a work around for installing other
How do I know which version am I running?
If I do:
# uname -a
Linux beaglebone 3.1.0+ #1 Tue Nov 15 15:51:15 CET 2011 armv7l GNU/
Should I deduct: 2011.x ?
That's something I haven't figured out either. opkg knows the version
somehow, but it's not telling.
The demo images on http://www.angstrom-distribution.org/demo/beaglebone/
contain the version embedded in the filename (e.g. Angstrom-Cloud9-IDE-
The only place on the beaglebone that I've noticed the version #
displayed is in the serial (i.e. USB-connected) console. On mine, it
displays "Angstrom v2012.01-core - Kernel 3.1.0+" above the login
I'm running the "2012.01.27" demo image downloaded from the web site.
To confuse things further, I think the Angstrom image that was
included in the box was an in-between version, 2011.11 or something
like that, but in terms of opkg compatibility it is close (maybe
identical) to 2012.01.
To find angstrom version:
cat /etc/dogtag (this file does not exist on my KncMiner which uses a BB Black)
or cat /etc/angstrom-version
Angstrom v2013.06 (Core edition)
Built from branch: angstrom-staging-yocto1.4
Target system: arm-angstrom-linux-gnueabi
or cat /etc/angstrom-build-info
Configured Openembedded layers:
meta-angstrom = angstrom-v2013.06-yocto1.4:947
meta-ruby = angstrom-staging-yocto1.4:5f9e
meta-kde = angstrom-staging-yocto1.4:25c0
meta-opie = master:c242efc6ca55772a88602f1
meta-java = master:7fb9465e5c2db618eedb59d
meta-browser = dylan:2140f2a114f7009f86479afb
meta-mono = master:ac286b1682e6bcc486ceb30
meta-ros = master:f69c619237e325e40b710b0
common-bsp = dylan:7fdf9c670a10c5031a2d5555
meta-ti = angstrom-staging-yocto1.4:134b
meta-efikamx = master:07f2a5c777b4f8669857353
meta-nslu2 = master:8948458fe3ec2b3c713b2a1
meta-palm = master:41c5c86813aefc21ace53ed
meta-handheld = master:1dd57dcf14056901e25d8a6
meta-n450 = dylan:86525216c6b8bdb850bf0195
meta-minnow = dylan:d5849d5ea14bc9b34ddd05b9
meta-raspberrypi = dylan:770b88b2ce696fddd2fdb99b
meta-linaro-toolchain = dylan:7ab5e76aac4344e1a228
meta-kncminer = master:a3014d0bccef2a449b3d10e
meta = angstrom-staging-yocto1.4:fef4