Jump to content

Igor

Administrators
  • Posts

    13604
  • Joined

  • Last visited

Everything posted by Igor

  1. Login as root and try with: update-rc.d brcm4330-patch defaults and reboot.
  2. Check the numbers above. Both are O.K. and there is not much difference anyway.
  3. It's a known issue found in all our desktop builds and it would be nice to be fixed once. Since it's a cosmetic I haven't pay any attention yet.
  4. We use the same kernel but few patches and our config. We will put update soon ... Wrote on mobile phone
  5. That thing was fixed, but even in bed I found another problem [ .... ] Building package dpkg-buildpackage: source package libvdpau-sunxi dpkg-buildpackage: source version 0.5.1~armbian5.17+1 dpkg-buildpackage: source distribution UNRELEASED dpkg-buildpackage: source changed by Igor Pecovnik <igor.pecovnik@****l.com> dpkg-buildpackage: host architecture armhf dpkg-buildpackage: warning: debian/rules is not executable; fixing that dpkg-source --before-build libvdpau-sunxi dpkg-checkbuilddeps: Unmet build dependencies: libcedrus1-dev dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting dpkg-buildpackage: warning: (Use -d flag to override.) [ error ] Failed building [ libvdpau-sunxi jessie armhf ]
  6. Can't do much at the moment - got sick and having a bed time , perhaps tomorrow. At least we are one step further - it's not happening only to me. One more thing regarding this - image for Jessie 3.4.112 desktop looks that it's too small.
  7. I am doing test builds and I notice some strange behaviour. First boot is very short and it resets, than we got this: (Orangepi PC+ / legacy / jessie CLI) What was changed / break here? Is this related to my build host?
  8. By adding those two files to: ~/.local/share/keyring/default Default_keyring ~/.local/share/keyring/Default_keyring [keyring] display-name=Default keyring ctime=1473189692 mtime=0 lock-on-idle=false lock-after=false Solves the problem. Wifi passwords are getting stored as plain text and we are not asked for anything regarding this.
  9. DEBUG_MODE is intended to create a (kernel, u-boot) patch out of changes. The name might not be completely adequate to what it does. But it does the job perfectly well and force checkout is a must for proper functioning. Perhaps we could do one IF sentence to checkup this.
  10. There are few files missing from repository so the only way is to compile all ... which takes some time. Will be fixed asap.
  11. For double you most likely need to select other / proper device tree in boot script. I never search to make support for other versions beside Quad.
  12. After this fix, our tools are producing an working image. You only need to recompile boot loader, working source is Denx mainline, branch: v2015.10 There is no NAND support in Vanilla.
  13. Not much output to console from kernel could be normal - change console to serial and enlarge verbosity level or just wait little longer that serial console kick in and / or connect remotely. Initial problem was broken u-boot, the rest is more or less unchanged.
  14. How could you missed this ? http://forum.armbian.com/index.php/topic/1580-nanopi-neo/ http://www.armbian.com/nanopi-neo
  15. If you don't want ram disk, this is the only needed change to boot script: from bootz ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r} to bootz ${kernel_addr_r} - ${fdt_addr_r} This is for sunxi kernel, but similar goes for others.
  16. Try this one: http://mirror.igorpecovnik.com/test/u-boot-sunxi-with-spl.bin dd if=u-boot-sunxi-with-spl.bin of=/dev/YOUR_SD_CARD bs=1024 seek=8 status=noxfer sync
  17. With current u-boot , you clearly can't boot so you need to wait for our update or try to compile recent u-boot version 2016.09-rc2 on yourself.
  18. WICD is / will be replaced with NetworkManager in new builds which is near to bug fixing stage.
  19. DEV branch (as the name indicates) is most problematic and is to avoid. NEXT branch is better but fibre support is not operational. Wireless should work fine here but in both 4.x cases, those are not matured kernels and things can go wrong.
  20. http://forum.armbian.com/index.php/topic/1915-orange-pi-lite-doesnt-connect-to-wifi-networks/?hl=wicd#entry14746
  21. If we have those unique: $CACHEDIR/sdcard $CACHEDIR/armada_default_jessie_no $tmpraw -> "armada_default_jessie_no.raw" which gets final name the same way. Anything else - without detail code inspection ? https://github.com/igorpecovnik/lib/commit/194b730d5c3dd6a8b52462df33ee788ac2a5a182 Probably some better way could be found?
  22. Lowering compression ratio saved almost 3h in total.
  23. Huh. It was booting on mine ... will check again, perhaps I forgot to push something. One thing which could be the problem - since sources were changed, you need to delete: sources/u-boot-udoo before restart the compilation. This will download new / working u-boot source. I am almost sure this is the problem.
  24. Orange Pi PC+ works fine. I have it here on my desk ... have you change SD card, PSU, ... ?
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines