• Content count

  • Joined

  • Last visited

  1. after upgrade, wifi will be disabled cause not supported in mainline anymore. That's what happens on experimental, things are tried and if they doesn't work smoothly, they are improved or in this case disabled. Since friendlyelect has for whatever reasons now also have a board with the xr819 wifi soldered on it you might be lucky and they improve the driver (or not, I've no clue if they have it on their todo list). When we talk about 3.4.113 kernel armbian.. Power Management lead to confusion. Whereas Bubba has better results with power management off, my opi0 lived longer with power management on.. (but in my case, it ended every time in a crash... ) IMO, go for a usb wifi stick or another board. I know that this sounds annoying, when you buyed it just freshly... I like my zeros, but I use them just for lightweight IoT server applications connected via cable to my router.
  2. When you started with a freshly burned SD-Card running mainline something like this should appear within your first login. If you did it via armbian-config, something like this appears: or this (if you moved to nightly): And if you had a brief look on armbian download page you would see something like this: and this: I can't repeat your experiment, booted a 4.11.7 image (wifi was visible, cause not deactivated on this image), followed by booting a 3.4.113 image and wifi worked, without any issues (no long-term test!!).. So it might be hard to figure out why wifi on your board is broken now. If you look around here, you'll see that wifi on this board is somehow questionable (just an example, you'll find multiple threads about this issue). A personal opinion: Using a older nightly with 4.11.7 just cause wifi wasn't deactivated by default isn't really smart (you got maybe wifi, but cause you've to freeze kernel and board upgrades, you'll miss all the improvements on board support). It seems that the wifi driver for XR819 is in such a bad shape that nobody wants (or is able) to work on it. If I would need wifi on one of my opi0, I'd go for a usb wifi stick. If I would need wifi permanently, I'd go for another board with better wifi support.
  3. Orange Pi One with nrf24l01

    I think the MySensors library comes also from this one basically. They made it quite easy to set up an nrf24... I left finally cause on arduinos node side they used outdated libraries which messed up with my other projects. I think it wouldn't be such a problem to separate arduinos libs, and get it running but my interests in nrf24 driven nodes is somehow limited.
  4. Orange Pi Plus 2 dies and burns

    means idling without any tasks or with hard load on the system? To quote Igor:
  5. Just a question. Why do you buy a SBC when you want a TV/mediacenter box? The Pi one is a cheap cool SBC but IMO not made for your task. Donald Trump would say: 'Nobody knew that Kodi could be so complicated.' and Angela Merkel: 'Kodi ist für uns alle #Neuland'. To be serious. I appreciate all the work done by developers to get Kodi to work on SBCs. But for me, Kodi on linux driven SBCs is in an early adopters phase, means it runs sometimes smoothly, sometimes not. If you're an end user who doesn't want to spend time in doing the research on which board does a decent job with Kodi, go for a *random android driven tv box*. They are made for such tasks and probably perform better than most SBCs. Maybe you should improve your google-fu... Cause then you will find results like this (search terms: xfce language russian) or this (search terms: xfce russian language package)...
  6. Problem is often not curret, I would recommend 2 amps (as xunlong do) but this is often not needed. The problem of all these small usb chargers is, that the voltage drops when they are running under high load. This doesn't matter if you charge a battery but your orange pi tends to be bitchy..
  7. How much current can they deliver? (what's specified on the PSU doesn't match every time with the reality!) USB port on a PC is not recommended (they're mostly deliver arround 500mA). We've an own subforum for underpowered boards here.. A personal opinion: Before start to think about booting from an USB stick, I would make sure that your system runs smoothly with an SD card. Just to reduce possible variables of failure.
  8. [Question] Arduino IDE in Orange Pi Zero

    Maybe this would help: Moved to: Common issues, cause not really board specific question.
  9. Being rude on your second post isn't smart at all. Don't expect that main maintainer and one of armbian bravest supporter reacting charmest when you claim that they did a bad job. Just for you, I downloaded today an opi zero ubuntu legacy image, burned it to SD card and booted it without issues. If you're not convinced that the issue is 'on your side', there's no reason to stay with armbian in the future for you. If you accept that there might be an 'on your side' issue, we can try to solve it. Hopefully you read in the meantime the getting started guide (igors first link). Unreliable PSU or faulty SD-cards are common issues which led to 'unstable armbian' or not booting at all. That's why we repeat this questions so often, when new users claiming that armbian isn't stable. The same applies for people using win32diskimager or dd when burning the image to an SD-card. Etcher validates the card after burning. Maybe, you hadn't any issues in the past with those other programs, but armbian recommends etcher for a reason and it's worth to use it. So, can you describe your setup? Did you follow the recommendations (e.g. f3 or h2testw to check your SD-Card, good PSU, short and thick micro USB cable)? As soon as we have those informations, we can try to help you getting up your OPi0 smoothly.
  10. Orange Pi Zero H2 Only Red blinking

    Powering through your computers USB? Without Y-cable? IMO a bad idea. Can you describe your PSU when boot fails?
  11. For those of you who're interested in running a CMS on Armbian I've a small tutorial how to get django CMS working. If you're not interested in the 'story' just want a step by step installation guide, scroll to the end of this post, there you find it. Story: Following their installation guide it fails during creation of a django project with 'djangocms -f -p . mysite'. The error looks something like: After a brief google search I found that other also had similar problems. It seemed that pillow is the problem while the whole installation failed. Unfortunately pip pillow also failed, and this one helped me to install pillow. After installation of libpq-dev python-dev libjpeg8-dev, pillow could be installed without any issues and 'djangocms -f -p . mysite' too. Starting the CMS with 'python runserver' worked too but unfortunately wasn't accessible over local network (since all of my armbian devices are running headless, I need access over network to the CMS). Inspired by a next google result, I found out that I should run the CMS on the SBCs network IP not on localhost by using 'python runserver'. Which led in a next error. ... DisallowedHost: Invalid HTTP_HOST header: '192.168.x.xx:8000'. You may need to add u'192.168.x.xx' to ALLOWED_HOSTS. Some housekeeping in the and restart of the CMS led than to a working system. # SECURITY WARNING: don't run with debug turned on in production! DEBUG = True ALLOWED_HOSTS = ['192.168.x:xx'] Lessons learned: Even if you're not a dev and your background is limited, it is possible to get something like this CMS to work if you're able to use google. By reading through google results and have a look on the output errors during installation you learn much more about your project/SBC than just following the step by step procedure I'll show at the end of this post. The 'tarzan approach' - Tarzan/me swings from tree/error to tree/error holding on to elastic lianas/error logs works but it makes sense to repeat this installation after get a straight forward approach for the next time you'll use it. Step by step procedure: Installing package dependencies sudo apt-get install libpq-dev python-dev virtualenv libjpeg8-dev Make your virtualenv folder for all your CMS projects (since django cms is capable to run multiple cms at once it might make sense to have a 'parent folder' where all of them are placed): mkdir CMS --> cd CMS Create and activate a virtual env: virtualenv env --> source env/bin/activate Update pip: pip install --upgrade pip Use the django CMS installer: pip install djangocms-installer Create a new directory to work in: mkdir tutorial-project --> cd tutorial-project Run it to create a new Django project: djangocms -f -p . mysite Setup for access via LAN: nano mysite/ --> ALLOWED_HOSTS = ['192.168.x:xx'] (IP of yor SBC) Start up the runserver: python runserver 192.168.x.xx:8000 Your CMS will be accessible via browser on your SBCs IP port 8000. Tested on: OPi 0: ARMBIAN 5.31 stable Ubuntu 16.04.2 LTS 3.4.113-sun8i Odroid HC1: ARMBIAN 5.33 user-built Debian GNU/Linux 8 (jessie) 4.9.46-odroidxu4
  12. Rock64 armbian image ethernet password

    To my knowledge, root 1234 should work on every board. That's often a sign that something on your system is corrupt. Did you follow the getting started recommendations? (e.g. etcher instead of dd/win32, reliable SD card & psu).
  13. Normally, the idea comes first, followed by buying the right board for the job. Since OPi 0 is prone to overheat (followed by thermal throttling), wifi is somehow questionable and it has no HDMI this board has some server or IoT use cases where performance isn't so important (only usb2, no Gbit ETH). You can build a OMV image (where all your DNLA and torrent stuff can be added and managed via webinterface). IMO the easiest way if you don't want spend much time in configuration etc.
  14. Samba Problem

    The RED led would be the smallest problem... (I think you could change that if you fiddle a little bit around). Raspian from Can you type once uname -r? I'm quite sure it would show something like 3.4.39 kernel. Further you should test (with a non root user): echo "rootmydevice" > /proc/sunxi_debug/sunxi_debug I don't know if they fixed it, but if not this should give you a hint why I would never use a OPi with a OS provided from their web page. Don't get me wrong, I'm a 'proud owner' of multiple oranges. Their boards are nice (OPi0 can be a little bit bitchy since rev. 1.4), but their own software support isn't. I've no clue where you'll use this server but I'm quite sure that you don't want a potentially rootable samba server in the middle of your samba clients.
  15. You buyed the false board (sorry to be so direct). I can't point you to the right direction cause I don't own any H5 boards at the moment. But repeat what's written if you boot up the first time an experimental build (which is the case for every H5 board): Experimental builds can break with every update, that's the reason why they're not recommended for end users. If you want best mainline support on allwinner boards you should have a look here. My recommendation (and that's a personal point of view) is a H3 board. Most headless stuff works on mainline and when not, you can try BSP kernel (3.4.113) to see if it works there. Since you own the board now and probably won't buy a new one soon I would freeze kernel after first boot: armbian-config --> Armbian --> Hold (to freeze kernel and board support packages).