Re: tulip driver 2.4.x kernel
Berkley,
Thanks for responding with your suggestions. It is nice to see someone
listening. I have had this problem since 2.4.0, and yours is the most
helpful to actually solve the problem. Most people assume user error, which
it may be, but I have also seen some indication on the net of real problems
with the de4x5 driver which I suspect. It took a while to generate this
information, but if I can fix the problem, it will be worth the effort. I
recompiled the 2.4.5 kernel to make sure that the only difference between the
two versions was the de4x5 and tulip ethernet drivers.
On Friday 22 June 2001 09:25 am, Mr. Berkley Shands wrote:
> "James D. Freels" wrote:
> > I have a DE-500-AA ethernet card on a PC164 motherboard with 500Mhz
> > 21164A Alpha chip. I purchased this turnkey from Microway. It has
> > worked fine with all kernels up until 2.4.x. Then it fails both with
> > de4x5 and tulip drivers.
>
> Please try an "ifconfig -a" are you getting collisions or carrier
> errors?
OK. I have three outputs to show: 1) ifconfig -a > ifconfig.2.2.19
2) ifconfig -a >ifconfig.2.4.5_de4x5, and 3) ifconfig.2.4.5_tulip. Nothing
unusual that I could see. The system runs 2.2.19 nearly all the time, so a
few errors show up out of the millions of packets transfered for that kernel.
ifconfig.2.2.19:
__________________
dummy Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
eth0 Link encap:Ethernet HWaddr 00:00:F8:05:C2:19
inet addr:128.219.17.74 Bcast:128.219.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:88795640 errors:481 dropped:0 overruns:0 frame:481
TX packets:28433672 errors:742 dropped:0 overruns:0 carrier:543
collisions:2051727 txqueuelen:100
Interrupt:17 Base address:0x8000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:8020 Metric:1
RX packets:6988535 errors:0 dropped:0 overruns:0 frame:0
TX packets:6988535 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
ifconfig.2.4.5_de4x5
________________
dummy0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
eth0 Link encap:Ethernet HWaddr 00:00:F8:05:C2:19
inet addr:128.219.17.74 Bcast:128.219.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9798 errors:0 dropped:0 overruns:0 frame:0
TX packets:61 errors:0 dropped:0 overruns:0 carrier:0
collisions:4 txqueuelen:100
Interrupt:17 Base address:0x8400
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:36 errors:0 dropped:0 overruns:0 frame:0
TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
ifconfig.2.4.5_tulip
_______________
dummy0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
eth0 Link encap:Ethernet HWaddr 00:00:F8:05:C2:19
inet addr:128.219.17.74 Bcast:128.219.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1929 errors:0 dropped:0 overruns:0 frame:0
TX packets:39 errors:1 dropped:0 overruns:0 carrier:1
collisions:0 txqueuelen:100
Interrupt:17 Base address:0x8400
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:36 errors:0 dropped:0 overruns:0 frame:0
TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
> I have 3 pc164lx boxes, they don't show this problem.
That is good. I also have another pc164lx box, that has a a later tulip
device, but I have not tested the new kernel on it yet.
> All have firmware V5.8-1 and the srm console.
This machine is at v4.8-1 or srm. I have read where later versions of srm
may not work for it. when I originally bought the machine, I tri-booted
between DEC-Unix, Linux, and Alpha-NT. So, I got used to changing firmware.
I am willing to upgrade the SRM version, if it won't cause more problems than
fix.
> <DT><A
> HREF="http://ftp.digital.com/pub/Digital/Alpha/firmware/index.html";
> ADD_DATE="983218449" LAST_VISIT="993060491"
> LAST_MODIFIED="983218444">Alpha Systems Firmware</A>
> <DT><A
> HREF="http://www.alpha-processor.com/support/firmware.shtml";
> ADD_DATE="983471635" LAST_VISIT="993060620"
> LAST_MODIFIED="983471629">API NetWorks, Inc: Firmware</A>
> The microway is a good box...
Damn right Microway is good! I have bene a customer of theres long before
Alphas came out. They have always been a customer that brings high
performance to the desktop at a reasonable cost.
> What does ">>> show ewa*" return for ewa0_mode off the srm console?
Twisted-Pair
>
> Maybe I should back up a step. What does
> "Then it fails both with de4x5 and tulip drivers." mean ?
> it won't boot or it doesn't talk to the world?
It boots fine and will run for several minutes. But, when you give it a
decent network load, it just hangs the system dead. Luckily, the Linux
e2fsck process is robust enough to correct the many errors that show up on
the drives when it reboots. My main goal is to get reiserfs running on this
machine, but I am sure other new features of the kernel will also be used.
> Do you have aboot v0.7 or v0.7a installed? If not, you can
> end up not mounting root.
I am running v0.7a of aboot.
> If it does boot, but will not talk, make sure ">>> set ewa0_mode auto"
> and that your switch is autonegotiate on that port. The tulip driver
> should report how it is talking... (this is from the generic tulip
> driver CONFIG_DE4X5=y)
I don't understand why I need to change ewa0_mode to auto. I have no idea
where to look for the autonegotiate switch for the port ?
Again here are three examples of the ethernet section out of dmesg output:
dmesg.2.2.19_de4x5
_________________
Linux version 2.2.19 (root@fea6) (gcc version 2.95.2 20000220 (Debian
GNU/Linux)) #1 Thu Mar 29 16:20:46 EST 2001
Booting on EB164 variation PC164 using machine vector PC164 from SRM
.
.
.
eth0: DE500-AA at 0x8000 (PCI bus 0, device 7), h/w address 00:00:f8:05:c2:19,
and requires IRQ17 (provided by PCI BIOS).
de4x5.c:V0.544 1999/5/8 davies@maniac.ultranet.com
.
.
.
eth0: media is TP.
dmesg.2.4.5_de4x5
________________
Linux version 2.4.5 (root@fea6) (gcc version 2.95.2 20000220 (Debian
GNU/Linux)) #1 Fri Jun 22 14:00:43 EDT 2001
Booting on EB164 variation PC164 using machine vector PC164 from SRM
.
.
.
eth0: DE500-AA at 0x8400 (PCI bus 0, device 7), h/w address 00:00:f8:05:c2:19,
and requires IRQ17 (provided by PCI BIOS).
de4x5.c:V0.546 2001/02/22 davies@maniac.ultranet.com
.
.
.
eth0: media is TP.
dmesg.2.4.5_tulip
______________
Linux version 2.4.5 (root@fea6) (gcc version 2.95.2 20000220 (Debian
GNU/Linux)) #2 Fri Jun 22 14:47:12 EDT 2001
Booting on EB164 variation PC164 using machine vector PC164 from SRM
.
.
.
Linux Tulip driver version 0.9.15-pre2 (May 16, 2001)
tulip0: EEPROM default media type Autosense.
tulip0: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block.
tulip0: MII transceiver #5 config 0000 status 780d advertising 00a1.
tulip0: Advertising 01e1 on PHY 5, previously advertising 00a1.
eth0: Digital DS21140 Tulip rev 32 at 0x8400, 00:00:F8:05:C2:19, IRQ 17.
.
.
.
(no eth0 media message found ?)
________________________________
I hope you or someone can help me with this. I wonder if if may be necessary
to get a different ethernet card.
--
James D. Freels, P.E._i, Ph.D.
Oak Ridge National Laboratory
freelsjd@ornl.gov - work
jdfreels@home.com - home
Reply to: