Django, looks like you are on the money Many thanks, I am not
using fake macs, removed the section for the suspect pi in the
server.prefs and bingo it works, very pleased.
I assume at sometime I (or one of my kids!) has been in and started
playing with the settings on the player and
alastaid wrote:
> OK, so I maybe wrong with the term "firmware", but I ran the rpi-update
> as per here: http://www.devils-heaven.com/raspberry-pi-firmware-update/
>
> which did appear, at least, to be doing something on the board as
> opposed to the card, but I could be wrong, I cant even
OK, so I maybe wrong with the term "firmware", but I ran the rpi-update
as per here: http://www.devils-heaven.com/raspberry-pi-firmware-update/
which did appear, at least, to be doing something on the board as
opposed to the card, but I could be wrong, I cant even find out where I
read that
Greg Erskine wrote:
> I don't. I wanted you to confirm it can't be upgraded and ALL "user
> accessible" software is on the SD card? Yes?
Not quite. See my previous reply about "raspberrypi-bootloader".
> Yes you are right, I agree. I stopped playing with PCs 15 years ago and
> have forgotten
alastaid wrote:
> OK, so I maybe wrong with the term "firmware", but I ran the rpi-update
> as per here: http://www.devils-heaven.com/raspberry-pi-firmware-update/
>
> which did appear, at least, to be doing something on the board as
> opposed to the card, but I could be wrong, I cant even
Jeff07971 wrote:
> I don't think this is doing what you think it does
> This appears to be updating firmware files on the Raspian (Debian)
> system.
> These firmwares are pushed to certain devices which need them when
> connected.
>
> Actually just looked into this a bit further, they are
Julf wrote:
> Yes, the first stage bootloader firmware is update-able, but usually
> there is little need to do it unless you need to boot from exotic
> hardware or directly over the net.
No it's not. It is in embedded rom.
utgg wrote:
> No it's not. It is in embedded rom.
Yes and no. The RPi designers did quite some cost-cutting measures. The
first-stage bootloader, in RPi terminology, is indeed in ROM, and can't
be updated, but the only thing that that code can do is load the second
stage (bootcode.bin) from the
d6jg wrote:
> There is firmware on a Pi - it is the equivalent to a PCs BIOS - why its
> called firmware and not BIOS I am not sure.
Because "firmware" is the generic term for semi-permanently installed
control software held in non-volatile memory. One specific kind of
firmware is a boot loader
Greg Erskine wrote:
> The point I am trying to make is there is no firmware/boot software on
> the actual Raspberry Pi PCB itself, it is all loaded from the SD card
> when booting.
No, there is a first stage boot loader in ROM. It is needed to load
software from the SD card.
> When I was a
alastaid wrote:
> So this eliminates the SD card, OS, switch port, Ethernet cable, no DAC
> used, only leaves the pi?
Depends on how do you use squeezelite..
If you dont use a fake mac address for the squeezeliteplayer some
strange playersettings in your lms may also involved.
Do you use a
Julf wrote:
> Why would you need to do that? All it does is load the second stage boot
> program from SD..
I don't. I wanted you to confirm it can't be upgraded and ALL "user
accessible" software is on the SD card? Yes?
> "Proper" computers are a different thing (I see the raspberry pi as an
>
Julf wrote:
> No, there is a first stage boot loader in ROM. It is needed to load
> software from the SD card.
Yes, there must be some minimal code to get things started. How do you
update the first stage boot loader?
> These days non-volatile RAM is mostly flash memory, not (battery- or
>
Greg Erskine wrote:
> Yes, there must be some minimal code to get things started. How do you
> update the first stage boot loader?
Why would you need to do that? All it does is load the second stage boot
program from SD.
> Good. I am going to remove all those batteries and super caps from my
>
alastaid wrote:
> Whilst I have been thinking about it, when I started building my rig, I
> do remember one of the blog posts saying I should upgrade the firmware
> of the pi, and to be honest I cannot remember if I did them all, so I
> will go through this proves on the non working one, see if
Sorry for not being clear, to try and eliminate as much as I could, I
have two identical Pi's, the working one and non working one, no DAC
just using the headphone for testing, same SD card. So try it in the
working pi all fine, then swap the same sd card to the non working pi,
use the same
There is firmware on a Pi - it is the equivalent to a PCs BIOS - why its
called firmware and not BIOS I am not sure.
*Vortexbox LMS 7.8 music on QNAP TS419p via NFS* iThingys/iPeng/Tablets
*Living Room* - SB3 -> Onkyo TS606 - > Celestion Ditton F20s - Zone 2 ->
Sony TA FE 320 -> Sennheiser RS
d6jg wrote:
> There is firmware on a Pi - it is the equivalent to a PCs BIOS - why its
> called firmware and not BIOS I am not sure.
The point I am trying to make is no firmware/boot software on the actual
Raspberry Pi PCB itself, it is all loaded from the SD card.
If I understand correctly,
alastaid wrote:
> I just swapped the sd card into another pi with the same network cable
> and power supply (just using the headphone socket to eliminate the DAC),
> and it worked perfectly. It has to be the pi surely?
May i didnt understand what you've done:confused:
Did you change two RPi
Are you using a USB DAC on the non working Pi? I can't see the DAC type
mentioned before.
The Pi Ethernet port & USB do share the same bus and it is known to
cause problems with certain hardware.
*Vortexbox LMS 7.8 music on QNAP TS419p via NFS* iThingys/iPeng/Tablets
*Living Room* - SB3 ->
Hi,
New to all of this and very pleased with where I have got to so far.
So, have a multi room setup using LMS 7.9, I have 6 clients running on
Pi B+ all work fine except one, which pauses the playback roughly for
about 10 seconds every two or three minutes (but can vary). I have
changed all
alastaid wrote:
> Hi,
>
> New to all of this and very pleased with where I have got to so far.
> So, have a multi room setup using LMS 7.9, I have 6 clients running on
> Pi B+ all work fine except one, which pauses the playback roughly for
> about 10 seconds every two or three minutes (but
Hi & welcome
change the power source from the one that always fails to another (from
another Pi that didnt fails)
>
> Have I got it right that the pi loses network connectivity, and if so,
> have I got a faulty pi as I cant think what else to try?
Can you ping /ssh to it when it fails playing?
Look at interface TCP and IP statistics to see if there is a burst of
errors/retries or retransmissions.
Faulty connector etc can cause intermittent errors.
Try a USB ethernet (or even wifi) adaptor to eliminate the onboard
Ethernet part of the Pi.
Hi,
Thanks for the quick responses, so I have swapped with known good power
supplies, and no change. It does move around with the specific pi
board.
Tried it again, with a continuous ping from another machine, and the
player stopped playing, but the ping stayed perfect and consistent in
alastaid wrote:
> Hi,
>
> Thanks for the quick responses, so I have swapped with known good power
> supplies, and no change. It does move around with the specific pi
> board.
>
> Tried it again, with a continuous ping from another machine, and the
> player stopped playing, but the ping
Ok,
Started on the logging front.
slimproto had nothing
stream had the following:
[15:49:15.497148] stream_thread:249 end of stream
[15:51:39.440958] stream_sock:384 connecting to 192.168.2.11:80
[15:51:39.443271] stream_sock:413 header: GET
/stream.mp3?player=b8:27:eb:8c:54:c8 HTTP/1.0
Do you ping from the sever ?
Main hifi: Touch + CIA PS +MeridianG68J MeridianHD621 MeridianG98DH 2 x
MeridianDSP5200 MeridianDSP5200HC 2 xMeridianDSP3100 +Rel Stadium 3
sub.
Bedroom/Office: Boom
Kitchen: Touch + powered
No it was another machine, but will try from the server
alastaid's Profile: http://forums.slimdevices.com/member.php?userid=65063
View this thread: http://forums.slimdevices.com/showthread.php?t=104698
alastaid wrote:
> It looks like it just looses contact with the server stream? Yet you
> can ping it continuously with no error during the "dropout"
If it loses contatc then another GET would be issued - is there a second
GET ?
Otherwise it is LMS that has stopped sending ?
Possibilties are
just tried pinging it from the server, and it pings fine, starting to
think I should just send the pi back, as to test my sanity, I just
swapped the sd card into another pi with the same network cable and
power supply (just using the headphone socket to eliminate the DAC), and
it worked
alastaid wrote:
> just tried pinging it from the server, and it pings fine, starting to
> think I should just send the pi back, as to test my sanity, I just
> swapped the sd card into another pi with the same network cable and
> power supply (just using the headphone socket to eliminate the
bpa wrote:
> I've seen a network interface (not on a pi) which had problem with large
> packets (CRC errors) yet received small "ping type" packets OK (bad
> clock h/w got out of sync with data if network frame was large) - that
> is why wireshark would be definitive but using another network
33 matches
Mail list logo
