Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Hi, I have installed debian etch on my DNS-313 (by modifing rd.gz not to delete all files on each boot). However, a few minutes running debian the system freezes (not even ping works) and I have to pull the power cable. Are anyone else having this problem, have a missed anything?
Thanks
Offline
...provides too little informations about the problem. (I´m running etch on the 313 too, but without any problems)
- where did you get the etch?
- fresh and clean installation?
- are there any daemons running after boot?
- dhcp or fixed IP? Maybe the box changes his IP-addr.?
- a few minutes? Exactly?
These days I´m setting up a fresh Debian on my DNS-313 with cdebootstrap. Guess, the currently running still has some bugs. Will provide the new for download when finished.
ChBear.
Offline
I have tracked down the problem to the ntpd daemon. It seems that when ntpd tries to modify the hardware clock,
the system hangs.
Do you know if the d-link supplied "sntp" can be run as a daemon instead?
Offline
Don´t know, but I also don´t trust the d-link supplied files.
I´m running ntp_1:a4.2.2.p4+dfsg-2_arm without problems.
ChBear.
Offline
mjuul wrote:
Hi, I have installed debian etch on my DNS-313 (by modifing rd.gz not to delete all files on each boot). However, a few minutes running debian the system freezes (not even ping works) and I have to pull the power cable. Are anyone else having this problem, have a missed anything?
Thanks
I tried to modify rd.gz file:
1. Stripped the 104-byte uboot header
2. Unpacked resulting gzip file
3. Mounted unpacked image (it is a ext2 filesystem image)
4. Modified linuxrc file in it
5. Unmouned, packed with gzip (rd.gz.mod)
6. Recreated uboot header with: mkimage -a 0x800000 -e 0x800000 -n 'boot ramdisk' -A arm -O linux -T ramdisk -C gzip -d rd.gz.mod rd.gz
mkimage tool is located in uboot-mkimage ubuntu package
UNFORTUNATELY, such modified ramdisk does not work, the system does not boot up to a network-reachable state (probably just hangs on trying to load the ramdisk). My bet is, mkimage command parameters are bad. Any hints?
Offline
examine the Image/toolchain/bin/mkflash script. there are valid parameters for a mkimage
Last edited by pcp (2008-05-19 23:52:22)
Offline