Hey Guys,

Just wanted to report a problem with the tulip driver. Alexander perhaps you know more about this...

Anyway, using a livecd built from very recent trunk, it loads the tulip driver for my network card:

tulip0:  EEPROM default media type Autosense.
tulip0:  Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block.
tulip0: Index #1 - Media 10baseT (#0) described by a 21140 non-MII (0) block. tulip0: Index #2 - Media 100baseTx (#3) described by a 21140 non-MII (0) block. tulip0: Index #3 - Media 10baseT-FDX (#4) described by a 21140 non-MII (0) block. tulip0: Index #4 - Media 100baseTx-FDX (#5) described by a 21140 non-MII (0) block.
tulip0:  MII transceiver #1 config 3100 status 7809 advertising 01e1.
eth0: Davicom DM9102/DM9102A rev 49 at 0001ec00, 00:80:AD:D0:6A:C4, IRQ 18.
eth0: Setting full-duplex based on MII#1 link partner capability of 45e1.

However, after some time, the card stops working - the network connection sort of freezes. If I 'rmmod tulip' and then 'modprobe dmfe' and restart the network, everything works and is stable. So, apparently dmfe is the correct driver:

dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
ACPI: PCI Interrupt 0000:02:09.0[A] -> GSI 18 (level, low) -> IRQ 18
eth0: Davicom DM9102 at pci0000:02:09.0, 00:80:ad:d0:6a:c4, irq 18.

Any ideas on what we should do about this?

--
JH
--
http://linuxfromscratch.org/mailman/listinfo/livecd
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to