I just backed up my files, wiped the drive, and installed 7.0 fresh. I know
it's the hard way, but I figured it was a good opportunity to scrutinize
what's installed and running now that I've been running RH for a little
while. Thus, the old mods were gone, but I copied the mods I was using into
the RH7.0 collection. However, because they were of the previous kernel
version, they refused to work, so I had to recompile.
I got frustrated with it, so I bought another Linksys card of the same model
and revision as the original and installed it and the drivers. The cards
seem to work ok now, but I keep getting this "SIOCADDR??: Network not found"
error when I bind eth1 interface to the local network. Seems to work fine,
though. Plus, I'll get an occasional martian log in my messages log. What
do these mean?
I believe the original problem (when I had 2 different cards) was that the
linksys and netgear NICs are both based on modified tulip drivers. So the
linksys, being notorious for not working well with other tulip cards, kept
screwing up on a request for the netgear card. That's my theory, anyway.
Driver confusion. Am I totally off?
Drew
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Luke C Gavel
Sent: Saturday, January 20, 2001 5:01 PM
To: RedHat general mailling list
Subject: Re: Ethernet driver woes
On Sat, 20 Jan 2001, Luke wrote:
> On Mon, 15 Jan 2001, Drew Hunt wrote:
>
> <snip>
>
> > kernel RPM form RH, it stopped masqing FTPs because the ipv4 mods were
"not
> > of the current kernel version". Ok, so I figure this is a nice
opportunity
> > to upgrade to RH7.0 since I have it installed on two other machines and
has
> > been working great. That way I get the newer kernel, update the system
> > files and the right ipv4 mods all in the same package. Wrong...
>
> <snip>
>
> > Now the drivers I was using for 6.2 (kernel 2.2.16-3) are now crap in
the RH
> > 7.0 kernel (2.2.16-20?). I could only find source for one (the Linksys)
to
>
> <snip>
>
> try upgrading mod-utils-X.X.X.rpm as well. Did you?
>
>
Also, check in /lib/modules and see what is happening there. Is
there a 'rpmsave' thingy of any sort? Did it leave the old
kernel modules alone, or did it try to blindly mesh the new with
the old in some screw-upped sort of way? *tsks at RHAT kernel
rpm developers* What about re-running 'ldconfig' for the dlls?
_______________________________________________
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
