[tulip] RH7.0 issues with tulip.c and problems the new web site does not for me
james hill
dragonking7@mediaone.net
Fri, 24 Nov 2000 02:30:28 -0500
This is a multi-part message in MIME format.
------=_NextPart_000_0074_01C055BE.822E6640
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Special instructions for Red Hat 7.0
Red Hat 7.0 has a flawed configuration with their default install. It =
uses the header files from an unreleased 2.3.99 kernel, rather than =
installing the header files from the kernel that is actually running. =
While this likely seemed like a good idea to someone, it makes it =
impossible to automatically build kernel modules.=20
A second problem is that 7.0 provides an experiment version of gcc that =
was not intended for public release. The stable version of gcc needed to =
correctly compile the kernel has been renamed to kgcc.=20
The work-around is to substitute kgcc for gcc and to add =
-I/usr/src/linux/include on the compile command line when compiling by =
hand. The Makefile in the tar file and RPM automatically include this =
compile flag, however they cannot automatically use 'kgcc'.=20
To repeat: this is a flaw that was introduced with Red Hat 7.0. It is a =
Red Hat configuration problem, not a driver=20
This does not work. Everybody keeps saying it but it does not work. =
RH7.0 default source location after 'rpm -ivh' for the kernel is =
/usr/src/redhat/SOURCES but then you have to run the SPEC file which =
under /usr/src/redhat/SPECS to get all the header files even then you =
have to make modifications to it to get it to work right. NO sym link is =
created. So -I/usr/src/include/linux should be =
-I/usr/src/redhat/BUILD/linux/include and I still get problems when =
compiling the .c files because it does not like my modversions.h The =
only way I have been able to get these drivers to compile is by creating =
an empty modversions.h file. Now that I have them compiled I getting =
unresolved symbols when I try to install.
Maybe I am smoking crack but I have not been successful at getting these =
drivers at all.=20
I have been reading these boards religiously for two weeks now I even =
went back read aug, sept, oct, this month's posts nothing has worked. =
Anybody know of another NIC something a NIC -----> USB that has linux =
drivers or better yet a NIC that is already supported.
Your crack smokin' linux buddy
Jimmy
------=_NextPart_000_0074_01C055BE.822E6640
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 bgColor=3D#486c88>
<DIV>
<H2><EM><FONT face=3DArial size=3D1>Special instructions for Red Hat=20
7.0</FONT></EM></H2>
<P><EM><FONT face=3DArial size=3D1>Red Hat 7.0 has a flawed =
configuration with their=20
default install. It uses the header files from an unreleased 2.3.99 =
kernel,=20
rather than installing the header files from the kernel that is actually =
running. While this likely seemed like a good idea to someone, it makes =
it=20
impossible to automatically build kernel modules. </FONT></EM>
<P><EM><FONT face=3DArial size=3D1>A second problem is that 7.0 provides =
an=20
experiment version of <TT>gcc</TT> that was not intended for public =
release. The=20
stable version of <TT>gcc</TT> needed to correctly compile the kernel =
has been=20
renamed to <TT>kgcc</TT>. </FONT></EM>
<P><EM><FONT face=3DArial size=3D1>The work-around is to substitute =
<TT>kgcc</TT>=20
for <TT>gcc</TT> and to add <TT>-I/usr/src/linux/include</TT> on the =
compile=20
command line when compiling by hand. The <TT>Makefile</TT> in the tar =
file and=20
RPM automatically include this compile flag, however they cannot =
automatically=20
use 'kgcc'. </FONT></EM>
<P><EM><FONT face=3DArial size=3D1>To repeat: this is a flaw that was =
introduced=20
with Red Hat 7.0. It is a Red Hat configuration problem, not a driver=20
</FONT></EM></P>
<P><FONT face=3D"Lucida Console" size=3D2></FONT> </P>
<P><FONT face=3DArial size=3D2>This does not work. Everybody keeps =
saying it but it=20
does not work. RH7.0 default source location after 'rpm -ivh' for =
the=20
kernel is /usr/src/redhat/SOURCES but then you have to run the SPEC file =
which=20
under /usr/src/redhat/SPECS to get all the header files even=20
then you have to make modifications to it to get it to work right. =
NO sym=20
link is created. So -I/usr/src/include/linux should be=20
-I/usr/src/redhat/BUILD/linux/include and I still =
get=20
problems when compiling the .c files because it does not like my=20
modversions.h The only way I have been able to get =
these drivers to=20
compile is by creating an empty modversions.h file. Now that I =
have them=20
compiled I getting unresolved symbols when I try to install.</FONT></P>
<P><FONT face=3DArial size=3D2>Maybe I am smoking crack but I have not =
been=20
successful at getting these drivers at all. </FONT></P>
<P><FONT face=3DArial size=3D2></FONT> </P>
<P><FONT face=3DArial size=3D2>I have been reading these boards =
religiously=20
for two weeks now I even went back read aug, sept, oct, this =
month's posts=20
nothing has worked. Anybody know of another NIC something a NIC =
----->=20
USB that has linux drivers or better yet a NIC that is already=20
supported.</FONT></P>
<P><FONT face=3DArial size=3D2>Your crack smokin' linux buddy</FONT></P>
<P><FONT face=3DArial size=3D2>Jimmy</FONT></P>
<P><FONT face=3DArial size=3D2></FONT> </P>
<P><FONT face=3DArial size=3D2></FONT> </P>
<P><FONT face=3DArial size=3D2></FONT> </P>
<P><FONT face=3D"Lucida Console" =
size=3D2></FONT> </P></DIV></BODY></HTML>
------=_NextPart_000_0074_01C055BE.822E6640--