I ended up figuring out what was wrong.  I had to follow the
directions on http://joshuawise.com/horndis under "Notes about
Mavericks".  After following those instructions and then uninstalling
horndis and reinstalling everything worked.

On Fri, Jun 6, 2014 at 4:44 PM,  <rbaxte...@gmail.com> wrote:
> How was this resolved?  I think I am running into the same problem.  I just
> got my BeagleBone Black Rev C and tried installing the drivers on OSX
> 10.9.3.  Installation of the drivers went fine but I couldn't connect to
> http://192.168.7.2.  I went to my Network Preferences and saw there were a
> bunch of BeagleBone entries but all were modem connections.  I removed them
> all.  When I go to add a new interface I see a bunch of entries for
> beaglebone including BeagleBoneBlack (en5), BeagleBoneBlack (usbmodem1d113),
> and BeagleBoneBlack (usbmodem1d111) (usbmodem1d111).  I assume I don't want
> the usbmodem ones so I try selection BeagleBoneBlack (en5) and clicking
> create, but nothing happens, no new interface is created.  Any ideas?
>
>
>
> On Wednesday, September 18, 2013 8:19:37 PM UTC-4, ch...@weetopia.com wrote:
>>
>> I had the same issue. My user account on my MBA13 10.8.4 is a standard
>> user (i.e., non-root).
>>
>> So I logged in as root (Admin user), and plugged in the BBB, installed the
>> drivers. It worked.
>>
>> Logged out, rebooted the BBB, and now the USB connection is recognized as
>> USB Ethernet.
>>
>> I would guess that one of the PRE or POST install scripts requires root
>> privileges to run, and wrapping it in sudo or asking for permissions instead
>> of silently failing is preferable.
>>
>> cheers
>>
>> -chris
>>
>> On Thursday, July 11, 2013 7:08:25 AM UTC-7, Richard Cook wrote:
>>>
>>> Trying to get BBB on the air via USB using MacBook Pro OS X 10.8.4
>>> without success.
>>> Connected O.K. -- LEDs flashing nicely and BEAGLEBONE disk mounts and is
>>> accessible on my desktop.
>>> Installed derivers for Mac OS X from the BEAGLEBONE disk. No errors.
>>> No server response from 192.168.7.2
>>> No response to ping of same address
>>>
>>> Ran shell script patch included in FTDI directory (do_patch.sh)
>>> No server response from 192.168.7.2
>>> No response to ping of same address
>>>
>>> Searched FAQs
>>> Nothing relevant found
>>>
>>> Advice?
>>>
>>>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/zhLaiO45d74/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to