Jump to content


  • Posts

  • Joined

  • Last visited

  1. Hello, I have an image based on Armbian 5.37 and I have noticed that after upgrading linux-jessie-root-lime2 from 5.37 to 5.60, the Lime2 was not able to get an IP for eth0. The only way is to execute dhclient eth0 I have noticed that a lot of file was added in linux-jessie-root-lime2_5.60_armhf/data/usr/lib/armbian and I think that one of them are responsible of this issue. Do you have any idea on how to fix that ? Thanks
  2. I'm experimenting the same issue with a lot of devices, the 50Mo get filled up very quickly. Most of the time, nginx logs are responsible of that, but also hostapd in some case the wifi dongle is not present. This is very very annoying as the server can not work properly after the log folder is full. The only way is to move/remove files. I removed log2ram, but as I understand zram does the same !!
  3. Hello, I'm using the last Kernel (4.13.3) and U-boot (2017-09). I noticed that the device does not reboot each time we ask for it. It sometime get stuck and I have to start it manually, this is really annoying for my needs. I figure it out that the Device Tree from 4.13.3 introduce some improvement on AXP209 and power management. I tried Device Tree file from 4.11.x and everything seems fine. Does any body noticed it ? Thanks
  4. Hey all, I'm using U-boot 2017-09 and Kernel 4.13. I'm looking for a way to disable the board auto start. I'm explaining. When you plug the power in, the board start by itself and U-boot does the rest. I would like to disable this feature in order to be able to plug in the power, charge the battery if needed and start the board with the regular push button. Is there any tweak to be done in the Device Tree ? Thanks Florian
  5. Thanks for the procedure. Change are quite heavy from 4.11 to 4.12 on Lime2. I wanted to give a try on an older kernel, but I think it does not worth spending time on this. I'd rather try to understand with my device tree fragment does not work any more on 4.13 I'll make a PR on the doc about KERNELBRANCH
  6. Ok I will. I have currently issue during patching from build/patch/kernel/sunxi-next/. Some patch can not be applied against Kernel version 4.11 / 4.12, 4.13 is fine but contains changes on device tree that I does not want. Does the last patch files from armbian works only along kernel 4.13 ?
  7. Hey, I'm trying to lock kernel version to 4.11. The documentation is talking about the variable ARMBIAN_MAINLINE_KERNEL_VERSION, which does not do anything, as the script does not take it into account and still clone the last version of kernel (4.13) I cheat and copy KERNELBRANCH='branch:linux-4.11.y' instead in userpatches/lib.config which seems to do the job. What is wrong then ? Documentation or me ? Thanks Florian
  8. From what I have read, there is no way to use systemd in a chroot. This is quite annoying when it comes to build customization... chroot command could be swaped for systemd-nspawn in the Armbian build framework, does anybody tried this before ?
  9. Hello, I try to use DBus within the chroot and I got this issue : Failed to create bus connection The command used was : hostnamectl set-hostname device_name Systemd does not seems to work within the chroot, do you have any workaround ? Thanks, Florian
  10. Thanks for those advices. Marvell and Intel boards from ESPRESSObin, SolidRun or InHand sounds great, but unfortunately none of them provide an UPS. We can not afford to design a proper one around a SOM module or a carry board that would ingrate such component. @Igor do you know good UPS such as https://www.adafruit.com/products/2465 but with better battery and power management such as the one we can find on Olimex ? Furthermore I'm not sure that AdaFruit products are CE compliant. I never heard of the Atheros 9380. It is seems to be available only as PCIe @hojnikb did you try the Orange Pi Win plus ? it looks interesting. I don't know if all the components are compatible with linux legacy or mainline kernel. I have not seen any Armbian release for this board so far. As you said, using a bridge USB -> SATA can be an issue for data transfers. ITX board are by fare too power hungry
  11. Hello, I'm going to industrialize a project using currently the Olimex Lime2. This board is great and have exactly what I need, among others, battery charger and SATA capability. However I figured out that I can not use this board as there is no CE compliance and thus can not be sold as a product. I'm looking for the fellowing specifications : Run on battery for around 5-6 hours, so the board needs a battery charger Good computation >= 1Gz at least 2 cores Large RAM >= 2GB SATA connectivity: We need to load large amount of data, between 250Go and 1To, so a SSD driver connected to a SATA port is required Good wifi card and linux driver: The wifi hotspot created should at least handle 15 users connected simultaneously An Ethernet port to transfer the data If you have heard of any board having this feature, please share it So far is what I have found : CompuLab SBC-iAM but the technology is quite old Best Florian
  12. Thanks Chris, I mess your comment above. I'm trying to build a new image right now. Unfortunately I'm not using Lime2-eMMC version but only Lime2
  13. I'm having the same issue, try to build Kernel 4.7.5, here is some output : losetup /dev/loop0 output/images/Armbian_5.20_Lime2_Debian_jessie_4.7.5.img mount /dev/loop0p1 /media/ vmlinuz is still in 4.7.3 but dtb in 4.7.5 root@armbiancompiler-VirtualBox:~# ll /media/boot/ total 16504 drwxr-xr-x 4 root root 4096 sept. 29 12:07 ./ drwxr-xr-x 22 root root 4096 sept. 29 11:35 ../ drwxr-xr-x 2 root root 4096 sept. 29 11:27 bin/ -rw-r--r-- 1 root root 6944 sept. 29 11:28 boot.bmp -rw-r--r-- 1 root root 2825 sept. 29 11:24 boot.cmd -rw-r--r-- 1 root root 2897 sept. 29 12:07 boot.scr -rw-r--r-- 1 root root 139450 sept. 14 19:51 config-4.7.3-sunxi lrwxrwxrwx 1 root root 15 sept. 29 11:27 dtb -> dtb-4.7.5-sunxi/ drwxr-xr-x 2 root root 4096 sept. 29 11:27 dtb-4.7.5-sunxi/ -rw-r--r-- 1 root root 4039657 sept. 29 11:35 initrd.img-4.7.3-sunxi -rw-r--r-- 1 root root 0 sept. 29 11:35 .next lrwxrwxrwx 1 root root 13 sept. 29 11:27 script.bin -> bin/lime2.bin -rw-r--r-- 1 root root 2454560 sept. 14 19:51 System.map-4.7.3-sunxi -rw-r--r-- 1 root root 4039721 sept. 29 11:35 uInitrd -rw-r--r-- 1 root root 0 sept. 29 11:28 .verbose -rwxr-xr-x 1 root root 6180832 sept. 14 19:51 vmlinuz-4.7.3-sunxi* lrwxrwxrwx 1 root root 19 sept. 29 11:35 zImage -> vmlinuz-4.7.3-sunxi* root@armbiancompiler-VirtualBox:~# ll /media/usr/src/ total 16 drwxr-xr-x 4 root root 4096 sept. 29 11:31 ./ drwxr-xr-x 10 root root 4096 sept. 29 11:09 ../ drwxr-xr-x 24 root root 4096 sept. 29 11:33 linux-headers-4.7.3-sunxi/ drwxr-xr-x 4 root root 4096 sept. 29 11:31 linux-headers-4.7.5-sunxi/ When boot on this version uname -r show me 4.7.3, how can we build for 4.7.5 ? Thanks
  14. Hey all, I have been running 5 Lime2 during more than 48 hours, downloading and processing data. I set the DRAM just below 480 which is 456. So far I had no hang, no freeze, nothing wrong. This might be not the best value but at least I have a working board, which is a really good news. I'll try the DRAM value 504 as soon as I have a rev E in hand. Best Florian
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines