Alex0010

Did you use this module? It is possible it fell out in 5.26 release, so it needs to be readded to the kernel config if it can be used on these boards. Those were CUPS modules, which I do not use - it got pulled along with Samba I guess. I removed their conf files from /etc/modules-load.d/ and now my system boots fine. Thanks for all the help, but please don't do this again guys

I am progressing with this. Burned Armbian_5.25_Cubieboard_Debian_jessie_next_4.9.7.img to the second card again, booted, upgraded - now got linux-image-next-sunxi and linux-dtb-next-sunxi versions 5.26 instead of 5.27.2017<...> - so apparently you fixed packages in repository successfully. I then connected both the first and the second SD cards to PC and copied /boot/ directory from 2nd to 1st, edited /boot/armbianEnv.txt with correct UUID of 1st card and booted OS in emergency mode (see below). Removed linux-image-next-sunxi and linux-dtb-next-sunxi packages and installed them again, this time getting versions 5.26. OS boots in emergency mode and: How can I repair the modules now?

https://docs.armbian.com/search.html?q=unbrick Thanks for the pointer. I unpacked everything from here http://apt.armbian.com/pool/main/l/linux-4.9.12-sunxi/ and root package from here http://apt.armbian.com/pool/main/l/linux-jessie-root-cubieboard/linux-jessie-root-cubieboard_5.25_armhf.deb Unfortunately, it's still not booting (stuck at "Uncompressing Linux... done, booting the kernel.", see TTL log below). I noticed that /boot/uInitrd still links to /boot/uInitrd-4.10.12-sunxi, is that the problem? Files: Boot log:

Just tried power cycling couple of times - same result (not booting up on Cubieboard). SD card is working fine when connected to Linux PC. Same result with fresh SD card (updated several days ago to that damn 5.27 kernel). Can I get some guidance on that manual repair please? I would like to unbrick OS on the first SD card instead of starting afresh.

We remove that kernel from repository. Did you build it on your own? No, I just did the standard "apt-get update && apt-get dist-upgrade" and got 5.27. @zador.blood.stained said something about 5.27 being in a repo above. Can I manually repair this (I have a Linux PC with SD reader)?

I tried 2 cards now (see first post). First one was working fine before the upgrade. Second one I checked with f3 - no issues, and it booted fine with freshly written Armbian_5.25_Cubieboard_Debian_jessie_next_4.9.7. But it's not booting after upgrade that includes 5.27 kernel.

About TTL: But I was definitely booting Armbian on my board with TTL connected in the past - just to see if it works. It also boots fine on freshly flashed SD card (gets me to login prompt and then to fully functional bash). It stops working only after upgrade. 5.27 kernel is my primary suspect as well at this point. Can I pull older kernel from somewhere and point Armbian to boot it?

Never had a problem with Armbian on my board. After last full upgrade (linux-image-next-sunxi 5.27.170427 etc) system is not booting. I tried with a fresh SD card (image Armbian_5.25_Cubieboard_Debian_jessie_next_4.9.7) - it's booting fine afresh, but also doesn't boot after full upgrade. Below are logs for both cases. Boot with old card: Inital boot of new card (Armbian_5.25_Cubieboard_Debian_jessie_next_4.9.7), upgrade and stuck on boot: