I had my first receiver running on Jeff's excellent interface under Mandrake Linux 9.0. When it started making squealing noises from the power supply I returned it for a new one. Now my second Receiver is not working with Jeff's interface. I have lots of troubleshooting notes if anyone would like to delve into intracacies on RIO communication protocols and suggest anything for me to try.. here is a long summary...

Problem: RIO boots and hangs at 'Please Wait, Found Music Server".

Static IP vis DHCP... 10.0.0.251
Server is at 10.0.0.5
Interface Lisening at 10.0.0.5:80 Apache 1.3
I can successfuly build and dump the database via the interface.

Via logs I can tell the following...

21075 UDP Server Notes:

I had to modify the unique string that the server looks for the RIO to send. Jeff had the value

upnp:uuid:1D274DB1-F053-11d3-BF72-0050DA689B2F

but my RIO sends (difference at end)

upnp:uuid:1D274DB1-F053-11d3-BF72-0050DA689B3000

That is all fine as I have it fixed but this brings up the issue... are there different batches of RIO's out there that have different firmware? Do I have an old or new copy? Is this updatable? I did not see any answers to these in the FAQ (I hope I didn't miss them at least).

Anyway, I changed my code in ssdp.pl to look for the correct string and the RIO seems to contine by mounting the NFS share...

NFS Server Info:

My syslog shows the following data (forgive me if it is munged).. you can see the ssdp.pl server start. The initial RIO 21075 request, then the NFS mount, And then nothing...

Feb 27 18:21:55 rex SSDP: SSDP server started
Feb 27 18:22:02 rex SSDP: Receiving Data from 10.0.0.251 - upnp:uuid:1D274DB1-F053-11d3-BF72-0050DA689B3000:90:00:11:32:aa
Feb 27 18:22:02 rex SSDP: Linux request from 10.0.0.251.
Feb 27 18:22:02 rex rpc.mountd: authenticated mount request from 10.0.0.251:800 for /tftpboot/10.0.0.251 (/tftpboot)
Feb 27 18:22:06 rex rpc.mountd: authenticated mount request from 10.0.0.251:800 for /tftpboot/10.0.0.251 (/tftpboot)

Also, using tcpdump to look closer at the NFS I have...

18:31:07.945952 10.0.0.251.52428800 > rex.askey.org.nfs: 104 getattr fh Unknown/1
18:31:07.946054 rex.askey.org.nfs > 10.0.0.251.52428800: reply ok 96 getattr DIR 40777 ids 0/0 sz 4096 (DF)
18:31:07.955017 10.0.0.251.69206016 > rex.askey.org.nfs: 112 lookup fh Unknown/1 "dev"
18:31:07.955130 rex.askey.org.nfs > 10.0.0.251.69206016: reply ok 128 lookup fh Unknown/1 (DF)
18:31:07.956493 10.0.0.251.85983232 > rex.askey.org.nfs: 116 lookup fh Unknown/1 "console"
18:31:07.956601 rex.askey.org.nfs > 10.0.0.251.85983232: reply ok 128 lookup fh Unknown/1 (DF)
18:31:07.964128 10.0.0.251.102760448 > rex.askey.org.nfs: 116 lookup fh Unknown/1 "zImage"
18:31:07.964255 rex.askey.org.nfs > 10.0.0.251.102760448: reply ok 128 lookup fh Unknown/1 (DF)
<--- continuation 4K blocks of zImage reads clipped --->
18:31:08.404630 10.0.0.251.1629487104 > rex.askey.org.nfs: 120 lookup fh Unknown/1 "il-binary.o"
18:31:08.404744 rex.askey.org.nfs > 10.0.0.251.1629487104: reply ok 128 lookup fh Unknown/1 (DF)
<--- continuation 4K blocks of il-binary.o reads clipped --->
18:31:11.831664 10.0.0.251.52428800 > rex.askey.org.nfs: 104 getattr fh Unknown/1
18:31:11.831767 rex.askey.org.nfs > 10.0.0.251.52428800: reply ok 96 getattr DIR 40777 ids 0/0 sz 4096 (DF)
18:31:11.840795 10.0.0.251.69206016 > rex.askey.org.nfs: 112 lookup fh Unknown/1 "dev"
18:31:11.840981 rex.askey.org.nfs > 10.0.0.251.69206016: reply ok 128 lookup fh Unknown/1 (DF)
18:31:11.842353 10.0.0.251.85983232 > rex.askey.org.nfs: 116 lookup fh Unknown/1 "console"
18:31:11.842464 rex.askey.org.nfs > 10.0.0.251.85983232: reply ok 128 lookup fh Unknown/1 (DF)
18:31:11.847937 10.0.0.251.102760448 > rex.askey.org.nfs: 112 lookup fh Unknown/1 "sbin"
18:31:11.848043 rex.askey.org.nfs > 10.0.0.251.102760448: reply ok 128 lookup fh Unknown/1 (DF)
18:31:11.849408 10.0.0.251.119537664 > rex.askey.org.nfs: 112 lookup fh Unknown/1 "init"
18:31:11.849515 rex.askey.org.nfs > 10.0.0.251.119537664: reply ok 128 lookup fh Unknown/1 (DF)
<--- continuation 4K blocks of init reads clipped --->

The last file read via NFS is the init executable but it does not seem to be executed as that should then go back out to the UDP server to get the host IP and port for the web interface. This NFS read is the last network activity that I get from the RIO.

Okay, thats it... anyone have a suggestion that may point me in the right direction? I appreciate any feedback. Thank you...

There is a different rom in the rebranded (SONICblue sticker) receivers. The *only* difference is the logo shown on the screen and the uuid in the NFS server location broadcast; this is to allow it to only boot from updated servers which will serve them a second kernel that doesn't show "Dell" either.

If you've fixed the uuid and are still having problems, I suspect it's not the unit. There's no point upgrading older units as it doesn't actually add anything new.

Hugo

My old Rio was a SonicBlue and so is the new one. None were Dell's so that shouldn't be the problem. Im trying 1.03 and 1.04 to see if that makes a difference

After reading some similar threads I can say this about my RR process..

1. My /tftpboot dir is configured with (no_root_squash) and all files are at 775.
2. Looking at the NFS accesses, the player reads /sbin/init last and then stops. It never makes it to the player executable.
3. The RR is frozen at 'Please Wait, Found Music Server'