The New 4-core Raspberry Pi

Raspberry Pi related support

Re: The New 4-core Raspberry Pi

Postby Tinitus » 22 Apr 2015, 19:47

Hi Da Alchimist,

thanks for your reply and the link. This looks promising.

Best Regards

Tinitus
Tinitus
 
Posts: 79
Joined: 20 Mar 2015, 20:53

Re: The New 4-core Raspberry Pi

Postby Tinitus » 23 Apr 2015, 23:49

Hi Frank,

I followed the cookbook, I downloaded all the files from the github. There were some in excess to the list in the cookbook, which I downloaded nevertheless. There is also one file missing in the cubox-i section:

wget https://github.com/RuneAudio/RuneOS/raw ... o.1.3501.0

There is no libva.so.1.3501.0 file in the cubox-i section. Can you tell me whether I need it? If yes can I download the one in the rapsberry section?

I have not installed the files I downloaded from the github yet. When I rebooted in order to set the wifi I already got the RuneOs it said version 0.3 and 1.3 and hardware rapsberry, is that normal?

Thanks for your help and Orion's cookbook.

Best Regards

Tinitus
Tinitus
 
Posts: 79
Joined: 20 Mar 2015, 20:53

Re: The New 4-core Raspberry Pi

Postby hondagx35 » 24 Apr 2015, 18:36

User avatar
hondagx35
 
Posts: 3042
Joined: 11 Sep 2014, 22:06
Location: Germany

Re: The New 4-core Raspberry Pi

Postby Tinitus » 24 Apr 2015, 19:47

Hi Frank,

thank you for your help. I had the idea to download libva using pacman before reading your answer. It seems to have worked fine. Afterwards I tried to install the ffmpeg........tar.xz file with pacman -U but I got the answer

"could not find or read file"

I then downloaded ffmpeg......tar.xz a second time and tried to install it using pacman -U and got the answer

"error: ffmpeg.......tar.xz: unrecognized archive format"

and

"error: ffmpeg.....tar.xz: cannot open package file"

Being a noob I would think I need a software able to read tar.xz files. If I was in windows I would think of something like 7zip. Do I need to install such a program on the C1?
concerning the master dev issue I followed the link you posted to my question whether it was possible to build something for the C1. Prefering to be on the leading edge, thanks for letting me know that there is also a dev branch for cubox-i. I will try to install one of the other pkg.tar.xz files in order to find out whether it is only the ffmpeg.......tar.xz file with which I have a problem or whether my problem is a general one.

Best Regards

Tinitus
Tinitus
 
Posts: 79
Joined: 20 Mar 2015, 20:53

Re: The New 4-core Raspberry Pi

Postby Tinitus » 24 Apr 2015, 20:02

Hi,

just another thought maybe the files for cubox-i (Freescale) do not work with my C1 (Amlogic). Then probably none of the packages for e. g. will work either.

Tinitus
Tinitus
 
Posts: 79
Joined: 20 Mar 2015, 20:53

Re: The New 4-core Raspberry Pi

Postby hondagx35 » 24 Apr 2015, 21:48

User avatar
hondagx35
 
Posts: 3042
Joined: 11 Sep 2014, 22:06
Location: Germany

Re: The New 4-core Raspberry Pi

Postby fminne » 02 May 2015, 13:45

Hi,
Thanks all for this nice product. I am starting to use RuneAudio on a RPI2. I experience a strange thing: when starting up the RPI2, it takes more then 90 seconds before I can contact the RPI2 via the browser. A ping is working nearly immediately after the power-up. I am using a wired Ethernet-connection and no WiFi-dongle.
I checked the log-files, in which I can see that the RPI2 is waiting on a wlan0-interface. After 96 seconds, it gives a time-out, after which everything is working perfectly.
[ 9.765622] systemd[1]: Started Network Name Resolution.
[ 11.087582] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
[ 11.093616] systemd-networkd[184]: eth0 : gained carrier
[ 11.107860] systemd-networkd[184]: eth0 : could not start IPv6 router discovery
[ 11.107916] systemd-networkd[184]: eth0 : failed
[ 96.252130] systemd[1]: Job sys-subsystem-net-devices-wlan0.device/start timed out.
[ 96.252249] systemd[1]: Timed out waiting for device sys-subsystem-net-devices-wlan0.device.
[ 96.252401] systemd[1]: Dependency failed for Automatic wireless network connection using netctl profiles.
I tried to find somewhere a configuration-file in which a wlan0 is asked to start, but I couldn’t find such a file.
Does anyone knows how I can get rid of those 90 seconds-delay?
On a RPI B+, I didn’t have that problem.
Regards, Frank M.
debug-log: http://pastebin.com/x20mqkMK
fminne
 
Posts: 3
Joined: 02 May 2015, 13:39

Re: The New 4-core Raspberry Pi

Postby hondagx35 » 02 May 2015, 15:31

User avatar
hondagx35
 
Posts: 3042
Joined: 11 Sep 2014, 22:06
Location: Germany

Re: The New 4-core Raspberry Pi

Postby fminne » 03 May 2015, 06:12

Hi Frank,

Thank you for the reply. Unfortunally, I can’t disable the netctl-auto@wlan0, because it is apparently not started:
[root@runeaudio ~]# netctl stop netctl-auto@wlan0
[root@runeaudio ~]# netctl disable netctl-auto@wlan0
No regular unit file found for profile 'netctl-auto@wlan0'
[root@runeaudio ~]# netctl list
eth0
[root@runeaudio ~]#
Even when I do “netctl list” before the 90 seconds have expired, only “eth0” is replied.
I presume it must come from somewhere earlier in the startup.

It seems to be solved: I removed the logical link " netctl-auto@wlan0.service" from the directory "/etc/systemd/system/multi-user.target.wants/". Now the RPI2 starts up without delay :D

The only strange thing which remains is that my webradio, which is in the queue, is not starting to play automatically after a reboot. The RPI B+ was always automatically playing the queue after a restart, but on the RPI 2, I have to log on and push the play-button.

Thank you for your help, Frank M.
fminne
 
Posts: 3
Joined: 02 May 2015, 13:39

Re: The New 4-core Raspberry Pi

Postby hondagx35 » 03 May 2015, 11:06

User avatar
hondagx35
 
Posts: 3042
Joined: 11 Sep 2014, 22:06
Location: Germany

support RuneAudio Donate with PayPal

PreviousNext

Return to Raspberry Pi

Who is online

Users browsing this forum: No registered users and 33 guests