Igor

Administrators
  • Content Count

    10222
  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Raffles

Applications

Calendar

Everything posted by Igor

  1. Have you come here with upgrades or you started with clean image? Stability issues are in most cases related to U-boot and board configuration. Board conf hasn't been changed for a while, uboot is changing constantly. There was the same issue with R1 not long time ago. Kernel and distribution doesn't play any role here.
  2. Some releases had stability issues. Which build do you have? Check: /etc/armbian.txt or /root/readme.txt Last one is stable.
  3. It's possible but usually not recommended, especially setting all to Y. http://serverfault.com/questions/116299/automatically-answer-defaults-when-doing-make-oldconfig-on-a-kernel-tree I already add a lot of tuners. Use my new development config: https://github.com/igorpecovnik/lib/blob/second/config/linux-sunxi-next.config (the script branch will be default when I'll be sure everything is going ok)
  4. Yes, they are all re-uploaded. Maybe you download them too fast? (server needs up to one hour for mirroring) Everything is the same but build date must be today. Build date: 31.08.2015 (armbian.txt inside zip) I test some of them.
  5. (TIME) Time out waiting for device dev-ttyS0 device. Kernel 4.x and Jessie. This problems occur one some boards. Dunno why. It's working fine on my Cubietruck. One solution is to power cycle but if this won't help ... choose Wheezy or Trusty, try also to boot bare board, without anything on USB.
  6. The most important problem here is that NAND is not supported in kernel different from 3.4.x ... If this is ok, than download latest system (4.1.6). You will need to boot from SD card, than change boot script parameter from root=/dev/mmcblk0p1 to /dev/sda, copy kernel files /lib/modules/xxxxxxxxxx from SD card to SDA. Boot from hard drive. Add /dev/mmcblk0p1 to your /etc/fstab and mount under /boot Done.
  7. Hey. No, the problem was here at my web page. I am doing something and I didn't notice that one module was failed Thanks. Everything is back again. For NAND restore you will need to do with Phoenix tools. No other way, sorry. (walk around) BR, Igor
  8. Development is very much open so there is a constant interaction between users and developers. I do most of the distribution development, scripting, some kernel / u-boot patching and basic testing. What I miss, community find and it's usually quickly fixed. No special organization ... but I have top authority. Armbian started as an hobby ROM project for Cubitruck two years ago I am open to re-think and change the organization of the project.
  9. Check if XVID codec is supported. I think it's not. Try if sample video is working: http://samplemedia.linaro.org/H264/big_buck_bunny_1080p_H264_AAC_25fps_7200K.MP4
  10. Igor

    kernel update

    Oh, thanks. True. Anyway, there will be no tar packaged deb files anymore. Everything it is now on the repository apt.armbian.com
  11. At this point upgrade is ready only for advanced users. Repository: apt.armbian.com Key: http://apt.armbian.com/armbian.key Add to sources if not there: deb http://apt.armbian.com $(lsb_release -cs) main Packages naming logic for apt-get install: I. Kernel 3.4: Deprecated linux-u-boot-DEVICE_NAME-default (cubieboard, cubietruck, lime, ...) linux-image-sunxi (all) or linux-image-banana (for boards bananapi, orange, lamobo r1) linux-headers-sunxi or linux-headers-banana (for boards bananapi, orange, lamobo r1) linux-firmware-image-sunxi or linux-firmware-image-banana (for boards bananapi, orange, lamobo r1) linux-$(lsb_release -cs)-root-DEVICE_NAME (cubieboard, cubietruck, lime, ...) I. Kernel 3.4 sun4i (Allwiner A10) linux-u-boot-DEVICE_NAME-default (cubieboard, lime-a10) linux-image-sun4i linux-headers-sun4i linux-firmware-image-sun4i linux-$(lsb_release -cs)-root-DEVICE_NAME (cubieboard, lime-a10) I. Kernel 3.4 sun7i (Allwiner A20) linux-u-boot-DEVICE_NAME-default (cubieboard, cubietruck, lime, ...) linux-image-sun7i linux-headers-sun7i linux-firmware-image-sun7i linux-$(lsb_release -cs)-root-DEVICE_NAME (cubieboard, cubietruck, lime, ...) II. Mainline stable kernel: linux-u-boot-DEVICE_NAME-next (cubieboard, cubietruck, lime, ...) linux-image-next-sunxi linux-headers-next-sunxi linux-firmware-image-next-sunxi linux-dtb-next-sunxi linux-$(lsb_release -cs)-root-next-DEVICE_NAME (cubieboard, cubietruck, lime, ...) You need to install all packages otherwise you might end up with not booting system. III. Mainline or developement kernel: linux-image-dev-sunxi More info: https://www.armbian.com/kernel/ Beta repository: https://forum.armbian.com/index.php/topic/2422-more-proper-testing-better-armbian-experience/
  12. You need to alter boot script on your SD card /boot/boot.cmd and set from root=/dev/sda1 back to /dev/mmcblk0p1 (on the end of this line add loglevel=9 to get more output from kernel boot) Than you need to recompile boot.cmd to boot.scr. Tools: linux computer with installed uboot tools
  13. Can you catch a boot log ? Without this it's hard to say what's wrong ... Do you have onboard wireless? Anything on USB? I am not experiencing any delays. HB boots "like a rocket" (with SSD).
  14. If you are talking about first (updating packages) and second boot (creating swap space), long boot is normal. 2 min is normal. Those warnings / errors are safe to ignore.
  15. There is no display manager (package nodm) Edit the contents of file /etc/default/nodm or install display manager of your choice.
  16. Only remove old conflicting packages, repeat install and you are done. Wrote on mobile phone
  17. I just uploaded new version yesterday where update method is changed / simplified but I haven't updated manual or publish upgrade script yet. I need few days to prepare documentations and to make sure upgrade works on all possible scenarios. Check this: http://forum.armbian.com/index.php/topic/203-416-cubietruck-nexttar-do-not-be-prepared/?p=1174 And this http://www.armbian.com/documentation/ Or wait few days.
  18. I used the default driver implementation - check what an how it works: http://linux-sunxi.org/Cedrus It's not user friendly but hacker friendly Playing of video is normal. In window or full screen. HDMI audio is possible to achieve. http://linux-sunxi.org/Audio_Codec
  19. Thanks. USB / SATA should work but I need to check again if you say it's not working. Maybe it just doesn't auto mount? Can you check to mount it manual? The idea is to provide basic desktop simply because I have not much experiences in this area and because primary target is solid CLI system. I am not sure about GL but if it can be added and if I got some help It can be added.
  20. Video acceleration works (tested) but OpenGLES is failing to compile so it's not included. I hope this will eventually be fixed but can't say when.
  21. You can try with a bit more conservative settings: ieee80211n=1 noscan=1 ht_capab=[SHORT-GI-20][SHORT-GI-40][HT40] with disabling all this. Fast and stable Realtek wireless in AP mode is perhaps expecting too much.
  22. Upgrade for advanced users is ready: Repository: apt.armbian.com Key: http://apt.armbian.com/armbian.key Add to sources if not there: deb http://apt.armbian.com $(lsb_release -cs) main Packages naming logic: Kernel 3.4: linux-u-boot-DEVICE_NAME (cubieboard, cubietruck, lime, ...) linux-image-sunxi (all) or linux-image-banana (for boards bananapi, orange, lamobo r1) linux-headers-sunxi or linux-headers-banana (for boards bananapi, orange, lamobo r1) linux-firmware-image-sunxi or linux-firmware-image-banana (for boards bananapi, orange, lamobo r1) linux-$(lsb_release -cs)-root-DEVICE_NAME (cubieboard, cubietruck, lime, ...) Mainline stable kernel: linux-u-boot-next-DEVICE_NAME (cubieboard, cubietruck, lime, ...) linux-image-next-sunxi linux-headers-next-sunxi linux-firmware-image-next-sunxi linux-dtb-next-sunxi linux-$(lsb_release -cs)-root-next-DEVICE_NAME (cubieboard, cubietruck, lime, ...) Mainline latest kernel: linux-image-dev-sunxi (not implemented yet) If you don't understand what's written above wait for official release together with update script which will fix this for you. Currently under testing.
  23. Yes, now everything will be updated via apt-get. That's also the reason why there is no new .tar package and why I have a lot of extra manual work with this release. Not only the kernel and OS but also "the big picture" - build script was rewritten totally. Next kernel update will be done fully auto on Jessie and half on Wheezy - you'll only need to issue apt-get upgrade command. If you don't want this, you will need to disable it. If you are running old kernel you will stay there and vice versa. Updating will be done within kernel family. I also reduce / combine kernels down to minimum. There are 6 different kernels for all boards now, 4 x legacy: sunxi for majority, special for banana, lamobo and orange, cubox, udoo and 2 x mainline: sunxi and udoo P.S. Building process is half done.
  24. I produce some bug in the middle of the publishing process ... now I need to rebuild most images which are going to be rebuild / updated during the night. The rest (packages and repository) when everything is done and when I got some sleep I'll publish some text about changes and than it's officially online