Search the Community

Showing results for tags 'help'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Announcements & first aid
    • Announcements
    • Board doesn't start
  • Community forums
    • Common issues / peer to peer technical support
    • Reviews, Tutorials, Hardware hacks
    • Help wanted
    • Feature Requests
    • TV boxes
    • General chit chat
  • Bug tracker - supported boards and images only
    • Allwinner A20
    • Allwinner H2 & H3
    • Allwinner A64, H5, H6 and H616
    • Armada A388, A3700
    • Amlogic S905(x), S922X
    • NXP (Freescale)
    • Rockchip 3288 & 3328
    • Rockchip 3399
    • Other supported boards
  • Development
    • Development
  • TV Boxes's General Chat
  • TV Boxes's Reviews/Tutorials
  • TV Boxes's FAQ
  • TV Boxes's TV Boxes running Armbian
  • TV Boxes's Rockchip CPU Boxes
  • TV Boxes's Amlogic CPU Boxes
  • TV Boxes's Allwinner CPU Boxes
  • Android fanboys's Forums
  • Gaming on ARM's Reviews
  • Gaming on ARM's Issues
  • Kobol Forum's Helios4
  • Kobol Forum's Helios64

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start






Website URL






Found 17 results

  1. Hello everyone, I’m starting this message by apologizing for my poor English (I am French) and also by informing you that I am a newbie with Linux. I have a big problem with my NAS Helios64. At first, I thought this problem was caused by OMV. So I went to the OMV forum to explain my situation. I created the following topic: . There, a kind moderator (macom) asked me to enter some instructions to try to pinpoint the root of the problem. After giving him some outputs, he told me: "For me it looks like your SD card is dead." My installation is not on an SD card but on the eMMC chip of the Helios64. (I followed the Kobol wiki instructions exactly from here : ) After that, my NAS has become unreachable. I can no longer log into the OMV Dashboard. I cannot reach the NAS by SSH either. I can just tell you that all the LED lights on the NAS are solid blue. No red diode on. Is the eMMC chip of my NAS dead? Is there a solution that would prevent me from losing all the data stored on the hard drives? (They are in RAID1 and they are encrypted with the OMV LUKS encryption plugin) (I have not made a data backup elsewhere ... I know, big mistake!) I thank in advance all those who will take the time to help me.
  2. Hi Armbians, (If this question is already asked/answered please help me find the link.) I need the "ceph" and "rbd" kernel modules for my orange and banana pi. I am starting with the most recent images released: Armbian_4.5_xxxx_Debian_jessie_4.2.3. What are the minimum required steps to build the additional kernel modules? Where is the source tree for that kernel build (4.3.3-sunxi)? I would prefer to build directly on the PI (as opposed to x-compile) but either is ok. I tried a few things, including git clone of Igors "lib" project with build scripts. Runnig that pulled a kernel source tree: "sources/linux-vanilla/v4.3.3" which I am able to use to build my kernel modules, but they fail to load with: "modprobe: ERROR: could not insert 'rbd': Exec format error". Please enlighten me. Blade.
  3. Dear All ... My board is cubie2. Let's say I want to move led pins to pins other than PH20-PH21. In 3.x kernel , all we need to do is edit the fex file and compile it to script.bin. The edited parts is (from PH20/PH21 to PE10/PE11) : [gpio_para] gpio_used = 1 gpio_num = 8 gpio_pin_1 = port:PE04<3><default><default><1> gpio_pin_2 = port:PE05<3><default><default><1> gpio_pin_3 = port:PE06<3><default><default><1> gpio_pin_4 = port:PE07<3><default><default><1> gpio_pin_5 = port:PE08<3><default><default><1> gpio_pin_6 = port:PE09<3><default><default><1> gpio_pin_7 = port:PE10<3><default><default><1> gpio_pin_8 = port:PE11<3><default><default><1> [leds_para] leds_used = 1 leds_num = 2 leds_pin_1 = port:PH20<1><default><default><0> leds_name_1 = "green:ph20:led1" leds_default_1 = 1 leds_pin_2 = port:PH21<1><default><default><0> leds_name_2 = "blue:ph21:led2" leds_default_2 = 0 leds_trigger_2 = "heartbeat" become : [gpio_para] gpio_used = 1 gpio_num = 6 gpio_pin_1 = port:PE04<3><default><default><1> gpio_pin_2 = port:PE05<3><default><default><1> gpio_pin_3 = port:PE06<3><default><default><1> gpio_pin_4 = port:PE07<3><default><default><1> gpio_pin_5 = port:PE08<3><default><default><1> gpio_pin_6 = port:PE09<3><default><default><1> [leds_para] leds_used = 1 leds_num = 2 leds_pin_1 = port:PE10<1><default><default><0> leds_name_1 = "green:PE10:led1" leds_default_1 = 1 leds_pin_2 = port:PE11<1><default><default><0> leds_name_2 = "blue:PE11:led2" leds_default_2 = 0 leds_trigger_2 = "heartbeat" My question is , how to do it with vanila (4.x) kernels ? Sincerely -bino-
  4. Hi all, there is an issue with SPI on a Banana Pro (A20). I am on mainline kernel 4.5.5 now, but the problem already occurred on 3.4.109. SPI transfers are way to slow for my application, independently from the SPI clock. Investigating the SPI signals it turned out that there is an enormous delay between CS going active (low) and the transmission starting. The delay is in the magnitude of 10...20 usec which is a large multiple of the pure transmission time, so increasing the SPI clock does not solve the problem. The connected device is an SPI TFT display, so I have to send a large number of SPI words of 2 bytes each, where CS must toggle after each word (required by the target device). Consequently, the transmission of a large amount of data takes about several hundred times longer than required. I am not a driver expert, but I have looked into the source code of spi_sun4i.c which is the low level driver used for the A20 as far as I know. Here it seems, that the CS signal is under software control, i.e. it is handled as a normal GPIO. CS must be set/cleared by an explicit function call. I wonder, if this is the reason for the large delay. I found a quick-and-dirty workaround, where somebody configured the SPI controller directly via /dev/mem (i.e. bypassing kernel driver) and kept CS under hardware control, so the delay between CS and start of transmission is only some hundred nanoseconds. Now I am thinking of a modification of the SPI low level driver to keep CS under hardware control as well. However, I am not sure if this is a solution to my problem. Does anybody have a similar experience or a better idea than kernel modification? Any comments are welcome :-) Thanks
  5. I have Armbian Jessie running on a Orange Pi Lite board and the login script is showing the local loopback ip ( It appears to be doing this because /etc/update-motd.d/30-sysinfo calls ifconfig -a and pulls the first ip, which in this particular case, is the local loopback. For the orangepi-lite, i wrote the following command in and it fixes the problem in this case. sudo sed -i "s/ifconfig -a/ifconfig wlan0/g" /etc/update-motd.d/30-sysinfo It basically changes the script to pull the ip address from wlan0 instead of whatever one it finds first This could also be called from the command line for the same effect instead of during compilation. However, for other boards using an ethernet adapter, this obviously wont work without changing wlan0 to eth0 or whatever network you have. I am not the best a bash script, and I am trying to find a way to edit the script in /etc/update-motd.d/30-sysinfo to display the first valid inet address instead of just the first inet address it finds. It is currently pulled like so. ip_address=$((ifconfig -a) | sed -n '/inet addr/s/.*addr.\([^ ]*\) .*/\1/p' | head -1) Anyone have any ideas?
  6. Hi, not sure if this problem is related to Armbian, but in my case it occurs only on an Armian system. I have mainline kernel (4.7.x) running on a Banana Pro. wlan is configured as access point and works without any problems. eth0 is configured as client with static IP. The Banana is running 24/7, but the ethernet port is used only sporadically. The switch where eth0 is connected to is powered down most time. The problem is that eth0 forgets its IP configuration after a while, ifconfig then reports no IP address for eth0. I have to login via wlan and then ifdown/ifup eth0, then it works again. After a couple of hours (I dont know exactly how long), the IP is lost again. What is going wrong here?
  7. Hey, I compiled and installed the latest kernel (4.7.3 and uboot 2016-09) but something went wrong. The dtb file was missing. while a manually correct the missing dtb from another run a flashed uboot in the wrong way. Instead of using the drive /dev/sdc I used the partition /dev/sdc1. I read this: with these two commands I should have erased the first 1Mb dd if=/dev/zero of=/dev/sdc1 bs=1k count=1023 seek=1 dd if=u-boot-sunxi-with-spl.bin of=/dev/sdc1 bs=1024 seek=8 (Luckily there is no backup at all ) gpart gives me this: gpart -vg /mnt/veracrypt1/Armbian_5.14_Cubietruck_Debian_jessie_4.6.2.raw dev(/mnt/veracrypt1/Armbian_5.14_Cubietruck_Debian_jessie_4.6.2.raw) mss(512) Primary partition(1) type: 131(0x83)(Linux ext2 filesystem) size: 1525mb #s(3123200) s(2048-3125247) chs: (16/0/1)-(1023/3/32)d (0/0/0)-(0/0/0)r hex: 00 00 01 10 83 03 E0 FF 00 08 00 00 00 A8 2F 00 ---------------------------------------------------------------------------------------- gpart -vg /mnt/veracrypt1/broken_cubietruck.img dev(/mnt/veracrypt1/broken_cubietruck.img) mss(512) Primary partition(1) type: 131(0x83)(Linux ext2 filesystem) size: 14991mb #s(30701568) s(2048-30703615) chs: (0/56/33)-(913/88/8)d (0/0/0)-(0/0/0)r hex: 00 38 21 00 83 58 C8 91 00 08 00 00 00 78 D4 01 I try to use the values from the raw image to recover at least some data, but fsch.ext4 fails. Do you see an opportunity to restore the partition table? Or to recover the filesystem? Edit: Topic can be deleted. I wasn't capable of restoring the filesystem.
  8. Hi! Can anyone help me to enable kernel crash dumps option in the menuconfig? When I build the kernel, and when the menuconfig appears, there is no option of Kernel crash dump. To be more explicit, I need the following options activated ( based on ): CONFIG_CRASH_DUMP=y CONFIG_KEXEC=y CONFIG_DEBUG_INFO=y CONFIG_RELOCATABLE=y I have searched for them with the / feature in the menu config, but there are no such options. I need this in order to debug a device that is calling kernel panic at boot time. Thanks!
  9. How do i compile MT7601 Wifi Dongle Driver on armbian for orangepi one. I have an loboris image for Orangepi PC which has driver for MT7601. How i import driver from loboris kernel to armbian sd card. Please Help
  10. HI! Im using lamobo r1. How to build custom rootfs in armbian? Or If the related documents, plz leave a link.
  11. Hello, I'm using the armbian trusty image with legacy kernel and try to setup an iscsi target server with it. Actually I tried to build my own kernel with the instruction list and the tools of armbian and activated the iscsi target in the kernel configure. In I set kernel configure to yes and then I start compiling. Maybe you can tell me how to do it in the right way? Thanks and greetings
  12. Hello! Im new in this community, I would like to know if there is a language like the C of Arduino's or any other to use in Raspberry Pi. I would appreciate your help. Greetings!
  13. Hello everyone, I'm in the process of building a file/download server with a Banana Pi Pro using the JMB 321 SATA port multiplier. Right now I'm just trying to build an image that will allow me to boot from an SSD, then I will deal with adding the JMB. I compiled a fresh image following the menu options after executing ./ selecting bananapi/jessie/next and it boots up correctly except it does not detect the SSD I have connected directly to the SATA port.(does not show in blkid or fdisk -l) Image name provide: Armbian_4.83_Bananapipro_Debian_jessie_4.3.4 Going thru the kernel logs, I found this: Jan 26 20:22:03 localhost kernel: [ 3.498489] ahci-sunxi 1c18000.sata: PHY power up failed. Jan 26 20:22:03 localhost kernel: [ 3.498557] ahci-sunxi: probe of 1c18000.sata failed with error -5 It says on armbian/banana-pi that "NAND is not supported yet" for kernel 4.3.3, does this mean the SATA port? If so, is there a 4.x kernel that does support it? Or am I just doing something wrong? Has anyone been able to successfully accomplish what I am trying to do? (JMB with bootable SSD) Thanks for any help, greatly appreciated.
  14. Hi Igor! I am sorry for so many questions, but I just can't seem to find the solution for my question. I need to activate (install) the Philips SAA7111/3/4/5 video decoders module, that is located in Device Drivers -> Multimedia Support -> Encoders, decoders, sensors and other helper chips . (when running menuconfig) Usually, this is done by downloading a new kernel, then running the menuconfig and going to Drivers/Multimedia Support and unselect "Autoselect ancillary drivers (tuners, sensors, i2c, frontends)" and a new list of "Encoders, decoders, sensors and other helper chips ." appears. And there i select Philips SAA7111/3/4/5 video decoders module by pressing Y. After this I save the .config and compile the kernel and install it and reboot. I tried this on banana pi and it compiled without errors but I could not boot it. The image of the kernel, in /boot folder somehow needed to be linked to the zImage, which I could not do (I have read about the u-boot and could not figure out how to use it) and ultimately I decided to install the new Debian Wheezy 4.1.2 from your website. In a previous post you told me that in order to upgrade kernel, I need to follow the instructions from I did that, and tried to install the same kernel, 4.1.2 but it offered me no way of configuring it. Because the whole point of compiling new kernel is to add the Philips SAA7111/3/4/5 video decoders module, that is present by default in the kernel but it is not included/activated by default. So how can I do this? How can activate the Philips SAA7111/3/4/5 video decoders module ? Thank you very much in advance and sorry for so many questions.
  15. Hi! Can someone please explain how can I activate the "Encoders, decoders, sensors and other helper chips\VIDEO_SAA711X" option in menuconfig from Device Drivers -> Multimedia support ? I have banana pi and it is running debian wheezy kernel 3.19.3 from this link: I also have a easycap somagic usb video capture card and in order to install it's drivers, I need to activate all of it's dependencies from kernel otherwise when compiling the module, I get many warnings and when I try to do modprobe to the generated .ko file, it also gives me error. I contacted the developers of the driver for the easycap somagic smi2021 usb card and they said that those errors are probably because dependencies upon which the driver is depending are not installed/activated. Here is the full conversation (it is short): In the folder where I downloaded and extracted debian wheezy 3.19.3 when I run make menuconfig, I need to go to "Device Drivers -> Multimedia support ->Encoders, decoders, sensors and other helper chips -> Philips SAA7111/3/4/5 video decoders" but when I go to "Multimedia Support" there is no "Encoders, decoders, sensors and other helper chips" to activate or to choose. How can I get the "Encoders, decoders, sensors and other helper chips" to be in "Multimedia Support" when I run make menuconfig? Thanks
  16. Hi, I'm in need of help with the I2S "drivers" for Arch Linux ARM and the A20 processor. I need to create a 4-wire I2S output. 1. BCLK 2. LRCLK 3. DATA 4. MCLK = 256xfs I can't seem to work out how to make #4, a Master Clock fixed at 256 * Fs. I've been using this code as a starting point: and I am not a Kernel developer. At all. Thanks.
  17. I tried to rebuild the Banana Pi image with kernel 3.19.7 adding the configuration from here to the next config before rebuilding. I get a lot of prompts and I said m for modular or Y for yes to each of them. The tuner still isn't showing up in Tvheadend. I can donate some BTC so you have a test unit to help get this working.