> Date: Tue, 15 May 2007 06:26:44 -0700> From: [EMAIL PROTECTED]> To:
> [email protected]> Subject: Re: NIC Driver Installation
> Problems> > On 5/15/07, Daniel Rozeboom <[EMAIL PROTECTED]> wrote:> >> >
> Sorry to have to e-mail this question out to everyone, but I have asked it> >
> on linuxquestions.org and haven't received much help (and I don't have> >
> access to IRC behind my proxy). I have a relatively clean LFS build and I'm>
> > working on putting some BLFS packages on. My network card (a Realtek> >
> RTL8168/8111) had never been automatically recognized, so I tried to install>
> > the drivers provided by Realtek, but I had the following output after
> "make> > modules" that seems to indicate some unhappy errors:> >> >
> ********************************************************> > make -C src/
> modules> > make[1]: Entering directory `/usr/src/r1000_v1.05/src'> > make
> -C /lib/modules/2.6.16.27/build> > SUBDIRS=/usr/src/r1000_v1.05/src modules>
> > make[2]: Entering directory `/sources/linux-2.6.16.27'> >> > WARNING:
> Symbol version dump /sources/linux-2.6.16.27/Module.symvers> > is missing;
> modules will have no dependencies and modversions.> >> > CC [M]
> /usr/src/r1000_v1.05/src/r1000_n.o> > In file included from
> include/linux/module.h:10,> > from /usr/src/r1000_v1.05/src/r1000.h:1,> >
> from /usr/src/r1000_v1.05/src/r1000_n.c:5:> > include/linux/sched.h:4:36:
> error: asm/param.h: No such file or directory> > You seem to be missing your
> kernel source tree.> > The external module needs to build against the linux
> source tree for> each version of the kernel. The way you do this is by
> keeping the> linux-* directory instead of deleting it. Customarily, the
> symlinks at> /lib/modules/$version/{build,source} are updated to point to
> the> location on disk where you've placed your configured source tree. You>
> can see at the beginning of the output that it's trying to change to> this
> directory:> > > make -C /lib/modules/2.6.16.27/build> > So, you'll have to
> rebuild a new kernel (grab the latest 2.6.16> version) and keep the
> directory. Update the symlinks in> /lib/modules/2.6.16.*/{build,source} and
> then you should be able to> restart this process with the realtek drivers.> >
> --> Dan> -- > http://linuxfromscratch.org/mailman/listinfo/blfs-support> FAQ:
> http://www.linuxfromscratch.org/blfs/faq.html> Unsubscribe: See the above
> information page
Hi Dan, Thanks so much for the quick response -
I loaded up a 2.6.16.51 kernel tree and (after fixing errors in the
source code file for the driver) managed to get the module installed
and running. However, I'm still not getting connectivity yet (I know
this is probably beyond the domain of BLFS, but perhaps you can lend
some insight). The module loads up fine and recognizes my card as
eth0, but it always seems to say "Link Status: Not Linked" and DHCP
will fail due to a timeout error. Is this link status equivalent to
the driver detecting connectivity with a hub or the like? I never see
any received packets show up with ifconfig, but I do see two
transmitted packets for each DHCP attempt. I saw your post on the net
about checking for cable connectivity
(http://linuxfromscratch.org/pipermail/blfs-dev/2006-October/015767.html),
but on my system, /sys/class/net/eth0/carrier has no contents (neither
a 1 nor a 0) - do you know why that might be? Thanks for any advice
you can offer.- Daniel
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
