Jump to content

Igor

Administrators
  • Posts

    13651
  • Joined

  • Last visited

Posts posted by Igor

  1. Hi Igor, thanks for the update. Any reason why the kernel version went down from 4.9.5 to 4.9.4 from the beta repo?

     

    That was pure coincidence. We are preparing to put out update for all images and I made first test build two days ago. Kernel on those images (the one you downloaded) is having higher kernel number but lower package version number than nightly builds ... which are currently on hold due to changes on download server. 

     

    In any case, don't bother with that :)

     

     

  2. To give full support is important to have the board on your desk, hope they send you one.

     

    The core problem is that I / we already have more boards than time to deal with :) We need to skip some boards, but if someone takes the lead and bring in some (similar) device, we will assist. 

     

    Can those A64 devices share one legacy kernel?

     

    My Nano Pi M64 was dispatched, but first we need to expand Amlogic section ...

  3. It's an i4-pro. I have Armbian_5.20_Cubox-i_Debian_jessie_3.14.79_desktop.7z booted fine on the same box (and all previous versions of Armbian). Not sure why it is not recognised, but I will look at forcing the dtb tomorrow

     

    I am pretty sure, the problem is in u-boot, since our boot scripts uses parameters, which are detected by u-boot. There were some recent changes in u-boot and regression is possible - because of latest hw revisions, which brought: eMMC, 4G and HB2. But anyway, just try to set dtb file manually. If that won't help, you need to ask Solidrun to fix u-boot.

  4. I have now Banana Pi M64 booting from eMMC with OV5640, Wifi and GbE working with the correct settings for the board. BT not tested but i think is working also.

     

    So we could (shall we?) add it to the build system? I assume the rest is the same as for Pine64?

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines