Jump to content

SteeMan

Moderators
  • Posts

    1425
  • Joined

  • Last visited

Posts posted by SteeMan

  1. 12 minutes ago, fever_wits said:

    I am using the 13.03 image, in this version in install linux-headers does not work, I installed it by hand.

    13.03 image of what?

     

    13 minutes ago, fever_wits said:

    Currently, when I install a new version of the kernel, the old version of the kernel is uninstalled, and if the OS does not start, I have to do everything from the beginning. It could be a setting, but I can't find where it is.

    That is how Armbian works.  There is not option to change that behavior.

  2. 9 hours ago, Sandwichmacher said:

    What do you mean with outdated? Armbian Stretch? Armbian in general surely not...

    Technically the user space you are using is Debian Stretch.  Armbian provides the boot environment and linux kernel, the user space comes from either Debian or Ubuntu (depending on the version you choose to install).

    From the Debian release page: : "Debian 9.13 was released July 18th, 2020. Debian 9.0 was initially released on June 17th, 2017. The release included many major changes, described in our press release and the Release Notes. Debian 9 (stretch) has been superseded by Debian 10 (buster). Security updates have been discontinued as of July 6th, 2020."

     

    So Debian stretch stopped being supported over three years ago.  Armbian generally follows similar time lines to the underlying support of the Debian or Ubuntu user spaces.  The message you are getting is because Armbian recently cleaned up the support status of these older releases.  So even though no updates have been created for the Armbian parts for likely years, you didn't have any message that you weren't getting any updates until the recent change.

     

    The reality is that you need to upgrade your system.  You haven't received any security updates for years.

  3. @fever_wits I just want to point out if you don't already know, the board you have isn't supported by Armbian.  It is community maintained.  That means there is no one specifically that has responsibility for the board.  It is up to people who read these forums to respond if they have an interest.  So don't expect any specific response in any specific time frame.  Having said that, this is the correct place to post questions, observations, and hopefully solutions to issues with your board.  Armbian provides community builds as a service but doesn't have the resources to test or in anyway to support them.  So fixes/changes happen only as community members contribute them via PRs to armbian.  If no one contributes, over time the quality of a board degrades and when it stops building it then gets removed from armbian all together.

     

  4. This is certainly possible.  The level of difficulty depends on exactly what you mean by 'using a different kernel'.  Start with https://docs.armbian.com/Developer-Guide_Welcome

     

    The basic Armbian kernel build process is to start with a kernel git tree, apply a bunch of patches that are missing from said tree (usually patches that haven't yet made it to mainline), combine with a kernel specific config file and build the resulting kernel.

     

    So depending on what the differences are between your 'different kernel' and what Armbian builds, you could insert your different kernel into any/all of those areas (i.e. you could add the missing patches that other kernel has, you could fix/change the kernel config to add/removed features, or you could use an entirely different git kernel source tree, or a combination of these three). 

     

    The key would be to figure out what is different between the Armbian and other kernel that is relevant for your board.  Ideally this could be done as a PR to Armbian to add better support for that board into Armbian.

  5. Moved post to unsupported/community maintained. This is not a supported board.

     

    My mistake, misread the post.  This is pine64 not pinebook a64.  That board should be supported but the forum structure isn't up to date.  I have added the correct tag for the post, but left it in the original locatation.

  6. If you click the button on that page labeled: Community Maintained Builds?  (it is just above the selectors for all of the builds), then on the github page that link takes you to, click on Download Latest Image?

     

    Or to save you the work you could use the link at the top of the FAQ instructions.

     

    Or just go here: https://github.com/armbian/community/releases (latest build is 211, note they are listed in alpha order so the newest is not at the top)

  7. 3 hours ago, TurK-FX said:

    But now my question I only see the below files:

    u-boot-s905x2-s922

    u-boot-s905x-s912

    u-boot-s905

     

    I don't see anything for s905x3. Which one I should copy to u-boot.ext for s905x3?

     

    Your tutorial says there should be 4 files, but I  got 3 files. I don't have the u-boot-s905x3 in there. 

    I downloaded

    Armbian_23.8.1_Aml-s9xx-box_jammy_current_6.1.50.img

    and

    Armbian_23.8.1_Aml-s9xx-box_bookworm_current_6.1.50.img

     

    from the archived section of the link you sent me. 

    Use the u-boot-s905x3 found in the current rolling releases.  Why are you trying to use an old archived release?

  8. Providing logs with 

    armbianmonitor -u

     helps with troubleshooting and significantly raises chances that issue gets addressed.

     

    13 minutes ago, Gabriel Souza said:
    [    0.000000] Linux version 6.1.77+ (odroid@odroid) (gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #1 SMP PREEMPT Wed Mar  6 17:56:35 -03 2024

    This doesn't look like an Armbian kernel.  What image are you using?

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines