Active threads

Showing topics posted in the last 365 days.

This stream auto-updates   

  1. Past hour
  2. Hi, question here. It is quite interesting, Is it possible to get FM working on this chip AP6212A?
  3. 1.24V seems awfully low for h5@1.37Ghz. Did you check if that was actually the frequency, while testing ? in my experience, such high frequencies need forced cooling to stay below 75C
  4. Maybe 816Mhz is the max sustained frequency over a longer period of time. Every h3 board otherwise should hit at least 1.0Ghz on short bursts, if only there aren't any power related issues.
  5. Today
  6. i'm having a problem i don't understand. i'm using @balbes150 armbian ubuntu xenial image for s905 (sticky thread above) on nexbox a95x s905 1G/8G box. the system runs from sdcard without problems, i've been using a previous debian image for about 6 months without any problems. i recently had to modify the box physical setup and touching it (simply pluging an usb cable), the power connector switched off (very annoying thing about those a95x boxes). After that the system would not boot again (no screen display) so i simply figured the sdcard got corrupted. that's what seems to have happened as using a serial connector i get the kernel boot message which at some point hangs and breaks like this : Give root password for maintenance (or press Control-D to continue): last lines : i have attached the full boot log. so i tried fsck.ext4 and it gives me that on the live system : root@amlogic-s905x:~ fsck.ext4 -n -f /dev/mmcblk1p2 e2fsck 1.42.13 (17-May-2015) Warning! /dev/mmcblk1p2 is mounted. Warning: skipping journal recovery because doing a read-only filesystem check. Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Free blocks count wrong (3307614, counted=3307612). Fix? no Free inodes count wrong (868976, counted=868974). Fix? no ROOTFS: 57168/926144 files (0.1% non-contiguous), 479298/3786912 blocks here's my mount output on the live system : not sure what that one is about : /dev/mmcblk1p2 on /var/log.hdd type ext4 (rw,noatime,nodiratime,errors=remount-ro,commit=600) touch /forcefsck, did not fix the problem. the boot process seems to always hang at the same point, then fail to recovery login. But when checking the sdcard i my ubuntu desktop, i don't get any fsck errors. So i'm wondering what's going on.. thx screenlog.0.recovery
  7. Dear all, I'm using Armbian_5.25_Pine64_Ubuntu_xenial_default_3.10.104_desktop. The default display resolution of 720p60 is working fine. When I change to full hd with 1080p60 it's working fine. But when I change to 2160p30 in /boot/armbianEnv.txt it isn't working. Even the eth0 isn't working any more, i.e. the LEDs are not blinking and I couldn't connect to the system any more (additional to the fact that the monitor connected to hdmi is also dark). Has anybody been successful with pine64 and 4K with that image or another desktop image? Best regards, Willy P.S.: I also did the FastEthernet fix "ethtool -s eth0 speed 100 duplex full" and "export http_proxy=...; apt-get update; apt_get upgrade" on the plain vanilla image. That's all before testing the display resolutions.
  8. i believe that @Shimon mentions the fact that s905 max real clock is 1.56GHz (not 2GHz as reported by the amlogic kernel), and there has been some work to try and "fix" that (by amlogic ? in the latest s905x kernel ?), and that fix would also try to make the s905 run a little faster (1.75GHz?).. Personally i don't think it'll make a difference but of course it would be nice to have real clock speed data in your system.. For an apparently far more powerful soc, i'm now looking at the rockchip rk3288 ("old" 32bit soc with turbo mode of 2GHz maybe 2.2GHz?), available on the Miqi and asus tinker board. For example performance with openssl on a single thread is 40-60% faster than on s905 (which is already quite fast) and on par with big boards like xu4..
  9. Thanks. Did I undertand you correctly? It's best gpu support that I can get from this build(5.27 debian). For s905 this build provides gpu driver and vdpau facility. Anyway thank you for build. I am gonna use it as headless server.
  10. preview

    On quick comparison there are few minor differences - LEDs are wired differently, eMMC section is useless but generally it should work with MiQi dtb. Have you try? If it works, we only need to create a patch to create this file. Put our tools into "create patches" and when prompted, create a rk3288-miniarm.dts file with adjusted LED gpio and removed eMMC. Than push resulted patch (when tested) to patches/kernel/rockchip-dev
  11. Hello! I'm using Wheezy under kernel 3.4.x on Lime2 with 7" LCD and i added fbcon=rotate:1 in boot.cmd and the console booted in portrait but LXDE is still in landscape. I also added FBDEV_ROTATE_CCW=90 but with no results. I can rotate the screen from the /usr/share/X11/xorg.conf.d/XX-fbturbo.conf file but every time i touch the screen the LXDE crashes. Any suggestions please how to rotate the screen in LXDE? Thank you!
  12. Just a thought. the boot loader offset locations *should* be hardware bound by the SoC, there shouldn't be any difference between MiQi and Tinker Board unless the MiQi is using an SPI device to load a bootloader, but that does not sound like the case. With the cat command throwing it's data away instead of adding it to the output binary, the Tinker Board did exactly as you describe here, only showed the U-Boot SPL message.
  13. Yesterday
  14. UPDATE: After several trial and errors I found out, probably, it is related to THIS sudo /home/user/hyperion/build/bin/hyperiond /home/user/hyperion.config.json. Because when I run this script via rc.local and then manually hyperion-v4l2, then behaviour is the same.
  15. I just wanted to put my idle Cubox 4x4 to work for personal projects. If I would use it for something real, I would definitely go your way.
  16. ____ _ _ _ _ / ___| _| |__ (_) ___| |_ _ __ _ _ ___| | __ | | | | | | '_ \| |/ _ \ __| '__| | | |/ __| |/ / | |__| |_| | |_) | | __/ |_| | | |_| | (__| < \____\__,_|_.__/|_|\___|\__|_| \__,_|\___|_|\_\ Welcome to ARMBIAN 5.27 stable Debian GNU/Linux 8 (jessie) 3.4.113-sun7i System load: 0.92 Up time: 1 min Memory usage: 4 % of 984Mb IP: 192.168.1.77 CPU temp: 34°C Usage of /: 15% of 7.2G How can I change this logo?
  17. hi peter, you can copy the same fstab on opi, without the boot partition (remember to create the correct partitions for unionfs and copy there the current contents of etc and var). why you are using unionfs for home and media?, i think that is better if your app stop to write on home and use some folder on tmp (but this is only my opinion) the cmdline.txt of the opi is the /boot/boot.cmd on opi, but i'm not sure that works as the opi, the opi bootloader is different, and you have find the correct row. by the way i've some trouble with the opi (i can do it on rpi) if i need to restore the the system (for example to install some other package). It is useful in development stage.
  18. I tried this script but some commands do not work at all: + ip link set lan1 master eth0.102 RTNETLINK answers: Operation not supported
  19. H2+/H3/H5 boards overview (2017/03 update) Since it has been a while since this topic has been updated and a lot of new boards have been released in the meantime it's time for a new overview. I'll add also H2+ and H5 based boards since in the meantime we learned that those SoCs are pin-to-pin compatible and recently vendors started to simply exchange H3 with H5 on some PCB (and vice versa in at least one occurence). From a software point of view H5 is quite different (using 64-bit Cortex-A53 CPU cores and ARMv8 instruction set, some early boot stages are also totally different compared to Cortex-A7/ARMv7 used in H3 and H2+) and it should also be noted that Armbian currently only provides OS images based on mainline kernel for H5 boards (so please forget about HW accelerated video decoding or 3D for now or maybe ever since none of the developers is in the mood to deal with Allwinner's BSP/legacy kernel for H5 (regarding 'BSP' just look above in post #2). While software support for H5 is currently somewhat different hardware features are pretty much the same as with H3 (still 3 to 4 real USB2 host ports and one USB2 OTG port: a simple register setting can switch the Micro USB port's PHY between the so called 'musb' controller used for OTG and a real EHCI/OHCI controller pair: with mainline kernel it will soon be possible to switch OTG to a real 4th USB2 host port with full feature set that still has not to share bandwidth with any of the other USB ports). CPU performance with H5 compared to H3 is slightly higher at the same clockspeed but some workloads that benefit from either 64-bit or ARMv8 instruction set are significantly faster (eg. software making use of NEON instructions might perform almost twice as fast and the best example is the stupid 'sysbench' CPU pseudo benchmark which shows over 10 times better scores on the same hardware when compiled with ARMv8 settings). In the following list I will also introduce some subjective 'categories' to deal better with the huge amount of boards we can use in the meantime: NAS category: these are the H3/H5 boards with Gigabit Ethernet IoT category: these are the small and cheap boards best suited for low consumption 'General purpose' category: all the other H3 devices, these are also those you should look for if you want a cheap device to run with X11, OpenELEC, RetrOrangePi or Lakka since they all feature HDMI and full legacy kernel support As already said the differentiation is subjective and partially misleading since new boards like NanoPi NEO 2 featuring Gigabit Ethernet are also that inexpensive, small and energy efficient that they could serve both as NAS and IoT nodes (actually you can somewhat control behaviour since GbE vs. Fast Ethernet makes a pretty huge difference in consumption so it's up to you). Boards that might fit in multiple categories are listed more than once to make comparisons more simple if you're only interested in a specific device category: NAS category (only due to Gigabit Ethernet available): Banana Pi M2+: H3, 1GB DRAM, 8GB slow eMMC, 1+2 USB ports useable, Wi-Fi/BT Banana Pi M2+ EDU: H3, 512MB DRAM, no eMMC, 1+2 USB ports useable NanoPi M1 Plus: H3, 1GB DRAM, 8GB slow eMMC, 1+3 USB ports useable, Wi-Fi/BT NanoPi M1 Plus 2: H5, 1GB DRAM, 8GB slow eMMC, 1+3 USB ports useable, Wi-Fi/BT NanoPi NEO 2: H5, 512MB DRAM, no eMMC, 1+1+2 USB ports useable NanoPi NEO Plus 2: H5, 512MB DRAM, no eMMC, 1+2+2 USB ports useable, Wi-Fi OrangePi PC 2: H5, 1GB DRAM, no eMMC, 1+3 USB ports useable OrangePi PC 3: H5, 2GB DRAM, 16GB fast eMMC, 1+3 USB ports useable, Wi-Fi OrangePi Plus: H3, 1GB DRAM, 8GB eMMC, 1+4 USB ports useable (hub), Wi-Fi OrangePi Plus 2: H3, 2GB DRAM, 16GB fast eMMC, 1+4 USB ports useable (hub), Wi-Fi OrangePi Plus 2E: H3, 2GB DRAM, 16GB fast eMMC, 1+3 USB ports useable, Wi-Fi IoT category (cheap, small, energy efficient, most of them headless): NanoPi Air: H3, 512MB DRAM, 8GB slow eMMC, 1+1+2 USB ports useable, Wi-Fi/BT, no Ethernet NanoPi NEO: H3, 256/512MB DRAM, no eMMC, 1+1+2 USB ports useable, Fast Ethernet NanoPi NEO 2: H5, 512MB DRAM, no eMMC, 1+1+2 USB ports useable, Gigabit Ethernet NanoPi NEO Plus 2: H5, 512MB DRAM, no eMMC, 1+1+2 USB ports useable, Wi-Fi, Gigabit Ethernet OrangePi Zero: H2+, 256/512MB DRAM, no eMMC, 1+1+2 USB ports useable, Wi-Fi, Fast Ethernet OrangePi Zero Plus 2: H3, 512MB DRAM, 8GB fast eMMC, 1+1+2 USB ports useable, Wi-Fi/BT, no Ethernet but HDMI General purpose (HDMI and full legacy kernel support: video/3D HW accelerated): Beelink X2: H3, 1GB DRAM, 8GB slow eMMC, 1+1 USB ports useable, Wi-Fi, Fast Ethernet NanoPi M1: H3, 1GB DRAM, no eMMC, 1+3 USB ports useable, Fast Ethernet OrangePi Lite: H3, 512MB DRAM, no eMMC, 1+2 USB ports useable, Wi-Fi, no Ethernet OrangePi One: H3, 512MB DRAM, no eMMC, 1+1 USB ports useable, Fast Ethernet OrangePi PC: H3, 1GB DRAM, no eMMC, 1+3 USB ports useable, Fast Ethernet OrangePi PC Plus: H3, 1GB DRAM, 8GB fast eMMC, 1+3 USB ports useable, Wi-Fi, Fast Ethernet OrangePi Zero Plus 2: H3, 512MB DRAM, 8GB fast eMMC, 1+1+2 USB ports useable, Wi-Fi/BT, no Ethernet pcDuino Nano 4: See above, it's just an OEM version of NanoPi M1 done for Linksprite Some important notes: The following boards are listed in more than 1 category due to advanced feature mix: NanoPi NEO 2, NanoPi NEO Plus 2 and OrangePi Zero Plus 2 CE/FCC certifications: Please check individually and don't trust in logos silkscreened on the PCB, even if it looks like 'CE' it might mean 'China Export' instead IO bandwidth: H2+/H3/H5 SoC features 3+1 USB2 ports but on a few boards an internal USB hub is used so while these expose more USB receptacles some ports have to share bandwidth. Also on these boards a buggy/slow GL830 USB-to-SATA bridge is used. Search for 'hub' above to identify them. eMMC: shows most of the times higher random IO performance compared to 'the average SD card', but some vendors use pretty slow eMMC on their boards (Xunlong being the exception with OPi PC Plus, Plus, Plus 2, Plus 2E and Zero Plus 2). Please do not overestimate eMMC -- there's no need to choose crappy/slow SD cards and if you follow the usual recommendations difference in performance varies not that much (for example eMMC on most boards shows pretty low sequential write speeds that will be easily outperformed by any good SD card and differences in random IO don't have to be that huge, simply watch out for SD cards showing A1 or even A2 logo) USB ports: Some of the IoT devices have two of the SoC's USB host ports available on a pin header to be used with soldering or combined with various Docks, HATs or 'Expansion boards' (search for '1+1+2' above). On OPi One/Lite the unexposed USB host ports are available at pretty tiny solder pads so only usable with a lot of soldering experience Wi-Fi/BT: all boards providing both Wi-Fi and BT rely on Ampak's AP6212 so performance is identical, the Wi-Fi only boards either rely on RTL8189ETV/8189FTV (slightly better Wi-Fi performance than AP6212) or Allwinner's XR819 (so expect low Wi-Fi performance with OPi Zero or NEO Plus 2 since implementation is low-end and currently driver sucks) Yeah, each vendor's naming scheme totally sucks. Partially there are rules involved (the 'Plus' then means eMMC with Xunlong or GBit Ethernet with FriendlyELEC... mostly) but please don't trust in and check always individually! And now another few words on a different technical detail affecting both performance and thermal behaviour of the various boards: Voltage regulation / DVFS. TL;DR: the SoC can be fed with a variable voltage (VDD_CPUX), the lower the voltage the lower the temperature (less problems with heat/overheating), the higher the voltage the higher the maximum CPU clockspeed. So the best idea is to adjust this dynamically (low voltage/clockspeed when idle and only increasing both when needed). There are 3 variants to implement this: not at all, primitive or advanced (using a voltage regulator that's able to adjust VDD_CPUX in 20mV steps) Only 3 devices implement no voltage regulation at all: Banana Pi M2+/EDU (frying the SoC constantly at 1.3V therefore prone to overheating), Beelink X2 (no idea) and NEO 2 (only 1.1V therefore limited to 1008MHz cpufreq max since above instabilities might occur). Some boards use SY8106A I2C accessible voltage regulator where we can use fine grained voltage settings (Armbian fine-tuned these for every board so far to achieve max performance). This applies only to the following Xunlong boards: OPi PC, PC Plus, PC 2, PC 3, Plus, Plus 2 and Plus 2E. All other boards implement a simple two voltage scheme and are able to switch between 1.1V (up to 912MHz possible with H2+/H3 or 1008MHz with H5) or 1.3V (1.2GHz max with H2+/H3 and 1.25GHz with H5) And finally to add some stupid rankings: the cheapest board is from Xunlong (Orange Pi Zero: $7), the fastest is from Xunlong (Orange Pi PC 2 for $20) and the one with best feature set and onboard peripherals is also from Xunlong (Orange Pi Plus 2E: $35). And that's only due to OrangePi PC 3 still not being released at the time of this writing (since otherwise regarding both performance and features this specific Xunlong board... ) Hope that helps
  20. Installed tightvncserver and sudo apt-get install xfonts-base. When I try to connect and see the "foto". How can I fix this?
  21. Maybe following these steps in other thread but changing Spanish by Dutch. For me the key step is purging the existing locales.
  22. Thats true. But despite the speed limitation it seems stable so far. However, there is one warning I keep getting: [ 30.600191] drivers/video/owl/backlight/owl_pwm_bl.c/owl_backlight_is_on: get backlight failed! I tried to disable this module before compiling the kernel, but could not found it exactly. Do you have a clue? How can I get more info on the error, to better lead me to its corresponding module on the kernel?
  23. Hi hojnikb, I just did what you say, and it works perfect. Thank you very much
  24. Was never implying that. I'm sure you have hard data to back up this claim. Well, if friendlyelec images are all fine and dandy, why the hell do we have armbian for h3 in the first place ? I mean, if their images are top notch, a modification of their images for other h3 products (like from xunlong) would be more in place. Like this Again, rudeness isn't really fitting for a technical forum like this.
  25. preview

    Anyone wanting to express his personal opinions only or discuss off-topic stuff, please feel free to do this in this splitted thread now and let's focus here on information and development towards NEO2 and NEO Plus 2. Thanks.
  26. Hello guys, at the moment I have big trouble with setting orange zero as AP. If i use legacy version I can setup AP properly, but at nightly version I continually getting resets or bootloops. I have tried 5.27.170321, 5.27.170323, 5.27.170324 with same result. Here is my listing from serial console if I want to start hostapd: Can anyone help me resolve this problem please?
  27. Thank you guys, actually i'm working on luks encryption method + dracut-gmcrypt, i trying to use a key generated from mac address of pi, but actually the biggest problem is to luks a existing image system on pi...i have found this for luks in place conversion, but i give a segmentation fault during the encryption progress and nothing works
  28. I am very sorry,no, no it is no massage from Armbian,that is what I see on screen of my computer. I go install Armbian again with"Etcher" and install it.Please don,t compare my knowledge about computer with yours. For me is this a wonderful discovery process.
  1. Load more activity