bombobrudi

Thnx for the hint - I will try. Update: nice - It is working now! Many thnx @tkaiser

Dear all, After having problems with the 5.04 armbian and kernel 4.4.3 I went ober to build my own image. Prepared an ubuntu 14.04 and built jessie image, xenial image, with the 3.x and 4.x kernel. After its not working I tried an ubuntu 16.04 system and built again all images. No single image will boot... No errors while the build process (default settings). Please find the boot messages in the image file here: https://www.dropbox.com/s/2kpddhdkh5czw91/image1.JPG?dl=0 Any idea, what the problem could be? Thanks, bb

Thnx for your reply Igor. Just want to be sure, the bootlog creation will start loggin AFTER I will activate it with armbianmonitor -b and after the reboot? Because If I reset while the preparing phase at the FIRST fresh boot, everything seems to work as normal... Does it make sense then? Thnx againg, bb

Hi all. Strange thing happens. I've tried to run a fresh installation of the 4.4.3 kernel version of armbian 5.04. The first boot takes forever (I gave up after 2 hours; a few times). It started and hung up at updating packages. Every try; tried about 10 times. If I switched to 5.04 with kernel 3.4.110 - the first boot takes about 1minute and cubietruck rebooted once, so everything worked perfectly. Any idea what could happened? Some extra info: If I logged in during this "updating packages" period, the normal process of creating a new user worked as normal. After that I could restart the cubietruck normally. So my question: Do I get some problems if I log in while the "updating packages"-process and reboot after that? - normally at the first boot it should be restarted once, right? Many thnanks for your replies. bb

I had the same problem, but now with version 4.5 with kernel 4.2.3 the problem is gone.

Many thanks to you Igor. I had the same problem, but now with version 4.5 with kernel 4.2.3 the problem is gone. Nice work!