On Tue, 11 Jul 2000, Torben Mathiasen wrote:
> 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.
Some BIOS(es) fail to put a usable address in the PCI registers for
some devices. For instance, if you have a shared-memory buffer that
is Nk in length, it must be on a Nk boundary! Some BIOSes ignore this
which may prevent the first portion of an allocated buffer from being
addressed. See if you can get a BIOS upgrade. If not, see if your driver
can take a parameter (using append=) from LILO.
Cheers,
Dick Johnson
Penguin : Linux version 2.2.15 on an i686 machine (797.90 BogoMips).
"Memory is like gasoline. You use it up when you are running. Of
course you get it all back when you reboot..."; Actual explanation
obtained from the Micro$oft help desk.
-
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