Jump to content


  • Posts

  • Joined

  • Last visited

Posts posted by SteeMan

  1. So you don't want to remove:






    (those last two are your linux kernel and dtb files - which was the reason you couldn't boot previously)


    1 hour ago, Domas said:

    # deb http://apt.armbian.com jammy main focal-utils focal-desktop # disabled on upgrade to jammy

    So you can see here the upgrade disabled the armbian apt repository.  So it can't install the updated armbian packages.


    So should be:

    deb http://apt.armbian.com jammy main jammy-utils jammy-desktop


    (So uncomment and change all references from focal to jammy)


    1 hour ago, Domas said:

    Now it says Armbian 23.02.2 Jammy

    shouldn't the version be 24. something?

    That is coming from one of the armbian* files located in /etc.  I don't remember which one.  If after everything is upgraded, if it still isn't showing the correct value, you can edit.  I think this should get updated by the installation of the correct armbian-bsp-* package.

  2. 43 minutes ago, Domas said:

    I only freeze the kernel, i suppose it is something different?



    Or maybe I can try to upgrade without freezing kernel? Or is that a guaranteed fail?

    Ive never frozen the kernel when doing upgrades.  So that shouldn't be necessary.


    I would recommend redoing the upgrade, and at the end looking at the list of obsolete packages and not removing them.  Finish the upgrade (without removing obsolete packages) then go see what the status of your /etc/apt/sources.d/armbian.list file is and make that correct, then use apt to update/upgrade your armbian packages.  Then look at your obsolete packages and make sure the list is sane (that is it's not removing any armbian needed packages, *armbian*, linux-image-* or linux-dtb-*.)  Only then would I remove obsolete packages.


  3. 15 minutes ago, livingcreative said:

    How to get really minimum build and where to find actual informaton about that kind of builds as there are many tutorials but they seems to be outdated/incomplete or do not cover board specifics.

    I would suggest you use the armbian build system and build the CLI minimal build for your board.  That should be sufficient for your needs as a starting point.  It is also a low barrier to entry as you can get that working with minimal understanding of what is going on behind the scenes.  Then you can dig into the details to learn as you need.

  4. 54 minutes ago, voapilro said:

    I have being using some Raspberry Pi for several years, and I am happy with them, but prices are higher year by year, so Orange Pi could be a good alternative.

    A significant reason that the Raspberry Pis are more expensive is that the manufacturer actually invests time and resources into the underlying software.  OrangePi does not.  OrangePi takes advantage of the open source community hoping they can get software support for free without contributing much if anything to that process.  There is a reason that OrangePi boards are not generally supported by Armbian, and lack of manufacturer support is a big reason.


    So that means that if you want good software to run on OrangePi boards, then OrangePi expects you to do the work.  And that is a lot about what this thread in the forum is about - the community trying to support these boards.

  5. It looks to me like the upgrade is uninstalling the kernel, dtb and likely other armbian packages.  Likely because it thinks they are extra for some reason.

    During the upgrade are you seeing an option to remove old packages?  If so look at that list and see if there are any Armbian packages in that list (there shouldn't be) (specifically anything with Armbian in the name as well as linux-image-* and linux-dtb-*)

    I think successful upgrades disable the Armbian apt repository which should leave all the armbian packages untouched.  Then after the upgrade, you manually enable the armbian apt repository for the correct release and then do an apt update/upgrade of the armbian packages.

  6. 12 minutes ago, sambento said:

    So, do you know any working armbian image for this KM1 box? I'll try armbian as soon as I restore the device.

    No clue as I don't have that box.  Search the forums for information.

    As far as build goes, you should be reading the FAQ posts:




  7. If you have ever run coreelec on the box, you will not be able to install Armbian.  The coreelec changes the boot environment on emmc in a way incompatible with Armbian.  You will need to reinstall an original android firmware which will restore the boot environment if you want to install Armbian.

  8. @mc510 You may know this but I'm adding this in case you or others reading this thread don't.  This board isn't supported by Armbian.  With limited resources Armbian can only support a limited number of boards with their resources.  This board is a Community Maintained board, which means that it is up to the people in these forums to submit PRs to maintain and or improve support for this board.  What often happens is that no one contributes back to the community and over time Community boards degrade in quality until they no longer build in which case they are set to end of life status.  And removed.

    For the official description on Supported vs Community Maintained see:


  9. Start by reading this:


    Note that especially for amlogic based CPUs this is really only good for server tasks.  Don't expect a usable desktop replacement.  Also if your box really has an s805 CPU, there really isn't any support for those older CPUs.  But your box likely has an s905w CPU (at least many with that name do, but you really should open the box to make sure what you have as manufacturers change components all the time and use the same case)

    Finally if all that doesn't scare you away:


  10. I can't explain what you are seeing, as everything appears in order.  The only thing I'm going to suggest as a long shot, is that you are getting pointed to a mirror that for some reason isn't up to date (which shouldn't be the case).  Since I don't know where you are located in the world, you could try to update your armbian.list file to point explicitly to a different mirror (list is available here: https://github.com/armbian/mirror)


    When I look at the mirror I get resolved to, I see the 24.2.1 packages in the bullseye repository.  I don't understand why apt isn't finding them for you.



  11. I don't have this board personally, so I can only make educated guesses.  The two things that caught my eye were the text "Hit any" which I assume should say Hit any key (it seems like some of the output is garbled). Such a message often has a timeout associated with it so you have some time to use the keyboard.  The other thing I noticed is that your build is using uboot 2022.01, where current code is using uboot 2024.01.  So you might want to build a current version and see if the newer uboot has any difference in behavior.

  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines