Problems with Orange PC+


Recommended Posts

I have 2 working Orangepi Zero v 1.4 live, booting and working right now. In two different locations running the latest Armbian version. Just ran a test from my phone and seeing as how I never setup wifi, have only ever used Ethernet from first install. Ima go ahead and say it's working. If I really wanted, I could fire up my OPiPC+ and compare since that's another board you claim to have problems with but.... I'm probably not going to.

My gut says isolated incident, user error, OP has admitted hardware issues and clearly couldn't tell the difference between Armbian and stock chinese eMMC software. Kinda disappointed that this one guys issue is taking up so much of each of the devs time.  You guys have so many better things to be doing. :(

~ Check your power cables on the Orangepi Zero. Ive experienced issues with this myself, using known good cables, especially when booting. This is also where a UART cable comes in handy.
~ I didn't see any proof of the health of your SD cards, just your word that they work on Raspi. Are you verifying the images after you burn them? I cherish each of my SD cards and want to deny deny that there is anything wrong with them, until they cause me issues for 15-20 minutes too long (similar to what you describe) and then I snap them in half.
~ Perhaps you're attempting an SSH connection too soon/wrong time? Putty can be weird like that. I've seen it take a couple extra moments after booting before Putty can establish a connection. If not, it'll just refuse the connection as seen in your picture.

Link to post
Share on other sites
Armbian is a community driven open source project. Do you like to contribute your code?

1 hour ago, StuxNet said:

I have 2 working Orangepi Zero v 1.4 live, booting and working right now. In two different locations running the latest Armbian version. Just ran a test from my phone and seeing as how I never setup wifi, have only ever used Ethernet from first install. Ima go ahead and say it's working.

My gut says isolated incident, user error, OP has admitted hardware issues and clearly couldn't tell the difference between Armbian and stock chinese eMMC software. Kinda disappointed that this one guys issue is taking up so much of each of the devs time.  You guys have so many better things to be doing. :(

 

Provide screenshot, and photo of the board please.

 

About the emmc i was just crazy to make some test all the night and i didnt see that the image was corrupted and default emmc booting up ! But you look so self confident, so after all test i'v provided you should directly tell me why all my raspberry pi working well and why all my orange pi don't work? (3 raspbery pi, 4 orange pi)

 

Yeah ok so my case dont need to be solved i dont deserv explaination i'm just unlucky to bought 100% faulty product this is the conclusion thank you a lot 100$ gone

 



screenshot.fw.png

Link to post
Share on other sites
20 minutes ago, blaster_56 said:

Yeah ok so my case dont need to be solved i dont deserv explaination i'm just unlucky to bought 100% faulty product this is the conclusion thank you a lot 100$ gone

 

Wow! Do you know how much my time is worth?! Your attitude already sucked at the time you wrote your first posting, you take no care at all to provide INFORMATION worth the name, you test different stuff like crazy and really already wasted a lot of time of different people still trying to help you. I even watched two videos which is something I HATE since moronically wasted time!

 

You talked about 'ethtool 100' which would be needed which is plain BS since both Zero and PC Plus are Fast Ethernet boards. Maybe you have an 'advanced' network switch or router box that can be configured to do crazy things? Adjusting MTU settings? Blocking MAC addresses? Sabotaging auto negotiation?

 

On your Windows box we can see that your DHCP server hands out DNS server addresses 208.67.222.222 and 208.67.220.220, on your Zero you do a 'ping google.com' which should IMMEDIATELY return something like 'PING google.com (172.217.17.238) 56(84) bytes of data.' since otherwise DNS RESOLUTION IS NOT WORKING! Your prompt does not even return within 20 seconds.

 

We still want to push you into the right direction or at least i want to know what could all go wrong if multiple error sources are combined and now you get back here with that antisocial 'so my case dont need to be solved i dont deserv explaination' BS while at the same time every second post from you postulates that Armbian is broken in general and you know other people suffering from the same problem. O, how this support crap sucks!!!

Link to post
Share on other sites

@tkaiser I did my test before posting,

My first faulty orange pi was received on 20 april, and i post on 18 june.

Since this time i'v test many orange pi, test multiple power supply test my network, ask my network enginer to check and his response is : driver is faulty, i'v contacted the developper of the driver, he told me that the driver will be updated and soon available.

I dont use any usb cable before, its directly connected in the power supply (picture ) 

I use vpn the 172.217.17.238 ip is a virtual interface

I'm just bored that everyone take me as a noob, you told me it can be power supply i bought a professional power supply to test it, same result as my original power supply (2 tested)

My Raspberry Pi works directly plug & play with same power supply. (I'll do video to proof this again)

Yeah about ethtool i'v made test on another version (stored in my emmc) and it work after a networking reload but i cannot provide this to my customers its absolutly not stable & professional, i need a simple & working images, just burn & work.

About the worth of your time :

I have developping team who work on my project specially designed for orange pi, so i have to fix this problem ASAP, i dont take in consideration that all my orange pi will be faulty.

Now you can understand that i have many pressure about this and answers like "you dont know difference between armbian and chineese default rom hohohoho" make me annoying.

 

@stuxnet Check again the SD test its full read & write test

WhatsApp Image 2017-06-21 at 9.43.25 PM.jpeg

Link to post
Share on other sites

I'm in agreement with tkaiser, fundamentally, not emotionally :P I'm inclined to go ahead and lock this thread but since I literally was made a mod two days ago I don't wanna outstep my bounds. I encourage someone else to though.


OP. I don't care about the attitude. I refuse to believe that you bought all those boards and they are all bad. I refuse to believe that the issue is with Armbian since I have all of the same boards as you and they work for me, well beyond the issues you describe.
Years of professional IT experience tell me you're the problem. (No insult intended) By that I mean you're the common denominator, you're the variable. Your network setup, SD card, a cable, something else or a combination of the above is the issue, which isn't at all farfetched seeing as how you know a thing or two about tech otherwise you wouldn't have purchased the boards. Sometimes things don't work for techies because we tinkered with the wrong thing. If you can't admit that possibility, then that's very telling.

We're all going above and beyond trying to help you, your attitude aside. Can you explain to me how all of my boards would be working fine if the issue was software with Armbian?

P.s. Why is "you dont know difference between armbian and chineese default rom hohohoho" annoying if that's literally what you expressed?

 

Quote

you have made this script so can you explain me why i have this chineese home screen after i build my image from your script ????

 

Link to post
Share on other sites
15 minutes ago, blaster_56 said:

i need a simple & working images, just burn & work

 

In other words Armbian (you're one of a few persons having trouble, there are thousands who don't).

 

I'm out since all the time you come up with complaints and excuses or weird claims that the problem must be lying somewhere else than where it obviously originates.

 

I asked you for f*cking 4 simple commands and their output, told you what's wrong in your video wrt 'ping google.com' (it's obvious if you know about how networking works! The Zero can not contact the OpenDNS servers he got from the DHCP server) and told you why you were measuring voltage wrong. What did I get back in return? A story about why your situation sucks. That doesn't help me since I want to help Armbian (this thread can be a nice template for 'how NOT to try to solve problems') and not you running a business (honestly I really don't care why you are doing what or not, I just want to get questions answered!)

Link to post
Share on other sites

Arp -a :

 

Spoiler

Interface : 192.168.75.1 --- 0xd
  Adresse Internet      Adresse physique      Type
  192.168.75.255        ff-ff-ff-ff-ff-ff     statique
  224.0.0.22            01-00-5e-00-00-16     statique
  224.0.0.251           01-00-5e-00-00-fb     statique
  224.0.0.252           01-00-5e-00-00-fc     statique
  239.255.255.250       01-00-5e-7f-ff-fa     statique

Interface : 192.168.254.1 --- 0xe
  Adresse Internet      Adresse physique      Type
  192.168.254.255       ff-ff-ff-ff-ff-ff     statique
  224.0.0.22            01-00-5e-00-00-16     statique
  224.0.0.251           01-00-5e-00-00-fb     statique
  224.0.0.252           01-00-5e-00-00-fc     statique
  239.255.255.250       01-00-5e-7f-ff-fa     statique

Interface : 192.168.56.1 --- 0x1a
  Adresse Internet      Adresse physique      Type
  192.168.56.255        ff-ff-ff-ff-ff-ff     statique
  224.0.0.22            01-00-5e-00-00-16     statique
  224.0.0.251           01-00-5e-00-00-fb     statique
  224.0.0.252           01-00-5e-00-00-fc     statique
  239.255.255.250       01-00-5e-7f-ff-fa     statique

Interface : 172.27.232.38 --- 0x21
  Adresse Internet      Adresse physique      Type
  172.27.232.1          00-ff-cb-ef-28-c0     dynamique
  172.27.239.254        00-ff-cb-ef-28-c0     dynamique
  172.27.239.255        ff-ff-ff-ff-ff-ff     statique
  224.0.0.22            01-00-5e-00-00-16     statique
  224.0.0.251           01-00-5e-00-00-fb     statique
  239.255.255.250       01-00-5e-7f-ff-fa     statique
  255.255.255.255       ff-ff-ff-ff-ff-ff     statique

Interface : 192.168.1.7 --- 0x23
  Adresse Internet      Adresse physique      Type
  192.168.1.1           00-06-31-e6-2f-da     dynamique
  192.168.1.255         ff-ff-ff-ff-ff-ff     statique
  224.0.0.22            01-00-5e-00-00-16     statique
  224.0.0.251           01-00-5e-00-00-fb     statique
  224.0.0.252           01-00-5e-00-00-fc     statique
  239.255.255.250       01-00-5e-7f-ff-fa     statique
  255.255.255.255       ff-ff-ff-ff-ff-ff     statique


 

 

ipconfig /all :

Spoiler


Configuration IP de Windows

   Nom de l'h“te . . . . . . . . . . : hacker-comp
   Suffixe DNS principal . . . . . . : 
   Type de noeud. . . . . . . . . .  : Diffusion
   Routage IP activ‚ . . . . . . . . : Non
   Proxy WINS activ‚ . . . . . . . . : Non
   Liste de recherche du suffixe DNS.: Home

Carte Ethernet Connexion au r‚seau local 15 :

   Statut du m‚dia. . . . . . . . . . . . : M‚dia d‚connect‚
   Suffixe DNS propre … la connexion. . . : 
   Description. . . . . . . . . . . . . . : TAP-Windows Adapter V9 #8
   Adresse physique . . . . . . . . . . . : 00-FF-BA-0C-FE-8E
   DHCP activ‚. . . . . . . . . . . . . . : Oui
   Configuration automatique activ‚e. . . : Oui

Carte Ethernet Connexion au r‚seau local 14 :

   Statut du m‚dia. . . . . . . . . . . . : M‚dia d‚connect‚
   Suffixe DNS propre … la connexion. . . : 
   Description. . . . . . . . . . . . . . : TAP-Windows Adapter V9 #7
   Adresse physique . . . . . . . . . . . : 00-FF-1C-EB-00-F8
   DHCP activ‚. . . . . . . . . . . . . . : Oui
   Configuration automatique activ‚e. . . : Oui

Carte Ethernet Connexion au r‚seau local 13 :

   Statut du m‚dia. . . . . . . . . . . . : M‚dia d‚connect‚
   Suffixe DNS propre … la connexion. . . : 
   Description. . . . . . . . . . . . . . : TAP-Windows Adapter V9 #6
   Adresse physique . . . . . . . . . . . : 00-FF-CA-72-E9-8B
   DHCP activ‚. . . . . . . . . . . . . . : Oui
   Configuration automatique activ‚e. . . : Oui

Carte Ethernet Connexion au r‚seau local 12 :

   Statut du m‚dia. . . . . . . . . . . . : M‚dia d‚connect‚
   Suffixe DNS propre … la connexion. . . : 
   Description. . . . . . . . . . . . . . : TAP-Windows Adapter V9 #5
   Adresse physique . . . . . . . . . . . : 00-FF-27-18-DF-04
   DHCP activ‚. . . . . . . . . . . . . . : Oui
   Configuration automatique activ‚e. . . : Oui

Carte Ethernet Connexion au r‚seau local 11 :

   Statut du m‚dia. . . . . . . . . . . . : M‚dia d‚connect‚
   Suffixe DNS propre … la connexion. . . : 
   Description. . . . . . . . . . . . . . : TAP-Windows Adapter V9 #4
   Adresse physique . . . . . . . . . . . : 00-FF-EB-76-A4-0A
   DHCP activ‚. . . . . . . . . . . . . . : Oui
   Configuration automatique activ‚e. . . : Oui

Carte Ethernet Connexion au r‚seau local 10 :

   Statut du m‚dia. . . . . . . . . . . . : M‚dia d‚connect‚
   Suffixe DNS propre … la connexion. . . : 
   Description. . . . . . . . . . . . . . : TAP-Win32 Adapter V9 for OpenVPN Accelerator
   Adresse physique . . . . . . . . . . . : 00-FF-32-A3-2E-A1
   DHCP activ‚. . . . . . . . . . . . . . : Oui
   Configuration automatique activ‚e. . . : Oui

Carte Ethernet Connexion r‚seau Bluetooth 3 :

   Statut du m‚dia. . . . . . . . . . . . : M‚dia d‚connect‚
   Suffixe DNS propre … la connexion. . . : 
   Description. . . . . . . . . . . . . . : P‚riph‚rique Bluetooth (r‚seau personnel) #3
   Adresse physique . . . . . . . . . . . : 48-51-B7-4A-E4-66
   DHCP activ‚. . . . . . . . . . . . . . : Oui
   Configuration automatique activ‚e. . . : Oui

Carte Ethernet Connexion au r‚seau local 9 :

   Statut du m‚dia. . . . . . . . . . . . : M‚dia d‚connect‚
   Suffixe DNS propre … la connexion. . . : 
   Description. . . . . . . . . . . . . . : TAP-Windows Adapter V9 #3
   Adresse physique . . . . . . . . . . . : 00-FF-9C-56-05-E8
   DHCP activ‚. . . . . . . . . . . . . . : Oui
   Configuration automatique activ‚e. . . : Oui

Carte r‚seau sans fil Connexion r‚seau sans fil 4ÿ:

   Statut du m‚dia. . . . . . . . . . . . : M‚dia d‚connect‚
   Suffixe DNS propre … la connexion. . . : 
   Description. . . . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter #6
   Adresse physique . . . . . . . . . . . : 4A-51-B7-4A-E4-63
   DHCP activ‚. . . . . . . . . . . . . . : Oui
   Configuration automatique activ‚e. . . : Oui

Carte r‚seau sans fil Connexion r‚seau sans fil 3ÿ:

   Statut du m‚dia. . . . . . . . . . . . : M‚dia d‚connect‚
   Suffixe DNS propre … la connexion. . . : 
   Description. . . . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter #5
   Adresse physique . . . . . . . . . . . : 4A-51-B7-4A-E4-62
   DHCP activ‚. . . . . . . . . . . . . . : Oui
   Configuration automatique activ‚e. . . : Oui

Carte r‚seau sans fil Connexion r‚seau sans fil 2ÿ:

   Suffixe DNS propre … la connexion. . . : Home
   Description. . . . . . . . . . . . . . : Intel(R) Wireless-N 7260
   Adresse physique . . . . . . . . . . . : 48-51-B7-4A-E4-62
   DHCP activ‚. . . . . . . . . . . . . . : Oui
   Configuration automatique activ‚e. . . : Oui
   Adresse IPv4. . . . . . . . . . . . . .: 192.168.1.7(pr‚f‚r‚) 
   Masque de sous-r‚seau. . . .ÿ. . . . . : 255.255.255.0
   Bail obtenu. . . . . . . . .ÿ. . . . . : mercredi 21 juin 2017 20:11:17
   Bail expirant. . . . . . . . .ÿ. . . . : jeudi 22 juin 2017 20:11:21
   Passerelle par d‚faut. . . .ÿ. . . . . : 192.168.1.1
   Serveur DHCP . . . . . . . . . . . . . : 192.168.1.1
   Serveurs DNS. . .  . . . . . . . . . . : 208.67.222.222
                                   208.67.220.220
   NetBIOS sur Tcpip. . . . . . . . . . . : Activ‚

Carte Ethernet Connexion au r‚seau local 3 :

   Suffixe DNS propre … la connexion. . . : 
   Description. . . . . . . . . . . . . . : TAP-Windows Adapter V9 #2
   Adresse physique . . . . . . . . . . . : 00-FF-CA-EF-28-C0
   DHCP activ‚. . . . . . . . . . . . . . : Oui
   Configuration automatique activ‚e. . . : Oui
   Adresse IPv6 de liaison locale. . . . .: fe80::ece6:ebf9:8c51:c47f%33(pr‚f‚r‚) 
   Adresse IPv4. . . . . . . . . . . . . .: 172.27.232.38(pr‚f‚r‚) 
   Masque de sous-r‚seau. . . .ÿ. . . . . : 255.255.248.0
   Bail obtenu. . . . . . . . .ÿ. . . . . : mercredi 21 juin 2017 20:11:39
   Bail expirant. . . . . . . . .ÿ. . . . : jeudi 21 juin 2018 20:11:39
   Passerelle par d‚faut. . . .ÿ. . . . . : 
   Serveur DHCP . . . . . . . . . . . . . : 172.27.239.254
   IAID DHCPv6 . . . . . . . . . . . : 1124138954
   DUID de client DHCPv6. . . . . . . . : 00-01-00-01-1C-E7-DD-AB-68-F7-28-4C-2F-80
   Serveurs DNS. . .  . . . . . . . . . . : 108.61.10.10
   NetBIOS sur Tcpip. . . . . . . . . . . : Activ‚

Carte Ethernet Connexion au r‚seau local 2 :

   Statut du m‚dia. . . . . . . . . . . . : M‚dia d‚connect‚
   Suffixe DNS propre … la connexion. . . : 
   Description. . . . . . . . . . . . . . : TAP-Windows Adapter V9
   Adresse physique . . . . . . . . . . . : 00-FF-11-EA-CD-EB
   DHCP activ‚. . . . . . . . . . . . . . : Oui
   Configuration automatique activ‚e. . . : Oui

Carte Ethernet Connexion au r‚seau local :

   Statut du m‚dia. . . . . . . . . . . . : M‚dia d‚connect‚
   Suffixe DNS propre … la connexion. . . : Home
   Description. . . . . . . . . . . . . . : Realtek PCIe GBE Family Controller
   Adresse physique . . . . . . . . . . . : 68-F7-28-4C-2F-80
   DHCP activ‚. . . . . . . . . . . . . . : Oui
   Configuration automatique activ‚e. . . : Oui

Carte Ethernet VMware Network Adapter VMnet1 :

   Suffixe DNS propre … la connexion. . . : 
   Description. . . . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1
   Adresse physique . . . . . . . . . . . : 00-50-56-C0-00-01
   DHCP activ‚. . . . . . . . . . . . . . : Non
   Configuration automatique activ‚e. . . : Oui
   Adresse IPv6 de liaison locale. . . . .: fe80::7cf1:2f80:e4d4:43a1%13(pr‚f‚r‚) 
   Adresse IPv4. . . . . . . . . . . . . .: 192.168.75.1(pr‚f‚r‚) 
   Masque de sous-r‚seau. . . .ÿ. . . . . : 255.255.255.0
   Passerelle par d‚faut. . . .ÿ. . . . . : 
   IAID DHCPv6 . . . . . . . . . . . : 352342102
   DUID de client DHCPv6. . . . . . . . : 00-01-00-01-1C-E7-DD-AB-68-F7-28-4C-2F-80
   Serveurs DNS. . .  . . . . . . . . . . : fec0:0:0:ffff::1%1
                                   fec0:0:0:ffff::2%1
                                   fec0:0:0:ffff::3%1
   NetBIOS sur Tcpip. . . . . . . . . . . : Activ‚

Carte Ethernet VMware Network Adapter VMnet8 :

   Suffixe DNS propre … la connexion. . . : 
   Description. . . . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8
   Adresse physique . . . . . . . . . . . : 00-50-56-C0-00-08
   DHCP activ‚. . . . . . . . . . . . . . : Non
   Configuration automatique activ‚e. . . : Oui
   Adresse IPv6 de liaison locale. . . . .: fe80::9583:acda:bc14:9301%14(pr‚f‚r‚) 
   Adresse IPv4. . . . . . . . . . . . . .: 192.168.254.1(pr‚f‚r‚) 
   Masque de sous-r‚seau. . . .ÿ. . . . . : 255.255.255.0
   Passerelle par d‚faut. . . .ÿ. . . . . : 
   IAID DHCPv6 . . . . . . . . . . . : 385896534
   DUID de client DHCPv6. . . . . . . . : 00-01-00-01-1C-E7-DD-AB-68-F7-28-4C-2F-80
   Serveurs DNS. . .  . . . . . . . . . . : fec0:0:0:ffff::1%1
                                   fec0:0:0:ffff::2%1
                                   fec0:0:0:ffff::3%1
   NetBIOS sur Tcpip. . . . . . . . . . . : Activ‚

Carte Ethernet VirtualBox Host-Only Network :

   Suffixe DNS propre … la connexion. . . : 
   Description. . . . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
   Adresse physique . . . . . . . . . . . : 08-00-27-00-E8-17
   DHCP activ‚. . . . . . . . . . . . . . : Non
   Configuration automatique activ‚e. . . : Oui
   Adresse IPv6 de liaison locale. . . . .: fe80::c5da:226:a995:b980%26(pr‚f‚r‚) 
   Adresse IPv4. . . . . . . . . . . . . .: 192.168.56.1(pr‚f‚r‚) 
   Masque de sous-r‚seau. . . .ÿ. . . . . : 255.255.255.0
   Passerelle par d‚faut. . . .ÿ. . . . . : 
   IAID DHCPv6 . . . . . . . . . . . : 1023934503
   DUID de client DHCPv6. . . . . . . . : 00-01-00-01-1C-E7-DD-AB-68-F7-28-4C-2F-80
   Serveurs DNS. . .  . . . . . . . . . . : fec0:0:0:ffff::1%1
                                   fec0:0:0:ffff::2%1
                                   fec0:0:0:ffff::3%1
   NetBIOS sur Tcpip. . . . . . . . . . . : Activ‚

Carte Tunnel isatap.{FB353482-6663-49BC-AA1A-65B9D56D7FD3} :

   Statut du m‚dia. . . . . . . . . . . . : M‚dia d‚connect‚
   Suffixe DNS propre … la connexion. . . : 
   Description. . . . . . . . . . . . . . : Carte Microsoft ISATAP
   Adresse physique . . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP activ‚. . . . . . . . . . . . . . : Non
   Configuration automatique activ‚e. . . : Oui

Carte Tunnel isatap.{330B5707-9141-4D79-ABFE-471FAE297B5E} :

   Statut du m‚dia. . . . . . . . . . . . : M‚dia d‚connect‚
   Suffixe DNS propre … la connexion. . . : 
   Description. . . . . . . . . . . . . . : Carte Microsoft ISATAP #2
   Adresse physique . . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP activ‚. . . . . . . . . . . . . . : Non
   Configuration automatique activ‚e. . . : Oui

Carte Tunnel isatap.{6F24B5D9-3E0B-4EC7-ADD4-0588DF6E9103} :

   Statut du m‚dia. . . . . . . . . . . . : M‚dia d‚connect‚
   Suffixe DNS propre … la connexion. . . : 
   Description. . . . . . . . . . . . . . : Carte Microsoft ISATAP #3
   Adresse physique . . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP activ‚. . . . . . . . . . . . . . : Non
   Configuration automatique activ‚e. . . : Oui

Carte Tunnel isatap.{01DE8936-E720-49B1-BFEA-858F26FE159F} :

   Statut du m‚dia. . . . . . . . . . . . : M‚dia d‚connect‚
   Suffixe DNS propre … la connexion. . . : 
   Description. . . . . . . . . . . . . . : Carte Microsoft ISATAP #4
   Adresse physique . . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP activ‚. . . . . . . . . . . . . . : Non
   Configuration automatique activ‚e. . . : Oui

Carte Tunnel isatap.{EF347290-1450-410E-87BE-6999B7713A5E} :

   Statut du m‚dia. . . . . . . . . . . . : M‚dia d‚connect‚
   Suffixe DNS propre … la connexion. . . : 
   Description. . . . . . . . . . . . . . : Carte Microsoft ISATAP #5
   Adresse physique . . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP activ‚. . . . . . . . . . . . . . : Non
   Configuration automatique activ‚e. . . : Oui

Carte Tunnel isatap.{BCA8BACD-6963-4F61-B807-EE431AC651DD} :

   Statut du m‚dia. . . . . . . . . . . . : M‚dia d‚connect‚
   Suffixe DNS propre … la connexion. . . : 
   Description. . . . . . . . . . . . . . : Carte Microsoft ISATAP #7
   Adresse physique . . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP activ‚. . . . . . . . . . . . . . : Non
   Configuration automatique activ‚e. . . : Oui

Carte Tunnel isatap.{1E274D22-7352-4FF4-9119-7FBB938A7463} :

   Statut du m‚dia. . . . . . . . . . . . : M‚dia d‚connect‚
   Suffixe DNS propre … la connexion. . . : 
   Description. . . . . . . . . . . . . . : Carte Microsoft ISATAP #8
   Adresse physique . . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP activ‚. . . . . . . . . . . . . . : Non
   Configuration automatique activ‚e. . . : Oui

Carte Tunnel isatap.{5CA97D76-925D-4EF8-B7DA-3D28431488B6} :

   Statut du m‚dia. . . . . . . . . . . . : M‚dia d‚connect‚
   Suffixe DNS propre … la connexion. . . : 
   Description. . . . . . . . . . . . . . : Carte Microsoft ISATAP #9
   Adresse physique . . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP activ‚. . . . . . . . . . . . . . : Non
   Configuration automatique activ‚e. . . : Oui
 

 

Traceroute 8.8.8.8 incoming & video proof too

 

(If you dont care dont speak about the value of your time, time is precious for everyone in this topic)

 

As you can see one orange pi is dead.

 

Compare with Raspberry PI 3 strictly same setup :

Regards

Link to post
Share on other sites

So what are we arguing about? All those videos prove is that it's hardware. Not software. Which is what we've been saying all along.
 

Quote

As you can see one orange pi is dead.

 

