Roland G

  • Content Count

  • Joined

  • Last visited

About Roland G

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Actually, I have found a similar topic question in the forum. "Add: KERNELBRANCH='tag:v4.14.52' to build/userpatches/lib.config" I will give this one a go. ---------- Looks like this was a red herring. I had a look at the relevant git repo and it reports: root@ubuntu:~/build# git ls-remote -t cde3c3fdf278bbf3edc895667a65c0cc16daee0c refs/tags/release-20161011 028bc40a6d227cb553236588c43f35ad7ae2af97 refs/tags/release-20161015 3e00738277533382e6a17148b80b09a8fabea268 refs/tags/release-20170220 49c16833b723b2c4fd0768483790a4f890cf2e10 refs/tags/release-20170417 3467c559d82943f7339578f92b0817b63b8b7ddc refs/tags/release-20170705 5ab215ee7f902201d4830b0b9536135143666b42 refs/tags/release-20171015 2801809213b2ebda0ab877ede0354d48fe95cde1 refs/tags/release-20171213 So the correct structure should be KERNELBRANCH='tag:release-yyyymmdd'. More on rockwell branches/tags:
  2. Actually, I have found a similar topic question in the forum. "Add: KERNELBRANCH='tag:v4.14.52' to build/userpatches/lib.config" I will give this one a go.
  3. I downloaded the kernel source and kernel headers on a rk3288 rockchip (tinkerboardS) and noticed there was a mismatch between kernel version, armbian release and chipset (rockchip64) - see below. root@tinkerboard:~# uname -a Linux tinkerboard 4.4.174-rockchip #7 SMP Sun Feb 10 11:57:26 CET 2019 armv7l armv7l armv7l GNU/Linux root@tinkerboard:~# cat /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=tinkerboard BOARD_NAME="Tinkerboard" BOARDFAMILY=rockchip VERSION=5.75 LINUXFAMILY=rockchip BRANCH=default ARCH=arm IMAGE_TYPE=stable BOARD_TYPE=conf INITRD_ARCH=arm KERNEL_IMAGE_TYPE=zImage root@tinkerboard:/usr/src# ls * linux-rockchip64-default_4.4.178_5.85_config.xz linux-source-4.4.178-rockchip64.tar.xz
  4. I have spent a considerable amount reading docs and getting my head around building a custom default kernel & desktop image. Patching the kernel and optimising the desktop environment is working well. The remaining question is: How do I select a specific - kernel 4.4.174 (based on armbian-release 5.75) ? It defaults to 4.4.176 and 5.86.
  5. I have tried K5.x but the problem persists. It works on 4.4.y but that creates problems with other peripheral devices. I would like to use armbian with the tinkerboardS but for this the hotspot issue needs to be resolved. Due to time constraints this would have to be resolved quickly. Would you be interested in fixing this as a commercial engagement?
  6. When connecting to the built-in wifi adapter (wlan0) on the tinkerboard S (rockchip 3288), the kernel produces a stacktrace and clients can't connect. [ 839.074341] kernel BUG at mm/slub.c:3904! [ 839.078825] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM - (see Is there a fix for this?
  7. ok. so it looks like /sources/linux-mainline/linux-4.19.y/arch/arm/boot/dts/rk3288-tinker.dts sets stdout to serial2 (see below). I have changed it to serial1, then tried to recompile armbian with "" but the dts reverts back to original during the process. How do I stop the automatic update of this file? chosen { stdout-path = "serial2:115200n8"; };
  8. Thanks for the prompt reply. Can you point me to some documentation on how to change console UART in DT? I would not know where to start here.
  9. We are looking at replacing the raspi3b+ with the tinkerboardS (rockchip 3288) in an embedded system, running armbian (bionic-4.19). Initial tests show that OS stability, board performance and form factor make the tinkerboardS a good substitute for the raspi. However, one issue we have run into is a conflict with pin 32 of the GPIO which is used by the hostboard for managing output devices. We have tried to turn off serial2 by removing the UART2 overlay and adding 'console=display' in /boot/armbianEnv.txt and also disabling & masking serial-getty@ttyS2.service but that hasn't stopped pin 32 from being chatty when connected to the hostboard. Is this possible that u-boot keeps writing/reading to and from ttyS2 (pin 32/33) regardless of the set kernel parameters? If so, how do we disable that?