Re: modprobe errors after apt-get upgrade

1999-10-16 Thread Pollywog
On 16-Oct-99 Christian Dysthe wrote: > On 16 Oct, Martin Fluch wrote: > >> >> Then there seems to be some modules in the directory, wich are not needed, >> e.g. they are left from the previous kernel... (have a look at their date) >> ... I guess you can savely remove them ... or move /lib/module

Re: modprobe errors after apt-get upgrade

1999-10-16 Thread Christian Dysthe
On 16 Oct, Martin Fluch wrote: > > Then there seems to be some modules in the directory, wich are not needed, > e.g. they are left from the previous kernel... (have a look at their date) > ... I guess you can savely remove them ... or move /lib/modules/2.2.12 to > /lib/modules/2.2.12.old and inst

Re: modprobe errors after apt-get upgrade

1999-10-15 Thread Martin Fluch
On Fri, 15 Oct 1999, Christian Dysthe wrote: > On 16 Oct, Martin Fluch wrote: > > > Then recompile the kernel ... that should work. > > > > Nope, did that. Same errors. Then there seems to be some modules in the directory, wich are not needed, e.g. they are left from the previous kernel... (h

Re: modprobe errors after apt-get upgrade

1999-10-15 Thread Christian Dysthe
On 16 Oct, Martin Fluch wrote: > Then recompile the kernel ... that should work. > Nope, did that. Same errors. -- Regards, Christian Dysthe E-mail: [EMAIL PROTECTED] Web: http://oddbird.dyndns.org/cdysthe/ ICQ 3945810 Powered by Debian GNU/Linux -

Re: modprobe errors after apt-get upgrade

1999-10-15 Thread Martin Fluch
On Fri, 15 Oct 1999, Christian Dysthe wrote: > On 15 Oct, Martin Fluch wrote: > > > depmod -a > > > Did depmod -a This is what I got: > > depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/aten.o > depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/bpck.o > depmod: *** Unresolved

Re: modprobe errors after apt-get upgrade

1999-10-15 Thread Pollywog
On 15-Oct-99 David Natkins wrote: > You upgrade to a new version of modutils. Do an update-modules. > That was the first thing I did. It did not stop the messages. thanks -- Andrew

Re: modprobe errors after apt-get upgrade

1999-10-15 Thread Pollywog
On 15-Oct-99 Christian Dysthe wrote: > On 15 Oct, Martin Fluch wrote: > >> depmod -a >> > Did depmod -a This is what I got: I got: depmod: *** Unresolved symbols in /lib/modules/2.2.12/misc/snd.o -- Andrew

Re: modprobe errors after apt-get upgrade

1999-10-15 Thread Christian Dysthe
On 15 Oct, Martin Fluch wrote: > depmod -a > Did depmod -a This is what I got: depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/aten.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/bpck.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/comm.o depmod: *** Unresolved

Re: modprobe errors after apt-get upgrade

1999-10-15 Thread Christian Dysthe
On 15 Oct, Pollywog wrote: > I did an upgrade of my potato system yesterday, and now I am getting this > error even though I went back to the /etc/modules.conf I was using before the > upgrade. > > Oct 15 16:56:47 lilypad modprobe: Note: /etc/modules.conf is more recent than > /lib/modules/2.2.12/

Re: modprobe errors after apt-get upgrade

1999-10-15 Thread Martin Fluch
On Fri, 15 Oct 1999, Pollywog wrote: > I did an upgrade of my potato system yesterday, and now I am getting this > error even though I went back to the /etc/modules.conf I was using before the > upgrade. > > Oct 15 16:56:47 lilypad modprobe: Note: /etc/modules.conf is more recent than > /lib/modu

Re: modprobe errors after apt-get upgrade

1999-10-15 Thread David Natkins
You upgrade to a new version of modutils. Do an update-modules. Pollywog wrote: > > I did an upgrade of my potato system yesterday, and now I am getting this > error even though I went back to the /etc/modules.conf I was using before the > upgrade. > > Oct 15 16:56:47 lilypad modprobe: Note: /et