On Mon, Jul 10 2000, Mario Mikocevic wrote:
> Well, it seems that #1 and #2 are corelated. Now, here's even more fun things ->
>
> if I boot test2 with OS setting set to OTHER server boots as UP and eepro100 works,
>
> if I boot test3 (pre2, pre5 and pre7 tested) with OS on OTHER server boots as UP but
> eepro100 spits 'eth0: card reports no RX buffers.' with endless slow stream of
> 'eepro100: wait_for_cmd_done timeout!' !?
>
> if I boot any of those test[23] kernels with BIOS OS setting to Unixware (set as 7
> I don't know if it makes difference) server boots as SMP but eepro100 is deaf with
> following errors :
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: Transmit timed out: status e050 0c00 at 0/28 command 0001a000.
>
Okay, first of all, the UP stuff when running with os set to other is normal.
What kind of eepro100 card is this (chip version)? I haven't tried the eepro100
driver for a while, but the driver has been updated quite frequently lately, so
you might want to send this bug report to the maintainer Andrew Savochkin.
Have you tried any of the 2.2.x kernels? Give it a shot, I suspect eepro100 driver
issues. If your eepro works with 2.2.x you could make a hybrid kernel with one
of the eepro driver from 2.3.x (probaly later than 2.3.47).
Also be sure that you adapter is in a pci master capable slot.
I'm sure Andrew knows a lot more about this.
-- Torben Mathiasen <torben.mathiasen@compaq.com> Linux ThunderLAN maintainer http://tlan.kernel.dk My opinions are my own and may not reflect those of my employer- 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 : Sat Jul 15 2000 - 21:00:13 EST