You are here: Home » Topic » Problem setting up firefly on NSLU2

Problem setting up firefly on NSLU2

This topic contains 9 replies, has 4 voices, and was last updated by  Anonymous 9 years, 5 months ago.

Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • #2398

    Anonymous

    Im running a NSLU2 with a 320GB Toshiba HDD. My PC is running Windows Vista SP1. I am trying to set this up to connect to a SB M1001.

    I have been able to see the HDD and format it. I have flashed with Beta 6.8 and as far as I can see its working. When i try to login to 192.168.0.77 to start mt-daapd via telnet using the admin account i get


    NOTE: RUNNING FROM INTERNAL FLASH



    This system is currently running from the internal flash memory,
    it has NOT booted up into “unslung” mode from an external drive.

    In this mode, very few services are running, and available disk
    space is extremely limited. This mode is normally only used
    for initial installation, and system maintenance and recovery.
    Cannot execute /dev/null: Permission denied

    anyone know how to get round this?

    Thanks,
    Conor

    #16885

    Anonymous

    I just did this …

    Check out http://wiki.fireflymediaserver.org/NSLU2_Installation … especially the section under “Flashing and Unslinging”. You have to use the steps in the README that comes with the 6.8 beta archive to “unsling” the operating system so it boots from the harddrive.

    Use that Wiki and the links it provides to other sources, and you’ll get it going. It took me quite a while, so you do need patience!

    #16886

    Anonymous

    Okay have gone through all that and now i can see the device on my SB. I just cant see any of the music I put on there.

    The music folder is set to /share/hdd/data/public/mp3 but if i browse to my HDD via windows its in a folder called My Music.

    Can you help me on this one?

    TIA,

    Conor

    #16887

    Anonymous

    I had a lot of trouble at this point, and ended up changing the folder structure on the drive attached to the NSLU2. I had just copied the iTunes folder structure over, complete with sub folders for each artist, which was a mistake. I found I had to have all the mp3 files in a single folder (at least, that was the way I got it working).

    Anyway, the default path you show is for a drive plugged into usb port 2. If you have it plugged into port 1, as I have, you need to change the “hdd” in the path to “flash” in the Firefly configuration file.

    The “share/hdd/data/public/” portion of the path won’t be seen in Windows. Are you seeing just the folder “My Music”? I’m not sure if the OS on the NSLU2 can work with spaces in the folder names (it could be that it does … I just don’t know). I was seeing the share name (creatively named the “NSLU2”) and the folder … //NSLU2/iTunes … in my set up.

    To fix my set up errors, I went into the NSLU2 config program (192.168.1.77) and created a share named “music”. When I mapped this folder as a drive, Windows saw it as //NSLU2/music.

    I deleted all the files in the iTunes folder on the NSLU2 to save space, and then deleted that share, leaving only my “music” share. I copied over all the files in different folders on my Windows machine to the NSLU2 “music” folder (“Agent Ransack”, a freeware search program, made this easy without having to go into each folder in Windows and copy it over).

    The final step was to configure the Firefly config file on the NSLU2 to reflect my new path. What appeared as “//NSLU2/music” on my Windows computer was really “share/flash/data/public/music”.

    I couldn’t access the config file by using “192.168.1.77:3698” for some reason. I had to edit the config file using Telnet (the instructions for that are at http://wiki.fireflymediaserver.org/NSLU2_Installation near the bottom … I have to admit I installed the PICO editor after failing to be able to do it using the VI editor included with the unslung distro). Once I edited the line correctly, I was able to also open the config file in my browser.

    I think this is correct … I’m working remotely right now, so I may have some of the steps wrong. I’ll check when I get home tonight to make sure.

    #16888

    Anonymous

    Okay i have figured out how to get to the config file and I think i found the line that points to the music location. Oh and i mapped directly to the slug and not to the ip address of the slug. Is this right?

    How do I then edit the line mp3_dir = /share/hdd/data/?

    I have tried changing this through the web admin but I keep getting

    Error: 500general:mp3_dir

    If you used PICO how do you install it and is it easier to use?

    #16889

    sonichouse
    Participant

    @conor wrote:

    Okay i have figured out how to get to the config file and I think i found the line that points to the music location. Oh and i mapped directly to the slug and not to the ip address of the slug. Is this right?

    How do I then edit the line mp3_dir = /share/hdd/data/?

    I have tried changing this through the web admin but I keep getting

    Error: 500general:mp3_dir

    If you used PICO how do you install it and is it easier to use?

    I use nano.

    you need to do

    ipkg update
    ipkg install nano
    #16890

    Anonymous

    I have installed nano now. how do i use it to edit the config file?

    #16891

    Anonymous

    the issue you are having with the config is just a file permission

    just do a chmod 644 on the config file and then the error should go away.

    #16892

    Anonymous

    I have tried that, and i still get the same error message.

    Any ideas?

    Conor

    #16893

    Anonymous

    Make sure you have the shares directory in your unslung config file set for sharing … the default IP to THIS config file is 192.168.1.77. You find this configuration item under Administration > Advanced > Shares. Click on the share and then click the “Access” button. It should appear in the “Groups with Access” box on the left; if not, highlight it and click the arrow key for “R/W Access” to move it to the left box. Save the config and exit out. I reboot the slug after doing this, although I’m not sure that’s entirely necessary.

    Then you should be able to use the Firefly config file at 192.168.1.77:3689 (that’s the default IP address).

Viewing 10 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic.