Active threads

Showing topics posted in for the last 365 days.

This stream auto-updates     

  1. Past hour
  2. Trying to boot NanoPi-K2

    [UPDATE] Turns out the NanoPi K2 was also affected by the Amlogic ATF allocation issue, I patched the device tree to rectify the issue. Not well tested, but I could kill it in a matter of seconds before, it does not fail under any memory-intensive test I could throw at it quickly.
  3. Today
  4. I've compared the kernel config for mainline and Marvell's 4.4 and one thing that stands out in regards to the SD card issue is: CONFIG_MMC_SDHCI_XENON In the linux-mvebu64-default.config it is set to y, in linux-mvebu64-next.config is it not set That could explain why it works to @umiddelb, his defconfig has it enabled too. I'll try it myself when I get the chance but that could be a few days away.
  5. Yesterday
  6. The same problem when I try to move root file system to SSD. After whole process was finished the script ask for reboot. After reboot I can't login neither with putty nor OMV through web interface. It is anything to do before I use 'nand-sata-install' script? NAS_login_attempt.avi
  7. @Igor I'm seeing the same behaviour from the NanoPi K2 (same reference design). Not being 1st priority I haven't dug in too deeply. I applied the ATF patch similar to the meson-GXL (Le Potato) and that fixed it on the K2.
  8. SPI loopback test

    Hi, every one! have any of you guys tried to perform SPI loopback tests on any of existing boards ? I mean this driver code I tried to find any information on how to run tests but I completely failed to make it. It would be nice if someone shares a step-by-step instruction. Thanks a lot.
  9. I will try and inform you! :-)
  10. important MMC: No card present error on Allwinner boards

    You have wrong file paths in this patch, it needs to be done relative to the u-boot repository root, so file paths should be "a/configs/nanopi_m1_plus_defconfig" and "b/configs/nanopi_m1_plus_defconfig" - check existing patches in the repository for examples:
  11. Orange Pi R1

    Update: Debian Jessie and Ubuntu Xenial with 3.4.113 (stable) Debian Stretch with 4.13.14 (nightly testing) Bootlogs: Running AP: wlan0 IEEE 802.11bgn ESSID:"ARMBIAN" Nickname:"<WIFI@REALTEK>" Mode:Master Frequency:2.432 GHz Access Point: 08:EA:40:7C:02:B1 Bit Rate:150 Mb/s Sensitivity:0/0 Retry:off RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0
  12. It's a small bug. Fixed. Tomorrow there will be a new server test image as well:
  13. Bananapi suddenly powers off

    Sure, fix your underpowering problems. I also hope a moderator has splitted the relevant posts here and merges/creates them into just another new thread over at
  14. My OpiPC2's USB HDD read speed is 1MB/s

    My knowledge is limited even to archive simple task on these SBC, I still trying to find good resources to improve my understanding. Your reply is a lot of help to me, thank you.
  15. You are absolutely right, I think these kind of mistake is too common and counter productive. And I feel stupid to make one more.
  16. ARMBIAN for Amlogic S905 and S905X

    The Tinker Board legacy did this, I had to change frequency governors from "conservative" to "ondemand". That's assuming you haven't already done that. ;-)
  17. Upcoming release questions

    Hm. Looks like there are indeed upstream repository problems, and fixing this for Xenial while not breaking Jessie build is tricky.
  18. Hello, guys, I am having some strange boot messages for my bananapi m2 running 4.13.14. They all are more or less device-tree related. May I ask you to look at it and give some comments ? 1) there is always a lot of messages like below, but WiFi is working fine: [ 10.801417] brcmfmac: brcmf_p2p_create_p2pdev: timeout occurred [ 10.801434] brcmfmac: brcmf_cfg80211_add_iface: add iface p2p-dev-wlan0 type 10 failed: err=-5 ....... [ 26.108251] brcmfmac: brcmf_fweh_call_event_handler: no interface object [ 26.108260] brcmfmac: brcmf_fweh_event_worker: event handler failed (72) 2) [ 8.460591] of_get_named_gpiod_flags: can't parse 'allwinner,pa-gpios' property of node '/soc@01c00000/codec@01c22c00[0]' [ 8.460598] of_get_named_gpiod_flags: can't parse 'allwinner,pa-gpio' property of node '/soc@01c00000/codec@01c22c00[0]' 3) [ 4.422315] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/soc@01c00000/mmc@01c11000[0]' [ 4.422322] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/soc@01c00000/mmc@01c11000[0]' 4) [ 3.653968] sun6i-a31-r-pinctrl 1f02c00.pinctrl: Reset controller missing 5) [ 3.645558] of_get_named_gpiod_flags: can't parse 'usb0_id_det-gpios' property of node '/soc@01c00000/phy@01c19400[0]' [ 3.645565] of_get_named_gpiod_flags: can't parse 'usb0_id_det-gpio' property of node '/soc@01c00000/phy@01c19400[0]' [ 3.645595] of_get_named_gpiod_flags: can't parse 'usb0_vbus_det-gpios' property of node '/soc@01c00000/phy@01c19400[0]' [ 3.645602] of_get_named_gpiod_flags: can't parse 'usb0_vbus_det-gpio' property of node '/soc@01c00000/phy@01c19400[0]' 6) [ 3.188346] of_get_named_gpiod_flags: can't parse 'gpio' property of node '/vcc3v0[0]' [ 3.188563] of_get_named_gpiod_flags: can't parse 'gpio' property of node '/vcc3v3[0]' [ 3.188743] of_get_named_gpiod_flags: can't parse 'gpio' property of node '/vcc5v0[0]' 7) [ 0.001853] /cpus/cpu@0 missing clock-frequency property [ 0.001862] /cpus/cpu@1 missing clock-frequency property [ 0.001870] /cpus/cpu@2 missing clock-frequency property [ 0.001880] /cpus/cpu@3 missing clock-frequency property Which ones of messages above are critical ?? Thanks a lot! dmesg_bananapim2.txt
  19. NanoPi Duo (plus Mini Shield)

    I have a few of those little guys, that's funny.
  20. SD-card destroyed by power-off ???

    This is about filesystem corruption and on the 1st generation Raspberries (A and B, not including A+/B+ and all the later variants!) there was a nice underpowering <--> SD card failure relationship: (reading through all the comments there is also interesting since you can easily see that a lot of Raspberry Pi users consider SD cards totally unreliable). That being said if you do not properly shutdown an Armbian installation filesystem corruption can occur as well though I never ran into this if not the SD card itself became corrupt (they all do after some time but this is just due to wear out or physical damage -- I just cooked one to death recently). Armbian's rather high commit interval of 10 minutes might add to this behaviour as well as an fsck running at boot if necessary (initrd). But if you have to deal with power losses you should not trust in filesystem self-healing but prepare for the worst (using a read-only rootfs, just search the forum for recipes) Not on any of the boards Armbian supports. The only SBCs I own that really need a FAT partition to boot are Raspberry Pis since there the primary OS that runs on the VideoCore IV can only be loaded from FAT due to the 1st stage bootloader living in the SoC not able to deal with anything else (that's also where the 'use SD-Formatter and format your SD card prior to usage' BS originates from since Raspberry Pis can not deal with ExFAT too while all modern SD cards exceeding a certain capacity ship preformatted with ExFAT. SD-Formatter is only needed with Raspberries Pi, SDXC cards and when the user wants to run NOOBS)
  21. Z28 [RK3328] 1/8

    My Z28 PRO is running Armbian using this method and our Rock Nightly image ... of course, fine-tuning is needed since I don't see ethernet nor Wifi, but luckily there is a screen and USB. Serial console login works. How to get properly into MASK ROM mode, which is needed to flash to eMMC on Alfawise Z28 PRO? Short a resistor marked on a picture and attach male A-A USB cable to USB otg port - on the other end as USB3.
  22. SD card speed

    Avoid sequential performance, because thats meaningless in the context of single board computers. What you should be focusing is random performance (4k-1 and 4k-32) which normally sux with cheap cards (think 0,01MB/s). Exception to this are samsung evo/evo+ cards, which have very good random 4k performance for SD card. At least that used to be the case, please someone correct me if i'm wrong.
  23. Banana Pi randomly not working

    I'm sorry but I'm a little confused what you mean by that. I tested my SD card using h2testw and this was the result It warned me about using just 7571 of the 7572 MByte of the SD Card before it started the test but I chose the default of using the whole capacity of the SD card. I tried manually setting 7572 MByte but the program still insisted and fell back to 7571 on manual. I don't think there is any problem with my SD card and I think the warning produced by h2testw is not in anyway related with what happened with my previous installation. Well I guess this post ended in more question than answers. I'll just observe it this will happen on a new installation.
  24. CubieTruck Nand installation

    So "Armbian_5.31_Cubieboard2_Debian_jessie_next_4.11.5" has no NAND support? Damn, I ruined my install, selected "install Next kernel" and... Now either to reinstall 3.4 to NAND or install 4.1 on SD?
  25. Wireguard on Armbian & TinkerBoard

    Wondering if Jason (@zx2c4) is still hanging around here... Question: is there a description / manual for the Wireguard config file syntax (i.e. all possible parameters)? Background: I have two Wireguard tunnels set up. The first (call it wg0) is my "main" interface (all traffic is routed through it); the second (wg1) is only a site-to-site connection to a different location. So when going from my location to the remote location, the wg1 traffic goes through wg0 until it hits wg0's endpoint and over the public Internet afterwards. Problem: I cannot set up the second interface (wg1) using wg-quick - or, more accurately, I can bring it up using wg-quick, but I cannot bring it down. When I do "wg-quick down wg1", the entire connectivity goes MIA. Obviously, I am not too keen to do that on the remote site, where I don't have "hands and eyes" to reboot the box, so I ended up building my own (ugly) script to start and stop the tunnel. The exact moment where everything dies is (I have added a "set -x" in the del_if() function in wg-quick): + cmd ip -4 rule delete table main suppress_prefixlength 0 + echo '[#] ip -4 rule delete table main suppress_prefixlength 0' [#] ip -4 rule delete table main suppress_prefixlength 0 + ip -4 rule delete table main suppress_prefixlength 0 My limited understanding says wg-quick is taking down the main (routing?) table, which causes all connectivity to collapse. I am therefore wondering if there is a way to tell wg-quick that this is not a "main" tunnel, i.e. it is not supposed to use it for redirecting / un-redirecting all traffic (similar to OpenVPN's "redirect-gateway def1" option). I googled a fair bit, but couldn't find anything.
  26. Last week
  27. Strange: sometime on reboot time and date is right, sometime is reset to 1970. RTC is brand new... but im thinking the battery is dead. Ok people... i need to understand. Ill write after battery. change.......
  28. Create an AP on Orange Pi Zero H2

    I have used these two guides in conjunction with changing to the beta branch, which the friend Igor recommended.
  29. Why are you using Armbian?

    > I dont like these "small" systems whcih only support OpenWRT Most small systems support only OpenWRT due to lack of resources; OpenWRT was born as an alternative open OS for Linksys home/SOHO access points and similar hardware with a fraction of the resources our SBC boards can count on today. Armbian installation on that class of devices would be impossible. > armbian/debian is for server type systems and mostly doesnt need the multimedia (video) of a raspberry pi. I'd say it's a complete dress one can cut to the desired length while OpenWRT is a nice pair of shorts full of pockets packed with tools:) Regarding multimedia, one of my goals with small boards such as NanoPIs and Orange PIs etc. would rather be the feasibility of the video output to be used in instruments to show data, waveforms etc with decent speed. That should require only 2D acceleration with no codecs involved.
  1. Load more activity