v1.03 on Alpha, 2.1.122/111
Gus Buerkle
buerkl@hoover.ee.cooper.edu
Wed Sep 30 20:25:13 1998
Hello,
I am running Linux 2.1.x on an Alpha 164LX. I had been using a 3Com 905TX
card, but always encountered kernel panics whenever the eth0 interface was
brought up under 2.1.x (worked fine for 2.0.x). So the switch was made
to the Intel EtherExpress Pro100 ('82557).
I started using Becker's driver v0.36, built into kernel 2.1.122.
It worked fairly well, but there was an occasional 'network crash', for
lack of a better term, in which the interface would become unresponsive
and the only way to get back on the network was to reboot. Bringing eth0
down and back up had no effect.
So I decided to move up to the v1.03 driver
Then I built the 2.1.123 kernel with eepro100.c v1.03 as a module.
When bringing the interface up, no errors are encountered, but nothing
happens. I'd like to get the new driver working, whether as a module
or built in. Here are some diagnostics:
/sbin/ifconfig:
[root@dunkel /root]# depmod -a
[root@dunkel net]# modprobe eepro100.o
[root@dunkel net]# cat /proc/modules
eepro100 17672 0 (unused)
[root@dunkel net]# ifup eth0
[root@dunkel net]# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:8020 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 coll:0
eth0 Link encap:Ethernet HWaddr 00:A0:C9:2A:9F:EB
inet addr:199.98.20.240 Bcast:199.98.20.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST 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 coll:0
Interrupt:18 Base address:0x8000
/var/log/messages:
Sep 30 14:00:10 dunkel kernel: eepro100.c:v1.03 8/11/98 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
Sep 30 14:00:10 dunkel kernel: eepro100.c:v1.03 8/11/98 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
Sep 30 14:00:10 dunkel kernel: eth0: Intel EtherExpress Pro 10/100 at
0x8000, 00:A0:C9:2A:9F:EB, IRQ 18.
Sep 30 14:00:10 dunkel kernel: Board assembly 352509-003, Physical
connectors present: RJ45
Sep 30 14:00:10 dunkel kernel: Primary interface chip DP83840 PHY #1.
Sep 30 14:00:10 dunkel kernel: DP83840 specific setup, setting register
23 to 8462.
Sep 30 14:00:10 dunkel kernel: General self-test: passed.
Sep 30 14:00:10 dunkel kernel: Serial sub-system self-test: passed.
Sep 30 14:00:10 dunkel kernel: Internal registers self-test: passed.
Sep 30 14:00:10 dunkel kernel: ROM checksum self-test: passed
(0x49caa8d6).
Sep 30 14:00:10 dunkel kernel: Receiver lock-up workaround activated.
/proc/net/dev:
[root@dunkel net]# cat /proc/net/dev
Inter-| Receive |
Transmit
face |bytes packets errs drop fifo frame compressed multicast|bytes
packets errs drop fifo colls carrier compressed
lo: 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0
eth0: 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0
/proc/modules:
[root@dunkel net]# cat /proc/modules
eepro100 17672 0 (unused)
It appears that the module has been loaded correctly, but the network
interface doesn't work.
Separately, I cannot compile the eepro-diag program from becker's site.
The following gcc error results:
[root@dunkel linux-2.1.122]# gcc -O -Wall -o eepro-diag eepro100-diag.c
In file included from eepro100-diag.c:30:
/usr/include/linux/in.h:109: parse error before `sa_family_t'
/usr/include/linux/in.h:109: warning: no semicolon at end of struct or
union
/usr/include/linux/in.h:116: parse error before `}'
In file included from /usr/include/asm/io.h:6,
from eepro100-diag.c:32:
/usr/include/asm/machvec.h:58: parse error before `*'
/usr/include/asm/machvec.h:60: parse error before `*'
/usr/include/asm/machvec.h:62: parse error before `*'
/usr/include/asm/machvec.h:65: parse error before `value'
/usr/include/asm/machvec.h:67: parse error before `value'
/usr/include/asm/machvec.h:69: parse error before `value'
/usr/include/asm/machvec.h:82: parse error before `vector'
My symlinks to /usr/src/linux are set up properly:
[root@dunkel linux-2.1.122]# ls -l /usr/include
lrwxrwxrwx 1 root root 28 Sep 18 13:53 linux ->
/usr/src/linux/include/linux
lrwxrwxrwx 1 root root 32 Sep 18 17:41 asm ->
/usr/src/linux/include/asm-alpha
lrwxrwxrwx 1 root root 27 Sep 18 13:53 scsi ->
/usr/src/linux/include/scsi
Any things I should check regarding this problem?
Thanks
August Buerkle