On Tue, Nov 18, 2008 at 01:51:13PM +, Martin Guy wrote:
> I only get 3 MB/s on a 100Mbps network using a 200MHz ARM CPU
> because it runs out of CPU to run the TCP network stack.
> You can find out whether this is your problem by running "vmstat 5"
> on a console while you beat the network/
>...
Ok, thanks for the indications!
>> My second question was about disks status led: It could be fine to see the
>> lighted when they
>> are working. With the original software they lights on traffic, so I think
>> that they are not
>> broken.
>The disks leds are disabled by default and don'
Andrea Lanza <[EMAIL PROTECTED]> writes:
> Yes, SS4000E , based on EM-7210 card.
>
> I got the kernel sources from www.kernel.org
> I took version 2.6.25.1
> then I patched it applying all the patches present in
>
> http://git.rtp-net.org/?p=ss4000e.git;a=summary
ok. So you have the patches and
Yes, SS4000E , based on EM-7210 card.
I got the kernel sources from www.kernel.org
I took version 2.6.25.1
then I patched it applying all the patches present in
http://git.rtp-net.org/?p=ss4000e.git;a=summary
I DON'T applied the commented out patches:
this is the series file:
compiler.patch
ha
Andrea Lanza <[EMAIL PROTECTED]> writes:
> hi al,
Hi,
> I am completly new to this list and to Debian and arm too.
>
> Anyway I succeded in installing my Intel S4000e with kernel 2.6.25.1 and
> latest lenny Debian.
You meant SS4000e, right ? :)
> I cross compiled my kernel using the patch I f
Thanks all for the answers.
I am using switched 1 GB/s network for my tests.
I don't "think" anything about Debian, I always used textual opensuse for my
linux boxes and servers,
so I am absolutely a novice regarding Debian.
But Debian seems to be the only distribution really supporting armel,
Riku Voipio wrote:
> On Tue, Nov 18, 2008 at 01:37:11PM +0100, Martin Michlmayr wrote:
>> It happens because of Riku's LED driver. When I compile a kernel
>> without the driver, I can start ifplugd just fine.
>
>> Riku, the best way to reproduce this is to install ifplugd (but _not_
>> change INT
On 11/18/08, Lennert Buytenhek <[EMAIL PROTECTED]> wrote:
> Is that the Cirrus ep93xx? If yes, then you're only getting 3 MB/s
> because the ethernet MAC is lame
Yes it is. Thanks for the info
M
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Cont
On Tue, Nov 18, 2008 at 01:51:13PM +, Martin Guy wrote:
> I only get 3 MB/s on a 100Mbps network using a 200MHz ARM CPU
> because it runs out of CPU to run the TCP network stack.
Is that the Cirrus ep93xx? If yes, then you're only getting 3 MB/s
because the ethernet MAC is lame and the mac
Hi!
I only get 3 MB/s on a 100Mbps network using a 200MHz ARM CPU
because it runs out of CPU to run the TCP network stack.
You can find out whether this is your problem by running "vmstat 5"
on a console while you beat the network/disks to death, watching the
"CPU - id" column. If it goes down
hi al,
I am completly new to this list and to Debian and arm too.
Anyway I succeded in installing my Intel S4000e with kernel 2.6.25.1 and latest
lenny Debian.
I cross compiled my kernel using the patch I found on the net and then moved
the zImage
to the scratched (init-ialized) RedBoot Flash.
On Tue, Nov 18, 2008 at 01:37:11PM +0100, Martin Michlmayr wrote:
> It happens because of Riku's LED driver. When I compile a kernel
> without the driver, I can start ifplugd just fine.
> Riku, the best way to reproduce this is to install ifplugd (but _not_
> change INTERFACES in /etc/default/ifp
* Ross Burton <[EMAIL PROTECTED]> [2008-11-17 10:59]:
> Installing ifplugd and setting INTERFACES in /etc/default/ifplugd to
> "auto" causes the bug for me. auto may well be the default.
It happens because of Riku's LED driver. When I compile a kernel
without the driver, I can start ifplugd just
13 matches
Mail list logo
