Jump to content

lanefu

Members
  • Posts

    1331
  • Joined

  • Last visited

Reputation Activity

  1. Like
    lanefu got a reaction from guidol in Armbian 20.02 (Chiru) Release Thread   
    git fetch git checkout v20.02-rc1 sudo ./compile.sh FORCE_CHECKOUT=no  
    Unofficial release notes https://gist.github.com/lanefu/e32eb43aaaa7928c51ca8890af58c841#file-temp_notes-md
  2. Like
    lanefu got a reaction from guidol in Armbian 20.02 (Chiru) Release Thread   
    git checkout master
    git pull
    sudo ./compile.sh
     
    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
     
     
  3. Like
    lanefu reacted to Igor in Seed our torrents   
    https://dl.armbian.com/_download-stats/
  4. Like
    lanefu reacted to jeanrhum in Armbian 20.02 (Chiru) Release Thread   
    Hi,
    I tested several sbcs:
    - buster image for pine64: http://ix.io/2bMQ
    - buster image for OPi+2E: http://ix.io/2bMU
    - buster image for pineh64-b (wlan0 visible, but not able to connect to my wifi network): http://ix.io/2bN0
  5. 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...
  6. Like
    lanefu got a reaction from TRS-80 in [Moderation] Dealing with subtle spammers placing "tiny little ads"   
    Maybe but... 4600 validating accounts disagree
     

  7. 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.
  8. 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).
  9. 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.
  10. 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).
     
    Humor
     
    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.
     
    Thanks!
     
    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):
     
     
  11. 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?
  12. 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 .
  13. 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  
  14. Like
    lanefu reacted to Igor in O Pi projects? Application?   
    2015-06-04 11:32:22 Apply for Orange Pi

    Not sure if its still relevant?
  15. Like
    lanefu reacted to TonyMac32 in Armbian 20.02 (Chiru) Release Thread   
    O RLY? Very nice.

    Sent from my Pixel using Tapatalk

  16. Like
    lanefu got a reaction from TRS-80 in Armbian 20.02 (Chiru) Release Thread   
    So good news.... I got a 1G Rock64 V2.  build RC1 image
     
    totally works
     

  17. Like
    lanefu reacted to Igor in Armbian 20.02 (Chiru) Release Thread   
    I will try to resolve Allwinner A64 issues, the rest will need to wait for next release.
  18. Like
    lanefu reacted to Igor in Armbian 20.02 (Chiru) Release Thread   
    False alarm. Everything is alright.
  19. Like
    lanefu got a reaction from TRS-80 in THE testing thread   
    So a bit of progress on the testing front
     
    a tool for testing freshly installed images on SBCs Jenkins testing to build kernel based on PR I'd love help enhancing the the jenkins scripts to make more accurate decisions on what to test based on file changes... I have some logic that does an okay job right now
  20. Like
    lanefu got a reaction from TRS-80 in THE testing thread   
    Im a devops consultant and fluent in Ansible so I think im Obligated in that regard. I can at least handle the plumbing hopefully others can implement the more granular testing once the framkework is in place.
  21. Like
    lanefu reacted to stut in Armbian 20.02 (Chiru) Release Thread   
    I was having issues connecting to certain APs, the password was always wrong even though I knew for sure they were right. In the end it was due to network-manager's random mac address trickery. After disabling it I could connect just fine. Maybe the random mac should be turned off by default as it can interfere with certain APs?
     
    A quick fix, create /etc/NetworkManager/conf.d/99-disable-wifi-random-mac.conf and add the following;
    [connection] wifi.mac-address-randomization=1 [device] wifi.scan-rand-mac-address=no  
  22. Like
    lanefu reacted to legogris in Process for adding CSC boards?   
    I'm having some success installing Debian on Raspberry Pi 3B+ and thought I'd proceed with making an Armbian build in order to have equivalent environments with other boards in my cluster.
    Is there any process/channel for this or should I just make a PR on the repo? What are some particular prerequisites I should be aware of that might block it from merging?
     
    I am very aware of armbian's stance on Raspberry Pi, and I understand you do not want to support it officially (if nothing else because you'd have difficulty handling the incoming clueless users), but I think there are a lot in the intended armbian audience who have Raspis lying around who would be happy about an armbian build. Also it could act as a gateway to bring people to educate themselves more on Linux in general.
     
  23. Like
    lanefu reacted to Meier in Last effort regarding RockPro64 kernel panics   
    Thanks for all the hints, will try this out.
     
    To be honest, I can't imagine to be the only one having these issues. Maybe it's just that our usage of the RockPro64 board with a PCIe NVMe M.2 SSD is not very common? We suspected the PCIe / SSD combination to be the cause for a long time, for but cannot really confirm this. The issues are consistent over dozens of RockPro64 boards and many SSD brands. And I've heard from users that the PinebookPro (which uses similar hardware) also freezes under heavy load when run with an SSD.
  24. Like
    lanefu reacted to Werner in Making IRC Channel Official   
    Of course not. Having voice in an non-moderated channel is an optical accentuation only.
  25. Like
    lanefu reacted to chwe in Proposed Forum Structure Change   
    more subforums add just more subforums I'll ignore.. and there are quite some atm. And it seems we have this discussion like once a year or so... And yes I started such a thread as well must be gone somewhere by one of our forum rearrangements...
     
    we have a:
     
    where all the not armbian related software questions can go as well..
     
    and we have a
    and chit chat.. IMO chit chat is the place where everything goes in nobody wants to deal with..
    The more subforums you have the higher the chance that people choose the wrong one.. means after its more moderation work and as you said time is valuable..
    In a perfect world I would not want to moderate at all cause people don't mess stuff up.. For me moderating is splitting/merge topics on request or when they're obviously not related to each other/connected to each other. Locking stuff down when it goes out of control... which happens from time to time when people get frustrated.. Otheerwise I see myself just a normal user/dev doing dev stuff or spaming in the chit chat about chit chat stuff:
     
    that's what this subforum is for... As well as asking which TV box may or may not be a good pick can have a living there.
     
    If the new structure ends in more moderating we do things wrong, if it ends in less moderating we do stuff right.. as simple as it is.. The same reason I had a iphone for years and not an android phone.. I just had to think less where I find what I need. This got better in android world but I'm not sure if it got better in the forum over time but I don't think a more fine grained forum will help here. I can be wrong on that but people tend to post fast and think less means if they don't find the topic it will fit within page one they'l post it wherever they are at this moment..  Ask yourself.. when did you last go to page 3 or page 4 on a googlesearch? The same happens on forums.. And that's why I mostly refuse to answer to posts where the solution can be found within the first two pages of a googlesearch.. or if I do, I'll use something like https://lmgtfy.com/ to remind those people that things are easy as hell if you use the right search terms. I guess this behavior is now called being toxic - I somehow missed this change in social moves from "it's being a dickmove to waste someone else' time if it can be found with a random search engine" to "every stupid question is worth an answer an how dare you are if it's not written super welcoming and inclusive to everyone"... Back to topic:
    That may sound hard but: for your own sake, better learn to deal with it.
     
    Users are interested in:
    a working SBC with all the features a boardmaker claims (and mostly he sums up the capability of the SoC - mostly this features are based on what works on android and have barely something to do with what works on debian/ubuntu having a recent debian/ubuntu cause nobody wants to deal with something like trusty anymore but they mostly don't care about stuff like bootloader and kernel at all as long as it has the features they need. We still have a bunch of users using the 3.4 bsp kernel on allwinner and we soon ran into the same nightmare with rockchip 4.4 (at least in rockchips case there is a chance that they forward port this to a more recent kernel once android requires a newer kernel) using the most crappy powersupply they have somewhere laying around getting support ASAP cause their problem is for sure the most important one on the world Developers are interested in:
    solving some interesting parts which didn't work before dealing as less as possible with users cause their mess there nice: everything works world up and soak up the time for development having a few users for testing cause testing is boring bringing new boards up, cause board bring up is a way more interesting than board maintenance.. So you see your point: having a well organized forum doesn't really affect both of the mayor groups we're dealing here with.. There are only a few people interested in maintaining the forum and from those few even less are interested in reorganize stuff cause this means more maintenance work and explaining the users why things have changed and how it is supposed to work now. There is this nice little saying: Rome wasn't built in one day, I would add but Nero burned it down in one. To explain that a bit more, if a change breaks the current state may make sense but break existing behavior hence ends in more rebuilding/moderating. This may work as long as you have the fresh "spirit" of moderating things.. but can you keep this over time (means for years not only months)? Cause that's what is needed if we decide to moving around things or moderate more stuff. It's not a change things and everything will be fine, people will still post on the wrong threads and people will still have a wrong assumption what armbian is (a spare time project which tries to do it's best to support a variety of boards as good as possible with a recent kernel with flavors of ubuntu/debian with some tweaks here and there to make debian more useful on such boards e.g nand-sata-install, and tweaks around zram due to limited ram on most of this boards).
    Or to summarize most of it related to your new job as moderator.. be patient and accept that changes might need their time. And right reorganization of the forum might not be on high priory during a release. Especially that this release model is something we're more or less doing "the first time". Or at least it's done the first time that way as we do/try to do it yet. There's for sure a bunch of stuff I forgot to write up.. 
     
    Disclaimer: as often.. this post may contain some sarcasm, some rants etc. (I may should have this in my signature for the future)...
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines