Jump to content

mmdienel

Members
  • Posts

    5
  • Joined

  • Last visited

  1. Hi Igor, tried your image, but no success. U-boot does not start. Only red LED on M2, no HDMI signal, no activity of green LED as with my selfmade image. Looks like your patch does not work. :-(
  2. Hi all, after building several images for BananaPi and R1 with Igors lib and getting some insight to the great stuff he has done I have extended my "configuration.sh" with the following: BPI-M2)#enabled #description A31 quad core 1Gb SoC Wifi #build 0 #-------------------------------------------------------------------------------------------------------------------------------- # Bananapi M2 #-------------------------------------------------------------------------------------------------------------------------------- REVISION="1.0" BOOTLOADER="https://github.com/BPI-SINOVOIP/BPI-Mainline-uboot" BOOTCONFIG="Bananapi_M2_defconfig" BOOTSOURCE="u-boot-bpi-m2" BOOTDEFAULT="master" UBOOTTAG="" MODULES="hci_uart gpio_sunxi rfcomm hidp sunxi-ir bonding spi_sun7i 8021q a20_tp" MODULES_NEXT="brcmfmac" LINUXFAMILY="banana" ;; No other changes were made. I successfully build images for trusty and jessie with mainline kernel (4.2.2). Armbian is booting without issues as far as I can see. I have tested ethernet and HDMI, both working, WLAN can be enabled and is up (only verified with "ifconfig", not connected to AP yet). "htop" shows all 4 cores. https://github.com/BPI-SINOVOIP/BPI-WiringPi can be build without issues and "gpio readall" shows all 40 pins. Further tests are ongoing as time permits. Comments are welcome.
  3. Found the solution or the cause of the different behaviour, deppends on how you look at it: Difference between ambian and x86 Debian or Ubuntu is the following: There is a file /etc/bash.bashrc.custom: if [ ${TERM} == "dumb" ]; then return fi export TERM=linux OUT="" ... This is never reverted and breaks the at least to me well known behaviour of mc. To fix this I added export TERM=xterm at the end of /etc/bash.bashrc.custom.
  4. echo $TERM gives "linux". With "TERM=xterm mc" the F-keys behave correct. How to set this persistant?
  5. Hallo, first I want to thank Igor for the creation of armbian, great stuff! Many thanks. Now to my issue: While setting up a Lamobo R1 with armbian i was not able to get F-keys F1 to F4 working in Midnight Commander (apt-get install mc). With all three flavours (whezzy, jessie and trusty) it is the same. I tried dpkg-reconfigure keyboard-configuration dpkg-reconfigure locales to get it working with my german (qwertz) keyboard. The behaviour is the same for local and remote (ssh). Tried also to bulid new image based on https://github.com/igorpecovnik/lib with # user DEST_LANG="de_DE.UTF-8" # sl_SI.UTF-8, en_US.UTF-8 CONSOLE_CHAR="UTF-8" # console charset TZDATA="Europe/Berlin" # time zone without any succsess. During setup of x86-machines as well as the Beaglebone Black with Debian or Ubuntu I never had this issue. Any hints? Michael
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines