Looking for help - Rasberry Pi - HiFiBerry Digi - Volumio

[ifor]

In MPod, select Menu, then Connections (guess you've already done this)

Select "Add player manually"

Select "Name" - give it any name you like

Connection mode - keep as the default (Remote)

Select Server - enter the IP address of your Pi

Ignore all other settings (ie leave them as they are) and press Save (top right corner)

If everything is working properly, you should now see your Pi listed under "Configured Players" with the name you gave it, it's IP address, and a bold "wireless" symbol and bold "remote control" symbol. If the wireless symbol is greyed out then MPod can't connect and something is [still] wrong with the set up.

If you do have a bold "wireless" symbol then select Menu again, then Browse, and you should see a list comprising of "USB" and "WEBRADIO"... that's probably as far as we can go for now as you don't have any music stored in the database yet.

Hope that makes sense - am a bit knackered and off to bed very soon! :wave:

The wireless symbol is greyed out, the remote symbol is "bold". The Pi wired, not wireless, so should I expect to see a bold wireless symbol if it was working correctly?

 

[ifor]

OK, on the pi,

Try a "sudo /etc/init.d/mpd restart" wait for that to finish, and then also do 'sudo /etc/init.d/ssh restart'

1) Stopping Music Player Daemon: mpd

Starting Music Player Daemon: mpdlisten: bind to '0.0.0.0:6000' failed: Address already in use (continuing anyway, because binding to '[::] :6600' succeeded)

2) Restarting OpenBSD Secure Shell server: sshd.

Then back to your Mac again try entering,10.0.0.102 in the browser, and try to ssh in again.

Could not access 10.0.0.102 from iMac browser.

 

[ifor]

Then back to your Mac again try entering,10.0.0.102 in the browser, and try to ssh in again.

Operation timed out

Whilst on your Mac also try pinging the RPi. Enter 'ping 10.0.0.102 -c 10' and post the output.

ping 10.0.0.102 -c 10

usage: ping [-AaDdfnoQqRrv] [-b boundif] [-c count] [-G sweepmaxsize] [-g sweepminsize]

[-h sweepincrsize] [-i wait] [-l preload] [-M mask | time] [-m ttl]

[-p pattern] [-S src_addr] [-s packetsize] [-t timeout]

[-W waittime] [-z tos] host

ping [-AaDdfLnoQqRrv] [-c count] [-I iface] [-i wait] [-l preload]

[-M mask | time] [-m ttl] [-p pattern] [-S src_addr]

[-s packetsize] [-T ttl] [-t timeout] [-W waittime]

[-z tos] mcast-group

 

[margetti]

Morning folks

Would be interested to see if the Pi can ping the mac...

From the pi type "ping -c 10 10.0.0.x" where x is the IP addr of your mac... you should get something like this:

pi@volumio:~$ ping -c 10 192.168.0.6

PING 192.168.0.6 (192.168.0.6) 56(84) bytes of data.

64 bytes from 192.168.0.6: icmp_req=1 ttl=128 time=2.00 ms

64 bytes from 192.168.0.6: icmp_req=2 ttl=128 time=7.30 ms

....

--- 192.168.0.6 ping statistics ---

10 packets transmitted, 10 received, 0% packet loss, time 9014ms

rtt min/avg/max/mdev = 3.892/9.238/16.236/3.326 ms

 

[margetti]

Question for daveh - does the mac support the "arp -a" command as it's used in windows?

We know from ifor's previous ifconfig results that his Pi's mac addr is b8:27:eb:14:a4:70 - would be interesting to see if the mac has this in it's arp table and what the corresponding IP address is - what do you think?

 

[ifor]

Morning folks

Would be interested to see if the Pi can ping the mac...

From the pi type "ping -c 10 10.0.0.x" where x is the IP addr of your mac... you should get something like this:

pi@volumio:~$ ping -c 10 192.168.0.6

PING 192.168.0.6 (192.168.0.6) 56(84) bytes of data.

From 10.0.0.102 icmp_seq=1 Destination Host Unreachable

repearted upto seq=10

 

[ifor]

I installed Fing on my iPad yesterday and 10.0.0.102 is not showing on the network.

 

[margetti]

From 10.0.0.102 icmp_seq=1 Destination Host Unreachable

repearted upto seq=10

Mmm... ok... let's try a few more pings on the Pi (just 4 pings instead of 10 to save a wee bit of time):

Let's see if it can ping itself -

ping -c 4 127.0.0.1

and then

ping -c 4 10.0.0.102

Now let's see if it can ping the Sitecom router -

ping -c 4 10.0.0.1

And finally, the AE -

ping -c 4 10.0.0.100

 

[ifor]

From 10.0.0.102 icmp_seq=1 Destination Host Unreachable

repearted upto seq=10

