On Sun, Nov 07, 1999 at 12:56:50PM -0500, Michael McKernan wrote:
>
> I'll describe the problem momentarily, but the thing on the top of my
> stack right now is my unsuccessful effort to try to replace the tulip
> driver with the most current one. I am unable to compile the driver
> because of what appears to be a bug in the kernel (2.2.5 and
> 2.2.12). FWIW, I am running RH6.0 on a miata. Here's what I get.
>
> In file included from /usr/include/asm/semaphore.h:11,
> from /usr/include/linux/fs.h:161,
> from /usr/include/linux/capability.h:13,
> from /usr/include/linux/binfmts.h:5,
> from /usr/include/linux/sched.h:8,
> from tulip.c:118:
> usr/include/asm/current.h:4: global register variable follows a function
> definition
> usr/include/asm/current.h:4: warning: call-clobbered register used
> for global register variable
>
> Has noone compiled a tulip driver for these kernels? Since the
> tulip.c in the kernel sources apparently leads to to a current.h
> which is identical, it seems that redhat can. How'd they do that?
>
I haven't had any problems compiling the tulip module on my miata in a
2.2.10 kernel. Though, I use the de4x5 driver instead of the tulip.
I found it to be more reliable for the internal ethernet controller.
>
> Now the original problem. I tried to setup networking as closely as
> possible to what I have on an Intel RH6.1 box (which also uses a
> tulip card) to get a very simple home network. The Intel box seems
> to get along well with a win95 box that I use to pay the bills. I can
> see activity at the hub from the alpha, which is apparently arp
> who-has requests, but nothing else in the network hears anything nor
> can the alpha hear anyone else. Pinging the host under its network
> name works ok. It's quite possible that I have overlooked something,
> and I'd very much appreciate a hint if that's the case.
>
Did you try a different cable and/or port on the hub?
BAPper
