From dsanders@u.washington.edu Sat Sep 11 01:37:28 1999 Received: from jason04.u.washington.edu (root@jason04.u.washington.edu [140.142.78.5]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id BAA53332 for ; Sat, 11 Sep 1999 01:37:27 -0700 Received: from dante28.u.washington.edu (dsanders@dante28.u.washington.edu [140.142.15.83]) by jason04.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id BAA15368 for ; Sat, 11 Sep 1999 01:37:26 -0700 Received: from localhost (dsanders@localhost) by dante28.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id BAA78314 for ; Sat, 11 Sep 1999 01:37:26 -0700 Date: Sat, 11 Sep 1999 01:37:25 -0700 (PDT) From: "D. Sanderson" To: UW Linux Group Subject: Re: Help! Not initializing eth0! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Many thanks for your response! I simply recompiled the kernel and modules, and everything worked OK. My mistake was to trying and install the new kernel via RPM directly. :) On Sat, 11 Sep 1999, Christopher Twigg wrote: > This might be a bit late (I was out of town) but check if the correct > module is getting loaded by doing a 'cat /proc/modules'. My best guess is > that one of the RPMs toasted your /etc/conf.modules somehow so you might > take a look at that. As far as updating your modules goes, the RPMs > and a reboot should take care of that but hopefully if you mess around > with loading your ethercard module by hand you'll be able to figure out > where it's going wrong. You didn't mention what kind of card you've got; > I've been having a lot of trouble with DEC Tulip cards and newer (2.2.10+) > kernels that I had to grab a newer driver for. One thing you could try is > find out who maintains the driver for your card, grab the latest version, > compile it by hand (according to instructions that I can dig up if > necessary), stuff it in the /lib/modules directory, and insmod it. One > would hope there would be a better solution, though. > > Christopher Twigg > cdtwigg@u.washington.edu > > On Tue, 7 Sep 1999, mike h wrote: > > > Assuming you load your network drivers as a module, if you updated the > > kernel I bet you'll also need to update your modules. Try loading your > > network card's driver using 'insmod' and see if it works. > > > > ----------------------------------------------- > > Michael Hornung foobar@u.washington.edu > > > > On Tue, 7 Sep 1999, D. Sanderson wrote: > > > > | > > |My box has been up and using the ethernet card for a couple of months. I > > |just installed ssh and added /usr/local/sbin/sshd to /etc/rc.d/rc.local, > > |and to make sure it starts up properly after a reboot, I shutdown -r now'd > > |the thing. > > | > > |Rh6.0 has that nice colored "OK/FAILED" thing next to items during start > > |up, and eth0 came up FAILED. It said it was going to delay initializing > > |eth0. It never got around to it, and now my server is inaccessible. > > | > > |Obviously I must mention that last night I downloaded and rpm -Fvh'd > > |everything in the RH6.0 "updates" directory, including the slightly newer > > |kernel. Do I need to recompile the kernel or something? Is there another > > |update that might have knocked out eth0 functionality? > > | > > |I don't even know where to begin diagnosing this problem. The card works > > |(before the reboot it did), the lights are all on. > > | > > |Any help I can get as soon as possible would be greatly appreciated! > > |Thanks! > > | > > |_____________________________________________________________________ > > |Dan Sanderson dsanders@u.washington.edu > > |University of Washington http://students.washington.edu/dsanders > > | > > | > > > > > > _____________________________________________________________________ Dan Sanderson dsanders@u.washington.edu University of Washington http://students.washington.edu/dsanders .