Jump to content

SteeMan

Moderators
  • Posts

    1885
  • Joined

  • Last visited

Posts posted by SteeMan

  1. Please read: https://forum.armbian.com/topic/16407-please-read-first

     

    What you are currently running is a vendor kernel - i.e. a heavily patched kernel that isn't maintained.  The builds you are trying to use are mainline kernel based.  Because of lack of vendor support, the mainline kernels while maintained and supported are often missing functionality that existed in the vendor kernels.  Add to that the vendor kernels were written to run android not general purpose linux.  The last comment I would make is that because the mainline kernels are distinct from the vendor kernels, the dtbs are not compatible across them as a lot has changed between 3.14 kernel days and 5.10 kernel days.

  2. 2 hours ago, geekinlinux said:

    im using ``sun50iw9p1`` i think `h616` does this image work and which dtb and u-boot file should i use. 

    @geekinlinux This is the second post you have posted essentially asking the same question.  You posted this in completely the wrong place (as this has nothing to do with a TX3 X3 box).  Please follow common etiquette and post things in the proper place.  Also I think you question was answered above by Werner who linked to a thread that states:

     

    "Before complaining about an issue read this!

    tl;dr: Put your Zero2 and/or any other H616 based device on the shelf and WAIT for proper support to come. And no. There is no ETA. Assuming usable state end 2021/beginning 2022"

     

     

  3. @Alexx That error message would point to an issue with your boot media.  Are you booting from an SD card or SSD?  The first thing I would check is if the root partition is actually named ROOTFS.  Since this is an ext4 partition I don't know if windows will tell you the partition name or not so you may need to attached to a linux system to verify.  But your boot media should have two partitions one named BOOT and the other named ROOTFS.

  4. @menelike So if I understand your posts correctly, you have a working environment with a legacy 3.x kernel.  You are looking for something newer.  So you tried a current build with a 5.x kernel and it didn't work.  So now you are trying to hack your 3.x install to get a 5.x kernel working in that environment?

     

    The 3.x legacy kernels are essentially unsupportable as they rely on a lot of vendor supplied code that isn't maintained.  The 5.x kernels are using mainline linux without all the crap.  The problem is that vendor support for mainline linux is minimal and therefore things that work on a legacy kernel will not work on mainline.  If you can't get your box to work on a 5.x based kernel on a clean install, you aren't likely to be able to move to a mainline based kernel.  The legacy kernel is significantly different than the mainline code base.  Formats for things like the dtb have changed a lot, such that the 3.x dbt isn't likely to be very helpful working with a 5.x kernel.

  5. @Scrooge69 Welcome to the armbian world and your first post in the forums.

    I unfortunately don't have much information in response to your questions.  balbes150 who created the builds referenced in this thread has moved his focus to other projects (the StationPC M1 and P1 boxes).  I don't own a rk3328 based device so I have no personal experience with them.  If you look at the recent activity in this thread there isn't anyone actively engaged currently supporting boxes like the one you have.  The best I can recommend is to try using the images linked in the thread and try things out.  Since you are puttimg the images on an SD card it won't hurt your device to test and experiment.  (I wouldn't recommend installing anything onto your emmc memory however).

  6. By clean copy I mean a fresh install of:

     

    20 hours ago, menelike said:

    Armbian_21.02.0-trunk_Aml-s812_bullseye_current_5.10.0_.img.xz

     

    I am assuming you are running from SD card, so install the build on a different SD card and see how well your box works with a recent build/kernel.  Once you have established a baseline of a working 5.10 environment then you can decide how you can get the box to have what you want on it by moving data between your old SD card and new SD card.

  7. @menelike Have you tried to install a clean copy of a build with a mainline kernel to see if that works on you box?  My recommendation would be to perform a clean install and then migrate over anything you need from the old 3.x kernel based install.  There is no upgrade path for what you are trying to do, so many things have changed overtime that I wouldn't be confident that you will ever end up with a stable environment.

  8. The language of this forum is English.  Please use a translation tool.

     

    1 hour ago, Fionda 4 said:

    Salve a tutti, sono nuovo di questo forum e vorrei sapere se ho aqcquistato un prodotto valido e cosa ci si puo fare con x96 mini.
    Grazie....

    Hi everyone, I am new to this forum and I would like to know if I have purchased a valid product and what can be done with x96 mini.
    Thanks....

  9. On 1/20/2021 at 3:49 AM, lgranie said:

    - format /boot in ext4

    A couple of thoughts/questions on this.  First why do you want to do this?  I understand some of the limitations of having /boot be on a fat filesystem, but is there some specific thing you need this for? 

    Second, this is likely not going to be easy as the amlogic TV box booting process is tied to the fact that /boot is on a fat partition.  If you look at aml_autoscript, s905_autoscript, emmc_autoscript they are coded with /boot being on a fat filesystem (i.e. using 'fatload').  If your goal is to get the standard armbian kernels to install cleanly on a /boot fat filesystem, then it may be easier to get armbian fixed.  Theoretically armbian supports /boot on a fat file system (there is code in the scripts to allow that), but it likely isn't tested much.

  10. @lcapriotti Very interesting.  My TX3 X3 is also the same board version as yours, which explains why I have never been successful in trying these alternate dtb files.  I never dug into what was going wrong, and this helps explain it.

    I have been running my TX3 X3 (BZ version) using meson-sm1-sei610.dtb. I have 100mbit ethernet working but no internal wifi.  So since you mention you have an external usb wifi, this might be a path to consider, using this dtb and forgoing the internal wifi.

  11. @jock Thanks for your comments.  I will certainly reach out to you before I do anything with your threads (like moving them to a different sub-forum, etc).  What you are doing seems to be working well for the users you are supporting, and I don't want to break what works.

    The support issues generally are on the amlogic side of things right now.  Since there is no active development support for builds for amlogic based TV boxes after balbes stopped supporting them.  The additional problem is that the majority of TV boxes produced seem to contain amlogic cpus (although rockchip seems to be changing that recently).  So the volume of users on the amlogic side is higher than allwinner and rockchip at the moment.  And as you point out the various china clones of varying quality tend to be amlogic based.

  12. @ballerburg9005 I just wanted to add a few of my own thoughts to this thread.  Overall I can see both sides to the above discussion.  There are valid points made by everyone commenting.  While we all sometimes need to have 'grand visions' of the future we would like to work towards, we also have to deal with the reality of where we currently are.  I often think of a saying "crawl, walk, run".  While we all want to be running to the finish line of an Olympic race, we all start by crawling first.  As that relates to armbian and more specifically armbian on TV boxes, we are at the crawling stage.  There is a lot of work to be done to just get us walking.  That doesn't mean that crawling and walking in themselves aren't valid and productive stages (they are and you can use a lot of different TV boxes today to do a lot of productive stuff).

    There is a lot of work to be done today to improve our crawling.  We need volunteers (like you) to pick up that work if we ever hope to get further along our path.  We need to build a community one volunteer at a time.  While visions are important, if we don't have people willing to do work today then we will never more forward.

    If you hang around armbian for any extended period of time, you will learn that the single thing that most bothers the core maintainers of the project are people having grand visions or even small visions of what should be done but who don't contribute any time to help and expect others to do the work for them.

    Whether intentional or not, that is how your post came across to Igor and Balbes and they reacted as they normally do to such posts.

    If you want to run to the finish line with your vision, you need to start by crawling.  Spend time on these forums following the issues to build your knowledge.  Help support new users to allow others with the technical knowledge time to work on development and progress on our shared goals.  This all doesn't happen overnight.

    I welcome your contributions to the efforts here, but starting off by getting into a disagreement with two of the core maintainers isn't likely the best way to have started.  Overtime you will realize we all share a lot of the same goals and can work together even through we have different personalities and sometimes have to overcome language/cultural differences.

  13. 2 hours ago, sfs said:

    DTB file used: meson-sm1-sei610-ethfix.dtb

     

     

    @sfs  This is not a valid submission.  The dtb you reference is not part of the distribution.  So a new user couldn't follow the general installation instructions and get your results.  As was mentioned in the instructions, you need to only use files from the distribution.  You can add comments about how other settings/dtbs/tweeks improved your installation.  Also if you are referencing external code, I would request that you also include or link to source code not the compiled objects (i.e. dts vs. dtb).  That way in the future someone may be able to maintain this addon/feature as changes to the underlying kernel/environment require.

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines