[beagleboard] Re: Mountain Lion RNDIS issue

GoogleGroups
1

Hi,

We ran into the same problem. The workaround we came up with is:

Connect to the beaglebone using the serial port using Terminal ( screen `ls
/dev/{tty.usb*B,beaglebone-serial}` 115200 )
In the Beaglebone terminal type the following command: rmmod
/lib/modules/3.2.18/kernel/drivers/usb/gadget/g_mass_storage
Next type: insmod /lib/modules/3.2.18/kernel/drivers/usb/gadget/g_ether.ko

It may be better to use 'systemctl stop storage-gadget-init.service;
systemctl start network-gadget-init.service' for the purpose of
keeping your instructions working across revisions and to otherwise
avoid unintended side-effects. The Angstrom Distribution uses systemd
to control start-up services among other tasks.

2

If you don’t see anything like /dev/tty.usb*B, let alone beaglebone-serial, what then?

To be precise, If I freshly flash the eMMC with debian, I get the full networking solution. However, I’m having a problem where I goof up Debian’s ability to boot. So I’d like to serial in so as to diagnose. But I don’t get the entries in /dev.

3

If you don't see anything like /dev/tty.usb*B, let alone beaglebone-serial,
what then?

The BeagleBone Black does not have the 'built-in' usb-serial adapter
like the beaglebone classic did..

You'll need a 3.3v ttl usb-serial adapter similar to this one:
http://www.digikey.com/product-detail/en/TTL-232R-3V3/768-1015-ND/1836393?cur=USD

To be precise, If I freshly flash the eMMC with debian, I get the full
networking solution. However, I'm having a problem where I goof up Debian's
ability to boot. So I'd like to serial in so as to diagnose. But I don't get
the entries in /dev.

You could just always 'reflash' and not do the same mistake..

Regards,

4

Actually, I’ve ‘not made the mistake’ 10 times with the same result. But I’ve now given up on the debian image and used the ubuntu image, and it worked fine the first time.

With debian, even plugging in a monitor and such didn’t help: I’d see the penguin and nothing further. With ubuntu, it all worked fine.

5

Well that's odd, as both images share the same kernel, only the
userspace is different.

Regards,

6

Robert,

thanks.