the 8139too is the module name of the RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support (NEW) option. Note: in menuconfig you can press "h" to get some more details about an option.The one below the experimental one.I'm kinda new to Linux as well but I think if you want to use modules you should compile all the drivers you want to try as modules then you only have to compile the kernel once. But if you don't mind just try compiling in the 8139too driver into the kernel.-ToshiDate: Wed, 3 Jan 2007 23:58:16 +0100From: helgeingvart@gmail.comTo: satowh@hotmail.comSubject: Re: Netgear FA-311CC: jgilmour@bigpond.net.au; crux@lists.crux.nulspci lists in one of it's lines:00:10.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139 C+ (rev 10)Found this (as experimental) in the same place as the National Semincondutor driver, and thus enabled it with *. Recompiled and installed new kernel. WOW: eth0 up and running! Got these warnings though:8139cp: pci dev 0000:00:10.0 (id 10ec:8139 rev 10) is not an 8139C+ compatible chip8139cp: Try the "8139too" driver instead.How can I build and install this module, since it seems that it's not part of kernel config? Any hints on documents describing such a process on crux? HelgeOn 1/3/07, Hitoshi Satow <satowh@hotmail.com> wrote: Yes, a * means it's compiled into the kernel. While an M means it can be loaded into the kernel as a module.It shouldn't matter if it's built in the kernel or as a module. I think modules just allow more flexibility for configuring your system and switching hardware. You should have a * on EISA, VLB, PCI and on board controllersand a * on National Semiconductor DP8381x series PCI Ethernet supportcheck dmesg and lspci -> is your hardware physically installed correctly in the computer? Check all your connections.-Toshi Date: Wed, 3 Jan 2007 21:34:13 +0100From: helgeingvart@gmail.comTo: jgilmour@bigpond.net.auSubject: Re: Fwd: Netgear FA-311CC: crux@lists.crux.nu Then it's not compiled in either. The natsemi code is located in:Device drivers -> Network device support -> Ethernet (10 or 100Mbit) -> EISA, VLB, PCI and on board controllers (i think this is a 2.6.19.xthing) -> National Semiconductor DP8381x series ...I've done all this already before. However I have a * on National Semiconductor DP8381x series, does that mean that its somehow compiled into the kernel,and not loaded as a module, and thus not visible in /sys/modules? Also, I'm running a 2.6.15.6 kernel, dunno if that means anything? That was the latest 2.2 image though. I will try to mark it with m instead and load it using modprobe inmy net script to see if that makes a difference. If you've enabled kernel modules above then you can select m or * and ifyou haven't then you'll only be able to select *. Either way should befine.I already have a m marked on the EISA, VLB, PCI and on board controllers. Now once you've done recomiled your kernel and run lilo and rebootedthen check that eth0 will be available with ifconfig -a. The reason a lot of this stuff isn't in the handbook or on the CD isthat it is assumed that someone interested in CRUX will have a firmgrasp of setting up hardware and software and recompiling kernels. If you're willing to working through these challenges though it is a veryrewarding distribution.Please bear with me, I'm not very often using Linux, but I will morein the future. Anyway, thanks for your support. And yes: I am learning... Regard,Helge F. Get free, personalized online radio with MSN Radio powered by Pandora. Try it! _________________________________________________________________ Get the Live.com Holiday Page for recipes, gift-giving ideas, and more. www.live.com/?addtemplate=holiday