pfeerick

Moderators
  • Content Count

    146
  • Joined

  • Last visited


Reputation Activity

  1. Like
    pfeerick reacted to TonyMac32 in ROCK64   
    Look at rockchip patchwork area, they are adding the RK805, which I believe is the pmic involved here? They are very similar, but not quite the same.  https://patchwork.kernel.org/project/linux-rockchip/list/?q=rk805
  2. Like
    pfeerick reacted to martinayotte in ROCK64   
    W25Q128 are now cheaper than 1 year ago ...
  3. Like
    pfeerick reacted to Igor in Improve 'Support over Forum' situation   
    https://github.com/igorpecovnik/webpage
     
    It did a lot of cleanup but still it's dirty. Perhaps it needs to be done from scratch. Essentially git clone + run.sh ... it makes cache files, which are included into Wordpress blog which handle those special tags and there is one bug with md parsedown library under php7 which results in some missing translation between md and html.
  4. Like
    pfeerick reacted to chwe in Improve 'Support over Forum' situation   
    If they want not read stuff, give them more stuff to read.  I did some tests with cheap USB chargers (bought two only for this test) and cables and thought I would publish it somewhere here in the forum. Cause I knew, that this would give a longer thread I collected all my data in Word (yeah, I'm normally a Windows user.  ) and thought to copy paste everything when I'm finished.  During the collection of data, I thought why shouldn't make something like a 'white paper' out of it? If I jump into a new topic I'm always interested  in application notes or white papers. 
    So, this is a draft (language has to cleaned up and some 'peer review' process should also been done before publishing it) about micro USB and what's to consider when using it. Maybe a set of such 'white papers' with common tasks, mistakes etc. about SBC could be something for armbian?
     
    BTW: I started this test with four USB chargers, the 0.60$ one from china didn't survive the test...

    Powering throught micro USB.pdf
  5. Like
    pfeerick reacted to tkaiser in Banana Pi R2   
    And a small documentation update. Our friends at SinoVoip provided a great piece of information called 'Banana Pi BPI-R1 BPI-R2 smart router board Comparison 20170612'. http://forum.banana-pi.org/c/Banana-Pi-BPI-R2
     
    Well, for whatever reasons the 'Comparison' isn't there any more. I don't know what might be the reason for (censorship maybe?) but fortunately the Internet remembers: http://archive.is/ibTTg
     
    Since I get comment updates via email here the last piece of information @RagnerBG(one of the many users not so happy with BPi R1 -- see here for his full list of hardware modifications needed to be happy with the R2 predecessor) added over there:
     

     
    (dear SinoVoip friends, you should have a look at https://en.wikipedia.org/wiki/Streisand_effect to avoid such stuff in the future. Also it would be great if you can immediately unhide all posts of mine you currently censor away)
     
  6. Like
    pfeerick got a reaction from tkaiser in Improve 'Support over Forum' situation   
    I'll shush for a while so we get some other voices here in the conversion, but let me be the first to say Thomas, you're a brain damaged retard for hoping (in my opinion against all hope) that somebody might listen and actually do something about it. But no, they insist on making excuses, and saying that they're doing a good job. And you know what I think we should do... boycott all the way until they learn the error of their evil ways.
     
    I don't think you missed any discussions on the forum, as I didn't see anything either, but who am I to argue with the boss. But then again... unsupported WIP, and new toys...
  7. Like
    pfeerick reacted to TonyMac32 in Improve 'Support over Forum' situation   
    I've run a couple small forums for Assembly Language programming/etc, I can say that no amount of quiz keeps out the machines.  And let's face it, do we want to make the bots smarter by feeding them harder puzzles?  Soon they will gain sentience. 
  8. Like
    pfeerick reacted to TonyMac32 in Improve 'Support over Forum' situation   
    I think the idea of the quiz is more harmful than the quiz itself.  "Who are these guys to put barriers in the way?" etc.  In general it comes across as unfriendly, snobbish, unwelcoming.
  9. Like
    pfeerick reacted to Igor in Improve 'Support over Forum' situation   
    Perhaps we can make a quiz after all  It does the job: "promote members to a group when they reach a specific rank in the quiz"
    https://invisioncommunity.com/files/file/8381-quizzes/
     
    @tkaiser Would you like to design this member evaluation quiz?  Even if we have only this quiz its worth the trouble.
     

    Well, some people would want to know more and some explanation must be present.
  10. Like
    pfeerick reacted to Igor in Improve 'Support over Forum' situation   
    Added yet another link - directly to "Getting started". @pfeerick I hope words are not too harsh ?

  11. Like
    pfeerick reacted to sean.wang in Banana Pi R2   
    For all I did there, I would say I can't represent the whole MediatTek, the contributions mostly comes from those passionates in MediaTek internally
    and the core member in LEDE/Openwrt.  Many people still don't recognize importance gained from open source I admit.  I don't blame them because
    everyone has different experiences for defining what success is for them although I still have a little complaining on them as @tkaiser did it for sinovoip
    why let me do the unnecessary and repetitive thing again wasting so much time and energy if they are done well in the initial.
     
    Instead, I would like to change their mindset as much as possible through upstreaming activity to help to link irrelevant groups among MediaTek internal,
    various communities, existing developers, potential users and so on to produce more chemical changes getting more attention on the importance of open source
    and prove commercial product still can be done well with combining appropriate open source project and finally allow us all together walking on the right path.
     
    Maybe there'll  a lot blames/questions/suggestions on coming bpi-r2, but I will be glad to listen to and reflect them into the MediaTek internal, and even
    welcome delivering patches to me making more robust to BSP
  12. Like
    pfeerick reacted to tkaiser in Banana Pi R2   
    This pretty much sums up the situation with SinoVoip. Even if you want to help them it's not possible since they're behind a wall of ignorance higher anyone could imagine. The most frustrating part is that they don't get what they do
  13. Like
    pfeerick reacted to kjn260 in OTA Imaging / Remote Update / mender.io   
    Hi Guys,
     
    I have recently been contracted to a new project where I have moved out of my comfort zone (embedded 8-bit/32-bit uC) and have started my work on a H3 based device (currently NanoPi Neo) with Armbian.
    Over the course of my work I have managed to get up to speed with the basics; configuration, scripting, hardware and interfaces and device trees to a point where I can now work on the device as a proof of concept.
    The work that has been contributed so-far to the armbian project is impressive as is the active and knowledgeable forum - to which I hope I can contribute.
     
    One element which I cannot find an easy solution to is one of remote update. In the embedded world because your whole program/environment is loaded from flash into device ram it is very easy (if you have a device with network connectivity) to have a RPC to download and reflash new firmware - this is very useful for installations where physical access is restricted or unavailable and changes must be made to the firmware.
     
    While it is possible to for example remote access (via SSH or some other means) to do system upgrades, I think a "whole-image" approach has some benefits especially when considering critical system deployments.
     
    So I have been researching options that may be easily deployed into the Armbian build environment - there are quite a few options I have found (https://wiki.yoctoproject.org/wiki/System_Update), however on looking at all the options the best suited to the Armbian environment is mender.io in my opinion.
    It is compatible with block devices (uSD/eMMC), compatible with uboot, has a "secure" and robust update mechanism with fallback, is open source and has agreeable licencing for integration with Armbian/Commerical Products etc.
     
    The only downside is that it is currently built for integration with the Yocto project and only has a reference hardware of a Beagle Bone Black. There has been some information provided for custom target/build integration: https://mender.io/blog/porting-mender-to-a-non-yocto-build-system.
    After reading this I have made some notes, but I am obviously still learning and feedback from those more experienced than I would be appreciated.
     
    1) Partition Layout
    At the moment the RESIZE_FS flag in the armbian build enviroment causes the rootfs partition to expand to the whole size of the available device, this can be overwritten to a fixed size at build time. Presumably with some modification to the script it could partition the device as required: https://docs.mender.io/1.0/devices/partition-layout
     
    2) Go/mender Client libraries
    These should be possible to be added as user-packages in the build stage?
     
    3)uBoot Patches:
    0001-Generic-boot-code-for-Mender.patch
    0002-Integration-of-Mender-boot-code-into-U-Boot.patch
     
    Should be able to be applied as user uboot patches at build stage?
     
    4)Artifact creation (e.g. update images):
    Can be completed with an additional post-build script using the mender artifact tool or integrated as an script in Armbian build environment.
     
    I suppose my questions are:
    -is there interest in such an addition of this feature into armbian?
    -for the people that are well versed in the armbian build environment - is there any potential pinch points for integration?
     
     
     
     
  14. Like
    pfeerick reacted to tkaiser in Moderator duties   
    Absolutely agree on that and was more talking about what happens in the future. In this specific case I see myself at fault since announcing to duplicate/recreate the thread and then not doing so timely. But fortunately we identified the issues quickly and those were fixed either internally or externally (thanks @Igorand Alasdair!).
     
    But these issues should remind us that Armbian forum is not only used for internal discussion but also to have some impact on the outside (at least that's one of my uses, I still refuse to run my own thing/blog and try to collect knowledge here as part of a community to try to help letting the community grow).
  15. Like
    pfeerick reacted to TonyMac32 in What's your favorite board(s) and why?   
    I still have it, it's gotten so old it's actually a collectible by this point...
  16. Like
    pfeerick reacted to TonyMac32 in What's your favorite board(s) and why?   
    Well, if the under-powered hardware is the talking point, I used my TRS-80 model 100 portable as a linux terminal just to prove it could be done...
  17. Like
    pfeerick reacted to zador.blood.stained in Kernel Option Requests?   
    We are trying to keep the config balanced for different use cases (server, desktop, multimedia, IoT), and if a kernel option has a recommended value it would be best to use it.
    config NO_HZ_IDLE bool "Idle dynticks system (tickless idle)" depends on !ARCH_USES_GETTIMEOFFSET && GENERIC_CLOCKEVENTS select NO_HZ_COMMON help This option enables a tickless idle system: timer interrupts will only trigger on an as-needed basis when the system is idle. This is usually interesting for energy saving. Most of the time you want to say Y here.  
    Usually if there is a patch foir the mainline kernel, then somebody needs to maintain this patch, adopting to kernel changes, otherwise this patch will be thrown out if it doesn't apply cleanly or breaks the compilation.
     
    The most reasonable solution in my opinion for this rather unusual use case would be to compile the kernel with required changes and patches, put the kernel packages on hold and forget about it unless you require a newer kernel for some reason.
  18. Like
    pfeerick reacted to James Kingdon in What does your workbench look like?   
    Heh, I love looking at other people's workbenches, seeing all the cool toys and the minor oddities we all keep. Look, a pile of floppies and a torroidal transformer. My eye is drawn to the line of partly glimpsed objects at the top of the frame. My inner 5 year old would never have been able to resist the temptation to see what was in every box...
     
    My own workbenches are just wildly embarrassing. I need to tidy. No, I need to excavate.
  19. Like
    pfeerick got a reaction from tkaiser in Moderator duties   
    Oops! Well, can't please everyone. But it was better to have been done sooner than later, as if we left it for a month or so we're either be stuck with that thread as it was, or break a load more sites when it does get split. 
     
    Edit: Alasdair just updated the link
  20. Like
    pfeerick got a reaction from Igor in Moderator duties   
    Oops! Well, can't please everyone. But it was better to have been done sooner than later, as if we left it for a month or so we're either be stuck with that thread as it was, or break a load more sites when it does get split. 
     
    Edit: Alasdair just updated the link
  21. Like
    pfeerick reacted to chwe in Improve 'Support over Forum' situation   
    Since this thread is started, a lot of improvements are made to clean up the forum. Also a lot of cool ideas to avoid same questions again and again. I have one for the Getting Started guide. Here's the part of burnig the SD-Card:
    Why don't we add one sentence about why we use Etcher to burn Armbian on a SD-Card? Something like: Compared to other burnig software like win32 etc. etcher validates the image after burning so that you don't run into SD-Card corruption. 
    On the SD-Card part there is clearly writte what TK found out with all his tests, but the reason why someone should use etcher isn't that clear. It's obvious that not every one will read it, but most of the blogs I saw in the past, copy-past their sentences from docs to save time, and hopefully they'll 'spreading of the gospel' 
     
    Thinking about 'The Ten Commandments' of armbian:
    1. Use a reliable powersource
    2. Burn your image with etcher
    3. Tbd
    Nobody calls into question the ten commandments, whereas a lot of people does this on armbians recommendations...  Ok, sounds like a religious armbian sect (time to go to bed  ). 
     
    Edit: Just had to search to find my own thread about my IoT stuff that I'm doing.  I miss somehow a subforum where users can describe their projects. For sure they can write a tutorial, but it can inhibit the less experienced users to call it a tutorial (I would never call my thread a tutorial cause it started more or less as a link sharing of some stuff I found with google, as soon as I have more time & being sure that everything works fine, I'll rewrite it to make something that I would call a tutorial).
  22. Like
    pfeerick reacted to Igor in Improve 'Support over Forum' situation   
    Well, we have to force (with nice words of course) to check at least 1,2,3 basic things. If they would do that in first place, huge amount of time would be saved. On both sides and we would be less stressed out.

    The main idea is that, they do something, before seeking for attention. Basic checks and preparation  .... that not first question on support is: please provide logs, chech this ... but filing an issue looks like this: "here are logs, I checked this but the problem is still here ..."
     
    I changed the title to some generic one. I hope it sounds better now  ... I am adjusting, unpinning and moving stuff, starting in A20 section. Let's wait if anyone else has any complains about this message, than we can enable this ... 
     
  23. Like
    pfeerick reacted to tkaiser in Improve 'Support over Forum' situation   
    Yes, that's way better than my idea! And both 'armbianmonitor -c $HOME' as well as starting a 3 min cpuburn run should be accessible via armbian-config so mods/users can try to help other users reporting stability issues by simply asking them to follow a few simple steps (underpowering testing should be accompanied by some USB consumers added after each successful 'Armbian underpowering test' run)
  24. Like
    pfeerick reacted to Yuan in Random no booting issue on OrangePi PC2   
    I did some measurements on both PC (connected to a plastic case wall plug 5V2A rated voltage power supply, actual output voltage is 5.36V), and PC2's (connected to the SMPS mentioned above, actual voltage is 5.40V) from GPIO pins and USB cable ends under load (running stress command):
    I get exact same 5.36V on bot GPIO pins and USB cable ends on PC I get regulated 5.23V on GPIO pins and 5.23V on USB cable ends on PC2 (5.40V->5.23V) As I use these SBC's for headless server use with no USB device attached to them, haven't encountered to any problem. But you may be right that 5.36V is dangerous for USB devices though.
  25. Like
    pfeerick reacted to zador.blood.stained in Orange Pi Zero /4.11.0-sun8i/ wlan0 is gone   
    It just fixes it barely enough to work without crashing (and fix is not related to the xradio driver, it's a kernel-wide fix)
     
    My opinion here would be "definitely no", we had enough crap about this driver and none of that was fixed (packet losses, open AP connection, virtual interfaces, P2P mode, etc.)