Troubleshooting a Failed TwonkyMedia Installation

Sorry to see you here. Since both of my recipes work for me I'll have to write this from memory, which like bad dreams become vague memories quickly.

I assume you came here because you typed http://192.168.1.77:9000, waited a long while, and did not see the TwonkyMedia GUI.

• Did you enter Gateway and DNS addresses on the NSLU2's LAN configuration page?
• If so, is it connected to a LAN that has Internet access?
• Those fields should be blank if your NSLU2 has no Internet access.

Assuming the preceding didn't help, the next step is to telnet into the NSLU2 and see if TwonkyMedia is running.

• Assuming your browser is still open, click  Home  (or open a browser and go to 192.168.1.77)
• Click  Administration .
• Enter admin for both user name and password.
• Click in the browser’s Address field and change it to read: http://192.168.1.77/Management/telent.cgi
• “Go” there.

• A very simple screen will appear with an  Enable Telnet  button. Click the button and wait a few seconds until it changes to read  Disable Telnet .
• Open a Windows Command Prompt (aka. “DOS box”).
• At the prompt type telnet 192.168.1.77 and press Enter.

• The NSLU2 will respond with “NAS login:”
• Type root and press Enter.
• The NSLU2 will respond with “Password:”
• Type uNSLUng, capitalized exactly as shown, and press Enter.
• You’ll see the following screen.

• Enter the command help and you’ll see a list of commands. If you cannot get the NSLU2 to respond to the telnet command see this page.

In the instructions that follow, after typing the text shown in blue always press the Enter key.

• Type the following (P S space minus A L, in lower case): ps -al

In the long list of running processes do you see TwonkyMedia listed as in this screen capture?

If you do see it listed, then it's running so perhaps you mistyped 192.168.1.77:9000 in your browser when you tried to access its GUI. Have you tried Cidero to see if it shows up as a UPnP server? Beyond this suggestion, post your situation to the TwonkyVision forum.

If you don't see the TwonkyMedia process, then it didn't run automatically when the NSLU2 booted. You did reboot the NSLU2 after installing TwonkyMedia, didn't you?

Let's see if it's in the proper directory.

• Type the following (L S space minus L, in lower case): ls -l /opt

Do you see it listed as shown in this screen capture?

If not, then it didn't get installed properly. If yours was a hard drive installation, I'd try the above command but change it slightly to read: ls -l /share/hdd/data/opt. Do you see it then? My understanding is a bit hazy in this area but you can at least post to the TwonkyVision forum more detail about where TwonkyMedia's files are located. With a hard drive installation it's my impression that listing the /opt directory should yield the same results as listing /share/hdd/data/opt.

If you do see it listed in the /opt directory, let's verify if its startup script is in the right location.

• Type the following (L S space minus L, in lower case): ls -l /opt/etc/init.d
• If yours was a hard drive installation, do you see "S99twonky"?
• If yours was a RAM installation, do you see "S99mediaserver"?

If not, the startup script isn't there so I'd try reinstalling TwonkyMedia or post your situation to the TwonkyVision forum.

But if the startup script is present, let's try running it manually.

• If yours was a hard drive installation, type the following: /opt/etc/init.d/S99twonky
• If yours was a RAM installation, type the following: /opt/etc/init.d/S99mediaserver

Does telnet respond with TwonkyMedia Version 3.1?

If it does, then it's running. You can repeat the "ps -al" command you tried earlier to see if its process is now listed, or try accessing its GUI by going to 192.168.1.77:9000 in your browser. The diagnosis at this point is that it's installed properly but is not automatically running upon NSLU2 bootup.

If you don't see the above response, and you're sure the startup script's filename is identical to one of the above, post your situation to the TwonkyVision forum.

This is about all the troubleshooting hints I can suggest at this time. Maybe more will occur to me or we'll see some additional tips in the TwonkyVision forum.

Before closing, let's exit Telnet and disable it in the browser.

• In the telnet window type Exit and press Enter. Close the Command Prompt window.
• Switch to the browser and click on the  Disable Telnet  button.
• Edit the browser's Address field to just read: http://192.168.1.77
• “Go” there.
• Click  Administration .
• Click  Status .
• Click  Shutdown Now .

One more suggestion: you can always restore the original Linksys firmware and start over. Or, instead of going back that far you can just re-flash the NSLU2 with uNSLUng. In the process of writing and testing these recipes I've done the latter plenty of times. (I usually reformat the hard drive, too, to ensure a clean slate. And, incidentally, I've found that despite warnings against reformatting an already-NSLU2-formatted drive, reformatting works fine.)

 

To re-flash uNSLUng follow the Restore Firmware instructions, but instead of using the Linksys .bin file use the uNSLUng .bin file.

Good luck!

Top