Mikhail Posted October 19, 2018 Posted October 19, 2018 (edited) So I have been struggling with my new Orange Pi Zero the last couple of days, I tried everything but was unable to get it working. I followed all debugging steps I could find through google and through this form so i am at the end of the rode. I have tried 2 different SD cards, on which I ran h2testw 1.4 with the following result: Spoiler Card 1: Test finished without errors. You can now delete the test files *.h2w or verify them again. Writing speed: 20.3 MByte/s Reading speed: 63.9 MByte/s H2testw v1.4 Card 2: Test finished without errors. You can now delete the test files *.h2w or verify them again. Writing speed: 19.9 MByte/s Reading speed: 64.7 MByte/s H2testw v1.4 Used 2 different power supplies, one of which is rated at 3A 5V and I use for my raspberry pi, so I know for certain this cant be the problems. I have used the following Image without problems: "Armbian_5.25_Orangepizero_Ubuntu_xenial_default_3.4.113.img" But any new image I try gives me problems, I have tried so far: Armbian_5.59_Orangepizero_Ubuntu_bionic_next_4.14.65.img Armbian_5.59_Orangepizero_Debian_stretch_next_4.14.65.img Armbian_5.59_Orangepizero_Ubuntu_xenial_default_3.4.113.img All burned and verified with Ether v1.4.5 without problem, but I was unable to get an IP assigned by my Router (On any of those builds above) and thus unable to login though ssh. So I ordered the following USB to TLL module from amazon but was unable to get it working (On both Windows/Ubuntu): Anpro 2 x CP2102 USB to TTL Converter This is how I wired it (According to the howto's I found in other threads: TXD -> RX, RXD -> TX, GND -> GND (As can be seen in the photos below) https://imgur.com/a/9fI10At and after that used the following command as root: screen /dev/ttyUSB0 115200, which gave me no output. I also tried it on PUTTY but also no output. If i missed any debug steps please let me know because I am out of idea's. Edited October 19, 2018 by Mikhail
chwe Posted October 19, 2018 Posted October 19, 2018 9 minutes ago, Mikhail said: I have tried 2 different SD cards, on which I ran h2testw 1.4 with the following result: Hide contents Card 1: Test finished without errors. You can now delete the test files *.h2w or verify them again. Writing speed: 20.3 MByte/s Reading speed: 63.9 MByte/s H2testw v1.4 Card 2: Test finished without errors. You can now delete the test files *.h2w or verify them again. Writing speed: 19.9 MByte/s Reading speed: 64.7 MByte/s H2testw v1.4 full card was tested? 11 minutes ago, Mikhail said: https://imgur.com/a/9fI10At seems it gots recognized in ubuntu so, there you go: the wiring looks correct. 14 minutes ago, Mikhail said: Armbian_5.59_Orangepizero_Debian_stretch_next_4.14.65.img 'should' work. Cause I burned and booted this image multiple times on my orange pi zero. 14 minutes ago, Mikhail said: If i missed any debug steps please let me know because I am out of idea's. if you own a multimeter, measure voltage between GND and 5V on the pin-header. The RPi can throttle if voltage isn't sufficient, the OPi Zero doesn't recognize it.
Mikhail Posted October 19, 2018 Author Posted October 19, 2018 Thank you for your fast reaction, sadly I won't have much time left today to follow all your steps, but I will try to respond as quickly as possible. Quote full card was tested? Yes full card (16gb), it was fully formatted by SD Card Formatter before hand. Quote I see you are using something with a ch341 Chipset, you think this might be the problem? (That I purchased the wrong type of USB to TLL adapter?) I will try to repeat those steps 1 on 1 tomorrow, since I don't have any time left today. Quote if you own a multimeter, measure voltage between GND and 5V on the pin-header. The RPi can throttle if voltage isn't sufficient, the OPi Zero doesn't recognize it. I sadly do not, but I do have an USB power meter, and it tells me the voltage is around 5.1V from the power cable. (And it works with both my Raspberry Pi and Other version of Armbian. Do you think it might have something to do with my network configuration? (I have a router provided by our ISP on subnet 192.168.1.0/24 and another router with the subnet 192.168.0.0/24 (To which the orange pi zero is connect), that something with DHCP handling is different in the new ubuntu version?)
chwe Posted October 19, 2018 Posted October 19, 2018 10 minutes ago, Mikhail said: I see you are using something with a ch341 Chipset, you think this might be the problem? (That I purchased the wrong type of USB to TLL adapter?) mhmm no.. the picture of your dmesg output shows it get's recognized.. I assume @martinayotte uses those CP thingies too.. And somewhre there should also be a CP one here.. but it's like your house keys, once you've more than one they get lost.. 14 minutes ago, Mikhail said: I sadly do not, but I do have an USB power meter, and it tells me the voltage is around 5.1V from the power cable. (And it works with both my Raspberry Pi and Other version of Armbian. well voltage drop can happen over the cable you use (it looks thick.. but who knows if it's just a bunch plastic or some thick wires inside.. You can connect a 'small consumer' (e.g. wifi stick, mouse, whatever you have ) to your powermeter and connect it on your OPi Zero's USB port.. this should also give you some insights how much 'juice' is available on your board.
martinayotte Posted October 19, 2018 Posted October 19, 2018 4 hours ago, chwe said: I assume @martinayotte uses those CP thingies too I think I've one somewhere, but most of my USB-TTL dongles are PL2303 or CH340, and few FTDI ...
Mikhail Posted October 20, 2018 Author Posted October 20, 2018 Quote well voltage drop can happen over the cable you use (it looks thick.. but who knows if it's just a bunch plastic or some thick wires inside.. You can connect a 'small consumer' (e.g. wifi stick, mouse, whatever you have ) to your powermeter and connect it on your OPi Zero's USB port.. this should also give you some insights how much 'juice' is available on your board. I have tested it and this are the results: Without load: 5.14V from Usb port. With 0.5A load: 4.94V Pictures: https://imgur.com/a/v1ztud9 I also followed your guide for connecting the CP2102 USB to TTL Converter, but still was unable to produce any output from the orange pi zero. I have ordered a FT232RL Module that hopefully will work with the serial interface. If you have any other things I could try please let me know, because I really don't know what is going wrong Edit: All the steps from your tutorial: https://imgur.com/a/9IET3MF
Mikhail Posted October 20, 2018 Author Posted October 20, 2018 I tried it once again with a FT232RL that I could borrow from my father and this is the result: https://imgur.com/a/3r65JRr I am still clueless about what is going on, so any help would be really appreciated.
Mikhail Posted October 21, 2018 Author Posted October 21, 2018 Ok I don't know why, but I reflashed the image another time and got serial to work, only problem now: I can't send any commands through serial so I am unable to use the console: https://imgur.com/a/J47uyMI
chwe Posted October 21, 2018 Posted October 21, 2018 14 hours ago, Mikhail said: I tried it once again with a FT232RL that I could borrow from my father looks like the same one I use mostly.. Never had issues with it.. (be aware, there are a bunch of fake FTDIs, actually mine was to cheap to be an original one but it works.. ) check if it's set to 3.3V (I don't know if 5V can fry it but I wouldn't test it) replace the wires (unlikely but who knows) from the wiring it looks correct but check it again connect RX to TX on the FDTI (without a board) start putty and type some chars.. if both LEDs blink up every-time the FDTI should work. (then it messes somewhere else) 1 hour ago, Mikhail said: Ok I don't know why, but I reflashed the image another time sounds like an SD/powering card issue, even when you verified that the cards aren't corrupted if boot/no boot isn't reliable... 1 hour ago, Mikhail said: https://imgur.com/a/J47uyMI can be used for adding code into a post.. you don't need to make print-screens, just copy paste the the console output.. and it looks 'mostly' well formated.
Mikhail Posted October 22, 2018 Author Posted October 22, 2018 Edit: TLDR: 4 out of the 8 cables that were supplied with the FDTI were broken, The Orange Pi Zero RX pin is probably broken (Lamp on FDTI turns off), Ethernet problem is fixed by manually going into Armbian-Config, still not sure what is causing no ip to be assigned on boot of device. 22 hours ago, chwe said: replace the wires (unlikely but who knows) connect RX to TX on the FDTI (without a board) start putty and type some chars.. if both LEDs blink up every-time the FDTI should work. (then it messes somewhere else) I actually did this (Thanks great debug methode!) and found out that 4 of the 8 cables that they send me didn't make good contact with the FDTI. So I selected the 4 working cables, which worked when connecting the RX and TX together on the FDTI (And echoed the input). And I think I figured out part of the issue: The RX pin of the Orange Pi Zero is broken, because I borrowed the same Orange Pi Zero from a friend of mine and with the same SD card, Power Cable and Setup it did work[ (Including login in as root). Log of Orange Pi Zero without working RX pin: (The send lamp on the FDTI stops working once I connect the cable to both ends). Spoiler U-Boot SPL 2018.05-armbian (Aug 21 2018 - 21:44:47 +0200) DRAM: 512 MiB Trying to boot from MMC1 U-Boot 2018.05-armbian (Aug 21 2018 - 21:44:47 +0200) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Zero DRAM: 512 MiB MMC: SUNXI SD/MMC: 0 Loading Environment from EXT4... ** File not found /boot/boot.env ** ** Unable to read "/boot/boot.env" from mmc0:1 ** Failed (-5) In: serial Out: serial Err: serial Net: phy interface0 eth0: ethernet@1c30000 230454 bytes read in 31 ms (7.1 MiB/s) Unknown command 'bmp' - try 'help' starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 scanning bus 0 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 3708 bytes read in 12 ms (301.8 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 626 bytes read in 10 ms (60.5 KiB/s) 8303689 bytes read in 650 ms (12.2 MiB/s) 6979384 bytes read in 549 ms (12.1 MiB/s) Found mainline kernel configuration 32098 bytes read in 81 ms (386.7 KiB/s) ** File not found /boot/dtb/overlay/-fixup.scr ** ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 8303625 Bytes = 7.9 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Loading Ramdisk to 49814000, end 49fff409 ... OK reserving fdt memory region: addr=43000000 size=6e000 Loading Device Tree to 497a3000, end 49813fff ... OK Starting kernel ... Loading, please wait... starting version 237 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Will now check root file system ... fsck from util-linux 2.31.1 [/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1 /dev/mmcblk0p1: recovering journal /dev/mmcblk0p1: clean, 35929/906240 files, 243172/3849616 blocks done. done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... done. Welcome to Ubuntu 18.04.1 LTS! [ OK ] Set up automount Arbitrary Executab…rmats File System Automount Point. [ OK ] Reached target System Time Synchronized. [ OK ] Created slice User and Session Slice. [ OK ] Started Dispatch Password Requests to Console Directory Watch. [ OK ] Started Forward Password Requests to Wall Directory Watch. [ OK ] Reached target Swap. [ OK ] Created slice System Slice. [ OK ] Listening on Journal Socket. Starting Load Kernel Modules... [ OK ] Reached target Slices. [ OK ] Listening on Syslog Socket. Starting Nameserver information manager... [ OK ] Listening on udev Kernel Socket. [ OK ] Listening on /dev/initctl Compatibility Named Pipe. Mounting POSIX Message Queue File System... [ OK ] Listening on Journal Socket (/dev/log). [ OK ] Listening on fsck to fsckd communication Socket. [ OK ] Reached target Local Encrypted Volumes. [ OK ] Reached target Remote File Systems. Starting Remount Root and Kernel File Systems... [ OK ] Listening on udev Control Socket. Starting udev Coldplug all Devices... Starting Set the console keyboard layout... [ OK ] Listening on Journal Audit Socket. Starting Journal Service... [ OK ] Created slice system-serial\x2dgetty.slice. [ OK ] Started ntp-systemd-netif.path. Starting Create list of required st…ce nodes for the current kernel... Starting Restore / save the current clock... Mounting Kernel Debug File System... [ OK ] Started Load Kernel Modules. [ OK ] Mounted POSIX Message Queue File System. [ OK ] Started Remount Root and Kernel File Systems. [ OK ] Started Create list of required sta…vice nodes for the current kernel. [ OK ] Started Restore / save the current clock. [ OK ] Mounted Kernel Debug File System. [ OK ] Started Nameserver information manager. [ OK ] Started Journal Service. [ OK ] Reached target Network (Pre). Starting Create Static Device Nodes in /dev... Starting Flush Journal to Persistent Storage... Starting Load/Save Random Seed... Starting Apply Kernel Variables... Mounting Kernel Configuration File System... [ OK ] Mounted Kernel Configuration File System. [ OK ] Started Flush Journal to Persistent Storage. [ OK ] Started Load/Save Random Seed. [ OK ] Started Create Static Device Nodes in /dev. Starting udev Kernel Device Manager... [ OK ] Started Set the console keyboard layout. [ OK ] Started Apply Kernel Variables. [ OK ] Reached target Local File Systems (Pre). Mounting /tmp... [ OK ] Mounted /tmp. [ OK ] Reached target Local File Systems. Starting Create Volatile Files and Directories... Starting Set console font and keymap... Starting Armbian ZRAM config... Starting Raise network interfaces... [ OK ] Started udev Kernel Device Manager. [ OK ] Started Set console font and keymap. [ OK ] Started Create Volatile Files and Directories. [ OK ] Found device /dev/ttyGS0. Starting Network Time Synchronization... Starting Update UTMP about System Boot/Shutdown... Starting Network Name Resolution... [ OK ] Started Entropy daemon using the HAVEGE algorithm. [ OK ] Started udev Coldplug all Devices. [ OK ] Started Update UTMP about System Boot/Shutdown. [ OK ] Started Network Time Synchronization. [ OK ] Started Network Name Resolution. [ OK ] Reached target Host and Network Name Lookups. [ OK ] Found device /dev/ttyS0. [ OK ] Started Raise network interfaces. [ OK ] Started Armbian ZRAM config. [ OK ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch. Starting Armbian memory supported logging... Starting Load/Save RF Kill Switch Status... [ OK ] Started Load/Save RF Kill Switch Status. [ OK ] Started Armbian memory supported logging. [ OK ] Reached target System Initialization. [ OK ] Started Discard unused blocks once a week. [ OK ] Listening on D-Bus System Message Bus Socket. [ OK ] Reached target Sockets. [ OK ] Started Daily apt download activities. Starting Armbian hardware optimization... [ OK ] Started Daily apt upgrade and clean activities. [ OK ] Started resolvconf-pull-resolved.path. [ OK ] Reached target Paths. [ OK ] Started Message of the Day. [ OK ] Started Daily Cleanup of Temporary Directories. [ OK ] Reached target Timers. Starting Armbian hardware monitoring... [ OK ] Started Armbian hardware optimization. [ OK ] Started Armbian hardware monitoring. [ OK ] Reached target Basic System. [ OK ] Started Regular background program processing daemon. [ OK ] Started Set the CPU Frequency Scaling governor. Starting Login Service... Starting Resets System Activity Data Collector... Starting LSB: Load kernel modules needed to enable cpufreq scaling... [ OK ] Started D-Bus System Message Bus. Starting Network Manager... Starting System Logging Service... [ OK ] Started ntp-systemd-netif.service. Starting Dispatcher daemon for systemd-networkd... Starting resolvconf-pull-resolved.service... Starting WPA supplicant... [ OK ] Started Resets System Activity Data Collector. [ OK ] Started Login Service. [ OK ] Started resolvconf-pull-resolved.service. [ OK ] Started System Logging Service. [ OK ] Started LSB: Load kernel modules needed to enable cpufreq scaling. [ OK ] Started WPA supplicant. Starting LSB: set CPUFreq kernel parameters... [ OK ] Started LSB: set CPUFreq kernel parameters. Starting LSB: Set sysfs variables from /etc/sysfs.conf... [ OK ] Started LSB: Set sysfs variables from /etc/sysfs.conf. Starting Hostname Service... [ OK ] Started Hostname Service. [ OK ] Started Network Manager. Starting Network Manager Wait Online... [ OK ] Reached target Network. Starting OpenBSD Secure Shell server... [ OK ] Started Unattended Upgrades Shutdown. Starting Permit User Sessions... [ OK ] Started Permit User Sessions. Starting Set console scheme... Starting Network Manager Script Dispatcher Service... [ OK ] Started Set console scheme. [ OK ] Created slice system-getty.slice. [ OK ] Started Network Manager Script Dispatcher Service. [ OK ] Started OpenBSD Secure Shell server. Starting Authorization Manager... [ OK ] Started Authorization Manager. [ OK ] Started Dispatcher daemon for systemd-networkd. [ OK ] Started Network Manager Wait Online. [ OK ] Reached target Network is Online. Starting /etc/rc.local Compatibility... [ OK ] Started /etc/rc.local Compatibility. [ OK ] Started Serial Getty on ttyS0. [ OK ] Started Serial Getty on ttyGS0. [ OK ] Started Getty on tty1. [ OK ] Reached target Login Prompts. [ OK ] Reached target Multi-User System. [ OK ] Reached target Graphical Interface. Starting Update UTMP about System Runlevel Changes... [ OK ] Started Update UTMP about System Runlevel Changes. Ubuntu 18.04.1 LTS orangepizero ttyS0 orangepizero login: Log of working Orange Pi Zero: Spoiler U-Boot SPL 2018.05-armbian (Aug 21 2018 - 21:44:47 +0200) DRAM: 512 MiB Trying to boot from MMC1 U-Boot 2018.05-armbian (Aug 21 2018 - 21:44:47 +0200) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Zero DRAM: 512 MiB MMC: SUNXI SD/MMC: 0 Loading Environment from EXT4... ** File not found /boot/boot.env ** ** Unable to read "/boot/boot.env" from mmc0:1 ** Failed (-5) In: serial Out: serial Err: serial Net: phy interface0 eth0: ethernet@1c30000 230454 bytes read in 30 ms (7.3 MiB/s) Unknown command 'bmp' - try 'help' starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 scanning bus 0 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 3708 bytes read in 12 ms (301.8 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 626 bytes read in 10 ms (60.5 KiB/s) 8303689 bytes read in 654 ms (12.1 MiB/s) 6979384 bytes read in 552 ms (12.1 MiB/s) Found mainline kernel configuration 32098 bytes read in 82 ms (381.8 KiB/s) ** File not found /boot/dtb/overlay/-fixup.scr ** ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 8303625 Bytes = 7.9 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Loading Ramdisk to 49814000, end 49fff409 ... OK reserving fdt memory region: addr=43000000 size=6e000 Loading Device Tree to 497a3000, end 49813fff ... OK Starting kernel ... Loading, please wait... starting version 237 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Will now check root file system ... fsck from util-linux 2.31.1 [/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1 /dev/mmcblk0p1: recovering journal /dev/mmcblk0p1: clean, 35928/906240 files, 243171/3849616 blocks done. done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... done. Welcome to Ubuntu 18.04.1 LTS! [ OK ] Started ntp-systemd-netif.path. [ OK ] Created slice User and Session Slice. [ OK ] Reached target System Time Synchronized. [ OK ] Started Dispatch Password Requests to Console Directory Watch. [ OK ] Created slice System Slice. [ OK ] Listening on /dev/initctl Compatibility Named Pipe. [ OK ] Listening on fsck to fsckd communication Socket. [ OK ] Listening on Syslog Socket. [ OK ] Reached target Slices. [ OK ] Listening on Journal Socket (/dev/log). [ OK ] Listening on Journal Socket. Starting Nameserver information manager... Mounting Kernel Debug File System... Starting Load Kernel Modules... Starting Set the console keyboard layout... Mounting POSIX Message Queue File System... Starting Restore / save the current clock... [ OK ] Listening on udev Kernel Socket. [ OK ] Started Forward Password Requests to Wall Directory Watch. [ OK ] Reached target Local Encrypted Volumes. [ OK ] Listening on udev Control Socket. Starting udev Coldplug all Devices... Starting Create list of required st…ce nodes for the current kernel... Starting Remount Root and Kernel File Systems... [ OK ] Listening on Journal Audit Socket. Starting Journal Service... [ OK ] Reached target Remote File Systems. [ OK ] Set up automount Arbitrary Executab…rmats File System Automount Point. [ OK ] Created slice system-serial\x2dgetty.slice. [ OK ] Reached target Swap. [ OK ] Mounted Kernel Debug File System. [ OK ] Started Load Kernel Modules. [ OK ] Mounted POSIX Message Queue File System. [ OK ] Started Restore / save the current clock. [ OK ] Started Create list of required sta…vice nodes for the current kernel. [ OK ] Started Remount Root and Kernel File Systems. [ OK ] Started Nameserver information manager. [ OK ] Reached target Network (Pre). Starting Load/Save Random Seed... Starting Create Static Device Nodes in /dev... Mounting Kernel Configuration File System... Starting Apply Kernel Variables... [ OK ] Started Journal Service. [ OK ] Started Load/Save Random Seed. [ OK ] Mounted Kernel Configuration File System. Starting Flush Journal to Persistent Storage... [ OK ] Started Set the console keyboard layout. [ OK ] Started Flush Journal to Persistent Storage. [ OK ] Started Apply Kernel Variables. [ OK ] Started Create Static Device Nodes in /dev. Starting udev Kernel Device Manager... [ OK ] Reached target Local File Systems (Pre). Mounting /tmp... [ OK ] Mounted /tmp. [ OK ] Reached target Local File Systems. Starting Set console font and keymap... Starting Armbian ZRAM config... Starting Raise network interfaces... Starting Create Volatile Files and Directories... [ OK ] Started Set console font and keymap. [ OK ] Started udev Kernel Device Manager. [ OK ] Found device /dev/ttyGS0. [ OK ] Started Create Volatile Files and Directories. Starting Update UTMP about System Boot/Shutdown... Starting Network Name Resolution... Starting Network Time Synchronization... [ OK ] Started Entropy daemon using the HAVEGE algorithm. [ OK ] Started udev Coldplug all Devices. [ OK ] Started Update UTMP about System Boot/Shutdown. [ OK ] Started Network Time Synchronization. [ OK ] Started Network Name Resolution. [ OK ] Reached target Host and Network Name Lookups. [ OK ] Found device /dev/ttyS0. [ OK ] Started Raise network interfaces. [ OK ] Started Armbian ZRAM config. [ OK ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch. Starting Armbian memory supported logging... Starting Load/Save RF Kill Switch Status... [ OK ] Started Load/Save RF Kill Switch Status. [ OK ] Started Armbian memory supported logging. [ OK ] Reached target System Initialization. Starting Armbian hardware monitoring... [ OK ] Listening on D-Bus System Message Bus Socket. [ OK ] Reached target Sockets. [ OK ] Started Daily apt download activities. [ OK ] Started Discard unused blocks once a week. [ OK ] Started resolvconf-pull-resolved.path. [ OK ] Reached target Paths. [ OK ] Started Message of the Day. [ OK ] Started Daily apt upgrade and clean activities. Starting Armbian hardware optimization... [ OK ] Started Daily Cleanup of Temporary Directories. [ OK ] Reached target Timers. [ OK ] Started Armbian hardware optimization. [ OK ] Started Armbian hardware monitoring. [ OK ] Reached target Basic System. Starting Dispatcher daemon for systemd-networkd... Starting System Logging Service... Starting resolvconf-pull-resolved.service... [ OK ] Started D-Bus System Message Bus. [ OK ] Started Set the CPU Frequency Scaling governor. [ OK ] Started ntp-systemd-netif.service. Starting LSB: Load kernel modules needed to enable cpufreq scaling... [ OK ] Started Regular background program processing daemon. Starting Login Service... Starting Network Manager... Starting Resets System Activity Data Collector... Starting WPA supplicant... [ OK ] Started System Logging Service. [ OK ] Started resolvconf-pull-resolved.service. [ OK ] Started Resets System Activity Data Collector. [ OK ] Started Login Service. [ OK ] Started WPA supplicant. [ OK ] Started LSB: Load kernel modules needed to enable cpufreq scaling. Starting LSB: set CPUFreq kernel parameters... [ OK ] Started LSB: set CPUFreq kernel parameters. Starting LSB: Set sysfs variables from /etc/sysfs.conf... [ OK ] Started LSB: Set sysfs variables from /etc/sysfs.conf. Starting Hostname Service... [ OK ] Started Hostname Service. [ OK ] Started Network Manager. Starting Network Manager Script Dispatcher Service... Starting Network Manager Wait Online... [ OK ] Reached target Network. Starting OpenBSD Secure Shell server... [ OK ] Started Unattended Upgrades Shutdown. Starting Permit User Sessions... [ OK ] Started Permit User Sessions. [ OK ] Started Network Manager Script Dispatcher Service. Starting Set console scheme... [ OK ] Started Set console scheme. [ OK ] Created slice system-getty.slice. [ OK ] Started OpenBSD Secure Shell server. [ OK ] Started Dispatcher daemon for systemd-networkd. Starting Authorization Manager... [ OK ] Started Authorization Manager. [ OK ] Started Network Manager Wait Online. [ OK ] Reached target Network is Online. Starting /etc/rc.local Compatibility... [ OK ] Started /etc/rc.local Compatibility. [ OK ] Started Serial Getty on ttyGS0. [ OK ] Started Getty on tty1. [ OK ] Started Serial Getty on ttyS0. [ OK ] Reached target Login Prompts. [ OK ] Reached target Multi-User System. [ OK ] Reached target Graphical Interface. Starting Update UTMP about System Runlevel Changes... [ OK ] Started Update UTMP about System Runlevel Changes. Ubuntu 18.04.1 LTS orangepizero ttyS0 orangepizero login: So now about the Ethernet problems, the log of the working Orange Pi Zero: Spoiler orangepizero login: root Password: You are required to change your password immediately (root enforced) Changing password for root. (current) UNIX password: Enter new UNIX password: Retype new UNIX password: ___ ____ _ _____ / _ \ _ __ __ _ _ __ __ _ ___ | _ \(_) |__ /___ _ __ ___ | | | | '__/ _` | '_ \ / _` |/ _ \ | |_) | | / // _ \ '__/ _ \ | |_| | | | (_| | | | | (_| | __/ | __/| | / /| __/ | | (_) | \___/|_| \__,_|_| |_|\__, |\___| |_| |_| /____\___|_| \___/ |___/ Welcome to ARMBIAN 5.59 stable Ubuntu 18.04.1 LTS 4.14.65-sunxi System load: 0.56 0.14 0.05 Up time: 0 min Memory usage: 10 % of 493MB IP: CPU temp: 42°C Usage of /: 5% of 15G [ General system configuration (beta): armbian-config ] New to Armbian? Check the documentation first: https://docs.armbian.com Thank you for choosing Armbian! Support: www.armbian.com Creating a new user account. Press <Ctrl-C> to abort Please provide a username (eg. your forename): ^C Disabling user account creation procedure Ubuntu 18.04.1 LTS orangepizero ttyS0 orangepizero login: root Password: Last login: Sun Oct 21 10:06:56 UTC 2018 on ttyS0 ___ ____ _ _____ / _ \ _ __ __ _ _ __ __ _ ___ | _ \(_) |__ /___ _ __ ___ | | | | '__/ _` | '_ \ / _` |/ _ \ | |_) | | / // _ \ '__/ _ \ | |_| | | | (_| | | | | (_| | __/ | __/| | / /| __/ | | (_) | \___/|_| \__,_|_| |_|\__, |\___| |_| |_| /____\___|_| \___/ |___/ Welcome to ARMBIAN 5.59 stable Ubuntu 18.04.1 LTS 4.14.65-sunxi System load: 0.31 0.12 0.04 Up time: 1 min Memory usage: 10 % of 493MB IP: CPU temp: 44°C Usage of /: 5% of 15G root@orangepizero:~# ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::42:f5ff:fe1a:61c8 prefixlen 64 scopeid 0x20<link> inet6 2002:57d6:d85a:0:42:f5ff:fe1a:61c8 prefixlen 64 scopeid 0x0<global> ether 02:42:f5:1a:61:c8 txqueuelen 1000 (Ethernet) RX packets 35 bytes 2296 (2.2 KB) RX errors 0 dropped 29 overruns 0 frame 0 TX packets 7 bytes 602 (602.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 33 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 94 bytes 6760 (6.7 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 94 bytes 6760 (6.7 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether 12:42:f5:1a:61:c8 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 root@orangepizero:~# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface root@orangepizero:~# However, when I went to armbian-config -> Network -> eth0 -> IP -> DHCP, it got an IP and the internet is working now on the device.
Mikhail Posted October 22, 2018 Author Posted October 22, 2018 dmesg (incase it helps): Spoiler root@orangepizero:~# dmesg | grep ethernet [ 4.557565] dwmac-sun8i 1c30000.ethernet: PTP uses main clock [ 4.557639] dwmac-sun8i 1c30000.ethernet: No regulator found [ 4.557815] dwmac-sun8i 1c30000.ethernet: Current syscon value is not the default 148000 (expect 58000) [ 4.557844] dwmac-sun8i 1c30000.ethernet: Chain mode enabled [ 4.557856] dwmac-sun8i 1c30000.ethernet: No HW DMA feature register supported [ 4.557867] dwmac-sun8i 1c30000.ethernet: Normal descriptors [ 4.557879] dwmac-sun8i 1c30000.ethernet: RX Checksum Offload Engine supported [ 4.557890] dwmac-sun8i 1c30000.ethernet: COE Type 2 [ 4.557901] dwmac-sun8i 1c30000.ethernet: TX Checksum insertion supported [ 4.558889] dwmac-sun8i 1c30000.ethernet: Found internal PHY node [ 4.559070] dwmac-sun8i 1c30000.ethernet: Switch mux to internal PHY [ 4.559083] dwmac-sun8i 1c30000.ethernet: Powering internal PHY [ 13.106606] dwmac-sun8i 1c30000.ethernet eth0: No MAC Management Counters available [ 13.106623] dwmac-sun8i 1c30000.ethernet eth0: PTP not supported by HW [ 16.249823] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off
Mikhail Posted October 24, 2018 Author Posted October 24, 2018 Today I installed AdvancedTomato firmware on my Router (Netgear R8000) which had stock firmware prior, and now the OrangePiZero's get an IP assinged after flash, So I guess it was a network problem all along. Thanks for your help @chwe. 1
chwe Posted October 24, 2018 Posted October 24, 2018 some combination just don't like each other... Sometimes for no reason. 1
Mikhail Posted October 24, 2018 Author Posted October 24, 2018 2 hours ago, chwe said: some combination just don't like each other... Sometimes for no reason. Amen to that, technologie is sometimes weird...
Recommended Posts