Jump to content

Igor

Administrators
  • Posts

    13611
  • Joined

  • Last visited

Everything posted by Igor

  1. I don't see much from this video except some errors related to SD card. Such crash can be caused by some bad 3rd party driver, bad power supply, bad SD card, wrong configuration, ... First and the most simple step is to exchange all hardware parts, one by one. SD card, cables, PSU, ...
  2. You started with some very old image, presumably beta at that time. You made several upgrades from that build and you are not very skilled ... it's much better that you start with fresh install. You will save yourself a lot of time and troubles. You will get updated system, resized FS, working CPU scaling ...
  3. Officially perhaps no, but I guess there must be some community builds. This is what I found with quick Google search: http://www.orangepi.org/orangepibbsen/forum.php?mod=viewthread&tid=191 Since Armbian is a solid base, official builds could be made in the future. I know some people at Volumio and will ping / ask them.
  4. There is no 5.04 for Orange Pi Zero since it was added recently and such regression would already be noticed. spidev_test produces O.K. result. Check your python scripts - beware they are not directly RPi compatible.
  5. There is no NAND chip on M1 (unless you have some weird version).
  6. This is completly off topic since it started for Cubox and you are asking about NAND on Allwinner. I assume you want to use it on Cubietruck ? Well, it's not reliable so it's disabled in DTB https://github.com/igorpecovnik/lib/blob/master/patch/kernel/sunxi-next/add-nand-to-cubietruck.patch.disabled For Allwinner A20 better upgrade to 4.9.9 ... there is no benefit of using kernel 4.4.x
  7. Where did you get such an image? We don't produce such a heavy build. Just download our server version and you are ready to go. There are some extra things by default, like build environment and various utilities, but none of those have any effect to load / speed. They only take some space, which is not critical element in 2017.
  8. AFAIK we (used to) have false temp readings (too low) on H2/H3 and they could be adjusted to meet reality? There were lot's of changes in latest update and we (I) could miss to record this one.
  9. Strange, upgrade / kernel install should work this way. Can you catch boot log via serial console, that we can see more?
  10. Warning: nightly downloads are automated untested builds and no end user support is provided for them!
  11. I don't understand what you want to achieve. All those modules are already enabled as (M)odules and they should be built by default. Building this kernel works for me - no errors.
  12. - it's an automated build, - it's built from development kernel 4.x., - it's building for testing purposes, for developers. All this is written at download page in big red box, so that it's hard to miss. I think we need to add more warnings, a popup window or similar, ... Yes, testing image could be broken.
  13. I would say it's a bug in Network manager. I have seen this but it's an rare event. Reboot should help to solve this issue. If it continue to happen, than we would need to inspect.
  14. Developing (Work in progress) mainline kernel has still very limited functionality. AFAIK if you want to use this camera, you need to write / port a driver. This is far for simple / just enabling it in config. Stick to legacy kernel when using multimedia functions.
  15. You are wasting time: https://github.com/igorpecovnik/lib/issues/604 https://github.com/igorpecovnik/lib/issues/592 https://github.com/igorpecovnik/lib/issues/591
  16. Last time (few days ago) I was checking latest Nightly https://dl.armbian.com/nanopiair/nightly/ and wireless was working out of the box.
  17. Why? You choose to use development / preview / beta kernel, where things are clearly not ready yet. Old stock legacy kernel is a better choice. Edit: I moved all H2/H3/A64 images with kernel 4.x to nightly section since you probably failed to read the text below download link: "Images were built from development branch."
  18. https://forum.armbian.com/index.php/topic/3466-mac-adress-of-my-opi-pc-has-changed/
  19. ... setenv video-mode sunxi:1920x1080-24@60,monitor=hdmi,hpd=0,edid=0 setenv rootfstype "ext4" saveenv You need to save uboot environment and it will manifest at second reboot. First saves, second make action. U-boot must have those parameters before reading boot script ...
  20. If you are doing upgrade, it can't work properly. It was clarified in another post - since you also need more recent boot script and DTB which is in repository doesn't have Ethernet enabled. It's only present in download image where you will have network + all cores and further upgrades will work. Remember, it's still developing kernel, which need further testing - there are bugs and limitations.
  21. I just did: - burn Armbian 5.20 (Armbian Xenial CLI) to SD card - login, create user and run nand-install - reboot - apt update & upgrade - rebooted many times just to make sure Everything is fine ... except known bugs. When you do such upgrades, be prepared and it's safer to acknowledge or show errors (than we can fix them if they are ours) to us before reboot.
  22. U-Boot 2012.07-00008-ge2d58a1-dirty (Aug 08 2014 - 20:57:19) for Exynos5422 If you wrote our image to eMMC (via SD card adapter), how is possible that you got this u-boot? Our u-boot has such prompt: U-Boot 2012.07 (Feb 06 2017 - 16:16:49) for Exynos5422 I will also get eMMC, but it will take some time ...
  23. Can you provide build date of your image. We forgot to include video acceleration packages in first build batch, so you could install broken image. If: cat /etc/armbian.txt | grep Build doesn't show 5.2.2017, you need to download image once again, otherwise ... we have a problem. Kodi will not just run. Use Openelec.
  24. It's a common opensource amateur project - you are welcome to fix it too: https://docs.armbian.com/Process_Contribute Otherwise just report and wait until is fixed. No other way. Absolutely normal.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines