On Sat, Dec 16, 2000 at 04:12:19PM -0500, Juan Fuentes wrote:
> Hi Mike i had a problem with modversion.h not being found, is this part of
> your problem? There is another issue, and that is that IIRC, the kernel
Actually, it turns out that the sourcecode was kept on a vfat system, so
it was
* Michael P. Soulier ([EMAIL PROTECTED]) wrote:
> Actually, I went to the linksys site, and I followed their incorrect
> instructions that don't quite lead you to all the headers you need, and I'm
> getting a compile error from the latest tulip source.
>
> I got it from here:
>
> ftp://
"Michael P. Soulier" wrote:
>
> Actually, I went to the linksys site, and I followed their incorrect
> instructions that don't quite lead you to all the headers you need, and I'm
> getting a compile error from the latest tulip source.
>
> I got it from here:
>
> ftp://ftp.scyld.com/pub/ne
On Sat, Dec 16, 2000 at 02:22:24PM -0500, David Bellows wrote:
>
> I have the same card. The tulip drivers that come with kernel don't
> work for me either and I tried several different kernel versions. My
> Linksys actually came with a Linux driver floppy. The driver was called
> tulip. I com
"Michael P. Soulier" wrote:
>
> Hi guys. I just put 2 Linksys NICs in a Slink box that I'm going to
> upgrade if I can get them working. It's going to be my gateway. Now, the docs
> say to use the tulip driver, but I just get a "device or resource busy&q
Hi guys. I just put 2 Linksys NICs in a Slink box that I'm going to
upgrade if I can get them working. It's going to be my gateway. Now, the docs
say to use the tulip driver, but I just get a "device or resource busy" error
from that indicating it's the wrong driver.
6 matches
Mail list logo