Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Pages: 1
I managed to get this running using instructons on wiki. Nfs seems to run flawlessly.
However I have a few questions.
1)
Is this kernel the dlink 1.04 firmware kernel with added nfs support?
2)
When running this reload package (http://www.inreto.de/dns323/misc/firmwa … -1.tar.bz2) are the symlinks to devices etc necisarry, (as described in wiki) or is this plainly unpack, run and smile?
3)
Normally my ffp located on USB, but when running reloaded boot it uses the /mnt/HD_a2/ffp, where is this specified? Is it running another fun_plug than the one located on /mnt/HD_a2?
Offline
1) it's the kernel sources from around firmware 1.03, if i remember correctly. maybe 1.04.
2) the ffp-reloaded howto describes how to boot ffp (no firmware!!) directly from disk. in this case, ffp _replaces_ the firmware, while it is usually an _add-on_ to the firmware. symlinks et al are preparations to boot from disk, and doesn't apply to the firmware-reloaded tarball - that boots the firmware, with a different kernel.
3) kernel command line: root=/dev/sdb4
Offline
Thanx for the reply
For my needs this is great.
+It is really simple to install (install a few funpkg run a script)
+Works same way as standard 1.04 firmware but with nfs support
+Harmless, only modifies in ram memory (right?), unplug device and your home safe.
I think more people would be interested. It is kind of hidden and sparsly documented. I could write something up in the wiki if there more people are interested.
3) Still dont know why it boots differently, didnt really understand your reply. I am running the scripts without modification from your tar. But I haven't had time analysing what happens.
By the way Im on rev B, might not work on other revs.
Another question,
4) Could a newer firmware be used by replacing the (initrd) with something somehow extracted from a dlink firmware? Kernel is same isnt it?
Offline
3)
Update, I found why ffp-reloaded doesnt reload to usb, this is because the usb module path is taken from uname -r which is different, easily fixed by cloning the dir.
And to answer the question, as it behaves as standard firmware. It looks in hd_a2 for the fun_plug
Offline
Another update in this almost oneman thread.
I have been using the reloaded firmware 1.04 with NFS support for a while. It performs good. I used to get alot stale NFS handles and my PCH could not browse dirs without dirty workarounds. These problems are solved. I am happy.
Did some experiments with fw 1.08. I extracted the initrd from version 1.08 using splitfwdns323 tool. It did not boot using the fonz modded 2.6.12 kernel. Im not sure weather or not the initrd generated should be gziped or not, tried both. I would need to read up on the subject and probably getting a jtag to get further. Currently I dont need any features of the 1.08.
I like the approach of using the dlink firmware with a slightly modified kernel.
Offline
Pages: 1