Jump to content

usb 3.0 gigabit as eth1 not recognized - opi pc

cam2019

By cam2019
in SD card and PSU issues

 Share

Recommended Posts

cam2019

cam2019

Posted
Posted

hi guys,

 

literally i'm new to orange pi and as well as here on armbian. like days old. I managed to run and use the usb device in rpi3b+ but was unable to on orange pi. now i know that this is a driver issue.

 

can someone show me how to download and install the driver on my opi pc?

 

TIA

 

Cam

gigabit.jpg

Igor

Igor

Posted
Posted
  On 6/8/2019 at 11:25 AM, cam2019 said:

literally i'm new to orange pi

Expand  

 

Without logs (armbianmonitor -u) we have absolutely no idea what to tell you. Drivers are usually not just installed but has to be ported to or enabled in the kernel. If you use old kernel 3.4.y forget about ... switch to new one and it will most likely just work. If not ... logs logs logs :) 

cam2019

cam2019

Posted
  • Author
Posted 
pi@orangepipc:~$ sudo ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.2.119  netmask 255.255.255.0  broadcast 192.168.2.255
        inet6 fe80::e9f5:f619:21ee:d30d  prefixlen 64  scopeid 0x20<link>
        ether 02:81:41:c6:e0:a6  txqueuelen 1000  (Ethernet)
        RX packets 1790  bytes 157475 (153.7 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 833  bytes 71647 (69.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 38

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        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

pi@orangepipc:~$
  Reveal hidden contents

Hope this helps. i don't know what to do next.

 

Thanks for the reply

guidol

guidol

Posted
Posted
  On 6/8/2019 at 11:25 AM, cam2019 said:

literally i'm new to orange pi and as well as here on armbian. like days old. I managed to run and use the usb device in rpi3b+ but was unable to on orange pi. now i know that this is a driver issue.

can someone show me how to download and install the driver on my opi pc?

Expand  

I do use the same USB3.0-ethetnet adapter on my devices under armbian and got NO driver issue. 

Welcome to ARMBIAN 5.73 stable Debian GNU/Linux 9 (stretch) 5.1.0-sunxi
package bsp-kernel[5.86] u-boot[5.85] dtb[5.86] firmware[5.83] config[5.88]
Linux opi-zero-99 5.1.0-sunxi #5.86 SMP Mon May 13 21:11:09 CEST 2019 armv7l GNU/Linux

[1399909.295651] usb 5-1: new high-speed USB device number 2 using ehci-platform
[1399909.455662] usb 5-1: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=30.00
[1399909.455734] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[1399909.455783] usb 5-1: Product: USB 10/100/1000 LAN
[1399909.455830] usb 5-1: Manufacturer: Realtek
[1399909.455874] usb 5-1: SerialNumber: 000001000000
[1399909.732093] usbcore: registered new interface driver r8152
[1399909.763071] usbcore: registered new interface driver cdc_ether
[1399909.867457] usb 5-1: reset high-speed USB device number 2 using ehci-platform
[1399910.083109] r8152 5-1:1.0 eth1: v1.09.9
[1399910.174042] r8152 5-1:1.0 enx00e04c68007b: renamed from eth1


Which version of armbian do you use? Maybe your eth1 is also renamed (see dmesg or ifconfig)

= Predictable Network Interface Name

 

Maybe you have to switch this off for eth1 as name:

http://www.itzgeek.com/how-tos/mini-howtos/change-default-network-name-ens33-to-old-eth0-on-ubuntu-16-04.html 

sudo nano /etc/default/grub
from: GRUB_CMDLINE_LINUX=""
to:   GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"
sudo grub-mkconfig -o /boot/grub/grub.cfg
reboot

 

[EDIT]  your code in your dmesg:

413 [ 5.906764] r8152 4-1:1.0 eth1: v1.09.9

414 [ 6.188868] EXT4-fs (zram0): mounted filesystem without journal. Opts: discard

415 [ 6.552250] r8152 4-1:1.0 enx00e04c680046: renamed from eth1

 

So now configure enx00e04c680046 or disable the predictable network names :)

 

Test:

ifconfig enx00e04c680046 up

and then look for the device with

ifconfig

cam2019

cam2019

Posted
  • Author
Posted

this is what i get 

  Reveal hidden contents

 

Igor

Igor

Posted
Posted
  On 6/8/2019 at 1:50 PM, cam2019 said:

I use the latest Armbian_5.83_Orangepipc_Debian_stretch_next_4.19.38.img

Expand  


Its not recognised at all - like it was not attached. Try connecting it via some powered USB hub.

Edit:
Next time use link generated by armbianmonitor -u ... to reduce those walls of text.

cam2019

cam2019

Posted
  • Author
Posted
  On 6/8/2019 at 1:57 PM, Igor said:


Its not recognised at all - like it was not attached. Try connecting it via some powered USB hub.

Expand  

 

could it be a power supply issue? the usb adapter works fine under windows so i'm sure its working fine. 

Igor

Igor

Posted
Posted
  On 6/8/2019 at 1:58 PM, cam2019 said:

could it be a power supply ssue? 

Expand  


Surely possible. What about other USB (especially USB3) devices? Do they work?

guidol

guidol

Posted
Posted
  On 6/8/2019 at 1:57 PM, Igor said:


Its not recognised at all - like it was not attached. Try connecting it via some powered USB hub.

Expand  

in his first dmesg it was recognized:
  

388 [ 5.571663] usbcore: registered new interface driver r8152
413 [ 5.906764] r8152 4-1:1.0 eth1: v1.09.9
414 [ 6.188868] EXT4-fs (zram0): mounted filesystem without journal. Opts: discard
415 [ 6.552250] r8152 4-1:1.0 enx00e04c680046: renamed from eth1

but not in the second one.

@cam2019 did you use another USB-Port? Maybe that has to be enabled in armbian-config -> system -> hardware ?

1
Igor

Igor

Posted
Posted
  On 6/8/2019 at 2:02 PM, guidol said:

but not in the second one.

Expand  


Than its almost 100% power related problem. Not an Armbian problem. 

cam2019

cam2019

Posted
  • Author
Posted
  On 6/8/2019 at 2:02 PM, guidol said:

in his first dmesg it was recognized:
  

388 [ 5.571663] usbcore: registered new interface driver r8152
413 [ 5.906764] r8152 4-1:1.0 eth1: v1.09.9
414 [ 6.188868] EXT4-fs (zram0): mounted filesystem without journal. Opts: discard
415 [ 6.552250] r8152 4-1:1.0 enx00e04c680046: renamed from eth1

but not in the second one.

@cam2019 did you use another USB-Port? Maybe hat has to be enabled in armbian-config -> system -> hardware ?

Expand  

its the only usb device that is connected at the moment and yes i tried using all the 3 ports still got no eth1

guidol

guidol

Posted
Posted
  On 6/8/2019 at 1:50 PM, cam2019 said:

I use the latest Armbian_5.83_Orangepipc_Debian_stretch_next_4.19.38.img

Expand  

with this version you shouldnt have a driver issue - like you could see in your first dmesg log :)

