sooperior

Members
  • Content Count

    45
  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Raffles

Applications

Everything posted by sooperior

  1. Same confirmation from me! I was driving me crazy trying to find what caused the system freeze. I have disabled most of the things that can be disabled and still occurs (even thought of log2ram because removing it gave me some more time to failure). The only difference in my case is sometimes it kernel panics and says something like "cpu 1 can not be stop". Some others it just freezes and I have to remove battery and power to restart. I have discarded power source: I have some cron tasks that peak cpu and temperature and seems to tolerate correctly, without voltage drops or simillar. It just happens... ramdomly. I'm running banana pi m1, latest kernel update.
  2. Just quick comment here: I am with latest armbian (5.23) and sun4i_ss seems to work correctly (seems, I need futher testing). So problems with encryption (ecryptfs, ssh, etc) should be gone
  3. My acknowledge to these guys too, and also to zador.blood.stained. The involvement and support I have seen in this project is lot better than most commercial initiatives. I donated because they really deserve it, and that's the real way to say thanks and keep up the good work.
  4. Be aware that Banana Pi and Pro share the same image, so don't get crazy if you see Banana Pro in your files or login
  5. By the way, I didn't check your link. Yes, you can also use those scripts but the guys at armbian made it a "built-in" feature. I think that my approach on the message above is way more simple.
  6. If you are using mainline kernel, you can use cron (for instance) to read every X minutes: /sys/power/axp_pmu/ac/connected >>To find out if connected to AC power or not (then it's battery) /sys/power/axp_pmu/battery/capacity >> To get a % of battery charge To me is easier to say at 20 (%) than 3.75 mV or similar I have a script that checks every 10 minutes, when ac is cut off it sends a warning mail. When battery is <20% it goes to self-shutdown Legacy kernel has something similar, but I can't check right now (google for that if you need it)
  7. Alternatively, you can do chmod -x 30-sysinfo or any other script you want to disable. The effect is the same as removing but you keep the file in case you want it in the future
  8. Is it really 30-sysinfo? My login takes also time but there are several processes involved in the login
  9. Then I don't know... do you get any errors in logs? dmesg or minidlna.log?
  10. It is possible. At least for banana pi M1 (A20) it can handle a 3TB hdd with no issues. Just remember that you have to change your disk partition table to GPT instead of standard MBR because the latter is limited to 2.2 gb. This is regarding SATA connection, if you use some kind of usb-to-sata adaptor, check that it is able to handle >2.2 TB
  11. Do you have enough inotify watches?I can't remember exactly where (look on google for increasing inotify watches on debian) but the default was low for me on debian. Maybe the other distributions just have more value by default.
  12. I suggest you use a computer with linux (installed or live) to do that, for instance with gparted. Resizing from the running system, even if possible (raspbian is able) is not a good idea.
  13. Then I will disable /etc/update-motd.d/40-updates and save some miliseconds in the login process
  14. That was it, you really hit the point. When i check history.log (.1 .2) there are traces of the updated packages. Thank you very much for the tip. And by the way, I'm gladly suprised that armbian has this feature turned on, I could never imagine that (and I love to keep my system updated)
  15. Just in case I have added backports and same result, no updates available
  16. Hi! Apollon77: Yes, all of them seem to download properly, no errors, timeouts, etc And I have checked the sources.list and looks pretty much the seem, I just miss backports, could that be the reason? armbian.list.txt sources.list.txt
  17. Hi! Is it only me or there are no updates to packages? Let me explain, I'm running jessie server on A20 latest stable kernel and when I run apt-get update, apt-get upgrade there are never updates available. I have experienced this for some of the latest releases and now I'm starting to thing that something is wrong with my system. Especially because I have a raspberry pi and that (yes, I know is raspbian) is getting updates to packages from time to time. I haven't modified or customized anything in the sources list. And the thing is that I'm getting updates for firmware/kernel when they are available. Any ideas? Is it something normal for armbian (/debian)?
  18. I know it is just shouting in the desert but nowbody should buy a board and then ask a third party for support. Instead we all should write the seller and say: You know what? Your product looks great but I will not buy a single one neither advice anyone to buy until third parties (sunxi, armbian...) say yes, this board has released all required docs to support it. Or if you have purchased one return it back: You sell it as open source. I have found your sources are missing. Here it is and give me my money back
  19. I suggest you use the search function in the forum for an answer. Before opening a new topic
  20. Interesting... but this thread is more or less about otg in "otg mode" or reliability issues, but I'm not able even to get anything detected. What is driving me crazy is this error: [ 4.516751] usb_phy_generic.0.auto supply vcc not found, using dummy regulator [ 4.517180] musb-hdrc musb-hdrc.1.auto: musb_init_controller failed with status -16 [ 4.517230] musb-hdrc: probe of musb-hdrc.1.auto failed with error -16 There is almost no info about that on google, I'm afraid it could be something armbian-specific PS: I'm not using any custom kernel, just out of the box armbian 5.23 with kernel 4.8.4
  21. Hi All, I'm trying to get usb otg enabled as host mode to add, for instance, a keyboard with a powered hub (I know otg is not delivering power or at least I don't want to drain more power with the otg) I'm using vanilla kernel 4.8.4 so I kind of expect otg enabled as host mode by default. Anyway, I get into dts and make sure this section: usb@01c13000 { compatible = "allwinner,sun4i-a10-musb"; reg = <0x1c13000 0x400>; clocks = <0x2 0x0>; interrupts = <0x0 0x26 0x4>; interrupt-names = "mc"; phys = <0x30 0x0>; phy-names = "usb"; extcon = <0x30 0x0>; allwinner,sram = <0x31 0x1>; status = "okay"; dr_mode = "host"; linux,phandle = <0x6e>; phandle = <0x6e>; }; has status=okay and dr_mode=host Driver seems to be the problem, I get this message on dmesg [ 4.516751] usb_phy_generic.0.auto supply vcc not found, using dummy regulator [ 4.517180] musb-hdrc musb-hdrc.1.auto: musb_init_controller failed with status -16 [ 4.517230] musb-hdrc: probe of musb-hdrc.1.auto failed with error -16 #modprobe sunxi does nothing google shows only one result for this error Any ideas for troubleshooting? I've also been looking for ideas in this thread https://forum.armbian.com/index.php/topic/385-banana-pi-usb-otg/but it seems to show the steps I have followed
  22. I think as a new bug on the allwinner security system sun4i-ss kernel module (maybe new version in armbian) or something changed on the armbian kernel that conflicts with this module. I have come to the same problem with ecryptfs, which internally uses ss. sun4i-ss 1c15000.crypto-engine: ERROR: Empty IV I have tested the same solution (blacklisting module) and it works. You just lose hardware acceleration (=slower)
  23. You can wait for it to be on the download page. The thing is that new version is released (and available) to update a current system, but it takes a while until developers build the full image and post it on the download page. If you want it now, you can download the "old" version and apt-get upgrade
  24. Hi I have a suggestion to modify update-mot.d script 30-sysinfo. It reports battery chargin or not depending on percentage (if <100% then is charging): # Battery info for Allwinner # kernel 4.4+ axp_dir="/sys/power/axp_pmu" if [[ -e "$axp_dir" ]]; then status_battery_connected=$(cat $axp_dir/battery/connected) if [[ "$status_battery_connected" == "1" ]]; then status_battery_charging=$(cat $axp_dir/charger/charging) status_ac_connect=$(cat $axp_dir/ac/connected) battery_percent=$(cat $axp_dir/battery/capacity) # dispay charging / percentage if [[ "$status_ac_connect" == "1" && "$battery_percent" -lt "100" ]]; then status_battery_text=" charging" elif [[ "$status_ac_connect" == "1" && "$battery_percent" -eq "100" ]]; then status_battery_text=" charged" else status_battery_text=" discharging" fi fi fi However, at least on banana pi M1 (A20) it can be below 100% and not charging, Seems that the PMU doesn't charge just for 1-2%. So we can just use driver info to check if it is really charging, like this: # Battery info for Allwinner kernel 4.4+ axp_dir="/sys/power/axp_pmu" if [[ -e "$axp_dir" ]]; then status_battery_connected=$(cat $axp_dir/battery/connected) if [[ "$status_battery_connected" == "1" ]]; then status_battery_charging=$(cat $axp_dir/charger/charging) status_ac_connect=$(cat $axp_dir/ac/connected) battery_percent=$(cat $axp_dir/battery/capacity) # dispay charging / percentage if [[ "$status_ac_connect" == "1" && "$status_battery_charging" == "1" ]]; then status_battery_text=" charging" elif [[ "$status_ac_connect" == "1" && "$status_battery_charging" == "0" ]]; then status_battery_text=" charged" else status_battery_text=" discharging" fi fi fi Hope someone else finds it useful
  25. Just +1 for armbian. I used bananian for over a year and it had very few releases with very few characteristics. And if you have a look at their bug tracker right now it looks like dead. On the other hand the guys at armbian are doing a huge job, frequent releases with bugfixes (this is of paramount importance to me) and new features. My hardware is also banana pi M1 and decission for armbian is absolutely clear.