[tulip] Compiling in the tulip driver
james hill
dragonking7@mediaone.net
Fri, 24 Nov 2000 10:17:40 -0500
This is a multi-part message in MIME format.
------=_NextPart_000_00A2_01C055FF.C67435A0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
>David Shochat (shochat@acm.org)
>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:=20
>1. With the kernel built and running normally (using only drivers that=20
>came with it), copy those 4 files into some random directory.=20
>2. compile them using the compile commands that you will find in the .c =
>source files.=20
>3. (as root) Copy pci-scan.o and tulip.o into /lib/modules/`uname=20
>-r`/net [you may want to rename the tulip.o that may have been built=20
>with your kernel first if you don't want to clobber it, but that =
tulip.o=20
>has never worked for me]=20
>4. depmod -a=20
>5. modprobe tulip=20
>6. If all goes well you can try bringing up the interface.=20
>7. And put alias eth<n> tulip in /etc/modules.conf for automation.=20
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.
Thanks=20
Jimmy
------=_NextPart_000_00A2_01C055FF.C67435A0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4207.2601" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2>>David Shochat (</FONT><A=20
href=3D"mailto:shochat@acm.org?Subject=3DRe:%20[tulip]%20Compiling%20in%2=
0the%20tulip%20driver&In-Reply-To=3D<3A1C4422.5020202@acm.org>"><EM><=
FONT=20
face=3DArial size=3D2>shochat@acm.org</FONT></EM></A><FONT face=3DArial=20
size=3D2>)<BR><STRONG>>Date:</STRONG> Wed Nov 22 2000 - 17:09:38 EST=20
wrote:</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>>That's a novel approach and maybe =
there's a way=20
to make it work. But if <BR>>you just want to get things working, =
here is how=20
I did it: <BR>>1. With the kernel built and running normally (using =
only=20
drivers that <BR>>came with it), copy those 4 files into some random=20
directory. <BR>>2. compile them using the compile commands that you =
will find=20
in the .c <BR>>source files. <BR>>3. (as root) Copy pci-scan.o and =
tulip.o=20
into /lib/modules/`uname <BR>>-r`/net [you may want to rename the =
tulip.o=20
that may have been built <BR>>with your kernel first if you don't =
want to=20
clobber it, but that tulip.o <BR>>has never worked for me] <BR>>4. =
depmod=20
-a <BR>>5. modprobe tulip <BR>>6. If all goes well you can try =
bringing up=20
the interface. <BR>>7. And put alias eth<n> tulip in =
/etc/modules.conf=20
for automation. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>In item 1 are you talking about=20
installation/distribution? If so which one and what kernel =
version?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Because, if a try using that I get =
'member not=20
found tbusy, start, interrupt' when I go to compile.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Thanks </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Jimmy</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial><BR><FONT =
size=3D2></FONT></FONT> </DIV></BODY></HTML>
------=_NextPart_000_00A2_01C055FF.C67435A0--