Igor

It looks like BSP package is missing from our index/repostitory or there is some problem with your image. I'll check.

I download it from here: http://downloads.slimdevices.com/nightly/?ver=7.9 The exact command list: wget http://downloads.slimdevices.com/nightly/7.9/sc/70b0c7c/logitechmediaserver_7.9.1~1515516449_arm.deb dpkg -i logitechmediaserver_7.9.1~1515516449_arm.deb After installation is done, WEB control is accessible on http://your_tinkerboard_ip:9000 Worked for me. Debian Stretch. Type lsb_release -a (since sprunge.us is currently down and I actually can't see anything) No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 9.3 (stretch) Release: 9.3 Codename: stretch

Armbian will not be more ready or more KODI friendly. Even on most "perfect" and "compatible" Intel hardware this is not as simple as you expect: https://forum.kodi.tv/showthread.php?tid=231955

Armbian Ubuntu or Debian Stretch? (or type armbianmonitor -u)

Then try few older kernels, oldest in the repository is: http://apt.armbian.com/pool/main/l/linux-4.11.4-sunxi/ I am running Tvheadend on 4.13.16-sunxi64 and I don't encounter problems of this kind. Well, it's a different board ...

armbian-config -> alternative kernels -> default Is it ok?

Not exactly. RK3328 is not the same as RK3288

Strange. I assume you have a network connection?

Yes, it is. We only support arm and arm64 architecture. Where - for what purpose - do you want to use armbian repository?

You can find mainline kernel here: https://www.kernel.org/ more precisely, most recent (stable to be) branch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/tree/?h=v4.14.12 + all those patches https://github.com/armbian/build/tree/master/patch/kernel/sunxi-next and you are there. If you are running beta builds and you want a patched complete H3 mainline kernel source on your board for whatever reason: apt install linux-source-4.14.12-next-sunxi If you plan to cross-compile, check this: https://github.com/armbian/build Add: one of the options is also sunxi-next branch at https://github.com/linux-sunxi/linux-sunxi

It does not exist in Debian Stretch but its function ... making a proper systemd service would be a better way, surely. We also have this first_run logic, worth mention at this place: https://github.com/armbian/build/blob/master/packages/bsp/armbian_first_run.txt.template

You can try adding this (before exit 0): sleep 10 # just in case since this is a dirty workaround nmcli device wifi connect UUID echo "password"| nmcli --ask c up UUID to your /etc/rc.local and Wifi network should be established. BTW: serial console looks like this on Windows, when powering/connecting via the OTG USB port:

This is a lot better. Tinkerboard is not able to function properly without attaching anything to its USB port (is unstable by default due to the insufficient powering method), while here I see another wifi adaptors, which BTW can work stable (Atheros AR9271) if properly powered. I can't tell for sure for the one on the board - I haven't test it very well under modern kernel. Try without anything attached to the board and try not to push CPU when trying this and try alternative drivers as already exposed. ii linux-headers-4.4.0-104 4.4.0-104.127 all Header files related to Linux kernel version 4.4.0 ii linux-headers-4.4.0-104-generic 4.4.0-104.127 armhf Linux kernel headers for version 4.4.0 on ARM (hard float) SMP ii linux-headers-generic XXX.XXX.0.104.109 armhf Generic Linux kernel headers Wrong. Remove those and install those from our kernel. Run armbian-config -> software -> install headers.

Well, only with Armbian (beta)

Probably the driver is not the best ... you can try to build some alternative driver: https://github.com/search?q=8723 Remember to blacklist existing driver and download headers - which you need for driver compilation - from armbian-config. Example. BTW. When asking for tips or seeking help, you have to tell us more than a vague description. We need to know everything, at least what is possible to collect automatically: armbianmonitor -u

Please describe your setup as best as possible so we know what your operating environment is like. Name of your board with all details, version number, take a picture if you are not sure what you have Name of the image you installed or logs, when you can boot the board: armbianmonitor -u (paste URL to your forum post) If your board does not boot, provide a log from serial console (UART) or at least make and attach a picture, where it stops. Describe the problem the best you can and provide all necessary info that we can reproduce the problem. If anything is attached to the board, supply all details How do you power the board?

This is normal. We only pushed an update to packages which had some troubles - board support and left others as is. I started with a clean image made from sources and could not reproduce problems you have. Here is my armbianmonitor -u: http://ix.io/DLr It was wrong permission for this file: /etc/cron.d/armbian-updates

We are struggling to put things together. Building A64 is currently (partially) broken. In Armbian and upstream ... broken net, USB and thermal are known shortcomings. The primary goal is to come out with the first stable (non-development) kernel around 4.14.y for which we will take care on a longer period ... with A10, A20, H3 and H5 this is done or close to, while A64 is more distant. Our resources are micro/mini/amateur and progress is as is.

How about now?

I had troubles with images above - sometimes network was not recognized ... so I tried to put together mvebu-next with 4.14.12 ... I only used DT from legacy, no other patches. The network works, CPU scaling works, SATA works, ... Fans. One is spinning fast and one slow. I didn't even try to resolve this PWM thingy. Download page: https://www.armbian.com/helios4/ Boot logs: http://ix.io/DIO Yes, I quickly find out that you need at least two drives so I added one at the bottom and case become stable. Eventually, I ended up in "engineering mode"

Dont know anything about this wireless chip found on recent boards. All mine have old Broadcomm chips which works. Perhaps only firmware is missing? Wrote on mobile

Nice! Known (upstream) bug, AFAIK unresolved.

Mount SD card on some Linux and add: fdt_file=imx6dl-hummingboard-som-v15.dtb or if you have HB2 fdt_file=imx6dl-hummingboard2-som-v15.dtb to the /boot/armbianEnv.txt If you have eMMC version then imx6dl-hummingboard-emmc-som-v15.dtb and imx6dl-hummingboard2-emmc-som-v15.dtb

Yes, you can. https://github.com/armbian/build

@zador.blood.stained Merging 4.4.y kernels from Marvell seems a bit problematic and wasteful. Shall we implement this workaround to the mvebu.conf: https://github.com/armbian/build/blob/master/config/sources/mvebu.conf#L16 if [[ $BOARD == helios4 ]]; then KERNELSOURCE='https://github.com/helios-4/linux-marvell' KERNELBRANCH='branch:linux-marvell-4.4' KERNELDIR='linux-helios-4' LINUXFAMILY=helios4 fi Mainline target remains mvebu-next. Any better idea?