Alsan Wong Posted September 17, 2016 Posted September 17, 2016 I've try to upgrade my pi to newest version of the system yesterday, but FAILED for both apt-get upgrade or by download and write the newest image. Here is my working log: 1. apt-upgrade from armbian 5.14 image - error message indicate there's error during the apt-get update process - reboot, the boot screen shows no bootup message, than begin the TFTP startup process - wait until TFTP timeout, the system halt. 2. download and write the newest **Armbian_5.20_Bananapipro_Ubuntu_xenial_4.7.3.7z** - can be startup with the boot screen, both power led and disk io led (green led) work as expected - system halt after a few second, the power led goes off - can power on the pi by long press the power button, but as same as the first boot, powered off a few seconds after power on - the message goes too fast, can't see what exact stage it reach Right now, I've to go back to the last working image (Armbian_5.14_Bananapipro_Ubuntu_xenial_4.6.2).
Igor Posted September 17, 2016 Posted September 17, 2016 1. If errors happen you need to deal with them before reboot. Now you need to unbrick it. 2. Armbian_5.20_Bananapipro_Ubuntu_xenial_4.7.3.7z works without a problem, tested. It's some problem on your side.
Alsan Wong Posted September 17, 2016 Author Posted September 17, 2016 for 1, that's acceptable answer. for 2, then why it can work while I go back to the old version?
Igor Posted September 18, 2016 Posted September 18, 2016 I would also like to understand what is going on, but it actually can be some hardware problem after all. If things are on the edge and our new build draw just a little more power it can crash on boot. I know this explanation might sound stupid but I would check cables / PSU. They are responsible for most (strange) problems.
tkaiser Posted September 18, 2016 Posted September 18, 2016 Banana Pro powered through the DC-IN Micro USB jack (not OTG), no peripherals connected, only network. The '/etc/init.d/brcm40183-patch' issue is present but everything else is working smoothly (running legacy kernel but this shouldn't matter if booting stops already in u-boot): macbookpro-tk:~ tk$ slogin 192.168.83.89 tk@192.168.83.89's password: ____ ____ _ ____ | __ ) __ _ _ __ __ _ _ __ __ _ | _ \(_) | _ \ _ __ ___ | _ \ / _` | '_ \ / _` | '_ \ / _` | | |_) | | | |_) | '__/ _ \ | |_) | (_| | | | | (_| | | | | (_| | | __/| | | __/| | | (_) | |____/ \__,_|_| |_|\__,_|_| |_|\__,_| |_| |_| |_| |_| \___/ Welcome to ARMBIAN Ubuntu 16.04.1 LTS 3.4.112-sun7i System load: 0.00 Up time: 14 hours IP: 192.168.83.89 CPU temp: 37°C Usage of /: 20% of 7.2G [ 18 updates to install: apt-get upgrade ] Last login: Sat Sep 17 17:34:58 2016 from 192.168.83.91 sudo -tk@bananapipro:~$ sudo -s [sudo] password for tk: root@bananapipro:~# cat /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=bananapipro BOARD_NAME="Banana Pi Pro" VERSION=5.16 LINUXFAMILY=sun7i BRANCH=default ARCH=arm root@bananapipro:~# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following package was automatically installed and is no longer required: libnl-route-3-200 Use 'sudo apt autoremove' to remove it. The following packages have been kept back: vim vim-common vim-runtime vim-tiny The following packages will be upgraded: armbian-firmware armbian-tools-xenial libnss-myhostname libpam-systemd libsystemd0 libudev1 linux-headers-sun7i linux-image-sun7i linux-u-boot-bananapipro-default linux-xenial-root-bananapipro systemd systemd-sysv udev 13 upgraded, 0 newly installed, 0 to remove and 4 not upgraded. Need to get 0 B/140 MB of archives. After this operation, 21.5 kB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 45578 files and directories currently installed.) Preparing to unpack .../systemd-sysv_229-4ubuntu8_armhf.deb ... Unpacking systemd-sysv (229-4ubuntu8) over (229-4ubuntu7) ... Processing triggers for man-db (2.7.5-1) ... Setting up systemd-sysv (229-4ubuntu8) ... (Reading database ... 45578 files and directories currently installed.) Preparing to unpack .../libpam-systemd_229-4ubuntu8_armhf.deb ... Unpacking libpam-systemd:armhf (229-4ubuntu8) over (229-4ubuntu7) ... Preparing to unpack .../libsystemd0_229-4ubuntu8_armhf.deb ... Unpacking libsystemd0:armhf (229-4ubuntu8) over (229-4ubuntu7) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for libc-bin (2.23-0ubuntu3) ... Setting up libsystemd0:armhf (229-4ubuntu8) ... Processing triggers for libc-bin (2.23-0ubuntu3) ... (Reading database ... 45578 files and directories currently installed.) Preparing to unpack .../libnss-myhostname_229-4ubuntu8_armhf.deb ... Unpacking libnss-myhostname:armhf (229-4ubuntu8) over (229-4ubuntu7) ... Preparing to unpack .../systemd_229-4ubuntu8_armhf.deb ... Unpacking systemd (229-4ubuntu8) over (229-4ubuntu7) ... Processing triggers for libc-bin (2.23-0ubuntu3) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for dbus (1.10.6-1ubuntu3) ... Setting up systemd (229-4ubuntu8) ... addgroup: The group `systemd-journal' already exists as a system group. Exiting. (Reading database ... 45578 files and directories currently installed.) Preparing to unpack .../udev_229-4ubuntu8_armhf.deb ... Unpacking udev (229-4ubuntu8) over (229-4ubuntu7) ... Preparing to unpack .../libudev1_229-4ubuntu8_armhf.deb ... Unpacking libudev1:armhf (229-4ubuntu8) over (229-4ubuntu7) ... Processing triggers for systemd (229-4ubuntu8) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for libc-bin (2.23-0ubuntu3) ... Setting up libudev1:armhf (229-4ubuntu8) ... Processing triggers for libc-bin (2.23-0ubuntu3) ... (Reading database ... 45578 files and directories currently installed.) Preparing to unpack .../armbian-firmware_5.20_armhf.deb ... Unpacking armbian-firmware (5.20) over (5.14) ... Preparing to unpack .../armbian-tools-xenial_5.20_armhf.deb ... Unpacking armbian-tools-xenial (5.20) over (5.14) ... dpkg: error processing archive /var/cache/apt/archives/armbian-tools-xenial_5.20_armhf.deb (--unpack): trying to overwrite '/etc/init.d/brcm40183-patch', which is also in package linux-xenial-root-bananapipro 5.16 Preparing to unpack .../linux-headers-sun7i_5.20_armhf.deb ... Unpacking linux-headers-sun7i (5.20) over (5.17) ... Preparing to unpack .../linux-image-sun7i_5.20_armhf.deb ... Unpacking linux-image-sun7i (5.20) over (5.17) ... Preparing to unpack .../linux-u-boot-bananapipro-default_5.20_armhf.deb ... Unpacking linux-u-boot-bananapipro-default (5.20) over (5.16) ... Preparing to unpack .../linux-xenial-root-bananapipro_5.20_armhf.deb ... Unpacking linux-xenial-root-bananapipro (5.20) over (5.16) ... Processing triggers for systemd (229-4ubuntu8) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for initramfs-tools (0.122ubuntu8.1) ... update-initramfs: Generating /boot/initrd.img-3.4.112-sun7i Errors were encountered while processing: /var/cache/apt/archives/armbian-tools-xenial_5.20_armhf.deb E: Sub-process /usr/bin/dpkg returned an error code (1) root@bananapipro:~# apt-get install -f Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: libnl-route-3-200 Use 'sudo apt autoremove' to remove it. 0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded. 8 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up udev (229-4ubuntu8) ... addgroup: The group `input' already exists as a system group. Exiting. update-initramfs: deferring update (trigger activated) Setting up libpam-systemd:armhf (229-4ubuntu8) ... Setting up armbian-firmware (5.20) ... Setting up linux-headers-sun7i (5.20) ... Compiling headers - please wait ... Setting up linux-image-sun7i (5.20) ... update-initramfs: Generating /boot/initrd.img-3.4.112-sun7i Setting up linux-u-boot-bananapipro-default (5.20) ... Setting up linux-xenial-root-bananapipro (5.20) ... Setting up libnss-myhostname:armhf (229-4ubuntu8) ... Processing triggers for initramfs-tools (0.122ubuntu8.1) ... update-initramfs: Generating /boot/initrd.img-3.4.112-sun7i Processing triggers for libc-bin (2.23-0ubuntu3) ... root@bananapipro:~# reboot Connection to 192.168.83.89 closed by remote host. Connection to 192.168.83.89 closed. macbookpro-tk:~ tk$ slogin 192.168.83.89 tk@192.168.83.89's password: ____ ____ _ ____ | __ ) __ _ _ __ __ _ _ __ __ _ | _ \(_) | _ \ _ __ ___ | _ \ / _` | '_ \ / _` | '_ \ / _` | | |_) | | | |_) | '__/ _ \ | |_) | (_| | | | | (_| | | | | (_| | | __/| | | __/| | | (_) | |____/ \__,_|_| |_|\__,_|_| |_|\__,_| |_| |_| |_| |_| \___/ Welcome to ARMBIAN Ubuntu 16.04.1 LTS 3.4.112-sun7i System load: 0.91 Up time: 56 sec Memory usage: 2 % of 984Mb IP: 192.168.83.89 CPU temp: 40°C Usage of /: 20% of 7.2G [ 6 updates to install: apt-get upgrade ] Last login: Sun Sep 18 07:42:05 2016 from 192.168.83.91 tk@bananapipro:~$ sudo armbianmonitor -u [sudo] password for tk: /var/log/armhwinfo.log has been uploaded to http://sprunge.us/bEUa Please post the URL in the Armbian forum where you've been asked for. I would also suspect powering problems, especially when/if the wrong Micro USB jack is used (OTG instead of DC-IN) or an average cable is used (the cable here is 20cm long and 20AWG rated). Edit: I was wrong, am currently using the 2nd best method (5.5/2.1 barrel to Micro USB adapter) since i did some storage tests some days ago and it's known that Micro USB cabling is not reliable enough for this: Edit 2: Upgrading my vanilla installation on BPi Pro to latest also worked flawlessly (except of the /etc/init.d/brcm40183-patch 'issue'): http://sprunge.us/iYKc Here it looks like this when idle: root@bananapro:~# cat /sys/power/axp_pmu/ac/voltage 5193500 And when running cpuburn-a7: root@bananapro:~# cat /sys/power/axp_pmu/ac/voltage 5105100 Edit 3: Powering through USB OTG also works with vanilla image. But it still looks like this here (5.2V idle and nearly no voltage drops under load since I avoid bad cabling): tk@bananapro:~$ cat /sys/power/axp_pmu/vbus/voltage 5205400
Alsan Wong Posted September 24, 2016 Author Posted September 24, 2016 OK, confirmed to be the cabling problem. I've test not under 10 cables these days and finally got 3 of them worked. But I'm still can't understand why the cabel which can worked with the old image can't work now. Anyway, thanks everyone.
(Phone).thumb.jpg.f60309bb32d95d32f028a6642a35c6ea.jpg)
Recommended Posts