falcon03

Hi, I am using Armbian_jessie_4.5 with kernel 4.3.x on a Banana pi. When entering any systemctl related command, I get the following error: Failed to get D-Bus connection: Unknown error -1 Any idea on what the problem might be? It's a fresh install.

Hi Igor, I didn't forget about this task, but I just didn't have enough time to work on it. Let's add to this that bash scripting is not my favorite language... Et voilà , the picture is complete! Now I have something that should work and I plan on setting up a github repository tomorrow. Is GPL v3 or later licensing fine for eventual inclusion in your armbian images? Initially I'll be supporting just Debian Jessie, but I could extend distro support in the future.

Hi Igor, I'll definitely keep looking into it, even if I am tempted to start developing a similar solution from scratch. In fact, the concept is pretty simple. It surely won't be as flexible as ramlog, but I think I could make it work for sure.., not to mention the fact that the systemd service is already done. In any case, my kernel process hit eof for today! :-) Having read the whole systemd documentation and written my first service is enough! I'll be back tomorrow! :-)

Yes, I think so.

ramlog.service.zipI think the systemd service should do its job properly. Unfortunately, ramlog does not start. In fact, even if ramlog teststartstop gives a positive result, running ramlog start fails and reports the following message: [....] Starting ramlog-tmpfs 2.0.0: /bin/cp: ‘/var/log.hdd/.’ and ‘/var/log/.’ are the same file. failed! Do you have any idea on what might be causing this problem?

Hi Igor, this afternoon I made some progress. I now have a service for systemd that should start/stop ramlog appropriately, i.e. before syslog. I do not know wether this is enough, but anyways I'm going to give it a try. I'll let you know in a few minutes...

Hi Igor, well, I was thinking to something like that. However, ramlog has a cool feature: it can be started/stopped manually. And in fact I was able to do so on my Jessie installation... The problem is that to do so you need to stop all the daemons that keep /var/log busy, start ramlog and then start those daemons again. This is the problematic part, as ramlog is not able to start/stop daemons automatically when it is started manually. Anyways, I think that the problem could be solved by writing a proper systemd service. In fact, it should support the before= clause, whose meaning should be obvious...

Hi Igor, I tried using your script. It reported that the upgrade was completed successfully, but after reboot.... Well, the bananapi simply didn't reboot properly. So I had to reinstall from a clean image... After that, I am under the impression that the machine is slower than before. It is consuming more ram for sure (10 mb Wheezy+3.19.0 VS 32 MB Jessie+4.1.6). In addition to this, I am not sure wether the image is using both CPU cores: how can I verify this?

Hi Igor, I've found the ramlog source code. Looks like it needs to be tidied up... In any case, what problems did it give on Jessie in addition to the init script to be ported to systemd? BTW, it is licensed under GPL v3, so I think we could easily fork it and restart its development... I absolutely need it or something equivalent, otherwise the performance on my bananapi degrade too much...

So, you're basically confirming what I was worried about! :-( Since I run hostapd, squid3, apache2 and other daemons, a lot of logging happens; so I would not be happy with storing logs immediately to the sd card. Will the upgraded image use systemd as a vanilla debian installation? Basically, I think we could solve the ramlog absence by mounting /var/log to a tmpfs and preparing some scripts to store the logs on phisical disk on shutdown/every x period of time. I think I'll work on something like that in the future, otherwise I cannot upgrade to Jessie!

Hi all, is anyone running Debian Jessie on a Bananapi? I'd like to upgrade from debian wheezy to Jessie, but I am afraid of a performance degrade due to the fact that ramlog is not available for Jessie. Since linux tends to write a lot of things to its logs, do you know wether Jessie performs worse, better or the same as Wheezy on Bananapi? I use my board as a proxy, router and web server...

Hi Igor, sorry for getting back to this so late. I followed the directions and edited my boot.cmd accordingly, but after generating the boot.scr file and rebooting my bananapi still uses kernel 3.19.0. I've also noticed the changes you made and the introduction of the armbian repo, so I added that and updated the kernel packages following the directions you posted in another topic, but my bananapi keeps booting with kernel 3.19.0. So, how can I boot with the newer 4.1.6 kernel?

Hi all, I have a bananapi and I have installed the debian Wheezy image with kernel 3.19.0. Now, I’d like to upgrade to kernel 4.0.4 to see wether the ananlog audio output is supported; so I downloaded all the deb packages from the website and installed them, but after reboot the system is still using kernel 3.19.0. How can I switch it to use kernel 4.0.4? I guess I should edit something in boot.cmd and convert it to boot.scr, but what should I change exactly? Thanks in advance for your help!