I find it really curious that you show the OpiZero fully booted, swap everything over, then very briefly show it (not even the TV output) before cutting the video. Then you fully record the bootup and even login of the Raspi.
Not to mention your issues up until now were with multiple boards not just the OpiZero. The name of this thread is, problems with OPi PC+, after all but w/e. Here's what I think happened.

You shorted a couple/several pins, using your sketchy aligator clips on a brand new OPiZero that you waiting several weeks to get.
Now you're upset and looking to put the blame on someone. Even if that's not true, it still remains that you might have accidentally. Alligator clips can be slippery, next time use proper connectors.

 

It's not software. Have you ever even bothered trying a UART as suggested multiple times? You never did answer my question as to why (if it wasn't hardware) it would be working for literally everyone else.

 

P.s. Lol, regards? Yea right dude. Good day.

Link to post
Share on other sites
4 hours ago, blaster_56 said:

Yeah ok so my case dont need to be solved i dont deserv explaination i'm just unlucky to bought 100% faulty product this is the conclusion thank you a lot 100$ gone

keep in mind, you dont spend this money to the armbian devs. you spend it to xunlong. So, being rude to the guys who gives you all the support for free isn't the best idea to solve your problems right?

3 hours ago, blaster_56 said:

I have developping team who work on my project specially designed for orange pi, so i have to fix this problem ASAP, i dont take in consideration that all my orange pi will be faulty.

Especially if you're under pressure and need support from people that give it for free, be polite. It doesn't help you if they are pissed,  cause they can just stop answer to your tread and you're alone with your problems.

 

I can confirm for you that with a rev. 1.4 opi zero (powered over micro usb @2A PSU, with samsung evo 32gb sd-card) and debian on it works fine (see pictures, for sure good enough to work with ssh).  Getting four (if I have it right in mind) damaged boards at once seems you're a really unlucky guy or you're brick them somehow (btw I would never power them with alligator clips, that's a harakiri way to power sensitive things).

 

With Igor, martinayotte and tkaiser you had at least three guys answering to your questions who are good in problem solving.  Doing their proposals should help you immediately to determine if it is a software or a hardware problem.

 

 

rev14.jpg

Armbian_531.png

Link to post
Share on other sites
7 minutes ago, chwe said:

keep in mind, you dont spend this money to the armbian devs. you spend it to xunlong. So, being rude to the guys who gives you all the support for free isn't the best idea to solve your problems right?

Especially if you're under pressure and need support from people that give it for free, be polite. It doesn't help you if they are pissed,  cause they can just stop answer to your tread and you're alone with your problems.

 

 Getting four (if I have it right in mind) damaged boards at once seems you're a really unlucky guy or you're brick them somehow (btw I would never power them with alligator clips, that's a harakiri way to power sensitive things).


Couldn't agree more about just being polite and the whole fact about how Armbian not directly profiting from board sales. As I mentioned before regarding the alligator clips. Granted I think he's using them for AV to the TV not power if he is though, wow... In any case, I know the v1.4 board has PWR/GND pins directly next to each other. No reason a slipped clip can't short em out.

Link to post
Share on other sites
12 hours ago, blaster_56 said:

If you dont care dont speak about the value of your time, time is precious for everyone in this topic

 

https://youtu.be/R5mSp05PFgc?t=1m12s

 

Thank you for the next shitty video. In the upper right corner on the display there's a yellow lightning bolt. That's Raspberry Pi firmware telling you that you're suffering from under-voltage. You have been told by me that your Multimeter measuring is stupid, you don't improve on that, still showing only silly numbers. You measure on the wrong side of the cable.

 

The yellow lightning bolt will be shown if voltage drops below 4.65V at the other side of the cable. With this video you proof that your cable is insufficient and not able to power devices reliably. I asked you about this before but you refused to give an answer.

 

Thanks to the next shitty video we now know that your devices suffer from under-voltage. Interestingly one OPi Zero boots under-volted, the other not.

 

I think we can add a 3rd problem source why things 'with Armbian' are failing:

  • powering problems
  • SD card problems
  • 'I am an expert, I know what I do, everyone talking to me is stupid'

Bildschirmfoto 2017-06-22 um 08.23.21.png

Link to post
Share on other sites

A note to the moderators of this forum:

 

This thread can serve as a nice example why 'Armbian is failing': Armbian images are tested (except of the nightlies -- I will never ever again write something about this nightly shit since I did it way too often but the inner circle doesn't care about external opinions) so when people experience problems it's usually either powering or SD card trouble.

 

Dear moderators: please use a methodology that doesn't suck. Users can suffer from both SD card problems and powering problems as we can see in this thread. Especially if they think they're experts they don't like answers that tell them they suffer from simple problems and since they think they're smart they try to use their own methodology ('I ruled out the SD card problem, it still doesn't work so all your recommendations are bullshit').

 

Please try to deal with that in a polite and structured way (that's the reason why I resigned from the moderator role a while ago) and focus on what's known: It's always the same (powering or SD cards and every 2 months 'update drama' for reasons I don't understand) but user expectations and ignorance level differ.

Link to post
Share on other sites

@StuxNet i bought the alligator yesterday...  I didn't do this before had many troubles

 

@tkaiser i want to insult you but i'll not do it because i want to solve my problem,

 

Sd card was tested :

 

#########################SD TEST################################

TEST 8 GB KINGSTOM

Warning: Only 14895 of 14896 MByte tested. -> This is mean that all the sd card was fully write, its mean all byte was write 
Test finished without errors. -> This is mean that no error was detected so you can think that SD card is 100% working (not 100% one MByte was not tested sorry)
You can now delete the test files *.h2w or verify them again.
Writing speed: 9.35 MByte/s -> This is the writing speed its mean the speed the byte was write
Reading speed: 75.2 MByte/s -> This is the reading speed its mean the speed the byte was read
H2testw v1.4

TEST 128 GB SAMSUNG

Warning: Only 122590 of 122591 MByte tested. -> This is mean that all the sd card was fully write, (its mean all byte was write) & read 
Test finished without errors. -> This is mean that no error was detected so you can think that SD card is 100% working (not 100% one MByte was not tested sorry)
You can now delete the test files *.h2w or verify them again.
Writing speed: 19.3 MByte/s -> This is the writing speed its mean the speed the byte was write
Reading speed: 43.5 MByte/s -> This is the reading speed its mean the speed the byte was read
H2testw v1.4

################################################################

 

For the SD stop to talk about this please.

 

For power yeah you are right that the cable make lost some voltage, so i'v took my other power supply and i'v checked what voltage was on the pin of Orange Pi B :

 

1498116551-vlcsnap-2017-06-22-14h16m28s7

(problem still the same wifi working ethernet is not working)

 

2 Questions that make you stop talking for nothing : 

 

Question number 1 : How can you explain that Orange PI A dont boot with exactly same configuration and Orange PI B boot ?
Question number 2 : Why keep continue to post in this thread if you cannot understand that the problem is deeper than power supply or sd card ?

 

Now tell me which number you wanna see on the orange pi zero pin and i will make your dreams true

For others, please help me to fix this situation or make me understand why its a problem :

 

@Igor You was right, i'v test with 5.31 build this morning, problem is the same. For you what is the problem if its not coming from power supply, sd card, or network setup?

 

Regards

Link to post
Share on other sites
26 minutes ago, blaster_56 said:

Why keep continue to post in this thread?

 

To show future moderators a way how to deal with problems (talking about persons with your attitude).

 

You showed already that

  • you failed to burn images since 'too smart to follow instructions'
  • understanding of basics ('Chinese stuff magically appearing on your Armbian build' while you in reality just failed to boot the board from SD card and Android on eMMC took over)
  • under-voltage happens in your setup
  • some network nonsense happens too (you still did not answer all my questions so you're locking yourself out of expertise you could benefit from)

Your attitude is 'I am an expert, everyone else is an idiot' and that's the reason you're still failing. You ignore advices and your methodology is painfully wrong (you think it must be someone else's fault and every advice you follow is just to proof 'idiots being wrong' instead of thinking why other people have no problems with their devices).

 

There exist multiple reasons why an SBC 'can not access the network': device does not even boot (you showed this in a video titled 'network problems', most probably under-voltage), it does boot the wrong image (your Android screenshot), board suffers from under-voltage (you proved that at least the white cable you use is a pile of crap) or maybe under-current (no one knows which mistake you make this time) and there's also some network problem (you happily ignore and don't try to help me helping you).

 

Link to post
Share on other sites
22 minutes ago, blaster_56 said:

For power yeah you are right that the cable make lost some voltage, so i'v took my other power supply and i'v checked what voltage was on the pin of Orange Pi B

 

To illustrate that: If you were able to learn you would've taken the Multimeter with the same setup (white cable) and showed us the voltage available on pin headers. That way the supporters and developers here would be able to identify a general problem (minimum voltage an OPi Zero 1.4 has to be fed with). You do something else just to follow the 'I am an expert and everyone else is an idiot' route.

Link to post
Share on other sites

For the moderators: Please keep in mind that it's 2017 and the 'usual ways' to test for counterfeit SD cards might not work anymore: https://forum.armbian.com/index.php?/topic/4348-problems-with-apt-get-upgrade-on-cubietruck/

 

 

Not related with this thread (here it was just 'too smart to follow instructions' in the beginning) but as a general note what to expect when being confrontated with 'network problems' that might be just 'boards not booting' for whatever reasons.

Link to post
Share on other sites

You failed to burn images since 'too smart to follow instructions' :

I succefully write a broken image because i forgot to check the checksum of the builded image.

 

understanding of basics ('Chinese stuff magically appearing on your Armbian build' while you in reality just failed to boot the board from SD card and Android on eMMC took over) : I had 2 orange pi pc plus, i mistake between one of them that i already tested and ship aboard to my developper. (After severals hours of testing  writing etc my optimist mind was gone)

under-voltage happens in your setup -> Yeah with the white cable, but this dosnt explain why its not works with all the other power supply not undervoltage.

My attitude is legit, i'v test with 4 orange pi, 3 powersupply and 1 professional power supply, i'v checked my sd card, and you keep telling me hooo its ur power supply sd or other things like this. (Raspberry working 100% with this setup)

 

Its undervoltage with the white cable i agree 100%, but i did the same test with the  other power supply (see the screenshot i post)

 

So its deeper, its not about power or network or sd.

 

I'll buy new orange pi zero with power supply to see if 5 of my 5 orange pi are faulty.

About SD Test tell me which tool i should use to show you that its absolutly not my SD.

 

3 Other Questions : 

- About SD Test tell me which tool i should use to show you that its absolutly not my SD.
- Tell me which number you wanna see on pin 1 and 2 and i'll do
- Tell me which power supply i should buy

 

Now for today tell me exactly what you want i do

 

Regards

Link to post
Share on other sites
1 hour ago, blaster_56 said:

problem still the same wifi working ethernet is not working

 

Why can't you stop mixing everything up?! Last post here:

  • FIX your powering problems if not already done (you have some, it took me watching shitty videos to aprove this by showing you 'RPi 3 displaying under-voltage symbol'. If supply voltage of an RPi 3 constantly drops below 4.65V then you should visit http://www.cnx-software.com/2017/04/27/selecting-a-micro-usb-cable-to-power-development-boards-or-charge-phones/ -- this is THE THIRD TIME I POST THIS LINK IN THIS THREAD!).
  • FIX your SD card problems (obviously you did in the meantime)
  • Get a serial console (you said you got your boards 2 months ago, next time you suffer please ask first since this would've been the first thing a supporter recommends. Do a web search for 'ebay cp2102 site:armbian.com', some sellers are pretty fast with delivering)

After successfully leaving this area it starts to make some sense to look for real problems. As already told there is one in your network. DNS resolution on your OPi Zero is not working for whatever reasons, on your Windows box the configuration is insanely complex, you mentioning ethtool switching to 100 Mbits/sec would 'fix something' is a clear sign of 'fiddle around with network settings without knowing what I do' (you won't understand but switching on and off WiFi on a board that's connected with both eth0 and wlan0 to the same AP/router is just a mess) and so on.

 

It's useless to continue at this level but thanks to the various videos I wasted my time watching at least there's clear evidence where 'the problem' originates from.

 

Link to post
Share on other sites

@tkaiser do you understand that i have 3 power supply ?

 

Undervoltage is only appear because of the white cable i never seen this sign with my other power supply

Which sd card problems ? I never had sd card problem.

 

I ask again : 

- Which voltage i should have at pin 1 and 2 on my orange pi zero ?

Its useless to continue for you because you cannot provide rational answers.

Today i will ask my network enginer to make a report, then you will stop to annoying me with network.

Shitty video ? Its proof of everything, i will do another one with exactly 5V on the orange pi zero.

What is the answer for the broken PI ? SD card Problem too ?

 

Regards

Link to post
Share on other sites

I personally think that 4.80v at the rpi header is too low, especially if the Orange Pi Zero was unloaded when you measured the voltage. 

 

As a comparison for you, I just ran up a freshly downloaded build of Armbian 5.30 Debian Jessie  onto a not great, but reliable microSD (I know tkaiser will be spitting chips when I say this... Sandisk Class 10 8GB - the red and grey type - it's what I had handy - but I usually use tested Samsung EVO cards - as quality cards is important). I used a power supply set to 5.30v, and a known good quality 1m microUSB lead. I loaded it up, checked the voltage at pins 1 & 2 of the 13 pin header - 5.20v when the power supply had dropped to 5.29... still well above the danger levels. I then enabled the wifi, pinged google. It worked fine. I then disabled the WiFi, plugged in the ethernet (connected to a GbE router/modem, but since Orange Pi Zero is limited to 100Mb isn't really relavant), tried pinging google again, and it worked fine again. I rebooted, left the wifi off, and tested the ethernet. Again no problem. I then ran a stress -c 4 to see what the voltage at the headers was on the orange pi zero. measured 5.08v - so it was a good thing I started off with 5.30v wasn't it! Cable and voltage is important.  Finally, the really test - would SSH work. In the mean time, I had run "sudo apt update && sudo apt upgrade" to upgrade the system to 5.31, so you'll see the warning message. But, I logged into to the ssh using 'ssh -l pfeerick 192.168.0.54' without any issue.

 

So you see, there is something peculiar going on here... as we have conflicting reports of 5.30 Jessie not working... Igor tested it, and it worked. So does my set up. I'll test it on a second OPi Zero just for kicks, but I doubt it will play up. So we are left with it being hardware, either the board, the power, or the microSD. And power/microSD are the top two issues that people don't realise is the problem. So please forgive the more experience people here on the forum when they get testy... it's just they've seen it again, and again, and again... along with the "it can't be this" and the "it can't be that"... when it fact it can be and most often is. 

 

So where does this leave us? I'm not sure yet. But you can see.. it's not as cut and dry as "the image is broken"... because if the image was broken, I wouldn't be able to show you this (serial terminal in the background, ssh session in the foreground):

 

orange-pi-zero-jessie-530.thumb.png.b97f3642c844468281be4d20084edda2.png

 

 

Orange Pi Zero Armbian 5.30 Jessie (first boot, wifi enabled and checked then disabled, then ethernet enabled/checked):

 

Spoiler

Linux orangepizero 3.4.113-sun8i #16 SMP PREEMPT Tue Jun 13 14:15:57 CEST 2017 armv7l
  ___                               ____  _   _____
 / _ \ _ __ __ _ _ __   __ _  ___  |  _ \(_) |__  /___ _ __ ___
| | | | '__/ _` | '_ \ / _` |/ _ \ | |_) | |   / // _ \ '__/ _ \
| |_| | | | (_| | | | | (_| |  __/ |  __/| |  / /|  __/ | | (_) |
 \___/|_|  \__,_|_| |_|\__, |\___| |_|   |_| /____\___|_|  \___/
                       |___/

Welcome to ARMBIAN 5.30 stable Debian GNU/Linux 8 (jessie) 3.4.113-sun8i
System load:   1.13 0.31 0.10   Up time:       0 min
Memory usage:  11 % of 494MB    IP:            192.168.0.53
CPU temp:      49°C             
Usage of /:    15% of 7.2G      

[ General system configuration: armbian-config ]

pfeerick@orangepizero:~$ sudo ifconfig

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

[sudo] password for pfeerick:

eth0      Link encap:Ethernet  HWaddr 0e:7a:b9:f7:b8:e3
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:678 (678.0 B)
          Interrupt:114

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:136 errors:0 dropped:0 overruns:0 frame:0
          TX packets:136 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:11472 (11.2 KiB)  TX bytes:11472 (11.2 KiB)

wlan0     Link encap:Ethernet  HWaddr dc:44:6d:6d:50:23
          inet addr:192.168.0.53  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::de44:6dff:fe6d:5023/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:114 errors:0 dropped:0 overruns:0 frame:0
          TX packets:63 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:21240 (20.7 KiB)  TX bytes:6864 (6.7 KiB)

pfeerick@orangepizero:~$ ping www.google.com.au
PING www.google.com.au (216.58.196.131) 56(84) bytes of data.
64 bytes from www.google.com.au (216.58.196.131): icmp_seq=1 ttl=54 time=41.1 ms
64 bytes from www.google.com.au (216.58.196.131): icmp_seq=2 ttl=54 time=94.6 ms
64 bytes from www.google.com.au (216.58.196.131): icmp_seq=3 ttl=54 time=202 ms
64 bytes from www.google.com.au (216.58.196.131): icmp_seq=4 ttl=54 time=93.8 ms
64 bytes from www.google.com.au (216.58.196.131): icmp_seq=5 ttl=54 time=151 ms
^C
--- www.google.com.au ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 41.113/116.737/202.706/55.350 ms

#unplug the wifi, ethernet not plugged in yet

pfeerick@orangepizero:~$ sudo ifconfig
eth0      Link encap:Ethernet  HWaddr 0e:7a:b9:f7:b8:e3
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:678 (678.0 B)
          Interrupt:114

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:136 errors:0 dropped:0 overruns:0 frame:0
          TX packets:136 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:11472 (11.2 KiB)  TX bytes:11472 (11.2 KiB)

# plug in the ethernet

pfeerick@orangepizero:~$ sudo ifconfig
eth0      Link encap:Ethernet  HWaddr 0e:7a:b9:f7:b8:e3
          inet addr:192.168.0.54  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::c7a:b9ff:fef7:b8e3/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:17 errors:0 dropped:0 overruns:0 frame:0
          TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1668 (1.6 KiB)  TX bytes:2550 (2.4 KiB)
          Interrupt:114

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:136 errors:0 dropped:0 overruns:0 frame:0
          TX packets:136 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:11472 (11.2 KiB)  TX bytes:11472 (11.2 KiB)

pfeerick@orangepizero:~$ sudo ping www.google.com.au
PING www.google.com.au (216.58.196.131) 56(84) bytes of data.
64 bytes from www.google.com.au (216.58.196.131): icmp_seq=1 ttl=54 time=39.6 ms
64 bytes from www.google.com.au (216.58.196.131): icmp_seq=2 ttl=54 time=38.3 ms
64 bytes from www.google.com.au (216.58.196.131): icmp_seq=3 ttl=54 time=42.5 ms
64 bytes from www.google.com.au (216.58.196.131): icmp_seq=4 ttl=54 time=38.5 ms
64 bytes from www.google.com.au (216.58.196.131): icmp_seq=5 ttl=54 time=38.9 ms
^C
--- www.google.com.au ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4007ms
rtt min/avg/max/mdev = 38.396/39.619/42.578/1.543 ms

 

 

 

 

 

Orange Pi Zero Armbian Debian Jessie 5.30 second boot, wifi disabled, ethernet only:

Spoiler

Last login: Thu Jun 22 11:02:30 CEST 2017 on ttyS0
Linux orangepizero 3.4.113-sun8i #16 SMP PREEMPT Tue Jun 13 14:15:57 CEST 2017 armv7l
  ___                               ____  _   _____              
 / _ \ _ __ __ _ _ __   __ _  ___  |  _ \(_) |__  /___ _ __ ___  
| | | | '__/ _` | '_ \ / _` |/ _ \ | |_) | |   / // _ \ '__/ _ \ 
| |_| | | | (_| | | | | (_| |  __/ |  __/| |  / /|  __/ | | (_) |
 \___/|_|  \__,_|_| |_|\__, |\___| |_|   |_| /____\___|_|  \___/ 
                       |___/                                     

Welcome to ARMBIAN 5.30 stable Debian GNU/Linux 8 (jessie) 3.4.113-sun8i   
System load:   0.64 0.15 0.05   Up time:       0 min
Memory usage:  9 % of 494MB     IP:            
CPU temp:      48�°C           
Usage of /:    15% of 7.2G   

[ 0 security updates available, 42 updates total: apt upgrade ]
Last check: 2017-06-22 11:23

[ General system configuration: armbian-config ]

pfeerick@orangepizero:~$ sudo ifconfig
[sudo] password for pfeerick: 
eth0      Link encap:Ethernet  HWaddr 0e:7a:b9:f7:b8:e3  
          inet addr:192.168.0.54  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::c7a:b9ff:fef7:b8e3/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:35 errors:0 dropped:0 overruns:0 frame:0
          TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:3389 (3.3 KiB)  TX bytes:2858 (2.7 KiB)
          Interrupt:114 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:200 errors:0 dropped:0 overruns:0 frame:0
          TX packets:200 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:16656 (16.2 KiB)  TX bytes:16656 (16.2 KiB)

pfeerick@orangepizero:~$ sudo ping www.google.com.au
PING www.google.com.au (216.58.203.99) 56(84) bytes of data.
64 bytes from ssl.gstatic.com (216.58.203.99): icmp_seq=1 ttl=54 time=39.2 ms
64 bytes from ssl.gstatic.com (216.58.203.99): icmp_seq=2 ttl=54 time=38.9 ms
64 bytes from ssl.gstatic.com (216.58.203.99): icmp_seq=3 ttl=54 time=42.5 ms
64 bytes from ssl.gstatic.com (216.58.203.99): icmp_seq=4 ttl=54 time=39.6 ms
^C
--- www.google.com.au ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 38.951/40.094/42.513/1.441 ms
pfeerick@orangepizero:~$ 

 

 

Link to post
Share on other sites
1 minute ago, blaster_56 said:

What is the answer for the broken PI ?

 

Maybe it simply is BROKEN? What about that? It would be already a huge step considering broken hardware being just broken hardware and not 'Armbian has a network problem' as you told us in the beginning (the video showing two OPi Zero, one not booting and titled 'network problem' or something like that -- you deleted or have hidden that video in the meantime? If so that sucks even more)

 

 Please provide your videos to whoever you bought this cheap hardware from for them to get an understanding about your 'ESD awareness', will help not refunding you definititely :)

Link to post
Share on other sites

I meant to mention - have you thought of trying the reverse? You keep trying to ping your Orange Pi zero, which appears to be 192.168.1.40.  What is the device at 192.168.1.1 you're trying to ping? Your router? your laptop? If it isn't, try pinging your laptops IP... if the Orange Pi Zero can't see it... then how do you expect to be able to ssh into your orange pi zero? One of the major problems here is that you only give us part of the information, and we have to guess the rest. We aren't clairvoyant... we don't know what testing and knowledge you do have.  We're just ordinary guys and gals who want to help other people. 

 

Look at this image (which I googled) and see what voltage you think should be on pins 1 and 2 of the 13 pin header:

 

Orange-Pi-Zero-Pinout-banner2.jpg?resize=702%2C336&ssl=1

 

Link to post
Share on other sites

some more numbers on pin 1&2 that are working (setup: orangepi zero rev. 1.4, micro USB powered, samsung evo32gb, headless ssh over LAN, with NRF24l01 radio module):

opi in idle modus: 5.16V

running cpu-miner: 5.12V

 

Edit:

Just tried to create a underpower situation on my opi zero (not easy when you throw away most of the bad usb chargers& cables). 

I got finally it with an old sony mobile phone charger and a thin noname 1m cable. Without any load on it delivers exactly 5.00V on its output (measured with a Keweisi USB powermeter). Connecting it to the opi zero voltage drops to arround ~4.8V on the USB output and ~4.5V on pin 1&2, which result in no proper startup of the opi. 
Things that indecate that opi 0 doesn't startup properly: 
-The LED (D7) does not shine (green one)
-The Opi 0 gets unexpectable hot (disconnected it after 1min to avoid burnig something on my board)

I don't wanna watch all your videos to see if D7 LED shines when you power the board but it's up to you to do that.

Link to post
Share on other sites

I'v made some test and result are strange.

 

For the test i'v put my laptop under linux live cd.

 

IX_Oy0BpRNKRjFiv0KmYoQ.png

 

zuCppDnzQaCe656AoHkO-w.png

 

 

In ethernet to ethernet i can ping from my laptop to orange pi, thing i cannot do from my laptop in wifi to orange pi, but i can do the both with my pi.

 

I really dont understand where it come from, tonight i'll go deeper about the networks test with my Engineer.

 

Regards

 

 

Link to post
Share on other sites

Ok I will add more noise. I spent some time looking at the "failed" build I reported. Turns out I have a SD card which "works fine" but will fail in the PC Plus and 2 out 6 zeros. BUT only those. And yes I swapped everything around and retested, and no I did not make videos.

Link to post
Share on other sites
5 minutes ago, martinayotte said:

Of course you had some problems, otherwise, you would not posted that Chinese Android screenshot !
 

Does he have a USB Serial to debug ? :lol:

Seriously it not funny at all, i waste many days for this trouble, i use orange pi only because of EMMC thing i cannot find at acceptable price on Raspberry.

 

If orange pi worked same as raspberry, i already release my project.

 

You never did mistake? I can tell you that when you receive a first orange PI who's faulty, second who booting but no internet, third no internet, fourth no internet, and you plug your raspberry pi and everything working perfectly in the second, you just getting mad to looking for the problem. Yeah i'v build an image and then i try to put this image via ftp to my main machine, and the image was faulty, i tried several times but without checking the checksum, how many chance to get a a faulty pi, and how many chance to get permanent writing problem between VM and your main computer using FTP protocol ?

 

So yes i'v mistake on this one but its not a reason to make all the problem i face to "minimalist".

 

I Have serious issue with my Orange PI and Internet on Ethernet Interfaces... Its a fact

 

Regards

Link to post
Share on other sites
Guest
This topic is now closed to further replies.