mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Meelis Roos <mroos@linux.ee>
To: Scott Feldman <sfeldma@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANN] removal of certain net drivers coming soon: eepro100,?xircom_tulip_cb, iph5526
Date: Tue, 1 Feb 2005 14:48:09 +0200 (EET)	[thread overview]
Message-ID: <Pine.SOC.4.61.0502011444310.26768@math.ut.ee> (raw)
In-Reply-To: <1106939504.18167.364.camel@localhost.localdomain>

> See if eepro100 works on your 82556 cards.  I would be surprised if it
> does.  If it does, maybe it's not that much trouble to add support to
> e100.  Let us know.

I did add the PCI ID to e100 to to try it with both drivers.

In short: both eepro100 and e100 have problems loading the eeprom and 
don't work at least out of the box.

Here is the dmesg, first card is onboard e100, 0000:01:0c.0 and 
0000:01:0d.0 are the 82556's.

e100: Intel(R) PRO/100 Network Driver, 3.3.6-k2-NAPI
e100: Copyright(c) 1999-2004 Intel Corporation
ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI interrupt 0000:01:08.0[A] -> GSI 11 (level, low) -> IRQ 11
e100: eth0: e100_probe: addr 0xff8fe000, irq 11, MAC addr 00:03:47:A4:64:D5
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 9
PCI: setting IRQ 9 as level-triggered
ACPI: PCI interrupt 0000:01:0c.0[A] -> GSI 9 (level, low) -> IRQ 9
e100: 0000:01:0c.0: e100_eeprom_load: EEPROM corrupted
e100: probe of 0000:01:0c.0 failed with error -11
ACPI: PCI Interrupt Link [LNKF] enabled at IRQ 11
ACPI: PCI interrupt 0000:01:0d.0[A] -> GSI 11 (level, low) -> IRQ 11
e100: 0000:01:0d.0: e100_eeprom_load: EEPROM corrupted
e100: probe of 0000:01:0d.0 failed with error -11

[...]

eepro100.c:v1.09j-t 9/29/99 Donald Becker 
http://www.scyld.com/network/eepro100.html
eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <saw@saw.sw.com.sg> and others
ACPI: PCI interrupt 0000:01:0c.0[A] -> GSI 9 (level, low) -> IRQ 9
eth1: Invalid EEPROM checksum 0x0000, check settings before activating this device!
eth1: 0000:01:0c.0, 00:00:00:00:00:00, IRQ 9.
   Receiver lock-up bug exists -- enabling work-around.
   Board assembly 000000-000, Physical connectors present:
   Primary interface chip None PHY #0.
Self test failed, status ffffffff:
  Failure to initialize the i82557.
  Verify that the card is a bus-master capable slot.
   Receiver lock-up workaround activated.
ACPI: PCI interrupt 0000:01:0d.0[A] -> GSI 11 (level, low) -> IRQ 11
eth2: Invalid EEPROM checksum 0x0000, check settings before activating this device!
eth2: 0000:01:0d.0, 00:00:00:00:00:00, IRQ 11.
   Receiver lock-up bug exists -- enabling work-around.
   Board assembly 000000-000, Physical connectors present:
   Primary interface chip None PHY #0.
Self test failed, status ffffffff:
  Failure to initialize the i82557.
  Verify that the card is a bus-master capable slot.
   Receiver lock-up workaround activated.
  mdio_read() timed out with val = 00000028.
  mdio_read() timed out with val = 00000028.
  mdio_read() timed out with val = 00000028.
  mdio_read() timed out with val = 00000028.
  mdio_read() timed out with val = 00000028.
  mdio_read() timed out with val = 00000028.
  mdio_read() timed out with val = 00000028.
  mdio_read() timed out with val = 00000028.
  mdio_read() timed out with val = 00000028.
  mdio_read() timed out with val = 00000028.

-- 
Meelis Roos (mroos@linux.ee)

  reply	other threads:[~2005-02-01 12:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-27 20:45 [ANN] removal of certain net drivers coming soon: eepro100, xircom_tulip_cb, iph5526 Jeff Garzik
2005-01-27 21:07 ` Christoph Hellwig
2005-02-06 18:44   ` [2.6 patch] kill IPHASE5526 Adrian Bunk
2005-01-27 22:57 ` [ANN] removal of certain net drivers coming soon: eepro100, xircom_tulip_cb, iph5526 Russell King
2005-01-27 23:31   ` David S. Miller
2005-01-28  0:14     ` Russell King
2005-01-28  0:48       ` Lennert Buytenhek
2005-01-28  0:48       ` David S. Miller
2005-01-28  1:58         ` Scott Feldman
2005-01-28  5:22           ` David S. Miller
2005-01-28  9:33           ` [ANN] removal of certain net drivers coming soon: eepro100,?xircom_tulip_cb, iph5526 Meelis Roos
2005-01-28 19:11             ` Scott Feldman
2005-02-01 12:48               ` Meelis Roos [this message]
2005-02-01 18:57                 ` Scott Feldman
2005-02-01 19:09                   ` linux-os
2005-02-01 19:28                     ` Scott Feldman
2005-01-29  8:17 ` [ANN] removal of certain net drivers coming soon: eepro100, xircom_tulip_cb, iph5526 Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.SOC.4.61.0502011444310.26768@math.ut.ee \
    --to=mroos@linux.ee \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfeldma@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome