From: Bill Davidsen <davidsen@tmr.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: 2.4.20 gets duplex wrong on NIC
Date: Tue, 3 Dec 2002 18:24:05 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44.0212031818310.1176-200000@oddball.prodigy.com> (raw)
[-- Attachment #1: Type: TEXT/PLAIN, Size: 388 bytes --]
In spite of modules.conf the system boots with the NIC in half duplex. I
verified this with the mii-tool, I can set it full with mii-tool and it
works right (copied a CD image 650MB), and the blade in the switch has
been set either full or auto without gain. Yes, I tried the e100 driver as
well.
Info I think shows this attached to prevent munging, let me know if more
is needed.
[-- Attachment #2: Type: TEXT/PLAIN, Size: 2797 bytes --]
Script started on Tue Dec 3 18:16:21 2002
Common profile 1.9 hacked lastmod 2002-11-14 21:55:45-04
No common directory available
Session time 18:16:21 on 12/03/02
oddball:root> tail -20\b\b\b\b\b\b\b\b^[[Kdmesg | tail -20
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,67), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
hdc: DMA disabled
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI ISAPNP enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
eepro100.c:v1.09j-t 9/29/99 Donald Becker http://www.scyld.com/network/eepro100.html
eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <saw@saw.sw.com.sg> and others
PCI: Found IRQ 9 for device 00:06.0
PCI: Sharing IRQ 9 with 00:07.2
eth0: Intel Corp. 82557/8/9 [Ethernet Pro 100], 00:90:27:07:F2:9E, IRQ 9.
Receiver lock-up bug exists -- enabling work-around.
Board assembly 713807-002, Physical connectors present: RJ45
Primary interface chip i82555 PHY #1.
General self-test: passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (0x24c9f043).
Receiver lock-up workaround activated.
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16)
lp: driver loaded but no devices found
oddball:root> mii-tool
eth0: no autonegotiation, 10baseT-HD, link ok
oddball:root> ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:90:27:07:F2:9E
inet addr:192.168.192.242 Bcast:192.168.192.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:253 errors:0 dropped:0 overruns:0 frame:0
TX packets:29 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:28278 (27.6 Kb) TX bytes:2192 (2.1 Kb)
Interrupt:9 Base address:0x4000
oddball:root> mii-tool -F 10baseT-FD /dev/eth0\b \b\b \b\b \b\b \b\b \b\b \b\b \b\b \b\b \beth0
oddball:root> mii-tool
eth0: 10 Mbit, full duplex, link ok
oddball:root> cat /etc/modules.conf
# $Id: modules.conf 1.3 2002/11/13 20:37:15 root Exp $
# parallel port
alias parport_lowlevel parport_pc
# network card (e100?)
alias eth0 eepro100
options eth0 full_duplex=1
# try to force load sound
#alias sound-slot-0 ac97
# USB info
alias usb-controller usb-uhci
oddball:root> lsmod
Module Size Used by Not tainted
lp 8544 0 (autoclean)
parport 32928 0 (autoclean) [lp]
apm 11996 1
eepro100 20940 1
mii 3492 0 [eepro100]
serial 47712 0 (autoclean)
oddball:root> exit
exit
Script done on Tue Dec 3 18:17:46 2002
next reply other threads:[~2002-12-03 23:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 23:24 Bill Davidsen [this message]
2002-12-04 0:04 ` Jeff Garzik
2002-12-05 17:24 ` Bill Davidsen
2002-12-05 17:34 ` Mr. James W. Laferriere
2002-12-09 1:05 ` Bill Davidsen
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=Pine.LNX.4.44.0212031818310.1176-200000@oddball.prodigy.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®