cam2019

cam2019

Posted
  • Author
Posted

ahh i see. i will change the power supply and will get back to you asap

 

thanks for the very fast replies

cam2019

cam2019

Posted
  • Author
Posted

after changing to 3amps 5v psu still i get this

  Reveal hidden contents

is my board damaged?

Igor

Igor

Posted
Posted
  On 6/8/2019 at 3:06 PM, cam2019 said:

after changing to 3amps 5v psu still i get this

Expand  

 

How do you power your board? What kind of cable do you use? Can you make a photo?

cam2019

cam2019

Posted
  • Author
Posted

http://ix.io/1Lfc

 

its just an improvised one. barrel jack to opi pc and a 5v from our own rpi3b+ custom board. the reason why i sorted to using the output of our custom board because i ran out of options. used 2 buck converters and still no luck. i am sure its at least 3 amps 5v as was designed by our engineer.

 

 

Igor

Igor

Posted
Posted

Measure 5V line on USB port to see if its within tolerance. Running low on ideas ... ofc it can be some hardware defects - in that case we both waste time.

1
Igor

Igor

Posted
Posted
  On 6/8/2019 at 3:56 PM, cam2019 said:

maybe its with the latest build of armbian?

Expand  

 

Or quirky driver/hardware combo which we didn't make and will not even try to fix.

 

1
guidol

guidol

Posted
Posted
  On 6/8/2019 at 3:56 PM, cam2019 said:

i already used 2nd board. i have 3. still no eth1. maybe its with the latest build of armbian?

Expand  

when you did try different boards - did you also try all of the !three! usb-ports on every board?

specially the single one on the other side of the eth0-port? Because in you first dmesg the USB-Ethernet adapter was recognized as eth1 and then renamed.

And this renamed name wouldnt go in every situation automatically up for ifconfig.

 

So check the other usb-ports and when you will see enx00e04c680046 in dmesg get him up with

ifconfig enx00e04c680046 up

and then he would be displayed in

ifconfig

 

when the port is down (not automatically up or no cable/link connected the interface is in down state) then it wouldnt displayed by

ifconfig

 

The part after enx is the MAC-address of your USB3.0 Ethernet-adapter.

 

I got this model running on my devices without special power supply and from my personal view there is no driver problem with armbian and this device.

1
cam2019

cam2019

Posted
  • Author
Posted

i got it working now. what did i do? i plugged in 3 gigabits all at the same time then it all got registered in ifconfig. and removed 1 by 1 until i only have 1.  


[sudo] password for pi:
enx00e04c68012f: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.10.10.1  netmask 255.255.254.0  broadcast 10.10.11.255
        inet6 fe80::5712:3fed:cdaa:9ee3  prefixlen 64  scopeid 0x20<link>
        ether 00:e0:4c:68:01:2f  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 44  bytes 5108 (4.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.2.110  netmask 255.255.255.0  broadcast 192.168.2.255
        inet6 fe80::ecc5:4572:5bee:8fcd  prefixlen 64  scopeid 0x20<link>
        ether 02:81:0c:80:12:7d  txqueuelen 1000  (Ethernet)
        RX packets 749  bytes 52425 (51.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 132  bytes 17546 (17.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 38

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 14  bytes 630 (630.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 14  bytes 630 (630.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

pi@orangepipc:~$

 

cam2019

cam2019

Posted
  • Author
Posted 
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.2.110  netmask 255.255.255.0  broadcast 192.168.2.255
        inet6 fe80::ecc5:4572:5bee:8fcd  prefixlen 64  scopeid 0x20<link>
        ether 02:81:0c:80:12:7d  txqueuelen 1000  (Ethernet)
        RX packets 548  bytes 49314 (48.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 159  bytes 21987 (21.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 38

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.10.10.1  netmask 255.255.254.0  broadcast 10.10.11.255
        inet6 fe80::6ffa:2eb7:3e4d:50f  prefixlen 64  scopeid 0x20<link>
        ether 00:e0:4c:68:01:2f  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 72  bytes 9425 (9.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 10  bytes 474 (474.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 10  bytes 474 (474.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

pi@orangepipc:~$

it is now eth1

 

using this

Thanks @guidol and @Igor

 

will bother you again soon :D

Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept