TRS-80

  • Content Count

    501
  • Joined

  • Last visited

Reputation Activity

  1. Like
    TRS-80 reacted to forestj in Free and Libre Open Source SBC List Thread   
    Hi,  I was just in the armbian matrix channel asking about FLOSS SBCs, SBCs which can be booted / operated without blobs or with as few blobs as possible.

    I am not one of those purist Stallmanite zealots who refuse to touch anything which i deem imperfect in the freedom department. Instead I am just trying to be practical and figure out whats the best options for SBCs which respect users. SBCs whose security/integrity is verifiable and doesn't hinge on appeals to authority, like "just trust our secret sauce, it will be fine".

    I want to know about any projects from the past, things that are in progress, and hear experiences from folks who are interested in open source firmware, bootloaders, etc.  I got the general idea from talking in the matrix channel that there are actually more FLOSS-friendly SBCs than a cursory google search might indicate, and I would like to discuss and put together a list.  Goal would be that this can perhaps be published somewhere, I'm not sure where would be the appropriate place on the Armbian documentation or web site, but I can also publish it myself and try to keep it up to date as this is something I'm keenly interested in.

    So, without further adieu, I will start, these are the projects I know about which I'm interested in:

    Bootloader software projects:
    https://libreboot.org/
    https://www.coreboot.org/

    It's not an SBC, but there is this project to have an open source bootloader/firmware linux laptop based on this chrome book: Asus c201 with RK3288
    https://github.com/SolidHal/PrawnOS

    This old open source hardware board I believe can be run with open source firmware but its quite slow and less than 1 GB RAM
    https://www.olimex.com/wiki/A10-OLinuXino-LIME

    Someone from matrix said that the ROC-RK3399-PC (http://en.t-firefly.com/product/rocrk3399pc) can be run without blobs:
     

    Please let me know about any other open source firmware/bootloader for SBC projects that you know about!!
  2. Like
    TRS-80 reacted to jimbolaya in mpd segfault on OrangePi One   
    Armbianmonitor: http://ix.io/2HqW I'm not sure if I should pursue this here or if I should open a ticket through Debian Bugs.
     
    A recent update now causes mpd to segfault. mpd comes from the Debain armhf repository.
     
    I'm not sure how to determine if this is a hardware issue with my board somehow or if there is an interaction with a new kernel or if it's because the package updated the binary or a library.  To make sure it wasn't something weird in my configuration I moved the conf file out of the way and re-ran mpd with the same result.
     
    If it helps, I can post an strace output of the issue.
     
    James
  3. Like
    TRS-80 reacted to arox in Buyng a new board to replace my Banana PI   
    I have exactly the same need, except I am looking for two identical boards : it is my KISS (*) version of a cluster of application, storage and backup server with disk redundancy. One application and storage online server and an other offline backup/archive server with the same content + the archives. So I can switch the boards in case of failure or restore the content of last day in case of file loss.
     
    I use two BPI M1 at present - one having lost its USB ports. One SSD for app and one bigger HDD for bkp. 
    So ? SATA is "has been" and is over-performed my new standards but it fulfill my present requirements, and it is a cheap and conservative solution. TRS-80 is wright : the best is to use USB3 and a converter (you will experience a huge improvement comparing BPI), so you are not limited on the choice of the boards and will continue to use the disks for years. Just, some return of experience will be valuable for choosing one : for my desktop, I buyed a uASP able JMicron controller which is allegedly not compatible with a via controller and seems a bit power hungry. 
     
    So any modern Rockchip 64 bits, reasonably priced fanless boards that do not consume to much power would do the trick for me. (2 boards and 2 "good" adapters). And with OS on disk, no need for eMMC. 
     
    (*) KISS : Keep it simple stupid. Security is antinomic with complexity. And when you experience a hardware failure many years after having put in place the machine and forgotten everything about how it works, the last thing you need is complexity and deprecated, out-of-date, not retro-compatible or not replaceable software or hardware.
  4. Like
    TRS-80 reacted to gounthar in Board Bring Up Station P1 rk3399, M1 rk3328   
    Or is it the other way around?
  5. Like
    TRS-80 reacted to Igor in Allwinner A31s   
    Because we decided to not waste more of our private time and our private money for dealing with hardware "you" purchase for a few bucks. And with "your" endless continuous questions for which you rarely give even a "thank you" for. Not entirely nothing to be fair - you still cover around 0.5% of our running costs with the donations.
     
     
    Armbian has nobody that have time to work for you. How a board gets a support is usually determined this way:
    but there is some grey zone in between. Some boards - where support is cheap in term of time - can skip this process.
     
     
    We didn't hide or break anything intentionally.  What you are looking for, it was not developed at all.  Read this section before you get more ideas what we should or shouldn't do for you. Also look forum https://forum.armbian.com/forum/38-feature-requests/ where is a pile of wishes we have no resources even to read what's about.
  6. Like
    TRS-80 reacted to SteeMan in Please Read First   
    I fully agree with @TRS-80 comments above directing most users towards officially supported SBC hardware options.  However, I do want to add my own personal thoughts on why I choose to continue to use these Android TV boxes with unsupported armbian running on them:
     
    1) It is a challenge and therefore a learning opportunity.  I would never have learnt to build my own linux kernels from source if I was still exclusively using x86 hardware.  If you want a challenge you will find it here.
     
    2) Price vs specs.  The Android TV boxes are built to be cheap consumer devices.  They are produced in larger quantities which drives down the per unit price.  You will generally not be able to get the same level of hardware for the same price with a standard SBC.  But that cheapness with - no support by the manufacturers and potentially sub-standard components.  If the manufacturers goal is to sell the lowest price box they are likely cutting corners somewhere to make that happen.
     
    3) emmc is standard.  TV boxes always come with internal storage while most SBCs do not.  Again from a price/performance standpoint having internal emmc storage vs running off an SD card is a plus.  emmc storage *should* be faster and longer lasting than storage on an sd card.  The caveats here being that this is one of the areas that the manufacturers may cut corners.  For example I have two TX3 mini boxes that are supposed to have 16GB of emmc memory (like the other TX3 mini boxes I have), but they were instead manufactured with cheaper nand memory for which there is no mainline kernel support.  There is no visible difference between the identically packaged boxes that had emmc vs those that came with nand, other than opening the case and looking at the physical chips on the boards.
     
    4) cases come standard.  TV boxes always come with cases, whereas for SBCs that is an extra cost.  For my uses having a case is a big improvement vs not having one.  A downside if that these cases are not necessarily well designed to provide adequate cooling.  So depending on your use case, overheating might be a problem.
     
    While I own both SBCs and TV boxes, I personally find the TV boxes work best for my needs (running server based software) and I enjoy the challenge of getting them running and keeping them running with the great underlying work that the armbian project is doing to build on top of.
     
    I feel that if someone wants to use *unsupported* armbian on TV boxes and has the correct expectations (set your expectations low) and is looking to learn and is up for a challenge these are fun things to work with.  And I look forward to working with you on these forums.
  7. Like
    TRS-80 got a reaction from pomelo in u-boot- files location.   
    Well, I guess I would consider maintaining download links, documentation, etc. and other things you mention as a part of "support."
     
    I think you are very lucky to have @SteeMan helping you.  Which I would also consider "support", by the way...  And also why I don't understand the slightly snide / passive aggressive comments like
     
     
    directed toward people who are trying to help you.
     
    As I said in my first post to you, I can empathize with your frustration, we have all been there.  Please, really stop and consider that for a moment.
     
    Because speaking to other members of the community (especially those rare and valuable people like SteeMan who so selflessly contribute their time and efforts to help others) is not going to be tolerated.  Consider this an official warning from a Moderator.  So maybe take a break or whatever, go for a walk, or at minimum think about how you are talking to people, especially those who are trying to help you, before making your next reply.
     
    Cheers.
  8. Like
    TRS-80 reacted to NicoD in NanoPi M4V2 randomly crashes   
    Update : It was a mesa bug that produced the crashes. 
    RK3399 is now back stable with latest updates. Even at 2Ghz and ondemand governor. 
    But not all problems are fixed yet with mesa/panfrost. The errors in dmesg are still there. And some things that use panfrost will not work. 
    Mesa has had a major update to version 20.2.4. So if you need panfrost, best to use mesa 20.2.3. https://docs.mesa3d.org/relnotes/20.2.4.html
    You can also download the old version of Armbian Reforged with mesa 20.2.3. But be sure not to upgrade for the moment. 
     
  9. Like
    TRS-80 reacted to Narvey in MITM attack? Hash Sum mismatch   
    Like this?
    until apt update; do sleep 90; done  
  10. Like
    TRS-80 reacted to SteeMan in MyGica 1960 S912B trying hard to get Ubuntu installed   
    @FHam 
    First I want to restate some of the basics around armbian on android tv boxes.  1) They are not supported.  2) A single developer (balbes150) has worked years on getting things to the state they are.  3) As of October 14th balbes150 removed support for amlog cpus, so that is the last build that will maybe work on your box, 4) There is a very small number of people on this forum/club that are able to provide any guidance, 5) Most likely no one on this forum/club has ever seen your specific box, 6) Expectations should be set low (i.e. don't expect anything to work) but if you do get the box to boot, get hdmi and wired ethernet to work, you are doing good.  7) Really don't expect things like wifi, bluetooth, remote control etc to work.  8) If you get this working on your box, it will likely only be useful for server type tasks, maybe a little light graphical desktop usage, but certainly not video/multimedia.
     
    There is a lot of information in the two threads you have opened on your installation problems.  I think at this point it would make sense to start from the beginning and step through the basics to try to help you.  There were a couple of very important questions asked of you in the old closed thread that you didn't answer.  I am going to make some recommendations in an effort to try to help.
    1) Use the latest/last build that supports amlogic cpus: https://yadi.sk/d/_rQgn_FosYuW0g/20.10/20201014
    2) Follow the instructions (I agree that the instructions are often not clear) from the first post of this thread: 
    I recently wrote a post that attempted to help someone better understand the instructions for an amlogic cpu as he was having difficulty understanding the instructions from balbes150.  This may help you:
     
     
     
    3) Pay particular attention to the first sentence in red.  If you have ever tried to install other linux builds on this box, stop.  You will first need to restore the box with an original android firmware before continuing.  This is true even if the box is still running android.  The key here is if you have ever 'attempted' to install something else.  The installation process for some other firmwares will modify the booting environment in ways that cause the armbian install to no longer work.  The armbiantv installation is dependent on an unmodified default android environment.  I have more than once solved problems I have had by reverting a box to a clean fresh state by reinstalling the android firmware.  Note, when I say reinstall the android firmware, that doesn't mean using the android functionality to reset the box, it means going out and finding the correct manufactures firmware file and using the low level amlogic tools to install that on your box.  This is one of the questions asked in the previous thread that you didn't answer, which is why I am spending so much time on it.  It is critical that the state of the box be known and clean otherwise we are all just wasting time.
     
    4) In your previous thread you have a screen shot showing you trying to run aml_autoscript.zip from android recovery.  From my understanding if you find yourself in android recovery you are doing something wrong.  No part of the installation process uses android recovery.  I have always been successful with the 'toothpick' method and would recommend you stick with that.  
     
    5)  The extlinux.conf file you posted in the previous thread had a number of errors in it.  Please post the extlinux.conf file you are currently trying to use.
     
    You are working with a box that isn't common.  I have no experience with it.  But by correctly following the installation, you may yet be successful. 
  11. Like
    TRS-80 got a reaction from FHam in MyGica 1960 S912B trying hard to get Ubuntu installed   
    @FHam,
     
    I wish you best of luck in getting this working.  It is possible (maybe?), however can be difficult (as you are perhaps finding out).
     
    If you cannot get it working, or get tired of messing around with unsupported devices, you could also consider starting over with one of Armbian officially supported devices, where you would not only have a much easier time, but also enjoy long term and (generally) much more stable support situation.
     
    Just something to consider.  I really feel bad for you guys struggling with these TV Boxes in here.  But the wide variations and random hardware make them extremely difficult to support.  And without software support, the most impressive specs in the world "on paper" really don't mean anything.
     
    By contrast, I am enjoying a couple well supported devices for a number of years now, they run flawless and for the most part "just work."  Just keep it in mind, the next time you go device shopping...
  12. Like
    TRS-80 got a reaction from balbes150 in u-boot- files location.   
    Well, I guess I would consider maintaining download links, documentation, etc. and other things you mention as a part of "support."
     
    I think you are very lucky to have @SteeMan helping you.  Which I would also consider "support", by the way...  And also why I don't understand the slightly snide / passive aggressive comments like
     
     
    directed toward people who are trying to help you.
     
    As I said in my first post to you, I can empathize with your frustration, we have all been there.  Please, really stop and consider that for a moment.
     
    Because speaking to other members of the community (especially those rare and valuable people like SteeMan who so selflessly contribute their time and efforts to help others) is not going to be tolerated.  Consider this an official warning from a Moderator.  So maybe take a break or whatever, go for a walk, or at minimum think about how you are talking to people, especially those who are trying to help you, before making your next reply.
     
    Cheers.
  13. Like
    TRS-80 got a reaction from devman in Self-hosting micro- (or regular) services, containers, homelab, etc.   
    I have been having some long running, on and off discussion with @lanefu in IRC (and elsewhere), because I know this is his area of expertise.  However he is busy, and I can appreciate he might not want to spend his free time talking about stuff he gets paid to do M-F. 
     
    Then I also realized, certainly I am not the only one interested in Armbian in order to be doing such things.  So I thought I would make a thread about this, instead, to open the discussion to a larger group people here in the broader community.
     
    I have my own thoughts, concerns, things I want to do, and have already done, but I thought I would make a more general thread where like minded people can discuss their experiences, what has worked (or not), what services you might be running (or would like to), etc.
     
    I guess I will begin by saying I have been running some services for family and friends, first on a Cubietruck since maybe 2017 (or earlier?) and then later on some ODROID-XU4 in addition.  I run XMPP server (Prosody) which has been very hassle free "just works" as well as some experiments into Home Automation and other things which have had some, well let's just say mixed results. 
     
    Currently my interest is in containers and like technologies, but I am very new to it.  I been reading a lot, but there is so much to know and I can't help but feel I am a bit late to the game.  That's by design though, as I don't like being (too) early of a technology adopter, generally speaking.  Well, certainly not with such "hyped" technologies like containers, anyway.
     
    In fact I thought it was a bunch of baloney and hype for a long time, but even cranky old cynic like me now sees some advantages of abstracting things, changing servers/services from "pets" to "cattle" if you will, for reproducibility, redundancy, and other reasons.
     
    Anyway, I am prone to walls of text of idiotic ramblings, so I will stop here and give some others a chance.    Hope everyone is enjoying their holiday weekend so far. 
  14. Like
    TRS-80 got a reaction from pomelo in u-boot- files location.   
    I am posting because I can empathize with your frustration, so please take this in the way it is intended (a constructive hint, even if not directly related to the issue you are trying to solve).
     
    So now perhaps you guys start to understand why TV Boxes are not officially supported.  Because getting them to work can be "an adventure" to say the least.
     
    I wish you both the best of luck, sorry I don't know any more specifics which might be directly relevant.
  15. Like
    TRS-80 got a reaction from gprovost in Btrfs scrub causes crash.   
    In the meantime I received a quite interesting reply on my above linked thread from none other than tkaiser himself.  It's quite long and full of lots of good info, but the TL;DR is that I am re-thinking my position on btrfs now, most especially on ARM (while overall, and on x86 especially I maintain my position).  But maybe you guys know all of that already and that's why you use btrfs in the first place. 
     
    However if I am going to shit up someone else's thread, especially with (apparently wrong) information, the very least I feel I should do is return and issue a retraction / update.
     
    Cheers!
  16. Like
    TRS-80 got a reaction from gprovost in ZFS on Helios64   
    @scottf007,
     
    Igor's comment was more directed at the others in the thread who are trying to solve this particular bugbear.  In other words, mostly development talk.
     
    There are lots of clues and instructions littered throughout these forums that will tell you how to get this working.  However if you get too frustrated or can't figure it out, just wait a bit longer and eventually something will be released to make this "easier" for the average Joe.
  17. Like
    TRS-80 reacted to JeremyA in NanoPi R2S: lan0 goes offline with high traffic   
    I did the install of the latest armbian build and the device is now rock solid, no reboots after 18 hours - compared to between one and four hours to failure before the upgrade.
     
    For the benefit of others who wish to repeat the process here are my install steps. I used a fairly powerful debian buster desktop to do the build but it still took some time, maybe half an hour including download time? I chose to only build the kernel elements by answering the prompts from the build script compile.sh
     
    cd /usr/src/ git clone --depth 1 https://github.com/armbian/build mv build build-armbian cd build-armbian/ ./compile.sh docker cd /usr/src/build-armbian/output/debs scp *.deb root@192.168.0.1:~ ssh root@192.168.0.1 dpkg -i armbian-firmware-full_21.02.0-trunk_all.deb linux-dtb-current-rockchip64_21.02.0-trunk_arm64.deb linux-image-current-rockchip64_21.02.0-trunk_arm64.deb linux-u-boot-current-nanopi-r2s_21.02.0-trunk_arm64.deb systemctl reboot  
  18. Like
    TRS-80 reacted to jxj in openwifi an open source fpga 802.11 wifi developer device   
    Thank you renky and thank you TRS-80 for the very good advice. 
     
    This is Xianjun Jiao which is the primary author of the openwifi project. I am being encouraged and inspired by people like you guys. And I do agree that no matter how big the difficulty/risk is we should try it out!
     
    Now I am pushing the USB based WiFi dongle/chip design (in this way, people use openwifi just like any other COTS WiFi dongle!) in my spare time, and already got some progress. I am drawing the schematic and discussing with some hardware experts on the design, and good news is that seems like there is a hope that we can make an openwifi FPGA SDR dongle with price < 100 dollar, which will be much much cheaper than the COTS FPGA development boards currently we support. I believe the cost and "easy-to-use" are two key factors for an open source hardware/chip project to setup a large community (like Raspberry Pi, etc) -- this was also the main feedback I got in the last FOSDEM2020 where I announced the openwifi project for the first time.
     
    Why I see the 100 dollar FPGA dongle as the first step? Because I want the openwifi chip project to be sustainable by itself, not taking external funding as a main supportive source.  Yes we do need funding for some phases, like the board manufacturing and testing phase. But after that, I hope it can go to crowdfunding and sale to hackers/hobbyists/community, and finally make the project survive by itself. With this FPGA dongle, I believe we can already boost the community a lot (much much cheaper than current COTS FPGA boards), and make the chip design more mature, which will be very good preparation for real chip tape out.
     
    You might notice that I mentioned "in my spare time".  This actually reveals the difficulty currently I have. As you might know I work for IDLab which is a joint lab between Gent university (UGent) and imec, Belgium. Although I proposed and started the openwifi project internally at the beginning, the reason why openwifi project can survive for years in imec/UGent is that it is useful for some internal projects. Then I successfully convinced my boss and BD (business developer) to opensource the design from the dissemination point of view, that is why you can see it now. So we should realize that openwifi developers (me and my colleagues) have to work for other internal projects. We can't say we work for openwifi project internally, because there isn't such an openwifi project officially in imec/UGent. Only because openwifi is useful for other internal projects, our job positions are kept and we get salary to raise our families. I tried several times to make the openwifi an official internal project, but so far I am not successful. The imec/UGent business development is quite traditional/old-fashion. They mainly care about using the openwifi for other internal projects and then sell the non-open source license/IP/patent of those internal projects, which is understandable because this mode works successfully for the big company/organization.  So actually they don't care much about the hardware price, the low cost chip/dongle design, and setup a big open source community. That is why I have to try to push the chip/dongle project in my spare time (and also with my private computer, not the company computer!)
     
    I still need to find some time to discuss with my boss to get permission that I am allowed to push the real open source chip direction in my spare time.
     
    In this phase, I believe I can handle most of the technical challenges. But from a project management/advancing point of view, maybe I need very skillful management/operation people's help! Any further advice or spreading/discussion will be appreciated!
     
    Above are some progressions and thoughts. A bit long text and mess situation. Hope I can make it more and more clear in the near future. Keep an eye on the upcoming libreplanet2021, rC3 and fosdem2021, I might have presentations there.
     
    Thanks again for your caring about the openwifi project!
     
  19. Like
    TRS-80 got a reaction from lanefu in A cordial request for help: DTB for MIPI display on SOM-RK3399   
    I read this several days ago, and it bother me, although I didn't know what to say about it.  It bother me for days, actually.  Until today reading this post make me think of you again, so I come searching back and find this thread so I can reply.
     
    When you said
     
     
    I picture you toiling away in your lab, as many of us do, often alone, in order to solve some problem.  I think all sciences have advanced through millennia by such efforts.
     
    I think you just got unlucky with some (very specific) question.  Apparently the right people did not see your thread.  Or maybe no one knows anything that can help.  I have seen many times in these forms people replying to old threads from months, even years ago with some additional information, partial, or full solution.
     
    Anyway, now there is a solution, thanks to your efforts.  I thank you for sharing your results, which I think are even more important as that is the only way we all may advance together.
     
    However, next time you are feeling alone, and/or discouraged, please do drop by IRC and say hello.  Until then, cheers, mate!
  20. Like
    TRS-80 got a reaction from Werner in Btrfs scrub causes crash.   
    In the meantime I received a quite interesting reply on my above linked thread from none other than tkaiser himself.  It's quite long and full of lots of good info, but the TL;DR is that I am re-thinking my position on btrfs now, most especially on ARM (while overall, and on x86 especially I maintain my position).  But maybe you guys know all of that already and that's why you use btrfs in the first place. 
     
    However if I am going to shit up someone else's thread, especially with (apparently wrong) information, the very least I feel I should do is return and issue a retraction / update.
     
    Cheers!
  21. Like
    TRS-80 reacted to cu6apum in A cordial request for help: DTB for MIPI display on SOM-RK3399   
    Thank everybody for MASSIVE support...
     
    Either 5.x kernels are not working with MIPI/DSI, or the DTB structure has changed so hard so I cannot get even a dmesg on whether or not the panel is detected at all.
    Managed to boot ubuntu with 4.4.179 (armbian REFUSED to boot whatever I do), decompiled the old successful DTB, modded the distro one (still no source files; there's only nonworking crap in source tree) and combined.
    After 2 more days I do have the panel alive.
  22. Like
    TRS-80 reacted to fabiobassa in CSC Armbian for RK322X TV Boxes   
    @zero48
     
    ......... night is made for sleeping  for mostly people on the earth, but not for tecnicians ajajajajaj

  23. Like
    TRS-80 reacted to jeanrhum in Implement Device Tree Editor   
    First pull request for me: https://github.com/armbian/config/pull/123
    It is a basic implementation with my humble knowledge in bash. It may be improved by experts if possible.
    I tested on my armbian dev config and it seems to work. I hope to have follow the right way to make a PR since it is my first one.
  24. Like
    TRS-80 reacted to martinayotte in Which kernel is the armbian supported one for OPI Zero H2?   
    It is here : https://www.armbian.com/orange-pi-zero/
  25. Like
    TRS-80 got a reaction from NicoD in NanoPi M4V2 randomly crashes   
    The current status last I read seemed to me that people are currently testing and looking for a solution.  I think it's a regression introduced by newer kernel or something like that.  You can find more info in this other thread which is about desktop however there seems to be a lot of RK3399 specific discussion starting at the post I linked.
     
    Best thing you could do at this point is familiarize yourself with the discussion / issue, perhaps try and modify dtb and other things if you are capable, if not just follow along and give additional testing when more advanced users eventually post their solutions.  Because the evidence becomes much stronger if testing has been done by multiple people to confirm results (instead of jut one person).
     
    Also, if you don't own a UART yet, you probably should to get one (or more) on their way to you in the mail.  They are only couple bucks apiece, and IMO anyone who play with SBC should own at least one!
     
    EDIT: NicoD advice a few posts up (use legacy kernel) or Pedro Lamas' may be best in this case.  I did not read it until after posting.  Understand that as a Mod I read almost everything that is posted, so I end up with shallow (therefore sometimes wrong) understanding on a wide variety of topics.  lol  Don't mind me, carry on.  Some of general ideas in my post still apply, however, so I leave those.  Cheers.