Jump to content

Recommended Posts

Posted

Hello,

 

First of all thanks for the very nice dist, it's clean and optimized.

 

Unfortunately the Banana Pi is unbootable after having done the following:

 

  • Migrate the root fs to my USB drive and make it bootable with the nand-sata-install  script
  • Change the hostname (modify /etc/hosts, modify /etc/hostname, run /etc/init.d/hostname.sh, reboot)
  • run apt-get update && apt-get dist-upgrade, reboot

Each time the Banana Pi could not boot anymore, and that happened with both Jessie and Wheezie images.

 

I can't get any screenshots of the boot screen because it's a headless server.

 

Any ideas?

 

mk16

Posted

Thanks!

 

I'll check this ASAP.

 

Please tell me which kernel have you used, legacy 3.4.110 or vanilla? You probably used latest images (v4.5) ?

Posted

I've used those two vanilla images, v4.5 indeed:

 

 Wheezy & Jessie

 

When I did a dist-upgrade, the kernel was updated from 4.2.3 to 4.3.3, here's the /boot dir after the upgrade:

 

root@bananapi:/boot# ls -al

total 7572

drwxr-xr-x  5 root root    4096 Jan 19 21:31 .

drwxr-xr-x 22 root root    4096 Jan 19 21:12 ..

drwxr-xr-x  2 root root    4096 Jan 19 21:28 bin

-rw-r--r--  1 root root    6944 Oct 11 19:10 boot.bmp

-rw-r--r--  1 root root    1896 Jan 19 21:17 boot.cmd

-rw-r--r--  1 root root    1968 Jan 19 21:33 boot.scr

-rw-r--r--  1 root root  122375 Dec 28 11:27 config-4.3.3-sunxi

drwxr-xr-x  2 root root   12288 Jan 19 21:26 dtb

drwxr-xr-x  2 root root    4096 Dec 28 11:27 dtb.old

-rw-r--r--  1 root root       0 Jan 19 21:29 .next

lrwxrwxrwx  1 root root      22 Oct 11 19:11 script.bin -> /boot/bin/bananapi.bin

-rw-r--r--  1 root root 1988477 Dec 28 11:27 System.map-4.3.3-sunxi

-rwxr-xr-x  1 root root 5591872 Dec 28 11:27 vmlinuz-4.3.3-sunxi

lrwxrwxrwx  1 root root      19 Jan 19 21:29 zImage -> vmlinuz-4.3.3-sunxi

Posted

It refuses to stay on Y :) ... I think it's something related to recent changes in USB area with OTG intro ... 

 

I try few combinations but no luck.

Posted

Should I pin the kernel packages to the 4.2.3 version for the time being?

 

I'm planning in the near future to boot from SATA, I suppose I won't be affected by the issue then?

 

Thanks for the quick answers btw :)

Posted

Yes, rather roll back to 4.2.3 until this is resolved.

 

SATA booting is working fine on all kernels.

Posted (edited)

Great! I don't recall precisely the command, is it debuild? For now I've exluded the following packages from upgrade:

 

hi  linux-dtb-next-sunxi            4.5                               armhf        Linux DTB, version 4.2.3-sunxi
hi  linux-firmware-image-next-sunxi 4.5                               armhf        Linux kernel firmware, version 4.2.3-sunxi
hi  linux-headers-next-sunxi        4.5                               armhf        Linux kernel headers for 4.2.3-sunxi on armhf
hi  linux-image-next-sunxi          4.5                               armhf        Linux kernel, version 4.2.3-sunxi
hi  linux-wheezy-root-next-bananapi 4.5                               armhf        Various root file system tweaks for ARM boards
 

Should I compile only the image package?

Edited by mk16
Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines