Re: Ethernet troubles
Ooops:
On Tue, 2004-03-09 at 09:44, Nick THOMPSON accidentally wrote the
following in HTML and would like to apologise for any inconvenience
caused:
> I don't think thats it. I was upgrading from 2.2.20 to 2.4.18-1-586tsc
> (what does the tsc mean?) and I think it was seeing the appropriate
> /lib/modules directory. I did rename the 2.2.20 dir anyway, but it
> didn't help at all.
>
> Seems the 3c509 driver thinks it has found two ethernet ports, 0x220
> and 0x300 IIRC on IRQ 5 and 10 respectively. I'm sure I only have the
> one though. eth0 in ifconfig -a actually does seem to have a correct
> IP address (10.0.0.60) and says it has sent out packets, though RXed
> none. eth1 is not even configured, but then it doesn't exist....
>
> I still get complaints about /etc/modules.conf being newer than
> /lib/modules/2.4.18-1-586tsc/modules.dep. Each boot a lot of time is
> spent generating the modules dependencies, but it looks like that is
> never saved. I guess this issue should be sorted out first before I
> start to wonder about why the ethernet doesn't work...?
>
> Did I mess up upgrading the kernel, by only doing and "apt-get install
> kernel-image-..."? Was there some other magic I missed that would have
> smoothed the upgrade?
>
> Thanks,
> Nick.
>
> On Mon, 2004-03-08 at 19:35, Sylvain Cauchon wrote:
> > Nick THOMPSON wrote:
> >
> > > Hi,
> > >
> > > I'm new to Debian and am considering switching over from Mandrake. I
> > > have a test installation installed just last week (woody network
> > > install) that was working well. I easily upgraded it to KDE3.2 and then
> > > attempted an upgrade of the kernel to the latest stable for woody
> > > (2.4.18 IIRC). Anyway, I started out the kernel upgrade with a single
> > is still loaded automatically, but I do get a warning that my
> > > /etc/modules.conf is newer that my blah-blah-blah.dep file several times
> > > during the boot sequence. Sorry - don't remember the file name.
> > >
> > > Any ideas as to how I should proceed from here would be very gratefully
> > > received.
> >
> > >
> > Hi There,
> > Sounds like you did not rename your modules before proceeding with the
> > installation of a new kernel image of the same version. Is this the
> > case? if so you should rename your old /lib/modules/2.x.x tol
> > /lib/modules/old2.x.x. this will allow the newer kernel to access the
> > correct modules hope this helps bye for now syl
Reply to: