Thanks Robert,
What I saw on the x86 was that eth1 was successfully brought up - all it
missed was an IP address. So "ifconfig eth1" had MAC address etc, just no
address.
Thanks, Iain


On 1 July 2015 at 18:26, Robert Nelson <[email protected]> wrote:

> On Wed, Jul 1, 2015 at 12:09 PM, Robert Nelson <[email protected]>
> wrote:
> > On Wed, Jul 1, 2015 at 12:06 PM,  <[email protected]> wrote:
> >> Hi,
> >>
> >> I have created SD card images from the June 29th debian 8.1 images for
> both
> >> console and lxqt.
> >>
> >> With the lxqt image I was successfully getting a linux machine to
> create an
> >> new interface eth1with address 192.168.7.1 when USB was connected.
> >>
> >> I know that the console image is stripped down and that in the March
> 2015
> >> image it was necessary to install udhcpd and then update to the latest
> >> boot-scripts to get it to work.
> >> I tried this on the 29th June console image but with no success. The
> >> boot-scripts were actually at the latest version when I did git pull.
> >>
> >> Is there another component missing in the  Debian 8.1 console image?
> >
> > Actually anything after June 16 has udhcpd installed by default for
> > the console image....
> >
> >
> https://github.com/RobertCNelson/omap-image-builder/commit/1b2d8ece564f5fb708e8139ee40db05691cc3e03
> >
> > I'll dl and check, as something is going on..
>
> So on the bbb: (journalctl -f)
>
> Jun 29 07:36:23 beaglebone sh[275]: generic-board-startup: [startup
> script=/opt/scripts/boot/am335x_evm.sh]
> Jun 29 07:36:24 beaglebone kernel: using random self ethernet address
> Jun 29 07:36:24 beaglebone kernel: using random host ethernet address
> Jun 29 07:36:24 beaglebone kernel: using host ethernet address:
> 54:4A:16:BB:AE:0B
> Jun 29 07:36:24 beaglebone kernel: using self ethernet address:
> 54:4A:16:BB:AE:00
> Jun 29 07:36:24 beaglebone kernel: usb0: HOST MAC 54:4a:16:bb:ae:0b
> Jun 29 07:36:24 beaglebone kernel: usb0: MAC 54:4a:16:bb:ae:00
> Jun 29 07:36:24 beaglebone kernel: using random self ethernet address
> Jun 29 07:36:24 beaglebone kernel: using random host ethernet address
> Jun 29 07:36:24 beaglebone kernel: g_ether gadget: Ethernet Gadget,
> version: Memorial Day 2008
> Jun 29 07:36:24 beaglebone kernel: g_ether gadget: g_ether ready
> Jun 29 07:36:24 beaglebone kernel: g_ether gadget: high-speed config
> #1: CDC Ethernet (ECM)
>
> on the x86:
>
> [14634.248639] usb 1-1.2: new high-speed USB device number 4 using ehci-pci
> [14634.341396] usb 1-1.2: New USB device found, idVendor=0525,
> idProduct=a4a2
> [14634.341403] usb 1-1.2: New USB device strings: Mfr=1, Product=2,
> SerialNumber=3
> [14634.341407] usb 1-1.2: Product: BeagleBoneBlack
> [14634.341410] usb 1-1.2: Manufacturer: Circuitco
> [14634.341413] usb 1-1.2: SerialNumber: 0C-000C2115BBBK
> [14634.409956] cdc_subset: probe of 1-1.2:1.0 failed with error -22
> [14634.410766] cdc_subset 1-1.2:1.1 usb0: register 'cdc_subset' at
> usb-0000:00:12.2-1.2, Linux Device, aa:a0:be:c6:fb:91
> [14634.410936] usbcore: registered new interface driver cdc_subset
> [14634.416672] cdc_ether: probe of 1-1.2:1.0 failed with error -16
> [14634.416714] usbcore: registered new interface driver cdc_ether
> [14634.424461] cdc_subset 1-1.2:1.1 usb0: kevent 12 may have been dropped
>
> Other then my usb3.0 hub acting up again and dropping the connection
> everything seems to be in spec..
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
> --
> 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/T7N2xs7K0TU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> 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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to