hello,
On Fri, 5 Jul 2002, Rajeev Sharma wrote:
>yap i have tried it out but not working...
>then i got rtl8139-diag form www.scyld.com...
>it is fine but give some problems when you compile it for
>rtl8129...
try the mii-diag you can found in the same tar of the 8139too driver:
On Fri, 5 Jul 2002, Jason Lim wrote:
> Are you sure? I used it a long time ago with Realtek cards, and it worked
> fine.
>
> Not sure about the latest version... but I can't see why they would remove
> Realtek compatibility?!
yap i have tried it out but not working...
then i got rtl8139-d
hello,
On Fri, 5 Jul 2002, Rajeev Sharma wrote:
>yap i have tried it out but not working...
>then i got rtl8139-diag form www.scyld.com...
>it is fine but give some problems when you compile it for
>rtl8129...
try the mii-diag you can found in the same tar of the 8139too driver:
On Fri, 5 Jul 2002, Jason Lim wrote:
> Are you sure? I used it a long time ago with Realtek cards, and it worked
> fine.
>
> Not sure about the latest version... but I can't see why they would remove
> Realtek compatibility?!
yap i have tried it out but not working...
then i got rtl8139-
> Are you sure? I used it a long time ago with Realtek cards, and it worked
> fine.
It works fine for mee too:
[EMAIL PROTECTED]:~$ mii-diag eth1
Basic registers of MII PHY #32: 1100 782d 0501 45e1 0001 .
The autonegotiated capability is 0100.
The autonegotiated media type is 100
- Original Message -
From: "Rajeev Sharma" <[EMAIL PROTECTED]>
To:
Cc: <[EMAIL PROTECTED]>
Sent: Friday, July 05, 2002 11:42 AM
Subject: Re: transfer rate
> Hi all ,
>
> > $ dmesg |egrep eth[0-2]
> > eth1: Intel Corp. 82557 [Ethernet Pro 100], 00:A
Hi all ,
> $ dmesg |egrep eth[0-2]
> eth1: Intel Corp. 82557 [Ethernet Pro 100], 00:A0:C9:39:4C:2C, IRQ 19.
> eth2: ns83820 v0.15: DP83820 v1.2: 00:40:f4:17:74:8a io=0xfebf9000
> irq=16 f=h,sg
> eth2: link now 1000 mbps, full duplex and up.
yap i tried it out as it shows the output as abov
> Are you sure? I used it a long time ago with Realtek cards, and it worked
> fine.
It works fine for mee too:
stefan@ididntdoit:~$ mii-diag eth1
Basic registers of MII PHY #32: 1100 782d 0501 45e1 0001 .
The autonegotiated capability is 0100.
The autonegotiated media type is 10
> I have checked the things with mii-tool ..but as it don't support
> rtl cards ...
>
> is there some options for rtl cards..
> i am using a RTL8139 100Mbit card..
Are you sure? I used it a long time ago with Realtek cards, and it worked
fine.
Not sure about the latest version... but I can't se
- Original Message -
From: "Rajeev Sharma" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, July 05, 2002 11:42 AM
Subject: Re: transfer rate
> Hi all ,
>
> > $ dmesg |egrep eth[0-2]
> > eth1: Intel Corp. 82557
Hi all ,
> $ dmesg |egrep eth[0-2]
> eth1: Intel Corp. 82557 [Ethernet Pro 100], 00:A0:C9:39:4C:2C, IRQ 19.
> eth2: ns83820 v0.15: DP83820 v1.2: 00:40:f4:17:74:8a io=0xfebf9000
> irq=16 f=h,sg
> eth2: link now 1000 mbps, full duplex and up.
yap i tried it out as it shows the output as abo
> I have checked the things with mii-tool ..but as it don't support
> rtl cards ...
>
> is there some options for rtl cards..
> i am using a RTL8139 100Mbit card..
Are you sure? I used it a long time ago with Realtek cards, and it worked
fine.
Not sure about the latest version... but I can't s
On Thu, 4 Jul 2002, Emilio Brambilla wrote:
> check the duplex negotiation... for better performance usually you should
> force to 100mbit/FullDuplex both the switch port and the server nic (use
> the mii-tool or the eth kernel module parameter on the linux side)
I have checked the things with
Hi All,
Further to what Jeff said I can also recommend a utility called
"mii-diag". Simply running this utility will enable you to see the
currently selected media type. Use "mii-diag -h" to see full options. It
also allows you to set the media type.
Cheers, Fred.
--
To UNSUBSCRIBE, email to
Hi, I suggest you check the duplex mode on your ethernet interface and
your switch. I had a problem similar to yours just a couple of months
ago, and tracked it down to the interface auto-negotiating into half
instead of full duplex. On a busy ethernet interface that can cause
enough collisions t
Hi All,
Further to what Jeff said I can also recommend a utility called
"mii-diag". Simply running this utility will enable you to see the
currently selected media type. Use "mii-diag -h" to see full options. It
also allows you to set the media type.
Cheers, Fred.
--
To UNSUBSCRIBE, email to
Hi, I suggest you check the duplex mode on your ethernet interface and
your switch. I had a problem similar to yours just a couple of months
ago, and tracked it down to the interface auto-negotiating into half
instead of full duplex. On a busy ethernet interface that can cause
enough collisions
hello,
On Thu, 4 Jul 2002, Rajeev Sharma wrote:
> it shows 1% data loss and some time 0% data loss..
> i have checked my cables,switch ...but no use
check the duplex negotiation... for better performance usually you should
force to 100mbit/FullDuplex both the switch port and the server nic
hello,
On Thu, 4 Jul 2002, Rajeev Sharma wrote:
> it shows 1% data loss and some time 0% data loss..
> i have checked my cables,switch ...but no use
check the duplex negotiation... for better performance usually you should
force to 100mbit/FullDuplex both the switch port and the server ni
>-)Try changing the network cable anyway. If the wrong pairs are used for
>-)twisted pair (10base-T) then the cable may produce some of the symptoms you
>-)describe.
i have changed my network cable (both patch cord and wire from swith to
I/O box)
But nop...things are same ..
mainly prob
it shows 1% data loss and some time 0% data loss..
Try changing the network cable anyway. If the wrong pairs are used for
twisted pair (10base-T) then the cable may produce some of the symptoms you
describe.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Troub
>-)Try changing the network cable anyway. If the wrong pairs are used for
>-)twisted pair (10base-T) then the cable may produce some of the symptoms you
>-)describe.
i have changed my network cable (both patch cord and wire from swith to
I/O box)
But nop...things are same ..
mainly pro
it shows 1% data loss and some time 0% data loss..
Try changing the network cable anyway. If the wrong pairs are used for
twisted pair (10base-T) then the cable may produce some of the symptoms you
describe.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trou
23 matches
Mail list logo
