• Content Count

  • Joined

  • Last visited

Reputation Activity

  1. Like
    lanefu got a reaction from TDCroPower in Problem: install MongoDB for Unifi Controller   
    the OS mongo packages are usually super outdated, not surprised they don't work.
    Consider this container.  the project builds multiarch containers for arm32, arm64, and x86.
  2. Like
    lanefu reacted to TonyMac32 in Various AML-S905X-CC bugs (Le Potato)   
    Echoing what Lanefu said, thanks for the info, and sorry about the rough edges!  A new set of sound patches have been submitted upstream, I will take a look at them and see if they can be used as a means of cleaning up our current implementation (targeted originally for 4.19).  
    The memory limit seems to be a potential u-boot issue.  For the display, the Amlogic clock framework has been an ongoing project for mainline, with a lot of changes.  I will spend some quality time with everyone's favorite S905X board and get back to you.  🙂
  3. Like
    lanefu reacted to javaboyuk in Kernel 5.4.12-imx6 - ethernet stops working   
    Ok just upgraded to the new release of armbian.. thanks guys!!
    I have done limited testing but so far this appears to works well (5.4.20) with no line droping, so great news!
    Again thanks for producing Armbian.
  4. Like
    lanefu got a reaction from guidol in Armbian 20.02 (Chiru) Release Thread   
    If you want to build a "stable" image from the same code as the images we publish use v20.02 branch.
    If you want to build "unstable" image with latest and greatest us master branch.
  5. Like
    lanefu got a reaction from Werner in Armbian 20.02 (Chiru) Release Thread   
    Surprise!    About a month is what we're shooting for.  Sorry for the poor communication.  We're still learning how to manage this process.  Ideally we will start a bit earlier and release closer to the beginning of the month 
    Master will continue on as a rolling release.  You'll see that its version is already v20.05-trunk on master.
    Relevant fixes applied to v20.02 going forward should be cherry-picked to master.   Although so far we've actually been cherry-picking fixes from master to v20.02.  
    Going forward we'll update v20.02 for major bugs and stability issues until v20.05 is released.
    rc0 and rc1 branches will be deleted.  Rc1 ended up being a rolling branch this time.  Not sure how we'll handle this next time.  A lot will be on how manage publishing test images.
  6. Like
    lanefu reacted to TonyMac32 in Le Potato issues with U-boot glx postprocessing   
    That is fascinating.  Let me look over this stuff.

    I think it's unrelated to the packaging of U-boot, probably more the packaging of the kernel.  Or I could be totally wrong, it's late
  7. Like
    lanefu reacted to Igor in Armbian 20.02 (Chiru) Release Thread   
    I found a (tmp) workaround. 20.02.2 images for Lepotato are rebuilding with working (meson64) kernel 5.4.13 and the same kernel goes to the repository which will be updated right after that.
  8. Like
    lanefu reacted to denix in Date changed to 1978,System crash,Mysql run 195% of CPU   
    Some bill printer device
  9. Like
    lanefu got a reaction from guidol in Armbian 20.02 (Chiru) Release Thread   
    check out the branch direclty and try what i said here
  10. Like
    lanefu got a reaction from Igor in Armbian 20.02 (Chiru) Release Thread   
    I tried removing all patches and that didnt change the behavior.

    Ill take a look at kernel config again, but it seemed like it hasnt changed since we switched to mainline
  11. Like
    lanefu reacted to Igor in Armbian 20.02 (Chiru) Release Thread   
    When a current Le potato will fire apt update and reboot it will get stuck, right? Per board we can control: u-boot, bsp and DTB, kernel is identical to all meson64 family.

    Perhaps @Neil Armstrong can give us a hint with the error ?
  12. Like
    lanefu got a reaction from Werner in Date changed to 1978,System crash,Mysql run 195% of CPU   
    I'm just curious.. what do you use 1500 orange pc plus for?
  13. Like
    lanefu got a reaction from guidol in Armbian 20.02 (Chiru) Release Thread   
    git fetch git checkout v20.02-rc1 sudo ./ FORCE_CHECKOUT=no  
    Unofficial release notes
  14. Like
    lanefu got a reaction from guidol in Armbian 20.02 (Chiru) Release Thread   
    git checkout master
    git pull
    sudo ./
    will take you back to the master branch that you normally use.... FYI master is a rolling release..which may have looked like 19.11.x but its actually newer.. In fact we've updated the version in master release to reflect it as v20.05-trunk
  15. Like
    lanefu reacted to Igor in Seed our torrents
  16. Like
    lanefu reacted to jeanrhum in Armbian 20.02 (Chiru) Release Thread   
    I tested several sbcs:
    - buster image for pine64:
    - buster image for OPi+2E:
    - buster image for pineh64-b (wlan0 visible, but not able to connect to my wifi network):
  17. Like
    lanefu reacted to TRS-80 in [Moderation] Dealing with subtle spammers placing "tiny little ads"   
    OK, even if that is true, I don't understand why not to do it? It requires zero effort on our part? And makes one more hurdle for spammer, but not legitimate user.
    Thank you!. This is what I have seen as well, hence my arguing so strongly for it.
    There is "theories" of what spammer could do, and then there is data (that we have) of what they are actually doing...
  18. Like
    lanefu got a reaction from TRS-80 in [Moderation] Dealing with subtle spammers placing "tiny little ads"   
    Maybe but... 4600 validating accounts disagree

  19. Like
    lanefu reacted to Igor in [Moderation] Dealing with subtle spammers placing "tiny little ads"   
    The plan is to put more limit to newbies, perhaps create another group between validating and users. No limiting normal users. This is how I see it, but other might see it different which is why we talk first and do action on some common grounds later. If most of us will think this is a stupid idea, we won't proceed.
  20. Like
    lanefu reacted to Neko May in Armbian 20.02 (Chiru) Release Thread   
    I've seen it on a few boards, but the only one I can definitively say right now is the Orange Pi 3. I'd have to check the other boards one by one and see whether they do the same.
    As for the verbosity setting, yes, setting it to 7 will give you all the kernel output on serial (as well as HDMI if applicable).
  21. Like
    lanefu reacted to Neko May in Armbian 20.02 (Chiru) Release Thread   
    The kernels shipping with the 20.02-RC builds have their kernel message buffer size set far too small; the beginning of the message buffer has already started to be overwritten by the time the login prompt comes up. This rather unfortunately complicates testing the images due to the loss of information. Similarly, the default setting of "verbosity=1" in armbianEnv.txt has the similar effect of frustrating testing efforts as there is no output on the serial port until the login prompt. I propose the friendly suggestion to increase the dmesg buffer size to at least 256KB, and set the verbosity to 7 by default; I don't think the kind of people who use these boards are going to be afraid of kernel messages.
  22. Like
    lanefu reacted to TRS-80 in [Moderation] Dealing with subtle spammers placing "tiny little ads"   
    This will be the Moderator counterpart to the Announcement thread I made about the same issue where I asked for help from regular forum Members. In this thread, I will discuss methodology I developed to deal with these sort of spammers, once someone has Flagged such post(s).
    But first, some humor. Does anyone remember this guy? Anyway, that old infomercial kept playing over and over in my head today while I was working on this. I think we stumbled across some of his students! OK, carrying on...
    What Not To Do
    First thing to probably point out, let's not simply edit out these links one by one as we come across them. That doesn't really solve the problem. In fact it makes it worse by eliminating the "trail of bread crumbs" so to speak, the easiest way we have to "get them all" (which is by recursive searching). Allow me to explain...
    These links seem to be posted in groups, by a small number of spammers. Once you catch on to one part of a cluster of them, it is actually pretty easy to methodically work your way through and find quite a few more, and "get them all" (within a given cluster).
    Modus Operandi
    But let me back up even more, for those who are totally unaware of this issue. What these people (we think they are human) are doing, is to register, and then post some at least seemingly relevant information in some topic, at least enough to get their post(s) approved. Then they come back some days or even weeks (!) later, and edit their post(s) to insert spam links. To see some actual examples, have a look at the Announcement post linked in the beginning.
    1. Check Profile
    So, once I found one such post / Member, the first thing I would do is look at their profile. Typically they will have from 1-5 posts or so. I would right click, and open each new post in another tab. Sometimes you will have to search then in the thread (using your browser search function, Ctrl-F in Firefox) to find the post. You will quickly be able to determine whether they are a spammer or not (you will see all the spam links in all their few handful of posts).
    2. Flag as Spammer
    Once you are certain they are a spammer, there are a couple ways you can "Flag as Spammer." Since you already have their profile open, you can click that button in there. Other way is to mouse over their avatar, and then the gear at bottom right opens another little menu that gives you the same option. This should be the first real action you take, because it does a couple things all at once (which will save you some time):
    it Hides (not Deletes) all their posts, and Bans them from the site (permanently)  
    Note that the above are subject to Admin settings, and these are the current settings as of this writing.
    3. Being Thorough
    Now, if you like to be thorough (I do) I will also kind of go through the threads that contain their spam posts (especially after their post(s)) and look for the following:
    did any other user (usually unintentionally, or on accident) quote the spam links? if so, edit out those spam links by hand and leave a note what you did make sure no actually useful content was hidden (I have yet to find this in even one case)  
    4. What Must Be Done (at Minimum)
    However at a very minimum, you should be taking down a list of all these spam links you come across. This is key to the whole process. Methodically complete all of the above for each spammer and each of his posts. When you are done you should have a list of spam links, and one or more Banned spammers, with all their posts Hidden.
    5. Working our URL List of Spam Links
    Next step, we do a regular search on the forums for each of the spam links in turn. I like to leave this search window up, and again right click and open each result in a new tab, do whatever I need to do, and then come back to the main search result list, and keep going. Some pointers for this phase:
    Some results will be ones you already discovered Other results will lead you to additional spam posts and/or users. Take care of each of them in turn (as above) and continue to add to your URL list. Scratch each spam URL off your list once you have worked your way through all the results for that particular spam URL. Some times you may have to "massage" the URL a bit if it is too close to common search terms shorten to base URL add quotes around it prepend "https://www." etc...  
    6. The End
    Get yourself a cold, tasty, delicious adult beverage of your choosing. You earned it. You have made the world a slightly better place than it was this morning. You have Maintained Civilization. Etc. 
    I think that just about covers it. Any questions, comments are welcomed.
    One thing I would like to re-iterate, if you don't have the time / patience for this, just Flag the post(s) and leave it for someone else who does. I think it's better to handle these properly and thoroughly than to half-arse it, deleting few links and then handicapping our ability to "get them all" later on.
    EDIT: As an example, I will include my working list, below. This is what I came up with in a couple of hours this afternoon, all starting from one link that @Igor sent me in IRC (this is a bulleted checklist and table from org-mode; names of non spammers vindicated in my search have been removed):
  23. Like
    lanefu reacted to jernej in Armbian 20.02 (Chiru) Release Thread   
    If you have Pinebook in mind and the one from Olimex, they both use anx6345 IIRC. Driver for that chip was merged in kernel some time ago, but it doesn't consider "panel-supply" property. I guess that's what's wrong. @Icenowy?
  24. Like
    lanefu reacted to Icenowy in Armbian 20.02 (Chiru) Release Thread   
    @Igor @jernej I had a headache night to debug on ANX6345 on 5.6-rc1. The polarity of the reset pin in the DT should be reversed with the mainlined driver, compared to my first version.
    5.4 should not be affected by this because the DT binding enters at 5.5 and the real driver at 5.6 .
  25. Like
    lanefu got a reaction from _r9 in Help us test Armbian 20.02 RC1!   
    The first RC Images are out for Armbian 20.02.     We need your help testing Supported Boards for this release.   The download site is already configured for the RC1 images as the default download.  (We intend to improve this process in future releases, and provide separate download links.)
    Here's how to help:
    download and configure our testing tool (currently in alpha state) identify supported boards you have on our test tracking google sheet Run testing tool Perform any additional independent testing that you can Update test tracking google sheet with your results Please share major issues on our Armbian 20.02 (Chiru) Release Thread