[Temperature sensor DS18b20 (dallas 1-wire) easy configuration]

Hi All,

Just wanted to share a good story using armbian. I have used in the past 1-wire probes for temperature, and the process included decompiling, editing and recompiling dtb for my Banana Pi M1, which was not easy at all. Every firmware update deleted by changes and had to redo de recompilation.

 

With latest kernels and armbian version, the process is now extremely easy, just edit:

/boot/armbianEnv.txt

 

Adding this lines:

overlays=w1-gpio

param_w1_pin=PI3             # desired pin(7th pin (GCLK) or number 4 on first column where number 1 is +3V)

param_w1_pin_int_pullup=1     # internal pullup-resistor: 1=on, 0=off

 

I just struggled a little bit to find the GPIO code (decompiled dtb and checked possible candidates).

 

Information about temperature is here:

cat /sys/bus/w1/devices/XX-YYYYYYY[this is your probe serial, if you have more they will be in /sys/bus/w1/devices/] /w1_slave

 

You have plenty of information here, but don't need to do all they explain, just my edition has been enough:

http://linux-sunxi.org/1-Wire

 

 

 

[Troubles with kernel 4.14.144 on Odroid XU4]

On 9/30/2019 at 8:58 PM, ozymandias892 said:

I've noticed similar on 4.14.144 on a HC2, seems stable on 4.14.141.

 

I narrowed it down to transmission that causes it to crash once a torrent is uploaded, it seemed to sit there happily with no torrent activity.  Transmission is currently running in a docker on the ext4 SD card with the torrents downloaded to/seeded from the btrfs data drive.  

 

Same here on Odroid XU4, .144 crashes when a new torrent is added ("invalid inflight" as error). Installing latest armbian from today (with an older kernel) fixes issue.

[Lime2 mainline kernel with Debian 9 (stretch) becomes unresponsive (forced reboot required)]

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.

[Ecryptfs not available]

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

[Can we stop for a second and give credit due to the Armbian posse]

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.

[Where can i find Armbian for Banana Pi M1 ??? thanks]

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

[Battery management via AXP209 (Banana Pi/Pro)]

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.

[Battery management via AXP209 (Banana Pi/Pro)]

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)

[How to change motd?]

Realise this is an old thread - but as it was one of the first results in Google for this topic, I thought I'd update it with my (rather blunt) solution.

 

1) The script that produces the hardware info is located in /etc/update-motd.d - and is named "30-sysinfo".  Remove it (and if you like, the other scripts in there).  

 

2) Edit /etc/pam.d/login and /etc/pam.d/ssh - comment out the line that reads "session    optional   pam_motd.so motd=/run/motd.dynamic"

 

Result:  Editing /etc/motd now does the right thing - and my system no longer hangs for 30 seconds upon login simply to produce a colour ASCII art banner that tells me what CPU I'm running and what IP I'm logging in from.  

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

[No package updates]

Is it really 30-sysinfo? My login takes also time but there are several processes involved in the login

[Minidlna issue database]

Then I don't know... do you get any errors in logs? dmesg or minidlna.log?

[Cubietruck / A20: HDD more than 2TB?]

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

[Minidlna issue database]

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. 

[How to expand file system?]

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.

[No package updates]

Then I will disable /etc/update-motd.d/40-updates and save some miliseconds in the login process 

[No package updates]

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)

 

Hi,

 

unattended-upgrade is active by default. So updates (except kernel) are installed automatically. Have a look at /var/log/apt/history.log* for the installation history.

 

Bye,

wahlm

 

From my a20lime2 jessie headless server:

 

Start-Date: 2016-12-14  06:31:10
Commandline: /usr/bin/unattended-upgrade
Upgrade: apt:armhf (1.0.9.8.3, 1.0.9.8.4), libapt-pkg4.12:armhf (1.0.9.8.3, 1.0.9.8.4), apt-utils:armhf (1.0.9.8.3, 1.0.9.8.4), libapt-inst1.5:armhf (1.0.9.8.3, 1.0.9.8.4), apt-transport-https:armhf (1.0.9.8.3, 1.0.9.8.4)
End-Date: 2016-12-14  06:31:25

Start-Date: 2016-12-24  06:38:47
Commandline: /usr/bin/unattended-upgrade
Upgrade: libxml2:armhf (2.9.1+dfsg1-5+deb8u3, 2.9.1+dfsg1-5+deb8u4)
End-Date: 2016-12-24  06:38:49
 

[No package updates]

Just in case I have added backports and same result, no updates available

[No package updates]

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

[No package updates]

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)?

[Banana Pi M2 Ultra]

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

[Banana Pi M2 Ultra]

I suggest you use the search function in the forum for an answer. Before opening a new topic

[Enabling usb otg on banana pi m1 A20]

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

[Enabling usb otg on banana pi m1 A20]

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

[CIFS mount is failed on 5.23]

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)

[which armbian version - 5.20 or 5.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