> On Sun, Sep 10, 2000 at 03:50:20AM -0700, Nick Willson wrote: > > > Here is result of "modprobe tulip": > > /lib/modules/2.2.17/net/tulip.o: init_module: Device or resource busy > > Hint: this error can be caused by incorrect module parameters, including > > invalid IO or IRQ parameters > > /lib/modules/2.2.17/net/tulip.o: insmod /lib/modules/2.2.17/net/tulip.o > > failed > > /lib/modules/2.2.17/net/tulip.o: insmod tulip failed > > Are you sure your card works with the tulip-module? > If yes, try the "old_tulip" module instead of "tulip" during > kernel-configuration. >
I seem to have V2.0 of the same model of card in my own PC, working happily with tulip and a 2.2.17 kernel. The problem was with a 4.1 card. I tried old_tulip also, but got the same result I think (don't have access to the machine now). > > hda: QUANTUM FIREBALLP LM20.5, 19595MB w/1900kB Cache, CHS=2498/255/63 > > hdc: ATAPI 48X CD-ROM drive, 128kB Cache > > Looks like you have not activated UDMA. Have a look at #man hdparm > Thanks > Phil > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > -- Nick
