From: Nikolai Zhubr <zhubr.2@gmail.com>
To: netdev <netdev@vger.kernel.org>
Cc: tedheadster <tedheadster@gmail.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
whiteheadm@acm.org, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: Realtek 8139 problem on 486.
Date: Sun, 30 May 2021 13:36:10 +0300 [thread overview]
Message-ID: <60B36A9A.4010806@gmail.com> (raw)
In-Reply-To: <60B2E0FF.4030705@gmail.com>
Hi all,
30.05.2021 3:49, Nikolai Zhubr:
[...]
> eth0 Link encap:Ethernet HWaddr 00:11:6B:32:85:74
> inet addr:192.168.0.3 Bcast:192.168.0.255 Mask:255.255.255.0
> ......
> Interrupt:9 Base address:0x6000
>
> eth1 Link encap:Ethernet HWaddr 00:11:6B:32:85:74
> inet addr:192.168.0.4 Bcast:192.168.0.255 Mask:255.255.255.0
> ......
> Interrupt:9 Base address:0x8000
>
> whereas actually only one physical network card present. One can notice
> HWaddr and Irq is the same, although base addr is not.
>
> lspci says:
> 00:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139
> (rev 10)
Ok, sorted out this.
eth0 == rtl8139.c:v1.07 5/6/99
eth1 == 8139too Fast Ethernet driver 0.9.18-pre4
So, 8139too 0.9.18-pre4 as of kernel 2.2.20 is the one that apparently
works correctly here. I feel the bisect is going to be massive.
Thank you,
Regards,
Nikolai
> Now as soon as ip configuration is done preperly, I can ifup any of them
> successfully.
> And, eth0 shows some familiar misbehaviour: I can do ssh, but scp large
> file fails with subsequent communication breakdown. On the other hand,
> eth1 works fine, scp and iperf3 (both as a client and as a server) show
> quite regular operation. I'm puzzled a bit. But at least it looks like a
> possible starting point.
>
>
> Thank you,
>
> Regards,
> Nikolai
>
>>
>> - Matthew
>>
>
next prev parent reply other threads:[~2021-05-30 10:26 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-29 14:08 Realtek 8139 problem on 486 Nikolai Zhubr
2021-05-29 18:42 ` Heiner Kallweit
2021-05-29 21:44 ` tedheadster
2021-05-30 0:49 ` Nikolai Zhubr
2021-05-30 10:36 ` Nikolai Zhubr [this message]
2021-05-30 17:27 ` Nikolai Zhubr
2021-05-30 20:54 ` Arnd Bergmann
2021-05-30 23:17 ` Nikolai Zhubr
2021-05-31 16:53 ` Nikolai Zhubr
2021-05-31 18:39 ` Arnd Bergmann
2021-05-31 22:18 ` Nikolai Zhubr
2021-05-31 22:30 ` Heiner Kallweit
2021-06-01 7:20 ` Arnd Bergmann
2021-06-01 10:53 ` Nikolai Zhubr
2021-06-01 11:42 ` Heiner Kallweit
2021-06-01 16:09 ` Nikolai Zhubr
2021-06-01 21:48 ` Heiner Kallweit
2021-06-01 23:37 ` Nikolai Zhubr
2021-06-02 9:12 ` Arnd Bergmann
2021-06-07 23:07 ` Nikolai Zhubr
2021-06-08 7:44 ` Arnd Bergmann
2021-06-08 20:32 ` Nikolai Zhubr
2021-06-08 20:45 ` Arnd Bergmann
2021-06-08 22:07 ` Nikolai Zhubr
2021-06-09 7:09 ` Arnd Bergmann
2021-06-12 17:40 ` Nikolai Zhubr
2021-06-12 22:41 ` Arnd Bergmann
2021-06-13 14:10 ` Nikolai Zhubr
2021-06-13 21:52 ` Arnd Bergmann
2021-06-03 18:32 ` Maciej W. Rozycki
2021-06-04 7:36 ` Arnd Bergmann
2021-06-20 0:34 ` Thomas Gleixner
2021-06-20 10:19 ` Arnd Bergmann
2021-06-21 4:10 ` Maciej W. Rozycki
2021-06-21 11:22 ` Arnd Bergmann
2021-06-21 14:42 ` Maciej W. Rozycki
2021-06-21 15:20 ` Arnd Bergmann
2021-06-22 11:12 ` David Laight
2021-06-22 12:42 ` Nikolai Zhubr
2021-06-22 13:22 ` Arnd Bergmann
2021-06-22 18:42 ` Nikolai Zhubr
2021-06-22 19:26 ` Arnd Bergmann
2021-06-23 1:04 ` Maciej W. Rozycki
2021-06-24 17:56 ` Nikolai Zhubr
2021-06-24 18:25 ` Maciej W. Rozycki
2021-07-14 23:32 ` Maciej W. Rozycki
2021-07-15 7:32 ` Nikolai Zhubr
2021-07-16 23:48 ` Maciej W. Rozycki
2021-06-23 16:31 ` Nikolai Zhubr
2021-06-23 23:39 ` Maciej W. Rozycki
2021-06-24 8:28 ` Arnd Bergmann
2021-07-02 19:02 ` Nikolai Zhubr
2021-07-03 9:10 ` Arnd Bergmann
2021-07-08 19:21 ` Nikolai Zhubr
2021-07-09 7:31 ` Arnd Bergmann
2021-07-09 12:43 ` David Laight
2021-06-01 17:44 ` Maciej W. Rozycki
2021-06-02 15:14 ` Nikolai Zhubr
2021-06-02 15:28 ` Arnd Bergmann
2021-05-31 19:05 ` Heiner Kallweit
2021-05-31 18:29 ` Denis Kirjanov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=60B36A9A.4010806@gmail.com \
--to=zhubr.2@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=jgarzik@pobox.com \
--cc=netdev@vger.kernel.org \
--cc=tedheadster@gmail.com \
--cc=whiteheadm@acm.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).