Hi guys,

I've a 100Mbit Dlink VIA Rhine based network card. lspci gives it as
00:0e.0 Ethernet controller: VIA Technologies, Inc. VT6105 [Rhine-III] (rev 86)

I compiled my 2.6.7 kernel with VIA Rhine support modularized. I could then modprobe via-rhine (lsmod shows it) and bring eth0 up fine. ifconfig give something like

eth0 Link encap:Ethernet HWaddr 00:05:5D:63:A6:E8
inet addr:192.168.254.5 Bcast:192.168.254.255 Mask:255.255.255.0
inet6 addr: fe80::205:5dff:fe63:a6e8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1743 errors:0 dropped:0 overruns:0 frame:0
TX packets:1720 errors:0 dropped:0 overruns:0 carrier:0
collisions:19 txqueuelen:1000
RX bytes:529718 (517.3 Kb) TX bytes:233191 (227.7 Kb)
Interrupt:5 Base address:0x5000


I then recompiled with VIA Rhine support included into the kernel. However, now I cannot bring eth0 up and ifconfig tells me "error fetching interface information: Device not found" which I suppose means that the card is not detected, right?

Is compiling support into the kernel equivalent to modularizing that support and modprobing, because this seems to be the only difference in my actions. Am I missing something when compiling support into the kernel.

Oh, I'm running gentoo 1.4.16 and to compile the kernel in both cases i do
make && make modules_install
then
cp arch/i386/boot/bzImage /boot/kernel-2.6.7
cp System.map /boot/System.map-2.6.7
and reboot.

Thankyou.

Make sure that you are doing a make mrproper on the kernel before doing the make menuconfig or whatever one your using to select kernel mods. Then make sure you do a "make all" instead of just a "make". Not sure if make only builds the stuff in the kernel and not the modules. Every thing else looks fine tho.


Druisgod

Thankyou for your reply druisgod. Unfortunately, I'm still getting the same results.