This has nothing to do with LAN, there has been a problem with naming of IDE devices, check the DMA mode with hdparm. With the latest CVS images, the problem has been fixed.

The latest CVS Image could be a OoZooN image for example, and testing with hdparm works in this way:
for device 1:
hdparm -i /dev/discs/disc0/disc
for device 2:
hdparm -i /dev/discs/disc1/disc

for benchmarking simply change the -i to -tT

Might be the power supply.

I had the very same problem, i first thought it was the image, but it's probably the "being down for a while" that brings back the speed.

Replacing the capacitors on the power supply really fixed this problem.

Sorry, my english is not very good but to fix the slow Network is really simple.

Open wit an Unixcompatible Editor The file:
\\Dreambox\Configuration\etc\init.d\boot <- This is a Samba Link to my Box
Change:
# sleep after 10min
hdparm -S 120 /dev/discs/disc0/disc
echo 32 > /proc/progress
# set UDMA66
hdparm -X66 /dev/discs/disc0/disc
echo 34 > /proc/progress
# accustic management
hdparm -M 128 /dev/discs/disc0/disc

to:

# sleep after 10min
hdparm -S 120 /dev/discs/disc1/disc
echo 32 > /proc/progress
# set UDMA66
hdparm -X66 /dev/discs/disc1/disc
echo 34 > /proc/progress
# accustic management
hdparm -M 128 /dev/discs/disc1/disc

(simple disk0 to disk1)

after that it works again

Falls ein Entwickler mit liest: da wird übrigens nicht UDMA66 gesetzt, sondern UDMA33. Nur falls sich jemand wundert, daß nur Mode 2 angezeigt wird. Vielleicht könnte man den Kommentar mal generell in der bootup ändern

Hallo Kodo,

ich glaube, in den neueren Images ist der Fehler gefixt.

Zitat von eagle

This don't work...

..and into new images the problem is not resolved !!!!

Is this related to the thing that if you have CF mounted in the box, then /dev/discs/disc0 is is the CF?
If you remove the CF, then /dev/discs/disc0 is actually the HDD.

I had to change the /etc/fstab /media/hdd mount too to disc1.
This is with Experimental image 27.4.2009, and has been quite some time!

Zitat von eagle

I solved removing the CF!

The fstab of dm7025 :

Code

/dev/ide/host0/bus0/target0/lun0/part1 /media/hdd auto defaults              0 0
/dev/ide/host1/bus0/target0/lun0/part1 /media/cf auto  defaults              0 0
/dev/ide/host1/bus0/target0/lun0/disc /media/cf auto  defaults             0 0
/dev/scsi/host0/bus0/target0/lun0/part1 /media/usb auto defaults           0 0
/dev/scsi/host0/bus0/target0/lun0/disc  /media/usb auto defaults           0 0

How do you change the mount dell'hdd in disc1??? No /dev/discs/disc0/part1 string..

But this problems should resolve the DMM!

Thanks

Alles anzeigen

My image from 27.4.2009 (DMM Experimental) has a totally different one:

rootfs           	/                	auto   	defaults          	1 1
proc             	/proc            	proc   	defaults          	0 0
devpts           	/dev/pts         	devpts 	mode=0620,gid=5   	0 0
usbdevfs         	/proc/bus/usb    	usbfs  	defaults          	0 0
/dev/root  	/boot            	jffs2  	ro                	0 0
tmpfs            	/var             	tmpfs  	defaults          	0 0
tmpfs            	/tmp             	tmpfs  	defaults          	0 0
/dev/discs/disc0/part1 /media/cf     	auto   	defaults          	0 0
/dev/discs/disc1/part1 /media/hdd     	auto   	defaults          	0 0

The line with /media/cf was originally /media/hdd and the following line I had to add myself.
If I ever take the CF away, then I would have to edit the fstab again. This is not good.

Zitat von tero_

The line with /media/cf was originally /media/hdd and the following line I had to add myself.
If I ever take the CF away, then I would have to edit the fstab again. This is not good.

This is not good, it's very very bad.
But even worst is the DMM silence. It would be so simple to say "we are working on it" or "we don't know how to solve"
Even "we don't care about it" woul be better than nothing ...

An experimental dm7025 image with sourcedate 20090611, even with changes provided by

Zitat

make DEVICEDB depending on model type

and

Zitat

statially store detected hardware type; it's unlikely to change at runtime

still has heavy problems with network speed. If CF is inserted, speed reaches no more then 4 MB/s. Without CF, speed is automatically increased to normal value: about 7 MB/s. This problem afflicts only dm7025, and apparently only after changes introduced for dm8000: older images don't suffer of it, so a solution has to be possible.
Is there any serious project about it? It would be welcome to hear something at this from DMM developers...
Here's my today fstab:

rootfs               /                    auto       defaults              1 1
proc                 /proc                proc       defaults              0 0
devpts               /dev/pts             devpts     mode=0620,gid=5       0 0
usbdevfs             /proc/bus/usb        usbfs      defaults              0 0
/dev/root      /boot                jffs2      ro                    0 0
tmpfs                /var                 tmpfs      defaults              0 0
tmpfs                /tmp                 tmpfs      defaults              0 0
/dev/ide/host0/bus0/target0/lun0/part1 /media/hdd auto defaults              0 0
/dev/ide/host1/bus0/target0/lun0/part1 /media/cf auto  defaults              0 0
/dev/ide/host1/bus0/target0/lun0/disc /media/cf auto  defaults             0 0
/dev/scsi/host0/bus0/target0/lun0/part1 /media/usb auto defaults           0 0
/dev/scsi/host0/bus0/target0/lun0/disc  /media/usb auto defaults           0 0

Thank you!

Simply place this in bootup:
# HDD Tuning
hdparm -X66 -m16 -S120 -M 128 /dev/discs/disc1/disc
echo 32 > /proc/progress

# CF Tuning
hdparm -X66 /dev/discs/disc0/disc
echo 34 > /proc/progress

With this, you will have have both, CF and HDD running in UDMA2 Mode, if supported by the device. And, my LAN speed is always around 7-9 MB/s WITH CF

Zitat von Kodo

Simply place this in bootup:
....

Thanks a lot, I'll try for sure as soon as I could...
But, (and I'm not asking to you... ) if it's so simple, why have we to go on with these "home made" patches, instead of having a strong, permanent solution into CVS sources (like once was...)?
It seems to me that network transfert and harddisk managment are basical functions, surely not exotic options....

I'm not 100% sure, but I think, that developers already fixed this some time ago. But probably your Image is not new enough to already contain this fix...

Tode