problem with dhcpcd-1.3.18-pl3 daemon, 3c59x driver and 3com 905c card
Dusan Vujosevic
dusanv@cadlink.com
Wed Mar 22 17:24:57 2000
This is a multi-part message in MIME format.
------=_NextPart_000_004A_01BF9423.3E8A9920
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi,
I have a problem with dhcpcd-1.3.18-pl3 daemon (by Sergei Viznyuk), =
3c59x driver (by Donald Becker, obtained in March from =
http://cesdis.gsfc.nasa.gov/pub/linux/drivers/3c59x.c) and 3com 905c =
card. When the dhcpcd asks for an IP from a Windows 2000 server (retail =
version) it reports the MAC address (hardware address, station address =
... whatever you want to call it) of eth0 as 00:00:00:00:00:00. The =
servers gives it an IP. But if you have two of these on the network they =
both get the same IP since thier MACs are the same (00:00:00:00:00:00). =
'ifconfig' gives the correct MAC though. If I pass that MAC to dhcpcd as =
a command line option everything works fine. The driver provided by 3com =
(patch for kernel 2.2.5) behaves in the exact same way. Donald Becker's =
driver also gives a checksum error on load but loads OK (shown in dmesg =
below). I verified this with 3 different 3com 905c cards I could get my =
hands on. I also have absolutely no problems with the 3com 905b card =
(any driver - kerenel 2.2.5 original 3c59x, new 3c59x or 3com 3c90x).
Any help would be appreciated.
Thanks,
Dusan
Some info & files:
I'm running kernel 2.2.5. Debian distribution 2.0 (with some upgrades). =
NIC driver is always compiled into the kernel (dhcpcd requirement).
****dmesg*****:
Linux version 2.2.5 (root@chris) (gcc version 2.7.2.3) #14 Thu Mar 23 =
03:08:26 CET 2000
Detected 400926543 Hz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 399.77 BogoMIPS
Memory: 128364k/131072k available (768k kernel code, 408k reserved, =
1496k data, 36k init)
CPU: Intel Celeron (Mendocino) stepping 05
Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.26 (19981001) Richard Gooch (rgooch@atnf.csiro.au)
PCI: PCI BIOS revision 2.10 entry at 0xfb2e0
PCI: Using configuration type 1
PCI: Probing PCI hardware
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0 for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
NET4: AppleTalk 0.18 for Linux NET4.0
Starting kswapd v 1.5=20
Serial driver version 4.27 with no serial options enabled
ttyS00 at 0x03f8 (irq =3D 4) is a 16550A
ttyS01 at 0x02f8 (irq =3D 3) is a 16550A
pty: 256 Unix98 ptys configured
apm: BIOS version 1.2 Flags 0x07 (Driver version 1.9)
PIIX4: IDE controller on PCI bus 00 dev 39
PIIX4: not 100% native mode: will probe irqs later
hda: FUJITSU MPE3136AT, ATA DISK drive
hdc: LTN403L, ATAPI CDROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: FUJITSU MPE3136AT, 13031MB w/512kB Cache, CHS=3D1661/255/63
hdc: ATAPI 40X CD-ROM drive, 120kB Cache
Uniform CDROM driver Revision: 2.54
FDC 0 is a post-1991 82077
3c59x.c:v0.99L 5/28/99 Donald Becker =
http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
eth0: 3Com 3c905C Tornado at 0xec00, ***INVALID CHECKSUM 002f*** =
00:50:da:66:8d:be, IRQ 11
8K byte-wide RAM 5:3 Rx:Tx split, autoselect/Autonegotiate interface.
MII transceiver found at address 24, status 782d.
Enabling bus-master transmits and whole-frame receives.
Partition check:
hda: hda1 hda2 < hda5 >
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 36k freed
Adding Swap: 120452k swap-space (priority -1)
cdrom: open failed.
VFS: Disk change detected on device ide1(22,0)
(pci_find)IO:0xE801
IRQ: 10
VFS: Disk change detected on device ide1(22,0)
protocol 0400 is buggy, dev eth0
protocol 0400 is buggy, dev eth0
protocol 0400 is buggy, dev eth0
protocol 0000 is buggy, dev eth0
protocol 0000 is buggy, dev eth0
protocol 0608 is buggy, dev eth0
protocol 0608 is buggy, dev eth0
protocol 0608 is buggy, dev eth0
protocol 0008 is buggy, dev eth0
protocol 0008 is buggy, dev eth0
protocol 0000 is buggy, dev eth0
*****dhcpcd output (compiled w/ -DDEBUG & run w/ -d)******
parseDhcpMsgRecv: 10 options received:
i=3D1 len=3D4 option =3D 255.255.255.0
i=3D3 len=3D4 option =3D 192.168.16.1
i=3D6 len=3D4 option =3D 199.126.187.150
i=3D15 len=3D12 option =3D "cadlink.com"
i=3D23 len=3D1 option =3D 128
i=3D51 len=3D4 option =3D 2592000
i=3D53 len=3D1 option =3D 5
i=3D54 len=3D4 option =3D 199.126.187.150
i=3D58 len=3D4 option =3D 1296000
i=3D59 len=3D4 option =3D 2268000
DhcpMsgRecv->yiaddr =3D 192.168.16.150
DhcpMsgRecv->siaddr =3D 0.0.0.0
DhcpMsgRecv->giaddr =3D 0.0.0.0
DhcpMsgRecv->sname =3D ""
ServerHardwareAddr =3D 00.90.27.45.3E.A2
*****dhcpcd.log***********
Mar 23 05:11:57 chris dhcpcd[296]: broadcasting DHCP_REQUEST for =
192.168.16.150=20
Mar 23 05:11:57 chris dhcpcd[296]: broadcastAddr option is missing in =
DHCP server response. Assuming 192.168.16.255=20
Mar 23 05:11:57 chris dhcpcd[296]: DHCP_ACK received from =
(199.126.187.150)=20
*****vortex-diag -a********
vortex-diag.c:v1.09 7/28/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Index #1: Found a 3c905C Tornado 100baseTx adapter at 0xec00.
The Vortex chip may be active, so FIFO registers will not be read.
To see all register values use the '-f' flag.
Initial window 7, registers values by window:
Window 0: 0000 0000 d93f 0000 e3e3 00bf ffff 0000.
Window 1: FIFO FIFO 0700 0000 0000 007f 0000 2000.
Window 2: 5000 66da be8d 0000 0000 0000 0052 4000.
Window 3: 0000 0140 05ea 0000 000a 0800 0800 6000.
Window 4: 0000 0000 0000 0cfa 0001 8880 0000 8000.
Window 5: 1ffc 0000 0000 0600 0807 06de 06c6 a000.
Window 6: 0000 0000 0000 5700 0000 1f45 0000 c000.
Window 7: 0000 0000 0000 0000 0000 0000 0000 e000.
Vortex chip registers at 0xec00
0xEC10: **FIFO** 00000000 00000040 *STATUS*
0xEC20: 00000020 00000000 00080000 00000004
0xEC30: 00000000 1e4ce1b4 00099060 00080004
Indication enable is 06c6, interrupt enable is 06de.
No interrupt sources are pending.
Transceiver/media interfaces available: 100baseTx 10baseT.
Transceiver type in use: 100baseTX.
MAC settings: half-duplex.
Station address set to 00:50:da:66:8d:be.
Configuration options 4000.
****vortex-diag -e*******
vortex-diag.c:v1.09 7/28/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Index #1: Found a 3c905C Tornado 100baseTx adapter at 0xec00.
Parsing the EEPROM of a 3Com Vortex/Boomerang:
3Com Node Address 00:50:DA:66:8D:BE (used as a unique ID only).
OEM Station address 00:50:DA:66:8D:BE (used as the ethernet address).
Manufacture date (MM/DD/YYYY) 10/8/1999, division H, product BB.
Options: none.
Vortex format checksum is incorrect (00e2 vs. 10b7).
Cyclone format checksum is incorrect (0x72 vs. 0x74).
Hurricane format checksum is incorrect (0x5b vs. 0x74).
*******vortex-diag -m******
vortex-diag.c:v1.09 7/28/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Index #1: Found a 3c905C Tornado 100baseTx adapter at 0xec00.
MII PHY found at address 24, status 780d.
MII PHY 0 at #24 transceiver registers:
3000 780d 0040 6176 05e1 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
1000 0300 0000 0000 0000 0192 0200 0000
0036 000c 0f00 ff40 0026 0000 0000 000b.
------=_NextPart_000_004A_01BF9423.3E8A9920
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial><FONT size=3D2>I have a =
problem </FONT><FONT=20
size=3D2>with dhcpcd-1.3.18-pl3 daemon (by Sergei Viznyuk), 3c59x driver =
(by=20
Donald Becker, obtained in March from htt</FONT></FONT><FONT =
face=3DArial=20
size=3D2><A=20
href=3D"ftp://cesdis.gsfc.nasa.gov/pub/linux/drivers/3c59x.c">p://cesdis.=
gsfc.nasa.gov/pub/linux/drivers/3c59x.c</A></FONT><FONT=20
face=3DArial size=3D2>) and 3com 905c card. When the dhcpcd asks for an =
IP from a=20
Windows 2000 server (retail version) it reports the MAC address =
(hardware=20
address, station address ... whatever you want to call it) of eth0 as=20
00:00:00:00:00:00. The servers gives it an IP. But if you have two of =
these on=20
the network they both get the same IP since thier MACs are the same=20
(00:00:00:00:00:00). 'ifconfig' gives the correct MAC though. If I pass =
that MAC=20
to dhcpcd as a command line option everything works fine. The =
driver=20
provided by 3com (patch for kernel 2.2.5) behaves in the exact same =
way.=20
Donald Becker's driver also gives a checksum error on load but loads OK =
(shown=20
in dmesg below). I verified this with 3 different 3com 905c cards I =
could get my=20
hands on. I also have absolutely no problems with the 3com 905b card =
(any driver=20
- kerenel 2.2.5 original 3c59x, new 3c59x or 3com 3c90x).</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Any help would be =
appreciated.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Thanks,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Dusan</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Some info & files:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I'm running kernel 2.2.5. Debian =
distribution 2.0=20
(with some upgrades). NIC driver is always compiled into the kernel =
(dhcpcd=20
requirement).</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>****dmesg*****:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Linux version 2.2.5 (root@chris) (gcc =
version=20
2.7.2.3) #14 Thu Mar 23 03:08:26 CET 2000<BR>Detected 400926543 Hz=20
processor.<BR>Console: colour VGA+ 80x25<BR>Calibrating delay loop... =
399.77=20
BogoMIPS<BR>Memory: 128364k/131072k available (768k kernel code, 408k =
reserved,=20
1496k data, 36k init)<BR>CPU: Intel Celeron (Mendocino) stepping =
05<BR>Checking=20
386/387 coupling... OK, FPU using exception 16 error =
reporting.<BR>Checking=20
'hlt' instruction... OK.<BR>POSIX conformance testing by UNIFIX<BR>mtrr: =
v1.26=20
(19981001) Richard Gooch (<A=20
href=3D"mailto:rgooch@atnf.csiro.au">rgooch@atnf.csiro.au</A>)<BR>PCI: =
PCI BIOS=20
revision 2.10 entry at 0xfb2e0<BR>PCI: Using configuration type =
1<BR>PCI:=20
Probing PCI hardware<BR>Linux NET4.0 for Linux 2.2<BR>Based upon Swansea =
University Computer Society NET3.039<BR>NET4: Unix domain sockets 1.0 =
for Linux=20
NET4.0.<BR>NET4: Linux TCP/IP 1.0 for NET4.0<BR>IP Protocols: ICMP, UDP, =
TCP<BR>NET4: AppleTalk 0.18 for Linux NET4.0<BR>Starting kswapd v 1.5 =
<BR>Serial=20
driver version 4.27 with no serial options enabled<BR>ttyS00 at 0x03f8 =
(irq =3D 4)=20
is a 16550A<BR>ttyS01 at 0x02f8 (irq =3D 3) is a 16550A<BR>pty: 256 =
Unix98 ptys=20
configured<BR>apm: BIOS version 1.2 Flags 0x07 (Driver version =
1.9)<BR>PIIX4:=20
IDE controller on PCI bus 00 dev 39<BR>PIIX4: not 100% native mode: will =
probe=20
irqs later<BR>hda: FUJITSU MPE3136AT, ATA DISK drive<BR>hdc: LTN403L, =
ATAPI=20
CDROM drive<BR>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14<BR>ide1 at =
0x170-0x177,0x376=20
on irq 15<BR>hda: FUJITSU MPE3136AT, 13031MB w/512kB Cache,=20
CHS=3D1661/255/63<BR>hdc: ATAPI 40X CD-ROM drive, 120kB Cache<BR>Uniform =
CDROM=20
driver Revision: 2.54<BR>FDC 0 is a post-1991 82077<BR>3c59x.c:v0.99L =
5/28/99=20
Donald Becker <A=20
href=3D"http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html">http://ces=
dis.gsfc.nasa.gov/linux/drivers/vortex.html</A><BR>eth0:=20
3Com 3c905C Tornado at 0xec00, ***INVALID CHECKSUM 002f*** =20
00:50:da:66:8d:be, IRQ 11<BR> 8K byte-wide RAM 5:3 Rx:Tx split,=20
autoselect/Autonegotiate interface.<BR> MII transceiver found at =
address=20
24, status 782d.<BR> Enabling bus-master transmits and whole-frame =
receives.<BR>Partition check:<BR> hda: hda1 hda2 < hda5 =
><BR>VFS:=20
Mounted root (ext2 filesystem) readonly.<BR>Freeing unused kernel =
memory: 36k=20
freed<BR>Adding Swap: 120452k swap-space (priority -1)<BR>cdrom: open=20
failed.<BR>VFS: Disk change detected on device=20
ide1(22,0)<BR>(pci_find)IO:0xE801<BR>IRQ: 10<BR>VFS: Disk change =
detected on=20
device ide1(22,0)<BR>protocol 0400 is buggy, dev eth0<BR>protocol 0400 =
is buggy,=20
dev eth0<BR>protocol 0400 is buggy, dev eth0<BR>protocol 0000 is buggy, =
dev=20
eth0<BR>protocol 0000 is buggy, dev eth0<BR>protocol 0608 is buggy, dev=20
eth0<BR>protocol 0608 is buggy, dev eth0<BR>protocol 0608 is buggy, dev=20
eth0<BR>protocol 0008 is buggy, dev eth0<BR>protocol 0008 is buggy, dev=20
eth0<BR>protocol 0000 is buggy, dev eth0<BR></FONT></DIV>
<DIV><FONT face=3DArial size=3D2> </DIV></FONT>
<DIV><FONT face=3DArial size=3D2>*****dhcpcd output (compiled w/ -DDEBUG =
& run=20
w/ -d)******</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>parseDhcpMsgRecv: 10 options=20
received:<BR>i=3D1 len=3D4 option =3D=20
255.255.255.0<BR>i=3D3 len=3D4 option =3D=20
192.168.16.1<BR>i=3D6 len=3D4 option =3D=20
199.126.187.150<BR>i=3D15 len=3D12 option =3D =
"cadlink.com"<BR>i=3D23 =20
len=3D1 option =3D 128<BR>i=3D51 len=3D4 =
option =3D=20
2592000<BR>i=3D53 len=3D1 option =3D 5<BR>i=3D54 =
len=3D4 option =3D 199.126.187.150<BR>i=3D58 =
len=3D4 =20
option =3D 1296000<BR>i=3D59 len=3D4 option =3D=20
2268000<BR>DhcpMsgRecv->yiaddr =3D=20
192.168.16.150<BR>DhcpMsgRecv->siaddr =3D=20
0.0.0.0<BR>DhcpMsgRecv->giaddr =3D=20
0.0.0.0<BR>DhcpMsgRecv->sname =3D=20
""<BR>ServerHardwareAddr =3D 00.90.27.45.3E.A2</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>*****dhcpcd.log***********</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Mar 23 05:11:57 chris dhcpcd[296]: =
broadcasting=20
DHCP_REQUEST for 192.168.16.150 <BR>Mar 23 05:11:57 chris dhcpcd[296]:=20
broadcastAddr option is missing in DHCP server response. Assuming =
192.168.16.255=20
<BR>Mar 23 05:11:57 chris dhcpcd[296]: DHCP_ACK received from =20
(199.126.187.150) <BR></FONT><FONT face=3DArial size=3D2></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>*****vortex-diag =
-a********</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>vortex-diag.c:v1.09 7/28/99 Donald =
Becker (<A=20
href=3D"mailto:becker@cesdis.gsfc.nasa.gov">becker@cesdis.gsfc.nasa.gov</=
A>)<BR>Index=20
#1: Found a 3c905C Tornado 100baseTx adapter at 0xec00.<BR>The Vortex =
chip may=20
be active, so FIFO registers will not be read.<BR>To see all register =
values use=20
the '-f' flag.<BR>Initial window 7, registers values by =
window:<BR> Window=20
0: 0000 0000 d93f 0000 e3e3 00bf ffff 0000.<BR> Window 1: FIFO =
FIFO 0700=20
0000 0000 007f 0000 2000.<BR> Window 2: 5000 66da be8d 0000 0000 =
0000 0052=20
4000.<BR> Window 3: 0000 0140 05ea 0000 000a 0800 0800 =
6000.<BR> =20
Window 4: 0000 0000 0000 0cfa 0001 8880 0000 8000.<BR> Window 5: =
1ffc 0000=20
0000 0600 0807 06de 06c6 a000.<BR> Window 6: 0000 0000 0000 5700 =
0000 1f45=20
0000 c000.<BR> Window 7: 0000 0000 0000 0000 0000 0000 0000=20
e000.<BR>Vortex chip registers at 0xec00<BR> 0xEC10: **FIFO** =
00000000=20
00000040 *STATUS*<BR> 0xEC20: 00000020 00000000 00080000=20
00000004<BR> 0xEC30: 00000000 1e4ce1b4 00099060=20
00080004<BR> Indication enable is 06c6, interrupt enable is=20
06de.<BR> No interrupt sources are =
pending.<BR> Transceiver/media=20
interfaces available: 100baseTx 10baseT.<BR>Transceiver type in =
use: =20
100baseTX.<BR> MAC settings: half-duplex.<BR> Station address =
set to=20
00:50:da:66:8d:be.<BR> Configuration options 4000.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>****vortex-diag -e*******</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>vortex-diag.c:v1.09 7/28/99 Donald =
Becker (<A=20
href=3D"mailto:becker@cesdis.gsfc.nasa.gov">becker@cesdis.gsfc.nasa.gov</=
A>)<BR>Index=20
#1: Found a 3c905C Tornado 100baseTx adapter at 0xec00.<BR>Parsing the =
EEPROM of=20
a 3Com Vortex/Boomerang:<BR> 3Com Node Address 00:50:DA:66:8D:BE =
(used as a=20
unique ID only).<BR> OEM Station address 00:50:DA:66:8D:BE (used as =
the=20
ethernet address).<BR> Manufacture date (MM/DD/YYYY) 10/8/1999, =
division H,=20
product BB.<BR>Options: none.<BR> Vortex format checksum is =
incorrect=20
(00e2 vs. 10b7).<BR> Cyclone format checksum is incorrect (0x72 =
vs.=20
0x74).<BR> Hurricane format checksum is incorrect (0x5b vs.=20
0x74).<BR></FONT></DIV>
<DIV><FONT face=3DArial size=3D2> </DIV></FONT>
<DIV><FONT face=3DArial size=3D2>*******vortex-diag =
-m******</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>vortex-diag.c:v1.09 7/28/99 Donald =
Becker (<A=20
href=3D"mailto:becker@cesdis.gsfc.nasa.gov">becker@cesdis.gsfc.nasa.gov</=
A>)<BR>Index=20
#1: Found a 3c905C Tornado 100baseTx adapter at 0xec00.<BR> MII PHY =
found=20
at address 24, status 780d.<BR> MII PHY 0 at #24 transceiver=20
registers:<BR> 3000 780d 0040 6176 05e1 0000 0000=20
0000<BR> 0000 0000 0000 0000 0000 0000 0000 =
0000<BR> =20
1000 0300 0000 0000 0000 0192 0200 0000<BR> 0036 000c 0f00 =
ff40 0026=20
0000 0000 000b.<BR><BR></DIV></FONT>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><BR> </DIV></FONT>
<DIV> </DIV></BODY></HTML>
------=_NextPart_000_004A_01BF9423.3E8A9920--
-------------------------------------------------------------------
To unsubscribe send a message body containing "unsubscribe"
to linux-vortex-bug-request@beowulf.org