Jump to content
  • 0

Orange Pi Win Plus no Ethernet on Ubuntu Bionic


Alex333
 Share

Question

I need help. I builded image Armbian_5.67_Orangepiwin_Ubuntu_bionic_next_4.14.81_desktop. Ethernet don't work. Wi-Fi is Ok.

When I tested image Armbian_5.59_Orangepiwin_Ubuntu_xenial_default_3.10.107_desktop Ethernet and Wi-Fi worked on the same board.

armbianmonitor -u
System diagnosis information will now be uploaded to sysctl: permission denied on key 'vm.mmap_rnd_bits'
sysctl: permission denied on key 'vm.mmap_rnd_compat_bits'
sysctl: permission denied on key 'vm.stat_refresh'
http://ix.io/1s78

 

Link to comment
Share on other sites

9 answers to this question

Recommended Posts

  • 0
1 hour ago, Alex333 said:

Ethernet don't work. Wi-Fi is Ok.


Modern kernel has little to do with old 3.10.y (luckily).  Support for A64 in kernel 4.14.y is considered experimental and is without end user support. This feature was not developed, is making troubles or was not broken. It would be fixed if we know how or we had enough resources to get there ... That is also the reason why there are no images with a kernel 4.14.y Somebody need to fix it once: https://www.armbian.com/get-involved 


Here:

are much bigger chances of success. But since there is not much help except usual suspects, things go slowly. OrangepiWin is not operational yet.

Link to comment
Share on other sites

Search Before Posting!

  • 0

I feel sorry.

Already has a test image Ubuntu Bionic desktop mainline kernel 4.14 for Banapi M64. This board has identical hardware with Orange Pi Win Plus, CPU, Ethernet and BT controllers.

These boards are like twin brothers. Is there any information about Ethernet and Wi-Fi works on Banapi M64?

Link to comment
Share on other sites

  • 0
12 minutes ago, Alex333 said:

This board has identical hardware with Orange Pi Win Plus, CPU, Ethernet and BT controllers.


Obviously not - check schematics. Anyway, we have much better solution which is out for try: https://dl.armbian.com/orangepiwin/archive/Armbian_5.67_Orangepiwin_Debian_stretch_dev_4.19.2.7z It's clearly not finished yet, but its working much better.

Link to comment
Share on other sites

  • 0

Thank you Igor. I will test this image.

I use OrangePi Win Plus with Waveshare 7 LCD HDMI (C) display (WSVGA resolution 1024x600). Sorry this old theme. 

I have tried many methods with old image Ubuntu_xenial_default_3.10.107 but Waveshare worked incorrectly.

I was glad when new image Ubuntu Bionic began to works with resolution 1024x600 Waveshare display correctly (automatically).

Three times I thank the developers for supporting low resolutions in Bionic.

I hope it will work sooner or later. :)

 

Link to comment
Share on other sites

  • 0
On 11/16/2018 at 6:32 PM, Alex333 said:

Ethernet don't work. Wi-Fi is Ok.

 

Сontinuation:

1.  I compared and analyzed only Ethernet schematic part for BananaPI-M64 and OrangePi Win/Plus boards. Soc Allwinner A64 connection to Ethernet chip RTL8211D/E fully identically.

     But there is one nuance as RTL8211 powered:

For BPI-M64 board. 

     RTL8211 voltage supply 3.3V comes directly from Power Managment chip (PMIC AXP803). Plus additional voltage regulator chip 3.3V to 2.5V for GMAC-RGMII. 

For OPI Win/Plus board.

     RTL8211 is powered by two separate voltage regulator chips 5V to 3.3V and 5V to 2.5V.  These Vregs are turn on/off by signal EMAC-PWR-EN who comes from Soc pin PD14 (PD14/LCD-D20/LVDS-VP1/RGMII-NULL/RMII-RXER). For BPI-M64 board this pin not used (it is Test Point 3).

     If signal EMAC-PWR-EN is "1" RTL8211 is powered and Ethernet is working.

     If Soc pin PD14 "0" RTL8211 is not powered and Ethernet don't work.

 

