Under 32bit the tulip driver works fine, but under 64 bit it gives me a
lot if problems. I updated the tulip
to what is in the current repository, and the issue still exists. Any
suggestions.
First off it continually sends data out the network interface and never
negotiates is speed and duplex.
Second in the log files all I see is an uninformative message
0000:00:07.0: tulip_stop_rxtx() failed
Here is all the bootup information differences I can find on the driver
64 bit
Dec 31 16:01:29 lfs tulip0: ***WARNING***: No MII transceiver found!
Dec 31 16:01:29 lfs tulip1: ***WARNING***: No MII transceiver found!
32 bit
Dec 31 16:01:16 lfs tulip0: MII transceiver #1 config 1000 status 7809
advertising 01e1
Dec 31 16:01:16 lfs tulip1: MII transceiver #1 config 1000 status 7809
advertising 01e1.
Complete boot log - yes I know the date and time are off.
Under a 64 bit compile
Dec 31 16:01:29 lfs Linux Tulip driver version 1.1.13 (May 11, 2002)
Dec 31 16:01:29 lfs PCI: Enabling device 0000:00:07.0 (0045 -> 0047)
Dec 31 16:01:29 lfs tulip0: Old format EEPROM on 'Cobalt Microserver'
board. Using substitute media control info.
Dec 31 16:01:29 lfs tulip0: EEPROM default media type Autosense.
Dec 31 16:01:29 lfs tulip0: Index #0 - Media MII (#11) described by a
21142 MII PHY (3) block.
Dec 31 16:01:29 lfs tulip0: ***WARNING***: No MII transceiver found!
Dec 31 16:01:29 lfs eth0: Digital DS21143 Tulip rev 65 at
ffffffffb0001400, 00:10:E0:00:32:DE, IRQ 19.
Dec 31 16:01:29 lfs PCI: Enabling device 0000:00:0c.0 (0005 -> 0007)
Dec 31 16:01:29 lfs tulip1: Old format EEPROM on 'Cobalt Microserver'
board. Using substitute media control info.
Dec 31 16:01:29 lfs tulip1: EEPROM default media type Autosense.
Dec 31 16:01:29 lfs tulip1: Index #0 - Media MII (#11) described by a
21142 MII PHY (3) block.
Dec 31 16:01:29 lfs tulip1: ***WARNING***: No MII transceiver found!
Dec 31 16:01:29 lfs eth1: Digital DS21143 Tulip rev 65 at
ffffffffb0001480, 00:10:E0:00:32:DF, IRQ 20.
Dec 31 16:01:29 lfs bootlog: Bringing up the eth0 interface...[ OK ]
Dec 31 16:01:30 lfs bootlog: Adding IPv4 address 172.16.0.99 to the
eth0 interface...[ OK ]
Dec 31 16:01:31 lfs bootlog: Setting up default gateway...[ OK ]
Dec 31 16:01:32 lfs 0000:00:07.0: tulip_stop_rxtx() failed
Dec 31 16:01:38 lfs 0000:00:07.0: tulip_stop_rxtx() failed
Dec 31 16:01:44 lfs 0000:00:07.0: tulip_stop_rxtx() failed
Dec 31 16:01:50 lfs 0000:00:07.0: tulip_stop_rxtx() failed
Dec 31 16:01:56 lfs 0000:00:07.0: tulip_stop_rxtx() failed
Dec 31 16:02:02 lfs 0000:00:07.0: tulip_stop_rxtx() failed
Dec 31 16:02:08 lfs 0000:00:07.0: tulip_stop_rxtx() failed
Under 32 bit
Dec 31 16:01:16 lfs Linux Tulip driver version 1.1.13 (May 11, 2002)
Dec 31 16:01:16 lfs PCI: Enabling device 0000:00:07.0 (0045 -> 0047)
Dec 31 16:01:16 lfs tulip0: Old format EEPROM on 'Cobalt Microserver'
board. Using substitute media control info.
Dec 31 16:01:16 lfs tulip0: EEPROM default media type Autosense.
Dec 31 16:01:16 lfs tulip0: Index #0 - Media MII (#11) described by a
21142 MII PHY (3) block.
Dec 31 16:01:16 lfs tulip0: MII transceiver #1 config 1000 status 7809
advertising 01e1.
Dec 31 16:01:16 lfs eth0: Digital DS21143 Tulip rev 65 at b0001400,
00:10:E0:00:32:DE, IRQ 19.
Dec 31 16:01:16 lfs tulip1: Old format EEPROM on 'Cobalt Microserver'
board. Using substitute media control info.
Dec 31 16:01:16 lfs tulip1: EEPROM default media type Autosense.
Dec 31 16:01:16 lfs tulip1: Index #0 - Media MII (#11) described by a
21142 MII PHY (3) block.
Dec 31 16:01:16 lfs tulip1: MII transceiver #1 config 1000 status 7809
advertising 01e1.
Dec 31 16:01:16 lfs eth1: Digital DS21143 Tulip rev 65 at b0001480,
00:10:E0:00:32:DF, IRQ 20.
Dec 31 16:01:17 lfs bootlog: Bringing up the eth0 interface...[ OK ]
Dec 31 16:01:17 lfs bootlog: Adding IPv4 address 172.16.0.99 to the
eth0 interface...[ OK ]
Dec 31 16:01:18 lfs bootlog: Setting up default gateway...[ OK ]
Dec 31 16:01:20 lfs eth0: Setting full-duplex based on MII#1 link
partner capability of 45e1.
--
----
Jim Gifford
[email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]