vlad59

I'll do that tomorrow, thanks

How can I put it .... Of course you're right

So I retried today. All tests were made with a modified ATX board so the 5V should be clean (I didn't have my multimeter at hand to be totally sure but it really should) without any usb devices . The ambient temperature is between 24 and 26°C (so quite hot) I made two first tests with 648MHz and two tests with 624MHz Both tests failed within 15 minutes. What's interesting is that the soc temp goes above 100°C (103 or 104°C). Does the kernel has a failsafe depending on temperature ? could it be the cause ? lima_memtester is way more stressing that the cpuburn test I made following tkaiser's instructions some weeks ago. Another interesting thing that bugs me is that there never is more that 1 core killed. I remember lurking on a discussion about that a few days ago, maybe we need to more agressive (at least on this board). So far my plan is : * Try to tweak the cooling table to kill 3 cores when cooling state = 5 (other adjustments could be made after) * Add a fan I'm really not a fan of my last proposal as that would mean putting both my nanopi in the trash .

Great so I guess buying two Nanopi M1 before any review was not a good idea ... Thanks for the information Still the tests were made with an USB power supply, I'll remake the test with ATX power supply / GPIO pin to make sure it was not a power problem.

About the cpufreq, I made the change 10 minutes ago, I should have thought of that before .... Sorry . The 2 chips are samsung k4b2g1646q-bck0. If you need something else : a picture / to run a command, I'll do it. Of course I forgot to state the obvious, the cube spin over a light gray background so I think it was good ... After 10 minutes, full screen went lightgray and keyboard / mouse weren't working anymore -> crash ! I may have moved the mouse during the test but I don't think it could be that.

So I tried your image on my Nanopi (as asked on github), I've been optimistic and tried 696MHz First, I got a crash after 10 minutes or so. I tried 672, also crash. I tried 648, still crash within the 10 first minutes. I made a sprunge : http://sprunge.us/hMHS I still have strange ARISC errors so I don't think the DRAM is that bad, there could be a more general problem about Nanopi M1 or maybe the fact that it only have 512Mo of RAM ..... I haven't really checked the log, I'll do it tonight. EDIT : I've attached the rpi monitor graph. The real tests were made after 13:00

Fixed by Igor today. Thanks

Hi, Yesterday, I reinstalled my NanopiM1 and I noticed the download link for H3 devices uses many different versions : orangepipcplus : 5.14 orangepiplus2e : 5.14 orangepilite : 5.13 nanopim1 : 5.10 bananapim2plus : 5.13 orangepi2h3 : 5.10 orangepioneh3 : 5.13 orangepipch3 : 5.14 orangepiplush3 : 5.14 tkaiser explained me why there were both 5.13 and 5.14 (see here) so no problem here. But the 5.10 are quite old and for the Nanopi M1, the dvfs_table included is buggy. I do remember reading of a difficulty to detect the difference between Orange Pi PC and NanoPi M1 but I don't know if that may be the reason. Anyway, I can also add an issue if Github should be preferred for this kind of report.

Hi, I tested to build some deb package yesterday on my Nanopi M1 and it went surprisingly good and quite fast so I wondered ... I know that the documented way of building armbian is with a x64 computer (with Virtualbox / docker). As I already stated I don't have a big enough x64 computer at hand, would it be feasible to tweak the scripts to build one image (not all) using either my Nanopi M1 (but I guess 512Mo of RAM will be problematic) or a Banana Pi / Raspberry Pi 2 ? If not, building uboot / kernel only ? I started to read the scripts, there are many scripts and but I think I can understand many of them individually even if the global architecture is hard to follow. I know that it's certainly not on Armbian's roadmap so I don't want the work done for me, I just want an honest opinion about my question. Thanks in advance.

As a side note, I changed the hostname / fex (as explained by tkaiser) and tried to upgrade my 5.10 install. I got this error Setting up libdpkg-perl (1.17.27) ... Setting up dpkg-dev (1.17.27) ... Setting up initramfs-tools (0.120+deb8u2) ... update-initramfs: deferring update (trigger activated) Setting up linux-firmware-image-sun8i (5.13) ... Setting up linux-headers-sun8i (5.13) ... Compiling headers - please wait ... Setting up linux-image-sun8i (5.13) ... update-initramfs: Generating /boot/initrd.img-3.4.112-sun8i Setting up linux-jessie-root-nanopim1 (5.11) ... Setting up linux-u-boot-nanopim1-default (5.11) ... Setting up openssl (1.0.1t-1+deb8u2) ... Processing triggers for libc-bin (2.19-18+deb8u4) ... Processing triggers for systemd (215-17+deb8u4) ... Processing triggers for initramfs-tools (0.120+deb8u2) ... /boot/initrd.img-3.4.112-sun8i does not exist. Cannot update. root@nanopim1:~# ls /boot/ bin/ boot.scr uInitrd bin.old/ config-3.4.112-sun8i .verbose boot.bmp script.bin vmlinuz-3.4.112-sun8i boot.cmd System.map-3.4.112-sun8i zImage

After making some tests for Jernejsk with Openelec, I reinstalled Armbian on one of my Nanopi M1, I noticed that to the download image is still 5.10 (whereas Orange Pi PC is 5.14). Is this just a glitch or is there a problem I can help with ?

First thanks for this project and thanks for doing this kind of thing to make it bigger !! I can't do much (not enough time in a day) but I can try some stuff anyway : * I can test many things on my devices (3 banana pi, 2 nanopi M1,a bunch of Raspberry PI, and even some Pogoplug, Sheevaplug and Dockstar from way back) * I can help with documentation * I can help with FAQ / documentation translation (in French) if needed. * I've also checked and saw that the project didn't use Travis or another CI, compiling all possible kernels and all the boostrap is certainly not possible but there's maybe some gain in having some check with Travis. My only computers at home are my SBC (the list is up there) and my work computer running Windows so I guess I can't build easily Armbian.

If you're using a fex file then you're using a old kernel 3.4.XXX. Newer kernel use DT

I tried with DTS / AC3 and they're fine. I didn't test passthrough yet but that's on my todo list.

Hi, Nanopi M1 is so similar to Orange Pi One that you can use the amazing work provided by jernejsk and run Openelec using the VPU of the H3. Here are the links : * Main page * prebuilt images list * Github project * The issue I've opened I'm using the embedded IR Sensor with my remote (that was the toughest part) and the only modification I made was to change to cpufreq governor from performance to conservative but if you use the latest image you shouldn't have to do that. Well so far so good. I'm using a little heat sink and the cpu temperature is between 60°C and 80°C depending of the video I'm playing.

About the A20, I knew about the drivers and I checked everything when I put the server into "production" : 5,16V / 270mA idle and 5.01V / 570 ~ 700mA under heavy CPU / MEM / SSD / network load. I has never failed me since (2 reboots and always my fault). I always use good quality 2A certified USB power supply and use an old ATX power supply for testing purpose, I have way more power that any of the SBC I have tested can use.

sorry for the offtopic I don't really care about high performance, I just need a computer that's small enough to be hidden (to please my wife) and that does no use much current as it's has to be up day and night. My current setup with a banana pi has a normal load15 of 0.1 (and is at 600MHz 99% of the time). When it was hosting some websites, the load15 never exceeded 0.5. I simply don't want it to burn / crash / or reboot as as soon as I create a big bzip2 using pbzip2 (parallel) or I make a mistake in a program and use 100% of one core. So I also put a heat sink on my banana pi just to be on the safe side (it's also on the side to ease convection). If I follow you (and the RPI monitor graph) it's not needed at all for the H3, interesting to know ! Thanks

Ok, the heat sink is on the way and I'll make sure to add holes to the 3D printed case. If you need any other test, just ask and I'll do it.

@ @lex The one from here : https://github.com/igorpecovnik/lib/issues/284#issuecomment-216655399

Sorry for the delay, the weather was so good that playing with the nano pi was lower in my priority list . Here is the rpi monitor output. As I said this is without any fan or heatsink and the room temperature is 22.1 °C (mesured by a DS18B20). The soc gets very hot !!!!!

Never used stress before but I think it's not working well. I'll try to explain, I've opened two ssh connections to the nanopi. On one I start stress in foreground, As soon as I type anything (ls for example) on the other ssh window I got this : root@nanopim1:~# stress -m 2 -c 2 stress: info: [4373] dispatching hogs: 2 cpu, 0 io, 2 vm, 0 hdd stress: FAIL: [4373] (416) <-- worker 4377 got signal 9 stress: WARN: [4373] (418) now reaping child worker processes stress: FAIL: [4373] (452) failed run completed in 25s dmesg output show this : [ 946.072340] Out of memory: Kill process 5359 (stress) score 348 or sacrifice child [ 946.072352] Killed process 5359 (stress) total-vm:263848kB, anon-rss:192556kB, file-rss:8kB [ 946.102159] stress: page allocation failure: order:0, mode:0x220da I have no heatsink on my H3 CPU but it doesn't seem linked to temperature.

Hi, It took me longer than expected but my Nanopi M1 is ready running armbian. @tkaiser I made the changes you asked. @all I'm ready to make whatever test you need. My Nanopi only has 512Mo of RAM if that's important to you.

Hi, I received my Nanopi yesterday but I've no µSD card available . I'll try to borrow one from one of my kids and I'll be able to make some tests tonight or tomorrow. I'll keep you posted

Hi Igor, Thanks a lot for the information. I'll contact Stefan and post here.

Hi all, I've been using a banana pi as a home server since forever. It's currently running bananian with a legacy kernel. I want to use docker to make it cleaner to use so mainline is needed. My banana pi is running off a 256Go SSD (SATA) and connected through a Gigabit Switch (that's why I did not find many replacement over the years, both low power, SATA and Gigabits are hard to find even with Hardkernel stuff). So first what's running on my server now : * nzbget * nfs server * nginx as reverse proxy * nginx + php * MQTT server (Mosquitto) * MQTT relay server (with mqttwarn) * homemade domotic stuff For all of this, I guess docker will be ok. Next I'm also using some stuff over GPIO : * a DHT22 sensor * a Nokia 5110 LCD * two pushbuttons * An Uart connected to an arduino (for domotic nodes) I have another banana pi so I installed latest armbian and made some tests. I was using WiringBP (https://github.com/LeMaker/WiringBP) and it seems to be still working with a mainline kernel so the DHT22, Nokia LCD and pushbuttons are OK (even if I was using SPI for the nokia display with legacy kernel and had to bitbang with mainline). For the uart, If I read well I'll have to edit the dtc to enable it (I was using the J11 headers for ease of use). I'll try to read more and do that. So for all that it should work. No the hard stuff : * I was using the csi camera, it seems it's not supported with mainline ? * I also wanted to replace my smallish nokia LCD screen with a larger one (to tell the truth, wife's order), so I naturally thought of using Lemaker screens : 7' or 5' . Again it seems it's not supported. Is there any workaround, alternative ? Thanks in advance and sorry for the long post.