On Mon, Mar 20, 2017 at 9:37 PM, Jon Seymour <[email protected]> wrote:
> I am trying to use d D-Link USB Ethernet with Debian 8.7 running on BBB.
>
>
> The device describes itself as: "D-Link DUB-1312 USB 3.0 to Gigabit Ethernet
> Adapter".
>
>
> The lsusb output is:
>
>
>     "Bus 001 Device 002: ID 2001:4a00 D-Link Corp."
>
>
> The driver for this device is ax88179_178a which is loaded into the kernel
> as a module.
>
>
>
> The driver finds the device:
>
>
> [   21.274812] ax88179_178a 1-1:1.0 eth1: register 'ax88179_178a' at
> usb-musb-hdrc.1.auto-1, D-Link DUB-1312 USB 3.0 to Gigabit Ethernet Adapter,
> e4:6f:13:f3:df:43
>
> [   21.280951] usbcore: registered new interface driver ax88179_178a
>
> [   21.791100] omap-sham 53100000.sham: hw accel on OMAP rev 4.3
>
> [   21.836014] omap-aes 53500000.aes: OMAP AES hw accel rev: 3.2
>
> [   23.920271] asoc-simple-card sound: i2s-hifi <-> 48038000.mcasp mapping
> ok
>
> [   24.088282] ax88179_178a 1-1:1.0 enxe46f13f3df43: renamed from eth1
>
>
> If I manually bring enxe46f13f3df43 up, then I can configure it and get a
> working connection to the internet.
>
>
> I wanted to automatically bring up the device to use DHCP but when I added:
>
>
>    auto enxe46f13f3df43
>
>    iface enxe46f13f3df43 inet dhcp
>
>
> to /etc/network/interfaces the interface was not brought up automatically
> (even after reboot)
>
>
> I tried to statically configured the device with:
>
>
> auto enxe46f13f3df43
>
> iface enxe46f13f3df43 inet static
>
>     address 192.168.1.100
>
>     network 255.255.255.0
>
>     gateway 192.168.1.1
>
>
> but the interface also did not come up automatically in this case. It would
> come up correctly configured if I manually ran ifup enxe46f13f3df43.
>
>
> I also tried to change the interface name to eth1 using
> /etc/udev/rules.d/71-local-rules
>
>
> # Auto generated by RootStock-NG: setup_sdcard.sh
>
> # udevadm info -q all -p /sys/class/net/eth0 --attribute-walk
>
>
> # BeagleBone: net device ()
>
> SUBSYSTEM=="net", ACTION=="add", KERNELS=="enxe46f13f3df43",
> ATTR{dev_id}=="0x0", ATTR{type}=="1", NAME="eth1"
>
>
> I also tried to use the systemd.link feature by creating a file called
> /etc/systemd/network/10-local.link with these contents:
>
>
> [Match]
>
> Driver=ax88179_178a
>
>
> [Link]
>
> Name=eth1
>
>
> So, there are two problems here:
>
>
> - the interface is not being configured automatically
>
> - I can't rename the interface with either udevd or systemd.link
> configuration
>
>
> Can anyone help me understand why this isn't working as expected?

it's systemd that's doing the rename, in /boot/uEnv.txt, find the
"cmdline=coherent_pool=1M quiet" option and change it to:

cmdline="coherent_pool=1M net.ifnames=0 quiet"

Starting on Dec 9th 2016, we added the "net.ifnames=0" option by default.

on your next reboot, it'll show up as eth1..

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYhaHdnJB8-aBGoDFtWoGqkVJyaN%3Dh-67xacjWy_YtP_bQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to