Jump to content

Search the Community

Showing results for tags 'bananapi'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Armbian
    • Armbian project administration
  • Community
    • Announcements
    • SBC News
    • Framework and userspace feature requests
    • Off-topic
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Standard support
    • Amlogic meson
    • Allwinner sunxi
    • Rockchip
    • Other families
  • Community maintained / Staging
    • TV boxes
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Support

Categories

  • Official giveaways
  • Community giveaways

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP/Jabber


Skype


Github


Discord


Location


Interests

  1. Hello, I have a 4x20 LCD display (with an HD44780 compatible adaptor) connected to my Banana Pi. It is running (freshly installed, switched from Bananian) on the mainline kernel: Linux bpi 4.9.7-sunxi #1 SMP Thu Feb 2 01:52:06 CET 2017 armv7l GNU/Linux However, the display is not recognized. I checked the wire connections multiple times, they're okay and the backlight is on. So I assume this is a software issue. The output of "i2cdetect -y 1" is: 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- which leads me to the consideration that it is not even recognized by the system. I did the following things - without success: run "apt-get dist-upgrade" (where some 404 errors occured, see this topic for details) installed "i2c-tools" and "python-smbus" loaded "i2c-dev" kernel module According to the documentation https://docs.armbian.com/Hardware_Allwinner/#connect-your-lcd-display, the I2C stuff should work out of the box in the mainline kernel. Any help would be appreciated. Best regards and thanks in advance, Norbert Kahl
  2. Hi everyones, Last week, I tried to read the value from DS18b20 temperature sensor to log it in the monitor system I already have. But I could not get its value. I connect the DS18b20 with 4.7k pull up resistor to the pin 16th on the board, which is I guess is IO-4 [PH20] pin. What I have tried? - I have tried this: http://www.linuxx.eu/2014/09/banana-pi-temperature-sensor-ds18b20.html Step I did: Convert the /boot/script.bin to bananapi.fex, then add [w1_para] gpio = 4 to the end of file, save and convert it back to /boot/script.bin. Reboot. Problem: No w1 dir found in the /sys/bus (expecting it will show w1 dir but it's not). Use modprobe w1-gpio -> ERROR: no such device. - I have found the method with .dtb file, however I could not find any .dtb file in /boot. So I fail on very beginning step. If anyone happen to have this digital sensor work on 3.4.113-sun7i, please help me on this project. I appreciate any suggestions. Thank you so much. This is the Linux version I'm working (can be found at https://dl.armbian.com/bananapi/archive/Armbian_5.25_Bananapi_Debian_jessie_default_3.4.113.7z): cat /proc/version Linux version 3.4.113-sun7i (root@devel) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) ) #17 SMP PREEMPT Thu Feb 23 19:43:34 CET 2017
  3. I'm getting the following errors when running "apt-get upgrade" by banana pi: $ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... The following package was automatically installed and is no longer required: python-dialog Use 'apt-get autoremove' to remove it. Done The following packages will be upgraded: certbot linux-image-next-sunxi python-acme python-certbot 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 15.9 MB/16.1 MB of archives. After this operation, 1,021 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://apt.armbian.com/ jessie/main linux-image-next-sunxi armhf 5.27.170427 [15.9 MB] Fetched 15.9 MB in 14s (1,102 kB/s) (Reading database ... 56352 files and directories currently installed.) Preparing to unpack .../linux-image-next-sunxi_5.27.170427_armhf.deb ... Removing obsolete file 4.9.12-sunxi Removing obsolete file uInitrd-4.9.12-sunxi Unpacking linux-image-next-sunxi (5.27.170427) over (5.26) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-next-sunxi_5.27.170427_armhf.deb (--unpack): unable to create `/lib/modules/4.10.12-sunxi/kernel/drivers/media/rc/keymaps/rc-cinergy-1400.ko.dpkg-new' (while processing `./lib/modules/4.10.12-sunxi/kernel/drivers/media/rc/keymaps/rc-cinergy-1400.ko'): Read-only file system dpkg: error while cleaning up: unable to remove newly-extracted version of `/lib/modules/4.10.12-sunxi/kernel/drivers/media/rc/keymaps/rc-cinergy-1400.ko': Read-only file system This is followed by a few thousand lines of cleanup errors, followed by: dpkg: error while cleaning up: unable to remove newly-extracted version of `/usr/lib/linux-image-next-sunxi/overlay/sun4i-a10-uart7.dtbo': Read-only file system dpkg: error while cleaning up: unable E: Sub-process /usr/bin/dpkg returned an error code (2) E: Failed to write temporary StateFile /var/lib/apt/extended_states.tmp If I reboot it recovers, but if I try to run the upgrade again I get: $ sudo apt-get upgrade E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. $ sudo dpkg --configure -a $ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... The following package was automatically installed and is no longer required: python-dialog Use 'apt-get autoremove' to remove it. Done The following packages will be upgraded: certbot linux-image-next-sunxi python-acme python-certbot 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 0 B/16.1 MB of archives. After this operation, 1,021 kB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 56352 files and directories currently installed.) Preparing to unpack .../linux-image-next-sunxi_5.27.170427_armhf.deb ... Removing obsolete file 4.9.12-sunxi Removing obsolete file uInitrd-4.9.12-sunxi Unpacking linux-image-next-sunxi (5.27.170427) over (5.26) ... dpkg-deb (subprocess): cannot copy archive member from '/var/cache/apt/archives/linux-image-next-sunxi_5.27.170427_armhf.deb' to decompressor pipe: failed to read (Input/output error) dpkg-deb (subprocess): decompressing archive member: lzma error: unexpected end of input dpkg-deb: error: subprocess <decompress> returned error exit status 2 dpkg: error processing archive /var/cache/apt/archives/linux-image-next-sunxi_5.27.170427_armhf.deb (--unpack): cannot copy extracted data for './lib/modules/4.10.12-sunxi/kernel/drivers/net/usb/r8152.ko' to '/lib/modules/4.10.12-sunxi/kernel/drivers/net/usb/r8152.ko.dpkg-new': unexpected end of file or stream run-parts: failed to open directory /etc/kernel/postrm.d: Input/output error dpkg: error while cleaning up: subprocess new post-removal script returned error exit status 1 dpkg: error processing archive /var/cache/apt/archives/certbot_0.10.2-1~bpo8+1_all.deb (--unpack): unable to sync file '/var/lib/dpkg/tmp.ci//postinst': Input/output error dpkg: error processing archive /var/cache/apt/archives/python-certbot_0.10.2-1~bpo8+1_all.deb (--unpack): unable to sync file '/var/lib/dpkg/tmp.ci//postinst': Input/output error dpkg: error processing archive /var/cache/apt/archives/python-acme_0.10.2-1~bpo8+1_all.deb (--unpack): unable to sync file '/var/lib/dpkg/tmp.ci//postinst': Input/output error dpkg: error: unable to sync new file '/var/lib/dpkg/status-new': Input/output error E: Sub-process /usr/bin/dpkg returned an error code (2) How can I fix this? Thanks! Rob
  4. I recently switched from a Raspberry Pi 2 running Arch Linux to a Banana Pi (the original) running Armbian for music streaming using MPD. My output device is an XMOS-based Gustard U12 asynchronous USB transport feeding my DAC via AES/EBU. Using Armbian on the Banana Pi, all my 24-bit/192kHz music is being played back as 24/96, according to the display on the transport and DAC. All other sample rates (44.1, 88.2 etc.) are being played back in their native sample rates, as expected. Is ALSA on Armbian system-wide limited to 96 kHz? I have never had an issue like this before, and I don't know where to begin in regards to troubleshooting. I'm guessing that the audio is being passed through dmix, but I don't understand why it only happens to 24/192 content. The Banana Pi is using kernel 4.9.12, whereas my Raspberry Pi with Arch is using version 4.9.27. I'm using the following in my mpd.conf: audio_output { type "alsa" name "Gustard U12" device "hw:1,0" mixer_type "software" auto_resample "no" auto_channels "no" auto_format "no" use_mmap "yes" } I have also tried use_mmap "no", to no avail. EDIT: According to /proc/asound, it seems like the ALSA device is limited to 96kHz: $ cat /proc/asound/card1/stream0 XMOS xCORE USB Audio 2.0 at usb-1c1c400.usb-1, full speed : USB Audio Playback: Status: Running Interface = 1 Altset = 2 Packet Size = 224 Momentary freq = 44096 Hz (0x2c.1880) Feedback Format = 18.14 Interface 1 Altset 1 Format: S24_3LE Channels: 2 Endpoint: 1 OUT (ASYNC) Rates: 44100, 48000, 88200, 96000 Interface 1 Altset 2 Format: S16_LE Channels: 2 Endpoint: 1 OUT (ASYNC) Rates: 44100, 48000, 88200, 96000 Interface 1 Altset 3 Format: SPECIAL DSD_U32_BE Channels: 2 Endpoint: 1 OUT (ASYNC) Rates: 44100, 48000, 88200, 96000 But how can that be, when it works just fine on a different distro? Could it be the USB port falling back to USB 1.1 speeds for some reason? Can I check that somehow? EDIT²: Okay, my USB 1.x theory turned out to be correct - the cable was the culprit. When switching to the Banana Pi, I also switched to a shorter cable which apparently was an ancient USB 1.x cable. After replugging the old cable, everything is fine and 192kHz works as expected. Now the proc output also says "high speed" instead of "full speed": $ cat /proc/asound/card1/stream0 XMOS xCORE USB Audio 2.0 at usb-1c1c000.usb-1, high speed : USB Audio Playback: Status: Running Interface = 1 Altset = 2 Packet Size = 28 Momentary freq = 44097 Hz (0x5.8318) Feedback Format = 16.16 Interface 1 Altset 1 Format: S32_LE Channels: 2 Endpoint: 1 OUT (ASYNC) Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000 Data packet interval: 125 us Interface 1 Altset 2 Format: S16_LE Channels: 2 Endpoint: 1 OUT (ASYNC) Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000 Data packet interval: 125 us Interface 1 Altset 3 Format: SPECIAL DSD_U32_BE Channels: 2 Endpoint: 1 OUT (ASYNC) Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000 Data packet interval: 125 us
  5. Hello, I want to use the Banana Pi for VDR and need a dvb device - Geniatech T230 for example. Therefore I need i2c_mux enabled. On the 8. May 2017 I created a sd-card-image with your tool (virtualbox, ubuntu and "git clone https://github.com/igorpecovnik/lib --depth 1"), everything works fine. :-) But I forget to enable the remote controller adapter in the kernel... O.k., I started to rerun all the things and created a new sd-card-image. But the network is out of funktion. :-( The system doesn't reach the dhcp-server. The network with a static ip-adress is out of function, too. Anything was changed on the system, wasn't it? The network is out of function even when I don't change anything at the kernel config while building the new image. Please, help me... My second solution was: I took my first generated sd-card-image and installed only the kernel (compiled with your tool under virtualbox...) - i2c_mux enabled - installed with dpkg -i linux-image-sun7i_5.27_armhf.deb && dpkg -i linux-headers-sun7i_5.27_armhf.de on the running system on the banana But when I compile the media-build, it breaks with an error... What have I to do, installing only the kernel in my second solution? And what is the problem with the network with a new sd-card-image? Thanks for your help Stefan P.s.: Sorry for my bad English, I'm still learning... patch -s -f -N -p1 -i ../backports/v4.6_i2c_mux.patch 1 out of 2 hunks FAILED Makefile:137: recipe for target 'apply_patches' failed make[2]: *** [apply_patches] Error 1 make[2]: Leaving directory '/usr/local/src/media_build/linux' Makefile:383: recipe for target 'allyesconfig' failed make[1]: *** [allyesconfig] Error 2 make[1]: Leaving directory '/usr/local/src/media_build/v4l' Makefile:26: recipe for target 'allyesconfig' failed make: *** [allyesconfig] Error 2 can't select all drivers at ./build line 501.
  6. Hi, I installed the main line kernel for Banana Pi and connected a USB/Wifi dongle. The device connects correctly to the wireless network but becomes unreachable after a while. When the issue occures and I try to ping the device, it answers the first ping and then becomes unreachable, via Wifi interface but also via the ethernet interface. I can wait for an hour or so, then I can do a ping (only one) then the device becomes unresponsive. I have to restart the device (power on/off) in order to be able to connect via ssh, but I can work for a few minutes only, then network goes down again. I don't have a screen to connect to the HDMI so difficult to know what's going on inside It looks like a driver issue but I'm not sure... Any idea on how to debug this? Thank you, JM
  7. The following wifi dongle does not work with legacy kernel: Bus 002 Device 002: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter $ uname -a Linux bananapi 3.4.113-sun7i #40 SMP PREEMPT Thu Feb 2 01:44:33 CET 2017 armv7l armv7l armv7l GNU/Linux Freshly flashed Armbian_5.25_Bananapi_Ubuntu_xenial_default_3.4.113_desktop
  8. Gent's currently I run Igor's Debian Image on a BananaPi (kernel 3.4.105). I want to add the wifi driver for Ralink_RT5527. What is to do? Here my thoughts, - install header's - pull sunxi-kernel - copy config from running kernel - make menuconfig - add the driver - make correct ? Regards
  9. After boot a armbian Image: Debian server for banana pi, I done: apt-get update apt-get upgrade During the the upgrade I notice some text regarding Linux headers, and I found it on /usr/src linux-headers-4.9.7-sunxi linux-headers-4.9.12-sunxi But none 4.10.12 as the one is installed. uname -a Linux bananapi 4.10.12-sunxi #7 SMP Wed Apr 26 02:44:12 CEST 2017 armv7l GNU/Linux Googling on how to get this one installed was not usefull. My main issue is compiling dahdi for asterisk. It gives the error: You do not appear to have the sources for the 4.10.12-sunxi kernel installed. Any help. Thank you.
  10. Hello everybody! I'm trying to make a carPC based on Armbian (5.25 Bananapi Ubuntu xenial default 3.4.113 desktop) and a banana pi, almost everything works except for sound in navigation. root@bananapi:~/7ways# ./7ways root@bananapi:~/7ways# ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: Connection refused root@bananapi:~/7ways# ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: Connection refused root@bananapi:~/7ways# ALSA lib pcm_dmix.c:968:(snd_pcm_dmix_open) The dmix plugin supports only playback stream root@bananapi:~/7ways# ALSA lib pcm_dsnoop.c:545:(snd_pcm_dsnoop_open) The dsnoop plugin supports only capture stream root@bananapi:~/7ways# ALSA lib pcm_dsnoop.c:545:(snd_pcm_dsnoop_open) The dsnoop plugin supports only capture stream Maybe someone had such a problem. Please help.
  11. L.S., I made a download of 'Armbian_5.25_Bananapi_Debian_jessie_next_4.9.7.img' Unfortunately the boot process stops at LIRC at the 1st (!) boot: [ OK ] Started LSB: Raise network interfaces.. Starting ifup for eth0... [ OK ] Started ifup for eth0. [ OK ] Reached target Network. [ OK ] Reached target Network is Online. [ OK ] Reached target System Initialization. Starting Armbian filesystem resize service... [ OK ] Started Armbian filesystem resize service. [ OK ] Reached target Basic System. Starting LSB: Starts LIRC daemon.... [ OK ] Started LSB: Starts LIRC daemon.. I can imagine that LIRC is useful, but what's the purpose on a server image? Beside this, how can I disable it? U-Boot SPL 2017.03-armbian (Apr 23 2017 - 15:12:46) DRAM: 1024 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC1 U-Boot 2017.03-armbian (Apr 23 2017 - 15:12:46 +0200) Allwinner Technology CPU: Allwinner A20 (SUN7I) Model: LeMaker Banana Pi I2C: ready DRAM: 1 GiB MMC: SUNXI SD/MMC: 0 I found the same issue while compiling the latest sources from scratch ... Your help is appreciated. Many thanks. /September
  12. Hello everyone! I have Banana Pi and installed Ubuntu desktop Xenial 4.9.12. I have a USB wifi stick and Ubuntu recognizes , and USB works well. The problem is when I try to set my Banana Pi as an access point, then we Ubuntu reported to have root privileges. How to get root privileges in Ubuntu Xfce graphical environment? How to stop autologin before lifting graphic Xfce desktop, and to ask for the root password? Please help, and thank you in advance
  13. Hi, I read the docs but could not find out what to download to get a headless server. Getting Started says: "mainline: headless server, light desktop operations" In mainline there are 2 downloads for server (Debian, Ubuntu) and one for desktop (Ubuntu). I do not need a desktop, thus I do not want to waste space, RAM and CPU on anything related to it. May I ask, what to download or if there is no headless version what to do to remove the desktop-features alltogether? Thank you very much. Stephan
  14. Hi, I have a question regarding the new Banana Pi (A20) boot script created in Armbian 5.25. Many months ago I switched my roots from the SDCard to the sata disk using the sata-nand-install script, after that I used to switch between SD and HDD and vice versa, mostly for maintenance operations on the HDD (sometime the system gets corrupted and I have to restore the HDD partition with e2fsck from the SD). Until Armbian 5.20 I used to edit the boot.cmd file pointing to the desired root device, recompile the boot.scr and then the system were loaded from the desired partition. Now with Armbian 5.25 I'm not sure which file I have to edit to do the same, boot.cmd or ArmbianEnv.txt? I've tried both but the boot didn't seem to be right and I don't understand if it's because my HDD is dead or because I badly edited the new boot script. Could someone help me please? Thanks!
  15. Hey there, I am a long time user of your armbian operating system. It is great, I am using it for a simple home NAS system. But I have found one problem with armbian, which is very annoying: My standard Banana Pi keeps loosing the HDD Ive connected over Sata. It is a 3,5" Seagate Barracude 3TB drive formated as Ext4. It gets 5V and 12V power and runs quite perfect, as long as it has something to do. It spins up and down as I configured it. But when I leave the pi for a longer time period unattended (no workload), and the harddrive stays in spindown-mode too long, it wont identify the HDD anymore. The mount point and the /dev/sda are gone. I need to powercycle the whole system to get everything back up. Things I tried: fresh armbian, with fresh formated drive -> same problem fresh armbian, with another drive (WD green) -> same problem I noticed this problem quite a while a go, but never got to posting it. Hope somebody has an answer. Thanks in advance
  16. I had successfully installed openCV for armbian using instructions from this page: http://www.pyimagesearch.com/2015/10/26/how-to-install-opencv-3-on-raspbian-jessie/ I also highly recommend Adrians's openCV tutorials. happy openCV-ing Mladen
  17. Hi, No real problem, just a question. I'm using latest Armbian Jessie 5.25 with my good old Banana Pi. root@marvin:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies 144000 312000 528000 720000 864000 912000 960000 root@marvin:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 480000 root@marvin:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq 960000 Please notice that 480MHz (the min freq) is not in the available frequencies. So that gives the following output with cpufreq-info : root@marvin:~# cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 CPUs which need to have their frequency coordinated by software: 0 1 maximum transition latency: 244 us. hardware limits: 144 MHz - 960 MHz available frequency steps: 144 MHz, 312 MHz, 528 MHz, 720 MHz, 864 MHz, 912 MHz, 960 MHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 480 MHz and 960 MHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 528 MHz (asserted by call to hardware). cpufreq stats: 144 MHz:0,00%, 312 MHz:0,00%, 528 MHz:98,22%, 720 MHz:1,04%, 864 MHz:0,08%, 912 MHz:0,23%, 960 MHz:0,43% (39367) analyzing CPU 1: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 CPUs which need to have their frequency coordinated by software: 0 1 maximum transition latency: 244 us. hardware limits: 144 MHz - 960 MHz available frequency steps: 144 MHz, 312 MHz, 528 MHz, 720 MHz, 864 MHz, 912 MHz, 960 MHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 480 MHz and 960 MHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 528 MHz (asserted by call to hardware). cpufreq stats: 144 MHz:0,00%, 312 MHz:0,00%, 528 MHz:98,22%, 720 MHz:1,04%, 864 MHz:0,08%, 912 MHz:0,23%, 960 MHz:0,43% (39367) Should I set /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq to 528000 or is there a problem with 480MHz not being in available frequencies ? IIRC I had the same problem with the previous kernel (Armbian 5.24), I do not remember if it happened before.
  18. HI, i get the failure "***warning - bad CRC, using default environment" and the system don't boot. I tested it with an banana pi, cubieboard2 and olimex A20 Olinux Lime2 and all the same failure. Of course with the specific image. I flashed the image with ubuntu 14.04 lts (no virtual maschine) with dd bs=1M if=filename.raw of=/dev/sdb. I using the direkt letter of the drive sdb and not the specific partition sdb1. The windows flash tool dont works, i get an error when click on "copy", whats that, missing framework? What i make wrong?
  19. hi, since 2 days i am using on my Banana Pi the Debian Jessie with 4.8.15 Kernel with installed Openmediavault 3. The system is working stable, but the network-performance is less then my older Installation based on Debian Wheezy with Openmediavault 2. I tried change the MTU-Size to 9000 and overcklocking up to 1.2 GHz, booth is not possible. I don´t know why ? For the setting the MTU-Size i edited /etc/network/interfaces and added the value "mtu 9000" -> no effects I tried set the MTU over the OMV WebGUI under network settings -> no effects. ifconfig shows me MTU=1500 Booth ways was at Debian Wheezy possible. At Debian Wheezy i had overclock the CPU up to 1.2 Ghz. The system was stable 1 year. For this i edited the files from cpufrequtils (/sys/device/system...........) At the new system i can edit the values, but after them the values will be reset to standard values. I found many many manuals in the internet, but is´nt working. Can you help me? Step by step.......... ;-) I´m sorry for my englisch, i´m from poland, in the school i had to learn russian ................. :-((((
  20. wget https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.6.6.tar.xz tar -xpJf linux-4.6.6.tar.xz ln -s linux-4.6.6 linux make oldconfig make menuconfig make-kpkg clean CONCURENCY_LEVEL=3 fakeroot make-kpkg --initrd --revision=14082016.01 kernel_image kernel_headers But USB do not work! I do not found CONFIG_AXP20X_POWER in new config. After manual add its gone! How to solve this ?????
  21. Hi guys, I tried to disable console output on uart0 using this guide https://docs.armbian.com/User-Guide_Fine-Tuning/#how-to-toggle-boot-output But I still get boot output on uart0. Problem is, that I'm using uart0 for a java application. Java application crashes a few seconds after starting. I got the hint, that I should disable console output on this port, to make it working. See here: http://pi4j.com/example/serial.html I think that's the problem, because if I unplug my serial device from uart0, java app doesn't crash. I'm using Banana Pi. Kernel is Verison 4.8.12. Armbian is Jessie 5.24 with desktop. How can I disable the output? Yours, Martin
  22. Help please! I have a bp2 which was bought almost a year ago, and use Armbian_5.14_Bananapi_Debian_jessie_3.4.112.raw as the image for couple of months. Today, I'm try to upgrade to the Armbian_5.14_Bananapi_Ubuntu_xenial_4.6.2.raw image, but the pi can't boot at all. What I do to prepare the sdcard with the following procedure: 1. remote the old partitation, and create a new fat32 partitation 2. dd bs=1M if=Armbian_5.14_Bananapi_Ubuntu_xenial_4.6.2.raw of=/dev/sdc; and sync 3. mark the written partitation as bootable with fdisk ps: I'm using fish shell, and the syntax for the dd command is valid So, what's wrong with my steps? How can I troubleshoot? Thanks in advance.
  23. I know the A20 isn't really build for OC, but I would still like to do some tests with it running at 1008Mhz. As far as I understand Kernel 4.X doesn't use the fex files anymore, but rely on the dts (dtsi) files. I edited sun7i-a20-bananapi.dts &cpu0 { cpu-supply = <&reg_dcdc2>; operating-points = < /* kHz uV */ 1008000 1425000 960000 1400000 912000 1400000 864000 1350000 720000 1250000 528000 1150000 312000 1100000 144000 1050000 >; }; I made sure the build script doesn't overwrite the edited dts file. But BananaPi still says the max freq is 960 instead of 1008. root@bananapi:/tmp# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq 960000 I even double checked boot/dtb-4.8.12-sunxi/sun7i-a20-bananapi.dtb with device tree compiler to see if the values I set are there. The hexadecimal matches, so I don't understand why I can't get it working. cpu@0 { compatible = "arm,cortex-a7"; device_type = "cpu"; reg = <0x0>; clocks = <0x7>; clock-latency = <0x3b9b0>; operating-points = <0xf6180 0x15be68 0xea600 0x155cc0 0xdea80 0x155cc0 0xd2f00 0x149970 0xafc80 0x1312d0 0x80e80 0x118c30 0x4c2c0 0x10c8e0 0x23280 0x100590>; #cooling-cells = <0x2>; cooling-min-level = <0x0>; cooling-max-level = <0x6>; cpu-supply = <0x8>; linux,phandle = <0xb>; phandle = <0xb>; }; What am I missing?
  24. Hi specialists, I'm trying to understand how the axp209 on Banana Pi works with the A20. In the Banana Pi schematics I see, that they are connected with only four lines. Two lines are used for I²C (TWSI), one is from axp209 PWROK to RESET# of A20 and another one is connected from axp209 IRQ and GPIO2 to NMI# of A20. When system is off and I press my Power Button (K1) on the Pi, the system is booting. System is running and I long press the Power Button, System shuts down. But can anyone say whats happening? What does axp209 do with IRQ, GPIO2 and PWROK pins? Wich way does the A20 recognize, that it has to shutdown? Yours Martin
  25. Hello there. I am using ubuntu Xenial server on Banana pi. It has mysql, nginx, websites, and many programs and settings. I use it as a banana pi router. I used to use it as a server until now but now I got an hdmi to vga converter. Now I want to use Xfce. I installed xubuntu-desktop from the terminal. But the Xserver does not start because the GPU is not active. How do I activate the GPU without reinstalling? xorg err [ 14896.672] X.Org X Server 1.18.4 Release Date: 2016-07-19 [ 14896.673] X Protocol Version 11, Revision 0 [ 14896.673] Build Operating System: Linux 4.2.0-42-generic armv7l Ubuntu [ 14896.673] Current Operating System: Linux server2 4.8.4-sunxi #6 SMP Sun Oct 23 15:55:47 CEST 2016 armv7l [ 14896.674] Kernel command line: console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p1 rootwait rootfstype=ext4 cgroup_enable=memory swapaccount=1 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 enforcing=0 loglevel=7 [ 14896.675] Build Date: 14 September 2016 03:34:19PM [ 14896.675] xorg-server 2:1.18.4-0ubuntu0.1 (For technical support please see http://www.ubuntu.com/support) [ 14896.675] Current version of pixman: 0.33.6 [ 14896.675] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 14896.676] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 14896.677] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Nov 21 14:25:02 2016 [ 14896.679] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 14896.679] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 14896.682] (==) No Layout section. Using the first Screen section. [ 14896.682] (==) No screen section available. Using defaults. [ 14896.682] (**) |-->Screen "Default Screen Section" (0) [ 14896.682] (**) | |-->Monitor "<default monitor>" [ 14896.684] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 14896.684] (**) Option "BlankTime" "0" [ 14896.684] (**) Option "StandbyTime" "0" [ 14896.684] (**) Option "SuspendTime" "0" [ 14896.684] (**) Option "OffTime" "0" [ 14896.685] (==) Automatically adding devices [ 14896.685] (==) Automatically enabling devices [ 14896.685] (==) Automatically adding GPU devices [ 14896.685] (==) Max clients allowed: 256, resource mask: 0x1fffff [ 14896.685] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 14896.685] Entry deleted from font path. [ 14896.685] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. [ 14896.685] Entry deleted from font path. [ 14896.686] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. [ 14896.686] Entry deleted from font path. [ 14896.686] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist. [ 14896.686] Entry deleted from font path. [ 14896.686] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. [ 14896.686] Entry deleted from font path. [ 14896.686] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. [ 14896.686] Entry deleted from font path. [ 14896.686] (==) FontPath set to: /usr/share/fonts/X11/misc, built-ins [ 14896.686] (==) ModulePath set to "/usr/lib/arm-linux-gnueabihf/xorg/extra-modules,/usr/lib/xorg/extra-modules,/usr/lib/xorg/modules" [ 14896.686] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 14896.686] (II) Loader magic: 0x7f744f70 [ 14896.687] (II) Module ABI versions: [ 14896.687] X.Org ANSI C Emulation: 0.4 [ 14896.687] X.Org Video Driver: 20.0 [ 14896.687] X.Org XInput driver : 22.1 [ 14896.687] X.Org Server Extension : 9.0 [ 14896.704] (--) using VT number 2 [ 14896.704] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [ 14896.706] (II) no primary bus or device found [ 14896.706] (II) LoadModule: "glx" [ 14896.708] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 14896.718] (II) Module glx: vendor="X.Org Foundation" [ 14896.718] compiled for 1.18.4, module version = 1.0.0 [ 14896.719] ABI class: X.Org Server Extension, version 9.0 [ 14896.719] (==) AIGLX enabled [ 14896.719] (==) Matched modesetting as autoconfigured driver 0 [ 14896.720] (==) Matched fbdev as autoconfigured driver 1 [ 14896.720] (==) Assigned the driver to the xf86ConfigLayout [ 14896.720] (II) LoadModule: "modesetting" [ 14896.721] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so [ 14896.723] (II) Module modesetting: vendor="X.Org Foundation" [ 14896.723] compiled for 1.18.4, module version = 1.18.4 [ 14896.723] Module class: X.Org Video Driver [ 14896.723] ABI class: X.Org Video Driver, version 20.0 [ 14896.723] (II) LoadModule: "fbdev" [ 14896.725] (WW) Warning, couldn't open module fbdev [ 14896.725] (II) UnloadModule: "fbdev" [ 14896.725] (II) Unloading fbdev [ 14896.725] (EE) Failed to load module "fbdev" (module does not exist, 0) [ 14896.726] (==) Matched modesetting as autoconfigured driver 0 [ 14896.726] (==) Matched fbdev as autoconfigured driver 1 [ 14896.726] (==) Assigned the driver to the xf86ConfigLayout [ 14896.726] (II) LoadModule: "modesetting" [ 14896.727] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so [ 14896.727] (II) Module modesetting: vendor="X.Org Foundation" [ 14896.727] compiled for 1.18.4, module version = 1.18.4 [ 14896.727] Module class: X.Org Video Driver [ 14896.727] ABI class: X.Org Video Driver, version 20.0 [ 14896.727] (II) UnloadModule: "modesetting" [ 14896.727] (II) Unloading modesetting [ 14896.727] (II) Failed to load module "modesetting" (already loaded, 2138489976) [ 14896.728] (II) LoadModule: "fbdev" [ 14896.729] (WW) Warning, couldn't open module fbdev [ 14896.729] (II) UnloadModule: "fbdev" [ 14896.729] (II) Unloading fbdev [ 14896.729] (EE) Failed to load module "fbdev" (module does not exist, 0) [ 14896.729] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 14896.759] (WW) Falling back to old probe method for modesetting [ 14896.760] (EE) open /dev/dri/card0: No such file or directory [ 14896.760] (EE) No devices detected. [ 14896.760] (EE) Fatal server error: [ 14896.764] (EE) no screens found(EE) [ 14896.766] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 14896.766] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 14896.767] (EE) [ 14896.831] (EE) Server terminated with error (1). Closing log file.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines