+- PINE64 (https://forum.pine64.org)
+-- Forum: Pinebook Pro (https://forum.pine64.org/forumdisplay.php?fid=111)
+--- Forum: Linux on Pinebook Pro (https://forum.pine64.org/forumdisplay.php?fid=114)
+--- Thread: Ethernet on Bionic-Mate? (/showthread.php?tid=8348)
Ethernet on Bionic-Mate? - zaius - 11-16-2019
I have a possibly stupid question
I can't seem to get the Bionic-Mate build (run off SD) to connect to the internet with an Ethernet to USB adapter. When I was testing internet speeds with Debian, I just plugged it in and it worked with either USB port. Now I can't seem to get the same adapter to work Bionic-Mate. I've tried a bunch of settings. WiFi still works though. What am I doing wrong?
RE: Ethernet on Bionic-Mate? - xalius - 11-16-2019
Is the kernel config missing the driver for your dongle? What driver is it using on Debian?
RE: Ethernet on Bionic-Mate? - zaius - 11-16-2019
(11-16-2019, 05:54 PM)xalius Wrote: Is the kernel config missing the driver for your dongle? What driver is it using on Debian?
Sorry, no idea. Although I tried two different adapters, a Moshi USB 3 and the Pine64 USB 2, and they both worked on the stock Debian build.
RE: Ethernet on Bionic-Mate? - jpakkane - 11-17-2019
I had the same issue but manually running sudo dhclient made it work.
RE: Ethernet on Bionic-Mate? - zaius - 11-22-2019
(11-17-2019, 04:47 AM)jpakkane Wrote: I had the same issue but manually running sudo dhclient made it work.
I tried that, but it didn't work.
"Cannot find device eth0"
RE: Ethernet on Bionic-Mate? - ndp - 03-06-2020
(11-22-2019, 02:40 PM)zaius Wrote:(11-17-2019, 04:47 AM)jpakkane Wrote: I had the same issue but manually running sudo dhclient made it work.
I tried that, but it didn't work.
"Cannot find device eth0"
I got mine to work by making the following change to /lib/udev/rules.d/73-usb-net-by-mac.rules :
from:
IMPORT{builtin}="net_id", NAME="$env{ID_NET_NAME_MAC}"
to:
IMPORT{builtin}="net_id", NAME="eth0
After making the change I rebooted the pinebook pro and the usb ethernet connection now work properly.
I found the above solution in the following link:
https://superuser.com/questions/1000570/why-eth0-is-renamed-to-enx78e7d1ea46da-after-upgrade
In my case I also need the "r8152" kernel module because I have a Realtek 8152 USB ethernet adapter so I added r8152 to /etc/modules.
Hope this helps.
RE: Ethernet on Bionic-Mate? - zaius - 03-06-2020
(03-06-2020, 10:32 AM)ndp Wrote: I got mine to work by making the following change to /lib/udev/rules.d/73-usb-net-by-mac.rules :
from:
IMPORT{builtin}="net_id", NAME="$env{ID_NET_NAME_MAC}"
to:
IMPORT{builtin}="net_id", NAME="eth0"
After making the change I rebooted the pinebook pro and the usb ethernet connection now work properly.
I found the above solution in the following link:
https://superuser.com/questions/1000570/why-eth0-is-renamed-to-enx78e7d1ea46da-after-upgrade
In my case I also need the "r8152" kernel module because I have a Realtek 8152 USB ethernet adapter so I added r8152 to /etc/modules.
Hope this helps.
Thanks, I'll try that when I get chance. There has been quite a bit of OS development since the last time I used my PBP. I'm still leaning towards Ubuntu when things get settled, and there is an SPI boot, working SSD adapter, etc. Ubuntu is what I used the day my MBP was getting its battery replaced, and it seems to have the most software packaged.
RE: Ethernet on Bionic-Mate? - Arwen - 03-08-2020
@zaius, you can use "lsusb" to see what USB driver is needed. In my case;
Code:
# lsusb -s 004:004 -v
Bus 004 Device 004: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet
...
# grep -i 179 /usr/src/linux/.config
CONFIG_USB_NET_AX88179_178A=m
...
# modprobe ax88179_178a
# ifconfig -a
...
enp56s0f4u1u1: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether 00:0a:cd:26:45:3c txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
...Edit: Forgot to mention that I simplified the USB & kernel module command sequence. Meaning I ran commands to find what I needed, like the kernel module name.