Mmm... ok... let's try a few more pings on the Pi (just 4 pings instead of 10 to save a wee bit of time):

Let's see if it can ping itself -

ping -c 4 127.0.0.1

and then

ping -c 4 10.0.0.102

Now let's see if it can ping the Sitecom router -

ping -c 4 10.0.0.1

And finally, the AE -

ping -c 4 10.0.0.100

What's the 127.0.0.1?

 

[margetti]

What's the 127.0.0.1?

That's the "loopback address" - "ping -c 4 127.0.0.1" is just saying "ping myself". It should produce the same result as "ping -c 4 10.0.0.102"

 

[ifor]

Mmm... ok... let's try a few more pings on the Pi (just 4 pings instead of 10 to save a wee bit of time):

Let's see if it can ping itself -

ping -c 4 127.0.0.1

and then

ping -c 4 10.0.0.102

Now let's see if it can ping the Sitecom router -

ping -c 4 10.0.0.1

And finally, the AE -

ping -c 4 10.0.0.100

It successfully pinged itself both ways, but the Sitecom and AE were both unreachable.

 

[margetti]

It successfully pinged itself both ways, but the Sitecom and AE were both unreachable.

Very odd!

From an earlier post - "Connection is thus: router / Ethernet cable / Airport Extreme / Ethernet cable / Homeplug / mains / Homeplug / Ethernet cable / Pi."

Is it at all possible to plug the Pi directly into the ethernet port of the AE? ie eliminating the Homeplug section of the network entirely

As a first course of action we wouldn't necessarily need the Pi connected to the monitor/keyboard - use Fing (great little app btw) to see if the Pi then appears on the network.

And if it doesn't appear then try a different ehternet cable and ethernet port on the AE. I know you have already gone through this with Dave, but for the Pi not to be able to ping the AE the only obvious conclusion is that there is a fault between the Pi and the AE (or the AE, but I doubt that as everything else is working off the AE ok).

 

[ifor]

It successfully pinged itself both ways, but the Sitecom and AE were both unreachable.

Very odd!

From an earlier post - "Connection is thus: router / Ethernet cable / Airport Extreme / Ethernet cable / Homeplug / mains / Homeplug / Ethernet cable / Pi."

Is it at all possible to plug the Pi directly into the ethernet port of the AE? ie eliminating the Homeplug section of the network entirely

As a first course of action we wouldn't necessarily need the Pi connected to the monitor/keyboard - use Fing (great little app btw) to see if the Pi then appears on the network.

And if it doesn't appear then try a different ehternet cable and ethernet port on the AE. I know you have already gone through this with Dave, but for the Pi not to be able to ping the AE the only obvious conclusion is that there is a fault between the Pi and the AE (or the AE, but I doubt that as everything else is working off the AE ok).

Unfortunately, since the Pi seems to be temperamental with regard to picking up an IP address we wouldn't know, without it being connected to a monitor, whether it had one or not.

This is interesting: I refreshed Fing and scribbled down all the IP addresses. I then shut down the Pi with sudo halt and refreshed Fing and the Pi appeared in the listing as IP address 10.0.0.102 Raspberry Pi Foundation. Fing must have spotted it at the end of the shutdown process. I've just rebooted the Pi a couple of times and on both occasions it hasn't got an IP address.

I've got to hit the road now to drive up north and I won't be back until tomorrow evening. I really do appreciate all the help from the two of you.

Cheers

Ifor

 

[Dave_]

Question for daveh - does the mac support the "arp -a" command as it's used in windows?

I don't know tbh. My experience of OS X was disappointing and short lived

We know from ifor's previous ifconfig results that his Pi's mac addr is b8:27:eb:14:a4:70 - would be interesting to see if the mac has this in it's arp table and what the corresponding IP address is - what do you think?

Its worth a try.

But I was starting to think maybe there is either a) a bug in volumio, or b) the image ifor is using is corrupt.

I' dug a spare SD card out earlier and flashed it with the latest version on the volumio (1.2 beta from 06/03/14)

My PI obtained an IP and I was able load the web UI, and connect via SSH. So doesn't look like its a bug.

At this point I'm wondering if its worth ifor formatting the SD and downloading/flashing a fresh copy of volumio and starting over in case it is corrupt and causing the wierdness

 

[margetti]

At this point I'm wondering if its worth ifor formatting the SD and downloading/flashing a fresh copy of volumio and starting over in case it is corrupt and causing the wierdness

Agreed!

The only other thing that has come to mind after a bit of googling is that the Ethernet port on the Pi may have a dodgy solder joint. It could certainly explain the behaviour we've been seeing... will be interesting to get a report from Ifor when he gets back as to what the Ethernet link lights on the Pi are doing :?

 

[ifor]

