eepro100 failure at boot: no resources

[Andrey Savochkin]

Krawl,

You're absolutely right.

The both problems mentioned by you were fixed in 1.20.2.4 revision of the
driver.  Orion uses driver 1.20.2.3 and, certainly, experiences the same
problems as you did.

Orion, please update your driver.
You may take it from the latest 2.2.15 prepatch or from
ftp://ftp.sw.com.sg/pub/Linux/people/saw/kernel/v2.2/

Best regards
					Andrey V.
					Savochkin

On Thu, Apr 27, 2000 at 12:04:18PM -0700, Krawl, Roeland wrote:
> If your boot problem occurs when no network cable is attached (to your
> Ethernet card) then obviously your "No RX buffers" message is not caused as
> a result of receiving too many packets.
> 
> Your boot problem is similar to a problem that I (and a co-worker) found in
> the eepro100.c driver (version 1.09t) when controlling an 82559ER chip.
> 
> The problem was:
> The "wait_for_cmd_done()" routine (in the eepro100 driver) falsely gives the
> impression that the routine waits for command completion. We added an
> additional delay to ensure that the command has been completed before
> changing the contents of the System Control Block General Pointer in
> preparation for the next command.
>  
> 
> I doubt that the above problem has been fixed in the version you are using.
> I tried to report the problem and a suggested fix however Donald Becker did
> not respond to any of the emails sent to him. Andy Savochkin kindly
> responded to a recent email and is aware of the problem report and suggested
> fix.
> 
> Another problem in the driver that is worthy of mention here is:
> The driver is using a SCB status mask of 0xFC00. The Linux driver from Intel
> (recently released) correctly uses a status mask of  0xF300. The status mask
> of 0xFC00 prevents the driver from acknowledging the flow control and early
> receive interrupts in the 82559 chip.
-------------------------------------------------------------------
To unsubscribe send a message body containing "unsubscribe"
to linux-eepro100-request@beowulf.org