2.  I connected the multimeter to OPI Win/Plus and tested next image:

    a) Old image Ubuntu_xenial_default_3.10.107

    b) Builded image Armbian_5.65_Orangepiwin_Debian_stretch_next_4.14.79_desktop

    c) Builded image Armbian_5.67_Orangepiwin_Ubuntu_bionic_next_4.14.81_desktop

    d) Image https://dl.armbian.com/orangepiwin/archive/Armbian_5.67_Orangepiwin_Debian_stretch_dev_4.19.2.7z

 

    Image a). Signal EMAC-PWR-EN set to "1" after the moment Kernel starting. After load Ethernet is working.

    Images b) and c). Signal EMAC-PWR-EN set to "0" always. RTL8211 is not powered and certainly Ethernet don't work.

    Image c). Booting process non stable.

    If the download is successful signal EMAC-PWR-EN set to "1" after the moment Kernel starting. Ethernet is working.

    Sometimes the boot process suspended and error occurs. Only RESET buttom. 

    Photos when it happened:

20181120_2.thumb.jpg.5825cc32ae1ab6b74af363f6e1407307.jpg20181120_3.thumb.jpg.912746d3f8a5c67911773850ef3bbe03.jpg

 

3.  Anyone can try to solve this problem in new images. Need set to "1"  Soc pin PD14 may be in overlays or anywhere else in the booting process.

     I can help build and test image on OPI Win/Plus board. Soon I get BPI-M64 board.

 

Link to comment
Share on other sites

  • 0
On 11/21/2018 at 3:28 AM, Alex333 said:

3.  Anyone can try to solve this problem in new images. Need set to "1"  Soc pin PD14 may be in overlays or anywhere else in the booting process.

 

     I can help build and test image on OPI Win/Plus board. Soon I get BPI-M64 board.

  

Board: orangepi win plus

Problem: Unable to start Ethernet with mainline kernel and uboot

 

[ 4592.137430] dwmac-sun8i 1c30000.ethernet eth0: Could not attach to PHY
[ 4592.144091] dwmac-sun8i 1c30000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
RTNETLINK answers: No such device

It’s ridiculous. I have been suffering from the kernel driver configuration all the time until I saw this post.

I used to compile and start uboot and kernel with the default configuration. Ethernet has only a small possible performance boot (this is weird, but it is true)

Can you teach me how to set EMAC-PWR-EN to "1" ?:D

Im noobs。。。

Link to comment
Share on other sites

  • 0

I builded and tested dev image Nightly Ubuntu Bionic:

ARMBIAN 5.67.181125 nightly Ubuntu 18.04.1 LTS 4.19.4-sunxi64

It seems this problem is solved. Ethernet and Wi-Fi is worked on fly simultaneously.

 

How to build here

 

 

 

My console boot dump:

U-Boot 2018.11-rc3-armbian (Nov 25 2018 - 19:21:39 +0100) Allwinner Technology

CPU:   Allwinner A64 (SUN50I)
Model: OrangePi Win/Win Plus
DRAM:  2 GiB
MMC:   SUNXI SD/MMC: 0
Loading Environment from FAT... Unable to use mmc 0:1... In:    serial
Out:   vidconsole
Err:   vidconsole
Net:   phy interface7
eth0: ethernet@1c30000

230454 bytes read in 18 ms (12.2 MiB/s)
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB OHCI 1.0
USB2:   USB EHCI 1.00
USB3:   USB OHCI 1.0
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3042 bytes read in 10 ms (296.9 KiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
153 bytes read in 8 ms (18.6 KiB/s)
33996 bytes read in 19 ms (1.7 MiB/s)
3795 bytes read in 19 ms (194.3 KiB/s)
Applying kernel provided DT fixup script (sun50i-a64-fixup.scr)
## Executing script at 44000000
8654741 bytes read in 437 ms (18.9 MiB/s)
14243848 bytes read in 707 ms (19.2 MiB/s)
## Loading init Ramdisk from Legacy Image at 4fe00000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    8654677 Bytes = 8.3 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 4fa00000
   Booting using the fdt blob at 0x4fa00000
EHCI failed to shut down host controller.
EHCI failed to shut down host controller.
   Loading Ramdisk to 497bf000, end 49ffff55 ... OK
   reserving fdt memory region: addr=4fa00000 size=6e000
   Loading Device Tree to 000000004974e000, end 00000000497befff ... OK

Starting kernel ...

 

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...