I have installed Slimrio, and it will not connect to my Slimserver.

Wireshark tells me it is trying to connect to udp port 18678, rather than the slimp3 broadcast for a server address I would expect.

Slimrio appears to have booted correctly - the console screen says "No connection to slimserver".

Any ideas? Am I missing something obvious?

Cheers

Tim

I'm making no progress on this, in spite of having spent several hours investigating :-(

Slight correction to the symptoms - once booted, the device sends no packets - it is the Audio Manager software that is trying to connect on udp 18678.

Telnetting to port 5000 gets rather random results - sometimes the chars echo, sometimes not, and I can't get the simplest of commands (e.g. ls or pwd) to run. This leads me to believe that slimrio simply isn't working properly, unless I am doing something wrong? Has anyone used the port 5000 interface? Do you need to do anything special to make it work?

Cheers

Tim

PS I have tested it using the original Rio software - works perfectly

If it's getting to the "No connection" screen, you've already done all the hard work since we know the networking is up and able to run NFS. At that point, slimrio will be repeatedly sending out UDP broadcasts to port 3483; I can't imagine why you wouldn't see them unless perhaps there's some funny switch or firewall in the way.

Were you connecting to port 5000 from the same machine that served it the NFS image? If not, give that a try. Can you ping it from there?

What are you using to give it a DHCP address? Could it have been given the same address as another host on the network?

I've used telnet---but nc (netcat) is safer because it doesn't try to do any fancy quoting or negotiation like telnet can.

Thanks very much for the response Robin.

I am making some progress, but it still doesn't work :-(

I have tried simplfying the network (Windows Server 2003 (dhcp, audio receiver manager, wireshark), ddar, hub) - no improvement.

Tried using nc instead of telnet, and I can now get a sensible console session.

Killing slimrio and restarting with -v gets the message:

=> sending discovery request
sendto: Network is unreachable

Repeating with the -s flag and the ip of the slimserver gets:

=> sending discovery request
<= discovery response from <ip address>
No connection to slimserver

Wireshark shows the discovery requests & responses.

I'm baffled; so much works, yet it doesn't work!

Can you suggest any diagnostics I could do now I have a console session?

In particular how can I check the network configuration - I see busybox doesn't have ifconfig?

Thanks in advance.

Cheers

Tim

I have now got a full boot log (posted below) - again pretty baffling, it all looks clean, no error messages to speak of. The only thing I don't like is the gw=ffffffff line(s).

Is anyone in a position to compare it with a working log?

Cheers

Tim

empeg-net v1.01 20000710 (hugo@empeg.com)
If there is anyone present who wants to upgrade the flash, let them speak now,
or forever hold their peace...it seems not. Let fly the Penguins of Linux!

Clearing 4Mb of RAM...
Copying kernel...
Calling linux kernel...
Uncompressing Linux............................. done, booting the kernel.

boot no options
Linux version 2.2.14-rmk4-mercury17-v1.01 (altman@alisha.internal.empeg.com)
(gcc version 2.95.2 19991024 (release)) #73 Fri Jul 14 17:37:29 BST 2000
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
Calibrating delay loop... 65.33 BogoMIPS
Memory: 3116k/4M available (752k code, 20k reserved, 200k data, 8k init)
Dentry hash table entries: 512 (order 0, 4k)
Buffer cache hash table entries: 2048 (order 1, 8k)
Page cache hash table entries: 1024 (order 0, 4k)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0 for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
TCP: Hash tables configured (ehash 4096 bhash 4096)
Starting kswapd v 1.5
empeg clps7212 audio driver initialized
mercury display initialised.
mercury infra-red support initialised.
mercury rotary support initialised.
mercury buttons support initialised.
Probing for cs8900a
eth0: cs8900 rev J found at 0x300 media RJ-45, IRQ 7 00 90 00 11 4c 01
IP-Config: Entered.
eth0: using 10Base-T (RJ-45)
IP-Config: Opened eth0 (able=28)
DHCP: XID=57f3b1bb
Sending DHCP / UPnP requests...IP-Config: UPnP trying address 169.254.207.17
DHCP: Got extension 35 02
DHCP: Got extension 01 ff ff ff 00
DHCP: Got extension 3a 00 02 a3 00
DHCP: Got extension 3b 00 04 9d 40
DHCP: Got extension 33 00 05 46 00
DHCP: Got extension 36 c0 a8 00 0e
DHCP: Gateway is ffffffff
. OK
DHCP lease time (d:hh:mm) 4:00:00
IP-Config: Got DHCP answer from 192.168.0.14, my address is 192.168.0.111
Sending SSDP requests....SSDP: NFS server at 192.168.0.11:21076
OK
IP-Config: device=eth0, local=6f00a8c0, server=0b00a8c0, boot=0b00a8c0, gw=ffffffff, mask=00ffffff
IP-Config: host=192.168.0.111, domain=(none), path=`'
Looking up port of RPC 100003/2 on 192.168.0.11
Looking up port of RPC 100005/1 on 192.168.0.11
VFS: Mounted root (NFS filesystem) readonly.
Freeing unused kernel memory: 8k init
Bootstrap code size 348
Found kernel image "/zImage", size: 380620
Loading kernel image at virt c0180000... loaded
Found pna driver image "/il-binary.o", size: 0
Loading pna module image at virt c03e0000... loaded
Command line: "ip=192.168.0.111:192.168.0.11:21076::255.255.255.0:::off loadmodule=0xc03e0000"
Copying bootstrap code...
Calling architecture bootstrap loader...
c0180000 0005cecc c01de000 c01dd000
Uncompressing Linux........................... done, booting the kernel.

boot no options
Linux version 2.2.14-rmk4-mercury19 (robin@victoria)
(gcc version 3.4.2 (release) (CodeSourcery ARM Q3D 2004)) #1 Mon Jul 16 17:37:22 BST 2007
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
IP-Config: Parameter #0: `192.168.0.111'
IP-Config: Parameter #1: `192.168.0.11'
IP-Config: Parameter #2: `21076'
IP-Config: Parameter #4: `255.255.255.0'
IP-Config: Parameter #7: `off'
Calibrating delay loop... 65.33 BogoMIPS
Memory: 3156k/4M available (712k code, 20k reserved, 200k data, 8k init)
Dentry hash table entries: 512 (order 0, 4k)
Buffer cache hash table entries: 2048 (order 1, 8k)
Page cache hash table entries: 1024 (order 0, 4k)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0 for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
TCP: Hash tables configured (ehash 4096 bhash 4096)
Starting kswapd v 1.5
empeg clps7212 audio driver initialized
mercury display initialised.
mercury infra-red support initialised.
mercury rotary support initialised.
mercury buttons support initialised.
Probing for cs8900a
eth0: cs8900 rev J found at 0x300 media RJ-45, IRQ 7 00 90 00 11 4c 01
IP-Config: Entered.
eth0: using 10Base-T (RJ-45)
IP-Config: Opened eth0 (able=0)
IP-Config: device=eth0, local=6f00a8c0, server=0b00a8c0, boot=0b00a8c0, gw=ffffffff, mask=00ffffff
IP-Config: host=192.168.0.111, domain=(none), path=`'
Looking up port of RPC 100003/2 on 192.168.0.11
Looking up port of RPC 100005/1 on 192.168.0.11
VFS: Mounted root (NFS filesystem) readonly.
Freeing unused kernel memory: 8k init
init (1): unsupported llseek call standard
init (1): unsupported llseek call standard
sendto: Network is unreachable

No connection to slimserver
sendto: Network is unreachable

No connection to slimserver
sendto: Network is unreachable

No connection to slimserver
sendto: Network is unreachable

Not me. But you're right that gw=ffffffff looks wrong. Check your DHCP server configuration on host 192.168.0.14 -- is it handing out a bogus gateway address?

Peter

Just what I've been checking. It has option 003 (Router), and it is set to exactly what you would expect - 192.168.0.1

:-(

I've solved this.

Turns out to be a combination of "features" of the DHCP code in the server and the client. The client includes a Vendor Class (empeg:mercury) in the DHCP request. The server (Windows Server 2003) returns a DHCP lease _without_ including option 3, (router / default gateway - I assume it does this because of the presence of a Vendor Class - it shouldn't do according to the specs, but it does). The client, not receiving the expected option 3, uses the really useful default of 0xffffffff. When Slimrio loads, this default causes the IP stack to crash.

Now all I need to do is knock up a utility to provide the correct DHCP response, and coexist with my current DHCP setup and I'll be laughing.

Cheers

Tim

Working boot log for reference - may help someone else out.

empeg-net v1.01 20000710 (hugo@empeg.com)
If there is anyone present who wants to upgrade the flash, let them speak now,
or forever hold their peace...it seems not. Let fly the Penguins of Linux!

Clearing 4Mb of RAM...
Copying kernel...
Calling linux kernel...
Uncompressing Linux............................. done, booting the kernel.

boot no options
Linux version 2.2.14-rmk4-mercury17-v1.01 (altman@alisha.internal.empeg.com)
(gcc version 2.95.2 19991024 (release)) #73 Fri Jul 14 17:37:29 BST 2000
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
Calibrating delay loop... 65.33 BogoMIPS
Memory: 3116k/4M available (752k code, 20k reserved, 200k data, 8k init)
Dentry hash table entries: 512 (order 0, 4k)
Buffer cache hash table entries: 2048 (order 1, 8k)
Page cache hash table entries: 1024 (order 0, 4k)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0 for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
TCP: Hash tables configured (ehash 4096 bhash 4096)
Starting kswapd v 1.5
empeg clps7212 audio driver initialized
mercury display initialised.
mercury infra-red support initialised.
mercury rotary support initialised.
mercury buttons support initialised.
Probing for cs8900a
eth0: cs8900 rev J found at 0x300 media RJ-45, IRQ 7 00 90 00 11 4c 01
IP-Config: Entered.
eth0: using 10Base-T (RJ-45)
IP-Config: Opened eth0 (able=28)
DHCP: XID=42043489
Sending DHCP / UPnP requests...IP-Config: UPnP trying address 169.254.75.185
....
DHCP: Got extension 35 02
DHCP: Got extension 01 ff ff ff 00
DHCP: Got extension 03 c0 a8 00 0b
DHCP: Got extension 0c 6d 65 72 63 75 72 79 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00
DHCP: Got extension 11 2f 65 78 70 6f 72 74 2f 6d 65 72 63 75 72 79 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00
DHCP: Got extension 33 ff ff ff ff
DHCP: Got extension 3a ff ff ff ff
DHCP: Got extension 3b ff ff ff ff
DHCP: Gateway is 0b00a8c0
OK
DHCP lease time (d:hh:mm) 49710:06:28
IP-Config: Got DHCP answer from 192.168.0.11, my address is 192.168.0.111
Sending SSDP requests....IP-Config: ARP request from 00:03:47:b1:3a:07 (192.168.0.11)
SSDP: NFS server at 192.168.0.11:21076
OK
IP-Config: device=eth0, local=6f00a8c0, server=0b00a8c0, boot=0b00a8c0, gw=0b00a8c0, mask=00ffffff
IP-Config: host=mercury, domain=(none), path=`/export/mercury'
Looking up port of RPC 100003/2 on 192.168.0.11
Looking up port of RPC 100005/1 on 192.168.0.11
VFS: Mounted root (NFS filesystem) readonly.
Freeing unused kernel memory: 8k init
Bootstrap code size 348
Found kernel image "/zImage", size: 380620
Loading kernel image at virt c0180000... loaded
Found pna driver image "/il-binary.o", size: 0
Loading pna module image at virt c03e0000... loaded
Command line: "ip=192.168.0.111:192.168.0.11:21076:192.168.0.11:255.255.255.0:mercury::off loadmodule=0xc03e0000"
Copying bootstrap code...
Calling architecture bootstrap loader...
c0180000 0005cecc c01de000 c01dd000
Uncompressing Linux........................... done, booting the kernel.

boot no options
Linux version 2.2.14-rmk4-mercury19 (robin@victoria)
(gcc version 3.4.2 (release) (CodeSourcery ARM Q3D 2004)) #1 Mon Jul 16 17:37:22 BST 2007
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
IP-Config: Parameter #0: `192.168.0.111'
IP-Config: Parameter #1: `192.168.0.11'
IP-Config: Parameter #2: `21076'
IP-Config: Parameter #3: `192.168.0.11'
IP-Config: Parameter #4: `255.255.255.0'
IP-Config: Parameter #5: `mercury'
IP-Config: Parameter #7: `off'
Calibrating delay loop... 65.33 BogoMIPS
Memory: 3156k/4M available (712k code, 20k reserved, 200k data, 8k init)
Dentry hash table entries: 512 (order 0, 4k)
Buffer cache hash table entries: 2048 (order 1, 8k)
Page cache hash table entries: 1024 (order 0, 4k)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0 for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
TCP: Hash tables configured (ehash 4096 bhash 4096)
Starting kswapd v 1.5
empeg clps7212 audio driver initialized
mercury display initialised.
mercury infra-red support initialised.
mercury rotary support initialised.
mercury buttons support initialised.
Probing for cs8900a
eth0: cs8900 rev J found at 0x300 media RJ-45, IRQ 7 00 90 00 11 4c 01
IP-Config: Entered.
eth0: using 10Base-T (RJ-45)
IP-Config: Opened eth0 (able=0)
IP-Config: device=eth0, local=6f00a8c0, server=0b00a8c0, boot=0b00a8c0, gw=0b00a8c0, mask=00ffffff
IP-Config: host=mercury, domain=(none), path=`'
Looking up port of RPC 100003/2 on 192.168.0.11
Looking up port of RPC 100005/1 on 192.168.0.11
VFS: Mounted root (NFS filesystem) readonly.
Freeing unused kernel memory: 8k init
init (1): unsupported llseek call standard
init (1): unsupported llseek call standard
madplay (13): unsupported llseek call standard
madplay (13): unsupported llseek call standard
madplay.real (13): unsupported llseek call standard
madplay (14): unsupported llseek call standard
madplay (14): unsupported llseek call standard
madplay.real (14): unsupported llseek call standard

A Windows server doesn't operate according to standards?!? Say it ain't so!

Heh, yeah. But it was nice sleuthing work on his part.