Igor

I am aware of Odroid boot weirdness but if legacy kernel boots than this part should be o.k. ... I promise to play with it but this week I am very tiny with the time Subforum in development regarding "framework / script / building" is done. I am just no sure what to do with R1. It's a lot of topics, yes, even in Free sections are some ..

Doing this blindly is a recipe that it won't work I don't do such way even I have done it so many times. I think at least you forgot to rsync /lib/modules and /lib/firmware from boot image.

By default not possible. I am not that familiar with it to do it manually. Let's just close this topic and move to another.

Just grab latest (4.81) and you will be fine. There are at most three different versions anyway. If you are on the board, booted from SD, just install the deb package and the boot loader is auto written, if you are not than you need to extract the file and DD-it to the SD card (mmcblk0) and not to the partition (mmcblk0p1) The u-boot loader which you found is just for booting from NAND.

I need very detail information, since I don't have Banana PRO ... based on theory / quick checking it should work I have a very similar board (Cubietruck), which is working fine. Support for this chip is build into all kernels.

I don't see any problems ... there is no output to serial console, unless specified ... first boot takes little longer, so you need to wait 1-2min to get login prompt. One reboot is in the middle ... not any more in newer Jessie and Trusty builds. Next edit and change console=ttymxc0,115200 and change loglevel to 7 in boot.cmd, convert to boot.scr ... Than you should see much more. If you did not compile on X86 Ubuntu I can't say what went wrong

@zador I'll try to give some feedback on those changes later today. In one case I am using one such battery and it's working just fine. The other which I use is salvaged from some tablet. No official batteries here

Which modules are you trying and what the iwconfig tells?

@wildcat_paris OK, I'll take a look when possible. You can also try to install kernel 4.4 and DTB on the top of the working legacy build. You will only need to manually set DTB and that's all I think.

Thanks! This is part is unchanged - it's default Debian / Ubuntu way. I also need to Google for this info since I never try to change that. http://superuser.com/questions/443986/how-can-i-remove-the-ssh-last-login-info

Those are needed to boot u-boot and they are *must be* present in u-boot package.

All downloads are v4.5 and need to be upgraded to current version. Check also the docs.

Later Uboot auto detect monitor via EDID but if you got those green lines, that's ok ... as long as it's not UHD monitor 1440p-2160p .. In that case no picture is a normal (bug) behavior. Yes, try to boot without and attach it later ... next check if your script.bin, section for video output is having correct numbers. Correct = HDMI, not correct anything else. http://linux-sunxi.org/Display script.bin/fex file

The board was probably designed in a Broadcomm lab and their PR department fabricated this romantic story with "inventor", "fundation", "sweet fruit" ... to generate more sales.

Yep, it works properly. Now we only need a patch for legacy and we can rely on this parameter

Battery reading works properly [tested on Olimex Lime]... but the bug present in legacy is here too /sys/power/axp_pmu/status_battery_connected is 1 even there is no battery connected.

Both ways should work. If you are changing and tweaking things around double check if kernel installation was done properly after you done that.

I just try with fresh Debian Jessie 4.5. 1. Download 2. Install to NAND 3. apt-get update & upgrade 4. working normally Upgrade might fail if you change some (critical) things, if you ran out of space, ...

Possible if you are using SD boot, not possible if you use NAND. You need to install at least: uboot , kernel and dtb files http://www.armbian.com/kernel/

That's normal. The only diff between micro and lime is a config. Check where your /boot/script.bin points to ... if it's not pointing to proper one, change. So you get nothing on the screen but you can login via SSH?

https://github.com/igorpecovnik/lib/tree/master/scripts/update-motd.d I also did some rework based on those ideas. Battery info is also included, but need further testing. One full charge / discharge cycle is needed for auto calibration. - info that is not needed is hidden: if no updates available, if there is only one user logged, if there is no temperature readings, .... - each info has it's own configurable red point Not included anywhere ... yet. Only testing.

I just figured out there is something else ... need to look further. I just built 4.4 for CT and try USB install. It does not work ... CONFIG_CHR_DEV_SG=y Edit: SATA install works fine.

@zador https://github.com/igorpecovnik/lib/commit/7c1f7c548007d3238a6111f35750b795b4d94c38 boot-next.cmd fell out by mistake? I recreate it in next commit ...

Module has been changed some time ago .. to ap6210.

I read the post too quickly and haven't realized that you were upgrading the kernel too and ... The issue here is, that it has been months since last images build and we are only updating since. Before, we never had this much old images so upgrade time might become a problem. Still, this is completely normal on a PC or any other distro! First you install, than you issue update which can take hours ... if HW is on the level of Cubietruck.