FireFly Media Server › Firefly Media Server Forums › Firefly Media Server › General Discussion › Newbie question about using firefly on Maxtor mss+
- This topic has 56 replies, 8 voices, and was last updated 17 years, 11 months ago by rpedde.
-
AuthorPosts
-
24/11/2006 at 11:38 PM #7454rpeddeParticipant
@Iris wrote:
Confiqure a STATIC IP for the MSS. I had read this is another post but hadn’t placed a lot of emphasis on it simply because from the MSS interface my network configuration was correct and the MSS was working. However, once I tried to execute > ipkg update and got a “Host” error. A static i.p. fixed that.
That shouldn’t have to be the case, but it’s probably something to recommend if people have the same errors as you get (can’t do ipkg update, etc).
The other thing was trying to use Nano after Telneting in from a DOS prompt – the display was all screwed. Thanks to Dean’s post I used PuTTY and that resolved the issue.
That’s good to know. I wasn’t aware of that.
So, perhaps these two suggestions can be incorporated into the tutorial for other individuals who use it.
will do.
[quote[
I do think I have a minor clean-up to do (maybe something I missed) but on the Roku the server displays as “firefly svn-1433 on (none)”. I thought the (none) was due to the fact in the FireFly configuration a name for the server hadn’t been specified (by default) but me entering a description there didn’t change anything. Is this editable?
[/quote]The server name only updates on next restart. So if you change the server name you’ll have to reboot or stop and start hte server.
I also will eventually disable/uninstall the FireFly server installed on my laptop – will have to look around for instructions on that or will simply using Add/Remove Programs under Windows suffice?
It *should*, but somewhere the uninstaller stopped working and left cruft. 🙁 If you run the uninstaller, delete the program filesfirefly media server, and that should do it.
P.S. Ron, perhaps I should delete some of my posts that weren’t really specific to the installation – do you mind?
Go crazy!
— Ron
26/11/2006 at 7:30 PM #7455deanmGuestRon
Just to close off from Thursdays post – no surprise but after installing mss-ld-so everything came together easy as… 😀
Can now power down my desktop thats been on 24-7 serving the Roku.
Great job……
Dean
27/11/2006 at 8:36 PM #7456RickVParticipantHi Ron,
Here I am on the firefly forums. I’m the same as user Rick on the Roku Forums but that username was occupied.
I started with the installation on the MSS with the wiki step-by-step guide.
I’m stuck with the command:
# LD_LIBRARY_PATH=/opt/lib /opt/bin/nano /opt/etc/init.d/S60mt-daapdThis results in the following error:
/opt/bin/nano: error while loading shared libraries: cannot open shared object file: cannot load shared object file: No such file or directoryI then started to think of my Unix experience 20 years ago and went to the /opt/bin-directory. A file called nano is mentioned when I do an LS, but running just the command nano from there gives a “nano: not found” and running ./nano gives the same error as the command mentioned in the wiki.
Thank you for your help
28/11/2006 at 1:52 AM #7457rpeddeParticipant@RickV wrote:
# LD_LIBRARY_PATH=/opt/lib /opt/bin/nano /opt/etc/init.d/S60mt-daapd
Two things to try:
/opt/lib/ld.so.1 /opt/bin/nano
and see what that does.
Failing that, do this:
#export LD_TRACE_LOADED_OBJECTS=1
#/opt/lib/ld.so.1 /opt/bin/nano
You should get a bunch of crap back. Paste that back here so we can see it.. it should be list of the libraries it’s trying to link with. That might give us a clue as to what’s missing.
— Ron
[/img]28/11/2006 at 5:15 PM #7458RickVParticipantCode:
/opt/lib/ld.so.1 /opt/bin/nano
This gives the following error:
/opt/bin/nano: error while loading shared libraries: libncursesw.so.5: cannot open shared object file: No such file or directoryCode:
#export LD_TRACE_LOADED_OBJECTS=1
#/opt/lib/ld.so.1 /opt/bin/nanoThis gives the following error:
libncursesw.so.5 => not found
libc.so.6 => /opt/lib/libc.so.6 (0x2ab00000)
/lib/ld.so.1 => /opt/lib/ld.so.1 (0x55580000)[/quote]29/11/2006 at 12:23 AM #7459rpeddeParticipant@RickV wrote:
Code:
/opt/lib/ld.so.1 /opt/bin/nano
This gives the following error:
/opt/bin/nano: error while loading shared libraries: libncursesw.so.5: cannot open shared object file: No such file or directoryLooks to be missing libncurses. Maybe “ipkg install ncurses”? It should have been dragged in by nano though. Not sure why it wasn’t. If it came from the unslung feed, it is marked as requiring curses.
Did you get any errors when you tried to install?
29/11/2006 at 4:41 PM #7460RickVParticipantHi Ron,
I first did the:
ipkg install ncursus
after that I tried:
ipkg install nano
Both didn’t solve the problem.
Below the output:# ipkg install ncursus
Nothing to be done
An error ocurred, return value: 4.
Collected errors:
Cannot find package ncursus.
Check the spelling or perhaps run ‘ipkg update’# ipkg install nano
Package nano (2.0.1-1) installed in root is up to date.
Nothing to be done30/11/2006 at 3:49 AM #7461rpeddeParticipant@RickV wrote:
# ipkg install ncursus
Nothing to be done
An error ocurred, return value: 4.
Collected errors:
Cannot find package ncursus.
Check the spelling or perhaps run ‘ipkg update’Was that really ncursUs or ncursEs?
What does:
cat /opt/etc/ipkg.conf
show?
30/11/2006 at 11:51 AM #7462RickVParticipantHi Ron,
I executed “ipkg install ncursus”, did a copy/paste from the telnet-session.
Right now I see that you told me to use “ncurses”. I will give it a try as soon as I am home. Also I will give you the “cat” output if the are still errors.30/11/2006 at 5:32 PM #7463RickVParticipantHi Ron,
Here I am again.
Here is what I executed including the messages I received:
# ipkg install ncurses
Package ncurses (5.5-1) installed in root is up to date.
Nothing to be done
#
# cat /opt/etc/ipkg.conf
src nslu2 http://ipkg-us-dyoung.nslu2-linux.org/feeds/optware/mss/cross/unstable
src firefly http://ipkg.fireflymediaserver.org/mipsel
#
#Thank you for all the effort you putting into this.
-
AuthorPosts
- The forum ‘General Discussion’ is closed to new topics and replies.