At this point I'm wondering if its worth ifor formatting the SD and downloading/flashing a fresh copy of volumio and starting over in case it is corrupt and causing the wierdness

I have already reflashed the card and it still behaved the same. I also tried another SD card, but the Pi doesn't seem to like that one. I had thought of trying Squeezeplug on another card. I will aim to get another card before I get home tomorrow evening.

 

[ifor]

The only other thing that has come to mind after a bit of googling is that the Ethernet port on the Pi may have a dodgy solder joint. It could certainly explain the behaviour we've been seeing... will be interesting to get a report from Ifor when he gets back as to what the Ethernet link lights on the Pi are doing :?

I'll check when I get home but I think I have a full set of lights lit:
ACT – D5 (Green) – SD Card AccessPWR – D6 (Red) – 3.3 V Power is presentFDX – D7 (Green) – Full Duplex (LAN) connectedLNK – D8(Green) – Link/Activity (LAN)100 – D9(Yellow) – 100Mbit (LAN) connected[/list]

 

[Dave_]

At this point I'm wondering if its worth ifor formatting the SD and downloading/flashing a fresh copy of volumio and starting over in case it is corrupt and causing the wierdness

I have already reflashed the card and it still behaved the same.

Did you re-download the image each time though, or use the same file?

If the later its possible that the image is corrupt, and unfortunately from what I could see volumio don't provide a checksum for their downloads.

I also tried another SD card, but the Pi doesn't seem to like that one. I had thought of trying Squeezeplug on another card. I will aim to get another card before I get home tomorrow evening.

IME it could be an SD card issue. I had an sandisk card that I had all sorts of problems with using rasbian (or any rasbian based distro) but was fine with any non rasbian based distro. Odd as it is.

Might also be worth giving runeaudio a go, which is basically the same as volumio but built on Arch instead.

 

[ifor]

No, I didn't download afresh. Will do! The card that gets nowhere at all is a Verbatim card. I'm not sure what the one I'm using is, but it was a cheap an slow one bought from Currys. I should probably go upmarket.

 

[ifor]

I posted on the Apple forums and I have been advised to rename the AirPort Extreme with an SMB compliant name. Currently it is called Ifor's AirPort Extreme, which is a typical Apple name, but aplenty is not SMB compliant. It has also been suggested that I might benefit from downgrading the firmware, because the latest version is buggy. Until I get home I'm not sure which version of the firmware I'm running.

 

[margetti]

Morning

Good to hear the link lights are all up - should rule out a hardware issue on the Pi thank goodness :clap: And it indicates we have a good physical connection which is encouraging.

Can't comment on the SMB thing re the AE - I would have have thought this wasn't the problem at this stage as SMB runs on top of TCP/IP, which we have yet to get working. But you just never know... and it could well be an issue later if you will be accessing your music from a shared drive on the network.

My current line of thinking is hte same as Dave's regarding the SD card - either the downloaded image is corrupt, or it is getting corrupted on the SD card. From what I have read, a poorly (or a poorly performing) SD card is responsible for a large number of Pi problems.

Another thing (yes, another!) to make note of the quality of the Pi's power supply. A poorly power supply is another contributor to Pi frustration... with phone chargers being the main culprit. It's not so much that they don't provide enough current (although that may be the case), but that the stability of the supply voltage can vary widely - something the Pi doesn't like. Anway, I digress, just putting it out there for geeky background information

 

[ifor]

Well I got home later than expected without a new SD card. I have established that one of cards is definitely rubbish and I am flashing the "good" one with a new Volumio download just now. I checked the LEDs before I shut the Pi down and the top green one (SD Card Access) was only occasionally lit. Should it be lit all the time? Also, the card is only class 4; does this matter? I have a class 10 card arriving tomorrow.

 

[margetti]

Not sure about the SD Card Access light tbh - my Pi is in a case and lights not visible so not easy to check immediately. Will have a look when i can.

The SD Class thing, from what I've read, is all a bit vague as what defines a "class" doesn't necessarily relate to how well it performs. But I'm probably confusing matters - in a nutshell, Class 4 is not good for the Pi and could very well explain the problems you've had.

Class 10 should be just the ticket!

 

[Dave_]

Pretty sure the SD light flashes when the card is being read/written too.

As for the class of card that's a can of worms.My advice just get a decent card and ignore the class.

There are a number of SD card recommendation/benchmark lists for the RPi being maintained if you do a search. (Posting from my phone, so too much faff to be finding/posting links)

 

[ifor]

There is no change with the card reflashed from the newly downloaded .img.

I've just shut it down again. It had the 10.0.0.102 IP address again, but Fing said the device was down, but again when I refreshed Fing just after it had shut down it said the device is up.

Tomorrow I'll try a new card and/or downgrading the firmware of and renaming the AirPort Extreme. I'll report back.