Andrey,
I managed to get the EEPro100 back. It's the exact same card, the exact
same problem, but now on pre7-6. It's sitting in eth1, with the ne2k-pci
as eth0. The system boots fine as none of my rc scripts disturb
eth1. ifconfig -a works fine, but don't try to change anything on eth1
... straight lock.
Here's the boot message:
eth1: Intel Corporation 82557 [Ethernet Pro 100], 00:90:27:58:89:F7, IRQ
9.
Reciever lock-up bug exists -- enabling work-around.
Board assembly 721383-006, Physical connectors present: RJ45
Primary interface chip i82555 PHY #1.
General self-test: passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (0x04f4518b).
This motherboard doesn't support PnP, I statically allocated IRQ 9 in the
BIOS. It's on Level/Auto. Devfs is also enabled.
Take care,
d
On Fri, 28 Apr 2000, Andrey Savochkin wrote:
> Daniel,
>
> On Wed, Apr 26, 2000 at 05:27:53AM -0500, Daniel Stone wrote:
> > I'm using an Intel 82559 (EtherExpress PRO/100) and I'm experiencing a
> > strange problem.
> >
> > I went into its setup (Ctrl-S at boot), and disabled its setup message as
> > it was annoying me. I boot Linux with the EEPro PCI driver in for the
> > first time, and BOOM, it hangs halfway through its initialisation. I go
> > back, enable the setup message, and it works.
> >
> > But I have an rc script - ifconfig eth0 down, set its ip, back up. It hung
> > when it got there. I booted into single mode, and found that even though
> > it works, it froze on the first ifconfig.
> >
> > I'm now on a RealTek, and there were NO IRQ conflicts, the card was on IRQ
> > 9, nothing else was using that, as I only have the video card (which has
> > no IRQ) and that's it. It was assigned to IRQ 9 (my mobo doesn't do PnP,
> > you assign PCI IRQs manually) and Edge/Auto - no IRQ sharing.
> >
> > Can anyone shed some light?
>
> During initialization eepro100 driver provides messages about the hardware
> and the initialization process. They are usually stored in your log files by
> klog/syslog system. Could you send me the messages for successful and
> unsuccessful network startup of your system?
>
> Best regards
> Andrey V.
> Savochkin
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun May 07 2000 - 21:00:20 EST