[olug] Problems with setting up NICs

Brian Roberson roberson at bstc.net
Tue Oct 30 12:04:50 UTC 2001 

the file you are trying to compile is a kernel module which needs the rest
of the kernel in place to have all the correct includes/ifdef's/ etc.... If
you are wanting to stay "stock"  you may want to do some searching on
redhat's site, the issue you are having I am sure others have had and it is
in the erratta/other documentation. If you are willing to "just fix it" grab
the kernel source rpm, install it and recompile the modules ( If you are
sticking with the standard kernel, you can just remake the modules you wish
and load them normally, you dont have to recompile the kernel )


----- Original Message -----
From: "Don Kauffman" <dkauffman at tconl.com>
To: <olug at bstc.net>
Sent: Monday, October 29, 2001 10:57 PM
Subject: Re: [olug] Problems with setting up NICs


> Hello,
>
> I'm still not up and running with the NIC's on the Linux box. I found that
the
> pci_scan module does not compile with the 2.2 kernel.  (Thanks, Mike for
warning
> me.) I've located several copies of the 8139too.c module for 2.2.  I've
not
> found a way to get a clean compile nor have I been able to find any
instructions
> on compiling this. There is a very strange "construction" that looks
something
> like this:
>
> #ifdef RTL8139_NDEBUG
> #define assert(expr) do {} while (0)
> #else
> #define assert(expr)
>         if(!(expr)) {
>         printk( "Assertion failed! %s,%s,%s,line=%d\n",
>         #expr,__FILE__,__FUNCTION__,__LINE__);
>         }
> #endif
> I get this warning on this line: 8139too.c:174:57: invalid preprocessing
> directive #expr
>
> I'm a newbie to C so I don't know what is happening or what is supposed to
be
> here.  I'm attemtping to use gcc to compile because there was no makefile.
This
> is the problem with using source that doesn't come with a distribution I'm
> guessing --  I didn't get all the goodies with it. Does anyone have any
> suggestions? I'd be willing to bring the box to the next OLUG meeting if
anyone
> would be able to assist in installing  this driver and is planning to be
there.
>
> Thanks for all the help!
>
> Don
>
> Mike Peterson wrote:
>
> > I have seen the pci_scan module referenced before also.
> > It was for netgear FA 312 cards.
> > I am not positive, but I think it is a 2.4 kernel module.
> > The 2.2.19 kernel with coyote does not contain the pci_scan but has the
> > 8139too.
> > Let us know when  you get it working.
> >
> > ----- Original Message -----
> > From: "Don Kauffman" <dkauffman at tconl.com>
> > To: <olug at bstc.net>
> > Sent: Friday, October 26, 2001 11:24 AM
> > Subject: Re: [olug] Problems with setting up NICs
> >
> > > It  is apparently not included with RH 7.0. I'm running the 2.2.16-22
> > Kernel.
> > > I'd prefer to get comfortable with this setup before I start upgrading
> > kernels.
> > > I''ve installed other distributions  but found that  RedHat 7.0 has
what I
> > need
> > > and want in a multipurpose system -- for the most part. This  little
> > problem
> > > being one of the OTHER parts. :-(
> > >
> > > I'm going to have a try at compiling the stuff I need for this driver.
> > It's a
> > > little more complicated  than just one simple driver. Apparently there
is
> > a scan
> > > module (pci-scan.o) that needs to be compiled as well.
> > >
> > > Thanks all!
> > >
> > > Don
> > > Mike Peterson wrote:
> > >
> > > > What release of Redhat or Linux distribution are you running again?
> > > >
> > > > It is not included with Redhat 6.2.
> > > >
> > > > It is included with Redhat 7.1
> > > > It is located in lib/modules/2.4.2-2/kernel/drivers/net
> > > > It has a date of Apr 8, 2001.
> > > > Size is 26356
> > > >
> > > > The 8139too.o driver is included in Coyote Linux 1.30 and 1.31.
> > > >
> > > > www.coyotelinux.com
> > > >
> > > > Coyote uses the 2.2.19 kernel so the drivers could work with Redhat
6.x.
> > > >
> > > > ----- Original Message -----
> > > > From: "Don Kauffman" <dkauffman at tconl.com>
> > > > To: <olug at bstc.net>
> > > > Sent: Friday, October 26, 2001 9:55 AM
> > > > Subject: Re: [olug] Problems with setting up NICs
> > > >
> > > > > I found a later version of the rtl8139 driver and downloaded the
> > source.
> > > > I'll
> > > > > give  a try at  compiling that. I may be back though.
> > > > >
> > > > > Now, I wasn't able to find the 8139too.o either on the systerm or
on
> > the
> > > > net.
> > > > > Do you know where I can find it?
> > > > >
> > > > > Thanks all!
> > > > >
> > > > > Don
> > > > > Mike Peterson wrote:
> > > > >
> > > > > > The dlink cards also use 8139too and not rtl8139 for the driver.
> > > > > >
> > > > > > -----Original Message-----
> > > > > > From: Phil Brutsche [mailto:phil at giedi.obix.com]
> > > > > > Sent: Thursday, October 25, 2001 5:40 PM
> > > > > > To: olug at bstc.net
> > > > > > Subject: Re: [olug] Problems with setting up NICs
> > > > > >
> > > > > > Don Kauffman wrote:
> > > > > >
> > > > > > > Hello,
> > > > > > >
> > > > > > > I've run into a problem trying to install two DLink DFE-530TX+
> > NICs w/
> > > > > >
> > > > > > > the RealTek Chipset rtl8139
> > > > > >
> > > > > >        ^^^^^^^^^^^^^^^^^^^^^^^
> > > > > >
> > > > > > > append="eth=0,0,eth0,eth=0,0,eth1"
> > > > > >   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > > > > >
> > > > > > RTL8139-based ethernet cards are PCI; the IO port and IRQ are
> > > > automatically
> > > > > > assigned by the BIOS at system boot.  The IO port and IRQ are
also
> > > > > > automatically determined by the driver when it loads.
> > > > > >
> > > > > > The "append=..." line in your lilo.conf is the source of your
> > trouble.
> > > > > > Remove it, re-run lilo, then reboot.
> > > > > >
> > > > > > The only time you need to include that line is if you're using a
> > legacy
> > > > > > kernel (ie < 2.4.x) and/or you're using ISA ethernet cards that
> > don't
> > > > have
> > > > > > an ISAPNP setting.
> > > > > >
> > > > > > Phil
> > > > > >
> > > > > > -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
> > > > > >
> > > > > > For help contact olug-help at bstc.net - run by ezmlm
> > > > > > to unsubscribe, send mail to olug-unsubscribe at bstc.net
> > > > > > or `mail olug-unsubscribe at bstc.net < /dev/null`
> > > > > > (c)2001 OLUG http://www.olug.org
> > > > > >
> > > > > > -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
> > > > > >
> > > > > > -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
> > > > > >
> > > > > > For help contact olug-help at bstc.net - run by ezmlm
> > > > > > to unsubscribe, send mail to olug-unsubscribe at bstc.net
> > > > > > or `mail olug-unsubscribe at bstc.net < /dev/null`
> > > > > > (c)2001 OLUG http://www.olug.org
> > > > > >
> > > > > > -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
> > > > >
> > > > >
> > > > > -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
> > > > >
> > > > > For help contact olug-help at bstc.net - run by ezmlm
> > > > > to unsubscribe, send mail to olug-unsubscribe at bstc.net
> > > > > or `mail olug-unsubscribe at bstc.net < /dev/null`
> > > > > (c)2001 OLUG http://www.olug.org
> > > > >
> > > > > -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
> > > > >
> > > >
> > > > -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
> > > >
> > > > For help contact olug-help at bstc.net - run by ezmlm
> > > > to unsubscribe, send mail to olug-unsubscribe at bstc.net
> > > > or `mail olug-unsubscribe at bstc.net < /dev/null`
> > > > (c)2001 OLUG http://www.olug.org
> > > >
> > > > -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
> > >
> > >
> > > -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
> > >
> > > For help contact olug-help at bstc.net - run by ezmlm
> > > to unsubscribe, send mail to olug-unsubscribe at bstc.net
> > > or `mail olug-unsubscribe at bstc.net < /dev/null`
> > > (c)2001 OLUG http://www.olug.org
> > >
> > > -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
> > >
> > >
> >
> > -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
> >
> > For help contact olug-help at bstc.net - run by ezmlm
> > to unsubscribe, send mail to olug-unsubscribe at bstc.net
> > or `mail olug-unsubscribe at bstc.net < /dev/null`
> > (c)2001 OLUG http://www.olug.org
> >
> > -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
>
>
> -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
>
> For help contact olug-help at bstc.net - run by ezmlm
> to unsubscribe, send mail to olug-unsubscribe at bstc.net
> or `mail olug-unsubscribe at bstc.net < /dev/null`
> (c)2001 OLUG http://www.olug.org
>
> -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
>
>


-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_

For help contact olug-help at bstc.net - run by ezmlm
to unsubscribe, send mail to olug-unsubscribe at bstc.net
or `mail olug-unsubscribe at bstc.net < /dev/null`
(c)2001 OLUG http://www.olug.org

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_

More information about the OLUG mailing list