FireFly Media Server › Firefly Media Server Forums › Firefly Media Server › Nightlies Feedback › Edgy Very Happy
- This topic has 7 replies, 3 voices, and was last updated 17 years, 7 months ago by robinson.
-
AuthorPosts
-
10/02/2007 at 7:15 PM #1091AnonymousInactive
I’ve been anxiously awaiting a nightly for Edgy. I replaced 2.4 stable (from source) with the 1498 Edgy package. I had no trouble installing it and it works great with the M-1001.
THANKS! 😀
12/02/2007 at 3:16 AM #9093rpeddeParticipant@action wrote:
I’ve been anxiously awaiting a nightly for Edgy. I replaced 2.4 stable (from source) with the 1498 Edgy package. I had no trouble installing it and it works great with the M-1001.
THANKS! 😀
Good to hear. Thanks for the feedback.
— Ron
14/02/2007 at 4:50 PM #9094robinsonParticipantI installed firefly svn-1498 on a fresh Edgy. First it runs fine but after a few minutes it doesn’t show up in my iTunes but the mt-daapd runs itself. Only the Bonjour part does’t work. After I shut down the computer and reboot it after several minutes I have it back to work for these few minutes. What’s going wrong?
15/02/2007 at 1:29 AM #9095rpeddeParticipant@robinson wrote:
I installed firefly svn-1498 on a fresh Edgy. First it runs fine but after a few minutes it doesn’t show up in my iTunes but the mt-daapd runs itself. Only the Bonjour part does’t work. After I shut down the computer and reboot it after several minutes I have it back to work for these few minutes. What’s going wrong?
That’s almost always firewall stopping inbound udp to 224.0.0.251 port 5353.
Do you have a firewall of any kind running?
15/02/2007 at 2:45 PM #9096robinsonParticipant@rpedde wrote:
@robinson wrote:
I installed firefly svn-1498 on a fresh Edgy. First it runs fine but after a few minutes it doesn’t show up in my iTunes but the mt-daapd runs itself. Only the Bonjour part does’t work. After I shut down the computer and reboot it after several minutes I have it back to work for these few minutes. What’s going wrong?
That’s almost always firewall stopping inbound udp to 224.0.0.251 port 5353.
Do you have a firewall of any kind running?
Thanks for reply, but I tested it out without firewall and that’s not the problem.
Then I tried start firefly with /sbin/mt-daapd -f and can see it in iTunes again without rebooting. But again after a few minutes firefly disappears.
I think (but don’t know how to prove it), it depends on the built in mdns and the avahi daemon on ubuntu.
Maybe I could try to compile from the source by myself but I’m not shure how to do it exactly including avahi instead of its own mdns.
After I installed samba I coudn’t start firefly at all.
I typed /sbin/mt-daapd -f in a terminal and get the following message- Firefly Version svn-1498: Starting with debuglevel 2
Starting rendezvous daemon
Starting signal handler
Initializing database
Starting web server from /usr/share/mt-daapd/admin-root on port 3689
Listen port: Address already in use
Error staring web server: Address already in use
Aborting
Rendezvous socket closed (daap server crashed?) Aborting.
Aborting16/02/2007 at 12:45 AM #9097robinsonParticipantNow I know the problem. After installing Avahi Zeroconfig Browser on my Ubuntu I realized, that mdns still running. Then I connected my MacBook Pro with an ethernet cable instead of the wireless connection and it works like a charm. Now I guess, it comes from my Netgear WLAN router. Maybe I find a way to fix this.
16/02/2007 at 4:15 AM #9098rpeddeParticipant@robinson wrote:
Now I know the problem. After installing Avahi Zeroconfig Browser on my Ubuntu I realized, that mdns still running. Then I connected my MacBook Pro with an ethernet cable instead of the wireless connection and it works like a charm. Now I guess, it comes from my Netgear WLAN router. Maybe I find a way to fix this.
Ah, yeah… my dad had the same problem with his netgear. Updating the firmware fixed it.
— Ron
16/02/2007 at 11:02 PM #9099robinsonParticipant@rpedde wrote:
@robinson wrote:
Now I know the problem. After installing Avahi Zeroconfig Browser on my Ubuntu I realized, that mdns still running. Then I connected my MacBook Pro with an ethernet cable instead of the wireless connection and it works like a charm. Now I guess, it comes from my Netgear WLAN router. Maybe I find a way to fix this.
Ah, yeah… my dad had the same problem with his netgear. Updating the firmware fixed it.
— Ron
I updated the firmware earlier today and now it works!
-
AuthorPosts
- The forum ‘Nightlies Feedback’ is closed to new topics and replies.