Linux kernel 2.0.35 and Intep EEPro 10+/100B/100+
Scott Stone
sstone@ume.pht.co.jp
Wed Sep 30 04:31:06 1998
On Tue, 29 Sep 1998, Nikica Petrinic wrote:
> Dear Scott,
>
> Thanks again. Still no luck :( .
>
> I made eepro100 a module by changing only three things in make xconfig:
> 1) enabled modules support
> 2) enabled CONFIG_KERNELD
> 3) changed from Y to M for EEPro
> and recompiled kernel and made/installed modules.
>
> - I checked if the dirver ended up in /lib/modules/2.0.35/net - positive.
> - I checked if /etc/rc.d/rc.sysinit is 'clever' enough to know about loading
> modules at boot - positive.
> - I checked that /etc/conf.modules contains 'alias eth0 eepro100' - positive
>
> I attached the things I recorded following various advice I collected over the
> last few days. I am not panicking just as yet - but I'm getting there.
>
> Nik
>
> output from ifconfig
> ------------------------------
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
> UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1
> RX packets:233 errors:0 dropped:0 overruns:0
> TX packets:233 errors:0 dropped:0 overruns:0
>
> eth0 Link encap:Ethernet HWaddr 00:A0:C9:C7:32:6A
> inet addr:163.1.9.124 Bcast:163.1.9.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0
> TX packets:31 errors:0 dropped:0 overruns:31
> Interrupt:10 Base address:0xe4e0
It's like I said before - your kernel is configured correctly - your
problem lies somewhere else, such as your TCP/IP settings, your hub, your
cabling, or something of that nature.
--------------------------------------------------
Scott M. Stone <sstone@pht.com, sstone@turbolinux.com>
<sstone@pht.co.jp>
Head of TurboLinux Development/Systems Administrator
Pacific HiTech, Inc (USA) / Pacific HiTech, KK (Japan)
http://www.pht.com http://armadillo.pht.co.jp
http://www.pht.co.jp http://www.turbolinux.com