Did you try this tutorial? http://learn.adafruit.com/beaglebone/wifi
I was able to use that to get my wifi working pretty quickly - and I know absolutely nothing about Linux. I made sure to get an adapter that worked with the Beagle - http://www.amazon.com/gp/product/B003MTTJOY/ref=oh_details_o01_s00_i00?ie=UTF8&psc=1.
Can’t say much about your other issues though - but Wifi wasn’t a problem for me.
Bruce D Lightner
The Ubuntu elinux link-> did you build your images or use the provided prebuilt?
I also found a very nice easy new way for the Bone/EVM after some bad experiences
it’s the TI Sitara Linux SDK very
I was very hesitant to use OE but I discovered the TI SDK is based on Arago which uses OE. i CUT THIS BLURB from their site
http://arago-project.org/wiki/index.php/Main_Page
Many users will want to use the official SDK products from the TI software download page. Others will want the cutting edge of using upstream OpenEmbedded or Angstrom distributions. Arago serves the middle ground where an advanced user wishes to get a peek into an upcoming release or to peek under the hood of an existing release
— On Fri, 6/7/13, Christopher Berg cubeberg@gmail.com wrote:
> From: Christopher Berg cubeberg@gmail.com
> Subject: [beagleboard] Re: Angstrom on Beaglebone Black (Switched to Ubuntu)
> To: beagleboard@googlegroups.com
> Date: Friday, June 7, 2013, 7:52 AM
>
> Did you try this tutorial? http://learn.adafruit.com/beaglebone/wifi
> I was able to use that to get my wifi working pretty quickly - and I know absolutely nothing about Linux. I made sure to get an adapter that worked with the Beagle - http://www.amazon.com/gp/product/B003MTTJOY/ref=oh_details_o01_s00_i00?ie=UTF8&psc=1.
> Can’t say much about your other issues though - but Wifi wasn’t a problem for me.
>
> On Friday, June 7, 2013 12:38:29 AM UTC-4, Bruce D Lightner wrote:
>
> > I loved the specs on the Beaglebone Black TI ARM processor and hardware…but Angstrom on BBB sucks—and is not worth the effort!
> >
> > I’ve given up on Angstrom. Overall it is not stable. WiFi does not work. The new-and-improved Linux configuration utility “systemctl” does not work properly—for networking and/or for Wifi. Hours and hours of wasted time. What bozo thought that Linux needed yet-another-way to configure!!! Truly STUPID!
> >
> > And, the very latest (two-day old) BBB image from BeagleBoard.Org did not help. Amazingly bad experience. Who at BeagleBoard.Org thought that Angstrom was a good idea? They need to be shown out the door!
> >
> > I was about to trash both of my Beaglebone Black PCBs and switch back to Rasberry Pi when I discovered the Ubuntu port for BBB. Highly recommended. USB Wifi worked out-of-the box as expected. Stable as a rock.
> >
> > http://elinux.org/ BeagleBoardUbuntu#eMMC:_ BeagleBone_Black
> >
> > I even was able to login to the Ubuntu via a simple Web page! Screw the stupid USB “networking connection” from a Windows PC. I was never ever able to make that work to get a shell login from my Windows 7 PC! And, SSH via a “real” Ethernet connection did not work on my first BBB because some SSH “key file” was zero-length. (That cost me ~4 hours!)
> >
> > It’s time for BeagleBoard.Org to admit they screwed up and to dump the “default” Angstrom Linux distribution. A total waste of time!!!
> >
> > Great hardware…lousy software choices. (Someone has been smoking way too much Python!
>
> –
> For more options, visit http://beagleboard.org/discuss
> —
> You received this message because you are subscribed to the Google Groups “BeagleBoard” group.
> To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
|
I used the pre-built BBB Ubuntu image discussed here…
http://elinux.org/BeagleBoardUbuntu#eMMC:_BeagleBone_Black
In particular, I put the following image on a 4GB SDCard and installed it over the “stock” Angstrom release…
http://rcn-ee.net/deb/flasher/raring/BBB-eMMC-flasher-ubuntu-13.04-2013-05-29.img.xz
Worked like a charm.
Note that I’m strictly a “command line” Linux user. Setting up WiFi with WPA2 that way takes a bit of work, but that’s fine with this particular application.
Best regards,
Bruce
no one mentioned buildroot 
I use Ubuntu or TI SDK/Matrix as a demo for my customers. Ubuntu is to show how well desktop experience with a PC can be the same at an embedded paltform. TI SDK/Matrix is to show that all hardware is functional - 3D for example.
Hi Maxim
How many real world application need this PC experience?
Are they buying after demo? just curious
— On Fri, 6/7/13, Maxim Podbereznyy lisarden@gmail.com wrote:
Ubuntu is to show how well desktop experience with a PC can be the same at an embedded paltform.
|
no one mentioned buildroot
I don't know buildroot. Is it good?
I'll add my 2 cents on this one. Buildroot is outstanding, but it
solves a different problem than Ubuntu and Angstrom. The basic idea
with Buildroot is that you pick what you want (i.e. U-boot, Linux
kernel, busybox, libraries, your app, etc.), and then it does
everything needed to create the image files for your system. It
doesn't do any package management, and the configuration feels more
"locked in" than other distros. Development is all done off device and
cross-compiled. I like this a lot, but my projects are mostly the kind
where you make a firmware image that gets burned onto a bunch of
devices and then is never modified unless there's a software update.
I've had the feeling that Buildroot is a great match for a lot of the
projects that people are doing here, but it lags behind Ubuntu and
Angstrom in terms of Beaglebone support. For example, I can't speak to
BBB support in Buildroot, since I don't have one, but it looked like
the 3.8 kernel updates were only committed recently. I'm sure that it
will get there, though.
Frank
I'll add my 2 cents on this one. Buildroot is outstanding, but it
solves a different problem than Ubuntu and Angstrom. The basic idea
with Buildroot is that you pick what you want (i.e. U-boot, Linux
kernel, busybox, libraries, your app, etc.), and then it does
everything needed to create the image files for your system. It
doesn't do any package management, and the configuration feels more
"locked in" than other distros. Development is all done off device and
cross-compiled. I like this a lot, but my projects are mostly the kind
where you make a firmware image that gets burned onto a bunch of
devices and then is never modified unless there's a software update.Yes I like this about buildroot.
I've had the feeling that Buildroot is a great match for a lot of the
projects that people are doing here, but it lags behind Ubuntu and
Angstrom in terms of Beaglebone support. For example, I can't speak to
BBB support in Buildroot, since I don't have one, but it looked likeHmm you say buildroot lags behind then you say you don't know
about BBB support in buildroot. What the...?
The original white Beaglebone is the one that I've used.
the 3.8 kernel updates were only committed recently. I'm sure that it
will get there, though.This is an aspect of the BBB I don't understand. And maybe it is an aspect
of the upstream that I don't understand. Is it the arm cortex-a8 support
in the linux kernel that's lagging? Or is the BBB somehow so unique it
requires special drivers to function?
The lag that I was referring to was getting BBB support into
Buildroot. It's a community-driven effort (like much of the other
software development here), so it happens when someone makes it
happen.
Also, regarding ARM Cortex-A8 support, that's not the issue. That's
been there forever. The problem is that between the release of the
original Beaglebone and the BBB, the Linux kernel had a major change
in how ARM devices are supported. Rather than stagnate on the old
kernel version, the Beagleboard people chose to stay current. Check
out the list archives about the Linux 3.8 upgrade. There have been
lots of posts about this and a lot of effort is going in to fixing
issues.
Frank
Windows has had a cmd( CLI ) ssh “client” since the XP days. It is not something I would like to use all the time, but I have used it. puTTY of course puts it to shame. However, and this could be what I was originally thinking of. the ( New ?) RUN SSH command is based on puTTY … but it seems rather limited.