FREESCO v0.4.x & HP Compaq Business Desktop D530 USDT

Support section for FREESCO v0.4.x

Re: FREESCO v0.4.x & HP Compaq Business Desktop D530 USDT

Postby Lightning » Wed Dec 28, 2011 9:16 pm

Ethernet controller: DEC DC21140 (rev 34)
So the reality is that the chip set is really a DEC DC21140. Which both tulip and the de4x5 drivers fully support. So either driver should work without any issues. Which I would still recommend starting with the de4x5 driver, but I would double check throughput with both drivers just to see if there might be a difference somewhere. The tulip driver is a much more developed driver than the DEC driver and it might have extra testing for different registers. Looking at the source of the DEC driver there are tons of various fixes listed for the 21140 chip, so it could still be a better driver though. Only testing can really answer which one might be better for the Digital Electronics Corporation chip.
If you are afraid that you might make a mistake. The chances are high that you will never learn anything.
User avatar
Lightning
FREESCO GOD !!
 
Posts: 12079
Joined: Wed Nov 14, 2001 6:50 am
Location: Oregon, USA

Re: FREESCO v0.4.x & HP Compaq Business Desktop D530 USDT

Postby free » Thu Dec 29, 2011 5:29 pm

I did tests with both drivers.
With tulip driver at startup disturbs me the following:
----- dmesg | sed -n /eth/P -----
eth0: Digital DS21140 Tulip at 0x1000, 00 e0 29 XX XX XX, IRQ 11.
eth0: EEPROM default media type Autosense.
eth0: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block.
eth0: MII transceiver #3 config 3100 status 786b advertising 01e1.
eth1: Digital DS21140 Tulip at 0x1080, 00 e0 29 YY YY YY, IRQ 10.
eth1: EEPROM default media type Autosense.
eth1: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block.
eth1: MII transceiver #3 config 3100 status 786b advertising 01e1.
eth1: Advertising 01e1 on PHY 0 (3).
eth0: Advertising 01e1 on PHY 0 (3).
eth1: The transmitter stopped! CSR5 is fc068002, CSR6 320e0202.
eth1: Setting full-duplex based on MII Xcvr #3 parter capability of 45e1.
eth0: The transmitter stopped! CSR5 is fc068002, CSR6 320e0202.
eth0: Setting full-duplex based on MII Xcvr #3 parter capability of 45e1.

----- ifconfig -----
eth0 Link encap:Ethernet HWaddr 00:E0:29:XX:XX:XX
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5181384 errors:0 dropped:0 overruns:0 frame:0
TX packets:3702751 errors:135 dropped:0 overruns:0 carrier:135
collisions:0 Interrupt:11 Base address:0x1000
eth1 Link encap:Ethernet HWaddr 00:E0:29:YY:YY:YY
inet addr:80.253.56.49 Bcast:80.253.56.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4786926 errors:0 dropped:0 overruns:0 frame:0
TX packets:6118094 errors:170 dropped:0 overruns:0 carrier:170
collisions:0 Interrupt:10 Base address:0x1080
lo Link encap:Local Loopback
inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1
RX packets:308 errors:0 dropped:0 overruns:0 frame:0
TX packets:308 errors:0 dropped:0 overruns:0 carrier:0
collisions:0

With de4x5 driver at startup is better:
----- dmesg | sed -n /eth/P -----
eth0: DC21140 at 0x1000 (PCI bus 6, device 4), h/w address 00:E0:29:XX:XX:XX,
eth1: DC21140 at 0x1080 (PCI bus 6, device 5), h/w address 00:E0:29:YY:YY:YY,
eth1: media is 100Mb/s full duplex.
eth0: media is 100Mb/s full duplex.

----- ifconfig -----
eth0 Link encap:Ethernet HWaddr 00:E0:29:XX:XX:XX
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10269829 errors:0 dropped:0 overruns:0 frame:0
TX packets:9153490 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 Interrupt:11 Base address:0x1000
eth1 Link encap:Ethernet HWaddr 00:E0:29:YY:YY:YY
inet addr:80.253.56.49 Bcast:80.253.56.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9811926 errors:0 dropped:0 overruns:0 frame:0
TX packets:10838147 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 Interrupt:10 Base address:0x1080
lo Link encap:Local Loopback
inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1
RX packets:546 errors:0 dropped:0 overruns:0 frame:0
TX packets:546 errors:0 dropped:0 overruns:0 carrier:0
collisions:0

I am currently testing de4x5 driver.
User avatar
free
Junior Member
 
Posts: 33
Joined: Sun Feb 26, 2006 8:13 pm
Location: Bulgaria

Re: FREESCO v0.4.x & HP Compaq Business Desktop D530 USDT

Postby Lightning » Thu Dec 29, 2011 7:42 pm

The one thing that I see from the Tulip driver is "carrier:170" on eth0. Which the DEC driver has sent more packets and shows "carrier: 0". As for the rest of it, the thing to understand is that the standard drivers have the debugging code enabled and the Tulip driver is probably just giving extra information about what actions it is taking and most likely in order to test for full duplex it needs to stop the transmitter first. So if you don't see any problems with the DEC driver it will definitely save some kernel memory and it does look a lot cleaner at start up and does not seem to have any packet errors.

On the built in drivers I removed all of the debugging code to make them look better at start up and the extra information is almost completely superfluous. Of course it also saved almost 5K of disk space as well. :wink:
If you are afraid that you might make a mistake. The chances are high that you will never learn anything.
User avatar
Lightning
FREESCO GOD !!
 
Posts: 12079
Joined: Wed Nov 14, 2001 6:50 am
Location: Oregon, USA

Previous

Return to FREESCO Support for v0.4.x

Who is online

Users browsing this forum: No registered users and 3 guests

cron