sgei

Members
  • Content Count

    34
  • Joined

  • Last visited

About sgei

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

705 profile views
  1. Hi, add rmmod sun4i_gpadc in /etc/rc.local But I do not understand why there is no real fix for this problem. Steffen
  2. Hello, I know there are some threads regarding this issue, but there does not seem to be a correct solution. Since kernel 4.14 (or maybe earlier), there are some Kworker processes that consume 10-25% CPU. In May 2018 I once had an image built with the kernel 4.17.13. With this the problem had disappeared. But now with the DEV-kernel 4.19.X it's back. Can someone please investigate or say something about this? Steffen
  3. Hi, ist it possible to select a specific kernel version in the build tool (not only next, dev ...)? I need kernel 4.17. Thanks. Steffen
  4. Hi, thanks for the quick reply. I will try to build a new image with the *.eos config. Thanks. Steffen
  5. Hi Igor, hi team, we are using Armbian since the the first version. We only using it with Banana Pi and Banana Pi Pro. Yesterday I wanted to build a new image for our BananaPro projects, but unfortunately there is no support for Banana Pi Pro anymore. Why? Is it possible to continue supporting this board? What is the difference to the Banana Pi? You still support Banana Pi. Thanks. Steffen
  6. root@bpro:/etc/armbianmonitor/datasources# ll insgesamt 0 lrwxrwxrwx 1 root root 27 Aug 8 12:03 pmictemp -> /sys/power/axp_pmu/pmu/temp lrwxrwxrwx 1 root root 47 Aug 8 12:03 soctemp -> /sys/devices/virtual/thermal/thermal_zone0/temp root@bpro:/etc/armbianmonitor/datasources# cat pmictemp 31700 root@bpro:/etc/armbianmonitor/datasources# cat soctemp cat: soctemp: Das Argument ist ungültig /usr/bin/armbianmonitor: Zeile 352: [: -ge: Einstelliger (unärer) Operator erwartet. °C 32.2°C 4.89V 0/6 18:11:45: 960MHz 0.43 8% 3% 4% 0% 0% 0%/usr/bin/armbianmonitor: Zeile 351: read: Lesefehler: 0: Das Argument ist ungültig Steffen
  7. Hi Igor, I tried to change the value from "console=both" to "console=tty0", but when I try this with armbian-config there is no "console=" entry in /proc/cmdline anymore. How can I remove "console=ttyS0,115200" ? Steffen
  8. Hi, I have a BananaPi and BananaPi Pro connected to the Lemaker 7" TouchLCD. When I boot the system, I can't see any console output. I only see a flashing cursor in the left top corner and then it starts the X-window-manager. What do I have to change to see the boot messags on my LVDS LCD? I have tried to change the console=both value to tty0 or tty1 via armbian-config, but this doesn't work. Any ideas? Here is the output from cat /proc/cmdline: root=UUID=e9635572-227e-485c-b76d-b4f0d6d34394 rootwait rootfstype=ext4 console=tty1 console=ttyS0,115200 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 loglevel=1 ubootpart=3c5d8b7c-01 ubootsource=mmc usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 cgroup_enable=memory swapaccount=1 Steffen
  9. Hi, yesterday I installed kernel 4.17.13 - problem is solved! Steffen
  10. Hi everybody, Here is a tutorial to enable the Lemaker 7" Touchscreen on BananaPi Pro with Debian Stretch and Mainline-Kernel 4.XX.XX. Kernel: Mainline 4.17.13 / Stretch Board: BananaPi Pro WebLinks: • https://forum.armbian.com/topic/1905-enabling-lcd-in-u-boot-kernel-472/ • https://forum.armbian.com/topic/1849-touch-driver-banana-pi/ • http://www.atakansarioglu.com/getting-started-bananapi-linux/ • http://forum.lemaker.org/thread-15482-1-1.html • http://linux-sunxi.org/LCD To make the 7"LCD and the Touchscreen working with BananaPi Pro we need to patch some files and change the kernel config to build the driver for the touchscreen. To do this we need a working setup of the Armbian build tool chain (https://docs.armbian.com/Developer-Guide_Build-Preparation/) /home/<USER>/build/cache/sources/u-boot/v201X.XX/configs/Bananapro_defconfig /home/<USER>/build/cache/sources/u-boot/v201X.XX/arch/arm/dts/sun7i-a20-bananapro.dts /home/<USER>/build/cache/sources/linux-mainline/linux-4.XX.y/arch/arm/boot/dts/sun7i-a20-bananapro.dts 1. U-Boot ( u-boot version that supports the LCD - must be compiled) Start the build process with ./compile.sh CREATE_PATCHES=yes When asked for: [ warn ] Applying existing u-boot patch [ /home/armbian/build/output/patch/u-boot-sunxi-next.patch ] [ warn ] Make your changes in this directory: [ /home/armbian/build/cache/sources/u-boot/v201X.XX ] [ warn ] Press <Enter> after you are done [ waiting ] a) edit /home/<USER>/build/cache/sources/u-boot/v201X.XX/configs/Bananapro_defconfig add the following: #7" LVDS LCD CONFIG_VIDEO_LCD_MODE="x:1024,y:600,depth:24,pclk_khz:55000,le:100,ri:170,up:10,lo:15,hs:50,vs:10,sync:3,vmode:0" CONFIG_VIDEO_LCD_PANEL_LVDS=y CONFIG_VIDEO_LCD_POWER="PH12" CONFIG_VIDEO_LCD_BL_EN="PH8" CONFIG_VIDEO_LCD_BL_PWM="PB2" b) edit /home/<user>/build/cache/sources/u-boot/v201X.XX/arch/arm/dts/sun7i-a20-bananapro.dts LCD: add after: &pio { ... }; the following: &pwm { pinctrl-names = "default"; pinctrl-0 = <&pwm0_pins_a>, <&pwm1_pins_a>; status = "okay"; }; Touchdriver: add after: &i2c2 { pinctrl-names = "default"; pinctrl-0 = <&i2c2_pins_a>; status = "okay"; }; the following: &i2c3 { status = "okay"; pinctrl-names = "default"; pinctrl-0 = <&i2c3_pins_a>; edt: edt-ft5x06@38 { compatible = "edt,edt-ft5x06", "edt,edt-ft5206"; reg = <0x38>; pinctrl-names = "default"; pinctrl-0 = <&edt_ft5x06_pins_a &edt_ft5x06_pins_b>; interrupt-parent = <&pio>; interrupts = <7 9 IRQ_TYPE_EDGE_FALLING>; touchscreen-size-x = <1024>; touchscreen-size-y = <600>; }; }; add after: &pio { gmac_power_pin_bananapro: gmac_power_pin@0 { allwinner,pins = "PH23"; allwinner,function = "gpio_out"; allwinner,drive = <SUN4I_PINCTRL_10_MA>; allwinner,pull = <SUN4I_PINCTRL_NO_PULL>; }; led_pins_bananapro: led_pins@0 { allwinner,pins = "PH24", "PG2"; allwinner,function = "gpio_out"; allwinner,drive = <SUN4I_PINCTRL_10_MA>; allwinner,pull = <SUN4I_PINCTRL_NO_PULL>; }; the following: edt_ft5x06_pins_a: ft5@0 { // interrupt pins = "PH9"; function = "irq"; drive-strength = <20>; bias-pull-up; }; edt_ft5x06_pins_b: ft5@1 { // reset-gpios pins = "PH7"; function = "gpio_out"; drive-strength = <20>; bias-pull-up; output-high; }; Then save and press <Enter> to continue. 2. Kernel patches - DTB (Device Tree Blob) file that fits to your Kernel and supports pwm When asked for: [ warn ] Applying existing kernel patch [ /home/<USER>/build/output/patch/kernel-sunxi-next.patch ] [ warn ] Make your changes in this directory: [ /home/<USER>/build/cache/sources/linux-mainline/linux-4.XX.y ] [ warn ] Press <Enter> after you are done [ waiting ] c) edit /home/<USER>/build/cache/sources/linux-mainline/linux-4.XX.y/arch/arm/boot/dts/sun7i-a20-bananapro.dts add the same lines like section b) Then save and press <Enter> to continue. 3. Compile Touchdriver menuconfig > Device Drivers > Input Device Support > Touchscreens > EDT FocalTech FT5x06 I2C Touchscreen support Exit and save the Kernel configuration. This is the outcome. You probably have a newer version than 5.41. Now we have to install the new DEBs. dpkg -i linux-u-boot-next-bananapipro_5.41_armhf.deb dpkg -i linux-dtb-next-bananapipro_5.41_armhf.deb dpkg -i linux-image-next-bananapipro_5.41_armhf.deb (dpkg -i linux-source-next-bananapipro_5.41_armhf.deb dpkg -i linux-headers-next-bananapipro_5.41_armhf.deb) reboot The result: The LCD and the touchscreen are working. Attention! Kernel version 4.14.XX still had problems with the shutdown. When the patches were made for the LCD, the board did not shut down completely during a shutdown (LCD still had voltage and the red LED on the board did not go out). With the kernel 4.17.XX (4.17.13) the problem is solved. Furthermore, with this kernel version the kworker problem (kworker needs 10% CPU) is solved. 4. Control the Power of the Backlight: The backlight PWM is on PIN CON2 PB2. Following the instructions on http://linux-sunxi.org/GPIO#Accessing_the_GPIO_pins_through_sysfs_with_mainline_kernel http://forum.lemaker.org/thread-10852-1-1.html we have to export GPIO-PIN 34. (position of letter in alphabet - 1) * 32 + pin number position of letter in alphabet: B = 2 pin number: 2 ( 2 - 1 ) * 32 + 2 = 34 echo 34 > /sys/class/gpio/export echo "out" > /sys/class/gpio/gpio34/direction Power on the Backlight: echo "1" > /sys/class/gpio/gpio34/value Power off the Backlight: echo "0" > /sys/class/gpio/gpio34/value Now we could use a switch connected to a GPIO-IN to control the backlight. Steffen
  11. Thanks a lot. Than I will try to build my environment based on Debian Stretch and Mainline-Kernel. Steffen
  12. Hello, I've built a new and clean Image for "Armbian_5.34_Bananapipro_Debian_stretch_default_3.4.113_desktop". The network-manager is not running and can not be started. root@bananapipro:~# /etc/init.d/network-manager start [....] Starting network-manager (via systemctl): network-manager.serviceJob for NetworkManager.service failed because the control process exited with error code. See "systemctl status NetworkManager.service" and "journalctl -xe" for details. failed! root@bananapipro:~# root@bananapipro:~# systemctl status NetworkManager.service ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2017-11-17 12:29:11 CET; 2min 36s ago Docs: man:NetworkManager(8) Process: 1590 ExecStart=/usr/sbin/NetworkManager --no-daemon (code=exited, status=226/NAMESPACE) Main PID: 1590 (code=exited, status=226/NAMESPACE) Nov 17 12:29:11 bananapipro systemd[1]: NetworkManager.service: Unit entered failed state. Nov 17 12:29:11 bananapipro systemd[1]: NetworkManager.service: Failed with result 'exit-code'. Nov 17 12:29:11 bananapipro systemd[1]: NetworkManager.service: Service hold-off time over, scheduling restart. Nov 17 12:29:11 bananapipro systemd[1]: Stopped Network Manager. Nov 17 12:29:11 bananapipro systemd[1]: NetworkManager.service: Start request repeated too quickly. Nov 17 12:29:11 bananapipro systemd[1]: Failed to start Network Manager. Nov 17 12:29:11 bananapipro systemd[1]: NetworkManager.service: Unit entered failed state. Nov 17 12:29:11 bananapipro systemd[1]: NetworkManager.service: Failed with result 'exit-code'. Steffen
  13. Hello guys, I have tried the following HowTo to get my 7 inch LCD working, but I can't find the file "sources/u-boot/v2016.09/configs/Bananapi_defconfig". Can anybody help me please? Thanks. Steffen
  14. Hello everybody, I was running Armbian Wheezy for a very long time. Now I switched to the latest build and I have some problems. My System: BananaPi Pro Lemaker 7" touchscreen with ft5x_ts touch controller Armbian 5.25 Kernel 3.4.113 LXDE Desktop (task-lxde-desktop) Here you can download my image: www.geier-media.de/upload/armbian/armbian_jessie_5.25_3.4.113_4gb_20170319_01.zip And here is the install text file: www.geier-media.de/upload/armbian/armbian_jessie_5.25_3.4.113_4gb_20170319_01.txt Users: root (PW: ".root") / vispro (PW: ".vispro") The BIN-File for the touchscreen is activated! In Debian Whezzy I activated the third button emulation with the following tasks: "touch /etc/X11/xorg.conf" "nano /etc/X11/xorg.conf" Section "InputClass" Identifier "Touchscreen" MatchProduct "ft5x_ts" Driver "evdev" Option "EmulateThirdButton" "1" Option "EmulateThirdButtonTimeout" "750" Option "EmulateThirdButtonMoveThreshold" "30" EndSection Unfortunately it is not working with Debian Jessie. Does anybody has an idea? Thanks. Steffen