How to start RuneAudio installation? [photo attached]

[Quaresma]

Well, I think I did everything according to the downloading instructions page. Now, I have inserted the login [root] and password [rune] and I don't really know what to do or write in front of [root@runeaudio ~] #. I only want to continue with the installation of Rune Audio in my Raspberry Py B+. Can anyone help me? Thanks!

[ACX]

If you see that screen it means that you already have installed it... Just point a web browser to or and have fun

A RuneAudio device (in this case, your Raspberry Pi) is meant to be used as an headless server and controlled from remote by another device (PC, tablet or smartphone - anything capable of running a modern web browser). So you won't need a monitor and a keyboard connected to it to enjoy the music.

[Quaresma]

Thank you very much for your reply ACX. I have tried several times to open the RuneAudio application using my IP Address (http://192.168.1.136), but it was only half satisfactory because I could see the Player's page with an information in the middle: "MPD-Empty queue, add some music!" and when I tried to open the MPD item or any item of the MENU (upper right corner) the screen presents the "Connecting..." icon, but it really doesn´t connect to anything and freezes. It stays like that, locked up, until the page is manually forced to close. So, I thought I better use another way to get into the configuration mode and not wirelessly. It seems that:
1. Rune Audio didn't get the IP address automatically when it booted on the device for the first time;
2. At present the interface RuneUI doesn't allow any settings or changes through the configuration menu.

I think I have to uninstall RuneAudio from the SD card. Is there a way of doing it safely? At present I can't do anything else with my Raspberry Pi because I can't make that first screen go off! Thanks in advance.

[hondagx35]

Have you tried to update your installation?
If not, please follow these steps:
how-to-update-the-runeui-via-git-t547.html

[Quaresma]

Hi, Hondagx35, thanks for your reply. As per your suggestion, I have made the installation update and it went sucessfully. Sixteen files have been changed. But something continues to be wrong because the spinning arrows keep coming to freeze the monitor as I press any menu button, even when I'm in the Development Settings page. I don't understand why the UI tries to make a connection when is already connected to the device. And now, this warning message appears in the lower part of the screen: "Warning: socket_write() expects parameter 1 to be resource, boolean given in /srv/http/app/libs/runeaudio.php on line 104 Warning: socket_last_error() expects parameter 1 to be".
Thanks again.

[Quaresma]

When I power up my Raspberry Pi I can see on the television, among those hasty lines running up the screen, two warning messages I believe they are the cause of my problem, but I don't know whether this is due to the installation of the Raspberry Pi operating system or to the flashing of the RuneOS onto the SD card:

1. [FAILED] Failed to listen on Journal Socket (/dev/log).
2. [FAILED] Failed to listen on Journal Socket.

All the other lines have a green [OK] before the statement. Any ideas to solve this problem? Thank you in advance.

[hondagx35]

Hi,

these two error messages are absolutly normal and have nothing to do with your problem!

After the update your pi (rune) has to work.
Best would be to reinstall the image on your sd-card.
Before making any changes go to the dev page and make the update.

Always a good idea after an update is to clear your browsers cache (Ctrl-F5 forces a cache refresh).

[Tass]

I'm having the exact same issue. Spinning 'connection' image, can't do anything. I've performed the update, but still have the issue. I don't mind re-writing the SD card - it'll be annoying if this keeps happening though...

Otherwise - really great! Looking forward to playing!

[popov]

Hi

I may have the same "issue".
Please test :
[list=]open a new instance. he second willa have the same issue, but the first one should work.
With IE, don't allow cace => IE options[/list]

I not really understand why, and you may have to switch between instances
Look like puh client is not receving the information.

Boring, but working

Regards