Incorrect IRQ/IO addr. with Zipslack's "tulip" ethernet driver
 

I have an old P1 running Zipslack (Kernel 2.4.?)... works wonderfully... except for the ethernet card. I have the same odd problem described here at linuxquestions.org over and over again - everything seems okay, but can't ping anything (neither on the LAN or the WAN).

I also can run "fli4l" (minimal linux distro) from a floppy, which works fine with my ethernet card (but, unlike slackware, doesn't like my 36GB SCSI drive...)... the only difference I can find between slack and fli4l is that running "ifconfig eth0" displays two different IRQ and IO address numbers (when it is working, running under fli4l, the interrupt is "4" and base address "0x4000". Running under slackware gives me interrupt: 10 and address 0x1200 [plus or minus a zero]).

So, I figured this would be an easy fix - just initialize the tulip driver with manual IRQ/IO settings... right? But alas, the tulip driver does not seem to support this.

My question is, how do I get my ethernet card working under Slack? BIOS doesn't seem to be helping me much - the computer is older, and the BIOS does have a place where I can turn off certain interrupts/etc., but I'm not sure what exactly I need to do.

I think it is most likely that the tulip drivers are two different versions - if there is some way I could replace the slackware tulip driver with the fli4l tulip driver, I wouldn't be surprised if that would fix it - but I am a two-week newbie to Linux, and I really don't know what I am doing yet... I don't have any c complier installed as part of the Zipslack package, otherwise I'd just download the source and compile the latest driver...