Jump to content

Igor

Administrators
  • Posts

    13589
  • Joined

  • Last visited

Everything posted by Igor

  1. We haven't change anything vital ... what kind of error do you get? Where do you stuck?
  2. It's one of those minor / unimportant issues, for which no one has find time to check what's wrong. If you find out, please provide a fix.
  3. In most cases, problems are drivers and WiFi drivers are among most critical ones. It's actually hard to find a good working one. RTL8812AU was working fine on my brief testing ... but don't actually use it. Not with build in driver, but with this one: https://github.com/gnab/rtl8812au It's easy to compile within armbian, just blacklist the on which is build in if necessary. And make sure you have good - original power supply, USB3 powering is a must.
  4. Video out is currently broken: https://groups.google.com/forum/#!searchin/linux-sunxi/a31|sort:relevance/linux-sunxi/L9oBoyj0MsA/dYidS9BrBQAJ https://forum.armbian.com/index.php?/topic/3281-banana-pi-m2-hdmi-no-signal/#comment-26982
  5. I think the only difference between this openwrt and our legacy is enabled power management (by mistake) in one of our early builds. Disable PM and wifi connecting shoul dramatically improve. Wrote on mobile
  6. how do you power the tablet? is battery operational?
  7. Orane Pi Zero as an IOT node is good enough. To be more precise, transferring data in a client mode with low speed and low range demand, is acceptable, mainline (still development) kernel is recommended in any case.
  8. I guess they realised and Zero2 is getting Ampak 6212, which is much better ... while I saw this crappy wireless chip on one Friendlyelec board (Neo plus 2)
  9. @tao This kernel is still in development phase - we don't provide user support for it and AFAIK new Ethernet driver is in making. It's seem a waste of time to implement temporally workarounds into the user space if proper solution is around the corner.
  10. That's good enough workaround. I guess we need to create a proper systemd compatible startup script. I'll try to implement it to general configuration, now that I know about this problem.
  11. This is the critical part. You will need exact board configuration (script.bin) for your tablet, so you need to find it ... from stock Android, which is probably on your NAND. If you already killed it, than you need to find stock image ...
  12. There are three kernels (two "legacy" 3.14 and mainline) for those boards (cubox, hummingboard 1 and 2, ...) while none is perfect ... Your board is directly supported (have it's own board configuration) only in Solidrun development kernel, which we don't use due to problems with PCI stack. Well, it's possible to build an image with that kernel, but we don't provide downloads and/or support. I don't use that kernel in any way. I would advise you to go for 4.9.5 -> can be upgraded to 4.10.9, but there you will also need to force loading DTB to make this board boot. I'll try to make this process simpler in the future or make a separate DTB files for all those "new" boards, which might need special treatment. But it's some work and I don't have any of this hardware to make a test.
  13. That's correct - as I told, this logo function is not completely done and functional since it has some bugs and I don't know how to proceed.
  14. Your device is not properly recognised by u-boot (which we use stock from Solidrun) so you will need to edit boot script and set correct DTB manually ... which is imx6q-cubox-i.dtb in your case. Put setenv fdt_file "imx6q-cubox-i.dtb" to /boot/boot.cmd and recompile to /boot/boot.scr ... double check if this file exists - it has proper naming in: /boot/dtb/
  15. @Da Alchemist Should be o.k. now: https://github.com/igorpecovnik/lib/commit/71d89e856da2d56fa56822885a30149f7d2ee420
  16. You need a whole patch which include logo: https://github.com/igorpecovnik/lib/blob/master/patch/kernel/sunxi-next/armbian-boot-logo-on-screen-center.patch ... but I am not sure it's working on this kernel.
  17. I just checked again and it's working, also with stock config and connecting to AP. There is a typo / syntax error in one of the guides. This is correct way: echo 'options dhd op_mode=2' >/etc/modprobe.d/ap6212.conf I guess this is the problem ?
  18. Orange Pi PC+ would be recommendation - for general usage - among those cheap boards. Note that there is no web acceleration on any of those boards, which means browsing and watching videos within browser is slow / not usable, while normal browsing is satisfactory. LibreOffice working nice and without a problem. Check videos on Youtube for better picture how it looks like: https://www.youtube.com/results?search_query=armbian
  19. I did and also did't saw AP. Than I try the same on Friendly ARM M1+ which uses the same wireless chip and it's working. Than I used nanopim1plus.bin on Banana M2+ and it's working there too ... which means stock board configuration is messed up.
  20. Don't know. I know there were some problems with WiFi chips on BPi M2 and they replace this chip. I have no idea if this is related somehow. I'll try to reproduce on my M2+
  21. Working on ... Edit 1: some strange problems ... can't boot the board. Edit 2: http://sprunge.us/IcUG with all patches, as is Edit 3: http://sprunge.us/RKBT (only with packaging patch) I guess unrelated to our patches.
  22. None without seeing logs first. Type armbianmonitor -u It's possible that Friendly arm has new version of Air PCB / wifi chip and some adjustment to driver is needed? Can't tell without investigating and talking to FriendlyARM. Perhaps somebody else has more information on the issue? Legacy kernel: FriendlyARM uses their own 3.4 kernel , which we took and add 149 patches which fix waste amount of problems. There is nothing in their Github history regarding different WiFi or board settings. BTW: Dietpi is not different in term of hardware support since they are using our kernel repository for Allwinner boards and don't have own development. Bugs here are bugs there and only we fix them eventually. Mainline kernel. Nightly builds are from "mainline" development branch and kernel is not done. But it works fine on my AIR board out of the box - compare numbers on PCB. It's also possible that your power supply simply does not provide enough power. I use such power supply:
  23. During spring cleaning I found Nokia 128Mb SD card and I could not resist to make the standard test ... which took around one hour to finish I expect worse.
  24. Both kernels and especially last beta image from today works perfectly fine. wlan0 device is controlled by network manager: nmtui-connect, select your SSID, type password and you are ready to go.
  25. This is not a problem but dirty "NAND availability check" ... BTW: for armbian-config testing you only need to switch to beta repository and issue apt-get update / upgrade.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines