[tulip] Compiling in the tulip driver

[james hill]

I have kernel 2.2.16-22smp install currently. I have installed the
***source*** rpm. I am using RH7.0

> For example, if you have a RedHat 2.2 kernel-source RPM installed,
> (please note ****source****), then since that puts it in
/usr/src/linux
> (against the advice of certain respected people), the switch:

if I use the command 'rpm -ivh kernel-2.2.16-22.src.rpm' this only
places stuff at two locations:

a bunch files goes to /usr/src/redhat/SOURCES and spec files goes to
/usr/src/redhat/SPECS not to /usr/src/linux  There is no directory path
my system such as that either real or symbolic. I tried running the
compiler right the rpm command and it did not work. And after much
fumbling about I came across this article:

http://www.scyld.com/pipermail/tulip/2000-October/002685.html

In the end I have had no luck with ANY "solution" that has been posted
on the this board. Everybody keeps saying this crap about "oh you need
to use this compiler or that compiler" and "use -I/usr/src/linux" or
"-I/usr/src/linux/include"  tag. None of this has worked. I have already
posted what it took to get them to compile. I am not sure I did that
correct.

http://www.tux.org/hypermail/linux-tulip/this-month/0100.html

I have, however, finally gotten those .c files to compile. the only
problem I have now is pci-scan.o has bunch of unresolved symbols and
tulip cannot initialize ie it is reporting device busy. I know my BIOS
is reporting the IRQ to be 10 but linux thinks it's IRQ16 and I don't
know of any way of mapping it. I also have PNP in my BIOS turned-off.
Just so no one is guessing I have a Linksys EtherFast LNE100TX NIC. I
have ran out of Ideas. Any card I go out to buy I will have to compile
the drivers for and I will more then likely run into the same problems.
I guess I could go to another distribution but I may find myself in the
same boat I'm in now. Welcome to World of Linux =)


Your crack smokin' linux buddy

Jimmy

----- Original Message -----
From: "David Shochat" <shochat@acm.org>
To: "james hill" <dragonking7@mediaone.net>
Cc: <tulip@scyld.com>
Sent: Friday, November 24, 2000 12:27 PM
Subject: Re: [tulip] Compiling in the tulip driver


> I should be careful to make it clear what I personally have done. I
have
> done this successfully with:
> 2.2.14-5
> 2.2.16-3
> 2.2.16-21
> (all from RedHat)
> In the last case, I had to take special measures (which have turned
into
> a raging controversy) to make sure that the compile could see the
2.2.16
> kernel headers.
> I guess I'm stepping into a hornet's nest now, but here goes...
>
> Let me try to choose my words very carefully to avoid being flamed.
>
> I suspect that your problem is that the compiler in your case is
picking
> up kernel headers which are other than are needed for this particular
> kernel module to compile correctly. This is because of the nature of
the
> error you say you are getting. If that is true, I think the solution
for
> you is to use a -I switch in your compile command which points to a
> place that contains the 2.2 kernel headers. That is not exactly how I
> did it (I am now ashamed to admit even to my friends and family how I
> actually did it), but I believe it will work.
>
> For example, if you have a RedHat 2.2 kernel-source RPM installed,
> (please note ****source****), then since that puts it in
/usr/src/linux
> (against the advice of certain respected people), the switch:
>
>   -I/usr/src/linux/include
>
> would do it. Othewise, I'll bet you could just get a 2.2 kernel source
> tarfile installed anywhere at all (no need to actually compile the
> kernel) and have your -I point to its include directory.
>
> james hill wrote:
>
> >  >David Shochat (/shochat@acm.org/
> >
<mailto:shochat@acm.org?Subject=Re:%20[tulip]%20Compiling%20in%20the%20t
ulip%20driver&amp;In-Reply-To=&lt;3A1C4422.5020202@acm.org&gt;>)
> > *>Date:* Wed Nov 22 2000 - 17:09:38 EST  wrote:
> >
> >  >That's a novel approach and maybe there's a way  to make it work.
> > But if
> >  >you just want to get things working, here is how  I did it:
> >  >1. With the kernel built and running normally (using only  drivers
that
> >  >came with it), copy those 4 files into some random  directory.
> >  >2. compile them using the compile commands that you will find  in
> > the .c
> >  >source files.
> >  >3. (as root) Copy pci-scan.o and tulip.o  into /lib/modules/`uname
> >  >-r`/net [you may want to rename the tulip.o  that may have been
built
> >  >with your kernel first if you don't want to  clobber it, but that
> > tulip.o
> >  >has never worked for me]
> >  >4. depmod  -a
> >  >5. modprobe tulip
> >  >6. If all goes well you can try bringing up  the interface.
> >  >7. And put alias eth<n> tulip in /etc/modules.conf  for
automation.
> >
> > In item 1 are you talking about  installation/distribution? If so
> > which one and what kernel version?
> >
> > Because, if a try using that I get 'member not  found tbusy, start,
> > interrupt' when I go to compile.
> >
>
>