yam1

  • Content Count

    61
  • Joined

  • Last visited

Everything posted by yam1

  1. But those were supposably soldiers buried alive...
  2. I have been having the same problem for a number of images, I ended up having to add a user patch to use the uboot in May.
  3. Thanks to everyone for the work here, so if you use armbian-add-overlay on the created file below, it should just work in the future. usbotg2host.dts
  4. Alternatively, you could use a usb to ethernet connector, this would give you network (my user build next works just fine and boots - I just did it today).
  5. That's right analog sound seems available (as shown by /proc/asound/cards) when using a pine64 5.70 next image with nanopi a64 but no sound ever comes out of the connection, wifi does work.
  6. I haven't, but you may want to try this aufs blog post: https://superuser.com/questions/833576/differences-of-aufs-unionfs-and-overlayfs-from-each-other
  7. If you add anything crappy to your system, your system would become crappy because it is contagious. I always baby mine and they provide me with joy.
  8. Still has SPI 110 errors, but seems less frequent on 4.19.y, double spi and analog audio still works.
  9. Wouldn't you opt for an oled display instead, brighter, smaller, and higher resolution for fifty cents more? And its using only 4 lines, sample usage:
  10. Here are some of my SBCs that are under $20 (see photo below). I have divided them into two categories, with hdmi and not. The ones on the left are without, and on the right are with. The ones without are mostly orangepi's and nanopi's. Just do a search on their web sites and if it is under $20, I have it. One thing to consider is the ones with two spi channels (e.g. nanopi core 1 - note core 2 is better but its over $20), this would allow connecting two spi screens. If you connect two relatively big 3.2 ili9341 screens, with the browser stretched across them, your experience would still suff
  11. CSC supported is just as great as any other boards. The only thing I could not get working is hdmi sound, wifi works fine, both spi channels work fine - but not as well as other boards (more 110 errors), perhaps hardware related? I use it as a laptop with my lap dock, and a bluetooth dongle for sound.
  12. You could easily do that with any SBC discussed in this forum, e.g. k1plus dual screen + bluetooth keyboard, or a zero plus 2 h5, 5 inch hdmi + bluetooh keyboard, or a pi zero with double 18650 batteries and a 2.4" screen
  13. The issue is question is missing spidev argument: param_spidev_spi_bus=0 I can confirm spi_spidev works in 4.17.11. But I could not get other user device tree overlays to work properly in 4.17.11.
  14. Tinker board dual - work in progress:
  15. Fire 3 dual - work in progress:
  16. K1 plus dual with battery power:
  17. Accidentally clicked on kodi while looking for smtube and surprised to see it on my SPI display - no more DRI authentication errors :-) This was on a OPI Prime (H5), kernel 4.17.10.
  18. Happy to report both SPI channels worked properly with 5.47 stable using 4.14.51-sunxi64:
  19. Another Neo Core dual screen version - Neo Core 256mb with USB storage integrated:
  20. Adding one more dual screen SBC, Pine64:
  21. I have no less than 50 SBCs from different vendors, including OrangePi, BananaPi, RaspberryPi, and NanoPi. All of my failures came from NanoPi, so much for providing boards with industrial quality. These were all DOA's: - one NanoPi Neo microSD slot failed to latch, new board, shipping not refunded - two of the mini shields for Neo Core/Core2 failed to do anything - I bought four of these kits, the failures were never refunded - four UNO dock V2 - I bought 4 of these, all of them not working, never refunded I do like the NanoPi boards when they work, but their
  22. Not sure if this has been reported - the usual way of enabling spi overaly "overlays=spi-spidev and param_spidev_spi_bus=x" seems to be broken and when an overlay fails at boot time, it tries to load the base dtb from /.../alllwinner/allwinner/*, note the extra allwinner in the path - so it fails. The pin definitions for the Euler SPI are wrong. When you manage to get both SPIs up. SPI 0 is being enabled as spi1.0 and SPI 1 being enabled as spi0.0. It also fails to merge board neutral ili9341 SPI definition files (at boot time) that has always worked on H3 and H5 boards. To work
  23. It runs almost everything now with Larry's work
  24. In my experience, most of the time the SBC hangs is when all 4 cores are busy for too long the system overheats and CPU scaling causing the system to be unresponsive. CPU scaling does work as far as cutting down the load but somehow the affected processes do not like it and i have to reboot.