Jump to content

SteeMan

Moderators
  • Posts

    2002
  • Joined

  • Last visited

Posts posted by SteeMan

  1. Note that I believe Armbian will reset the max CPU frequency on boot.

    There is code in /usr/lib/armbian/armbian-hardware-optimization that uses the values defined in /etc/default/cpufrequtils to initialize the governor, min and max frequencies at boot time.  So even though cpufrequtils is no longer an installed set of tools, Armbian is still doing some of the same work based on its old configuration files.

    So assuming this works as it used to, all you should need to do is set the max speed you want in /etc/default/cpufrequtils

  2. There are no Armbian builds that old,  in fact Amlogic TV boxes weren't incorporated into Armbian until later Linux kernels.  What you must have been using would most likely have been a fork of Armbian.

     

    What you are asking for isnt possible in the way you are asking.  You essentially want Armbian ported to the 5.15 Linux kernels, which is a huge project. 

     

    You would be better served but spending a month or so figuring out why current kernels don't work for you and fixing that.

  3. 5 hours ago, marfalk said:

     

    1. If I do not install Armbian to the internal eMMC, will I be able to boot back to Android, by just removing the SD Card and powering off then back on the device?
    2. Later, if I decide to install Armbian to a USB drive or an internal SATA Hard-Drive, will I be able to boot back to Android, or it will modify the boot loader in a way that it will not be possible?

    As long as you don't install Armbian to your emmc, you should be able to still boot android by removing the SD and/or usb drives.  Once you install to emmc you will overwrite the android installation

  4. If you want to understand what should be happening under a normal installation:

    Installing "multiboot" (i.e. pressing the hidden reset button while powering the device) runs the script aml_autoscript 

    That script sets some uboot environment variables that are used by subsequent boots

    The boot process for these boxes is to use the original android uboot to intiialize the device and then hand off the boot process to the u-boot.ext from armbian.

    This is done in the script s905_autoscript (or emmc_autoscript).

    Which then essentially just runs (for emmc):

    if fatload mmc 1 0x1000000 u-boot.ext; then go 0x1000000; fi;

    (or "mmc 0" for SD card).

    The chainloaded u-boot then boots via the information in the extlinux/extlinux.conf file.

     

  5. Given where you are, my only suggestion is to restore the box to a clean android firmware (so the uboot environment is restored to a clean state).  Then restart with a current build (don't use the 6 year old build that you found somewhere).  The two versions aren't compatible.

    Then get things running cleanly from SD card first, and then if you still want move the install to emmc.

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines