ifup, both at boot time, and when called manually, prints:
"Delaying eth0 initialization"
At 06:17 PM 8/25/2000 -0500, you wrote:
>Ok I made a symlink in /lib/modules (2.2.14 -> 2.2.14-5.0), but now it
>claims there's a modules mismatch between kernel numbers! What the heck?
>I"ve never seen such a blasted set up. How in the world is it that this
>didn't happen to other people? Did I forget to install something? I did a
>custom install, but mostly I increase the number of packages - in fact I
>don't thing I un-marked a single rpm.
>
>The exact error is:
>[root@bismuth]# modprobe rtl8139
>/lib/modules/2.2.14/net/rtl9139.o: kernel version mismatch
> /lib/modules/2.2.14/net/rtl9139.o was compiled for kernel version
> 2.2.14-5.0 while this kernel is version 2.2.14.
>
>then the usual insmod: failed insmod: failed stuff.
>
>I have a totally broken modprobe package?
>
>
>Trying to stay calm,
>
> JW
>
>
>
>
>At 06:07 PM 8/25/2000 -0500, you wrote:
>>Well, I'm not even sure what to say. I've been using Linux for over a
>>year now, used 4 distros, and installed it dozen of time, but I can't get
>>my eth0 to work at all on Red hat 6.2
>>
>>It's a linksys, I belive, and it was auto-detected as a "rtl8139" (I can
>>see that in both linuxconf and if I cat /etc/conf.modules)
>>
>>If I remember correctly that's exactly what SuSE 6.4 saw it as and it
>>DOES work on in SuSE.
>>
>>I don't want to get onto a Red-Hat-is-bad band wagon, but this makes me
>>want to cry. I tried to use linuxconf through telnet to change the root
>>password on a remote server and that failed, too. Fortunately good ol'
>>"passwd" didn't fail.
>>
>>Anyway, route -n shows 127.0.0.1 only.
>>
>>All of the correct information still shows up in linuxconf after
>>rebooting, but none-the-less there's still no eth0 working.
>>
>>Has anyone else had this problem? I know that Linsyscards are cheesy, put
>>honestly....I've had it working in both Stormix and Suse and Debian on
>>this very box.
>>
>>if use linuxconf or netconfig, both go through the motions with no
>>errors, but nothing changes. However if I use ifconfig I get something
>>like this:
>>
>>[note that somehow it does manage to remember the host name :-)]
>>[root@bismuth]# ifconfig eth0 192.168.0.70
>>SIOSIFADDR: No such device
>>eth0: unknown interface: no such device
>>[root@bismuth]#
>>
>>What is going on here?
>>
>>Also note that conf modules is _entirely_ composed of the following:
>>
>>[root@bismuth]3 cat /etc/conf.modules
>>alias eth0 rtl8139
>>alias parport_lowlevel parport_pc
>>[root@bismuth]#
>>
>>In suse it's way longer then that!
>>
>>I also notice that lsmod also shows _nothing_
>>
>>If I do "modprobe rtl8139" I get:
>>
>>modprobe: Can't open /lib/modules/2.2.14/modules.dep (no such file or
>>directory)
>>
>>That Ain't no lie, because there _is_ no /lib/modules/2.2.14 - the only
>>thing in there is /lib/modules/2.2.14-5.0
>>
>>Should there be a symlink? What a blasted thing to have missing!
>>
>>[root@bismuth]# depmod -a
>>depmod: Can't open /lib/modules/2.2.14/modules.dep for writing
>>
>>Even the slightest clue would be greatly appreciated.
>>
>> JW
>>
>>
>>
>>_______________________________________________
>>Redhat-list mailing list
>>[EMAIL PROTECTED]
>>https://listman.redhat.com/mailman/listinfo/redhat-list
>
>
>
>_______________________________________________
>Redhat-list mailing list
>[EMAIL PROTECTED]
>https://listman.redhat.com/mailman/listinfo/redhat-list
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
