Jump to content

Search the Community

Showing results for tags 'bananapim1plus'.

  • 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

Product Groups

  • Misc
  • Support

Categories

  • Armbian
  • Armbian releases

Categories

  • Volunteering opportunities

Calendars

  • Community Calendar

Categories

  • Members

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

Found 22 results

  1. Glad to say creating virtual machine and getting Armbian build environment and running ./compile.sh was easy and successful for bananapim1plus / 6.1 kernel / jammy. Created SD card and booted and is running fine. Added DT overlay to enable spidev and got /dev/spidev0.0 as expected. Got new version of cross compiler to build code I formerly ran on fedora image and the SPI driver behaves differently. It pulses CS low for every transfer instead of optionally staying low for multiple transfers based on "cs_change" field in each transfer message. Found kernel source in build/cache/sources/linux-kernel-worktree/6.1__sunxi__armhf/drivers/spi, and tried editing there to begin debugging (even tried git commit there), and each time I re-run ./compile.sh, my changes are blown-away. Looking to understand what the standard workflow is for this? Do I have to use user patches? Do I have to build the kernel somewhere else and inject it into the img somewhere? Any suggestions welcome. THANK YOU.
  2. hello after updating from cat /proc/version Linux version 4.14.84-sunxi (root@armbian.com) (gcc version 7.2.1 20171011 (Linaro GCC 7.2-2017.11)) #3 SMP Sat Dec 1 07:18:41 CET 2018 to Linux version 4.19.13-sunxi (root@armbian.com) (gcc version 7.2.1 20171011 (Linaro GCC 7.2-2017.11)) #5.70 SMP Sat Jan 12 15:43:21 CET 2019 my one wire thermometer stopped working - is there some additional steps needed now? I didn't change my configuration overlays=w1-gpio param_w1_pin=PB10 param_w1_pin_int_pullup=0  and now I have dmesg [ 1174.451457] w1_master_driver w1_bus_master1: Attaching one wire slave 00.e80000000000 crc 2b [ 1174.456242] w1_master_driver w1_bus_master1: Family 0 for 00.e80000000000.2b is not registered. [ 1234.023523] w1_master_driver w1_bus_master1: Attaching one wire slave 00.180000000000 crc 5f [ 1234.029428] w1_master_driver w1_bus_master1: Family 0 for 00.180000000000.5f is not registered. ... ls /sys/bus/w1/devices 00-180000000000 00-580000000000 00-980000000000 w1_bus_master1 (00-... directories names and count changes after every minute) cat /sys/kernel/debug/gpio gpiochip0: GPIOs 0-287, parent: platform/1c20800.pinctrl, 1c20800.pinctrl: gpio-40 ( |ahci-5v ) out hi gpio-224 ( |cd ) in lo IRQ gpio-225 ( |cd ) in lo IRQ gpio-227 ( |usb2-vbus ) out hi gpio-228 ( |usb0_id_det ) in hi IRQ gpio-230 ( |usb1-vbus ) out hi gpio-244 ( |cubieboard2:green:us) out lo gpio-245 ( |cubieboard2:blue:usr) out lo gpio-271 ( |onewire@0 ) in lo gpiochip1: GPIOs 413-415, parent: platform/axp20x-gpio, axp20x-gpio, can sleep: there is no "gpio-42" line, old was cat /sys/kernel/debug/gpio gpiochip0: GPIOs 0-287, parent: platform/1c20800.pinctrl, 1c20800.pinctrl: gpio-40 ( |ahci-5v ) out hi gpio-42 ( |w1 ) in hi gpio-224 ( |cd ) in lo IRQ gpio-225 ( |cd ) in lo IRQ gpio-227 ( |usb2-vbus ) out hi gpio-228 ( |usb0_id_det ) in hi IRQ gpio-230 ( |usb1-vbus ) out hi gpio-244 ( |cubieboard2:green:us) out lo gpio-245 ( |cubieboard2:blue:usr) out lo gpiochip1: GPIOs 413-415, parent: platform/axp20x-gpio, axp20x-gpio, can sleep:
  3. I am using GPIO(CON3) pins 8 and 10 for a project. In BPI M1+, functions for those pins are PH0 and PH1 respectively. https://bananapi.gitbooks.io/bpi-m1-bpi-m1-plus-/content/en/bpi-m1+_gpio_pin_define.html But, when I added overlays=uart3 ,I didn't work properly . When I checked the overlay file sun7i-a20-uart3.dtbo , by changing it to .dts , I figured out that this overlay file uses PG6,PG7 pins, not PH0,PH1 pins. So, to modify the configurations without adding uart3 overlay in the /boot/armbianEnv.txt file, I wanted to edit the /boot/dtb/sun7i-a20-bananapi-m1-plus.dtb file. When I check the file, there are uart3_pins_a option and uart3_pins _b in the __symbols section with the path name as below. Also pins assigned for each pins_a and pins_b are mentiond in the pinctrl@01c20800. How can I activate(set) the uart3_pins_b option which is assigned to the correct pins (PH1 and PH0)for BPI M1+ ?
  4. · Hello, So I tried to figure out the original dtb file used but the system by default when I boot the image without any fine configuration. But I couldn't find any information about the default dtb. I checked at /boot/boot.cmd , but nothing is mentioned for "setenv fdtfile" which was available in the old kernel. I figured out that I can add a suitable .dtb in the /boot/armbianEnv.txt in the following post. https://forum.armbian.com/index.php?/topic/4817-banana-pi-m1-extra-configuration/ fdtfile=sun7i-a20-bananapi-m1-plus.dtb But there is no way to know which .dtb file is used when this information is not set. Can somebody let me know how to figure out the currently used .dtb file in the system? And to change the .dtb file, is adding it to the armbianEnv.txt as mentioned above right?
  5. Hi all I'm trying to set up a samba AD domain on a BananaPi M1+ running Armbian 5.31 (Debian Jessie) but fail miserably when trying to provision the domain. Using "samba-tool domain provision --use-rfc2307 --interactive", all starts well but then falls over with the error: Error loading module '/usr/lib/arm-linux-gnueabihf/samba/vfs/acl_xattr.so': /usr/lib/arm-linux-gnueabihf/samba/vfs/acl_xattr.so: cannot open shared object file: No such file or directory error probing vfs module 'acl_xattr': NT_STATUS_UNSUCCESSFUL and a whole lot more. Bottom line is that this "acl_xattr.so" doesn't exist anywhere on the machine. It is supposed to install with Samba but apparently doesn't. The reported Samba version is 4.2.14-Debian Any ideas what I can do to get this going? Cheers
  6. I installed Armbian 4.5 Debian Jessie 3.4.109 and added XFCE desktop, but there is no audio on 3.5 jack (I cannot test HDMI audio output). I built my own Debian Jessie 3.4.109 selecting Banana Pro and including XFCE desktop without any other change, and also in this case there is no audio on 3.5 jack. Some useful information to solve the problem. These are equals on both installation. root@bananapipro:~# cat /proc/asound/cards 0 [sunxicodec ]: sunxi-CODEC - sunxi-CODEC sunxi-CODEC Audio Codec root@bananapipro:~# cat /proc/asound/devices 2: [ 0- 0]: digital audio playback 3: [ 0- 0]: digital audio capture 4: [ 0] : control 33: : timer root@bananapipro:~# cat /proc/asound/pcm 00-00: M1 PCM : sunxi PCM : playback 1 : capture 1 root@bananapipro:~# cat /proc/asound/timers G0: system timer : 10000.000us (10000000 ticks) G3: HR timer : 0.001us (1000000000 ticks) P0-0-0: PCM playback 0-0-0 : SLAVE P0-0-1: PCM capture 0-0-1 : SLAVE root@bananapipro:~# cat /proc/asound/version Advanced Linux Sound Architecture Driver Version 1.0.25. root@bananapipro:~# lsmod Module Size Used by cpufreq_userspace 3524 0 spidev 6366 0 a20_tp 3365 0 8021q 18593 0 garp 6072 1 8021q stp 2032 1 garp llc 5365 2 stp,garp sunxi_ir 4037 0 hidp 17640 0 rfcomm 58686 0 hci_uart 25000 0 bluetooth 264185 5 hidp,hci_uart,rfcomm root@bananapipro:~# less /etc/asound.conf /etc/asound.conf: No such file or directory root@bananapipro:~# find / -iname *sunxi-snd* /sys/bus/platform/drivers/sunxi-sndhdmi This is related to my own image. root@bananapipro:~# dmesg | grep audio [ 0.000000] Kernel command line: console=tty1 root=/dev/mmcblk0p1 rootwait rootfstype=ext4 hdmi.audio=EDID:0 disp.screen0_output_mode=1280x1024p60 panic=10 consoleblank=0 enforcing=0 loglevel=1 This is related to Debian Armbian 4.5. root@bananapi:~# dmesg | grep audio [ 0.000000] Kernel command line: console=tty1 root=/dev/mmcblk0p1 rootwait rootfstype=ext4 sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_no_mali_mem_reserve sunxi_fb_mem_reserve=16 hdmi.audio=EDID:0 disp.screen0_output_mode=1280x1024p60 panic=10 consoleblank=0 enforcing=0 loglevel=1 Thanks for support.
  7. Hello, what is the difference between /sys/devices/platform/sunxi-i2c.0/i2c-0/0-0034/temp1_input this return 37800 and /sys/devices/platform/a20-tp-hwmon/temp1_input this return 46500 what value is correct? there are writing http://bananapi.com/index.php/forum/beginners/141-how-to-read-cpu-temperature You can find the CPU temperature data at "/sys/devices/platform/sunxi-i2c.0/i2c-0/0-0034/temp1_input" but bash.bashrc.custum use value from /sys/devices/platform/a20-tp-hwmon/temp1_input thanks hw: Banana Pi BPi-M1+
  8. Hi all. I have a Banana Pi M1+ and I want to use it as a NAS using a SATA HDD (1TB). I read this article http://linux-sunxi.org/Cpufreq#Performance.2Ffunctionality_impacts and I want to change the scaling_max_freq. I installed the "Armbian_5.20_Bananapi_Debian_jessie_4.7.3" image. But the maximum frequencies available is 960000. I tried to compile the kernel by myself, changing the file sources\linux-vanilla\v4.9.5\arch\arm\boot\dts\sun7i-a20.dtsi as suggested in other posts. cpu0: cpu@0 { compatible = "arm,cortex-a7"; device_type = "cpu"; reg = <0>; clocks = <&cpu>; clock-latency = <244144>; /* 8 32k periods */ operating-points = < /* kHz uV */ 1200000 1500000 1152000 1500000 1104000 1450000 1056000 1450000 1008000 1450000 960000 1400000 912000 1400000 864000 1300000 720000 1200000 528000 1100000 312000 1000000 144000 1000000 >; I changed also this row in compile.sh file FORCE_CHECKOUT="no" # ignore manual changes to source I verified that the file sources\linux-vanilla\v4.9.5\arch\arm\boot\dts\sun7i-a20.dtsi wasn't changed at the end of the compilation process. This is output of the compialtion: linux-headers-next-sunxi_5.24_armhf.deb linux-image-next-sunxi_5.24_armhf.deb linux-firmware-image-next-sunxi_5.24_armhf.deb linux-u-boot-next-bananapipro_5.24_armhf.deb linux-dtb-next-sunxi_5.24_armhf.deb I copied them on the Banana Pi and installed them with dpkg -i *.deb After rebooting, this is the output of the command "uname -a" Linux bananapi 4.9.5-sunxi #4 SMP Tue Jan 24 11:33:41 CET 2017 armv7l GNU/Linux and this is my "/etc/default/cpufrequtils" ENABLE=true MIN_SPEED=480000 MAX_SPEED=1200000 GOVERNOR=ondemand but the output of the command "cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies" is still the same 144000 312000 528000 720000 864000 912000 960000 What is wrong? Can someone help me? Thanks in advance. P.S. During kernel compilation I changed the default configuration to choose the "ondemand" governor as default governor rather than "schedutil". This change was successfully applied after reboot.
  9. Hi, I am totally new to Linux, but already managed to run OMV on my Banana Pi M1+ with Plex and other services I wanted on Armbian. Now I tried to run Kodi, so it could serve me both as NAS and HTPC. Firstly, I have installed xorg, then lightdm and set it up for autologin, which is working correctly. Then, I have installed Kodi 16 from git, but only gray box appears and then vanishes and screen stays black. My first impression was it is lacking GL drivers, so I have followed this tutorial: https://forum.armbian.com/index. ... pi-orangepi-pc-etc/, tested and everything seemed to be ok. I installed Emilia Pinball to check additionally - it renders correctly. Still, when I try to run Kodi it is gray screen, then black. I have opened Kodi log and I have found that, indeed, it does not see driver/device? 21:38:26 T:2967420928 ERROR: Failed to determine egl config for visual info 21:38:26 T:2967420928 ERROR: Previous line repeats 60 times. 21:38:26 T:2967420928 ERROR: EGL/GLX Error: vInfo is NULL! 21:38:26 T:2967420928 NOTICE: GL_VENDOR = NULL 21:38:26 T:2967420928 NOTICE: GL_RENDERER = NULL 21:38:26 T:2967420928 NOTICE: GL_VERSION = NULL 21:38:26 T:2967420928 NOTICE: GL_SHADING_LANGUAGE_VERSION = NULL 21:38:26 T:2967420928 NOTICE: GL_EXTENSIONS = NULL 21:38:26 T:2967420928 ERROR: GL: Error compiling vertex shader After this message, it is constantly repeating those, untill I close SSH connection. 21:38:30 T:2967420928 ERROR: Invalid GUI Shader selected - [guishader_frag_texture.glsl] 21:38:30 T:2967420928 ERROR: Invalid GUI Shader selected - [guishader_frag_fonts.glsl] 21:38:30 T:2967420928 ERROR: Previous line repeats 1 times. 21:38:30 T:2967420928 ERROR: Invalid GUI Shader selected - [guishader_frag_texture.glsl] 21:38:30 T:2967420928 ERROR: Invalid GUI Shader selected - [guishader_frag_fonts.glsl] 21:38:30 T:2967420928 ERROR: Previous line repeats 1 times. 21:38:30 T:2967420928 ERROR: Invalid GUI Shader selected - [guishader_frag_texture.glsl] 21:38:30 T:2967420928 ERROR: Invalid GUI Shader selected - [guishader_frag_fonts.glsl] The full log is available here: http://pasted.co/dc406eb6 I have installed drivers using normal user with sudo and I run Kodi as root using: xinit kodi What might be the issue here?
  10. I have a BananaPi M1+ running pure-ftpd, it was fine when using Armbian 5.14, but I have a problem after upgraded to Armbian 5.20. Here is the output of the filezilla client : If I disable the firewall by clearing all the iptables rules, filezilla can connect to pure-ftpd without problem.
  11. Hi all, traditionally I have used Bananian on the Bannan Pi M1+, but I thought that I would give Armbian a go as there seems to be more activity here and there are tools for compiling an entire image from scratch :-) So far I love Ambian, thank you for the work. I have tried the vanilla Jessie image (both downloaded from here and compiled myself) on the Banana Pi M1+ and with the exception of the WiFi issuet which I solved from this forum, all ran well. However I can't seem to find an SPI driver. My apologies if there is another forum post about this, I did try searching but the search function removed SPI from the query due to it being less than 4 chars :-( When I built my own image using the tools from this site, I did check the kernel configuration which was set to build in SPI support, but still no entry in /dev or a module to load. Any help would be appreciated. Thanks, Nick
  12. I'm currently playing with a Banana Pi M1 + and don't seem to be able to get the GPIO to work. I *think* that I have correctly mapped the IO pins that I am using through the schematic and fex file to find the corrisponding GPIO number for debian. When playing around in /sys/class/gpio I am able to export the GPIO pin that I'm looking for and change it's properties, direction, value etc. However these changes don't seem to appear on the physical IO pins. I noticed that some of the pins that I'm using are shared by UART 2, so I have disabled that in the FEX file but still no luck. I have a feeling that this is probably going to be DTB related, however I'm a little confused by the fact that Debian allows me to export them.
  13. On legacy kernel, Armbian_5.10_Bananapipro_Debian_jessie_3.4.112.7z, if I use /boot/script.bin with https://github.com/LeMaker/fex_configuration/raw/master/bin/banana_pi_35lcd.bin, my lcd works properly. But on Vanilla kernel, Armbian_5.10_Bananapipro_Debian_jessie_4.5.2.7z, if I change /boot/script.bin with https://github.com/LeMaker/fex_configuration/raw/master/bin/banana_pi_35lcd.bin, my lcd doesn't work. What should I check more?
  14. I've tried the current armbian release legacy & vanilla with my bpi m1+ board. and it looks like it's still have some distance away from an idea linux enviroment . The legacy version I've apt-get update and upgrade after login into the system, so all the software in the system is on their latest version. on default configuration, the wifi is not usable. I've to uncomment the ap6211 line in the /etc/modules file. after uncomment and restart, the wifi is usable and stable (very cool !). I've tried to transport 100G+ data through wifi interface, doesn't have any trouble with it. I can see card0 and card1 in the /proc/asound/ sub directory. and aplay -l can list 2 sound card. when I use card0 to play music file, the sun7i integrated audio codec driver works very well, I can plug my earphone into the 3.5mm headset jack on the board and hear the sound. But when I choose card1 to play , although the /proc/asound/card1/pcm0p/sub0/hw_params shows the correct value (so that tell me that the alsa driver layer working correctly at least), but I can't hear any sound through my PCM5102 DAC which connected to the M1 Plus board . and I've tried to use a logic analyzer to observe the i2s signal on the pin35/36/40. it doesn't show the right signal graph. so I guess the driver doesn't work corretly and the i2s core in the A20 chipset is not working at all. it looks like in the vanilla version, the m1plus dts file is different from the pipro dts file. but in the legacy version, the m1plus's script.bin file is just the same as the pipro's. does this correct ? The Vallina version I've modified the boot.scr file to make kernel use the sun7i-bananapi-m1plus.dtb file wifi is not usable. brcmfmac driver always tell me -110 error. there are no usable i2s driver in the current mainline driver and my question is: with legacy version, what can I try to make the i2s audio driver work right ? fex file or some any other magic configuration file? with vallina version, what can I try to make the wifi driver work right ? at last, very thanks for this great distribution, it's really a mess to collect so many fragment information through different github repo . ( u-boot/kernel/dts/driver and so on ) . I think it looks like A20 is the mainline support chipset in the sunxi community. hope we can provide better support for it.
  15. root@x1c:/tmp# diff -u m1plus.dts.orig m1plus.dts --- m1plus.dts.orig 2016-05-07 17:52:38.000000000 +0200 +++ m1plus.dts 2016-05-07 18:16:36.000000000 +0200 @@ -704,6 +704,13 @@ bus-width = <0x4>; non-removable; enable-sdio-wakeup; + brcmf: bcrmf@1 { + reg = <1>; + compatible = "brcm,bcm4329-fmac"; + interrupt-parent = <0x3a>; + interrupts = <7 15 0x00000008>; /* PH15 / EINT15 */ + interrupt-names = "host-wake"; + }; }; usb@01c13000 { @@ -1081,7 +1088,7 @@ allwinner,pins = "PI4", "PI5", "PI6", "PI7", "PI8", "PI9"; allwinner,function = "mmc3"; allwinner,drive = <0x2>; - allwinner,pull = <0x0>; + allwinner,pull = <0x1>; linux,phandle = <0x25>; phandle = <0x25>; }; the Armbian_5.10_Bananapipro_Debian_jessie_4.5.2 install doesn't make my M1+'s wifi usable. first, I use dtb -I dtb -O dts to get the m1-plus's dts source file. and then apply this patch. after apply this patch, my M1+ board's wifi is working well: root@bananapi:/home/luoyi# ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether 02:48:0a:81:ca:65 brd ff:ff:ff:ff:ff:ff 3: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 52:e1:7f:c0:a1:08 brd ff:ff:ff:ff:ff:ff 4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 98:3b:16:c7:cd:81 brd ff:ff:ff:ff:ff:ff inet 172.16.100.149/24 brd 172.16.100.255 scope global wlan0 valid_lft forever preferred_lft forever inet6 fe80::9a3b:16ff:fec7:cd81/64 scope link valid_lft forever preferred_lft forever root@bananapi:/home/luoyi# uname -a Linux bananapi 4.5.2-sunxi #11 SMP Thu Apr 28 21:53:25 CEST 2016 armv7l GNU/Linux root@bananapi:/home/luoyi# dmesg |grep -i mach [ 0.000000] Machine model: Banana Pi BPI-M1-Plus
  16. First of all, thanks for great Armbian, works great... When will be a release; Ubuntu 16.04 (Xenial) for BPIM1+ ?
  17. Banana Pi M1+ There is a very strange issue using SPDIF and/or I2S output. ( mpd, alsa, Armiban 4.4, kernel: 3.4.109-banana ) When starting play a new audio track, the left and right channel random swapping. Upgrading Alsa mpd does not helps. It looks this is known, a kernel level problem. for example: http://mailman.alsa-project.org/pipermail/alsa-devel/2011-February/037038.html Any suggestion how can I solve this issue? Thanks in advance!
  18. Hello, I have installed Armbian on my Banana M1+ and I have noticed „something“ strange in network communication. The network connector blinked rapidly even though nothing was running so I have installed iftop and found out this: iftop -i eth0 -NP Ankh-Morpork => a81.sub72.net78.udm.net Ankh-Morpork:51413 => a81.sub72.net78.udm.net:57855 Ankh-Morpork => ip70-118.245.80.crimea.com Ankh-Morpork:51413 => ip70-118.245.80.crimea.com:52026 Ankh-Morpork => adsl-225.37.6.247.tellas.gr Ankh-Morpork => ip5653f1a5.direct-adsl.nl Ankh-Morpork:51413 => adsl-225.37.6.247.tellas.gr:29932 Ankh-Morpork:51413 => ip5653f1a5.direct-adsl.nl:6881 I am wondering, what are these communications on newly installed system? Thank you, Regards, Petr Sourek
  19. Hi, I try to run Armbian 4.5 (Bananapi Ubuntu trusty 3.4.109 desktop) on my Banana Pi M1+, but after the "Starting kernel..." prompt the monitor show only the "No signal" warning. (I connect the Banana Pi to my monitor with HDMI - DVI converter, I will be able to try it with single HDMI cable a few days later.) However, it boots. I have a lot of tries to change the boot.cmd and the banana.bin, but I didn't achieve satisfying result. The result of dmesg: What can I try to solve it? Thank you very much for the help! Andrew
  20. Hi. I'm a new user. I have a Banana PI M1+, that is connected to a monitor with maximum resolution of 1280x1024 and with only DVI port. I'm using Armbian_4.5_Bananapi_Debian_jessie_3.4.109, and I installed XFCE using tasksel. If I leave it without any user interaction, the monitor goes to sleep, and I'm not able to wake it up anymore. But it works, because I'm able to connect to it using putty from another computer. So I tried to install Armbian_4.5_Bananapi_Debian_jessie_3.4.109, but I have the same problem. I tried also to disable "Switch Off After" in the Display section of power management without success. Can someone help me please?
  21. My board: Banana Pi, 1Ghz Dual Core, 1GB DDR3, SATA The os base: image http://www.bananapi.com/index.php/forum/others/1372-bpi-m1-bpi-m1-plus-new-image-ubuntu15-04-was-released#3306 Which is apt-get dist-upgraded to wily. I am trying to install self compiled kernel packages from: http://www.armbian.com/github/ I have succesfully used the compile.sh script and output for that is: total 19M -rw-r--r-- 1 petria petria 45K Nov 23 10:03 linux-dtb-next-sunxi_4.6_armhf.deb -rw-r--r-- 1 petria petria 52K Nov 23 10:03 linux-firmware-image-next-sunxi_4.6_armhf.deb -rw-r--r-- 1 petria petria 6.7M Nov 23 10:04 linux-headers-next-sunxi_4.6_armhf.deb -rw-r--r-- 1 petria petria 12M Nov 23 10:05 linux-image-next-sunxi_4.6_armhf.deb -rw-r--r-- 1 petria petria 169K Nov 23 10:05 linux-u-boot-next-bananapi_4.6_armhf.deb When I try to install packages on bananapi I get errors: root@bananapi:~/kernel# dpkg -i *.deb (Reading database ... 171422 files and directories currently installed.) Preparing to unpack linux-dtb-next-sunxi_4.6_armhf.deb ... Unpacking linux-dtb-next-sunxi (4.6) over (4.6) ... dpkg: error processing archive linux-dtb-next-sunxi_4.6_armhf.deb (--install): error setting ownership of './boot/dtb/sun6i-a31-hummingbird.dtb': Operation not permitted I suspect that is because the /boot partition is in VFAT format ? Can I change it to ext4 or so or how should I proceed to get armbian .deb kernel packages installed and working ? root@bananapi:~/kernel# dpkg -i *.deb (Reading database ... 171422 files and directories currently installed.) Preparing to unpack linux-dtb-next-sunxi_4.6_armhf.deb ... Unpacking linux-dtb-next-sunxi (4.6) over (4.6) ... dpkg: error processing archive linux-dtb-next-sunxi_4.6_armhf.deb (--install): error setting ownership of './boot/dtb/sun6i-a31-hummingbird.dtb': Operation not permitted
  22. I have a Banana PI M1+ with latest Armbian Jessie with 3.4.109 kernel. The dmesg contains many rows like this ones ... [ 1468.309084] Loading kernel module for a network device with CAP_SYS_MODULE (deprecated). Use CAP_NET_ADMIN and alias netdev- instead. ... ... [ 2779.128724] Loading kernel module for a network device with CAP_SYS_MODULE (deprecated). Use CAP_NET_ADMIN and alias netdev- instead. ... I tried to search on Google without success. Can someone help me please? Thanks.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines