Jump to content

Igor

Administrators
  • Posts

    13612
  • Joined

  • Last visited

Everything posted by Igor

  1. Article about Armbian in local / Balcan / Yu computer magazine, Serbian language. selection.pdf http://www.sk.rs/2017/02/sklp03.html http://www.sk.rs/2017/02/sklp04.html
  2. Well, its nice to hear that it survive this much upgrade ... but we have a problem with recent build which is single EXT4 partition and we changed boot scripts, boot loader received one patch ...
  3. Nothing is missing. https://docs.armbian.com/Hardware_Allwinner/#how-to-reconfigure-video-output
  4. @Nerten This does not look to be Armbian boot, at least no recent. This is how it looks like on SD card: I need bootlog from any of those images: https://www.armbian.com/odroid-xu4 written on eMMC. Well, in worse case I'll need to get eMMC and see what's going on
  5. H3 is not yet fully mainlined. We don't use main branch, but development (as stated at download page: Images were built from developement branch.). Nanopi neo from download section has working Ethernet. Tested. BTW: update will fail to bring Ethernet ATM.
  6. Yes, but I am not a god There are things that I simply don't know or would need to waste a lot of time to dig for info and give it to you. I don't provide manual Google service. Try using our search: https://www.armbian.com/search_gcse/
  7. Check this one, with network manager: http://forum.odroid.com/viewtopic.php?f=52&t=25472&sid=84d2b8f1e7ad477e9907591eb7fb030d
  8. Well, if this doesn't help, than I don't know. Mainline H3 kernel is in development phase and can work nice one day and can be completely broken the other day.
  9. None of mentioned thing eats much time., login takes around 1-2 seconds on an fully booted system. Measured on old A20 board ... (only) when system still loads, this can takes 10s or more.
  10. Remove armbian-firmware or firmware-ralink and double check if needed file exists before reboot. Make sure that apt update finished properly, without error code.
  11. Can you provide your network configuration, possible boot logs too.
  12. We can't start to resolve this: - without any logs or - without possibility to reproduce and catch logs. I don't have eMMC card for XU4
  13. I have no idea what you did wrong at self compiled - most likely you failed at writing stage. For diagnosing the problem, you need to provide build logs and you need to do more tests, not just one. What hardware you have is pretty much irrelevant - just follow the guideline: https://github.com/igorpecovnik/lib#how-to-build-my-own-image-or-kernel
  14. What if you use our prebuild images and other writing tool (Etcher) and some other SD card ? Error only indicates some state of fs corruption while "Warning - bad CRC, using default environment" is normal, ask Google.
  15. Now it depends of the use scenario. Old kernel is also not perfect, has bugs and ... it's old, general support is fading. Mainline kernel is still considered development with H3 chips ... so I would not stand on neither side, while I would recommend mainline kernel for older Allwinner chips, A10 and A20. There, it's clearly a better choice in most use cases, instead of old stock kernel. Soon, here (H3, H5, A64, ...) it will be the same.
  16. https://forum.armbian.com/index.php/topic/3267-eth0-stuck-at-half-duplex-orange-pi-zero/
  17. I guess you also doesn't have serial console? We would really like to fix this, instead going back to older schema.
  18. If you want to try, just go ahead, but if it doesn't work you are on your own - pleads for help will be ignored. That's the main difference between supported and unsupported board / kernel.
  19. https://forum.armbian.com/index.php/topic/3267-eth0-stuck-at-half-duplex-orange-pi-zero/ https://www.armbian.com/search_gcse/ half duplex -> first hit
  20. TV module is build in while it's in bad shape and we haven't touch it - it's stock Allwinner. I recently found some related tips on Facebook: https://www.facebook.com/groups/1131759626884432/permalink/1322666627793730/?hc_location=ufi
  21. I also successfully send and receive between Banana Pi running 4.9.7 and Android phone running Android 6.0.1
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines